* 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...
PKGLOCALEDIR and which install their locale files directly under
${PREFIX}/${PKGLOCALEDIR} and sort the PLIST file entries. From now
on, pkgsrc/mk/plist/plist-locale.awk will automatically handle
transforming the PLIST to refer to the correct locale directory.
* 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.
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
