PageRenderTime 75ms CodeModel.GetById 34ms RepoModel.GetById 1ms app.codeStats 0ms

/htdocs.OLD/ja/oldchangelog.html

https://bitbucket.org/sortsmill/sortsmill-tools
HTML | 2958 lines | 2385 code | 1 blank | 572 comment | 0 complexity | bdd4f95a66505276fccebb4cfb0669d1 MD5 | raw file
Possible License(s): GPL-3.0, LGPL-2.0

Large files files are truncated, but you can click here to view the full file

  1. <HTML>
  2. <HEAD>
  3. <!-- Created with AOLpress/2.0 -->
  4. <!-- AP: Created on: 16-Sep-2001 -->
  5. <!-- AP: Last modified: 15-Jul-2006 -->
  6. <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=Shift_JIS">
  7. <!--<TITLE>Older changes to FontForge</TITLE> -->
  8. <TITLE>FontForge ????????</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. <P>
  15. <!--
  16. <A HREF="changelog.html">Current changes</A><BR> -->
  17. <A HREF="changelog.html">??????</A><BR>
  18. <!--
  19. <A HREF="pfaeditchangelog.html">Changes to PfaEdit (predecessor to
  20. FontForge)</A> -->
  21. <A HREF="pfaeditchangelog.html">PfaEdit (FontForge ????) ????</A>
  22. <UL>
  23. <LI>
  24. <!-- 31-August-2005-->
  25. 2005?8?31?
  26. <UL>
  27. <LI>
  28. <!-- The mac fix for 25-Aug wasn't quite enough. -->
  29. 8/25 ? Mac ?????????????????
  30. <LI>
  31. <!-- I used to maintain a hidden value of the os2 linegap. This didn't change
  32. when users set linegap with font info, leaving users annoyed. -->
  33. ????OS/2 ? linegap ??????????????????????????????????????? linegap ????????????????????????????????
  34. <LI>
  35. <!-- It used to be that both the Hint-&gt;Add Hint and Hint-&gt;Create Hint commands
  36. would destroy all hint masks. Now we update those hint masks appropriately. -->
  37. ???????????????????????????????????????????????????????????????????????????????
  38. <LI>
  39. <!-- The "Original" encoding was broken, and reencoding to it gaves us 256 blank
  40. glyphs before glyph0. Sigh. -->
  41. ???????????????????????????????????????????????? 0 ??? 256 ?????????????????????
  42. <LI>
  43. <!-- The CodeRange bit for symbol doesn't mean the font contains any standard
  44. set of "symbol" glyphs, but rather either that it has a 3,0 cmap sub-table,
  45. or that there are glyphs mapped to 0xf000-0xf0ff in the 3,1 (unicode) sub-table. -->
  46. CodeRange ???? symbol ??????????? "Symbol" ????????????????????????????????3,0 cmap ???????????????3?1 (Unicode) ??????? 0xf000-0xf0ff ????????????????????????
  47. <P>
  48. <!-- Setting this bit should give you a symbol encoding as well as all the other
  49. encodings you've set bits for. It doesn't work under windows. It doesn't
  50. work. TrueType fonts do not provide a symbol encoding, while 'CFF ' fonts
  51. only provide a symbol encoding. But hey, let's support it anyway! -->
  52. ???????????????????????????????????? Symbol ????????????????????????? Windows ????????????????TrueType ????? Symbol ??????????????Symbol ????????????????? 'CFF ' ???????????????????????????????!
  53. <P>
  54. <!-- change View-&gt;Goto to know about this range as MS Symbol. -->
  55. ???????? MS Symbol ???????????????
  56. <LI>
  57. <!-- Importing an eps file (or pasting the x clipboard) made use of an uninitialized
  58. variable. (introduced 7-Aug) -->
  59. EPS ????????? (??? X ????????????) ???????????????? (8/7 ??)?
  60. <LI>
  61. <!-- Cleanup pasting references from one font to another (gave some very strange
  62. results when pasting refs with no unicode encodings). -->
  63. ????????????????????? (??? Unicode ??????????????????????????????)?
  64. </UL>
  65. <LI>
  66. <!-- 25-August-2005-->
  67. 2005?8?25?
  68. <UL>
  69. <LI>
  70. <!-- Recode the mac resource fork routines so that they no longer use the FSSpec
  71. structure. 10.4 complains about it. -->
  72. Mac ???????????????????FSSpec ??????????????????????? 10.4 ??????????
  73. <LI>
  74. <!-- Bug in mm font charstring generation. -->
  75. ?????????????? charstring ????????
  76. <LI>
  77. <!-- If a font contained mac feature setting names, then when ff generated it,
  78. ff would produce duplicate entries in the 'name' table for these guys. One
  79. for the name in the font itself, and one for the name ff thought that feature
  80. setting should have. -->
  81. Mac ????????????????FF ??????????? 'name' ???????????????????????1 ????????????????????? 1 ?? ff ?????????????????????
  82. <LI>
  83. <!-- Nobody else puts apple unicode names into the 'name' table so I probably
  84. should not either. Adobe says one should not. Apple's website implies one
  85. should - - but Apple doesn't and its ttf website is not very accurate. -->
  86. Apple Unicode ? 'name' ????????????????????????????????????????Adobe ??????????????????Apple ? Web ??????????????????????????????????????Apple ? TTF ???? Web ???????????????
  87. <LI>
  88. <!-- When ff generated a ttf/otf font with applemode set and opentype off then
  89. the font would have version 'true'. Which means windows would reject it.
  90. That's probably not a good idea given that this situation is default on the
  91. mac - - even if we don't have a GSUB/GPOS table we should at least let the
  92. glyphs show on windows. -->
  93. ff ? TTF/OTF ? Apple ???????OpenType ??????????????????????????? 'true' ????????????Windows ????????????????? Mac ????????????????????????????GSUB/GPOS ??????????????????????????????????????????
  94. <P>
  95. <!-- On the other hand some people might want to make fonts that only work on
  96. macs. So add a configure flag. -->
  97. ?????Mac ????????????????????????????????????? configure ????????????
  98. <LI>
  99. <!-- ff couldn't undo changing the lig carets (if it weren't compiled for multilayer) -->
  100. FF ??????????????????? (?????????????????????)?
  101. <LI>
  102. <!-- Copying a pairwise positioning left memory in a bad state. -->
  103. ?????????????????????????????????????
  104. <LI>
  105. <!-- Coalesce all lookups with the same feature &amp; script lang. This makes
  106. ATM happy about kerning on windows. -->
  107. ???????????????????????????????????Windows ???????????? ATM ??????????????
  108. <LI>
  109. <!-- When rasterizing a multilayer font we would sometimes get warnings from the
  110. stroker about how the stroke self-intersected. Get rid of those warnings. -->
  111. ????????????????????????????????????????????????????????????????????????????????????
  112. <LI>
  113. <!-- Pasting from a multilayered font into a normal one crashed -->
  114. ?????????????????????????????????????
  115. <LI>
  116. <!-- If an order2 font were turned into a PS font, then characters with hint conflicts
  117. got no hints. -->
  118. 2 ?????? PS ?????????????????????????????????????
  119. <LI>
  120. <!-- Makers of fonts on the mac often use out of bound GIDs as flags in contextual
  121. su bstitutions. What I have seen is that one sub-table will insert such a
  122. "glyph" w hen a match is found, and then the next sub table will remove the
  123. flag, and perf orm subsequent transformations. This is important on the mac
  124. because there is a limited number of substitutions that can happen once a
  125. match is found, but if a match is found at the start (ie. the match being
  126. some magic marker glyph) then u nlimited substitutions are available. When
  127. ff first stumbled on these fonts it crashed, then it treated a gid&gt;glyph_cn
  128. t as an error (and so it ignored the substitution). I've just put in code
  129. that c reates dummy glyphs for all these bizarre GIDs so (I hope) the font
  130. will work af ter passing through ff (only there will be some real blank glyphs
  131. at the end of the font rather than vaper-ware glyphs). -->
  132. Mac ?????????????????????????????????? GID ?????????????????????????????????????????????????????????????????????????????????????Mac ????? 1 ??????????????????????????????????????????? (????????????????????????????) ??????????????????????????????????FF ??????????????????????????????????????? gid&gt;glyph_cnt ???????????????? (??????????????)????????? GID ?????????????????????ff ???????????????????????? (????????????????????????????????????????????????)?
  133. <LI>
  134. <!-- The Active Hints pane (of Point Info) didn't always work if a glyph had more
  135. than one contour. -->
  136. [??????] ?? (???????????? 1 ????????????????????????
  137. <LI>
  138. <!-- Be more canny in the use of subroutines for references in type1/2 output. -->
  139. Type1/Type2 ???????????????????????????????
  140. <LI>
  141. <!-- When generating contextual lookups, ff did not set the lookup count between
  142. gpos and gsub. So if a font had both contextual gpos &amp; gsub elements
  143. ff got confused. -->
  144. ???????????????ff ? GPOS ? GSUB ?????????????????????????????????????????? GPOS ? GSUB ?????????????FF ??????????
  145. <LI>
  146. <!-- The code for cff encodings (ie. in bare cff non-cid fonts) didn't handle
  147. multiply encoded glyphs -->
  148. CFF ??? (?????? CFF ? CID ??????) ????????????????????????????
  149. <LI>
  150. <!-- Change the default color of the prev control point (so it's easier for me
  151. to see) -->
  152. ???????????????? (?????????????????)?
  153. </UL>
  154. <LI>
  155. <!-- 11-August-2005-->
  156. 2005?8?11?
  157. <UL>
  158. <LI>
  159. <!-- The configure script did not find libfreetype when it lived (solely) in
  160. /usr/X11R6/libs -->
  161. /usr/X11R6/libs ??? libfreetype ??????configure ??????????????????
  162. <LI>
  163. <!-- On the Mac, menus incorrectly suggested using Cmd rather than Ctl. (Cmd used
  164. to work on earlier versions of the X server, but now it is snagged by the
  165. X11 menubar itself.) -->
  166. Mac ??????????? Ctl ???? Cmd ????????? (Cmd ?????? X ????????????????????? X11 ??????????????????????)?
  167. <LI>
  168. <!-- ff uses the Alt/Meta key to alter the behavior of some tools (magnify, ruler,
  169. pointer, pencil, etc.) in the editing windows. This doesn't work well on
  170. the mac. First there is no real Alt/Meta key. If we contemplate using Option
  171. or Command it will generally already be used to turn the single button mouse
  172. into a three button mouse (Option - mouse =&gt; button 2, Command - mouse
  173. =&gt; button 3). So instead use the CapsLock key. -->
  174. FF ??????????????? (????????????????) ?????????????? Alt/Meta ???????????? Mac ?????????????????????? Alt/Meta ?????????Option ??? Command ??????????????????1 ??????? 3 ???????????????????????? (Option-???????2, Command-???????3)???????? CapsLock ?????????
  175. </UL>
  176. <LI>
  177. <!-- 9-August-2005-->
  178. 2005?8?9?
  179. <UL>
  180. <LI>
  181. <!-- The big5 encoding stopped at 64000, which confused routines which expected
  182. unencoded glyphs to start at 65536. -->
  183. Big5 ????????? 64000 ???????????????????????? 65536 ??????????????????????????????
  184. <LI>
  185. <!-- We would crash when reencoding a font with enough unencoded alternate unicode
  186. code points. -->
  187. ??????????? Unicode ??????????????????????????????????????????????
  188. <LI>
  189. <!-- The code for creating an 8/16 cmap subtable didn't work. -->
  190. 8/16 cmap ??????????????????????????
  191. <LI>
  192. <!-- ff would crash if it had two windows open on the same font and one got reencoded -->
  193. ??????????????????????????????????????????????????
  194. <LI>
  195. <!-- Didn't set the length of the format4 'cmap' sub-table, so the offset to the
  196. format12 (32bit unicode) table was wrong. -->
  197. ?????? 4 'cmap' ???????????????????????????? 12 (32 ??? Unicode) ?????????????????????
  198. <LI>
  199. <!-- ttfcopyfile can complain about a ttf table offset being wrong. Give it the
  200. info so that it will now tell us which table has the wrong offset. -->
  201. ttfcopyfile ??TTF ????????????????????????????????????????????????????????????????????????
  202. <LI>
  203. <!-- Uninitialized variable in metricsview when creating a popup window. -->
  204. ????????????????????????????????
  205. <LI>
  206. <!-- Redo the ttfnames pane of the font info dlg. Now show the names as an editable
  207. list. -->
  208. ???????????? [TTF ?] ??????????????????????????????????
  209. <LI>
  210. <!-- Histogram dlg still used wrong encodings for selected glyphs when historgrams
  211. invoked from Hints menu. -->
  212. ??????????????????????????????????????????????????????????????
  213. </UL>
  214. <LI>
  215. <!-- 7-August-2005-->
  216. 2005?8?7?
  217. <UL>
  218. <LI>
  219. <!-- SelectIf failed when passed an encoding which was out of bounds -->
  220. SelectIf() ???????????????????????????
  221. <LI>
  222. <!-- Added a new scripting command: ToString -->
  223. ???????????? ToString() ????
  224. <LI>
  225. <!-- Using the X clipboard to paste a glyph into a glyph that contained stuff
  226. caused a crash. -->
  227. X ??????????????????????????????????????????????????????????
  228. <LI>
  229. <!-- Using the X clipboard to paste a glyph with references or with multilayer
  230. did no t work. -->
  231. X ??????????????????????????????????????????????????????????????????
  232. <LI>
  233. <!-- None of ttf, otf nor svg got multiply encoded glyphs output properly. -->
  234. TTF, OTF, SVG ??????????????????????????????????
  235. <LI>
  236. <!-- FF screwed up memory when creating ligatures from an svg font. -->
  237. SVG ?????????????????????????????
  238. <LI>
  239. <!-- Merge fonts was writing to bad memory. -->
  240. ??????????????????????????
  241. <LI>
  242. <!-- FF was confused by a strange MM font -->
  243. FF ?????? MM ?????????????????
  244. <LI>
  245. <!-- FindExistingSlot should understand altuni. -->
  246. FindExistingSlot() ? altuni ??????????
  247. <LI>
  248. <!-- Font View didn't display current unicode of multiply encoded glyphs. (same
  249. for popups). -->
  250. ????????????????????????? Unicode ???????????? (?????????)?
  251. <LI>
  252. <!-- Still having problems generating type1 code for complicated reference glyphs. -->
  253. ????????? Type1 ?????????????????
  254. <LI>
  255. <!-- Retain knowlege of multiple unicode encodings for some glyphs. Used when
  256. a glyph has multiple encodings and is reencoded. -->
  257. ???????? Unicode ?????????????????????????????????????????????????????
  258. <LI>
  259. <!-- Add back an option to compact an encoding. It's not the same as the old compact
  260. which kept track of the former encoding. This just compacts, user must explicitly
  261. reencode. -->
  262. ?????????????????????????????????????????????????????????????????????????????????????????????????????????????
  263. <LI>
  264. <!-- Force encoding didn't work if the new encoding had more slots than the old. -->
  265. ?????????????????????????????????????????????????????
  266. <LI>
  267. <!-- FF also failed to parse glyph based contextual lookups properly -->
  268. FF ?????????????????????????????????
  269. </UL>
  270. <LI>
  271. <!-- 3-August-2005-->
  272. 2005?8?3?
  273. <UL>
  274. <LI>
  275. <!-- FF failed to parse class based contextual lookups properly (contextual chaining
  276. lookups were ok) -->
  277. FF ??????????????????????????????? (?????????????)
  278. </UL>
  279. <LI>
  280. <!-- 2-August-2005-->
  281. 2005?8?2?
  282. <UL>
  283. <LI>
  284. <!-- <FONT COLOR="Red"><STRONG><BIG>The OS/2 ulCodeRanges field has been broken
  285. for a long time, and has failed to mark the presence of any latin code
  286. pages.</BIG></STRONG></FONT> -->
  287. <FONT COLOR="Red"><STRONG><BIG>OS/2 ? ulCodeRanges ??????????????????????????????????????????????</BIG></STRONG></FONT>
  288. <LI>
  289. <!-- The ulCodeRanges field never set Vietnamese, TradChinese, Mac nor PC OEM -->
  290. ulCodeRange ??????????????Mac ??? PC OEM ????????????????????????????
  291. <LI>
  292. <!-- FF did not support EUC-CN, ISO-2022-CN, ISO=2022-KR iconv encodings properly. -->
  293. FF ? iconv ? EUC-CN, ISO-2022-CN, ISO-2022-KR ?????????????????????????
  294. <LI>
  295. <!-- Work around a bug in iconv's support for CP1258 -->
  296. iconv ? CP1258 ???????????
  297. <LI>
  298. <!-- Put some code in to warn users about unknown language/locales in the ttf
  299. 'name' table. -->
  300. TTF ? 'name' ???????????????/??????????????????
  301. <LI>
  302. <!-- Enter some new language/locale codes for ms. -->
  303. ??? MS ???/???????????????
  304. <LI>
  305. <!-- Crash when moving the end of an open path in an order2 font. -->
  306. 2 ????????????????????????????????????
  307. <LI>
  308. <!-- If one loaded an encoding specified by codepoint and then cancelled the dlg
  309. which asked for a name for that encoding, then ff would crash. -->
  310. ?????????????????????????????????????????????????????????ff ????????????????
  311. <LI>
  312. <!-- Don't use Adobe's glyphnames when they are obviously wrong (use uni???? instead) -->
  313. ????????????????? Adobe ??????????? (???? uni???? ???)
  314. <LI>
  315. <!-- Add (better) support for the new dotlessj -->
  316. ??? dotlessj ? (????) ????????
  317. <LI>
  318. <!-- Put a check into the context chain dlg to make sure that people don't add
  319. sequence/lookup pairs where the sequence number is too big. -->
  320. ?????????????????????????????????/??????????????????????????
  321. <LI>
  322. <!-- Make class be the default format for contextual/chaining substitutions rather
  323. than coverage tables. -->
  324. ?????????????????/????????????????????????????????
  325. <LI>
  326. <!-- <FONT COLOR="Red"><STRONG><BIG>The format of the LineBreak.txt file changed
  327. with Unicode 4.1, so all the line break info is wrong (essentially lines
  328. never broke in text fields).</BIG></STRONG></FONT> -->
  329. <FONT COLOR="Red"><STRONG><BIG>LineBreak.txt ???????????? Unicode 4.1 ?????????????????????????? (???????????????????????????????)?</BIG></STRONG></FONT>
  330. <LI>
  331. <!-- Reference to bad memory when creating a popup in combinations list. -->
  332. ?????????????????????????????????????
  333. <LI>
  334. <!-- Still problems in the 'name' table when Mac &amp; Mac Unicode strings don't
  335. match. -->
  336. 'name' ???????Mac ? Mac Unicode ????????????????????????
  337. <LI>
  338. <!-- Use of the X clipboard for transfering glyphs resulted in a crash -->
  339. ???????????? X ?????????????????????????
  340. <LI>
  341. <!-- When generating an old-style 'kern' table (either OpenType nor Apple modes
  342. set) decompose all kerning classes into kern pairs as we do for AFM files. -->
  343. ?????? 'kern' ????? (OpenType ????Apple ??????????????) ??????AFM ????????????????????????????????????????????
  344. <LI>
  345. <!-- Scripting didn't have a way to generate a font with neither Apple nor OpenType
  346. tables. Add one. -->
  347. ??????????Apple ? OpenType ?????????????????????????????????
  348. <LI>
  349. <!-- Oops. wrong default extension for otb fonts from scripts. -->
  350. ?????????? OTB ???????????????????????????????
  351. <LI>
  352. <!-- Fix some potential crashes where loading font types left a new field unset. -->
  353. ???????????????????????????????????????????????????????????????
  354. </UL>
  355. <LI>
  356. <!-- 28-July-2005-->
  357. 2005?7?28?
  358. <UL>
  359. <LI>
  360. <!-- <FONT COLOR="Red"><STRONG><BIG>Redesigned the way encodings are handled.
  361. From the user's perspective Encodings are no longer controlled by FontInfo,
  362. but via an encoding menu.</BIG></STRONG></FONT> -->
  363. <FONT COLOR="Red"><STRONG><BIG>??????????????????????????????????????????????????????????????????????????????????????</BIG></STRONG></FONT>
  364. <LI>
  365. <!-- If we create a bitmap strike in an empty font then change the fontview to
  366. look at the strike. -->
  367. ?????????????????????????????????????????????????
  368. <LI>
  369. <!-- The SetWidth command of FontView produced garbage defaults for empty fonts -->
  370. ??????????????? SetWidth() ??????????????????????????
  371. <LI>
  372. <!-- Don't set the hinting needed bit on: bitmap only fonts, multilayered fonts,
  373. stroked fonts nor quadratic fonts. -->
  374. ??????????????????????????????????? 2 ?????????????????????????????????
  375. <LI>
  376. <!-- Fix some problems with the generated names in File-&gt;Generate multiple -->
  377. ??????????????????????????????????
  378. <LI>
  379. <!-- The Save command failed to reset the font window's title (so it still looked
  380. modified) -->
  381. ????????????????????????????????????? (????????????????)?
  382. <LI>
  383. <!-- The enabled state of Encoding-&gt;Detach Glyphs was wrong -->
  384. ?????????????????????????????????????
  385. <LI>
  386. <!-- FF still didn't allow two ligatures to be created for the same glyph (ie.
  387. it complained if you tried to make both "f + f + i =&gt; ffi" and "ff + i
  388. =&gt; ffi" -->
  389. FF ??????????? 2 ????????????????????????? (????"f + f + i ? ffi" ? "ff + i ? ffi" ?????????????????????)?
  390. <LI>
  391. <!-- Added a TypeOf command to scripting -->
  392. ?????? TypeOf() ????????
  393. <LI>
  394. <!-- Added a GetPosSub command to scripting. -->
  395. ?????? GetPosSub() ????????
  396. <LI>
  397. <!-- Werner says negative widths and depths be set to 0 in tfm files. -->
  398. ????????? TFM ?????? 0 ??????? Werner ????????
  399. <LI>
  400. <!-- FontForge was generating an incorrect warning message. If a 'name' table
  401. contains a duplicate entry for a given platform/specific/language/id that's
  402. an error in the font. But ff conflated mac names with window names and so
  403. was only checking language/id. So if the mac windows names were different
  404. (which is probably a bad design idea, but not an error) ff said it was wrong.
  405. It can also be caused by using a character in the string which is not in
  406. the Mac Encoding for that language. -->
  407. FontForge ?????????????????????????????????????/??/??/???ID ? 'name' ?????????????????????????????????????? ff ? Mac ????? Windows ????????????????/ID ? 2 ??????????????????????Mac ? Windows ?????????????? (?????????????????????????????) ff ????????????????????????????? Mac ???????????????????????????????????????????????????????
  408. <LI>
  409. <!-- Don't set "Hinting needed" flag in bitmap only fonts. -->
  410. ????????????????????????????????????????
  411. <LI>
  412. <!-- AutoHint had a crash if there were open contours in a glyph being hinted. -->
  413. ?????????????????????????????????????????????????
  414. <LI>
  415. <!-- Add a couple of browsers to the list to check by default. -->
  416. ????????????????????? 2 ?????
  417. <LI>
  418. <!-- Using the kerning pair closeup dlg to create a new kerning pair caused a
  419. crash (eventually). -->
  420. ???????????????????????????????????? (????) ????????????
  421. <LI>
  422. <!-- When saving a block of ttf bitmap glyphs all with about the same metrics, -->
  423. TTF ????????????????????????????????????????
  424. <LI>
  425. <!-- Kern pairs were not scaled to emsize when loading from an afm file. -->
  426. AFM ???????????????????? EM ????????????????????
  427. <LI>
  428. <!-- Add a series of new selection commands, to the font view and to scripting: -->
  429. ???????????????????????????????
  430. <UL>
  431. <LI>
  432. SelectChangedGlyphs
  433. <LI>
  434. SelectHintingNeeded
  435. </UL>
  436. <P>
  437. <!-- (just to scripting) -->
  438. (???????)
  439. <UL>
  440. <LI>
  441. SelectSingletons
  442. <LI>
  443. SelectMoreSingletons
  444. <LI>
  445. SelectFewerSingletons
  446. </UL>
  447. <LI>
  448. <!-- Revert Glyph didn't work. One bug caused by multilayer, one caused by encoding
  449. changes, and one really old one. -->
  450. ?????????????????????????????????????? 1 ??????????????????? 1 ??????? 1 ???????????????
  451. <LI>
  452. <!-- GetFontNames returned an uninitialized value on bad ttf files. -->
  453. GetFontNames() ????? TTF ???????????????????????????
  454. <LI>
  455. <!-- Add some new scripting commands to access the TeX per-glyph fields. -->
  456. TeX ??????????????????????????????????????????
  457. <LI>
  458. <!-- Werner suggested some improvements to tfm output. -->
  459. Werner ??????? TFM ?????????????
  460. <LI>
  461. <!-- Cleanup behavior of generating ttf bitmaps in a script. -->
  462. TTF ??????????????????????????????
  463. <LI>
  464. <!-- I was attaching script/langs to lookups when parsing GPOS/GSUB. That wasn't
  465. good enough. Each sub-table and have it's own set, so attach script/langs
  466. to subtables as well. Still a flaw in that sub-tables could be referenced
  467. through severel extension sub-tables or directly and I don't unravel that
  468. complexity until too late. -->
  469. GPOS/GSUB ?????????/??????????????????????????????????????????????????????????????????????????/????????????????????????????????????????????????????????????????????????????????????????????????????
  470. <LI>
  471. <!-- ATM which handles some kerning for otf fonts for Word, does not handle 'kern'
  472. features where the feature contains more than one lookup. So whenever we
  473. have a feature with multiple lookups try to compress them into one lookup
  474. with multiple sub-tables. -->
  475. Word ???? OTF ??????????????????? ATM ??'kern' ??? 2 ????????????????????????????????????????????????????????????????????? 1 ????????????????????????
  476. <LI>
  477. <!-- Transform (in fontview) and Scale To Em do not scale the vertical advance. -->
  478. (?????????)??????????????????????????????????????????????
  479. <LI>
  480. <!-- We didn't test the right thing when deciding where a subroutine containing
  481. refs began. -->
  482. ??????????????????????????????????????????????
  483. <LI>
  484. <!-- Remove Undoes was broken by the encoding changes. -->
  485. ???????????????????????????(N)??????????????
  486. <LI>
  487. <!-- When saving multiple, make sure we don't get extraneous kerns. (to glyphs
  488. not in the current sub-font). -->
  489. ?????????????(??????????????????????) ???????????????????????
  490. <LI>
  491. <!-- Make sure the blue lines (marking hints needing to be updated) get cleared
  492. properly. -->
  493. (?????????????????) ???????????????????????
  494. <LI>
  495. <!-- Some display problems in the SameGlyphAs command. -->
  496. SameGlyphAs() ????????????????
  497. <LI>
  498. <!-- The Apply Substitutions code did not consider the possibility of loops:<BR>
  499. a-&gt;b-&gt;c-&gt;d-&gt;a -->
  500. ???????????? a?b?c?d?a ???????????????????????
  501. <LI>
  502. <!-- Werner suggests indicating multi-layer in the version string. -->
  503. ????????????????????????? Werner ????????
  504. <LI>
  505. <!-- Mark to Mark anchor classes should allow each mark glyph also to contain
  506. a base mark entry. -->
  507. ?????????????????????????????????????????????????????
  508. <LI>
  509. <!-- Give unicode name data (in grey) for dotted names. (ie for A.super give unicode
  510. name data for "A", but in grey so it stands out as modified). -->
  511. ?????????????? Unicode ?????? (???) ???(????A.super ? Unicode ? "A" ????????????????????????????)
  512. <LI>
  513. <!-- Add scripting routines to detach glyphs from the encoding and to remove them
  514. from the font. -->
  515. ?????????????????????????????????????????????????????
  516. <LI>
  517. <!-- FF produced some very strange 'gasp' tables... depending on the bitmap fonts
  518. in the sfd and not on the bitmaps in the output ttf for one thing. -->
  519. FF ????????? 'gasp' ????????????? SFD ???????????? ????????????? TTF ?????????????????????
  520. <LI>
  521. <!-- Werner wants an Invert Selection command. -->
  522. Werner ??[???????] ??????????????
  523. <LI>
  524. <!-- The position of Coptic and Glagolithic has been shifted in Unicode 4.1 (shifted
  525. from some earlier proposal). -->
  526. ???????????????? Unicode 4.1 ????????? (??????????????????????????)?
  527. <LI>
  528. <!-- Patch by KANOU, ttc files were broken. -->
  529. ?????????TTC ?????????????
  530. <LI>
  531. <!-- Some english language strings in the ttfnames pane of fontinfo where sort
  532. of bound to equivalent fields in the names pane. Make this clearer, and
  533. consistent. -->
  534. ???????????? [TTF ?] ????????????????[??] ??????????????????????????????????????????????????
  535. <LI>
  536. <!-- Werner thinks my error messages for scripts should be improved. -->
  537. Werner ?????????????????????????
  538. <LI>
  539. <!-- Add a check in case sfd files contain unreasonable values for pixelsize,
  540. etc. -->
  541. SFD ????????????????????????????????????????
  542. <LI>
  543. <!-- Werner suggests a -- dry &lt;scriptfile&gt; argument which does syntax checking
  544. without actually executing the script. I think it is trivial. -->
  545. ?????????????????????? --dry &lt;?????????&gt; ???????? Werner ???????????????????????
  546. <LI>
  547. <!-- Werner points out that the DSC Version comment has a very specific syntax:<BR>
  548. %%Version: &lt;version&gt; &lt;revision&gt;<BR>
  549. &lt;version&gt; is a real, &lt;revision&gt; is a uint. So we can't use the
  550. font's version string here (which might be anything). Instead we now generate
  551. a version comment<BR>
  552. %Version: &lt;string&gt;<BR>
  553. rather than a DSC Comment. -->
  554. Werner ????????DSC ????????????????????:
  555. %%Version: &lt;version&gt; &lt;revision&gt;<BR>
  556. &lt;version&gt; ????, &lt;revision&gt; ???????????????? (??????????) ?????????????????????DSC ???????????????????<BR>
  557. %Version: &lt;string&gt;<BR>
  558. ?????????????
  559. <LI>
  560. <!-- We used to assign a unicode value to ".notdef"s when reading ps encoding
  561. file, if the encoding was in the region of control chars (so location 1 would
  562. get uni0001, while location 65 would get -1). Seems inconsistent. -->
  563. PS ??????????????????????????????????????????????? Unicode ? ".notdef" ?????????? (???????? 1 ? uni0001 ?????????? 65 ? -1 ?????)???????????????
  564. <LI>
  565. <!-- Oops. I failed to provide a mechanism to add other iconv encoding names into
  566. my menu. -->
  567. ?????????????????????????????????????????????
  568. <LI>
  569. <!-- Code to support group display. -->
  570. ????????????????????
  571. <LI>
  572. <!-- Was not reading ps encoding files properly. -->
  573. PS ?????????????????????????????
  574. <LI>
  575. <!-- Remove encoding should always be available. -->
  576. ????????????????????????????
  577. </UL>
  578. <LI>
  579. <!-- 19-July-2005-->
  580. 2005?7?19?
  581. <UL>
  582. <LI>
  583. <!-- Extend to Unicode 4.1 -->
  584. Unicode 4.1 ????
  585. <LI>
  586. <!-- Change to configuration system to allow relative pathspecs for
  587. --with-freetype-src didn't work. -->
  588. configure ????????? --with-freetype-src ?????????????????????????????????
  589. <LI>
  590. <!-- Context chain dlg had problems with empty patterns (no terminal NUL in empty
  591. string used to represent them) -->
  592. ?????????????????????????????? (????????????? NUL ????????????)
  593. <LI>
  594. <!-- The [EditData] button in contextual fontinfo pane was disabled due to reasons
  595. which are no longer valid.. -->
  596. ?????????????? [??????] ??????????????????????????????????
  597. <LI>
  598. <!-- Transforming by a negative scale factor screwed up the hints. -->
  599. ??????????????????????????
  600. <LI>
  601. <!-- Add move up/down buttons to the kerning class dlg (class lists area) Use
  602. the selection from the class lists to highlight offsets. -->
  603. ????????????? (?????????) ??/???????????????????????????????????????????????????????
  604. <LI>
  605. <!-- Print sample did not handle kerning by classes. -->
  606. ??????????????????????????????????????
  607. <LI>
  608. <!-- When we had: a glyph which contained refs where that glyph was itself used
  609. as a reference in another glyph and all glyphs (except the last) lived in
  610. subroutines then we got multiple declarations of hints and the middle glyph
  611. was translated from where it should have been. -->
  612. ?????????????????????????????????????????????????????????????????? (??????????) ???????????????????????????????????????????????????
  613. <LI>
  614. <!-- When changing lists they should not scroll back to the beginning. -->
  615. ???????????????????????????????????
  616. <LI>
  617. <!-- Various fixes regarding hints: changing hints should set the char changed
  618. flag changing a glyph should mark all glyphs that refer to it as having out
  619. of date hints display out of date hints in font view. hints weren't being
  620. preserved (and should have been) in charview in Paste and transform. -->
  621. ????????????: ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
  622. <LI>
  623. <!-- Apply Substitutions was badly broken when ff compiled with multilayer. -->
  624. ff ??????????????????????????????????????????
  625. <LI>
  626. <!-- Kern Pair dlg looked at garbage memory when it closed (and crashed sometimes). -->
  627. ???????????????????????????????????? (??????????????????)?
  628. <LI>
  629. <!-- ff decides whether to add a 'gasp' table to a font based on whether the font
  630. has instructions or not. ff's own ttf fonts contain instructions in .notdef
  631. but nowhere else, so ignore .notdef when making this check. -->
  632. ff ???????????????????????? 'gasp' ?????????????????????????ff ???? TTF ????? .notdef ?????????????????????????????????????? .notdef ?????????????
  633. <LI>
  634. <!-- One more attempt to rule out absurd results in simplify(). -->
  635. simplify() ??????????????????????? 1 ????????
  636. <LI>
  637. <!-- if the lsb/rsb dlg was given a negative value it complained about negative
  638. widths. (whether the width would have been negative or not). -->
  639. ?????????????????????????(???????????????????) ???????????????????????????
  640. <LI>
  641. <!-- $italicangle has been broken since I added reals to scripting. -->
  642. $italicangle ??????????????????????????
  643. <LI>
  644. <!-- The kernclass dialog did not handle deleted classes properly. -->
  645. ??????????????????????????????????????
  646. <LI>
  647. <!-- Add ability to undo hints. -->
  648. ??????????????
  649. <LI>
  650. <!-- Once again starting a browser on windows is broken. -->
  651. ?????Windows ?????????????????
  652. <LI>
  653. <!-- We didn't do a bounds check when indexing into the names array of an encoding
  654. (when building a character from scratch). If the index was huge the result
  655. was garbage, generally leading to a crash sometime thereafter. -->
  656. ????????? names ????????????????(?????????????????) ??????????????????????????????????????????????????????????????????????????
  657. <LI>
  658. <!-- An open path consisting of a single point caused replace with reference to
  659. crash. -->
  660. 1 ?????????????????????????????????????????????????
  661. <LI>
  662. <!-- Generating a postscript resource font on the mac from a script did not work. -->
  663. Mac ??????????? PostScript ??????????????????????????
  664. <LI>
  665. <!-- Werner points out that afm files generated by FontForge still claim to have
  666. been made by pfaedit. Oops. -->
  667. Werner ??FontForge ????? AFM ????????PfaEdit ???????????????????????????
  668. <LI>
  669. <!-- Didn't parse user defined encodings properly and often omitted the first
  670. glyph. -->
  671. ??????????????????????????????????????????????
  672. </UL>
  673. <LI>
  674. <!-- 24-June-2005-->
  675. 2005?6?24?
  676. <UL>
  677. <LI>
  678. <!-- Improvements in the way type42 fonts where handled in printing. -->
  679. ???? Type42 ???????????
  680. <LI>
  681. <!-- Fix a crash when parsing mangled cff files -->
  682. ??? CFF ?????????????????????
  683. <LI>
  684. <!-- Marvelous triple bug: -->
  685. ???????:
  686. <UL>
  687. <LI>
  688. <!-- Adobe's Tech Note 5176 (cff format) says that a private dict is required.
  689. They mean it's required in a type1 font. -->
  690. Adobe ? Tech Note 5176 (CFF ??????) ???????????????????????Type1 ??????????????????
  691. <LI>
  692. <!-- Because of this I put a null private dict entry into my cid cff fonts. -->
  693. ????????CID CFF ?????????? 1 ???????????????????????
  694. <LI>
  695. <!-- ghostview finds the null private dict entry and tries to read data from it
  696. even though it is of 0 length. -->
  697. ghostview ?????????????????????????? 0 ???????????????????
  698. </UL>
  699. <LI>
  700. <!-- Add postscript code necessary for loading a cff font to my cff font output. -->
  701. CFF ????????????? PostScripto ??????????? CFF ????????
  702. <LI>
  703. <!-- Fix some uninitialized variables in the display dlg. -->
  704. ??????????????????????
  705. <LI>
  706. <!-- We didn't get DSC pages properly when printing a CID keyed font. -->
  707. CID ????????????DSC ???????????????????
  708. <LI>
  709. <!-- The default (notdef) glyph generated by my palm output routines was a little
  710. wonky. -->
  711. Palm ?????????????????? (notdef) ???????????????????????
  712. <LI>
  713. <!-- The rle image reader in my sfd routines had an off by one error causing it
  714. to reject some images. -->
  715. SFD ????????????????????????? 1 ???????????????????????????
  716. <LI>
  717. <!-- We used to munch memory when loading empty glyphs from mac NFNT resources. -->
  718. Mac ? NFNT ?????????????????????????????????
  719. <LI>
  720. <!-- It used to be that we didn't set the default background until the first font
  721. view window was opened. This meant that if we loaded a grey scale bitmap
  722. before opening a window (ie. from the command line) then that bitmap's clut
  723. would be relative to white rather than the appropriate background. -->
  724. ??????????????????????????????????????????????????????????????????????? (????????????????) ???????????????????????????? clut ????????????????????????????????????????
  725. <LI>
  726. <!-- Add some code to protect against badly generated bitmap strikes in sfnts. -->
  727. sfnt ???????????????????????????????????????
  728. <LI>
  729. <!-- vhea &amp; vmtx tables were generally wrong in otf fonts (unless the last
  730. full vmetric happened to be the last full hmetric). Also fix problems with
  731. cid hmtx output. -->
  732. OTF ?????????? vhea ??? vmtx ???????????????????? (??????????????????????????????????????????????)?CID ? hmtx ????????????
  733. <LI>
  734. <!-- The sfd reader looked in the wrong place for sli information in cid keyed
  735. fonts. -->
  736. CID ????????????????SFD ??????????/??????????????????????????
  737. <LI>
  738. <!-- Damn. Default output (for stdout) encoding never gets initialized when in
  739. a script. -->
  740. ??????????? (????) ????????????????????????????
  741. <LI>
  742. <!-- I realized a few months ago that there is a difference between encodings
  743. based on names and encoding based on unicode codepoints. Unfortunately I
  744. was only saving encodings as though they were based on names (generating
  745. default names if necessary). This patch retains the distinction even when
  746. encodings are saved to the preferences folder. -->
  747. ????Unicode ??????????????????????????2, 3 ?????????????????????????????? (?????????????????????) ????????????????????????????????????????????????????????????????????????
  748. <LI>
  749. <!-- AddAccent behaved differently when passed a glyphname and a unicode code
  750. point. In the first case it used the glyph specified. In the second it performed
  751. an arcane search which would not always use the specified glyph (left over
  752. from the days when it was important to use a glyph in Adobe Standard so you
  753. could do a seac). -->
  754. AddAccent ????????????? Unicode ?????????????????????????????????????????????????Unicode ?????????????????????????????????????????? (????seac ??????? Adobe ???????????????????????????????????????)?
  755. <LI>
  756. <!-- When debugging composite glyphs ff failed to notice when we switched from
  757. one glyph to another and so failed to reset the instruction list to those
  758. of the new glyph. -->
  759. ???????????????????????????????? ff ???????????????????????????????????????
  760. <LI>
  761. <!-- Problem with cubic to quadratic spline approximation. Fixed by a more careful
  762. comparison between original and resulting spline. -->
  763. 3 ??? 2 ???????????????????????????????????????????????????????????
  764. <LI>
  765. <!-- Kerning (and Anchor positioning) didn't work when printing to pdf. -->
  766. ????? (???????????) ??PDF ??????????????????
  767. <LI>
  768. <!-- Won-kyu Park points out that ff's internal utf7 parser (deep in the guts
  769. of sfd.c) only parses utf7 strings as produced by ff. He took a utf7 string
  770. produced by python and inserted it and ff could not read it. He provides
  771. a patch to fix the problem. -->
  772. Won-kyu Park ??ff ??? UTF-7 ??? (sfd.c ???????) ??ff ????? UTF-7 ??????????????????????? Python ????? UTF-7 ????????????ff ????????????????????????????????
  773. <LI>
  774. <!-- If we got an invalid second order spline, let's fix it up into some vaguely
  775. reasonable form, so the poor user doesn't keep getting errors. -->
  776. ??? 2 ?????????????????????????????????????????????????????????????????????
  777. <LI>
  778. <!-- Extra "-" in type42 header removed. -->
  779. Type42 ??????? "-" ????
  780. <LI>
  781. <!-- The anchor dialog was all screwed up. -->
  782. ?????????????????????
  783. <LI>
  784. <!-- The test in show att that all components of a substitution existed failed
  785. to handle a trailing space. -->
  786. ?ATT???(S)?????????????????????????????????????????????
  787. <LI>
  788. <!-- Make page Up/Down work in Show ATT -->
  789. ?ATT???(S)?? Up/Down ?????????????
  790. <LI>
  791. <!-- Sometimes the simplify algorithem fails to converge. -->
  792. ??????????????????????????????
  793. <LI>
  794. <!-- When generating a tfm file the width (height, depth, ic) table was being
  795. scaled twice. -->
  796. TFM ?????????? (??????ic) ???? ? 2 ?????????????
  797. <LI>
  798. <!-- Remove a NaN that occurred when moving quadratic splines. -->
  799. 2 ??????????????? NaN ????
  800. <LI>
  801. <!-- Oops. The unicode code point of a glyph was restricted to BMP by Glyph Info
  802. dlg. -->
  803. ????????????????????? Unicode ????? BMP ???????????
  804. <LI>
  805. <!-- Werner gave me a font where the glyphs were not properly ordered. So you
  806. can't tell the length of a glyph by loca[i+1]-loca[i]. The data appear valid
  807. in spite of that. So put in a warning for this particular case (we were
  808. generating a warning, but it wasn't as meaningful as it might be.) -->
  809. ?????????????????? Werner ?????????????????????? loca[i+1]-loca[i] ????????????????????????????????????????????????????????????? (????????????????????????????????????????)?
  810. <LI>
  811. <!-- Make View-&gt;Show ATT aware of the mark attachment class info so it can
  812. show the classes. -->
  813. ???(V)?ATT???(S)??????????????????????????????????
  814. <LI>
  815. <!-- When interpolating to quadratic fonts where the two designs didn't match
  816. then the various possible errors gave us bad splines: Different numbers of
  817. points on the paths meant that the control points at the end (after we reached
  818. the end of the contour in one design but not the other) didn't match. Different
  819. designs meant that interpolating a line (with no control points) to a curved
  820. spline again produced nasties. -->
  821. 2 ???????????????????2 ??????????????????????????????????????????????????: ???????????????????????????????? (?????????????????????????????) ???????????????????????????(????????) ??????????????????????????????????????????????
  822. <LI>
  823. <!-- Drag and drop was broken. -->
  824. ????&amp;?????????????
  825. <LI>
  826. <!-- Extend lookup flags support to include mark attachment classes (as defined
  827. in GDEF). -->
  828. ?????? (GDEF ??????) ?????????????????????
  829. <LI>
  830. <!-- Bad argument type checking on the AddAccent scripting command. -->
  831. AddAccent ??????????????????????????????
  832. <LI>
  833. <!-- Infinite loop in a rare case involving a flex hint at the start of a contour. -->
  834. ???????? flex ??????????????????????????
  835. <LI>
  836. <!-- The merge fonts command would crash. -->
  837. ???????????????????????????????
  838. <LI>
  839. <!-- Problems parsing some bare cff fonts. -->
  840. ?? CFF ?????????????????????
  841. </UL>
  842. <LI>
  843. <!-- 2-May-2005-->
  844. 2005?5?2?
  845. <UL>
  846. <LI>
  847. <!-- Add support for Mark Classes. -->
  848. ???????????????
  849. <UL>
  850. <LI>
  851. <!-- New pane in Font Info to create them -->
  852. ?????????????????????????
  853. <LI>
  854. <!-- New field in the feature tag dlg to use them -->
  855. ??????????????????????????
  856. <LI>
  857. <!-- Input/Output routines -->
  858. ???????
  859. </UL>
  860. <LI>
  861. <!-- Drag and drop was broken -->
  862. ????????????????????
  863. <LI>
  864. <!-- Infinite loop in some bizarre cases when generating a hinted opentype font. -->
  865. ?????? OpenType ????????????????????????????????????
  866. <LI>
  867. <!-- The Merge Fonts command was broken -->
  868. ???????(M) ?????????????
  869. <LI>
  870. <!-- The scripting command: AddAccent checked for the wrong argument type -->
  871. ?????????: AddAccent ?????????????????
  872. <LI>
  873. <!-- ff generated an error when loading some bare cff fonts. -->
  874. ff ????????? CFF ????????????????????????
  875. <LI>
  876. <!-- Store desired fontview sizes in prefs file -->
  877. prefs ????????????????????????????????????
  878. <LI>
  879. <!-- Add a tweak to make the mac's dynamic loader look for fink libraries -->
  880. Mac ??????????? Fink ??????????????????????
  881. <LI>
  882. <!-- Problems parsing bare cff cid-keyed fonts -->
  883. CFF ? CID ?????????????????????
  884. <LI>
  885. <!-- recognize that code page 932 is a variant of SJIS -->
  886. ?????? 932 ? SJIS ????????????????????
  887. <LI>
  888. <!-- The feature tag 'nutf' is an obsolete name for 'afrc' -->
  889. ???? 'nutf' ? 'afrc' ????????????
  890. <LI>
  891. <!-- Add a couple of new scripting functions -->
  892. 2 ????????????
  893. <UL>
  894. <LI>
  895. <!-- Int() which casts its real/int/unicode argument to int -->
  896. ??/??/Unicode ???????????? Int()
  897. <LI>
  898. <!-- UCodePoint() which casts its real/int/unicode argument to unicode -->
  899. ??/??/Unicode ? Unicode ??????? UCodePoint()
  900. </UL>
  901. <LI>
  902. <!-- scripting CharInfo no longer creates the glyph it is asked about -->
  903. ?????? CharInfo ??????????????????????????
  904. <LI>
  905. <!-- WorthOutputting/DrawsSomething can now be applied to the current selection -->
  906. WorthOutputting/DrawsSomething ????????????????????????????
  907. <LI>
  908. <!-- When using the freetype rasterizer don't do an automatic close of open paths. -->
  909. FreeType ??????????????????????????????????
  910. <LI>
  911. <!-- For SCWorthOutputting I used to check both that !widthset and width==em-size.
  912. Remove the em-size check, should be redundant and somethimes (marks) is wrong. -->
  913. SCWorthOutputting ?????!widthset ? width==em-size ???????????????em-size ???????????????????????? (???????) ???????????????
  914. <LI>
  915. <!-- The various FindBounds routines didn't pad stroked fonts appropriately -->
  916. ??? FindBounds ???????????????????????????????
  917. <LI>
  918. <!-- Discrepency in docs and code on spelling of scripting Auto[tT]race command.
  919. Accept both variants -->
  920. Auto[tT]race ????????????????????????????????????????????
  921. <LI>
  922. <!-- A debug statement was left in the ps interpreter -->
  923. PS ?????????????????????
  924. <LI>
  925. <!-- Make the help command look for japanese docs in the ja locale -->
  926. ja ???????????????????????????????
  927. <LI>
  928. <!-- Add a select fewer scripting command -->
  929. SelectFewer() ?????????????
  930. <LI>
  931. <!-- Fix some problems with custom encodings -->
  932. ???????????????????????????
  933. <LI>
  934. <!-- Support '\r' and '\r\n' as line-endings for backslash continuation -->
  935. ????????????????'\r' ? '\r\n' ??????????
  936. <LI>
  937. <!-- New version of Japanese UI -->
  938. ??? UI ???????
  939. <LI>
  940. <!-- The kerning pair dlg would sometimes fail to display a pair when searching
  941. on the second char of the pair. -->
  942. ????????????????? 2 ????????????????????????????
  943. <LI>
  944. <!-- Danish translation of some style names, courtesy of Anders Lund -->
  945. ?????????????????????Anders Lund ???????????
  946. <LI>
  947. <!-- Fix some problems with SJIS encoding -->
  948. SJIS ??????????????????????
  949. <LI>
  950. <!-- The point info dlg was quite unusable if you typed in somethng which wasn't
  951. a number -->
  952. ??????????????????????????????????????
  953. <LI>
  954. <!-- When in debug mode display pointer position in pixels -->
  955. ????????????????????????????????????
  956. <LI>
  957. <!-- Point Info had problems with order2 splines -->
  958. ???????????2 ???????????????????
  959. <LI>
  960. <!-- The instruction pane of the debug window was interpretting keystrokes it
  961. should not have -->
  962. ?????????????????????????????????????????????
  963. <LI>
  964. <!-- Peter Selinger has changed the way potrace is built so it no longer uses
  965. cygwin (it uses MinGW instead). This means ff can't pass it the name of a
  966. temp file as '/tmp/foo' because (on windows) /tmp is a cygwin fiction. So
  967. continue to put the file on cygwin's /tmp, but cd to that directory and then
  968. pass the bare filename. -->
  969. Peter Selinger ? potrace ???????????cygwin ?????????? (???? MinGW ????????)?????(Windows ??) /tmp ? cygwin ???????ff ????????? '/tmp/foo' ???????????????????????Cygwin ? /tmp ????????????????????????????? cd ????????????????????????
  970. <LI>
  971. <!-- Add some more greek PUA small caps -->
  972. PUA ???????????????????????????????????
  973. <LI>
  974. <!-- Add scroll bars to debug windows which lacked them -->
  975. ???????????????????????????????
  976. <LI>
  977. <!-- Add a gloss window which explains what a ttf instruction is going to use
  978. and what it is going to do. -->
  979. ?? TTF ???????????????????????????????????????????????????
  980. <LI>
  981. <!-- Was using the wrong accent to build cyrillic breves. -->
  982. ???????????????????????????????????????
  983. <LI>
  984. <!-- Remove the adobe private use defs from libgunicode and put them in fontforge. -->
  985. Adobe ??????????? libgunicode ??????FontForge ???????
  986. <LI>
  987. <!-- ff had problems reading pfm files containing kerning pairs using non-existant
  988. chars -->
  989. ff ????????????????????????? PFM ???????????????????
  990. <LI>
  991. <!-- Add pixels per em in register view. -->
  992. ?????????em ?????????????????
  993. <LI>
  994. <!-- No contours in twilight zone -->
  995. ????????????????????
  996. <LI>
  997. <!-- When generating tt fonts we did not set bit 8 in 'head'.Flags. This gives
  998. bad results when ppem is not an integer -->
  999. TT ??????????'head' ??????? 8 ??????????????????em ?????????????????????????
  1000. <LI>
  1001. <!-- When reencoding to adobe standard (or any encoding where glyph names are
  1002. more important than code points) make sure we use glyph names rather than
  1003. code points (so "f_i" is not in AdobeStd while "fi" is. But they map to the
  1004. same code point). -->
  1005. Adobe standard ???????????? (??????????????????????????????)????????????????????????????(???? AdobeStd ?? "f_i" ???? "fi" ?????????????????????????????????)?
  1006. <LI>
  1007. <!-- When creating a debug window in a glyph with no instructions (or in which
  1008. 'gasp' has turned off hinting) we used not to rasterize it. -->
  1009. ??????????????????????????? (??? 'gasp' ????????????????????)????????????????????
  1010. <LI>
  1011. <!-- Script/lang count was wrong in a number of places -->
  1012. ????????????/?????????????????
  1013. <LI>
  1014. <!-- Oops, the transform dlg and menu both used the "round to int" string. Then
  1015. I changed what it looked like in the menu, a change which is not appropriate
  1016. for the transform dlg. Add a new string just for the dlg. -->
  1017. ???????????????????????"??????" ???????????????????????????????????????????????????????????????????????????????????????????
  1018. <LI>
  1019. <!-- Tavmjong Bah added something to the "ypogegrammeni" list. -->
  1020. Tavmjong Bah ? "ypogegrammeni" ??????????????
  1021. <LI>
  1022. <!-- Fix problems with multiple text fields in the same window all wanting input
  1023. contexts (for input methods). -->
  1024. ???????????????????????????? (??????????) ?????????????????????????
  1025. <LI>
  1026. <!-- We generated ligature code in morx for ligatures that were not worth outputting. -->
  1027. ????????????? morx ????????????????
  1028. <LI>
  1029. <!-- Pierre Hanser points out that a recent change to SetWidth broke the scritping
  1030. SetWidth command. -->
  1031. Pierre Hanser ????? SetWidth ?????????? SetWidth ????????????????????
  1032. <LI>
  1033. <!-- Yet more effort to remove rounding errors from remove overlap. If a control
  1034. point causes a slight overshoot we get an unexpected extremum very close
  1035. to one of the en…

Large files files are truncated, but you can click here to view the full file