* Support composites (references) in bitmap fonts.
* Support for the JSTF table (sfd extension).
* Added a set of new python functions for manipulating CID keyed fonts.
* Added support for reading/writing version 1.8 of Adobe's feature file format.
* Check for a buggy system on Apple 10.5 with X11.
* Fix more memory problems in Merge Fonts.
* If a font were missing a .notdef glyph. If the user tried to display
a font sample of text which included a character not in the font.
Then (after the recent patches for grid-fit metrics in Print dlg)
fontforge would crash.
* Fix a bug in old cubic to quadratic conversion.
* Lots of changes to extrema code.
* Initializing the font info dialog crashed on the mac when -O2 was
specified during configure (the default situation).
* After adding an Apply button the Transform dlg would crash if invoked
in a glyph with no undoes.
* Add an X resource editor.
* Make the metrics view be more like the display dlg in that you can specify
a point-size/dpi to view stuff (also include increment/decrement pointsize).
* Patch by "JustFillBug" to exend python scripting by making the find
interator become a find/replace iterator.
* Patch by Taco to fix a memory problem reading bad baseline data.
* Patch from Andrey PANOV to extend GlyphInfo (legacy scripting) by adding
"XProfile" and "YProfile" options.
* Add an [Apply] button to the transform and expand stroke dialogs in
the outline view.
* Make ff parse preference files independent of the decimal point local in
which they were written (that is -- accept either "." or "," in floating
numbers).
* If a Cubic layer had a notdef glyph, then sometimes, rasterizing using
freetype would fail (not a freetype problem, I didn't set things up right).
* Fix one more problems with points being snapped to a wrong stem side
(it was still possible in case of off-curve points).
* Metrics View and Display dlg weren't showing grid fit metrics properly.
* First release with Pango and Cairo
* The first time you run fontforge with Pango something takes several minutes
to initialize itself. This delay does not occur on subsequent invocations.
* Displaying magnified bitmap strikes in the font view often caused a crash.
* Non-English translations of "%d pixel bitmap" in the View menu of the font
view came out garbled. There were interpreted as latin1 rather than utf8.
-While the program is prepared to work w/o libxml2 (with some loss of
functionality), there is a little glitch -- see PR pkg/38446 by
Keith Waclena. The fix shouldn't be needed for pkgsrc anymore because
libxml2 should be found now, but add it anyway.
bump PKGREVISION
* Add support for Adobe's feature file syntax.
* Add a popup menu to the lookups pane of font info.
* Change the name of File->Merge Kern Info to File->Merge Feature Info
* Remove the code to produce the old, broken, 'size' feature.
* An earlier patch, designed to make the tabset work in the charview even if the user changed the name, didn't work.
* Bug in the selection iterator.
* Accept contour += (1,2) rather than forcing people to say contour += fontforge.point(1,2)
* Crash when mistyping a glyph name in Glyph Info possub panes. Probably in the equivalent lookup dlgs too.
* If a glyph contained two copies of another glyph, and one of those copies was off by enough that ff didn't recognize it, the depending on how the contours were ordered, ff might fail to recognize the first glyph too, even though it did match.
* Add iterators to contours and layers. Python users seem to expect them even when they aren't documented to exist.
* layer += contour didn't work in python. I was examining a bit through the wrong data type.
* Provide a mechanism for copying lookup information from one glyph to another. (Edit->Copy Lookup Data)
* Loading kerning info from a mac 'FOND' resource was broken by the lookup change.
* Python scripting command font.createChar didn't. Partial patch from Max Rabkin.
* Adding a kerning pair from the metrics view would often add two or three pairs with the same character combination and different values.
* Another remove overlap bug. Introduced recently.
* Reinstate Apply Substitutions scripting command.
* Add some dutch styles.
* Make yet another attempt to correct for rounding errors when loading a postscript font.
* Add a way to get a font's filename to python.
* Werner points out that in scripting I use "break" in an example. It isn't documented to work and I don't implement it but I do show it. Oops. Ok, make it work.
* Display substitutions was broken.
* When generating default names for subtables, it is confusing to name them the same as the lookup.
* Change to using USC4 from UCS2 internally.
* Provide default names for lookups once the user sets the feature.
* Disambiguate some strings for the polish translation
* Revert glyph should not work for old sfd files.
* Initial Greek translation.
* Add a pane to the Preference dlg allowing user to control some of fontforge's
hint creation.
* Update my opentype scripts list (in particular include music).
* Due to a typo, ff thought pretty much everything outside unicode BMP was in
the hebrew script.
* Add a new command to the point menu which allows you to specify a spline and
one coordinate (either X or Y) on that spline. FF will calculate the other
coordinate and add a point there.
* CODE2000 contains an anchor class with only base glyphs (no mark glyphs) as
part of a set of anchor classes. FF crashed.
* More...
* FF failed to output lookups in the right order for the GSUB table.
* FF would crash when attempting to generate a font which had no familyname
* FF could be built agains ft2.2 only if the debugger were being built.
Make it work always.
* Patch by Mike Frysinger from gentoo. Use the HOME environment variable in
preference to /etc/passwd.
* Write sfddiff as a fontforge script and put it back into the install process.
* Add code to font compare so it can do the old sfddiff --merge option.
* Someone wanted acorn2sfd! Make it compile again.
* Make configure look for libgif
* Extend to Unicode 4.1
* Context chain dlg had problems with empty patterns (no terminal NUL in empty string used to represent them)
* EditData button in contextual subs disabled at wrong times.
* Transforming by a negative scale factor screwed up the hints.
* Add move up/down buttons to the kerning class dlg (class lists area) Use the selection from the class lists to highlight offsets.
* Print sample did not handle kerning by classes.
* 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.
* When changing lists they should not scroll back to the beginning.
* 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.
* Apply Substitutions was badly broken when ff compiled with multilayer.
* Kern Pair dlg looked at garbage memory when it closed (and crashed sometimes).
* 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.
* One more attempt to rule out absurd results in simplify().
* if the lsb/rsb dlg was given a negative value it complained about negative widths. (whether the width would have been negative or not).
* $italicangle has been broken since I added reals to scripting.
* The kernclass dialog did not handle deleted classes properly.
* Add ability to undo hints.
* Once again starting a browser on windows is broken.
* 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.
* An open path consisting of a single point caused replace with reference to crash.
* Generating a postscript resource font on the mac from a script did not work.
* Werner points out that afm files generated by FontForge still claim to have been made by pfaedit. Oops.
* Didn't parse user defined encodings properly and often omitted the first glyph.
Changes 20041115:
* If ff started without a prefs file, then creating a new font would crash
* If a copyright string contained a newline then ff would generate bad
postscript
* If user added a comment to an empty glyph then the comment wasn't saved in
the sfd file.
* If ff saved a utf7 string to an sfd file (ttf names, etc.) and that string
contained a hyphen that followed immediately after something that needed to
be encoded in base64, then the hyphen would be lost.
* new french UI
* ff was (usually) setting the ascent/descent fields of the 'hhea' table to 0.
When the font was drawn on the mac it was clipped to nothing.
