Re: Making dummy fonts

On Tue, 2006-08-01 at 02:59, Peter B. West wrote:
> The AFM files in
> question are indeed as you describe.
Good. Sorry, I was confused by your use of base14 and was reading it as
a file format rather than specifying which afm files you had. My bad.
> So far, all of this is Adobe Standard encoding, accodring to the header.
> 
> There is also a Symbol font, and ZapfDingbats. The names in Symbol are
> recognizable glyph names- Pse Zeta bracketleft - but the ZapfDingbats
> font uses "aNNN" ranging from a1 to a205, with some gaps. Both specify
> teh encoding as FontSpecific. I assume that Symbol is the "Symbol"
> encoding, but what about ZapfDingbats?
> 
> Do I need an encoding file? Can I specify the use of a standard
> encoding?
You don't need an encoding file for Adobe Standard nor for Symbol, those
are built in to fontforge. FontForge does not have an encoding for
ZapfDingbats, so you'd have to make one of those. It should look like
        /ZapfDingbats [
        .notdef
        .notdef
        ...
        .notdef
        space
        a1
        a2
        a202
        a3
        ...
        a191
        .notdef
        ]


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV