Re: [ft-devel] Incomplete cmap table for platform 0 (Apple Unicode)

[Dmitry Timoshkov]

"George Williams" <address@hidden> wrote:

> On Sun, 2007-09-30 at 20:16, address@hidden wrote:
> > As I've shown in previous post, Apple Unicode cmap in the
> > sample font is NOT broken from the viewpoint of data
> > structure, I think. To detect "broken" cmap as you say,
> > it's required to investigate cmap, loca, glyf subtables
> > content semantically. After checking the all cmap, loca,
> > glyf subtables, the best cmap subtable would be chosen.
> > I'm not against the fact that such feature is convenient,
> > but I'm questionable if it should be built-in feature of
> > FreeType and should be enabled by default.
> I'm not sure how you could even do it. It is perfectly valid to have
> unencoded glyphs, desirable even. How on earth could you determine that
> one subtable was "better"?

http://www.freetype.org/freetype2/docs/reference/ft2-base_interface.html#FT_Select_Charmap

says:
"Because many fonts contain more than a single cmap for Unicode encoding, this
function has some special code to select the one which covers Unicode best."

So it looks like either documentation should be changed to not mention
that FT_Select_Charmap does the best choice, or FT_Select_Charmap behaviour
should be changed to actually "select the one which covers Unicode best".

--
Dmitry.