[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Devel] FIXED: pure CFF fonts and advanced widths
From: |
Tom Kacvinsky |
Subject: |
[Devel] FIXED: pure CFF fonts and advanced widths |
Date: |
Sun, 26 Nov 2000 11:49:31 -0500 (EST) |
Hi all,
I tracked the problem with weird horizontal advancements down to a
"bug" in the charstrings parsing code. I have commited a patch for
this -- let me know if it fixes your problems with pure CFF fonts.
It does for me. :)
Tom
On Sun, 26 Nov 2000, Tom Kacvinsky wrote:
> I have been seeing some of th same errors regarding advanced widths in pure
> CFF
> fonts taht Eric Blinn has reported. I can't seem to track it down, but I here
> is what I have found:
>
> If I take a OpenType/CFF font and extract the CFF table, the resulting pure
> CFF
> font does not display properly: all of the glyphs overwrite one another.
>
> If, on the other hand, I use ftview to display the OpenType/CFf font, the
> glyphs
> display properly.
>
> I tend to think that there is more metrics parsing going on for OpenType/CFF
> fonts than there is for pure CFF fonts. A quick scan of the code sort of
> enforces this view point.
>
> By the way, the code in t2parse, does not set decoder.builder.advance.x based
> on
> the advanced width given in a charstring.
>