Changes (Enhancements & Bug Fixes)
-
10-Dec-2003
-
When there were multiple features with the same tag (different scripts with
'kern' for instance) PfaEdit would produce multiple copies of the same lookup
instead of different lookups.
-
PfaEdit was not setting the right to left lookup flag bit properly for hebrew
(and presumably arabic) kerning
-
Remove overlap was coalescing some splines that it should not have.
-
Typo in expand stroke meant that some round line joins were really weird
-
5-Dec-2003
-
When changing the ascent/descent with fontinfo or scaletoem some of the OS/2
fields did not get updated properly.
-
The OS/2 TypoDescent field was set positive instead of negative.
-
Added two scripting functions SetTTFName and GetTTFName to give scripts access
to the truetype names as well as the PS ones
-
Patch from Kazuyuki. SetPanose didn't work when argument was an array.
-
New French translations from Pierre
-
$copyright didn't return the correct thing (Patch from Giuseppe Ghibo)
-
Kerning pair data for non-ASCII unicode characters did not get output properly
into SVG fonts
-
The AddATT scripting command did not add ligatures correctly leading to problems
when time came to generate a font.
-
23-Nov-2003
-
PfaEdit would crash if given an encoding for the locale which it didn't
understand
-
Center/Thirds in width from the font view would change the width
-
There was a synchronization problem and the truetype debugger window could
deadlock
-
PfaEdit failed to read a Contextual (but not Contextual chaining) Coverage
lookup properly.
-
10-Nov-2003
-
PfaEdit was crashing when loading a bitmap font with encoded characters outside
the range specified by the encoding (ie. a character 0x10000 in a unicode
BMP font).
-
Fixes for several memory leaks provided by Kazuki Ohta
-
Slight improvements to the View->Combinations->Ligature dlg
-
8-Nov-2003
-
Bug introduced 6-Nov, PfaEdit generated a bad 'loca' table when outputing
a ttf outline font with bitmaps.
-
PfaEdit was getting the truetype point number wrong when reading outlines
from an sfd file.
-
If the loca table was 2 or 4 bytes long, PfaEdit failed to warn about a bad
glyph count.
-
PfaEdit got confused if two truetype glyphs had the same name.
-
When dumping out embedded ttf bitmaps, PfaEdit got confused by the extra
glyphs (.null and return) and generated garbage.
-
Make View->Combinations->ligature dlg a bit better for non-latin glyphs
-
6-Nov-2003
-
The clut used for drawing anti-alias bitmaps in the metrics view was wrong.
-
In a bitmap only ttf file, PfaEdit was usually producing bad line spacing
data as far as the mac was concerned.
-
When importing bitmaps into an empty font, we might as well change to font
view to show the bitmaps rather than the empty outline data.
-
If glyph 0 was selected in the fontview then the File->Open Outline command
was disabled.
-
With a user defined encoding we were again getting occasional crashes.
(introduced by my work on bitmaps)
-
On certain glyphs, the optimizer introduced an slight error when calculating
a spline's coefficients from its control point. Even though this error was
on the order of 7e-8 it was enough that the rasterizer produced grossly incorrect
results. I have pulled the relevant routine out into its own file which is
now compiled by itself without optimization.
-
4-Nov-2003
-
When PfaEdit removes glyphs with Font Info->Encoding->Number of characters,
it will now run through the font and remove any ligatures, substitutions,
etc. refering to non-existant glyph names.
-
Some improvements to remove overlap.
-
Added a warning message so that when user attempts to output a ttf file where
no characters have unicode encodings, then the user at least gets warned
that the result will probably not work. For fonts with fewer than 256 glyphs
it will offer the choice of a symbol encoding.
-
If a reference were copied in the outline character view and pasted into
the font view, pfaedit would crash.
-
the expand stroke patch on 29-Sept broke caligraphic and elipse modes.
-
The mouse's scroll wheel did not work in the metrics view.
-
The metrics view resized very slowly under window managers which do continuous
resizing.
-
Give the magnifying glass's rectangle mode a threshold so that it doesn't
resize tiny rectangles which are really caused by mouse gitter.
-
Attempt to set a zoom size for character and bitmap windows, but modern window
managers don't seem to support the old protocol, and I can't find docs on
a new version.
-
Was not converting filenames to unicode properly for the open/generate progress
dlgs.
-
PfaEdit would crash when attempting to draw a character for which in had
no (X11) glyph when doing bidirectional text.
-
29-Oct-2003
-
When removing an ATT feature from a glyph using a script, PfaEdit would screw
up memory. Leading to unpredictable results.
-
28-Oct-2003
-
PfaEdit would crash when converting from cubic to quadratic splines in a
script
-
PfaEdit would leave a dangling pointer when converting from cubic to quadratic.
This did not affect ttf generation, but would affect most other opperations.
-
27-Oct-2003
-
PfaEdit would crash when changing the encoding of a font with a .notdef character
to a user defined encoding.
-
If one had multiple ligatures for the same glyph with the same tag and script,
PfaEdit would eat all but one of them.
-
When generating most kinds of font, of a font which had ligatures containing
glyph names that were not in the font, then PfaEdit would often screw up
memory and eventually crash.
-
26-Oct-2003
-
Simplify sometimes removed points at extrema even when it should not have
-
If one had a ttf font (with instructions) and merged in a postscript font
and then generated a ttf font, PfaEdit would complain about an internal error,
but go on to produce a valid font. It should no longer complain.
-
When generating fonts from a script, if the font were in compacted format
the generated font would have a compact encoding (instead of the desired
encoding).
-
Kanou provided a patch to speed up importing bitmap fonts.
-
23-Oct-2003
-
The change on the 20th to make custom encoding support 32bit unicode was
incomplete and made custom encodings crash instead.
-
The File->Display dialog ignored the left-sidebearing of a glyph causing
output of some fonts to look awful.
-
Was getting the AdobeStandardEncoding a bit wrong (after the 5-Oct change
to the new unicode glyph list which does not contain "fi" nor "fl")
-
I used to set the "widthset" bit on .notdef characters, but there's really
no point to that.
-
Maxim Iorsh tells me that U+fb4f should be a historic ligature.
-
On some displays right scrolling the Histogram dlg would leave black lines
on the window.
-
AutoHint removed too many stems from consideration as hints on some very
bold fonts
-
Make FontBBox of Type1 fonts be executable. Adobe says it doesn't have to
be, but dvips expects it to be.
-
20-Oct-2003
-
Windows XP & 2000 insist on having (what cygwin describes as) the execute
bit of the file set. So PfaEdit now sets execute permissions on ttf, otf
and pfb fonts on the cygwin platform.
-
If a menu was so big that it had to be positioned over the menubar (instead
of above or below it), and the user clicked on the menubar to invoke it,
then the mouse release would go to the new menu and invoke whatever item
happened to be under the cursor. Not good.
-
Oops. The Effects sub-menu should have been disabled for quadratic (truetype)
fonts.
-
Added a new configuration option --with-regular-link to disable my dlopening
of libraries. I dislike this. I don't think it is anywhere near as flexible
as the dlopen method. It makes it much harder to ship something that will
work with freetype (detecting whether the bytecode interpreter is present
must be done at link time rather than run time and that is a severe disadvantage.
But I have been asked for it.
-
Change internal format so that custom encodings can handle 32 bit unicode.
-
16-Oct-2003
-
PfaEdit was still outputting a disordered name table.
-
The source tarball on the website included many files twice and some files
that it should not have included at all. I should now be less than half the
size it used to be.
-
15-Oct-2003
-
PfaEdit did not bother to open files in binary mode. If cygwin was configured
with DOS linebreaks, then pfaedit failed to generate valid font files on
cygwin.
-
Added some more warnings to the default build list and fixed the problems
they indicated.
-
12-Oct-2003
-
Several bad bugs in last night's build (name table was (usually) all screwed
up, conversion from PS to TTF got incorrect Internal Error msgs)
-
Order tables in truetype output
-
My 5-Oct-2003 libpng fix broke it completely. Should now be refixed.
-
11-Oct-2003
-
Another patch from Kanou to recognize encodings better in bdf files.
-
Various memory fixes found by valgrind
-
The Element->Find Problems->ATT->Missing glyph names fixup dlg had
some formatting problems and failed to skip properly.
-
Draw an "x" through encodings which do not map to glyphs
-
If the user is in a compacted encoding and asks to print a font, then revert
to the uncompacted encoding for the duration of the printing.
-
View->Show ATT would show ligatures (and substitutions) even if some of
the glyphs in the glyph list were missing.
-
Fix a number of bugs found by the MS Font Validator
-
I misunderstood (and the spec incorrectly documented) the behavior of the
maxp table
-
I had a typo in figuring out the OS/2 table
-
I had one more case where I was computing the point count of a glyph incorrectly.
-
Make the width line snap to zero when the user drags near it.
-
6-Oct-2003
-
Give the Metrics View a vertical mode in which it does vertical kerning,
etc.
-
Add a hack to allow PfaEdit to parse a wierd pfb file.
-
6-Oct-2003
-
Fixed a number of bugs in the new kerning class dlg including:
-
Vertical kerning classes were displayed horizontally
-
When adding a new class the new offsets were garbage
-
The routine to convert a horizontal kerning class to the equivalent vertical
kerning class (of the vertical varients of the glyphs in the horizontal class)
didn't work.
-
In Back and Lookup Classes of a contextual chaining substitution by class,
the [New] button was never enabled. (it was disabled if []SameAs was on,
and then never enabled).
-
My new 94x94 encodings were actually 93x93. Patch by kanou.
-
5-Oct-2003
-
Got rid of GreekFixup and added Interpretations of encodings to FontInfo
-
PfaEdit failed to output ligature substitutions nested under a context/chain
sub
-
If a font had more than about 5 nested ligatures, pfaedit would screw up
its memory and (likely) crash
-
Fixed various problems pertaining to adding a kerning class to an empty font
-
Add a runtime check for the case where the user's system has a dynamic libpng
installed without libz
-
If a character had ligature carets then PfaEdit could crash when determining
its script
-
PfaEdit was reading mac 'kern' format 3 incorrectly.
-
Rewrote the Kerning class creation dialog. I hope it is clearer now.
-
2-Oct-2003
-
got rid of my strange 94x94 encodings for JIS/KSC/GB (based on the kuten
array) and used instead the much more obvious encoding that everyone else
uses.
-
BDF files were output with the wrong encoding name for JISX0208 (I was outputting
"JISX208" instead-- missing a "0").
-
Autotrace failed to read potrace output properly if there were more than
one contour in a given glyph.
-
Upgraded psunicodenames to the current Adobe Glyph List for New Fonts.
-
Simplify now works for quadratic splines. If one uses the []Allow Slopes
to Change checkbox then results are not good. I need a better algorithem.
-
If asked to generate a type0 postscript font for a font encoded with an extended
1byte encoding (ie. one that had about 300 characters) PfaEdit would probably
crash.
-
29-Sept-2003
-
When a path was both stroked and filled (in a postscript/eps file), pfaedit
would ignore the stroke.
-
I forgot that the stroke linewidth needs to be transformed by the current
transformation matrix. This meant that when a path should have been stroked
by an ellipse (when reading a ps/eps file) pfaedit would blithely stroke
it with a circle.
-
Added some support for reading the /Metrics array.
-
If there were a sharp corner (where the "radius of curvature" of the corner
was less than the radius of the pen used to stroke the path) then PfaEdit
would generate an incorrect path.
-
Round line joins were not a good approximation to circular arcs.
-
When filling the outline character view, rounding errors caused the fill
bitmap to stray from the outline.
-
Extend the functionality of the magnifying (or minifying) tool so that if
the user drags out a rectangle with it then the view will be shifted and
scaled so that rectangle fits in the window.
-
PfaEdit will no longer auto-generate hints on non-integral boundries. In
Type1 fonts such hints become meaningless and just confuse things.
-
PfaEdit will now draw a halo around points which will be part of a flex hint.
See the UpdateFlex preference item.
-
PfaEdit now has as set of commands for manipulating typographic features
in large lumps rather than one at a time.
-
Copy features from one font to another
-
Remove certain features
-
Give features a new tag
-
I have greatly rewritten the code for dealing with AAT fonts
-
PfaEdit now supports mac feature/setting values to be used as feature tags
as well as opentype 4 letter tags
-
PfaEdit will now read any feature in even if it doesn't map to an opentype
tag
-
PfaEdit understands the most of the state machines in the morx/mort tables
(it does not understand ligature state machines, it parses these for all
unconditional ligatures, but it will miss any condtional ones).
-
PfaEdit now lets you edit apple state machines
-
PfaEdit lets you specify feature/setting names in the font to override the
default values specified in preferences
-
Added support for reading Apple's format 3 kern sub-table format (another
way of storing a kerning class)
-
Oops. SVG didn't read relative movetos properly in a path option. Patch by
Kengo Ichiki.
-
Simplify had a bug when passed a path which consisted of a single point with
a zero length spline connecting it to itself
-
Simplify was not greyed out properly in quadratic fonts
-
Some of the low-level error routines consumed massive amounts of cpu time
while waiting for events
-
The PostScript parsing routines would sometimes think that "noaccess" was
part of the value of something in the private dictionary.
-
Several other patches to importing images by templates from scripts. By Kengo
Ichiki
-
Importing pcf bitmaps into the background had some problems.
-
4-Sept-2003
-
the 17-Aug addition of context/chaining broke anchor classes. Should be fixed
now.
-
Károly László has added Hungarian translations for the
style codes to Font Info->TTF Names
-
If a font had comments, an svg file generated from it had syntax errors.
-
Add support for generating multilingual strings (in 'name') for the apple
platform.
-
Add support for the packed gb2312 which mac and windows seem to use.
-
Make a UniqueID of -1 in Font Info mean that the font has no UniqueID.
-
Earlier Changes