lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Fontforge-devel] Re: UTF8 and (La)TeX backend?


From: Han-Wen Nienhuys
Subject: Re: [Fontforge-devel] Re: UTF8 and (La)TeX backend?
Date: Wed, 5 Jan 2005 00:40:56 +0100

address@hidden writes:
> On Tue, 2005-01-04 at 14:11, Han-Wen Nienhuys wrote:
> > Hmm. I'd say it should contain all info from the TFM 
> > 
> >   * metrics (these are entirely unrelated to the extents of the
> >     outlines)
> The advance widths have their natural place.
> Height/Depth information:
>    Per glyph Bounding box information is stored before every glyph in a
>    tt file (more accurately than in a tfm file). These data are not
>    stored in a cff file but are easily calculated from outlines.

Then they have to be there in the CFF separately. The H/D can be
different from the outlines, eg. due to overshoot. 

> >   * 30 spacing parameters
> I'm not sure what you mean by this. Are these the font parameter words?
> If so there may be 8 or 23 or 14... Oh, perhaps I see, if you don't
> overload them then there are 30 of them.

in my TFM reader it says,

        /* The maximum number of global font parameters we allow.  */
        #define TFM_MAX_FONTDIMENS 30

I guess they're font parameter words.

> >   * checksum
> Why? It has no meaning in an sfnt. Sfnts have their own checksums.

Hmm. Good point. TeX reads checksums when it writes DVI files. I
suppose that they're moot as long as TeX itself doesn't read Sfnts 

> Any thoughts on a tag for the table? "TEX ", "TeX ", "TFM " ...

TeX seems nice.

-- 

 Han-Wen Nienhuys   |   address@hidden   |   http://www.xs4all.nl/~hanwen 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]