|
|
"GG" == Giuseppe Ghibò writes:
GG> BTW. Since you used TeXtrace, and FontLab, I would like to point
GG> out about MF -> Type1 conversion. There is another tool (although
GG> it has several restrictions) called mf2pt1 (on CTAN:support)
GG> allowing such kind conversion (resulting is more precise than
GG> tracing [although has overlaps] because has fewer nodes, and thus
GG> files shorter),
yes, i know about mf2pt1, and it could not convert arbitrary METAFONT
fonts, because it uses METAPOST (which does not support some features
of METAFONT).
GG> and there is also a freeware font editor, called PfaEdit, at
GG> http://pfaedit.sourceforge.net, which has TWO interesting
GG> features:
GG> - 'Simplify': simplify the fonts reducing the number of
GG> unneeded nodes, make PFB file shorter.
GG> - 'Remove Overlap': remove overlaps in font paths.
i used FontLab to simplify (optimize), remove overlaps, and autohint
the fonts. i'm not sure that PfaEdit will give better results than
FontLab.
The current fonts are already quite short, e.g. they are about the
same size as commercial Type 1 EC fonts provided by Micropress, Inc.
This comparison was made on fonts which contain only glyphs from EC
fonts, because CM-Super fonts contain much more glyphs than fonts from
Micropress.
And there are possibilities to make the fonts even more short, which
will be used in next versions: move definitions of glyphs with the
same shape into subrs, and construct accented glyphs from non-accented
and accents via subrs.
GG> The second question is. Is there a table about choosing the
GG> UniqueID to be used for each of the Metafont fonts converted to
GG> PFB? If not how about to write one?
I'll add such a table.
Best,
v.
|
|