116 it is in the middle of the word, it might have a "tail" on both sides to join |
116 it is in the middle of the word, it might have a "tail" on both sides to join |
117 it to the letters that appear before and after. </p> <fig id="GUID-30A9DA99-E1C5-5EE5-AEB3-0BCD6DB0A692"> |
117 it to the letters that appear before and after. </p> <fig id="GUID-30A9DA99-E1C5-5EE5-AEB3-0BCD6DB0A692"> |
118 <title> Figure 1: Handwriting simulation might use different |
118 <title> Figure 1: Handwriting simulation might use different |
119 glyphs for the letter p depending on its position in a word |
119 glyphs for the letter p depending on its position in a word |
120 </title> |
120 </title> |
121 <image href="GUID-8F19C257-9A41-5D38-BC8A-285D0EB16E1B_d0e402675_href.png" placement="inline"/> |
121 <image href="GUID-8F19C257-9A41-5D38-BC8A-285D0EB16E1B_d0e402513_href.png" placement="inline"/> |
122 </fig> <p>Contextual shaping is an essential feature of some scripts, including |
122 </fig> <p>Contextual shaping is an essential feature of some scripts, including |
123 Arabic and many Indian and East Asian scripts, such as Devanagari, Kannada, |
123 Arabic and many Indian and East Asian scripts, such as Devanagari, Kannada, |
124 Telugu, Tamil, Bengali, Malayalam and Gurmukhi. For this reason, support for |
124 Telugu, Tamil, Bengali, Malayalam and Gurmukhi. For this reason, support for |
125 contextual shaping is sometimes referred to as <b>Brahmic support</b>. </p> </dd> |
125 contextual shaping is sometimes referred to as <b>Brahmic support</b>. </p> </dd> |
126 </dlentry> |
126 </dlentry> |
142 of the current graphics device. The diagram below shows how BitGDI implements |
142 of the current graphics device. The diagram below shows how BitGDI implements |
143 Graphics Devices and Contexts. </p> <fig id="GUID-36165480-E5BC-50F3-B205-5668EA7F0306"> |
143 Graphics Devices and Contexts. </p> <fig id="GUID-36165480-E5BC-50F3-B205-5668EA7F0306"> |
144 <title> Figure 2: The Graphics Device and Context Architecture. |
144 <title> Figure 2: The Graphics Device and Context Architecture. |
145 </title> |
145 </title> |
146 <desc><p>Note that the names of the BitGDI classes begin with <codeph>CFbs</codeph>. </p> </desc> |
146 <desc><p>Note that the names of the BitGDI classes begin with <codeph>CFbs</codeph>. </p> </desc> |
147 <image href="GUID-9D6D07D3-A93C-5290-AC08-15750AD34802_d0e402733_href.png" placement="inline"/> |
147 <image href="GUID-9D6D07D3-A93C-5290-AC08-15750AD34802_d0e402571_href.png" placement="inline"/> |
148 </fig> <p>Applications access font services through the <xref href="GUID-71DADA82-3ABC-52D2-8360-33FAEB2E5DE9.dita">Font |
148 </fig> <p>Applications access font services through the <xref href="GUID-71DADA82-3ABC-52D2-8360-33FAEB2E5DE9.dita">Font |
149 and Bitmap Server (FBSERV)</xref> which caches font bitmaps in a shared heap. |
149 and Bitmap Server (FBSERV)</xref> which caches font bitmaps in a shared heap. |
150 The Font and Bitmap Server ensures that there is only ever a single instance |
150 The Font and Bitmap Server ensures that there is only ever a single instance |
151 of a particular glyph bitmap in memory. However, eXecute In Place (XIP) ROM-based |
151 of a particular glyph bitmap in memory. However, eXecute In Place (XIP) ROM-based |
152 bitmaps (including fonts) are used in place and are not copied into the heap. </p> <p>Use |
152 bitmaps (including fonts) are used in place and are not copied into the heap. </p> <p>Use |