Changes since the last release may be found by performing a "cvs log" command on the file stamp.c.
TEGEUS:
Tell me,
What is your opinion of Progress? Does it, for example,
Exist? Is there ever progression without retrogression?
Therefore is it not true that mankind
Can more justly be said increasingly to Gress?-- A Pheonix too Frequent
Christopher Fry, 1950
"The trouble is," he said, "is that things never get better,
they just stay the same, only more so.--
FaustEric
Terry Pratchett, 1990
PUSHB_1 1 2
would lose the second number and not complain. In fixing that, I broke the first. Now both should work (I hope).
Pairwise positioning lookups could also get their device table offsets screwed up.
fontforge.FontView.FontSize: 24
[a-z] a b => does nothing a b [a-z] => does nothing a b => substitutes
will only substitute of "ab" is a word all to itself.
Make the "+" operator concatenate arrays
[1,2] + [3,4] == [1,2,3,4] [1,2] + 3 == [1,2,3]
There was no objection.
I have now removed them.
I also made the SetPrefs scripting function sort of work if the user tries to set one of these (it will set the appropriate flags in the default option set used by generate).
The defaults of these flags were different on the Mac from everywhere else. This meant that a script could do different things on the Mac and on linux. That seems like a bad idea. I have changed things so that the default options setting for generate is always OpenType.
THIS IS AN INCOMPATIBLE CHANGE AND SCRIPTS ON THE MAC COULD NOW BEHAVE DIFFERENTLY.
Legacy programs will not work when given a font in the correct format. New programs should be able to handle either correct or broken 'size' features.
A few of Adobe's programs make use of the 'size' feature, and XeTeX does. I know of no others (besides font editors). Both intend to upgrade their programs... So this may be less of an issue than I initially feared.
FontForge should now be able to read in a size feature in either format and gives the user the option of producing 'size' features in either format on output.
Windows won't use a font where the codepages field is 0.
The first sets the start point of each contour to the leftmost point, while the second orders the contours by their leftmost points. This will slightly reduce the size of output charstrings. It will also make more things available to be put in subroutines.
Use the appropriate defn for the version we happen to be outputting.
Both will select all encoding slots containing the named glyph (or unicode value)
Earlier Changes
Changes to PfaEdit (predecessor to
FontForge)