Mike FABIAN wrote:> Behdad Esfahbod <behdad@xxxxxxxxxx> さんは書きました:> >> Behdad Esfahbod wrote:>>>>> So, it's the case of a buggy fonts. When we have support for removing certain>>> glyphs from a font pattern you can use that to blacklist these glyphs.>>>>>> As for whether fontconfig is right or wrong, I crosschecked the table with:>>>>>> http://unicode.org/Public/MAPPINGS/VENDORS/APPLE/ROMAN.TXT>>>>>> and the fontconfig version is correct, but missing the entries 0xE0 to 0xFF.>>> Maybe there's good reason for not including those, and that reason may extend>>> to the ones you are removing. I have no idea. Keith?>> So, I checked again, and you are commenting out the everything but the ASCII>> range, essentially making the MacRoman encoding equivalent to ASCII. This>> plain means that the font in question has the wrong encoding tag. That's all.> > OK, so I should blacklist the wrong glyphs in these fonts when this> becomes possible with fontconfig. Fixing the encoding tag in the> fonts is not possible in case of commercial fonts. Right. I was actually wrong about fontconfig's table being incomplete. It's ascomplete as the ROMAN.TXT table. The sort order tricked me. behdad_______________________________________________Fontconfig mailing listFontconfig@xxxxxxxxxxxxxxxxxxxxxxxxx://lists.freedesktop.org/mailman/listinfo/fontconfig
