PageRenderTime 57ms CodeModel.GetById 19ms RepoModel.GetById 0ms app.codeStats 0ms

/htdocs.OLD/ja/charinfo.html

https://bitbucket.org/sortsmill/sortsmill-tools
HTML | 398 lines | 153 code | 0 blank | 245 comment | 0 complexity | 84eb7e120e5bd41254c13a3077436e33 MD5 | raw file
Possible License(s): GPL-3.0, LGPL-2.0
  1. <HTML>
  2. <HEAD>
  3. <!-- Created with AOLpress/2.0 -->
  4. <!-- AP: Created on: 29-Dec-2002 -->
  5. <!-- AP: Last modified: 3-Jul-2006 -->
  6. <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=Shift_JIS">
  7. <!--<TITLE>Char Info</TITLE>-->
  8. <TITLE>?????</TITLE>
  9. <LINK REL="icon" href="../fftype16.png">
  10. <LINK REL="stylesheet" TYPE="text/css" HREF="FontForge.css">
  11. </HEAD>
  12. <BODY>
  13. <DIV id="in">
  14. <H1 ALIGN=Center>
  15. <!-- Glyph Info-->
  16. ?????
  17. </H1>
  18. <H2>
  19. <IMG SRC="../charinfo.png" WIDTH="307" HEIGHT="409" ALIGN="Right">
  20. <!-- <A NAME="Character">Glyph</A> Info-->
  21. <A NAME="Character">???</A>??
  22. </H2>
  23. <UL>
  24. <LI>
  25. <!-- <A HREF="charinfo.html#Unicode">Encoding and Unicode data</A>-->
  26. <A HREF="charinfo.html#Unicode">????????? Unicode ??</A>
  27. <LI>
  28. <!-- <A HREF="charinfo.html#comment">Glyph Comment</A>-->
  29. <A HREF="charinfo.html#comment">???????</A>
  30. <LI>
  31. <!-- <A HREF="charinfo.html#position">Simple Glyph Positioning </A> (GPOS)-->
  32. <A HREF="charinfo.html#position">?????????</A>(GPOS)
  33. <LI>
  34. <!-- <A HREF="charinfo.html#pairwise">Pair-wise Glyph Positioning other than kerning
  35. </A>(GPOS)-->
  36. <A HREF="charinfo.html#pairwise">????????????????</A> (GPOS)
  37. <LI>
  38. <!-- <A HREF="charinfo.html#substitution">Glyph Simple Substitution</A> (GSUB,
  39. morx) -->
  40. <A HREF="charinfo.html#substitution">???????</A> (GSUB, morx)
  41. <LI>
  42. <!-- <A HREF="charinfo.html#multiple">Glyph Alternate Substitution</A> (GSUB)-->
  43. <A HREF="charinfo.html#multiple">????????</A> (GSUB)
  44. <LI>
  45. <!-- <A HREF="charinfo.html#multiple">Glyph Multiple Substitution</A> (GSUB)-->
  46. <A HREF="charinfo.html#multiple">?????????</A> (GSUB)
  47. <LI>
  48. <!-- <A HREF="charinfo.html#ligature">Glyph Ligature Substitution </A>(GSUB, morx) -->
  49. <A HREF="charinfo.html#ligature">???????</A> (GSUB, morx)
  50. <LI>
  51. <!-- <A HREF="charinfo.html#components">Components</A>-->
  52. <A HREF="charinfo.html#components">????</A>
  53. <LI>
  54. <!-- <A HREF="#CounterMasks">Counter Masks</A>-->
  55. <A HREF="#CounterMasks">???????</A>
  56. </UL>
  57. <P>
  58. <!--
  59. <A NAME="Unicode">This dialog </A>allows you to set the name and unicode
  60. encoding of a given glyph. If you know the name of the glyph then FontForge
  61. can tell you the encoding (if you press Set From Name), similarly if you
  62. know the encoding then FontForge can tell you the name. -->
  63. <A NAME="Unicode">???????</A>?????????????Unicode???????????????????????????(<CODE>[?????(<U>A</U>)]</CODE> ???????) FontForge ????????????????????????????????????????FontForge ?????????????????
  64. <P>
  65. <!--
  66. The name field contains a pull down list with (possibly) several synonyms
  67. for the name of this unicode code point. -->
  68. <CODE>Unicode?(<U>N</U>)</CODE> ????????? Unicode ?????????????? (????) ??????????????????????????????
  69. <P>
  70. <!--
  71. The Glyph class field is for the opentype 'GDEF' table. You can usually leave
  72. it set to automatic. FontForge will then figure out the class, and whether
  73. it should be output into GDEF. You can see what FontForge does in
  74. <A HREF="showatt.html">View-&gt;Show ATT</A>.<BR CLEAR=ALL> -->
  75. <CODE>OTF??????(<U>G</U>)</CODE> ?????? OpenType ?&lsquo;GDEF&rsquo;??????????????????????????????????????????FontForge ?????????GDEF ????????????????????????FontForge ????????????<A HREF="showatt.html"><CODE>??(<U>V</U>)</CODE>?<CODE>ATT???(<U>S</U>)</CODE></A>????????????<BR CLEAR=ALL>
  76. <P>
  77. <IMG SRC="../charinfo-comment.png" WIDTH="307" HEIGHT="359" ALIGN="Right"><!--You
  78. can assign an arbitrary (unicode) <A NAME="comment">comment</A> to the glyph.
  79. Simply type any text into this field. The comment is for your use, it will
  80. not go into any generated fonts. You may also assign a color to a glyph to
  81. make it stand out in the font view.<BR CLEAR=ALL> -->
  82. ??????????? (Unicode ?) <A NAME="comment">????</A>?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<BR CLEAR=ALL>
  83. <P>
  84. <IMG SRC="../charinfo-pos.png" WIDTH="305" HEIGHT="400" ALIGN="Right"><!-- There
  85. are 6 separate sub-dialogs to help you edit the
  86. <A NAME="features">features</A> of the <A HREF="gposgsub.html">GPOS and
  87. GSUB</A> tables (some of these data can be converted into various of Apple's
  88. AAT tables, particularly 'morx'). The first of these is the alternate
  89. <A NAME="position">position</A> dialog which allows you to associate certain
  90. modifications to a glyph's metrics with a feature in the GPOS table. -->
  91. <A HREF="gposgsub.html">GPOS ??? GSUB</A>?????<A NAME="features">??</A>????????????6 ?????????????????? (???????????????????? Apple ? AAT ?????????&lsquo;morx&rsquo;??????????????)????????????????????GPOS ???????????????????????????????????????<A NAME="position">??</A>??????????
  92. <P>
  93. <!--
  94. In the example at right the 'fwid' feature (full width) adds 400 units to
  95. the glyph's advance width and moves it horizontally by 200 units. -->
  96. ?????&lsquo;fwid&rsquo;(??) ??????????? 400 ????????????200 ???????????????
  97. <P>
  98. <!--
  99. A new entry in the list may be created by pressing the [New] button and a
  100. <A HREF="#Feature-Tag">dlg</A> will pop up with fields for the metrics you
  101. can change. It will also have a field for a feature tag, and a set of check
  102. boxes for flags (these flags are not relevant here, but are included as an
  103. exercise in asinine completeness. -->
  104. ????????????<CODE>[??(<U>N</U>)...]</CODE> ?????????????????????????????????????????<A HREF="#Feature-Tag">?????</A>????????????????????????????????????????????????????????? (???????????????????????????????????????????)?
  105. <P>
  106. <!--
  107. The [Delete] and [Edit] buttons should be fairly self-explanatory. [Copy]
  108. and [Paste] work as expected too. You can also paste something copied here
  109. into the font view (if you wish to have the same position information available
  110. in a large block of glyphs). -->
  111. <CODE>[??(<U>D</U>)]</CODE> ??? <CODE>[??(<U>E</U>)...]</CODE> ???????????????????<CODE>[???(<U>C</U>)]</CODE> ??? <CODE>[????(<U>P</U>)]</CODE> ?????????????????????????????????????????????????? (????????????????????????????????)?
  112. <P>
  113. <!--
  114. The <A NAME="pairwise">pairwise</A> positioning sub-dialog allows you to
  115. change the positions of two glyphs when they occur next to one another. The
  116. most common example of that is kerning (which is better done elsewhere, the
  117. metricsview for example, but it can be done here if you really want to do
  118. that).<BR Clear=Right> -->
  119. <A NAME="pairwise">????</A>???????????????2 ????????????????????????????????????????????????? (???????????????????????????????????????????????????????????<BR Clear=Right>
  120. <P>
  121. <IMG SRC="../charinfo-subs.png" WIDTH="305" HEIGHT="400" ALIGN="Right"><!-- A simple
  122. <A NAME="substitution">substitution</A> replaces one glyph with another.
  123. Here the glyph "one" has a substitution to "onesuperior" when the 'sups'
  124. (Superscript) feature is invoked. -->
  125. ??<A NAME="substitution">??</A> (<CODE>[??]</CODE>) ? 1 ??????????????????????????one??&lsquo;sups&rsquo;(?????) ???????????onesuperior???????????????
  126. <P>
  127. <!--
  128. FontForge recognizes a special feature tag ' RQD' to indicate that this feature
  129. is required for the given script/language. Such a feature will always be
  130. applied. -->
  131. FontForge ??????????????/???????????????????????&lsquo; RQD&rsquo;????????????????????????
  132. <P>
  133. <!--
  134. You can generate a substitution most easily by dragging a glyph from the
  135. font view and dropping it here (you will then be
  136. <A HREF="#Feature-Tag">prompted for a feature tag</A> for the substitution
  137. table. -->
  138. ???????????????????????????????????????????????? (?????????????<A HREF="#Feature-Tag">?????????????????</A>?
  139. <P>
  140. <!--
  141. The <A NAME="multiple">multiple</A> and alternate substitution sub-dialogs
  142. are very similar to this one except that they can take multiple glyph names.
  143. In a multiple substitution sub table each glyph is replaced by several other
  144. glyphs (sort of the reverse of a ligature), while in the alternate substitution
  145. sub-dialog each glyph is to be replaced by exactly one glyph from a list
  146. and the user is to be given a choice as to which glyph is to be chosen. -->
  147. [<CODE><A NAME="multiple">??</A>????</CODE>] ??? <CODE>[?????]</CODE> ??????????????????????????????????????????????<CODE>[??????]</CODE> ????????????????????????????????? (????????????)?<CODE>[??????]</CODE> ???????????????????????????? 1 ???????????????????????????????????????????
  148. <BR Clear=Right>
  149. <P>
  150. <IMG SRC="../charinfo-lig.png" WIDTH="305" HEIGHT="400" ALIGN="Right"><!-- The
  151. <A NAME="ligature">ligature</A> field allows you to tell FontForge that the
  152. current glyph is a ligature composed of several other glyphs. FontForge will
  153. often be able to fill this in with the right default value, but occasionally
  154. you may want to change it. The value should be a list of postscript glyph
  155. names separated by spaces. If a glyph may be viewed as two different ligatures
  156. then they may both be specified in different lines. For example "ffi" may
  157. be viewed as a ligature of "f" "f" and "i" or of "ff" and "i". -->
  158. <CODE>[<A NAME="ligature">??</A>]</CODE> ????????FontForge ?????????????????????????????????? FontForge ?????????????FontForge ??????????????????????????????????????????????????????????????????? PostScript ????????????????????????? 2 ???????????????????????????????????????????????????ffi?ff???i???????????????ff?i???????????
  159. <P>
  160. <!--
  161. In the example at right the "m" glyph is one of a set of flags stored in
  162. the GSUB table. It indicates that combining marks should be ignored when
  163. looking for the ligature. -->
  164. ???????m ? GSUB ?????????????????? 1 ??????????????????????????????????????????
  165. <P>
  166. <!--
  167. The <A HREF="gposgsub.html">GPOS and GSUB</A> tables allow further refinements
  168. of ligatures. You may classify a ligature as: Standard, Required, Discretionary,
  169. Historic or Fraction. Required ligatures must be replaced, Standard ligatures
  170. should be, Discretionary ones may be, and Historic ones should only be used
  171. int appropriate circumstances. The pull down list on the Tag field allows
  172. you to pick what type of ligature this should be. <BR Clear=Right> -->
  173. <A HREF="gposgsub.html">GPOS ??? GSUB</A> ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????<BR Clear=Right>
  174. <P>
  175. <IMG SRC="../charinfo-counters.png" WIDTH="307" HEIGHT="409" ALIGN="Right">
  176. <!--
  177. In complicated Asian glyphs, postscript has a mechanism for controlling the
  178. width of <A NAME="CounterMasks">counters</A> between stems. These are called
  179. counter mask
  180. hints<IMG SRC="newcountermask.png" WIDTH="282" HEIGHT="392" ALIGN="Left">.
  181. In Latin, Cyrillic, Greek fonts only glyphs like "m" are allowed to have
  182. counter masks, and only in very controlled conditions. See the description
  183. of <A HREF="hinting.html#Counter">counter masks</A>.<BR CLEAR=ALL> -->
  184. ?????????????PostScript ???????<A NAME="CounterMasks">????</A>????????????????????????????????????????<IMG SRC="../newcountermask.png" WIDTH="282" HEIGHT="392" ALIGN="Left">
  185. ??????????????????????????????????????????????m????????????????????????????????<A HREF="hinting.html#Counter">???????</A>????????????????<BR CLEAR=ALL>
  186. <P>
  187. <IMG SRC="../charinfo-counters.png" WIDTH="305" HEIGHT="400" ALIGN="Right">
  188. <!--
  189. Some <A NAME="components">glyphs</A> (ligatures, accented glyphs, Hangul
  190. syllables, etc.) are built up out of other glyphs (at least according to
  191. unicode). This pane of the dlg shows the components that Unicode says make
  192. up the current glyph, if those components are in the font then you can use
  193. FontForge's <KBD>Element-&gt;Build-&gt;Build Accented </KBD>or
  194. <KBD>Element-&gt;Build-&gt;Build Composite</KBD> commands to create the current
  195. glyph. The information displayed here is informative only, you may not change
  196. this field directly (it changes when you change the unicode value or glyph
  197. name associated with this glyph).<BR CLEAR=ALL>
  198. -->
  199. ?????<A NAME="components">???</A> (????????????????????????) ???????????????? (????? Unicode ???????)??????????????Unicode ????????????????????????????????????????????????FontForge ? <CODE>?????(<U>L</U>)</CODE>?<CODE>????(<U>U</U>)</CODE>?<CODE>?????????????(<U>B</U>)</CODE> ????? <CODE>?????(<U>L</U>)</CODE>?<CODE>????(<U>U</U>)</CODE>?<CODE>????????(<U>C</U>)</CODE> ???? ????????????????????????????????????????????????????????????????????????? (??????????????????? Unicode ??????????????????????????)?<BR CLEAR=ALL>
  200. <P>
  201. <!--
  202. The Next and Prev buttons allow you to move from one glyph to the next (if,
  203. for example, you need to enter encodings for a range of glyphs). -->
  204. <CODE>[?(<U>N</U>) &gt;]</CODE> ??? <CODE>[&lt; ?(<U>P</U>)]</CODE> ??????????????????????????????? (?????????????????????????????)?
  205. <P>
  206. <!--
  207. The Done (or Cancel) button only Cancels work in the current glyph. If you
  208. have already used Next or Prev then those earlier changes will not be
  209. cancelled.<BR Clear=Right> -->
  210. <CODE>[??(<U>D</U>)]</CODE> (??? <CODE>[?????(<U>C</U>)])</CODE> ??????????????????????????? <CODE>[?(<U>N</U>) &gt;]</CODE> ??? <CODE>[&lt; ?(<U>P</U>)]</CODE> ???????????????????????????????????<BR Clear=Right>
  211. <HR>
  212. <H3>
  213. <!-- <A NAME="Feature-Tag">Feature Tag Dialog</A>-->
  214. <A NAME="Feature-Tag">?????????</A>
  215. </H3>
  216. <TABLE ALIGN=Right>
  217. <TR>
  218. <TD><IMG SRC="../feature-tag-sub.png" WIDTH="226" HEIGHT="399" ALIGN="Top">
  219. <IMG SRC="../feature-tag-pos.png" WIDTH="226" HEIGHT="489" ALIGN="Top"></TD>
  220. </TR>
  221. </TABLE>
  222. <P>
  223. <!--
  224. These two dialogs allow you to specify an otf feature tag and all the other
  225. impedimenta that go along with it. They are used by
  226. <A HREF="charinfo.html#Character">Glyph Info</A> (above) to specify
  227. substitutions, positions, and ligatures, as well as by
  228. <A HREF="fontinfo.html#Anchors">Font Info</A> to specify anchor classes and
  229. contextual features. -->
  230. ???? 2 ??????????OTF ????????????????????????????????????????? (??) <A HREF="charinfo.html#Character">?????</A>?????????????????????????????<A HREF="fontinfo.html#Anchors">??????</A>???????????????????????????????
  231. <P>
  232. <!--
  233. You must either specify an opentype feature tag (a four glyph tag like 'liga'
  234. - - these are defined by
  235. <A HREF="http://partners.adobe.com/public/developer/opentype/index_tag3.html">Microsoft
  236. &amp; Adobe</A>, see the section on <A HREF="gposgsub.html">GPOS and GSUB</A>
  237. for more information), or an apple feature/setting value (Something like
  238. &lt;2,2&gt; where the first number is the feature and the second the setting
  239. for that feature). These features tell the opentype (or ATSUI) engine what
  240. this substitution is supposed to do. -->
  241. ?????OpenType ????? (&lsquo;liga&rsquo;???? 4 ????????????<A HREF="http://partners.adobe.com/public/developer/opentype/index_tag3.html">Microsoft ? Adobe</A>?????????????????????????<A HREF="gposgsub.html">GPOS ? GSUB</A> ??????????????????) ??Apple ???/??? (??? &lt;2,2&gt; ??????????????????????2 ???????????????) ????????????????????????? OpenType (??? ATSUI) ?????????????????????????????
  242. <P>
  243. <!--
  244. <FONT COLOR="Red"><STRONG><BIG>CAVEAT: </BIG></STRONG></FONT>OpenType engines
  245. will only apply features which they believe are appropriate for the current
  246. script (in Latin scripts, Uniscribe will apply 'ccmp' and 'liga' (character
  247. composition/decomposition and ligature) features but will not apply 'medi'
  248. (substitution with a medial glyph variant) features because Latin doesn't
  249. need such a feature -- at least so they claim). Even worse, some applications
  250. may choose not to apply any features ever (Word does not do ligatures in
  251. latin).
  252. <A HREF="http://www.microsoft.com/typography/specs/default.htm">Microsoft
  253. tries to document </A>what features they apply for which scripts in Uniscribe,
  254. but that isn't very helpful since Word and Office have quite different behavior
  255. than the default. -->
  256. <FONT COLOR="Red"><STRONG><BIG>??: </BIG></STRONG></FONT>OpenType ???????????????????????????????????????? (????????Uniscribe ?&lsquo;ccmp&rsquo;???&lsquo;liga&rsquo;(????/???????) ??????????&lsquo;medi&rsquo;(???????????) ????????????????????????????????????????????????????????)???????????????????????????????????????????????? (Word ?????????????????)?
  257. Microsoft ??Uniscribe ???????????????????????<A HREF="http://www.microsoft.com/typography/specs/default.htm">????????????</A>??Word ??? Office ?????????????????????????????????????
  258. <P>
  259. <!--
  260. In <A NAME="lookup-flags">addition</A> you must specify a set of
  261. <A HREF="http://partners.adobe.com/public/developer/opentype/index_table_formats.html">flags</A>
  262. which control the behavior of the feature. If your feature is to be used
  263. in right to left text then select that flag. If your feature is to be used
  264. to combine glyphs even if there are intervening mark glyphs (accents and
  265. such) then select Ignore Combining Marks. If you are creating an Indic font
  266. then you will probably need to create mark classes (with
  267. <A HREF="fontinfo.html#MarkClass">Element-&gt;Font Info-&gt;Mark Classes</A>)
  268. which will be used with the Process Marks option to specify indic rearrangement. -->
  269. ???<A NAME="lookup-flags">???</A>???????????????????<A HREF="http://partners.adobe.com/public/developer/opentype/index_table_formats.html">???</A>?????????????????????????????????????????????????????????????(????????) ??????????????????????????????????????????????????????????????? (<A HREF="fontinfo.html#MarkClass"><CODE>?????(<U>L</U>)</CODE>?<CODE>??????(<U>F</U>)...</CODE>?<CODE>[??????]</CODE></A> ?) ????????????????????????????<CODE>??????</CODE>?????????????????????????????
  270. <P>
  271. <!--
  272. And a collection of scripts and languages for which the substitution will
  273. be active. In the example above the substitution is active for the greek
  274. script and the default language (which here means all languages as none have
  275. been singled out for special treatment), the cyrillic script and the default
  276. language, and the latin script and several languages. -->
  277. ????????????????????????????????????????????????????? (??????????????????????????????????)??????????????????????????????????????????????
  278. <P>
  279. <IMG SRC="../scriptlist-pulldown.png" WIDTH="243" HEIGHT="118">
  280. <P>
  281. <!--
  282. Clicking on the pulldown list produces a list of choices that are currently
  283. used in the font. The last choice allows you to change or add to this list. -->
  284. ????????????????????????????????????????????????????????????????????????
  285. <P>
  286. <!--
  287. Most of the time you will want to specify that your item should be active
  288. in just one script but in all languages of that script. For instance the
  289. "fl" ligature should probably always be applied in the latin script, no matter
  290. what the language is (except Turkish where ligatures should be explicitly
  291. disabled), however there is no point in having it active for cyrillic users
  292. as they will never see that combination of glyphs. On the other hand the
  293. es-zet ligature (German double-s, &szlig;) has fallen by the wayside in all
  294. (I think) languages but German so that ligature should only be active for
  295. the latin script, german language. -->
  296. ?????????????????????????? 1 ?????????????????????????????????????????????fl??????????????????????????????????? (??????????????????????????????????)????????????????????????????????????????????????????????????????????? (??????? s, &szlig;) ?????????????????????? (?????) ??????????????????????????????????
  297. <P>
  298. <!--
  299. And there are some glyphs that don't fall into one single script. The same
  300. digits are used for latin, cyrillic, greek, hebrew, (sometimes arabic) and
  301. many other script systems, so any ligatures of the digits (such as fractions)
  302. should be available in all script systems. -->
  303. ??????????????????????????????????????????????????????? (?????????) ???????????????????????????????? (????) ??????????????????????????
  304. <P>
  305. <!--
  306. The script names used by FontForge are those specified by
  307. <A HREF="http://partners.adobe.com/public/developer/opentype/index_tag1.html">Microsoft
  308. and Adobe for opentype</A>. These are almost compatible with
  309. <A HREF="http://www.evertype.com/standards/iso15924/document/dis15924.pdf">ISO
  310. 15924</A> except that all opentype scripts are in lower case (while those
  311. in ISO 15924 all start with capital letters) and short script names (such
  312. as "Lao") are converted to 'lao ' rather than 'Laoo'. I have extended the
  313. set of opentype scripts with many of those in ISO 15924 by making them all
  314. lower case (I have not used everything from ISO 15924 because it contains
  315. script variants for things which I consider to be one script (eg. fraktur
  316. has a separate script tag, but I consider it to be latin). -->
  317. FontForge?????????????<A HREF="http://partners.adobe.com/public/developer/opentype/index_tag1.html">Microsoft ? Adobe ? OpenType ????</a>????????????? <A HREF="http://www.evertype.com/standards/iso15924/document/dis15924.pdf">ISO 15924</A> ???????????OpenType ????????????????????? (??????ISO 15924 ???????????????) ???????????? (???Lao) ?&lsquo;Laoo&rsquo;????&lsquo;lao &rsquo;??????????????ISO 15924 ???????????????????????OpenType ??????????????????(ISO 15924 ??????? 1 ??????????????????????????????????????????????? (???????????????????????????????????????????????))?
  318. <H3>
  319. <!-- <A NAME="ScriptLang">The Script Language Dialog</A>-->
  320. <A NAME="ScriptLang">???????????</A>
  321. </H3>
  322. <P>
  323. <IMG SRC="../scriptlist.png" WIDTH="296" HEIGHT="205" ALIGN="Left"><!--This dialog
  324. shows all the script and language combinations which are in use in the current
  325. font. You may add a new combination or change an old one by pressing the
  326. obvious buttons. -->
  327. ???????????????????????????????????????????????????????????????????????????????????????
  328. <P>
  329. <!--
  330. If you want to specify a script or language that FontForge doesn't know about,
  331. then hold the control key down when pressing the [New...] or [Edit] buttons
  332. and you will get an unparsed dlg which will allow you to enter whatever you
  333. like (OpenType does not give a tag for the default language (it is has a
  334. special representation which does not involve tags), but for the sake of
  335. consistency I have assigned it the tag of 'dflt'. No 'dflt' tags will appear
  336. in the output font, instead they will be converted to the appropriate
  337. representation for the default language). -->
  338. FontForge ???????????????????????<CODE>[??(<U>N</U>)...]</CODE> ??? <CODE>[??(<U>E</U>)]</CODE> ???????? Control ????????????????????????????????????????(OpenType ???????????????????? (??????????????????????????) ??????????????&lsquo;dflt&rsquo;????????????&lsquo;dflt&rsquo;????????????????????????????????????????????)?
  339. <P>
  340. <!--
  341. The language names used by FontForge are those specified by
  342. <A HREF="http://partners.adobe.com/public/developer/opentype/index_tag2.html">Microsoft
  343. and Adobe for opentype</A>.-->
  344. FontForge ???????????<A HREF="http://partners.adobe.com/public/developer/opentype/index_tag2.html">Microsoft ? Adobe ??? OpenType ????</A>??????????
  345. <P>
  346. <!--
  347. Note: In most cases the order of scripts in the list is irrelevant, but kerning
  348. uses the initial script to determine the direction of the kern pair. So if
  349. you have kerning on the digits, and want those to be active in both latin
  350. and hebrew, you must use the unparsed dlg which allows you to order the scripts
  351. yourself (or add a greek, or cyrillic script to the list (something that
  352. comes before hebrew in alphabetic order and is left to right)).<BR CLEAR=ALL> -->
  353. ??: ??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? (????????????????? (?????????&lsquo;hebrew&rsquo;???????????????????????) ?????????) ????????
  354. <H3>
  355. <!-- <A NAME="Script"><IMG SRC="scriptsdlg.png" WIDTH="152" HEIGHT="215" ALIGN="Right">The
  356. Script Dialog</A> -->
  357. <A NAME="Script"><IMG SRC="../scriptsdlg.png" WIDTH="152" HEIGHT="215" ALIGN="Right">????????</A>
  358. </H3>
  359. <P>
  360. <!--
  361. This dialog shows all the scripts currently activated in this script-language
  362. collection. If you want to add a new script to the collection hold the control
  363. key down while clicking on the script. New scripts are added with the "default"
  364. language selected. If you want finer control over languages (ie. want to
  365. specify a language other than default) then double click on a script and
  366. you will get a dialog of languages. -->
  367. ??????????????-????????????????????????????????????????????????????Control ????????????????????????????????????????????????????????????????????????? (??????????????????????)???????????????????????????????????
  368. <H3>
  369. <IMG SRC="../langdlg.png" WIDTH="152" HEIGHT="215" ALIGN="Left"><!--The
  370. <A NAME="Language">Language</A> Dialog -->
  371. <A NAME="Language">??</A>?????
  372. </H3>
  373. <P>
  374. <!--
  375. This shows all languages active in the current script in the current
  376. script-language collection. Some languages are not meaningful in a given
  377. script (but I don't know enough to know which to remove so I include all
  378. possible languages and apologize for extraneous information). Use the control
  379. key to select multiple languages. At least one language must be
  380. specified.<BR CLEAR=ALL> -->
  381. ??????????/?????????????????????????????????????????????????????????????? (??????????????????????????????????????????????????????????????)????????????? Control ????????????????? 1 ??????????????????<BR CLEAR=ALL>
  382. <P>
  383. <!--
  384. See Also:-->
  385. ??:
  386. <UL>
  387. <LI>
  388. <!-- <A HREF="fontinfo.html">The font info dialog</A>-->
  389. <A HREF="fontinfo.html">???????????</A>
  390. <LI>
  391. <!-- <A HREF="getinfo.html">The get info dialogs</A>-->
  392. <A HREF="getinfo.html">??????????</A>
  393. </UL>
  394. <P ALIGN=Center>
  395. ? <A HREF="elementmenu.html">?</A> ? <A HREF="overview.html">??</A>
  396. ? <A HREF="elementmenu.html">?</A> ?
  397. </DIV>
  398. </BODY></HTML>