PageRenderTime 65ms CodeModel.GetById 18ms RepoModel.GetById 1ms app.codeStats 0ms

/htdocs.OLD/ja/gposgsub.html

https://bitbucket.org/sortsmill/sortsmill-tools
HTML | 1545 lines | 906 code | 0 blank | 639 comment | 0 complexity | b84164b98d4ae9cf96c6f2aeeedf7e13 MD5 | raw file
Possible License(s): GPL-3.0, LGPL-2.0 
    

  1. <HTML>

    2. 

  2. <HEAD>

    3. 

  3.   <!-- Created with AOLpress/2.0 -->

    4. 

  4.   <!-- AP: Created on: 29-Dec-2002 -->

    5. 

  5.   <!-- AP: Last modified: 11-Dec-2005 -->

    6. 

  6.   <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=Shift_JIS">

    7. 

  7. <!--<TITLE>Advanced Typography tables</TITLE> -->

    8. 

  8.     <TITLE>?????????? (ATT)</TITLE>

    9. 

  9.   <LINK REL="icon" href="../fftype16.png">

    10. 

  10.   <LINK REL="stylesheet" TYPE="text/css" HREF="FontForge.css">

    11. 

  11. </HEAD>

    12. 

  12. <BODY>

    13. 

  13. <DIV id="in">

    14. 

  14.   <H1 ALIGN=Center>

    15. 

  15. <!--  Advanced Typography Tables-->

    16. 

  16.       ?????????? (ATT)

    17. 

  17.   </H1>

    18. 

  18.   <P>

    19. 

  19. <!--

    20. 

  20.   These differ between OpenType (originally called TrueType Open) and Apple

    21. 

  21.   (GX or Apple Advanced Typography). My support for both OpenType and Apple

    22. 

  22.   is incomplete. -->

    23. 

  23.   ???? OpenType (?? TrueType Open ?????????) ? Apple (GX ??? Apple ????????? (ATT)) ???????????????? OpenType ? Apple ???????????????????

    24. 

  24.   <UL>

    25. 

  25.     <LI>

    26. 

  26. <!--  <A HREF="#opentype">The <B><CODE>GPOS</CODE></B>,

    27. 

  27.       <B><CODE>GSUB</CODE></B> and <B><CODE>GDEF</CODE></B> opentype tables</A>

    28. 

  28.       <A HREF="#opentype"><B><CODE>GPOS</CODE></B>, <B><CODE>GSUB</CODE></B> ??? <B><CODE>GDEF</CODE></B> OpenType ????</A>

    29. 

  29.     <LI>

    30. 

  30. <!--  <A HREF="#AAT">Apple Advanced Typography</A>-->

    31. 

  31.       <A HREF="#AAT">Apple ??????????</A>

    32. 

  32.     <LI>

    33. 

  33. <!--  <A HREF="#Conversion">What features can be converted between OpenType and

    34. 

  34.       AAT?</A>-->

    35. 

  35.       <A HREF="#Conversion">????? OpenType ? AAT ?????????</A>

    36. 

  36.     <LI>

    37. 

  37.       <A HREF="TrueOpenTables.html">other true type and open type tables</A>

    38. 

  38.     <LI>

    39. 

  39.       <A HREF="#Unsupported">What is unsupported</A>

    40. 

  40.     <LI>

    41. 

  41.       <A HREF="non-standard.html">FontForge's non-standard extensions</A>

    42. 

  42.   </UL>

    43. 

  43.   <H2>

    44. 

  44. <!--  The <B><CODE>GPOS,</CODE></B> <B><CODE>GSUB</CODE></B> and

    45. 

  45.       <B><CODE>GDEF</CODE></B> <A NAME="opentype">opentype</A> tables -->

    46. 

  46.       <B><CODE>GPOS</CODE></B>, <B><CODE>GSUB</CODE></B> ??? <B><CODE>GDEF</CODE></B> <A NAME="opentype">OpenType</A> ????

    47. 

  47.   </H2>

    48. 

  48.   <P>

    49. 

  49. <!--

    50. 

  50.   These two tables are used for positioning and substituting glyphs. The GPOS

    51. 

  51.   table can control things like: kerning, accent positioning, cursive joining,

    52. 

  52.   etc. The GSUB table can control things like: ligatures, arabic forms, vertical

    53. 

  53.   rotation, conversion to small caps, indic glyph rearrangement, etc. -->

    54. 

  54.   ????2?????????????????????????????

    55. 

  55.   GPOS ?????????????????????????: ??????????????????????????

    56. 

  56.   GSUB ?????????????????????????: ???????????????????????????????????????????????????

    57. 

  57.   <P>

    58. 

  58. <!--

    59. 

  59.   This page assumes basic familiarity with the abilities of the tables, for

    60. 

  60.   more information on them read, study and inwardly digest the opentype docs

    61. 

  61.   on:-->

    62. 

  62.   ????????????????????????????????????????????????????????????????????? OpenType ???????????????????????????

    63. 

  63.   <UL>

    64. 

  64.     <LI>

    65. 

  65. <!--  <A HREF="http://partners.adobe.com/public/developer/opentype/index_table_formats.html">The

    66. 

  66.       header for both GPOS and GSUB</A>-->

    67. 

  67.       <A HREF="http://partners.adobe.com/public/developer/opentype/index_table_formats.html">GPOS ? GSUB ????????</A>

    68. 

  68.     <LI>

    69. 

  69. <!--  <A HREF="http://partners.adobe.com/public/developer/opentype/index_table_formats2.html">The

    70. 

  70.       GPOS table</A>, for positioning glyphs -->

    71. 

  71.       <A HREF="http://partners.adobe.com/public/developer/opentype/index_table_formats2.html">GPOS ???? (????????????)</A>

    72. 

  72.     <LI>

    73. 

  73. <!--  <A HREF="http://partners.adobe.com/public/developer/opentype/index_table_formats1.html">The

    74. 

  74.       GSUB table</A>, for substituting glyphs-->

    75. 

  75.       <A HREF="http://partners.adobe.com/public/developer/opentype/index_table_formats1.html">GSUB ????</A> (??????????)

    76. 

  76.     <LI>

    77. 

  77. <!--  <A HREF="http://partners.adobe.com/public/developer/opentype/index_table_formats5.html">The

    78. 

  78.       GDEF table</A>, for classifying glyphs and for providing a ligature caret

    79. 

  79.       table -->

    80. 

  80.       <A HREF="http://partners.adobe.com/public/developer/opentype/index_table_formats5.html">GDEF ???? (????????????????????????????)</A>

    81. 

  81.     <LI>

    82. 

  82. <!--  <A HREF="http://partners.adobe.com/public/developer/opentype/index_tag3.html">The

    83. 

  83.       list of feature tags supported by opentype</A>-->

    84. 

  84.       <A HREF="http://partners.adobe.com/public/developer/opentype/index_tag3.html">OpenType ???????????????</A>

    85. 

  85.     <LI>

    86. 

  86. <!--  <A HREF="http://partners.adobe.com/public/developer/opentype/index_tag1.html">The

    87. 

  87.       list of script tags supported by opentype</A>-->

    88. 

  88.       <A HREF="http://partners.adobe.com/public/developer/opentype/index_tag1.html">OpenType ????????????????</A>

    89. 

  89.     <LI>

    90. 

  90. <!--  -<A HREF="http://partners.adobe.com/public/developer/opentype/index_tag2.html">The

    91. 

  91.       list of language tags supported by opentype</A>-->

    92. 

  92.       <A HREF="http://partners.adobe.com/public/developer/opentype/index_tag2.html">OpenType ???????????????</A>

    93. 

  93.   </UL>

    94. 

  94.   <P>

    95. 

  95. <!--

    96. 

  96.   The basic idea of the GPOS and GSUB tables is that each script (or language

    97. 

  97.   within a script) has a set of "features" that are available to it. A feature

    98. 

  98.   in turn is associated with a lookup which contains data for the feature.

    99. 

  99.   An example of a script is 'latn' for latin, 'arab' for arabic, 'hani' for

    100. 

  100.   chinese ideographs. Two examples of features are 'kern' which provides kerning

    101. 

  101.   information between pairs of glyphs and 'init' which will transform one set

    102. 

  102.   of glyphs to another when those glyphs are at the beginning of a word.-->

    103. 

  103.   GPOS ????? GSUB ????????????????????? (?????????????????) ??????????????“??”?????????????????????????????????????????? 1 ?????????????????????????????&lsquo;latn&rsquo;, ???????&lsquo;arab&rsquo;, ???&lsquo;hani&rsquo;????????????? 2 ??????????????????????????&lsquo;kern&rsquo;?????????????????????????????????????&lsquo;init&rsquo;??????

    104. 

  104.   <P>

    105. 

  105. <!--

    106. 

  106.   FontForge <A HREF="gposgsub.html#Unsupported">does not support </A>the full

    107. 

  107.   range of possibilities inherent in these tables. -->

    108. 

  108.   FontForge ?????? 2 ??????????????????????<A HREF="gposgsub.html#Unsupported">???????????????</A>?

    109. 

  109.   <H3>

    110. 

  110. <!--  The <B><CODE><A NAME="GPOS">GPOS</A></CODE></B> table-->

    111. 

  111.       <B><CODE><A NAME="GPOS">GPOS</A></CODE></B> ????

    112. 

  112.   </H3>

    113. 

  113.   <P>

    114. 

  114. <!--

    115. 

  115.   FontForge will read the following sub tables of the GPOS table: -->

    116. 

  116.   FontForge ? GPOS ?????????????????????:

    117. 

  117.   <TABLE Border=1>

    118. 

  118.     <TR>

    119. 

  119.       <TH></TH>

    120. 

  120.       <TH>name</TH>

    121. 

  121. <!--  <TH>Reading support</TH>-->

    122. 

  122.       <TH>????????</TH>

    123. 

  123. <!--  <TH>Writing support</TH>-->

    124. 

  124.       <TH>????????</TH>

    125. 

  125.     </TR>

    126. 

  126.     <TR>

    127. 

  127.       <TD>1</TD>

    128. 

  128. <!--  <TD>single adjustment</TD>-->

    129. 

  129.       <TD>1 ?????</TD>

    130. 

  130. <!--  <TD>This sub-table allows the font designer to change the metrics of a specific

    131. 

  131.         glyph. The feature tag will provide a context in which the change should

    132. 

  132.         occur. For instance the 'tnum' (tabular numbers) feature could change a

    133. 

  133.         proportionally spaced digit by adjusting its advance width to be some set

    134. 

  134.         value and then centering the digit (by adjusting the left side bearing) within

    135. 

  135.         the new width.</TD>-->

    136. 

  136.       <TD>????????????????????????????????????????????????????????????????????????????&lsquo;tnum&rsquo; (????) ??????????????????????????????????? (??????????????) ???????????????????????????????????????</TD>

    137. 

  137. <!--  <TD>These can be created with the <A HREF="charinfo.html">Element-&gt;Char

    138. 

  138.         Info</A>-&gt;Position command.</TD>-->

    139. 

  139.       <TD>???? <A HREF="charinfo.html"><CODE>?????(<U>L</U>)</CODE>?<CODE>?????(<U>I</U>)...</CODE></A>?<CODE>[??]</CODE> ?????????????????</TD>

    140. 

  140.     </TR>

    141. 

  141.     <TR>

    142. 

  142.       <TD>2</TD>

    143. 

  143. <!--  <TD>pair adjustment</TD>-->

    144. 

  144.       <TD>????????</TD>

    145. 

  145. <!--  <TD>This sub-table allows the font designer to change the metrics of a specific

    146. 

  146.         pair of glyph. The most common use of this is for kerning where the advance

    147. 

  147.         width of the first glyph is altered depending on which glyph follows it.

    148. 

  148.         But the table is more general than that and could support mark (accent, vowel)

    149. 

  149.         positioning over a base glyph (though that is more efficiently done with

    150. 

  150.         the mark to base subtable).</TD> -->

    151. 

  151.       <TD>????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? (????????) ??????????????????? (?????????????????????????????????????????????????)?

    152. 

  152.   </TD>

    153. 

  153. <!--  <TD>'kern' feature s may be created from the <A HREF="metricsview.html">Metrics

    154. 

  154.         View</A>. 'vkrn' with

    155. 

  155.         <A HREF="metricsmenu.html#VKernFromHKern">Metrics-&gt;VKern From HKern</A>.</TD>-->

    156. 

  156.       <TD>&lsquo;kern&rsquo;???????????????????????&lsquo;vkrn&rsquo;? <A HREF="metricsmenu.html#VKernFromHKern"><CODE>?????(<U>M</U>)</CODE>?<CODE>?????????????</CODE></A>?????????????</TD>

    157. 

  157.     </TR>

    158. 

  158.     <TR>

    159. 

  159.       <TD>3</TD>

    160. 

  160. <!--  <TD>cursive attachment</TD>-->

    161. 

  161.       <TD>??????</TD>

    162. 

  162. <!--  <TD>This sub-table allows the font designer to force adjacent characters

    163. 

  163.         to join at specific points. It can be used to generate the slanted script

    164. 

  164.         style needed for Urdu.</TD> -->

    165. 

  165. <!--  <TD>This sub-table allows the font designer to force adjacent glyphs to join

    166. 

  166.         at specific points. It can be used to generate the slanted script style needed

    167. 

  167.         for Urdu.</TD> -->

    168. 

  168.       <TD>?????????????????????????????????????????????????????????????????????????????????????????????????</TD>

    169. 

  169. <!--  <TD>Only the 'curs' feature is supported for this sub-table. These may be

    170. 

  170.         created with the <A HREF="pointmenu.html#AddAnchor">Points-&gt;Add Anchor</A>

    171. 

  171.         command</TD>-->

    172. 

  172.       <TD>????????????????????&lsquo;curs&rsquo;???????????<A HREF="pointmenu.html#AddAnchor"><CODE>?(<U>P</U>)</CODE>?<CODE>???????(<U>A</U>)...</CODE></A> ???????????????

    173. 

  173.     </TR>

    174. 

  174.     <TR>

    175. 

  175.       <TD>4</TD>

    176. 

  176. <!--  <TD>mark to base</TD>-->

    177. 

  177.       <TD>???????????</TD>

    178. 

  178. <!--  <TD>This sub-table allows the font designer to specify how mark glyphs (accents,

    179. 

  179.         vowel signs, etc.) are positioned over base glyphs. Every glyph can have

    180. 

  180.         an attachment point and the mark's attachment point will be placed on the

    181. 

  181.         base's attachment point so the two join properly. See my

    182. 

  182.         on the base's attachment point so the two join properly. See my

    183. 

  183.         <A HREF="overview.html#Anchors">example</A> in the overview.</TD>-->

    184. 

  184.       <TD>?????????????????????????? (????????????) ????????????????????????????????????????????????????????????????????????????????????? ????????????????????????????<A HREF="overview.html#Anchors">?</A>????????</TD>

    185. 

  185. <!--  <TD>These may be created with the

    186. 

  186.         <A HREF="pointmenu.html#AddAnchor">Points-&gt;Add Anchor</A> command</TD> -->

    187. 

  187.       <TD>???? <A HREF="pointmenu.html#AddAnchor"><CODE>?(<U>P</U>)</CODE>?<CODE>???????(<U>A</U>)...</CODE></A> ?????????????????</TD>

    188. 

  188.     </TR>

    189. 

  189.     <TR>

    190. 

  190.       <TD>5</TD>

    191. 

  191. <!--  <TD>mark to ligature</TD>-->

    192. 

  192.       <TD>????????</TD>

    193. 

  193. <!--  <TD>This sub-table is very similar to the previous one except that the base

    194. 

  194.         glyph is a ligature and may have several different points at which the same

    195. 

  195.         type of accent may be placed.</TD> -->

    196. 

  196.       <TD>?????????????????????????????????????????????????????????????????????????????????</TD>

    197. 

  197. <!--  <TD>These may be created with the

    198. 

  198.         <A HREF="pointmenu.html#AddAnchor">Points-&gt;Add Anchor</A> command</TD> -->

    199. 

  199.       <TD>???? <A HREF="pointmenu.html#AddAnchor"><CODE>?(<U>P</U>)</CODE>?<CODE>???????(<U>A</U>)...</CODE></A> ?????????????????</TD>

    200. 

  200.     </TR>

    201. 

  201.     <TR>

    202. 

  202.       <TD>6</TD>

    203. 

  203. <!--  <TD>mark to mark</TD>-->

    204. 

  204.       <TD>?????????</TD>

    205. 

  205. <!--  <TD>This sub-table is very similar to the previous two except that the base

    206. 

  206.         glyph is itself a mark. This may be used when a glyph has two accents each

    207. 

  207.         of which would normally be placed at the same attachment point on a base

    208. 

  208.         glyph. The second accent will be place relative to the first accent rather

    209. 

  209.         than to the base glyph.</TD> -->

    210. 

  210.       <TD>??????????? 2 ??????????????????????????????????????????????????? 2 ???????????????????????????????????????????????????2 ?????????????????????????????????????????????????????</TD>

    211. 

  211. <!--  <TD>These may be created with the

    212. 

  212.         <A HREF="pointmenu.html#AddAnchor">Points-&gt;Add Anchor</A> command</TD> -->

    213. 

  213.       <TD>???? <A HREF="pointmenu.html#AddAnchor"><CODE>?(<U>P</U>)</CODE>?<CODE>???????(<U>A</U>)...</CODE></A> ?????????????????</TD>

    214. 

  214.     </TR>

    215. 

  215.     <TR>

    216. 

  216.       <TD>7</TD>

    217. 

  217. <!--  <TD>contextual positioning</TD>-->

    218. 

  218.       <TD>?????????</TD>

    219. 

  219. <!--  <TD>This sub-table allows the font designer to control the positioning of

    220. 

  220.         glyphs when they occur within a specific string (or class of strings). For

    221. 

  221.         instance this table could say "when you see a digit followed by the string

    222. 

  222.         "th" then raise the "th" into a superscript position"</TD> -->

    223. 

  223.       <TD>????????????????????????????????????? (??????????) ??????????????????????????</TD>

    224. 

  224. <!--  <TD>These may be created with the

    225. 

  225.         <A HREF="fontinfo.html#Contextual">Element-&gt;Font Info-&gt;Contextual

    226. 

  226.         </A>command</TD> -->

    227. 

  227.       <TD>???? <A HREF="fontinfo.html#Contextual"><CODE>?????(<U>L</U>)</CODE>?<CODE>??????(<U>F</U>)...</CODE>?<CODE>[????]</CODE></A> ?????????????????</TD>

    228. 

  228.     </TR>

    229. 

  229.     <TR>

    230. 

  230.       <TD>8</TD>

    231. 

  231. <!--  <TD>chaining contextual positioning</TD>-->

    232. 

  232.       <TD>????????????</A>

    233. 

  233. <!--  <TD>This is a slightly more complex version of the above, it doesn't really

    234. 

  234.         add new capabilities, but it does provide a more logical approach to the

    235. 

  235.         issue.</TD> -->

    236. 

  236.       <TD>?????????????????????????????????????????????????????????????????????????????</TD>

    237. 

  237. <!--  <TD>These may be created with the

    238. 

  238.         <A HREF="fontinfo.html#Contextual">Element-&gt;Font Info-&gt;Contextual

    239. 

  239.         </A>command</TD> -->

    240. 

  240.       <TD>???? <A HREF="fontinfo.html#Contextual"><CODE>?????(<U>L</U>)</CODE>?<CODE>??????(<U>F</U>)...</CODE>?<CODE>[????]</CODE></A> ?????????????????</TD>

    241. 

  241.     </TR>

    242. 

  242.     <TR>

    243. 

  243.       <TD>9</TD>

    244. 

  244. <!--  <TD>extension positioning</TD>-->

    245. 

  245.       <TD>??????</TD>

    246. 

  246. <!--  <TD>This is used to allow for a GPOS table which is bigger than 64k. Its

    247. 

  247.         use should be quite invisible to the font designer</TD> -->

    248. 

  248.       <TD>????GPOS ????? 64K ???????????????????????????????????????????????????????????</TD>

    249. 

  249. <!--  <TD>FontForge uses this sub-table when needed.</TD>-->

    250. 

  250.       <TD>FontForge ?????????????????????????</TD>

    251. 

  251.     </TR>

    252. 

  252.     <TR>

    253. 

  253.       <TD>10+</TD>

    254. 

  254. <!--  <TD>reserved for future use</TD>-->

    255. 

  255.       <TD>???????????</TD>

    256. 

  256.       <TD></TD>

    257. 

  257. <!--  <TD>FontForge does not support these sub-tables yet.<BR>

    258. 

  258.         (nor does anyone)</TD>-->

    259. 

  259.       <TD>FontForge ? (?????????) ??????????????????????</TD>

    260. 

  260.     </TR>

    261. 

  261.   </TABLE>

    262. 

  262.   <P>

    263. 

  263. <!--

    264. 

  264.   FontForge also has built into it knowledge on how to provide default values

    265. 

  265.   for some features that use these tables. See

    266. 

  266.   <A HREF="elementmenu.html#DefaultATT">Element-&gt;Typo. Features-&gt;Default

    267. 

  267.   ATT</A> command for that. -->

    268. 

  268.   FontForge ????????????????????????????????????????????????????????????????????<A HREF="elementmenu.html#DefaultATT"><CODE>?????(<U>L</U>)</CODE>?<CODE>????(<U>Y</U>)</CODE>?<CODE>??????ATT(<U>D</U>)</CODE></A> ??????????????

    269. 

  269.   <P>

    270. 

  270. <!--

    271. 

  271.   FontForge will retain the order of features in the GPOS table and when a

    272. 

  272.   font is generated the order should be the same as it was before. -->

    273. 

  273.   FontForge ? GPOS ???????????????????????????????????????????????

    274. 

  274.   <H3>

    275. 

  275. <!--  The <B><CODE><A NAME="GSUB">GSUB</A></CODE></B> table-->

    276. 

  276.       <B><CODE><A NAME="GSUB">GSUB</A></CODE></B> ????

    277. 

  277.   </H3>

    278. 

  278.   <P>

    279. 

  279. <!--

    280. 

  280.   FontForge will read the following sub tables of the GSUB table: -->

    281. 

  281.   FontForge ??????????? GSUB ????????????:

    282. 

  282.   <TABLE Border=1>

    283. 

  283.     <TR>

    284. 

  284.       <TH></TH>

    285. 

  285.       <TH>name</TH>

    286. 

  286. <!--  <TH>Reading support</TH>-->

    287. 

  287.       <TH>????????</TH>

    288. 

  288. <!--  <TH>Writing support</TH>-->

    289. 

  289.       <TH>????????</TH>

    290. 

  290.     </TR>

    291. 

  291.     <TR>

    292. 

  292.       <TD>1</TD>

    293. 

  293. <!--  <TD>single substitution</TD>-->

    294. 

  294.       <TD>???? (????)</TD>

    295. 

  295. <!--  <TD>This sub-table allows the font designer to change from one glyph to another,

    296. 

  296.         with a context provided by the feature tag. For example many scripts have

    297. 

  297.         letters which have a different form at the end of a word than they do within

    298. 

  298.         (this is true of every letter in arabic, several in hebrew, lower case sigma

    299. 

  299.         in greek, and the long-s/short-s pair in renaissance latin). So the 'fina'

    300. 

  300.         feature would map the normal form into the final form, and the word processing

    301. 

  301.         program would do a lookup at the end of each word to see if a transformation

    302. 

  302.         was needed.</TD> -->

    303. 

  303.       <TD>??????????????????????????????????????????????????????????????????????????????????????????????????????????????? (?????????????????????????????????????????????????????????????? s/?? s ????????????)???????&lsquo;fina&rsquo;????????????????????????????????????????????????????????????????????</TD>

    304. 

  304. <!--  <TD>These can be created with the <A HREF="charinfo.html">Element-&gt;Char

    305. 

  305.         Info</A>-&gt;Substitution command.</TD> -->

    306. 

  306.       <TD>???? <A HREF="charinfo.html"><CODE>?????(<U>L</U>)</CODE>?<CODE>?????(<U>I</U>)...</CODE>?<CODE>[??]</CODE></A> ?????????????????</TD>

    307. 

  307.     </TR>

    308. 

  308.     <TR>

    309. 

  309.       <TD>2</TD>

    310. 

  310. <!--  <TD>multiple substitution</TD>-->

    311. 

  311.       <TD>????</TD>

    312. 

  312. <!--  <TD>This sub-table allows the font designer to replace one glyph by a series

    313. 

  313.         of others. This is generally used for rather technical layout issues.</TD>-->

    314. 

  314.       <TD>???????????????????????1 ?????????????????????????????????????????????????????????</TD>

    315. 

  315. <!--  <TD>These can be created with the <A HREF="charinfo.html">Element-&gt;Char

    316. 

  316.         Info</A>-&gt;Multiple Substitution command.</TD> -->

    317. 

  317.       <TD>???? <A HREF="charinfo.html"><CODE>?????(<U>L</U>)</CODE>?<CODE>?????(<U>I</U>)...</CODE>?<CODE>[????]</CODE></A> ?????????????????</TD>

    318. 

  318.     </TR>

    319. 

  319.     <TR>

    320. 

  320.       <TD>3</TD>

    321. 

  321. <!--  <TD>alternate substitution</TD>-->

    322. 

  322.       <TD>???????</TD>

    323. 

  323. <!--  <TD>This sub-table allows the font designer to have a series of "alternates"

    324. 

  324.         for each glyph. One common example would be an italic font which had several

    325. 

  325.         swash variants for each capital letter. The word processing program would

    326. 

  326.         allow the user to choose which variant was appropriate</TD> -->

    327. 

  327.       <TD>??????????????????????????“???”???????????????????????????????????????????????????????????????????????????????????????????????????????</TD>

    328. 

  328. <!--  <TD>These can be created with the <A HREF="charinfo.html">Element-&gt;Char

    329. 

  329.         Info</A>-&gt;Alternate Substitution command.</TD> -->

    330. 

  330.       <TD>???? <A HREF="charinfo.html"><CODE>?????(<U>L</U>)</CODE>?<CODE>?????(<U>I</U>)...</CODE>?<CODE>[??????]</CODE></A> ?????????????????</TD>

    331. 

  331.     </TR>

    332. 

  332.     <TR>

    333. 

  333.       <TD>4</TD>

    334. 

  334. <!--  <TD>ligature substitution</TD>-->

    335. 

  335.       <TD>????</TD>

    336. 

  336. <!--  <TD>This sub-table allows the font designer to replace a string of glyphs

    337. 

  337.         with another glyph. A common example is a ligature where the string

    338. 

  338.         <IMG SRC="f+i.png" WIDTH="24" HEIGHT="25" ALIGN="Middle"> is replaced by

    339. 

  339.         the <IMG SRC="fi.png" WIDTH="20" HEIGHT="25" ALIGN="Middle"> ligature.</TD> -->

    340. 

  340.       <TD>??????????????????????????????????? 1 ?????????????????????????????<IMG SRC="../f+i.png" WIDTH="24" HEIGHT="25" ALIGN="Middle"> ???????????? <IMG SRC="../fi.png" WIDTH="20" HEIGHT="25" ALIGN="Middle"> ?????????????????????</TD>

    341. 

  341. <!--  <TD>These can be created with the <A HREF="charinfo.html">Element-&gt;Char

    342. 

  342.         Info</A>-&gt;Ligature command.</TD> -->

    343. 

  343.       <TD>???? <A HREF="charinfo.html"><CODE>?????(<U>L</U>)</CODE>?<CODE>?????(<U>I</U>)...</CODE>?<CODE>[??]</CODE></A> ?????????????????</TD>

    344. 

  344.     </TR>

    345. 

  345.     <TR>

    346. 

  346.       <TD>5</TD>

    347. 

  347. <!--  <TD>contextual substitution</TD>-->

    348. 

  348.       <TD>???????</TD>

    349. 

  349. <!--  <TD>This subtable allows for a string of glyphs to replace another string

    350. 

  350.         of glyphs (or class of strings of glyphs)</TD> -->

    351. 

  351.       <TD>????????????????????????????? (?????????????) ?????????????

    352. 

  352. <!--  <TD>These may be created with the

    353. 

  353.         <A HREF="fontinfo.html#Contextual">Element-&gt;Font Info-&gt;Contextual

    354. 

  354.         </A>command</TD>-->

    355. 

  355.       <TD>???? <A HREF="fontinfo.html#Contextual"><CODE>?????(<U>L</U>)</CODE>?<CODE>??????(<U>F</U>)...</CODE>?<CODE>[????]</CODE></A> ?????????????????</TD>

    356. 

  356.     </TR>

    357. 

  357.     <TR>

    358. 

  358.       <TD>6</TD>

    359. 

  359. <!--  <TD>chaining contextual substitution</TD>-->

    360. 

  360.       <TD>?????????</TD>

    361. 

  361. <!--  <TD>This is a slightly more complex version of the above, it doesn't really

    362. 

  362.         add new capabilities, but it does provide a more logical approach to the

    363. 

  363.         issue.</TD> -->

    364. 

  364.       <TD>?????????????????????????????????????????????????????????????????????????????</TD>

    365. 

  365. <!--  <TD>These may be created with the

    366. 

  366.         <A HREF="fontinfo.html#Contextual">Element-&gt;Font Info-&gt;Contextual

    367. 

  367.         </A>command</TD> -->

    368. 

  368.       <TD>???? <A HREF="fontinfo.html#Contextual"><CODE>?????(<U>L</U>)</CODE>?<CODE>??????(<U>F</U>)...</CODE>?<CODE>[????]</CODE></A> ?????????????????</TD>

    369. 

  369.     </TR>

    370. 

  370.     <TR>

    371. 

  371.       <TD>7</TD>

    372. 

  372. <!--  <TD>extension positioning</TD>-->

    373. 

  373.       <TD>????</TD>

    374. 

  374. <!--  <TD>This is used to allow for a GSUB table which is bigger than 64k. Its

    375. 

  375.         use should be quite invisible to the font designer</TD> -->

    376. 

  376.       <TD>????GSUB ????? 64K ???????????????????????????????????????????????????????????</TD>

    377. 

  377. <!--  <TD>FontForge uses this sub-table when needed.</TD>-->

    378. 

  378.       <TD>FontForge ?????????????????????????</TD>

    379. 

  379.     </TR>

    380. 

  380.     <TR>

    381. 

  381.       <TD>8</TD>

    382. 

  382. <!--  <TD>reverse chaining contextual single substitution</TD>-->

    383. 

  383.       <TD>???????????????</TD>

    384. 

  384. <!--  <TD>This allows glyph substitutions to happen in reverse order, and it a

    385. 

  385.         variant of the chaining contextual subtable.</TD> -->

    386. 

  386.       <TD>????????????????????????????????????????????????</TD>

    387. 

  387. <!--  <TD>These may be created with the

    388. 

  388.         <A HREF="fontinfo.html#Contextual">Element-&gt;Font Info-&gt;Contextual

    389. 

  389.         </A>command</TD> -->

    390. 

  390.       <TD>???? <A HREF="fontinfo.html#Contextual"><CODE>?????(<U>L</U>)</CODE>?<CODE>??????(<U>F</U>)...</CODE>?<CODE>[????]</CODE></A> ?????????????????</TD>

    391. 

  391.     </TR>

    392. 

  392.     <TR>

    393. 

  393.       <TD>9+</TD>

    394. 

  394. <!--  <TD>reserved for future use</TD>-->

    395. 

  395.       <TD>???????????</TD>

    396. 

  396.       <TD></TD>

    397. 

  397. <!--  <TD>FontForge does not support these sub-tables yet.<BR>

    398. 

  398.         (nor does anyone)</TD>-->

    399. 

  399.       <TD>FontForge ? (?????????) ??????????????????????</TD>

    400. 

  400.     </TR>

    401. 

  401.   </TABLE>

    402. 

  402.   <P>

    403. 

  403. <!--

    404. 

  404.   FontForge also has built into it knowledge on how to provide default values

    405. 

  405.   for some features that use these tables. See

    406. 

  406.   <A HREF="elementmenu.html#DefaultATT">Element-&gt;Default ATT</A> command

    407. 

  407.   for that. -->

    408. 

  408.   FontForge ???????????????????????????????????????????????????????????

    409. 

  409.   <P>

    410. 

  410. <!--

    411. 

  411.   FontForge can produce some of these tables, but the text layout/word processing

    412. 

  412.   program used has to look up the tables and do the actual work of rearranging

    413. 

  413.   the glyphs. -->

    414. 

  414.   FontForge ???????????????????????????????????/???????????????????????????????????????????????????????????

    415. 

  415.   <P>

    416. 

  416. <!--

    417. 

  417.   FontForge will retain the order of features in the GSUB table, and the user

    418. 

  418.   may adjust it with the <A HREF="fontinfo.html#Order">Element-&gt;Font Info</A>

    419. 

  419.   command. -->

    420. 

  420.   FontForge ? GSUB ?????????????????????????? <A HREF="fontinfo.html#Order"><CODE>?????(<U>L</U>)</CODE>?<CODE>??????(<U>F</U>)...</CODE></A> ??????????????????

    421. 

  421.   <H3>

    422. 

  422. <!--  The <B><CODE><A NAME="GDEF">GDEF</A> </CODE></B>table-->

    423. 

  423.       <B><CODE><A NAME="GDEF">GDEF</A></CODE></B> ????

    424. 

  424.   </H3>

    425. 

  425.   <P>

    426. 

  426. <!--

    427. 

  427.   FontForge will read ligature carets out of a GDEF table. -->

    428. 

  428.   FontForge ????????? GDEF ?????????????

    429. 

  429.   <P>

    430. 

  430. <!--

    431. 

  431.   It will generate a GDEF table containing a glyph class definition sub-table

    432. 

  432.   (if needed) or a ligature caret sub-table (if needed). -->

    433. 

  433.   FontForge ???????????????? (?????) ?????????? (?????) ??? GDEF ???????????

    434. 

  434.   <H2>

    435. 

  435. <!--  <A NAME="AAT">Apple</A> Advanced Typography-->

    436. 

  436.       <A NAME="AAT">Apple</A> ?????? (ATT)

    437. 

  437.   </H2>

    438. 

  438.   <P>

    439. 

  439. <!--

    440. 

  440.   As above I do not go deeply into the abilities of these tables, for more

    441. 

  441.   information see Apple's docs: -->

    442. 

  442.   ??????????????????????????????????????????????? Apple ?????????????

    443. 

  443.   <UL>

    444. 

  444.     <LI>

    445. 

  445. <!--  <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6kern.html">The

    446. 

  446.       'kern' table</A> -->

    447. 

  447.       <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6kern.html">&lsquo;kern&rsquo;????</A>

    448. 

  448.     <LI>

    449. 

  449. <!--  <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6lcar.html">The

    450. 

  450.       'lcar' (ligature caret) table</A> -->

    451. 

  451.       <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6lcar.html">&lsquo;lcar&rsquo; (???????) ????</A>

    452. 

  452.     <LI>

    453. 

  453. <!--  <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6morx.html">The

    454. 

  454.       'morx' (extended glyph metamorphosis) table</A>-->

    455. 

  455.       <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6morx.html">&lsquo;morx&rsquo; (???????) ????</A>

    456. 

  456.       <UL>

    457. 

  457.         <LI>

    458. 

  458. <!--	  <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6mort.html">The

    459. 

  459. 	  'mort' (older version of 'morx') table</A>-->

    460. 

  460. 	  <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6mort.html">&lsquo;mort&rsquo; (&lsquo;morx&rsquo; ???) ????</A>

    461. 

  461.         <LI>

    462. 

  462. <!--	  <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6feat.html">The

    463. 

  463. 	  'feat' (feature) table</A> -->

    464. 

  464. 	  <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6feat.html">&lsquo;feat&rsquo; (??) ????</A>

    465. 

  465.         <LI>

    466. 

  466. <!--	  <A HREF="http://developer.apple.com/fonts/Registry/index.html">Apple's Font

    467. 

  467. 	  Feature registry</A> -->

    468. 

  468. 	  <A HREF="http://developer.apple.com/fonts/Registry/index.html">Apple ??????????</A>

    469. 

  469.         <LI>

    470. 

  470. <!--	  <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6Tables.html">Description

    471. 

  471. 	  of the subtables of the 'mort'/'morx' tables</A> -->

    472. 

  472. 	  <A HREF="http://developer.apple.com/fonts/Registry/index.html">&lsquo;mort&rsquo;/&lsquo;morx&rsquo;??????????????</A>

    473. 

  473.       </UL>

    474. 

  474.     <LI>

    475. 

  475. <!--  <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6opbd.html">The

    476. 

  476.       &lsquo;opbd&rsquo;(optical bounds) table</A> -->

    477. 

  477.       <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6opbd.html">&lsquo;opbd&rsquo; (??????) ????</A>

    478. 

  478.     <LI>

    479. 

  479. <!--  <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6prop.html">The

    480. 

  480.       'prop' (glyph properties) table</A> -->

    481. 

  481.       <A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6prop.html">&lsquo;prop&rsquo; (?????) ????</A>

    482. 

  482.   </UL>

    483. 

  483.   <P>

    484. 

  484. <!--

    485. 

  485.   FontForge will current read and produce (if Apple mode is set in font generation)

    486. 

  486.   the following tables: -->

    487. 

  487.   ???FontForge ?????????????? (Apple ????????????????????) ????:

    488. 

  488.   <TABLE BORDER CELLPADDING="2">

    489. 

  489.     <CAPTION>

    490. 

  490. <!--  Apple tables corresponding vaguely to <A HREF="#GDEF">GDEF</A>-->

    491. 

  491.       <A HREF="#GDEF">GDEF</A> ??????? OpenType ?????

    492. 

  492.     </CAPTION>

    493. 

  493.     <TR>

    494. 

  494.       <TH>tag</TH>

    495. 

  495.       <TH>name</TH>

    496. 

  496. <!--  <TH>Reading support</TH>-->

    497. 

  497.       <TH>????????</TH>

    498. 

  498. <!--  <TH>Writing support</TH>-->

    499. 

  499.       <TH>????????</TH>

    500. 

  500.     </TR>

    501. 

  501.     <TR>

    502. 

  502.       <TD><CODE>'lcar'</CODE></TD>

    503. 

  503. <!--  <TD>ligature caret table</TD>-->

    504. 

  504.       <TD>???????????</TD>

    505. 

  505. <!--  <TD>FontForge will read ligature carets</TD>-->

    506. 

  506.       <TD>FontForge ???????????????</TD>

    507. 

  507. <!--  <TD>FontForge will produce this table if the user has specified ligature

    508. 

  508.         carets</TD> -->

    509. 

  509.       <TD>FontForge ??????????????????????????????????</TD>

    510. 

  510.     </TR>

    511. 

  511.     <TR>

    512. 

  512.       <TD><CODE>'prop'</CODE></TD>

    513. 

  513. <!--  <TD>glyph properties table</TD>-->

    514. 

  514.       <TD>?????????</TD>

    515. 

  515. <!--  <TD>FontForge will read this table to figure out which glyphs are hebrew

    516. 

  516.         and arabic, and which have 'r2la' substitutions.</TD> -->

    517. 

  517.       <TD>FontForge ????????????????????&lsquo;r2la&rsquo;??????????????????????????????????????</TD>

    518. 

  518. <!--  <TD>FontForge will generate this table if the font contains some right to

    519. 

  519.         left glyphs.</TD> -->

    520. 

  520.       <TD>FontForge ????????????????????????????????????????????</TD>

    521. 

  521.     </TR>

    522. 

  522.   </TABLE>

    523. 

  523.   <P>

    524. 

  524.   <TABLE BORDER CELLPADDING="2">

    525. 

  525.     <CAPTION>

    526. 

  526. <!--  Apple tables corresponding vaguely to <A HREF="#GPOS">GPOS</A>-->

    527. 

  527.       <A HREF="#GPOS">GPOS</A> ??????? OpenType ?????

    528. 

  528.     </CAPTION>

    529. 

  529.     <TR>

    530. 

  530.       <TH>tag</TH>

    531. 

  531.       <TH>name</TH>

    532. 

  532. <!--  <TH>Reading support</TH>-->

    533. 

  533.       <TH>????????</TH>

    534. 

  534. <!--  <TH>Writing support</TH>-->

    535. 

  535.       <TH>????????</TH>

    536. 

  536.     </TR>

    537. 

  537.     <TR>

    538. 

  538.       <TD><CODE>'kern'</CODE></TD>

    539. 

  539. <!--  <TD>kerning table</TD>-->

    540. 

  540.       <TD>?????????</TD>

    541. 

  541. <!--  <TD>FontForge will read horizontal/vertical kerning pairs and classes. FontForge

    542. 

  542.         can read contextual kerning information too into a state machine.</TD> -->

    543. 

  543.       <TD>FontForge ????/???????????????????????????FontForge ???????????????????????????????</TD>

    544. 

  544. <!--  <TD>FontForge will produce this if the font contains kerning data - - kerning

    545. 

  545.         pairs, kerning by classes, and kerning by state machine.</TD> -->

    546. 

  546.       <TD>FontForge ??????????????????????????????????????????????????????????????????????</TD>

    547. 

  547.     </TR>

    548. 

  548.     <TR>

    549. 

  549.       <TD><CODE>'opbd'</CODE></TD>

    550. 

  550. <!--  <TD>Optical bounds table</TD>-->

    551. 

  551.       <TD>?????????</TD>

    552. 

  552. <!--  <TD>FontForge will read optical bounds</TD>-->

    553. 

  553.       <TD>FontForge ?????????????</TD>

    554. 

  554. <!--  <TD>FontForge will produce this table if the user has specified right and

    555. 

  555.         left bounds as simple positions ('lfbd' and 'rtbd').</TD> -->

    556. 

  556.       <TD>FontForge ???????????????????????? (&lsquo;lfbd&rsquo;?&lsquo;rtbd&rsquo;) ??????????????????????</TD>

    557. 

  557.     </TR>

    558. 

  558.   </TABLE>

    559. 

  559.   <P>

    560. 

  560.   <P>

    561. 

  561. <!--

    562. 

  562.   FontForge has support for the <CODE>'mort'</CODE> and

    563. 

  563.   <CODE>'<A NAME="morx">morx</A>'</CODE> tables (Glyph metamorphosis and extended

    564. 

  564.   glyph metamorphosis tables). These correspond vaguely to the

    565. 

  565.   <A HREF="#GSUB">GSUB</A> table. Note: Any feature type/setting combinations

    566. 

  566.   which correspond directly to an open type feature will be converted to the

    567. 

  567.   opentype tag when read in. It will be converted back to a feature/setting

    568. 

  568.   when an apple font is generated (use

    569. 

  569.   <A HREF="prefs.html#Mac">File-&gt;Preferences</A> to extend FontForge's mapping

    570. 

  570.   from feature type/setting to opentype tags). -->

    571. 

  571.   FontFonge ?? <CODE>&lsquo;mort&rsquo;</CODE>  (?????) ????? <CODE>&lsquo;<A NAME="morx">morx</A>&rsquo;</CODE> (???????) ?????????????????????????? <A HREF="#GSUB">GSUB</A> ???????????????: OpenType ??????????????????????/?????????????? OpenType ???????????????/??????????????Apple ?????????????? (FontForge ???/???? OpenType ???????????????<A HREF="prefs.html#Mac"><CODE>????(<U>F</U>)</CODE>?<CODE>????(<U>E</U>)...</CODE></A> ?????????)?

    572. 

  572.   <TABLE BORDER CELLPADDING="2">

    573. 

  573.     <CAPTION>

    574. 

  574. <!--  Sub tables of <CODE>'mort'</CODE> or <CODE>'morx'</CODE>-->

    575. 

  575.       <CODE>&lsquo;mort&rsquo;</CODE> ??? <CODE>&lsquo;morx&rsquo;</CODE> ???????????

    576. 

  576.     </CAPTION>

    577. 

  577.     <TR>

    578. 

  578.       <TH></TH>

    579. 

  579. <!--  <TH>name</TH>-->

    580. 

  580.       <TH>??</TH>

    581. 

  581. <!--  <TH>Reading support</TH>-->

    582. 

  582.       <TH>????????</TH>

    583. 

  583. <!--  <TH>Writing support</TH>-->

    584. 

  584.       <TH>????????</TH>

    585. 

  585.     </TR>

    586. 

  586.     <TR>

    587. 

  587.       <TD>0</TD>

    588. 

  588. <!--  <TD>Indic style rearrangement</TD>-->

    589. 

  589.       <TD>???????????</TD>

    590. 

  590. <!--  <TD>FontForge can read these and stores them as state machines (which can

    591. 

  591.         be edited with <A HREF="fontinfo.html#Mac-SM">Font Info</A>)</TD> -->

    592. 

  592.       <TD>FontForge ???????????????????????????? (???? <A HREF="fontinfo.html#Mac-SM">??????</A> ????????????)?</TD>

    593. 

  593. <!--  <TD>Any indic state machines will be output in the generated font.</TD>-->

    594. 

  594.       <TD>??????????????????????????????????</TD>

    595. 

  595.     </TR>

    596. 

  596.     <TR>

    597. 

  597.       <TD>1</TD>

    598. 

  598. <!--  <TD>contextual glyph substitution</TD>-->

    599. 

  599.       <TD>??????????</TD>

    600. 

  600. <!--  <TD>FontForge can read these and stores them as state machines (which can

    601. 

  601.         be edited with <A HREF="fontinfo.html#Mac-SM">Font Info</A>)</TD> -->

    602. 

  602.       <TD>FontForge ???????????????????????????? (???? <A HREF="fontinfo.html#Mac-SM">??????</A> ????????????)?</TD>

    603. 

  603. <!--  <TD>If the font contains any state machines they will be output here. If

    604. 

  604.         there are no state machines then the following conversions of opentype features

    605. 

  605.         will be done: -->

    606. 

  606.       <TD>?????????????????????????????????????????????????????????????? OpenType ?????????:

    607. 

  607.         <UL>

    608. 

  608. 	  <LI>

    609. 

  609. <!--	    FontForge will generate a <A NAME="cursive-connection">cursive connection

    610. 

  610. 	    </A>feature using this subtable type if the font contains 'init', 'medi',

    611. 

  611. 	    'fina' or 'isol' simple substitutions. -->

    612. 

  612. 	    FontForge ???????&lsquo;init&rsquo;,&lsquo;medi&rsquo;,&lsquo;fina&rsquo;???&lsquo;isol&rsquo;????????????????????????????<A NAME="cursive-connection">??????</A>??????????

    613. 

  613. 	  <LI>

    614. 

  614. <!--	    In <A HREF="gposgsub.html#sometimes">some cases</A> FontForge is able to

    615. 

  615. 	    convert an OpenType Contextual/Chaining substitution table into an Apple

    616. 

  616. 	    contextual glyph substitution table. -->

    617. 

  617. 	    <A HREF="gposgsub.html#sometimes">??????????????</A>???FontForge ? OpenType ?????????/???????????? Apple ???????????????????????????

    618. 

  618.         </UL>

    619. 

  619.       </TD>

    620. 

  620.     </TR>

    621. 

  621.     <TR>

    622. 

  622.       <TD>2</TD>

    623. 

  623. <!--  <TD>ligature substitution</TD>-->

    624. 

  624.       <TD>????</TD>

    625. 

  625. <!--  <TD>FontForge can read the unconditional information from these and stores

    626. 

  626.         them as opentype ligatures (which can be edited with

    627. 

  627.         <A HREF="charinfo.html#features">Char Info</A>).</TD> -->

    628. 

  628.       <TD>FontForge ???????????????OpenType ????????????????? (???? <A HREF="charinfo.html#features">?????</A> ????????????)?</TD>

    629. 

  629. <!--  <TD>If there are any ligatures with an apple feature/setting (or which have

    630. 

  630.         an opentype tag which can be converted to an apple feature/setting) then

    631. 

  631.         this table will be output.</TD>-->

    632. 

  632.       <TD>??????????????????? (??? Apple ???/???????? OpenType ????????) ??????????????</TD>

    633. 

  633.     </TR>

    634. 

  634.     <TR>

    635. 

  635.       <TD>4</TD>

    636. 

  636. <!--  <TD>non-contextual glyph substitution</TD>-->

    637. 

  637.       <TD>???????????</TD>

    638. 

  638. <!--  <TD>FontForge can read these and stores them as opentype simple substitutions

    639. 

  639.         (which can be edited with <A HREF="charinfo.html#features">Char Info</A>)</TD> -->

    640. 

  640.       <TD>FontForge ??????????OpenType ??????????????????? (???? <A HREF="charinfo.html#features">?????</A> ????????????)?</TD>

    641. 

  641. <!--  <TD>If there are any substitutions with an apple feature/setting (or which

    642. 

  642.         have an opentype tag which can be converted to an apple feature/setting)

    643. 

  643.         then this table will be output.</TD> -->

    644. 

  644.       <TD>??????????????????? (??? Apple ???/???????? OpenType ????????) ??????????????</TD>  </TR>

    645. 

  645.     <TR>

    646. 

  646.       <TD>5</TD>

    647. 

  647. <!--  <TD>contextual glyph insertion</TD>-->

    648. 

  648.       <TD>??????????</TD>

    649. 

  649. <!--  <TD>FontForge can read these and stores them as state machines (which can

    650. 

  650.         be edited with <A HREF="fontinfo.html#Mac-SM">Font Info</A>)</TD> -->

    651. 

  651.       <TD>FontForge ???????????????????????????? (???? <A HREF="fontinfo.html#Mac-SM">??????</A> ????????????)?</TD>

    652. 

  652. <!--  <TD>Any glyph insertion state machines will be output in the generated font.</TD>-->

    653. 

  653.       <TD>????????????????????????????????</TD>

    654. 

  654.     </TR>

    655. 

  655.   </TABLE>

    656. 

  656.   <H3>

    657. 

  657. <!--  What features can be <A NAME="Conversion">interconverted</A> between OpenType

    658. 

  658.       and AAT? -->

    659. 

  659.       OpenType ? AAT ??????????<A NAME="Conversion">????</A>????

    660. 

  660.   </H3>

    661. 

  661.   <P>

    662. 

  662. <!--

    663. 

  663.   Some features have almost the same meaning in OpenType and AAT (although

    664. 

  664.   they are expressed quite differently), others are similar enough that they

    665. 

  665.   can sometimes be converted, and others have essentially no common ground. -->

    666. 

  666.   ???????? OpenType ? AAT ??????????????? (???????????????????)?????????????????????????????????????????????????????

    667. 

  667.   <P>

    668. 

  668.   <TABLE BORDER CELLPADDING="2">

    669. 

  669.     <TR>

    670. 

  670. <!--  <TH>OT Table</TH>-->

    671. 

  671.       <TH>OpenType ????</TH>

    672. 

  672. <!--  <TH>AAT Table</TH>-->

    673. 

  673.       <TH>AAT ????</TH>

    674. 

  674.       <TH><P ALIGN=Left>

    675. 

  675. <!--    Description</TH>-->

    676. 

  676.         ??</TH>

    677. 

  677.     </TR>

    678. 

  678.     <TR>

    679. 

  679.       <TD VALIGN="Top"><P ALIGN=Center>

    680. 

  680.         GDEF</TD>

    681. 

  681.       <TD VALIGN="Top"><P ALIGN=Center>

    682. 

  682.         lcar</TD>

    683. 

  683. <!--  <TD>The ligature caret information in both 'GDEF' and 'lcar' is essentially

    684. 

  684.         identical and FontForge has no trouble reading both and converting from one

    685. 

  685.         to the other.</TD> -->

    686. 

  686.       <TD>??????????&lsquo;GDEF&rsquo;?&lsquo;lcar&rsquo;?????????FontForge ?????????????????????????

    687. 

  687.     </TR>

    688. 

  688.     <TR>

    689. 

  689.       <TD><P ALIGN=Center>

    690. 

  690.         GPOS</TD>

    691. 

  691.       <TD><P ALIGN=Center>

    692. 

  692.         kern</TD>

    693. 

  693. <!--  <TD>In most cases kerning information can be converted from one format to

    694. 

  694.         another. Both provide support for vertical kerning and right to left kerning.

    695. 

  695.         Both provide support for kerning by glyph pair and kerning by classes.-->

    696. 

  696.       <TD>??????????????????????????????????????????????????????????????????????????

    697. 

  697.         <P>

    698. 

  698. <!--    OpenType allows kerning commands to be supplied via a contextual chaining

    699. 

  699.         feature, Apple allows them to be controled by a state machine. FontForge

    700. 

  700.         supports both, but does not interconvert.</TD> -->

    701. 

  701.         OpenType ?????????????????????????????Apple ??????????????????????FontForge ?????????????????????????</TD>

    702. 

  702.     </TR>

    703. 

  703.     <TR>

    704. 

  704.       <TD><P ALIGN=Center>

    705. 

  705.         GPOS</TD>

    706. 

  706.       <TD><P ALIGN=Center>

    707. 

  707.         opbd</TD>

    708. 

  708. <!--  <TD>The GPOS features 'lfbd' and 'rtbd' provide the information needed to

    709. 

  709.         generate an Apple opbd table. If FontForge reads a font with an opbd table

    710. 

  710.         it will generate appropriate 'lfbd' and 'rtbd' features. If FontForge generates

    711. 

  711.         a font in apple mode that has these features it will create an opbd table.

    712. 

  712.         Similarly when FontForge reads an opbd table it will create 'lfbd' and 'rtbd'

    713. 

  713.         features.</TD> -->

    714. 

  714.       <TD>GPOS ??&lsquo;lfbd&rsquo;???&lsquo;rfbd&rsquo;? Apple ? opbd ???????????????????????????FontForge ? opbd ?????????????????????????&lsquo;lfbd&rsquo;???&lsquo;rtbd&rsquo;?????????FotnForge ? Apple ??????????????????????????????&lsquo;opbd&rsquo;???????????????FontForge ? opbd ????????????&lsquo;lfbd&rsquo;?&lsquo;rtbd&rsquo;?????????</TD>

    715. 

  715.     </TR>

    716. 

  716.     <TR>

    717. 

  717.       <TD><P ALIGN=Center>

    718. 

  718.         GPOS</TD>

    719. 

  719.       <TD>

    720. 

  720. 	  <HR>

    721. 

  721.       </TD>

    722. 

  722. <!--  <TD>I am not aware of any way to convert other GPOS features to AAT.</TD> -->

    723. 

  723.       <TD>?????? GPOS ??? AAT ??????????????????</TD>

    724. 

  724.     </TR>

    725. 

  725.     <TR>

    726. 

  726.       <TD><P ALIGN=Center>

    727. 

  727.         GSUB</TD>

    728. 

  728.       <TD><P ALIGN=Center>

    729. 

  729.         morx</TD>

    730. 

  730. <!--  <TD ROWSPAN=2>The 'mort' and 'morx' tables have the same capabilities ('mort'

    731. 

  731.         tables are an old format and Apple currently encourages that 'morx' tables

    732. 

  732.         be used instead). FontForge can read either one, but only generates 'morx'

    733. 

  733.         tables. Interconversion depends on specific feature types and the sub-table

    734. 

  734.         formats, see below</TD>-->

    735. 

  735.       <TD ROWSPAN=2>&lsquo;mort&rsquo;???&lsquo;morx&rsquo;???????????????? (&lsquo;mort&rsquo;???????????????Apple ??????????&lsquo;morx&rsquo;??????????????)?FontForge ??????????????????&lsquo;morx&rsquo;?????????????????????????????????????????????????????????????:

    736. 

  736.     </TR>

    737. 

  737.     <TR>

    738. 

  738.       <TD><P ALIGN=Center>

    739. 

  739.         GSUB</TD>

    740. 

  740.       <TD><P ALIGN=Center>

    741. 

  741.         mort</TD>

    742. 

  742.     </TR>

    743. 

  743.   </TABLE>

    744. 

  744.   <H4>

    745. 

  745. <!--  An analysis of GSUB and morx sub-tables and feature tags-->

    746. 

  746.       GSUB ??? morx ??????????????

    747. 

  747.   </H4>

    748. 

  748.   <P>

    749. 

  749. <!--

    750. 

  750.   OpenType uses a four character feature tag (like 'liga') while Apple uses

    751. 

  751.   two numbers to represent a feature setting (&lt;1,2&gt;). For FontForge to

    752. 

  752.   be able to inter-convert an OpenType feature into an Apple feature there

    753. 

  753.   must first be a correspondence between the two naming conventions. Sometimes

    754. 

  754.   there is an easy direct conversion (above 'liga' and &lt;1,2&gt; both represent

    755. 

  755.   "Common Ligatures") but far more often there is none. See

    756. 

  756.   <A HREF="gposgsub.html#OT-Mac-features">below</A> for a list of the tags

    757. 

  757.   and feature settings that FontForge considers similar enough to interconvert. -->

    758. 

  758.   OpenType ? 4 ??????? (&lsquo;liga&rsquo;??) ????????????Apple ???????? 2 ???? (&lt;1,2&gt; ??) ???????FontForge ??????OpenType ???? Apple ??????????????????????? 2 ??????????????????????????????????????????????????? (????&lsquo;liga&rsquo;? &lt;1,2&gt; ?????“??????”?????)?FontForge ??????????????????????????????????????<A HREF="gposgsub.html#OT-Mac-features">??</A>??????????

    759. 

  759.   <P>

    760. 

  760. <!--

    761. 

  761.   GSUB tables have 7 sub-table formats, while morx tables have 5. -->

    762. 

  762.   GSUB ?????? 7 ???????????????????????morx ?????? 5 ????????

    763. 

  763.   <TABLE BORDER CELLPADDING="2">

    764. 

  764.     <TR>

    765. 

  765. <!--  <TH>GSUB<BR>

    766. 

  766.         sub-<BR>

    767. 

  767.         table</TH>-->

    768. 

  768.       <TH>GSUB<BR>??<BR>????</TH>

    769. 

  769. <!--  <TH>morx<BR>

    770. 

  770.         sub-<BR>

    771. 

  771.         table</TH>-->

    772. 

  772.       <TH>morx<BR>??<BR>????</TH>

    773. 

  773.       <TH><P ALIGN=Left>

    774. 

  774. <!--    Description</TH>-->

    775. 

  775.         ??</TH>

    776. 

  776.     </TR>

    777. 

  777.     <TR>

    778. 

  778.       <TD VALIGN="Top"><P ALIGN=Center>

    779. 

  779. <!--    Single</TD> -->

    780. 

  780.         ??</TD>

    781. 

  781.       <TD VALIGN="Top"><P ALIGN=Center>

    782. 

  782. <!--    Non-<BR>

    783. 

  783.         Contextual<BR>

    784. 

  784.         Glyph</TD> -->

    785. 

  785.         ??<BR>???<BR>???</TD>

    786. 

  786. <!--  <TD>These two sub-tables have almost exactly the same capabilities. Each

    787. 

  787.         allows one glyph to be substituted for another. The morx sub-table also allows

    788. 

  788.         a glyph to be deleted, while the GSUB sub-table does not.</TD> -->

    789. 

  789.       <TD>???? 2 ????????????????????????????????? 1 ???????? 1 ????????????????morx ?????????????????????????GSUB ???????????????????</TD>

    790. 

  790.     </TR>

    791. 

  791.     <TR>

    792. 

  792.       <TD VALIGN="Top"><P ALIGN=Center>

    793. 

  793. <!--    Multiple</TD>-->

    794. 

  794.         ??</TD>

    795. 

  795.       <TD></TD>

    796. 

  796. <!--  <TD>This GSUB subtable allows a single glyph to be replaced by multiple glyphs.

    797. 

  797.         It has some similarities to Apple's Glyph Insertion sub-table except:-->

    798. 

  798.       <TD>?? GSUB ????????1 ????????????????????????????????????????Apple ??????????????????????????:

    799. 

  799.         <UL>

    800. 

  800. 	  <LI>

    801. 

  801. <!--	    the 'morx' sub-table always leaves the current glyph in the glyph stream,

    802. 

  802. 	    while this sub-table need not -->

    803. 

  803. 	   &lsquo;morx&rsquo;??????????????????????????????????????????????????????

    804. 

  804. 	  <LI>

    805. 

  805. <!--	    the 'morx' sub-table is contextual while this sub-table is never. (But if

    806. 

  806. 	    this sub-table is wrapped inside a Context or Chaining Context subtable the

    807. 

  807. 	    result can be contextual). -->

    808. 

  808. 	   &lsquo;morx&rsquo;????????????????????????????????????? (??????????????????????????????????????????????????????????????)?

    809. 

  809.         </UL>

    810. 

  810.       </TD>

    811. 

  811.     </TR>

    812. 

  812.     <TR>

    813. 

  813.       <TD></TD>

    814. 

  814.       <TD VALIGN="Top"><P ALIGN=Center>

    815. 

  815. <!--    Glyph<BR>

    816. 

  816.         Insertion</TD> -->

    817. 

  817.         ???<BR>??</TD>

    818. 

  818. <!--  <TD>This morx subtable allows a string of glyphs to be inserted before or

    819. 

  819.         after the current glyph (the current glyph always remains). This sub-table

    820. 

  820.         is contextual (ie. the insertion can be restricted to certain contexts).

    821. 

  821.         It bears some similarities to the GSUB Multiple subtable above.</TD> -->

    822. 

  822.       <TD>?? morx ?????????????????????????????????????? (?????????????????)???????????????? (??????????????????????????????)?????? GPOS ???????????????????????</TD>

    823. 

  823.     </TR>

    824. 

  824.     <TR>

    825. 

  825. <!--  <TD VALIGN="Top">Alternate</TD> -->

    826. 

  826.       <TD VALIGN="Top">???</TD>

    827. 

  827.       <TD></TD>

    828. 

  828. <!--  <TD>This GSUB subtable allows a single glyph to be replaced by any one of

    829. 

  829.         several alternatives (presumably with help from a word processor's UI). An

    830. 

  830.         example of this would be a character which had several swash variants. There

    831. 

  831.         is nothing like this in the 'morx' table.</TD>-->

    832. 

  832.       <TD>?? GSUB ???????????1 ???????????????? (???????????????? UI ???????) ??? 1 ?????????????????????????????????????????&lsquo;morx&rsquo;???????????????????????</TD>

    833. 

  833.     </TR>

    834. 

  834.     <TR>

    835. 

  835.       <TD VALIGN="Top"><P ALIGN=Center>

    836. 

  836. <!--    Ligature</TD> -->

    837. 

  837.         ??</TD>

    838. 

  838.       <TD VALIGN="Top"><P ALIGN=Center>

    839. 

  839. <!--    Ligature</TD> -->

    840. 

  840.         ??</TD>

    841. 

  841. <!--  <TD>Both formats have ligature sub-tables. The 'GSUB' version is unconditional

    842. 

  842.         (the ligature is always applied -- though a ligature substitution could be

    843. 

  843.         embedded in an OpenType contextual substitution to make it condtional). The

    844. 

  844.         'morx' version can be contextual (though in fonts I have examined it is usually

    845. 

  845.         uncontextual). FontForge only supports unconditional ligatures. -->

    846. 

  846.       <TD>???????????????????????????&lsquo;GSUB&rsquo;?????????????? (?????????????????? OpenType ???????????????????????????????)?&lsquo;morx&rsquo;???????????????????? (??????????????????????????)?FontForge ??????????????????????

    847. 

  847.         <P>

    848. 

  848. <!--    FontForge can read all the unconditional ligatures from a 'morx' sub-table.

    849. 

  849.         FontForge loses all contextual ligatures. -->

    850. 

  850.         FontForge ??????????????&lsquo;morx&rsquo;????????????????????FontForge ?????????????????????

    851. 

  851.         <P>

    852. 

  852. <!--    In OpenType, contextual ligatures can be built by wrapping a ligature sub-table

    853. 

  853.         inside a Context or Chaining Context subtable.</TD> -->

    854. 

  854.         OpenType ???????????????????????????????????????????????????????????</TD>

    855. 

  855.     </TR>

    856. 

  856.     <TR>

    857. 

  857.       <TD></TD>

    858. 

  858.       <TD VALIGN="Top"><P ALIGN=Center>

    859. 

  859. <!--    Contextual<BR>

    860. 

  860.         Glyph</TD> -->

    861. 

  861.         ?????<BR>???</TD>

    862. 

  862. <!--  <TD>This morx subtable allows single glyph substitutions to be applied within

    863. 

  863.         certain contexts. At first glance it seems that this could be converted into

    864. 

  864.         an opentype Context subtable, <A HREF="gposgsub.html#sometimes">but this

    865. 

  865.         is rarely the case</A>.</TD>-->

    866. 

  866.       <TD>?? morx ??????????????????????????????????????????????? OpenType ???????????????????????????????<A HREF="gposgsub.html#sometimes">???????????????????????</TD>

    867. 

  867.     </TR>

    868. 

  868.     <TR>

    869. 

  869.       <TD><P ALIGN=Center>

    870. 

  870. <!--    Context</TD> -->

    871. 

  871.         ????</TD>

    872. 

  872.       <TD></TD>

    873. 

  873. <!--  <TD ROWSPAN="2" VALIGN="Top">These GSUB subtables allow any collection of

    874. 

  874.         other substitutions to be applied contextually. At first glance one might

    875. 

  875.         think that these (with appropriate nested substitutions) might be converted

    876. 

  876.         to 'morx' contextual glyph substitutions, contextual ligatures, or even glyph

    877. 

  877.         insertion. <A HREF="gposgsub.html#sometimes">Unfortunately this is rarely

    878. 

  878.         the case</A>.</TD> -->

    879. 

  879.       <TD ROWSPAN="2" VALIGN="Top">???? GSUB ??????????????????????????????????????????? (??????????????) ??????????&lsquo;morx&rsquo;???????????????????????????????????????????????????<A HREF="gposgsub.html#sometimes">???????????????????????</A>

    880. 

  880.     </TR>

    881. 

  881.     <TR>

    882. 

  882.       <TD><P ALIGN=Center>

    883. 

  883. <!--    Chaining<BR>

    884. 

  884.         Context</TD> -->

    885. 

  885.         ???<BR>????</TD>

    886. 

  886.       <TD></TD>

    887. 

  887.     </TR>

    888. 

  888.     <TR VALIGN="Top">

    889. 

  889.       <TD><P ALIGN=Center>

    890. 

  890. <!--    Reverse<BR>

    891. 

  891.         Chaining<BR>

    892. 

  892.         Context</TD> -->

    893. 

  893.         ???<BR>???<BR>????</TD>

    894. 

  894.       <TD></TD>

    895. 

  895. <!--  <TD>This GSUB subtable is applied backwards to the stream of glyphs, it allows

    896. 

  896.         a single glyph substitution per contextual match. There is nothing like it

    897. 

  897.         in 'morx'.</TD> -->

    898. 

  898.       <TD>?? GSUB ????????????????????????????????????????????????????? 1 ???????????&lsquo;morx&rsquo;?????????????????</TD>

    899. 

  899.     </TR>

    900. 

  900.     <TR VALIGN="Top">

    901. 

  901.       <TD></TD>

    902. 

  902.       <TD><P ALIGN=Center>

    903. 

  903. <!--    Indic<BR>

    904. 

  904.         Rearrange-<BR>

    905. 

  905.         ment</TD> -->

    906. 

  906.         ????<BR>???<BR>???</TD>

    907. 

  907. <!--  <TD>This&lsquo;morx&rsquo;subtable allows for several glyphs to interchange their positions

    908. 

  908.         in the glyph stream. There is nothing like it in GSUB (or GPOS for that matter).</TD>-->

    909. 

  909.       <TD>??&lsquo;morx&rsquo;??????????????????????????????????????????????? GSUB ?? (??? GPOS ??) ???????????????</TD>

    910. 

  910.     </TR>

    911. 

  911.   </TABLE>

    912. 

  912.   <H4>

    913. 

  913. <!--  Why do contextual glyph substitutions only <A NAME="sometimes">sometimes</A>

    914. 

  914.       get generated in AAT? -->

    915. 

  915.       ?????????????<A NAME="sometimes">???</A>?? AAT ??????????

    916. 

  916.   </H4>

    917. 

  917.   <P>

    918. 

  918. <!--

    919. 

  919.   Sadly OpenType and AAT provide disjoint capabilities when it comes to contextual

    920. 

  920.   matching. AAT is more capable in some areas, OpenType more capable in others.

    921. 

  921.   FontForge is able to convert an OpenType contextual substitution into an

    922. 

  922.   AAT one if FontForge can detect that the OpenType substitution does not use

    923. 

  923.   capabilities beyond those of AAT. Currently this means: -->

    924. 

  924.   ?????????OpenType ? AAT ?????????????????????????????????????????? AAT ???????????????? OpenType ???????????FontForge ? OpenType ???????? AAT ??????????????????? OpenType ??? AAT ???????????????????? FontForge ??????????????????????????????????????????????:

    925. 

  925.   <UL>

    926. 

  926.     <LI>

    927. 

  927. <!--  There is an apple feature which matches the otf tag-->

    928. 

  928.       ?? OTF ??????? Apple ????????

    929. 

  929.     <LI>

    930. 

  930. <!--  And one of the following is true:-->

    931. 

  931.       ???????????? 1 ?????:

    932. 

  932.       <OL>

    933. 

  933.         <LI>

    934. 

  934. <!--	  Either -->

    935. 

  935. 	  ??????????????????:

    936. 

  936. 	  <UL>

    937. 

  937. 	    <LI>

    938. 

  938. <!--	      The sub-table is in coverage format -->

    939. 

  939. 	      ????????????????????????????

    940. 

  940. 	    <LI>

    941. 

  941. <!--	      The sub-table contains either exactly one nested single glyph replacement

    942. 

  942. 	      substitution, or<BR> -->

    943. 

  943. 	      ????????????? 1 ??????????????????????????<BR>

    944. 

  944. <!--	      it contains exactly two single glyph replacements and one of them refers

    945. 

  945. 	      to the last glyph matched (and the other does not) -->

    946. 

  946. 	      ???? 2 ??????????????????????? 1 ???????????????????? (?????? 1 ????????????)

    947. 

  947. 	  </UL>

    948. 

  948.         <LI>

    949. 

  949. <!--	  or -->

    950. 

  950. 	  ?????????

    951. 

  951. 	  <UL>

    952. 

  952. 	    <LI>

    953. 

  953. <!--	      The sub-table is in either glyph or class format -->

    954. 

  954. 	      ????????????????????????????????????

    955. 

  955. 	    <LI>

    956. 

  956. <!--	      If in class format then either the backtrack and lookahead classes must be

    957. 

  957. 	      the same as the main class, or they must not be used. -->

    958. 

  958. 	      ????????????????????????????????????????????????????????????????????????

    959. 

  959. 	    <LI>

    960. 

  960. <!--	      If a rule has a substitution at a given glyph position, then all rules which

    961. 

  961. 	      match the current rule up to that glyph position must also have a substitution

    962. 

  962. 	      at that position. -->

    963. 

  963. 	      ????????????????????????????????????????????????????????????????????????????????????

    964. 

  964. 	    <LI>

    965. 

  965. <!--	      A rule with exactly one substitution is acceptable<BR>

    966. 

  966. 	      A rule with one substitution in the middle and one substitution on the last

    967. 

  967. 	      glyph is acceptable.<BR>

    968. 

  968. 	      A rule may contain more substitutions only if there is another rule which

    969. 

  969. 	      matches it exactly up to the internal substitution.<BR>

    970. 

  970. 	      So the following rule set is valid: -->

    971. 

  971. 	      ???? 1 ??????????????????<BR>

    972. 

  972. 	      ??? 1 ???????????????????? 1 ??????????????<BR>

    973. 

  973. 	      ???????????????????????????????????????????????????????????????????????????<BR>

    974. 

  974. 	      ??????????????????????????:

    975. 

  975. 	      <TABLE BORDER CELLPADDING="2">

    976. 

  976. 	        <TR>

    977. 

  977. <!--		  <TH>Rule</TH>-->

    978. 

  978. 		  <TH>???</TH>

    979. 

  979. 		  <TD>a</TD>

    980. 

  980. 		  <TD>b</TD>

    981. 

  981. 		  <TD>c</TD>

    982. 

  982. 		  <TD>d</TD>

    983. 

  983. 		  <TD>e</TD>

    984. 

  984. 		  <TD>f</TD>

    985. 

  985. 	        </TR>

    986. 

  986. 	        <TR>

    987. 

  987. <!--		  <TH>Rule</TH>-->

    988. 

  988. 		  <TH>???</TH>

    989. 

  989. 		  <TD>a</TD>

    990. 

  990. 		  <TD>b</TD>

    991. 

  991. 		  <TD>c</TD>

    992. 

  992. 		  <TD>d</TD>

    993. 

  993. 		  <TD></TD>

    994. 

  994. 		  <TD></TD>

    995. 

  995. 	        </TR>

    996. 

  996. 	        <TR>

    997. 

  997. <!--		  <TH>Rule</TH>-->

    998. 

  998. 		  <TH>???</TH>

    999. 

  999. 		  <TD>a</TD>

    1000. 

  1000. 		  <TD>b</TD>

    1001. 

  1001. 		  <TD></TD>

    1002. 

  1002. 		  <TD></TD>

    1003. 

  1003. 		  <TD></TD>

    1004. 

  1004. 		  <TD></TD>

    1005. 

  1005. 	        </TR>

    1006. 

  1006. 	        <TR>

    1007. 

  1007. <!--		  <TH>Substitutions</TH> -->

    1008. 

  1008. 		  <TH>??</TH>

    1009. 

  1009. 		  <TD>A</TD>

    1010. 

  1010. 		  <TD>B</TD>

    1011. 

  1011. 		  <TD>C</TD>

    1012. 

  1012. 		  <TD>D</TD>

    1013. 

  1013. 		  <TD>E</TD>

    1014. 

  1014. 		  <TD>F</TD>

    1015. 

  1015. 	        </TR>

    1016. 

  1016. 	      </TABLE>

    1017. 

  1017. 	      <P>

    1018. 

  1018. <!--	      So the third rule will match an "ab" and convert them to "AB" (and this is

    1019. 

  1019. 	      valid because we have one internal and one final substitution and that's

    1020. 

  1020. 	      ok), then if that "ab" is followed by "cd" then rule 2 kicks in and will

    1021. 

  1021. 	      replace the "cd" with "CD" (again this has one internal and one final

    1022. 

  1022. 	      substitution, which is ok), and if that is followed by "ef" then they will

    1023. 

  1023. 	      be converted to "EF". -->

    1024. 

  1024. 	      ???? 3 ???????“ab”????????“AB”?????? (?????????? 1 ????????? 1 ??????????????????) ????“ab”???“cd”?????????? 2 ???????“cd”?“CD”????? (??????1 ??????? 1 ??????????????????????????)????“ef”??????????????“EF”????????

    1025. 

  1025. 	      <P>

    1026. 

  1026. <!--	      The following is not valid:-->

    1027. 

  1027. 	      ???????????:

    1028. 

  1028. 	      <TABLE BORDER CELLPADDING="2">

    1029. 

  1029. 	        <TR>

    1030. 

  1030. <!--		  <TH>Substitutions</TH> -->

    1031. 

  1031. 		  <TH>??</TH>

    1032. 

  1032. 		  <TD></TD>

    1033. 

  1033. 		  <TD>B</TD>

    1034. 

  1034. 		  <TD></TD>

    1035. 

  1035. 	        </TR>

    1036. 

  1036. 	        <TR>

    1037. 

  1037. <!--		  <TH>Rule</TH>-->

    1038. 

  1038. 		  <TH>???</TH>

    1039. 

  1039. 		  <TD>a</TD>

    1040. 

  1040. 		  <TD>b</TD>

    1041. 

  1041. 		  <TD>c</TD>

    1042. 

  1042. 	        </TR>

    1043. 

  1043. 	        <TR>

    1044. 

  1044. 		  <TD COLSPAN=4>

    1045. 

  1045. 		      <HR>

    1046. 

  1046. 		  </TD>

    1047. 

  1047. 	        </TR>

    1048. 

  1048. 	        <TR>

    1049. 

  1049. <!--		  <TH>Rule</TH>-->

    1050. 

  1050. 		  <TH>???</TH>

    1051. 

  1051. 		  <TD>a</TD>

    1052. 

  1052. 		  <TD>b</TD>

    1053. 

  1053. 		  <TD></TD>

    1054. 

  1054. 	        </TR>

    1055. 

  1055. 	        <TR>

    1056. 

  1056. <!--		  <TH>Substitutions</TH> -->

    1057. 

  1057. 		  <TH>??</TH>

    1058. 

  1058. 		  <TD>A</TD>

    1059. 

  1059. 		  <TD></TD>

    1060. 

  1060. 		  <TD></TD>

    1061. 

  1061. 	        </TR>

    1062. 

  1062. 	      </TABLE>

    1063. 

  1063. 	      <P>

    1064. 

  1064. <!--	      The two rules have substitutions at different places and that can't be expressed

    1065. 

  1065. 	      in an Apple state machine given that they have the same glyphs. -->

    1066. 

  1066. 	      2 ?????????????????????????????????????????? Apple ??????????????

    1067. 

  1067. 	  </UL>

    1068. 

  1068.       </OL>

    1069. 

  1069.   </UL>

    1070. 

  1070.   <P>

    1071. 

  1071. <!--

    1072. 

  1072.   FontForge does not even try to convert an AAT contextual glyph substitution

    1073. 

  1073.   sub-table, too few of these can be expressed in OpenType to make it worth

    1074. 

  1074.   while. -->

    1075. 

  1075.   FontForge ??AAT ????????????????????????????????????OpenType ????????????????????????????????

    1076. 

  1076.   <P>

    1077. 

  1077. <!--

    1078. 

  1078.   NOTE: It would be possible to convert more lookups to state machines if FontForge

    1079. 

  1079.   were willing to: -->

    1080. 

  1080.   ??: ?? FontForge ??????????????????????????????????????:

    1081. 

  1081.   <OL>

    1082. 

  1082.     <LI>

    1083. 

  1083. <!--  Use several state machines to represent complicated lookups -->

    1084. 

  1084.       ?????????????????????????

    1085. 

  1085.     <LI>

    1086. 

  1086. <!--  Add additional glyphs to the font to be used as temporary state flags. -->

    1087. 

  1087.       ??????????????????????????????

    1088. 

  1088.   </OL>

    1089. 

  1089.   <P>

    1090. 

  1090. <!--

    1091. 

  1091.   FontForge will do neither of these. -->

    1092. 

  1092.   ?????????FontForge ??????????????

    1093. 

  1093.   <H4>

    1094. 

  1094. <!--  <FONT COLOR="Red">BUG</FONT>-->

    1095. 

  1095.       <FONT COLOR="Red">??</FONT>

    1096. 

  1096.   </H4>

    1097. 

  1097.   <P>

    1098. 

  1098. <!--

    1099. 

  1099.   There is a subtle bug involved in converting a chaining contextual substitution

    1100. 

  1100.   into an Apple contextual glyph substitution. AAT does not have the concept

    1101. 

  1101.   of a backtrack list, this means that substitutions may occur in a different

    1102. 

  1102.   order. -->

    1103. 

  1103.   ??????????? Apple ????????????????????????????????AAT ??????????????????????????????????????????????????????

    1104. 

  1104.   <H4>

    1105. 

  1105. <!--  Why can't all contextual/chaining tables be

    1106. 

  1106.       <A NAME="not-converted">converted</A>? -->

    1107. 

  1107.       ??????????/????????????<A NAME="not-converted">????</A>?????

    1108. 

  1108.   </H4>

    1109. 

  1109.   <P>

    1110. 

  1110. <!--

    1111. 

  1111.   Well, obviously there are some thing that just aren't present. The concept

    1112. 

  1112.   of contextual positioning is missing from AAT, while Indic rearrangement

    1113. 

  1113.   is missing from OpenType. So let's concentrate on contextual substitutions,

    1114. 

  1114.   which both appear to support. The argument that follows is based on the

    1115. 

  1115.   capabilities of contextual matching, it applies equally to contextual ligatures,

    1116. 

  1116.   glyph insertion, glyph substitution and kerning, the examples given are only

    1117. 

  1117.   of glyph substitution because it is easier to represent (and because FontForge

    1118. 

  1118.   is only willing to convert contextual glyph substitutions) But even here,

    1119. 

  1119.   there is a very basic mismatch in concepts between the way OpenType and Apple

    1120. 

  1120.   specify contextual substitutions. Consider the following contextual substitution

    1121. 

  1121.   in a glyph list format: -->

    1122. 

  1122.   ?????????????????????????????????????? AAT ???????????????????? OpenType ????????

    1123. 

  1123.   ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? (??????FontForge ?????????????????????????????????)????????????OpenType ? Apple ???????????????????????????????????????????

    1124. 

  1124.   ????????????????????????????????????:

    1125. 

  1125.   <TABLE BORDER CELLPADDING="2">

    1126. 

  1126.     <TR>

    1127. 

  1127. <!--  <TH>Initial Sequence</TH>-->

    1128. 

  1128.       <TH>???????</TH>

    1129. 

  1129.       <TD>a</TD>

    1130. 

  1130.       <TD>b</TD>

    1131. 

  1131.       <TD>c</TD>

    1132. 

  1132.       <TD>d</TD>

    1133. 

  1133.     </TR>

    1134. 

  1134.     <TR>

    1135. 

  1135.       <TH><P ALIGN=Left>

    1136. 

  1136. <!--    Replace With</TH>-->

    1137. 

  1137.         ??????</TH>

    1138. 

  1138.       <TD>&nbsp;</TD>

    1139. 

  1139.       <TD>B</TD>

    1140. 

  1140.       <TD>C</TD>

    1141. 

  1141.       <TD>&nbsp;</TD>

    1142. 

  1142.     </TR>

    1143. 

  1143.   </TABLE>

    1144. 

  1144.   <P>

    1145. 

  1145. <!--

    1146. 

  1146.   Now in OpenType this means if you find the sequence "abcd" then replace the

    1147. 

  1147.   "b" with "B" and the" c" with "C". But this can't be expressed in an Apple

    1148. 

  1148.   state machine. In OpenType the match is done first, and then the substitutions

    1149. 

  1149.   occur. In a state machine the substitutions have to be done (almost) concurrently

    1150. 

  1150.   with the match and so must happen whether the final "d" is present or not.

    1151. 

  1151.   (Note I'm using a glyph sequence because it is easier to display in an example.

    1152. 

  1152.   The same problem applies if the substitution is expressed by classes or by

    1153. 

  1153.   coverage tables) -->

    1154. 

  1154.   ????OpenType ?????“abcd”??????????????????“b”?“B”??“c”?“C”?????????????? Apple ??????????????OpenType ????????????????????????????????? (????) ?????????????????“d”??????????????????????(??????????????????????????????????????????????????????????????????????????????????)

    1155. 

  1155.   <P>

    1156. 

  1156. <!--

    1157. 

  1157.   Consider the following table with two glyph strings -->

    1158. 

  1158.   ???????2 ????????????????????:

    1159. 

  1159.   <TABLE BORDER CELLPADDING="2">

    1160. 

  1160.     <TR>

    1161. 

  1161. <!--  <TH>Initial Sequence</TH>-->

    1162. 

  1162.       <TH>???????</TH>

    1163. 

  1163.       <TD>a</TD>

    1164. 

  1164.       <TD><P ALIGN=Center>

    1165. 

  1165.         b</TD>

    1166. 

  1166.       <TD><P ALIGN=Center>

    1167. 

  1167.         c</TD>

    1168. 

  1168.       <TD>d</TD>

    1169. 

  1169.     </TR>

    1170. 

  1170.     <TR>

    1171. 

  1171.       <TH><P ALIGN=Left>

    1172. 

  1172. <!--    Replace With</TH>-->

    1173. 

  1173.         ??????</TH>

    1174. 

  1174.       <TD>&nbsp;</TD>

    1175. 

  1175.       <TD><P ALIGN=Center>

    1176. 

  1176.         B</TD>

    1177. 

  1177.       <TD></TD>

    1178. 

  1178.       <TD>&nbsp;</TD>

    1179. 

  1179.     </TR>

    1180. 

  1180.     <TR>

    1181. 

  1181. <!--  <TH>Initial Sequence</TH>-->

    1182. 

  1182.       <TH>???????</TH>

    1183. 

  1183.       <TD>a</TD>

    1184. 

  1184.       <TD><P ALIGN=Center>

    1185. 

  1185.         b</TD>

    1186. 

  1186.       <TD><P ALIGN=Center>

    1187. 

  1187.         c</TD>

    1188. 

  1188.       <TD>e&nbsp;</TD>

    1189. 

  1189.     </TR>

    1190. 

  1190.     <TR>

    1191. 

  1191.       <TH><P ALIGN=Left>

    1192. 

  1192. <!--    Replace With</TH>-->

    1193. 

  1193.         ??????</TH>

    1194. 

  1194.       <TD>&nbsp;</TD>

    1195. 

  1195.       <TD></TD>

    1196. 

  1196.       <TD><P ALIGN=Center>

    1197. 

  1197.         &nbsp;C</TD>

    1198. 

  1198.       <TD>&nbsp;</TD>

    1199. 

  1199.     </TR>

    1200. 

  1200.   </TABLE>

    1201. 

  1201.   <P>

    1202. 

  1202. <!--

    1203. 

  1203.   So replace the "b" if the final "d" is present, otherwise replace the "c".

    1204. 

  1204.   Again this cannot be expressed in Apple's state machines. -->

    1205. 

  1205.   ???????“d”??????“b”??????????????“c”????????????Apple ???????????????

    1206. 

  1206.   <P>

    1207. 

  1207. <!--

    1208. 

  1208.   Finally consider -->

    1209. 

  1209.   ?????????????????:

    1210. 

  1210.   <TABLE BORDER CELLPADDING="2">

    1211. 

  1211.     <TR>

    1212. 

  1212. <!--  <TH>Initial Sequence</TH>-->

    1213. 

  1213.       <TH>???????</TH>

    1214. 

  1214.       <TD><P ALIGN=Center>

    1215. 

  1215.         a</TD>

    1216. 

  1216.       <TD><P ALIGN=Center>

    1217. 

  1217.         b</TD>

    1218. 

  1218.       <TD><P ALIGN=Center>

    1219. 

  1219.         c</TD>

    1220. 

  1220.       <TD>d</TD>

    1221. 

  1221.     </TR>

    1222. 

  1222.     <TR>

    1223. 

  1223.       <TH><P ALIGN=Left>

    1224. 

  1224. <!--    Replace With</TH>-->

    1225. 

  1225.         ??????</TH>

    1226. 

  1226.       <TD>&nbsp;</TD>

    1227. 

  1227.       <TD><P ALIGN=Center>

    1228. 

  1228.       </TD>

    1229. 

  1229.       <TD>C</TD>

    1230. 

  1230.       <TD>&nbsp;</TD>

    1231. 

  1231.     </TR>

    1232. 

  1232.     <TR>

    1233. 

  1233. <!--  <TH>Initial Sequence</TH>-->

    1234. 

  1234.       <TH>???????</TH>

    1235. 

  1235.       <TD><P ALIGN=Center>

    1236. 

  1236.         b</TD>

    1237. 

  1237.       <TD><P ALIGN=Center>

    1238. 

  1238.         c</TD>

    1239. 

  1239.       <TD><P ALIGN=Center>

    1240. 

  1240.         e</TD>

    1241. 

  1241.       <TD></TD>

    1242. 

  1242.     </TR>

    1243. 

  1243.     <TR>

    1244. 

  1244.       <TH><P ALIGN=Left>

    1245. 

  1245. <!--    Replace With</TH>-->

    1246. 

  1246.         ??????</TH>

    1247. 

  1247.       <TD><P ALIGN=Center>

    1248. 

  1248.         B&nbsp;</TD>

    1249. 

  1249.       <TD></TD>

    1250. 

  1250.       <TD><P ALIGN=Center>

    1251. 

  1251.         &nbsp;</TD>

    1252. 

  1252.       <TD>&nbsp;</TD>

    1253. 

  1253.     </TR>

    1254. 

  1254.   </TABLE>

    1255. 

  1255.   <P>

    1256. 

  1256. <!--

    1257. 

  1257.   If this substitution is given the sequence "abce" it cannot work in AAT.

    1258. 

  1258.   When it reads the "a" it will start down the "abcd" branch, the match will

    1259. 

  1259.   not fail until it looks for the "d" and finds "e" instead. At that point

    1260. 

  1260.   it is too late to switch to the "bce" substitution (which does match) because

    1261. 

  1261.   the "b" glyph will not have been marked as a substitution location. -->

    1262. 

  1262.   ??????????????????“abce”? AAT ?????????

    1263. 

  1263.   "a" ?????????“abcd”???????"d" ???????“e”??????????????????????“bce”?????????????(???????????????)??????“b”??????????????????????????

    1264. 

  1264.   <P>

    1265. 

  1265.     <HR>

    1266. 

  1266. <!--

    1267. 

  1267.   On the other hand, Apple's state machines can express things that OpenType

    1268. 

  1268.   tables cannot (again I'm restricting myself to contextual glyph substitutions).

    1269. 

  1269.   Consider the case of a swash glyph at the beginning (or end) of a word. Let

    1270. 

  1270.   us say that a word begins when a letter appears at the start of input or

    1271. 

  1271.   following a whitespace character. But OpenType has no way of expressing "start

    1272. 

  1272.   of input" (or end of input) in a contextual/chaining context, whereas Apple's

    1273. 

  1273.   state machines do.-->

    1274. 

  1274.   ???Apple ?????? OpenType ????????????????? (?????????????????????)?????? (?????) ???????????????????????????????????????????????????????? OpenType ?????/?????????????Apple ??????????“??????”(????????) ??????????????

    1275. 

  1275.   <P>

    1276. 

  1276. <!--

    1277. 

  1277.   Since Apple's glyph substitutions can delete glyphs a contextual glyph

    1278. 

  1278.   substitution table can create two character ligatures (one glyph is converted

    1279. 

  1279.   to the ligature and the other is deleted), while OpenType tables must use

    1280. 

  1280.   a ligature substitution to do this. -->

    1281. 

  1281.   Apple ?????????????????????????????????????? 2 ????????????????? (????????????????????????) ??OpenType ?????????????????????????????

    1282. 

  1282.   <P>

    1283. 

  1283. <!--

    1284. 

  1284.   Finally an AAT state machine can match a general regular expression, while

    1285. 

  1285.   OpenType tables can only match fixed length strings. Suppose you were typesetting

    1286. 

  1286.   mathematics and wanted a substitution which would convert an arbitrary digit

    1287. 

  1287.   string following a variable into a subscript (so x23 should become

    1288. 

  1288.   x<SMALL><SUB>23</SUB></SMALL>). It is easy to write a state machine which

    1289. 

  1289.   will keep substituting as long as it gets more digits, but you'd need an

    1290. 

  1290.   infinite number of OpenType rules to have the same expressive power. -->

    1291. 

  1291.   ????AAT ????????????????????????????OpenType ?????????????????????????????????????????????????????????????????? (?????x23 ? x<SMALL><SUB>23</SUB></SMALL> ?????)????????????????????????????????????????????? OpenType ??????????????????????

    1292. 

  1292.   <P>

    1293. 

  1293. <!--

    1294. 

  1294.   These examples probably seem fairly contrived, and (except for the swash

    1295. 

  1295.   one) they are. But they illustrate the point that the two formats have very

    1296. 

  1296.   different expressive capabilities and it is NOT possible to write a converter

    1297. 

  1297.   which will take any input in one format and produce an equivalent output

    1298. 

  1298.   in the other. -->

    1299. 

  1299.   ??????????????????????????(??????????????) ???????????????????2 ????????????????????????????????????????????????????????????????????????????????????<em>???</em>?????????????

    1300. 

  1300.   <H3>

    1301. 

  1301. <!--  Apple and OpenType features-->

    1302. 

  1302.       Apple ? OpenType ???

    1303. 

  1303.   </H3>

    1304. 

  1304.   <TABLE BORDER CELLPADDING="2">

    1305. 

  1305.     <CAPTION>

    1306. 

  1306. <!--  Correspondences between Apple and OpenType

    1307. 

  1307.       <A NAME="OT-Mac-features">features</A><BR>

    1308. 

  1308.       (that I support) -->

    1309. 

  1309.       Apple ? OpenType ? <A NAME="OT-Mac-features">??</A> ????<BR>

    1310. 

  1310.       (?????????????)

    1311. 

  1311.     </CAPTION>

    1312. 

  1312.     <TR>

    1313. 

  1313. <!--  <TH>Apple Feature Setting</TH>-->

    1314. 

  1314.       <TH>Apple ?????</TH>

    1315. 

  1315. <!--  <TH>OpenType Feature Name</TH> -->

    1316. 

  1316.       <TH>OpenType ????</TH>

    1317. 

  1317. <!--  <TH>OpenType Tag</TH> -->

    1318. 

  1318.       <TH>OpenType ??</TH>

    1319. 

  1319.     </TR>

    1320. 

  1320.     <TR>

    1321. 

  1321. <!--  <TD>Required Ligatures</TD> -->

    1322. 

  1322.       <TD>?????</TD>

    1323. 

  1323. <!--  <TD>Required Ligatures</TD> -->

    1324. 

  1324.       <TD>?????</TD>

    1325. 

  1325.       <TD>rlig</TD>

    1326. 

  1326.     </TR>

    1327. 

  1327.     <TR>

    1328. 

  1328. <!--  <TD>Common Ligatures</TD> -->

    1329. 

  1329.       <TD>??????</TD>

    1330. 

  1330. <!--  <TD>Standard Ligatures</TD> -->

    1331. 

  1331.       <TD>?????</TD>

    1332. 

  1332.       <TD>liga</TD>

    1333. 

  1333.     </TR>

    1334. 

  1334.     <TR>

    1335. 

  1335. <!--  <TD>Rare Ligatures</TD> -->

    1336. 

  1336.       <TD>????</TD>

    1337. 

  1337. <!--  <TD>Discretionary</TD> -->

    1338. 

  1338.       <TD>?????</TD>

    1339. 

  1339.       <TD>dlig</TD>

    1340. 

  1340.     </TR>

    1341. 

  1341.     <TR>

    1342. 

  1342. <!--  <TD>Fractions</TD>-->

    1343. 

  1343.       <TD>??</TD>

    1344. 

  1344. <!--  <TD>Fractions</TD>-->

    1345. 

  1345.       <TD>??</TD>

    1346. 

  1346.       <TD>frac</TD>

    1347. 

  1347.     </TR>

    1348. 

  1348.     <TR>

    1349. 

  1349.       <TD COLSPAN=3>

    1350. 

  1350. 	  <HR>

    1351. 

  1351.       </TD>

    1352. 

  1352.     </TR>

    1353. 

  1353.     <TR>

    1354. 

  1354. <!--  <TD>Contextual Alternatives</TD>-->

    1355. 

  1355.       <TD>????????</TD>

    1356. 

  1356. <!--  <TD>Cursive connection</TD>-->

    1357. 

  1357.       <TD>??????</TD>

    1358. 

  1358.       <TD>calt</TD>

    1359. 

  1359.     </TR>

    1360. 

  1360.     <TR>

    1361. 

  1361.       <TD COLSPAN=3>

    1362. 

  1362. 	  <HR>

    1363. 

  1363.       </TD>

    1364. 

  1364.     </TR>

    1365. 

  1365.     <TR>

    1366. 

  1366. <!--  <TD>Vertical Forms</TD>-->

    1367. 

  1367.       <TD>?????</TD>

    1368. 

  1368. <!--  <TD>Vertical Rotation 2</TD>-->

    1369. 

  1369.       <TD>????????</TD>

    1370. 

  1370.       <TD>vrt2</TD>

    1371. 

  1371.     </TR>

    1372. 

  1372.     <TR>

    1373. 

  1373. <!--  <TD>Monospace numbers</TD>-->

    1374. 

  1374.       <TD>????</TD>

    1375. 

  1375. <!--  <TD>Tabular numbers</TD>-->

    1376. 

  1376.       <TD>????</TD>

    1377. 

  1377.       <TD>tnum</TD>

    1378. 

  1378.     </TR>

    1379. 

  1379.     <TR>

    1380. 

  1380. <!--  <TD>Superscript</TD>-->

    1381. 

  1381.       <TD>?????</TD>

    1382. 

  1382. <!--  <TD>Superscript</TD>-->

    1383. 

  1383.       <TD>?????</TD>

    1384. 

  1384.       <TD>sups</TD>

    1385. 

  1385.     </TR>

    1386. 

  1386.     <TR>

    1387. 

  1387. <!--  <TD>Subscript</TD>-->

    1388. 

  1388.       <TD>?????</TD>

    1389. 

  1389. <!--  <TD>Subscript</TD>-->

    1390. 

  1390.       <TD>?????</TD>

    1391. 

  1391.       <TD>subs</TD>

    1392. 

  1392.     </TR>

    1393. 

  1393.     <TR>

    1394. 

  1394. <!--  <TD>Proportional Text</TD>-->

    1395. 

  1395.       <TD>????????????</TD>

    1396. 

  1396. <!--  <TD>Proportional Widths</TD>-->

    1397. 

  1397.       <TD>?????????</TD>

    1398. 

  1398.       <TD>pwid</TD>

    1399. 

  1399.     </TR>

    1400. 

  1400.     <TR>

    1401. 

  1401. <!--  <TD>Half-width Text</TD>-->

    1402. 

  1402.       <TD>??????</TD>

    1403. 

  1403. <!--  <TD>Half Width</TD>-->

    1404. 

  1404.       <TD>??</TD>

    1405. 

  1405.       <TD>hwid</TD>

    1406. 

  1406.     </TR>

    1407. 

  1407.     <TR>

    1408. 

  1408. <!--  <TD>Full-width Text</TD>-->

    1409. 

  1409.       <TD>??????</TD>

    1410. 

  1410. <!--  <TD>Full Width</TD>-->

    1411. 

  1411.       <TD>??</TD>

    1412. 

  1412.       <TD>fwid</TD>

    1413. 

  1413.     </TR>

    1414. 

  1414.     <TR>

    1415. 

  1415. <!--  <TD>Traditional Characters</TD>-->

    1416. 

  1416.       <TD>??????</TD>

    1417. 

  1417. <!--  <TD>Traditional</TD>-->

    1418. 

  1418.       <TD>???</TD>

    1419. 

  1419.       <TD>trad</TD>

    1420. 

  1420.     </TR>

    1421. 

  1421.     <TR>

    1422. 

  1422. <!--  <TD>Simplified Characters</TD>-->

    1423. 

  1423.       <TD>??????</TD>

    1424. 

  1424. <!--  <TD>Simplified</TD>-->

    1425. 

  1425.       <TD>???</TD>

    1426. 

  1426.       <TD>smpl</TD>

    1427. 

  1427.     </TR>

    1428. 

  1428.     <TR>

    1429. 

  1429. <!--  <TD>JIS 1978 Characters</TD>-->

    1430. 

  1430.       <TD>1978 ?? JIS ??</TD>

    1431. 

  1431. <!--  <TD>JIS 1978 Characters</TD>-->

    1432. 

  1432.       <TD>1978 ?? JIS ??</TD>

    1433. 

  1433.       <TD>jp78</TD>

    1434. 

  1434.     </TR>

    1435. 

  1435.     <TR>

    1436. 

  1436. <!--  <TD>JIS 1983 Characters</TD>-->

    1437. 

  1437.       <TD>1983 ?? JIS ??</TD>

    1438. 

  1438. <!--  <TD>JIS 1983 Characters</TD>-->

    1439. 

  1439.       <TD>1983 ?? JIS ??</TD>

    1440. 

  1440.       <TD>jp83</TD>

    1441. 

  1441.     </TR>

    1442. 

  1442.     <TR>

    1443. 

  1443. <!--  <TD>JIS 1990 Characters</TD>-->

    1444. 

  1444.       <TD>1990 ?? JIS ??</TD>

    1445. 

  1445. <!--  <TD>JIS 1990 Characters</TD>-->

    1446. 

  1446.       <TD>1990 ?? JIS ??</TD>

    1447. 

  1447.       <TD>jp90</TD>

    1448. 

  1448.     </TR>

    1449. 

  1449.   </TABLE>

    1450. 

  1450.   <P>

    1451. 

  1451. <!--

    1452. 

  1452.   FontForge will retain the order of features in the morx table, and the user

    1453. 

  1453.   may adjust it with the <A HREF="fontinfo.html#Order">Element-&gt;Font Info</A>

    1454. 

  1454.   command. (this is the same list as that used for GSUB table. GSUB features

    1455. 

  1455.   that don't correspond to mac features will be ignored). -->

    1456. 

  1456.   FontForge ? morx ??????????????????????? <A HREF="fontinfo.html#Order"><CODE>?????(<U>L</U>)</CODE>?<CODE>??????(<U>F</U>)...</CODE></A> ??????????????????(??? GSUB ???????????????????????Mac ?????????? GSUB ?????????)?

    1457. 

  1457.   <H2>

    1458. 

  1458. <!--  What is <A NAME="Unsupported">Unsupported</A>?-->

    1459. 

  1459.       ?????<A NAME="Unsupported">??????????</A>???

    1460. 

  1460.   </H2>

    1461. 

  1461.   <P>

    1462. 

  1462. <!--

    1463. 

  1463.   FontForge does not (yet) support all the advanced typographic features available

    1464. 

  1464.   in either opentype or apple advanced typography. -->

    1465. 

  1465.   FontForge ? OpenType ? AAT ???????(??) ??????????????????????????

    1466. 

  1466.   <H3>

    1467. 

  1467.     OpenType

    1468. 

  1468.   </H3>

    1469. 

  1469.   <UL>

    1470. 

  1470.     <LI>

    1471. 

  1471. <!--  FontForge does not support using truetype points to control positioning -->

    1472. 

  1472.       FontForge ? TrueType ?????????????????????????

    1473. 

  1473.     <LI>

    1474. 

  1474.       FontForge does not support some of the more esoteric uses of the lookup flags.

    1475. 

  1475.       FontForge ??????????????????????????????????

    1476. 

  1476.     <LI>

    1477. 

  1477. <!--  FontForge does not provide an attachment list subtable nor a MarkAttachClassDef

    1478. 

  1478.       subtable of the GDEF table. -->

    1479. 

  1479.       FontForge ? GDEF ????????????????? MarkAttachClassDef ????????????????

    1480. 

  1480.     <LI>

    1481. 

  1481. <!--  FontForge does not support the BASE and JUST tables-->

    1482. 

  1482.       FontForge ? BASE ????? JUST ??????????????

    1483. 

  1483.     <LI>

    1484. 

  1484. <!--  FontForge has minimal support for VORG-->

    1485. 

  1485.       FontForge ? VORG ????????????????????????

    1486. 

  1486.   </UL>

    1487. 

  1487.   <P>

    1488. 

  1488. <!--  <A HREF="TrueOpenTables.html">See here for a complete list of supported

    1489. 

  1489.   tables</A>. -->

    1490. 

  1490.   <A HREF="TrueOpenTables.html">??????????????????????????????</A>?

    1491. 

  1491.   <H3>

    1492. 

  1492. <!--  Apple Advanced Typography-->

    1493. 

  1493.       Apple ??????

    1494. 

  1494.   </H3>

    1495. 

  1495.   <UL>

    1496. 

  1496.     <LI>

    1497. 

  1497. <!--  FontForge will never generate a 'mort' table. It can read 'mort' tables,

    1498. 

  1498.       but it will only produce 'morx' tables. -->

    1499. 

  1499.       FontForge ????&lsquo;mort&rsquo;????????????&lsquo;mort&rsquo;????????????????????????&lsquo;morx&rsquo;?????????

    1500. 

  1500.     <LI>

    1501. 

  1501. <!--  FontForge is unable to parse contextual ligatures. It can find ligatures

    1502. 

  1502.       which start from state 0, but it will not find ligatures which start from

    1503. 

  1503.       other states (that is, which are contextual) -->

    1504. 

  1504.       FontForge ???????????????????????? 0 ????????????????????????? (??????????) ???????????

    1505. 

  1505.     <LI>

    1506. 

  1506. <!--  FontForge does not support the following Apple specific tables -->

    1507. 

  1507.       FontForge ???? Apple ?????????????????

    1508. 

  1508.       <UL>

    1509. 

  1509.         <LI>

    1510. 

  1510. <!--	  acnt (accent attachment) -->

    1511. 

  1511. 	  acnt (????????)

    1512. 

  1512.         <LI>

    1513. 

  1513. <!--	  bsln (baseline) -->

    1514. 

  1514. 	  bsln (??????)

    1515. 

  1515.         <LI>

    1516. 

  1516. <!--	  fdsc (font descriptor) -->

    1517. 

  1517. 	  fdsc (???????)

    1518. 

  1518.         <LI>

    1519. 

  1519. <!--	  fmtx (font metrics) -->

    1520. 

  1520. 	  fmtx (?????????)

    1521. 

  1521.         <LI>

    1522. 

  1522. <!--	  hsty (horizontal style) -->

    1523. 

  1523. 	  hsty (???????????)

    1524. 

  1524.         <LI>

    1525. 

  1525. <!--	  just (justification) -->

    1526. 

  1526. 	  just (???)

    1527. 

  1527.         <LI>

    1528. 

  1528. <!--	  trak (tracking) -->

    1529. 

  1529. 	  trak (??????)

    1530. 

  1530.         <LI>

    1531. 

  1531. <!--	  Zapf (glyph reference)-->

    1532. 

  1532. 	  Zapf (?????)

    1533. 

  1533.       </UL>

    1534. 

  1534.   </UL>

    1535. 

  1535.   <P>

    1536. 

  1536. <!--

    1537. 

  1537.   <A HREF="TrueOpenTables.html">See here for a complete list of supported

    1538. 

  1538.   tables</A>. -->

    1539. 

  1539.   <A HREF="TrueOpenTables.html">???????????????????????????????</A>?

    1540. 

  1540.   <P>

    1541. 

  1541.   <P ALIGN=Center>

    1542. 

  1542.   ? <A HREF="generate.html">?</A> ? <A HREF="overview.html">??</A> ?

    1543. 

  1543.   <A HREF="filemenu.html">?</A> ?

    1544. 

  1544. </DIV>

    1545. 

  1545. </BODY></HTML>

    1546. 

  1546.