> How an application can decide which cmap table is better without
> digging into internal cmap data?
It can't.
> Shouldn't that be a responsibility of Freetype to ignore
> incomplete/broken cmaps, especially since it already parses cmap
> tables
No. It does reject broken cmaps, but a valid, imcomplete cmap can't
be ignored.
> and can easily decide which one is better?
The `easily' is the critical word. I can imagine that there are cases
where different cmaps for Apple and Microsoft make sense, for example,
mapping glyphs into the PUA. So again, the answer is `no'. However,
MS cmaps are now preferred over Apple ones for both UCS-4 and UCS-2
cmaps.
Werner
_______________________________________________
Freetype-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/freetype-devel
