>>>>> "Juliusz" == Juliusz Chroboczek <[EMAIL PROTECTED]> writes:

Juliusz> I'm still not getting anything close to what you claim:

I'll be posting the pfaedit generated ttfs later tonight.  George
fixed a bug that was making it more difficult than necessary to
generate the scripts to automate conversion -- and did so w/in just a
few hours of when I posted the report; gotta love free/open software.

JC> Is there any benefit to a bdat table over a EPDT table?  pfaedit
JC> also shows sbit as an option,

Juliusz> The TTF spec doesn't document either.  I'll have a look in
Juliusz> the OTF spec and the GX documentation (if I can still find it).

I beleive apple still has it all online; I was very recently pointed
to some of that doc from a post on, I suspect, the opentype list.

Juliusz> Do you know what is implemented by FreeType 2?

ftview has no problem with EPDT+EBLC or bdat+bloc type ttf files as
generated by pfaedit, but does not see the bitmaps in either format
otf files as generated by pfaedit.  The only difference is a glyf
table with entries that look like this when ttdumped to ttx:

    <TTGlyph name="J"/><!-- contains no outline data -->

vs a CFF table with entries that look like this in ttx:

        <CharString name="J">
          -190 endchar
        </CharString>

(Note that not all have negative args to endchar) and that the CFF
versions do not have cvt or loca tables.  It is probably the lack of
one of those two tables that keeps ftview from displaying the bitmaps
in the otf versions.

Expect a URL for the four variations of at least most of the bdf fonts
in xfree86's cvs w/in the next twelve hours.

-JimC

_______________________________________________
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts

Reply via email to