Comment 10 for bug 1351092

Well, you get DroidSansFallbackFull.ttf first, which is good. That's what I got previously too (see comment #10 of bug #1335482), and it was the intention with

https://launchpad.net/ubuntu/+source/language-selector/0.129.2

However, after having tried various things back and forth, I don't get that result any longer. Instead I get:

$ dpkg-query -W fonts-droid language-selector-common
fonts-droid 1:4.3-3ubuntu1
language-selector-common 0.129.2
$ LANG=zh_TW.UTF-8 fc-match -s sans-serif | head -5
DroidSans.ttf: "Droid Sans" "Regular"
uming.ttc: "AR PL UMing TW" "Light"
uming.ttc: "AR PL UMing HK" "Light"
ukai.ttc: "AR PL UKai TW" "Book"
DejaVuSans.ttf: "DejaVu Sans" "Book"

I.e. approximately the same result as Cheng-Chia Tseng reported in comment #9 of bug #1335482. And that's not good, since it leads to "AR PL UMing TW" being used to render traditional Chinese contents instead of "Droid Sans Fallback".

So the result of the current configuration is unpredictable, and I'm pretty sure by now that the culprit which causes this unpredictability is 65-droid-sans-fonts.conf. The pending merge proposals should fix that.

I also think that the merge proposals will both fix bug #1334495 and make it possible to use fonts-droid in the phone.