Re: [Freetype] Ambiguously Undefined Glyphs [was: Mozilla needs some info on Xft]

[David Turner]

Hi J.,

> It is difficult to say without seeing a dump of the relevant parts of
> the fonts, but I'll take a guess.  Assuming that the AUGs' cmap
> entries point at valid loca entries, and that the loca entries point
> at valid glyph data (you have checked that, haven't you?), I'd be
> tempted to believe that they're trying to optimise the size of a type
> 4 cmap by having non-zero cmap entries that are aliased to the
> undefined glyph through the loca table.
>
I suspect they've simply been lazy. Most probably, the glyphs were
taken out of the original font by simply changing the content of
the "loca" and "glyf" table in the most simple way. You can do
that with a rather simple C program, or even a Perl script..

On the other hand, changing the charmaps is much, much different.
Re-ordering the glyph indices within the whole font is even more
problematic :-)
 
Cheers,

- David