Created attachment 449251 [details] standalone demo Description of problem: Droid Sans is being suggested by fontconfig as containing 0x6587 (etc) but it doesn't have that glyph Version-Release number of selected component (if applicable): google-droid-sans-fonts-20100409-1.fc14 How reproducible: 100% Steps to Reproduce: 1. install google-droid-sans-fonts 2. gcc fontconfigdemo.c -lfontconfig 3. ./a.out Actual results: Reqesting font with support for 0x6587: Suggestion is "Droid Sans" Expected results: Something else because Droid Sans does not have 0x6587 in it. Moving the .conf away elsewhere gives the correct results, so something in the .conf is causing this to be suggested, even though it can't satisfy the requested glyph Additional info: probably related to bug 517789
Our Droid Sans is a merge of all the Droid Sans parts Google released, including Droid Sans Fallback, which definitely includes 0x6587 So fontconfig is correct. The synthetic Fedora "Droid Sans" does include this glyph
crap, its OOo losage again :-(, more to-dos.
If that makes you feel better I think this particular fontconfig setup caused misery to Chromium developers first (I so wish keithp had listened to me when I wrote him splitting font files over script boundaries were not the solution for i18n. Now that Google has actually done what he suggested with Droid, and we're actually trying to define the synthetic fonts fontconfig is supposed to be good at, not only it is not solving the problems we had with big unicode fonts, but it's adding new ones to the mix)