/htdocs.OLD/ja/oldchangelog.html
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
- <HTML>
- <HEAD>
- <!-- Created with AOLpress/2.0 -->
- <!-- AP: Created on: 16-Sep-2001 -->
- <!-- AP: Last modified: 15-Jul-2006 -->
- <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=Shift_JIS">
- <!--<TITLE>Older changes to FontForge</TITLE> -->
- <TITLE>FontForge ????????</TITLE>
- <LINK REL="icon" href="../fftype16.png">
- <LINK REL="stylesheet" TYPE="text/css" HREF="FontForge.css">
- </HEAD>
- <BODY>
- <DIV id="in">
- <P>
- <!--
- <A HREF="changelog.html">Current changes</A><BR> -->
- <A HREF="changelog.html">??????</A><BR>
- <!--
- <A HREF="pfaeditchangelog.html">Changes to PfaEdit (predecessor to
- FontForge)</A> -->
- <A HREF="pfaeditchangelog.html">PfaEdit (FontForge ????) ????</A>
- <UL>
- <LI>
- <!-- 31-August-2005-->
- 2005?8?31?
- <UL>
- <LI>
- <!-- The mac fix for 25-Aug wasn't quite enough. -->
- 8/25 ? Mac ?????????????????
- <LI>
- <!-- I used to maintain a hidden value of the os2 linegap. This didn't change
- when users set linegap with font info, leaving users annoyed. -->
- ????OS/2 ? linegap ??????????????????????????????????????? linegap ????????????????????????????????
- <LI>
- <!-- It used to be that both the Hint->Add Hint and Hint->Create Hint commands
- would destroy all hint masks. Now we update those hint masks appropriately. -->
- ???????????????????????????????????????????????????????????????????????????????
- <LI>
- <!-- The "Original" encoding was broken, and reencoding to it gaves us 256 blank
- glyphs before glyph0. Sigh. -->
- ???????????????????????????????????????????????? 0 ??? 256 ?????????????????????
- <LI>
- <!-- The CodeRange bit for symbol doesn't mean the font contains any standard
- set of "symbol" glyphs, but rather either that it has a 3,0 cmap sub-table,
- or that there are glyphs mapped to 0xf000-0xf0ff in the 3,1 (unicode) sub-table. -->
- CodeRange ???? symbol ??????????? "Symbol" ????????????????????????????????3,0 cmap ???????????????3?1 (Unicode) ??????? 0xf000-0xf0ff ????????????????????????
- <P>
- <!-- Setting this bit should give you a symbol encoding as well as all the other
- encodings you've set bits for. It doesn't work under windows. It doesn't
- work. TrueType fonts do not provide a symbol encoding, while 'CFF ' fonts
- only provide a symbol encoding. But hey, let's support it anyway! -->
- ???????????????????????????????????? Symbol ????????????????????????? Windows ????????????????TrueType ????? Symbol ??????????????Symbol ????????????????? 'CFF ' ???????????????????????????????!
- <P>
- <!-- change View->Goto to know about this range as MS Symbol. -->
- ???????? MS Symbol ???????????????
- <LI>
- <!-- Importing an eps file (or pasting the x clipboard) made use of an uninitialized
- variable. (introduced 7-Aug) -->
- EPS ????????? (??? X ????????????) ???????????????? (8/7 ??)?
- <LI>
- <!-- Cleanup pasting references from one font to another (gave some very strange
- results when pasting refs with no unicode encodings). -->
- ????????????????????? (??? Unicode ??????????????????????????????)?
- </UL>
- <LI>
- <!-- 25-August-2005-->
- 2005?8?25?
- <UL>
- <LI>
- <!-- Recode the mac resource fork routines so that they no longer use the FSSpec
- structure. 10.4 complains about it. -->
- Mac ???????????????????FSSpec ??????????????????????? 10.4 ??????????
- <LI>
- <!-- Bug in mm font charstring generation. -->
- ?????????????? charstring ????????
- <LI>
- <!-- If a font contained mac feature setting names, then when ff generated it,
- ff would produce duplicate entries in the 'name' table for these guys. One
- for the name in the font itself, and one for the name ff thought that feature
- setting should have. -->
- Mac ????????????????FF ??????????? 'name' ???????????????????????1 ????????????????????? 1 ?? ff ?????????????????????
- <LI>
- <!-- Nobody else puts apple unicode names into the 'name' table so I probably
- should not either. Adobe says one should not. Apple's website implies one
- should - - but Apple doesn't and its ttf website is not very accurate. -->
- Apple Unicode ? 'name' ????????????????????????????????????????Adobe ??????????????????Apple ? Web ??????????????????????????????????????Apple ? TTF ???? Web ???????????????
- <LI>
- <!-- When ff generated a ttf/otf font with applemode set and opentype off then
- the font would have version 'true'. Which means windows would reject it.
- That's probably not a good idea given that this situation is default on the
- mac - - even if we don't have a GSUB/GPOS table we should at least let the
- glyphs show on windows. -->
- ff ? TTF/OTF ? Apple ???????OpenType ??????????????????????????? 'true' ????????????Windows ????????????????? Mac ????????????????????????????GSUB/GPOS ??????????????????????????????????????????
- <P>
- <!-- On the other hand some people might want to make fonts that only work on
- macs. So add a configure flag. -->
- ?????Mac ????????????????????????????????????? configure ????????????
- <LI>
- <!-- ff couldn't undo changing the lig carets (if it weren't compiled for multilayer) -->
- FF ??????????????????? (?????????????????????)?
- <LI>
- <!-- Copying a pairwise positioning left memory in a bad state. -->
- ?????????????????????????????????????
- <LI>
- <!-- Coalesce all lookups with the same feature & script lang. This makes
- ATM happy about kerning on windows. -->
- ???????????????????????????????????Windows ???????????? ATM ??????????????
- <LI>
- <!-- When rasterizing a multilayer font we would sometimes get warnings from the
- stroker about how the stroke self-intersected. Get rid of those warnings. -->
- ????????????????????????????????????????????????????????????????????????????????????
- <LI>
- <!-- Pasting from a multilayered font into a normal one crashed -->
- ?????????????????????????????????????
- <LI>
- <!-- If an order2 font were turned into a PS font, then characters with hint conflicts
- got no hints. -->
- 2 ?????? PS ?????????????????????????????????????
- <LI>
- <!-- Makers of fonts on the mac often use out of bound GIDs as flags in contextual
- su bstitutions. What I have seen is that one sub-table will insert such a
- "glyph" w hen a match is found, and then the next sub table will remove the
- flag, and perf orm subsequent transformations. This is important on the mac
- because there is a limited number of substitutions that can happen once a
- match is found, but if a match is found at the start (ie. the match being
- some magic marker glyph) then u nlimited substitutions are available. When
- ff first stumbled on these fonts it crashed, then it treated a gid>glyph_cn
- t as an error (and so it ignored the substitution). I've just put in code
- that c reates dummy glyphs for all these bizarre GIDs so (I hope) the font
- will work af ter passing through ff (only there will be some real blank glyphs
- at the end of the font rather than vaper-ware glyphs). -->
- Mac ?????????????????????????????????? GID ?????????????????????????????????????????????????????????????????????????????????????Mac ????? 1 ??????????????????????????????????????????? (????????????????????????????) ??????????????????????????????????FF ??????????????????????????????????????? gid>glyph_cnt ???????????????? (??????????????)????????? GID ?????????????????????ff ???????????????????????? (????????????????????????????????????????????????)?
- <LI>
- <!-- The Active Hints pane (of Point Info) didn't always work if a glyph had more
- than one contour. -->
- [??????] ?? (???????????? 1 ????????????????????????
- <LI>
- <!-- Be more canny in the use of subroutines for references in type1/2 output. -->
- Type1/Type2 ???????????????????????????????
- <LI>
- <!-- When generating contextual lookups, ff did not set the lookup count between
- gpos and gsub. So if a font had both contextual gpos & gsub elements
- ff got confused. -->
- ???????????????ff ? GPOS ? GSUB ?????????????????????????????????????????? GPOS ? GSUB ?????????????FF ??????????
- <LI>
- <!-- The code for cff encodings (ie. in bare cff non-cid fonts) didn't handle
- multiply encoded glyphs -->
- CFF ??? (?????? CFF ? CID ??????) ????????????????????????????
- <LI>
- <!-- Change the default color of the prev control point (so it's easier for me
- to see) -->
- ???????????????? (?????????????????)?
- </UL>
- <LI>
- <!-- 11-August-2005-->
- 2005?8?11?
- <UL>
- <LI>
- <!-- The configure script did not find libfreetype when it lived (solely) in
- /usr/X11R6/libs -->
- /usr/X11R6/libs ??? libfreetype ??????configure ??????????????????
- <LI>
- <!-- On the Mac, menus incorrectly suggested using Cmd rather than Ctl. (Cmd used
- to work on earlier versions of the X server, but now it is snagged by the
- X11 menubar itself.) -->
- Mac ??????????? Ctl ???? Cmd ????????? (Cmd ?????? X ????????????????????? X11 ??????????????????????)?
- <LI>
- <!-- ff uses the Alt/Meta key to alter the behavior of some tools (magnify, ruler,
- pointer, pencil, etc.) in the editing windows. This doesn't work well on
- the mac. First there is no real Alt/Meta key. If we contemplate using Option
- or Command it will generally already be used to turn the single button mouse
- into a three button mouse (Option - mouse => button 2, Command - mouse
- => button 3). So instead use the CapsLock key. -->
- FF ??????????????? (????????????????) ?????????????? Alt/Meta ???????????? Mac ?????????????????????? Alt/Meta ?????????Option ??? Command ??????????????????1 ??????? 3 ???????????????????????? (Option-???????2, Command-???????3)???????? CapsLock ?????????
- </UL>
- <LI>
- <!-- 9-August-2005-->
- 2005?8?9?
- <UL>
- <LI>
- <!-- The big5 encoding stopped at 64000, which confused routines which expected
- unencoded glyphs to start at 65536. -->
- Big5 ????????? 64000 ???????????????????????? 65536 ??????????????????????????????
- <LI>
- <!-- We would crash when reencoding a font with enough unencoded alternate unicode
- code points. -->
- ??????????? Unicode ??????????????????????????????????????????????
- <LI>
- <!-- The code for creating an 8/16 cmap subtable didn't work. -->
- 8/16 cmap ??????????????????????????
- <LI>
- <!-- ff would crash if it had two windows open on the same font and one got reencoded -->
- ??????????????????????????????????????????????????
- <LI>
- <!-- Didn't set the length of the format4 'cmap' sub-table, so the offset to the
- format12 (32bit unicode) table was wrong. -->
- ?????? 4 'cmap' ???????????????????????????? 12 (32 ??? Unicode) ?????????????????????
- <LI>
- <!-- ttfcopyfile can complain about a ttf table offset being wrong. Give it the
- info so that it will now tell us which table has the wrong offset. -->
- ttfcopyfile ??TTF ????????????????????????????????????????????????????????????????????????
- <LI>
- <!-- Uninitialized variable in metricsview when creating a popup window. -->
- ????????????????????????????????
- <LI>
- <!-- Redo the ttfnames pane of the font info dlg. Now show the names as an editable
- list. -->
- ???????????? [TTF ?] ??????????????????????????????????
- <LI>
- <!-- Histogram dlg still used wrong encodings for selected glyphs when historgrams
- invoked from Hints menu. -->
- ??????????????????????????????????????????????????????????????
- </UL>
- <LI>
- <!-- 7-August-2005-->
- 2005?8?7?
- <UL>
- <LI>
- <!-- SelectIf failed when passed an encoding which was out of bounds -->
- SelectIf() ???????????????????????????
- <LI>
- <!-- Added a new scripting command: ToString -->
- ???????????? ToString() ????
- <LI>
- <!-- Using the X clipboard to paste a glyph into a glyph that contained stuff
- caused a crash. -->
- X ??????????????????????????????????????????????????????????
- <LI>
- <!-- Using the X clipboard to paste a glyph with references or with multilayer
- did no t work. -->
- X ??????????????????????????????????????????????????????????????????
- <LI>
- <!-- None of ttf, otf nor svg got multiply encoded glyphs output properly. -->
- TTF, OTF, SVG ??????????????????????????????????
- <LI>
- <!-- FF screwed up memory when creating ligatures from an svg font. -->
- SVG ?????????????????????????????
- <LI>
- <!-- Merge fonts was writing to bad memory. -->
- ??????????????????????????
- <LI>
- <!-- FF was confused by a strange MM font -->
- FF ?????? MM ?????????????????
- <LI>
- <!-- FindExistingSlot should understand altuni. -->
- FindExistingSlot() ? altuni ??????????
- <LI>
- <!-- Font View didn't display current unicode of multiply encoded glyphs. (same
- for popups). -->
- ????????????????????????? Unicode ???????????? (?????????)?
- <LI>
- <!-- Still having problems generating type1 code for complicated reference glyphs. -->
- ????????? Type1 ?????????????????
- <LI>
- <!-- Retain knowlege of multiple unicode encodings for some glyphs. Used when
- a glyph has multiple encodings and is reencoded. -->
- ???????? Unicode ?????????????????????????????????????????????????????
- <LI>
- <!-- Add back an option to compact an encoding. It's not the same as the old compact
- which kept track of the former encoding. This just compacts, user must explicitly
- reencode. -->
- ?????????????????????????????????????????????????????????????????????????????????????????????????????????????
- <LI>
- <!-- Force encoding didn't work if the new encoding had more slots than the old. -->
- ?????????????????????????????????????????????????????
- <LI>
- <!-- FF also failed to parse glyph based contextual lookups properly -->
- FF ?????????????????????????????????
- </UL>
- <LI>
- <!-- 3-August-2005-->
- 2005?8?3?
- <UL>
- <LI>
- <!-- FF failed to parse class based contextual lookups properly (contextual chaining
- lookups were ok) -->
- FF ??????????????????????????????? (?????????????)
- </UL>
- <LI>
- <!-- 2-August-2005-->
- 2005?8?2?
- <UL>
- <LI>
- <!-- <FONT COLOR="Red"><STRONG><BIG>The OS/2 ulCodeRanges field has been broken
- for a long time, and has failed to mark the presence of any latin code
- pages.</BIG></STRONG></FONT> -->
- <FONT COLOR="Red"><STRONG><BIG>OS/2 ? ulCodeRanges ??????????????????????????????????????????????</BIG></STRONG></FONT>
- <LI>
- <!-- The ulCodeRanges field never set Vietnamese, TradChinese, Mac nor PC OEM -->
- ulCodeRange ??????????????Mac ??? PC OEM ????????????????????????????
- <LI>
- <!-- FF did not support EUC-CN, ISO-2022-CN, ISO=2022-KR iconv encodings properly. -->
- FF ? iconv ? EUC-CN, ISO-2022-CN, ISO-2022-KR ?????????????????????????
- <LI>
- <!-- Work around a bug in iconv's support for CP1258 -->
- iconv ? CP1258 ???????????
- <LI>
- <!-- Put some code in to warn users about unknown language/locales in the ttf
- 'name' table. -->
- TTF ? 'name' ???????????????/??????????????????
- <LI>
- <!-- Enter some new language/locale codes for ms. -->
- ??? MS ???/???????????????
- <LI>
- <!-- Crash when moving the end of an open path in an order2 font. -->
- 2 ????????????????????????????????????
- <LI>
- <!-- If one loaded an encoding specified by codepoint and then cancelled the dlg
- which asked for a name for that encoding, then ff would crash. -->
- ?????????????????????????????????????????????????????????ff ????????????????
- <LI>
- <!-- Don't use Adobe's glyphnames when they are obviously wrong (use uni???? instead) -->
- ????????????????? Adobe ??????????? (???? uni???? ???)
- <LI>
- <!-- Add (better) support for the new dotlessj -->
- ??? dotlessj ? (????) ????????
- <LI>
- <!-- Put a check into the context chain dlg to make sure that people don't add
- sequence/lookup pairs where the sequence number is too big. -->
- ?????????????????????????????????/??????????????????????????
- <LI>
- <!-- Make class be the default format for contextual/chaining substitutions rather
- than coverage tables. -->
- ?????????????????/????????????????????????????????
- <LI>
- <!-- <FONT COLOR="Red"><STRONG><BIG>The format of the LineBreak.txt file changed
- with Unicode 4.1, so all the line break info is wrong (essentially lines
- never broke in text fields).</BIG></STRONG></FONT> -->
- <FONT COLOR="Red"><STRONG><BIG>LineBreak.txt ???????????? Unicode 4.1 ?????????????????????????? (???????????????????????????????)?</BIG></STRONG></FONT>
- <LI>
- <!-- Reference to bad memory when creating a popup in combinations list. -->
- ?????????????????????????????????????
- <LI>
- <!-- Still problems in the 'name' table when Mac & Mac Unicode strings don't
- match. -->
- 'name' ???????Mac ? Mac Unicode ????????????????????????
- <LI>
- <!-- Use of the X clipboard for transfering glyphs resulted in a crash -->
- ???????????? X ?????????????????????????
- <LI>
- <!-- When generating an old-style 'kern' table (either OpenType nor Apple modes
- set) decompose all kerning classes into kern pairs as we do for AFM files. -->
- ?????? 'kern' ????? (OpenType ????Apple ??????????????) ??????AFM ????????????????????????????????????????????
- <LI>
- <!-- Scripting didn't have a way to generate a font with neither Apple nor OpenType
- tables. Add one. -->
- ??????????Apple ? OpenType ?????????????????????????????????
- <LI>
- <!-- Oops. wrong default extension for otb fonts from scripts. -->
- ?????????? OTB ???????????????????????????????
- <LI>
- <!-- Fix some potential crashes where loading font types left a new field unset. -->
- ???????????????????????????????????????????????????????????????
- </UL>
- <LI>
- <!-- 28-July-2005-->
- 2005?7?28?
- <UL>
- <LI>
- <!-- <FONT COLOR="Red"><STRONG><BIG>Redesigned the way encodings are handled.
- From the user's perspective Encodings are no longer controlled by FontInfo,
- but via an encoding menu.</BIG></STRONG></FONT> -->
- <FONT COLOR="Red"><STRONG><BIG>??????????????????????????????????????????????????????????????????????????????????????</BIG></STRONG></FONT>
- <LI>
- <!-- If we create a bitmap strike in an empty font then change the fontview to
- look at the strike. -->
- ?????????????????????????????????????????????????
- <LI>
- <!-- The SetWidth command of FontView produced garbage defaults for empty fonts -->
- ??????????????? SetWidth() ??????????????????????????
- <LI>
- <!-- Don't set the hinting needed bit on: bitmap only fonts, multilayered fonts,
- stroked fonts nor quadratic fonts. -->
- ??????????????????????????????????? 2 ?????????????????????????????????
- <LI>
- <!-- Fix some problems with the generated names in File->Generate multiple -->
- ??????????????????????????????????
- <LI>
- <!-- The Save command failed to reset the font window's title (so it still looked
- modified) -->
- ????????????????????????????????????? (????????????????)?
- <LI>
- <!-- The enabled state of Encoding->Detach Glyphs was wrong -->
- ?????????????????????????????????????
- <LI>
- <!-- FF still didn't allow two ligatures to be created for the same glyph (ie.
- it complained if you tried to make both "f + f + i => ffi" and "ff + i
- => ffi" -->
- FF ??????????? 2 ????????????????????????? (????"f + f + i ? ffi" ? "ff + i ? ffi" ?????????????????????)?
- <LI>
- <!-- Added a TypeOf command to scripting -->
- ?????? TypeOf() ????????
- <LI>
- <!-- Added a GetPosSub command to scripting. -->
- ?????? GetPosSub() ????????
- <LI>
- <!-- Werner says negative widths and depths be set to 0 in tfm files. -->
- ????????? TFM ?????? 0 ??????? Werner ????????
- <LI>
- <!-- FontForge was generating an incorrect warning message. If a 'name' table
- contains a duplicate entry for a given platform/specific/language/id that's
- an error in the font. But ff conflated mac names with window names and so
- was only checking language/id. So if the mac windows names were different
- (which is probably a bad design idea, but not an error) ff said it was wrong.
- It can also be caused by using a character in the string which is not in
- the Mac Encoding for that language. -->
- FontForge ?????????????????????????????????????/??/??/???ID ? 'name' ?????????????????????????????????????? ff ? Mac ????? Windows ????????????????/ID ? 2 ??????????????????????Mac ? Windows ?????????????? (?????????????????????????????) ff ????????????????????????????? Mac ???????????????????????????????????????????????????????
- <LI>
- <!-- Don't set "Hinting needed" flag in bitmap only fonts. -->
- ????????????????????????????????????????
- <LI>
- <!-- AutoHint had a crash if there were open contours in a glyph being hinted. -->
- ?????????????????????????????????????????????????
- <LI>
- <!-- Add a couple of browsers to the list to check by default. -->
- ????????????????????? 2 ?????
- <LI>
- <!-- Using the kerning pair closeup dlg to create a new kerning pair caused a
- crash (eventually). -->
- ???????????????????????????????????? (????) ????????????
- <LI>
- <!-- When saving a block of ttf bitmap glyphs all with about the same metrics, -->
- TTF ????????????????????????????????????????
- <LI>
- <!-- Kern pairs were not scaled to emsize when loading from an afm file. -->
- AFM ???????????????????? EM ????????????????????
- <LI>
- <!-- Add a series of new selection commands, to the font view and to scripting: -->
- ???????????????????????????????
- <UL>
- <LI>
- SelectChangedGlyphs
- <LI>
- SelectHintingNeeded
- </UL>
- <P>
- <!-- (just to scripting) -->
- (???????)
- <UL>
- <LI>
- SelectSingletons
- <LI>
- SelectMoreSingletons
- <LI>
- SelectFewerSingletons
- </UL>
- <LI>
- <!-- Revert Glyph didn't work. One bug caused by multilayer, one caused by encoding
- changes, and one really old one. -->
- ?????????????????????????????????????? 1 ??????????????????? 1 ??????? 1 ???????????????
- <LI>
- <!-- GetFontNames returned an uninitialized value on bad ttf files. -->
- GetFontNames() ????? TTF ???????????????????????????
- <LI>
- <!-- Add some new scripting commands to access the TeX per-glyph fields. -->
- TeX ??????????????????????????????????????????
- <LI>
- <!-- Werner suggested some improvements to tfm output. -->
- Werner ??????? TFM ?????????????
- <LI>
- <!-- Cleanup behavior of generating ttf bitmaps in a script. -->
- TTF ??????????????????????????????
- <LI>
- <!-- I was attaching script/langs to lookups when parsing GPOS/GSUB. That wasn't
- good enough. Each sub-table and have it's own set, so attach script/langs
- to subtables as well. Still a flaw in that sub-tables could be referenced
- through severel extension sub-tables or directly and I don't unravel that
- complexity until too late. -->
- GPOS/GSUB ?????????/??????????????????????????????????????????????????????????????????????????/????????????????????????????????????????????????????????????????????????????????????????????????????
- <LI>
- <!-- ATM which handles some kerning for otf fonts for Word, does not handle 'kern'
- features where the feature contains more than one lookup. So whenever we
- have a feature with multiple lookups try to compress them into one lookup
- with multiple sub-tables. -->
- Word ???? OTF ??????????????????? ATM ??'kern' ??? 2 ????????????????????????????????????????????????????????????????????? 1 ????????????????????????
- <LI>
- <!-- Transform (in fontview) and Scale To Em do not scale the vertical advance. -->
- (?????????)??????????????????????????????????????????????
- <LI>
- <!-- We didn't test the right thing when deciding where a subroutine containing
- refs began. -->
- ??????????????????????????????????????????????
- <LI>
- <!-- Remove Undoes was broken by the encoding changes. -->
- ???????????????????????????(N)??????????????
- <LI>
- <!-- When saving multiple, make sure we don't get extraneous kerns. (to glyphs
- not in the current sub-font). -->
- ?????????????(??????????????????????) ???????????????????????
- <LI>
- <!-- Make sure the blue lines (marking hints needing to be updated) get cleared
- properly. -->
- (?????????????????) ???????????????????????
- <LI>
- <!-- Some display problems in the SameGlyphAs command. -->
- SameGlyphAs() ????????????????
- <LI>
- <!-- The Apply Substitutions code did not consider the possibility of loops:<BR>
- a->b->c->d->a -->
- ???????????? a?b?c?d?a ???????????????????????
- <LI>
- <!-- Werner suggests indicating multi-layer in the version string. -->
- ????????????????????????? Werner ????????
- <LI>
- <!-- Mark to Mark anchor classes should allow each mark glyph also to contain
- a base mark entry. -->
- ?????????????????????????????????????????????????????
- <LI>
- <!-- Give unicode name data (in grey) for dotted names. (ie for A.super give unicode
- name data for "A", but in grey so it stands out as modified). -->
- ?????????????? Unicode ?????? (???) ???(????A.super ? Unicode ? "A" ????????????????????????????)
- <LI>
- <!-- Add scripting routines to detach glyphs from the encoding and to remove them
- from the font. -->
- ?????????????????????????????????????????????????????
- <LI>
- <!-- FF produced some very strange 'gasp' tables... depending on the bitmap fonts
- in the sfd and not on the bitmaps in the output ttf for one thing. -->
- FF ????????? 'gasp' ?????????????…… SFD ???????????? ????????????? TTF ?????????????????????
- <LI>
- <!-- Werner wants an Invert Selection command. -->
- Werner ??[???????] ??????????????
- <LI>
- <!-- The position of Coptic and Glagolithic has been shifted in Unicode 4.1 (shifted
- from some earlier proposal). -->
- ???????????????? Unicode 4.1 ????????? (??????????????????????????)?
- <LI>
- <!-- Patch by KANOU, ttc files were broken. -->
- ?????????TTC ?????????????
- <LI>
- <!-- Some english language strings in the ttfnames pane of fontinfo where sort
- of bound to equivalent fields in the names pane. Make this clearer, and
- consistent. -->
- ???????????? [TTF ?] ????????????????[??] ??????????????????????????????????????????????????
-
- <LI>
- <!-- Werner thinks my error messages for scripts should be improved. -->
- Werner ?????????????????????????
- <LI>
- <!-- Add a check in case sfd files contain unreasonable values for pixelsize,
- etc. -->
- SFD ????????????????????????????????????????
- <LI>
- <!-- Werner suggests a -- dry <scriptfile> argument which does syntax checking
- without actually executing the script. I think it is trivial. -->
- ?????????????????????? --dry <?????????> ???????? Werner ???????????????????????
- <LI>
- <!-- Werner points out that the DSC Version comment has a very specific syntax:<BR>
- %%Version: <version> <revision><BR>
- <version> is a real, <revision> is a uint. So we can't use the
- font's version string here (which might be anything). Instead we now generate
- a version comment<BR>
- %Version: <string><BR>
- rather than a DSC Comment. -->
- Werner ????????DSC ????????????????????:
- %%Version: <version> <revision><BR>
- <version> ????, <revision> ???????????????? (??????????) ?????????????????????DSC ???????????????????<BR>
- %Version: <string><BR>
- ?????????????
- <LI>
- <!-- We used to assign a unicode value to ".notdef"s when reading ps encoding
- file, if the encoding was in the region of control chars (so location 1 would
- get uni0001, while location 65 would get -1). Seems inconsistent. -->
- PS ??????????????????????????????????????????????? Unicode ? ".notdef" ?????????? (???????? 1 ? uni0001 ?????????? 65 ? -1 ?????)???????????????
- <LI>
- <!-- Oops. I failed to provide a mechanism to add other iconv encoding names into
- my menu. -->
- ?????????????????????????????????????????????
- <LI>
- <!-- Code to support group display. -->
- ????????????????????
- <LI>
- <!-- Was not reading ps encoding files properly. -->
- PS ?????????????????????????????
- <LI>
- <!-- Remove encoding should always be available. -->
- ????????????????????????????
- </UL>
- <LI>
- <!-- 19-July-2005-->
- 2005?7?19?
- <UL>
- <LI>
- <!-- Extend to Unicode 4.1 -->
- Unicode 4.1 ????
- <LI>
- <!-- Change to configuration system to allow relative pathspecs for
- --with-freetype-src didn't work. -->
- configure ????????? --with-freetype-src ?????????????????????????????????
- <LI>
- <!-- Context chain dlg had problems with empty patterns (no terminal NUL in empty
- string used to represent them) -->
- ?????????????????????????????? (????????????? NUL ????????????)
- <LI>
- <!-- The [EditData] button in contextual fontinfo pane was disabled due to reasons
- which are no longer valid.. -->
- ?????????????? [??????] ??????????????????????????????????
- <LI>
- <!-- Transforming by a negative scale factor screwed up the hints. -->
- ??????????????????????????
- <LI>
- <!-- Add move up/down buttons to the kerning class dlg (class lists area) Use
- the selection from the class lists to highlight offsets. -->
- ????????????? (?????????) ??/???????????????????????????????????????????????????????
- <LI>
- <!-- Print sample did not handle kerning by classes. -->
- ??????????????????????????????????????
- <LI>
- <!-- When we had: a glyph which contained refs where that glyph was itself used
- as a reference in another glyph and all glyphs (except the last) lived in
- subroutines then we got multiple declarations of hints and the middle glyph
- was translated from where it should have been. -->
- ?????????????????????????????????????????????????????????????????? (??????????) ???????????????????????????????????????????????????
- <LI>
- <!-- When changing lists they should not scroll back to the beginning. -->
- ???????????????????????????????????
- <LI>
- <!-- Various fixes regarding hints: changing hints should set the char changed
- flag changing a glyph should mark all glyphs that refer to it as having out
- of date hints display out of date hints in font view. hints weren't being
- preserved (and should have been) in charview in Paste and transform. -->
- ????????????: ????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
- <LI>
- <!-- Apply Substitutions was badly broken when ff compiled with multilayer. -->
- ff ??????????????????????????????????????????
- <LI>
- <!-- Kern Pair dlg looked at garbage memory when it closed (and crashed sometimes). -->
- ???????????????????????????????????? (??????????????????)?
- <LI>
- <!-- ff decides whether to add a 'gasp' table to a font based on whether the font
- has instructions or not. ff's own ttf fonts contain instructions in .notdef
- but nowhere else, so ignore .notdef when making this check. -->
- ff ???????????????????????? 'gasp' ?????????????????????????ff ???? TTF ????? .notdef ?????????????????????????????????????? .notdef ?????????????
- <LI>
- <!-- One more attempt to rule out absurd results in simplify(). -->
- simplify() ??????????????????????? 1 ????????
- <LI>
- <!-- if the lsb/rsb dlg was given a negative value it complained about negative
- widths. (whether the width would have been negative or not). -->
- ?????????????????????????(???????????????????) ???????????????????????????
- <LI>
- <!-- $italicangle has been broken since I added reals to scripting. -->
- $italicangle ??????????????????????????
- <LI>
- <!-- The kernclass dialog did not handle deleted classes properly. -->
- ??????????????????????????????????????
- <LI>
- <!-- Add ability to undo hints. -->
- ??????????????
- <LI>
- <!-- Once again starting a browser on windows is broken. -->
- ?????Windows ?????????????????
- <LI>
- <!-- We didn't do a bounds check when indexing into the names array of an encoding
- (when building a character from scratch). If the index was huge the result
- was garbage, generally leading to a crash sometime thereafter. -->
- ????????? names ????????????????(?????????????????) ??????????????????????????????????????????????????????????????????????????
- <LI>
- <!-- An open path consisting of a single point caused replace with reference to
- crash. -->
- 1 ?????????????????????????????????????????????????
- <LI>
- <!-- Generating a postscript resource font on the mac from a script did not work. -->
- Mac ??????????? PostScript ??????????????????????????
- <LI>
- <!-- Werner points out that afm files generated by FontForge still claim to have
- been made by pfaedit. Oops. -->
- Werner ??FontForge ????? AFM ????????PfaEdit ???????????????????????????
- <LI>
- <!-- Didn't parse user defined encodings properly and often omitted the first
- glyph. -->
- ??????????????????????????????????????????????
- </UL>
- <LI>
- <!-- 24-June-2005-->
- 2005?6?24?
- <UL>
- <LI>
- <!-- Improvements in the way type42 fonts where handled in printing. -->
- ???? Type42 ???????????
- <LI>
- <!-- Fix a crash when parsing mangled cff files -->
- ??? CFF ?????????????????????
- <LI>
- <!-- Marvelous triple bug: -->
- ???????:
- <UL>
- <LI>
- <!-- Adobe's Tech Note 5176 (cff format) says that a private dict is required.
- They mean it's required in a type1 font. -->
- Adobe ? Tech Note 5176 (CFF ??????) ???????????????????????Type1 ??????????????????
- <LI>
- <!-- Because of this I put a null private dict entry into my cid cff fonts. -->
- ????????CID CFF ?????????? 1 ???????????????????????
- <LI>
- <!-- ghostview finds the null private dict entry and tries to read data from it
- even though it is of 0 length. -->
- ghostview ?????????????????????????? 0 ???????????????????
- </UL>
- <LI>
- <!-- Add postscript code necessary for loading a cff font to my cff font output. -->
- CFF ????????????? PostScripto ??????????? CFF ????????
- <LI>
- <!-- Fix some uninitialized variables in the display dlg. -->
- ??????????????????????
- <LI>
- <!-- We didn't get DSC pages properly when printing a CID keyed font. -->
- CID ????????????DSC ???????????????????
- <LI>
- <!-- The default (notdef) glyph generated by my palm output routines was a little
- wonky. -->
- Palm ?????????????????? (notdef) ???????????????????????
- <LI>
- <!-- The rle image reader in my sfd routines had an off by one error causing it
- to reject some images. -->
- SFD ????????????????????????? 1 ???????????????????????????
- <LI>
- <!-- We used to munch memory when loading empty glyphs from mac NFNT resources. -->
- Mac ? NFNT ?????????????????????????????????
- <LI>
- <!-- It used to be that we didn't set the default background until the first font
- view window was opened. This meant that if we loaded a grey scale bitmap
- before opening a window (ie. from the command line) then that bitmap's clut
- would be relative to white rather than the appropriate background. -->
- ??????????????????????????????????????????????????????????????????????? (????????????????) ???????????????????????????? clut ????????????????????????????????????????
- <LI>
- <!-- Add some code to protect against badly generated bitmap strikes in sfnts. -->
- sfnt ???????????????????????????????????????
- <LI>
- <!-- vhea & vmtx tables were generally wrong in otf fonts (unless the last
- full vmetric happened to be the last full hmetric). Also fix problems with
- cid hmtx output. -->
- OTF ?????????? vhea ??? vmtx ???????????????????? (??????????????????????????????????????????????)?CID ? hmtx ????????????
- <LI>
- <!-- The sfd reader looked in the wrong place for sli information in cid keyed
- fonts. -->
- CID ????????????????SFD ??????????/??????????????????????????
- <LI>
- <!-- Damn. Default output (for stdout) encoding never gets initialized when in
- a script. -->
- ??????????? (????) ????????????????????????????
- <LI>
- <!-- I realized a few months ago that there is a difference between encodings
- based on names and encoding based on unicode codepoints. Unfortunately I
- was only saving encodings as though they were based on names (generating
- default names if necessary). This patch retains the distinction even when
- encodings are saved to the preferences folder. -->
- ????Unicode ??????????????????????????2, 3 ?????????????????????????????? (?????????????????????) ????????????????????????????????????????????????????????????????????????
- <LI>
- <!-- AddAccent behaved differently when passed a glyphname and a unicode code
- point. In the first case it used the glyph specified. In the second it performed
- an arcane search which would not always use the specified glyph (left over
- from the days when it was important to use a glyph in Adobe Standard so you
- could do a seac). -->
- AddAccent ????????????? Unicode ?????????????????????????????????????????????????Unicode ?????????????????????????????????????????? (????seac ??????? Adobe ???????????????????????????????????????)?
- <LI>
- <!-- When debugging composite glyphs ff failed to notice when we switched from
- one glyph to another and so failed to reset the instruction list to those
- of the new glyph. -->
- ???????????????????????????????? ff ???????????????????????????????????????
- <LI>
- <!-- Problem with cubic to quadratic spline approximation. Fixed by a more careful
- comparison between original and resulting spline. -->
- 3 ??? 2 ???????????????????????????????????????????????????????????
- <LI>
- <!-- Kerning (and Anchor positioning) didn't work when printing to pdf. -->
- ????? (???????????) ??PDF ??????????????????
- <LI>
- <!-- Won-kyu Park points out that ff's internal utf7 parser (deep in the guts
- of sfd.c) only parses utf7 strings as produced by ff. He took a utf7 string
- produced by python and inserted it and ff could not read it. He provides
- a patch to fix the problem. -->
- Won-kyu Park ??ff ??? UTF-7 ??? (sfd.c ???????) ??ff ????? UTF-7 ??????????????????????? Python ????? UTF-7 ????????????ff ????????????????????????????????
- <LI>
- <!-- If we got an invalid second order spline, let's fix it up into some vaguely
- reasonable form, so the poor user doesn't keep getting errors. -->
- ??? 2 ?????????????????????????????????????????????????????????????????????
- <LI>
- <!-- Extra "-" in type42 header removed. -->
- Type42 ??????? "-" ????
- <LI>
- <!-- The anchor dialog was all screwed up. -->
- ?????????????????????
- <LI>
- <!-- The test in show att that all components of a substitution existed failed
- to handle a trailing space. -->
- ?ATT???(S)?????????????????????????????????????????????
- <LI>
- <!-- Make page Up/Down work in Show ATT -->
- ?ATT???(S)?? Up/Down ?????????????
- <LI>
- <!-- Sometimes the simplify algorithem fails to converge. -->
- ??????????????????????????????
- <LI>
- <!-- When generating a tfm file the width (height, depth, ic) table was being
- scaled twice. -->
- TFM ?????????? (??????ic) ???? ? 2 ?????????????
- <LI>
- <!-- Remove a NaN that occurred when moving quadratic splines. -->
- 2 ??????????????? NaN ????
- <LI>
- <!-- Oops. The unicode code point of a glyph was restricted to BMP by Glyph Info
- dlg. -->
- ????????????????????? Unicode ????? BMP ???????????
- <LI>
- <!-- Werner gave me a font where the glyphs were not properly ordered. So you
- can't tell the length of a glyph by loca[i+1]-loca[i]. The data appear valid
- in spite of that. So put in a warning for this particular case (we were
- generating a warning, but it wasn't as meaningful as it might be.) -->
- ?????????????????? Werner ?????????????????????? loca[i+1]-loca[i] ????????????????????????????????????????????????????????????? (????????????????????????????????????????)?
- <LI>
- <!-- Make View->Show ATT aware of the mark attachment class info so it can
- show the classes. -->
- ???(V)?ATT???(S)??????????????????????????????????
- <LI>
- <!-- When interpolating to quadratic fonts where the two designs didn't match
- then the various possible errors gave us bad splines: Different numbers of
- points on the paths meant that the control points at the end (after we reached
- the end of the contour in one design but not the other) didn't match. Different
- designs meant that interpolating a line (with no control points) to a curved
- spline again produced nasties. -->
- 2 ???????????????????2 ??????????????????????????????????????????????????: ???????????????????????????????? (?????????????????????????????) ???????????????????????????(????????) ??????????????????????????????????????????????
- <LI>
- <!-- Drag and drop was broken. -->
- ????&?????????????
- <LI>
- <!-- Extend lookup flags support to include mark attachment classes (as defined
- in GDEF). -->
- ?????? (GDEF ??????) ?????????????????????
- <LI>
- <!-- Bad argument type checking on the AddAccent scripting command. -->
- AddAccent ??????????????????????????????
- <LI>
- <!-- Infinite loop in a rare case involving a flex hint at the start of a contour. -->
- ???????? flex ??????????????????????????
- <LI>
- <!-- The merge fonts command would crash. -->
- ???????????????????????????????
- <LI>
- <!-- Problems parsing some bare cff fonts. -->
- ?? CFF ?????????????????????
- </UL>
- <LI>
- <!-- 2-May-2005-->
- 2005?5?2?
- <UL>
- <LI>
- <!-- Add support for Mark Classes. -->
- ???????????????
- <UL>
- <LI>
- <!-- New pane in Font Info to create them -->
- ?????????????????????????
- <LI>
- <!-- New field in the feature tag dlg to use them -->
- ??????????????????????????
- <LI>
- <!-- Input/Output routines -->
- ???????
- </UL>
- <LI>
- <!-- Drag and drop was broken -->
- ????????????????????
- <LI>
- <!-- Infinite loop in some bizarre cases when generating a hinted opentype font. -->
- ?????? OpenType ????????????????????????????????????
- <LI>
- <!-- The Merge Fonts command was broken -->
- ???????(M) ?????????????
- <LI>
- <!-- The scripting command: AddAccent checked for the wrong argument type -->
- ?????????: AddAccent ?????????????????
- <LI>
- <!-- ff generated an error when loading some bare cff fonts. -->
- ff ????????? CFF ????????????????????????
- <LI>
- <!-- Store desired fontview sizes in prefs file -->
- prefs ????????????????????????????????????
- <LI>
- <!-- Add a tweak to make the mac's dynamic loader look for fink libraries -->
- Mac ??????????? Fink ??????????????????????
- <LI>
- <!-- Problems parsing bare cff cid-keyed fonts -->
- CFF ? CID ?????????????????????
- <LI>
- <!-- recognize that code page 932 is a variant of SJIS -->
- ?????? 932 ? SJIS ????????????????????
- <LI>
- <!-- The feature tag 'nutf' is an obsolete name for 'afrc' -->
- ???? 'nutf' ? 'afrc' ????????????
- <LI>
- <!-- Add a couple of new scripting functions -->
- 2 ????????????
- <UL>
- <LI>
- <!-- Int() which casts its real/int/unicode argument to int -->
- ??/??/Unicode ???????????? Int()
- <LI>
- <!-- UCodePoint() which casts its real/int/unicode argument to unicode -->
- ??/??/Unicode ? Unicode ??????? UCodePoint()
- </UL>
- <LI>
- <!-- scripting CharInfo no longer creates the glyph it is asked about -->
- ?????? CharInfo ??????????????????????????
- <LI>
- <!-- WorthOutputting/DrawsSomething can now be applied to the current selection -->
- WorthOutputting/DrawsSomething ????????????????????????????
- <LI>
- <!-- When using the freetype rasterizer don't do an automatic close of open paths. -->
- FreeType ??????????????????????????????????
- <LI>
- <!-- For SCWorthOutputting I used to check both that !widthset and width==em-size.
- Remove the em-size check, should be redundant and somethimes (marks) is wrong. -->
- SCWorthOutputting ?????!widthset ? width==em-size ???????????????em-size ???????????????????????? (???????) ???????????????
- <LI>
- <!-- The various FindBounds routines didn't pad stroked fonts appropriately -->
- ??? FindBounds ???????????????????????????????
- <LI>
- <!-- Discrepency in docs and code on spelling of scripting Auto[tT]race command.
- Accept both variants -->
- Auto[tT]race ????????????????????????????????????????????
- <LI>
- <!-- A debug statement was left in the ps interpreter -->
- PS ?????????????????????
- <LI>
- <!-- Make the help command look for japanese docs in the ja locale -->
- ja ???????????????????????????????
- <LI>
- <!-- Add a select fewer scripting command -->
- SelectFewer() ?????????????
- <LI>
- <!-- Fix some problems with custom encodings -->
- ???????????????????????????
- <LI>
- <!-- Support '\r' and '\r\n' as line-endings for backslash continuation -->
- ????????????????'\r' ? '\r\n' ??????????
- <LI>
- <!-- New version of Japanese UI -->
- ??? UI ???????
- <LI>
- <!-- The kerning pair dlg would sometimes fail to display a pair when searching
- on the second char of the pair. -->
- ????????????????? 2 ????????????????????????????
- <LI>
- <!-- Danish translation of some style names, courtesy of Anders Lund -->
- ?????????????????????Anders Lund ???????????
- <LI>
- <!-- Fix some problems with SJIS encoding -->
- SJIS ??????????????????????
- <LI>
- <!-- The point info dlg was quite unusable if you typed in somethng which wasn't
- a number -->
- ??????????????????????????????????????
- <LI>
- <!-- When in debug mode display pointer position in pixels -->
- ????????????????????????????????????
- <LI>
- <!-- Point Info had problems with order2 splines -->
- ???????????2 ???????????????????
- <LI>
- <!-- The instruction pane of the debug window was interpretting keystrokes it
- should not have -->
- ?????????????????????????????????????????????
- <LI>
- <!-- Peter Selinger has changed the way potrace is built so it no longer uses
- cygwin (it uses MinGW instead). This means ff can't pass it the name of a
- temp file as '/tmp/foo' because (on windows) /tmp is a cygwin fiction. So
- continue to put the file on cygwin's /tmp, but cd to that directory and then
- pass the bare filename. -->
- Peter Selinger ? potrace ???????????cygwin ?????????? (???? MinGW ????????)?????(Windows ??) /tmp ? cygwin ???????ff ????????? '/tmp/foo' ???????????????????????Cygwin ? /tmp ????????????????????????????? cd ????????????????????????
- <LI>
- <!-- Add some more greek PUA small caps -->
- PUA ???????????????????????????????????
- <LI>
- <!-- Add scroll bars to debug windows which lacked them -->
- ???????????????????????????????
- <LI>
- <!-- Add a gloss window which explains what a ttf instruction is going to use
- and what it is going to do. -->
- ?? TTF ???????????????????????????????????????????????????
- <LI>
- <!-- Was using the wrong accent to build cyrillic breves. -->
- ???????????????????????????????????????
- <LI>
- <!-- Remove the adobe private use defs from libgunicode and put them in fontforge. -->
- Adobe ??????????? libgunicode ??????FontForge ???????
- <LI>
- <!-- ff had problems reading pfm files containing kerning pairs using non-existant
- chars -->
- ff ????????????????????????? PFM ???????????????????
- <LI>
- <!-- Add pixels per em in register view. -->
- ?????????em ?????????????????
- <LI>
- <!-- No contours in twilight zone -->
- ????????????????????
- <LI>
- <!-- When generating tt fonts we did not set bit 8 in 'head'.Flags. This gives
- bad results when ppem is not an integer -->
- TT ??????????'head' ??????? 8 ??????????????????em ?????????????????????????
- <LI>
- <!-- When reencoding to adobe standard (or any encoding where glyph names are
- more important than code points) make sure we use glyph names rather than
- code points (so "f_i" is not in AdobeStd while "fi" is. But they map to the
- same code point). -->
- Adobe standard ???????????? (??????????????????????????????)????????????????????????????(???? AdobeStd ?? "f_i" ???? "fi" ?????????????????????????????????)?
- <LI>
- <!-- When creating a debug window in a glyph with no instructions (or in which
- 'gasp' has turned off hinting) we used not to rasterize it. -->
- ??????????????????????????? (??? 'gasp' ????????????????????)????????????????????
- <LI>
- <!-- Script/lang count was wrong in a number of places -->
- ????????????/?????????????????
- <LI>
- <!-- Oops, the transform dlg and menu both used the "round to int" string. Then
- I changed what it looked like in the menu, a change which is not appropriate
- for the transform dlg. Add a new string just for the dlg. -->
- ???????????????????????"??????" ???????????????????????????????????????????????????????????????????????????????????????????
- <LI>
- <!-- Tavmjong Bah added something to the "ypogegrammeni" list. -->
- Tavmjong Bah ? "ypogegrammeni" ??????????????
- <LI>
- <!-- Fix problems with multiple text fields in the same window all wanting input
- contexts (for input methods). -->
- ???????????????????????????? (??????????) ?????????????????????????
- <LI>
- <!-- We generated ligature code in morx for ligatures that were not worth outputting. -->
- ????????????? morx ????????????????
- <LI>
- <!-- Pierre Hanser points out that a recent change to SetWidth broke the scritping
- SetWidth command. -->
- Pierre Hanser ????? SetWidth ?????????? SetWidth ????????????????????
- <LI>
- <!-- Yet more effort to remove rounding errors from remove overlap. If a control
- point causes a slight overshoot we get an unexpected extremum very close
- to one of the en…
Large files files are truncated, but you can click here to view the full file