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 Phoenix 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
There is also a python command font.generateTtc()
File->X Resource Editor...->FontView->Font Size
was
supposed to allow the user to set the size of the glyph labels in the fontview.
It didn't. Fixed.
Sadly the preference item wasn't very smart and turned off names like uE001 as well. Fix that.
If you have an entry like:
msgid "CV*Open|Ctl+O" msgstr "Super+O"
then that will rebind Open in the charview and nowhere else.
Note that the string "CV*Open|Ctl+O" will not appear in the pot file, you must add it manually if you want to do this (that's because I don't want people to do this).
If you have a rebinding for
msgid "Open|Ctl+O"
and no entry for "CV*Open|Ctl+O" (ie. the common case) then all menus (including the charview) will follow the standard rebinding.
I hope I have worked around this by adding a preference item
File->Preferences->Generic->ExportClipboard
Turn this Off if the clipboard doesn't seem to work.
Peter Baker says that a solution is to go into X11 Preferences, click on the "Input" tab, and uncheck "Enable key equivalents under X11".
Possibly downloading a new set of developer tools will fix it:
http://developer.apple.com/Tools/ (then log in, (or become a member & log in, it's free)) Click on Downloads In the "Downloads" side bar, click on "Developer Tools" Download and Install 3.1.3
Together these meant that ff did not use appropriate command keys in the
menus.
I wish Apple wouldn't do pointless changes.
Extend this a little so the user can specify a range of y values (return the extent in x when y is between ybottom and ytop).
And that appears not to be what he wants anyway. Oh well.
I wish to thank Michal Nowakowski for fixing my bugs these last few months.
I no longer have as much time for FontForge as I have in the past, and my
attention to the project is spotty.
Currently I am training to run a 50 mile race (~80K) to celebrate my 50th birthday this year. I've already run a 50K race as preparation. |
Element->Other Info->Justification
.
FontForge now supports the 'BASE' table (in feature files).
The new format is considerably better than the old and can now be used to express almost all of OpenType.
Changes:
Apple appears to have shipped a buggy version of X11 with 10.5. The problem
appears fixed in 10.5.6 (It may have been fixed earlier, but I don't have
a machine on which I can test that).
The problem only affects fontforge it if uses pango or cairo. This release of fontforge tries to check for a buggy system, and if it thinks it is running on one, then it will refuse to use Pango and Cairo. The problem does not affect Mac 10.4.* You may upgrade from 10.5 to 10.5.6 by going to the Apple Menu and selecting the "Software Update" menu item, and then the "Mac OS X Update Combined". You probably need to install X11 before you upgrade the Operating System. |
Cairo will draw anti-aliased lines and splines (and text as well). Cairo also supports translucent colors.
If you have an old release of pango then it may not be able to draw on top of cairo, in which case you won't see complex scripts drawn properly in the outline glyph view (the only view in which cairo is active).
Start up is slower with either Pango or Cairo active because both use fontconfig to initialize stuff and that can take time.
Cairo, and to a lesser extent, Pango can slow down drawing. Especially if you use X across a wire (on a display not connected to your computer). The slowdown depends to some extent on your video card, driver, X release, etc. If you find these libraries too slow to be useable you may turn either off in Preferences. (You may also turn them off at configure time).
The first time fontforge starts with pango (I think it's pango) enabled, initialization is very slow -- several minutes -- do not be alarmed, it only happens once.
Pango crashes on my cygwin system, so my cygwin build does not ship with either pango or cairo.
The version of cairo available from fink on the mac (1.0) is too old for it to work with fontforge (which needs at least 1.2). So the mac builds do not ship with cairo.
The default initialization of fontconfig on the mac doesn't seem to find any fonts. You should create a ~/.fonts directory and drop into it the fonts you want to be displayed.
Created a teeny tiny translation file for Malayalam.
Gdraw.GGadgets.ImagePath
Add new commands to select glyphs which
In both "Show Grid Fit" and the TT debugger it used to be possible to turn off the display of outlines in the foreground layer simply by unchecking "fore". Now it can no longer be done, and as a result it's become more difficult to check at a glance the overall effect of TT instructions. It would be nice to have this capability back.
Adjust the width to length ratio used to determine if a diagonal stem is acceptable.
Also if we didn't save the background layer (layer=0) then a random layer would (inappropriately) become the background.
Extend the 'layr' format to store a background/foreground flag per layer.
Remove the hack that if the modifier mask for the command key was set then we'd also set the control mask (this meant that the command key would work as control, but it meant it could only work as control).
Let the command key work as itself, and put in special code to check whether X11 is going to give us the command key (or will that key be used in the X11's own menubar). If we get command then we load a special set of keymap bindings (which, presumably, will use command). If we don't find a special set of keymaps, then fall back on normal processing.
Clean up drag and drop from the font view a bit.
My approach failed if the lookup contains multiple subtables and a base glyph has two marks being attached, one from each subtable -- I would attach the mark in the first subtable, but then having found a subtable that worked would stop, and the second mark never got attached.
![]() |
![]() |
Changes to create a stub Mac application. Add an apple event handler to fontforge so that it will notice when the finder wants it to open files. Add icons, etc. so it will look like a mac app.
With layers that should all change. We should only set the width if there is nothing in any of the potential foreground layers. Don't count the background layers or the grid psuedo layer. Don't count open contours (might be a secondary guide line layer or something). If we're going to clear a layer before pasting (normal behavior in fontview) then don't count the layer cleared.
Also allow the user to specify exactly how many ligature carets s/he wants rather than just setting a minimum bound.
Also 'lcar' (Apple) output was broken.
Also neither AAT nor OpenType supports negative lig carets, so if the user drags a lig caret line negative, have it stick at 0.
We don't generate version 4 yet, and we won't for a while. Version 4 will include the ability to insert backslash newline into long lines. This is so we can conform to the internet requirements of fewer than 990 bytes on a line. And the delay is so that people don't scream at me for making an incompatible change to the format -- if I give the parser time to perculate through the user community, with luck no one will even notice -- especially as long lines are rare.
Actually it's worse than that, the spec says that if there are too many things on the stack then start parsing the stack from the unexpected end.
Adobe have admitted that the obvious reading of their spec is incorrect (they can't quite bring themselves to say the spec is wrong). So revert some of the way we were parsing type2 charstrings.
(Only do this if font doesn't use these areas).
Fix a couple of other foreground specific things too.
Do something similar for bad transformation matrices (those with members 2 or more (or less than -2)).
(setting is sticky).
glyph.altuni
either None, or a tuple of tuples, one sub-tuple for each alternate. each sub-tuple is (alternate-unicode, variation selector (or -1), reserved for future=0 now).
Provide some icons
Also update the install procedure to put them in the right place.
Preference item containing a directory from which to read icon files
(also boxify the Find Problems dlg).
Also add a bookmark (and back/forward) mechanism.
$ fontforge
http://openfontlibrary.org/people/Nasenbaer/Nasenbaer_-_Widelands.ttf
Also, was a crash bug when mixing a font with a baseline table and a font without one (in the disply dlg).
Element->Insert Text
Outlines)
It adds the text outlines directly (instead of a draw command
using another font) because most fonts can't include text drawing in their
glyphs. Also include a Bind to Path variant.
This could be used to produce a grid of guidelines, or, in conjunction with
Element->Overlap->Intersec
t it could provide a poor man's
"Pattern Fill" (Since Pattern fills are only available in type3 fonts this
sort of makes them work for any font type).
Add python scripting (font.horizontalBaseline, font.verticalBaseline) too.
Add support under Show ATT.
Remove the old vertical origin field.
./configure --enable-type3
is specified, of course.
Also add support for cliping paths
Make fonts containing images work in pdf output.
Earlier Changes
Changes to PfaEdit (predecessor to
FontForge)
Changes to the sfd format.