[Devel] Re: FIXED: pure CFF fonts and advanced widths

[Tom Kacvinsky]

I think I figured it out -- it has to do with line advance.  But my "real" job
beckons right now (paperwork -- ugh!).  I know more later...

Sorry for mistyping your name!

Tom

On Mon, 27 Nov 2000, Blinn, Eric W wrote:

>
> Thanks Tom. I tried your fix. It cleaned up the glyph metrics problems
> nicely.
>
> You mention still having some pure CFF fonts that don't display properly.
> I'd be interested to know what additional problems you are seeing.
>
> > ----------
> > From:       Tom Kacvinsky[SMTP:address@hidden
> > Sent:       Monday, November 27, 2000 2:41 PM
> > To:         address@hidden
> > Subject:    [Devel] Re: FIXED: pure CFF fonts and advanced widths
> >
> > Well, this fixed the problems that Eirc Blinn reported with example.cff
> > (excepting the horizontal flip), but I still have some pure CFF fonts that
> > don't
> > display properly.  I don't know what is going on...
> >
> > Tom
> >
> > On Sun, 26 Nov 2000, Tom Kacvinsky wrote:
> >
> > > 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.
> > > >
> > >
> > >
> > > _______________________________________________
> > > Devel mailing list
> > > address@hidden
> > > http://www.freetype.org/mailman/listinfo/devel
> > >
> >
> >
> > _______________________________________________
> > Devel mailing list
> > address@hidden
> > http://www.freetype.org/mailman/listinfo/devel
> >
>
> _______________________________________________
> Devel mailing list
> address@hidden
> http://www.freetype.org/mailman/listinfo/devel
>