> Why does FcCharSetHasChar fail for non-BMP characters? It's because > ... > fonts like Code2001 has multiple Cmaps all with the identical symbolic > FT encoding 'FT_ENCODING_UNICODE' but with different char. coverage. > Code2001 has 4 cmaps, pid=0,eid=0(Unicode), pid=1,eid=1(AppleRoman), > pid=3(MS),eid=1(Unicode) and pid=3(MS),eid=10(Unicode). Only the last > cmap has non-BMP characters although the first and the third are also > Unicode cmap. I'm not familiar with Truetype internals, so my question might fail the issue, but why do there have to be multiple encoding mappings for Unicode at all? This seems like a little bit chaotic to me. Why does this font not just contain a single set of information for Unicode usage?
Regards, Thomas Wolff -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
