Re: [Devel] Dingbats in FreeType?

[James H. Cloos Jr.]

>>>>> "Keith" == Keith Packard <address@hidden> writes:

Keith> If you can provide a mapping from FT_ENCODING_ADOBE_CUSTOM to
Keith> Unicode, I can easily plug that into fontconfig which already
Keith> includes special handling for Apple Roman and MS Symbol
Keith> encodings.

The mapping is of course font-specific.  Below is for zapf dingbats
only.  I'm sure there are other useful fonts (such as Carta or Cheq)
that also show up as FR_ENCODING_ADOBE_CUSTOM....

Markus Kuhn's uniset package uses zdingbat.txt from:

ftp://ftp.unicode.org/Public/MAPPINGS/VENDORS/ADOBE/zdingbat.txt

That corresponds to the 1997 version of Adobe's afm file for ITC Zapf
Dingbats, but is not up to date with Unicode 3.2.

The earlier versions of Adobe's font, as well as URW++'s Dingbats,
leave 14 of the glyphs out of the encoding vector.  They are now
encoded in the 0x80 to 0x9f range in the font.  zdingbat.txt puts
them in the U+F8D7 - U+F8E4 range of unicode, but unicode 3.2 added
them as U+2768 - U+2775.  They retain the same relative order.

Adobe has this on their site, which looks to be up-to-date with 3.2:

http://partners.adobe.com/asn/developer/type/zapfdingbats.txt

but that only has the glyph names, not their order in the font's
default encoding vector.

I suspect the best choice for fontconfig is to ignore the encoding
vector in type1 fonts like dingbats in favour of using the glyph
names directly.  

-JimC