$ LANG=zh_CN.UTF-8 fc-match 'sans-serif'
DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular"
$ LANG=zh_HK.UTF-8 fc-match 'sans-serif'
DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular"
$ LANG=zh_TW.UTF-8 fc-match 'sans-serif'
DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular"
Looks promising, doesn't it? :)
I'd like a few Chinese users to test the language-selector version in my PPA.
Then there are a few questions:
* Should this change make it to the archive, or are there drawbacks?
* Should we add 'binding="strong"' to all the
69-language-selector-zh-*.conf files to be safe?
* Should we add 'binding="strong"' to serif and monospace as well?
Thanks for the tip, Pellaeon Lin! To me it's useful indeed.
$ LANG=zh_CN.UTF-8 fc-match 'sans-serif' ckFull. ttf: "Droid Sans Fallback" "Regular"
ukai.ttc: "AR PL UKai CN" "Book"
$ LANG=zh_HK.UTF-8 fc-match 'sans-serif'
uming.ttc: "AR PL UMing CN" "Light"
$ LANG=zh_TW.UTF-8 fc-match 'sans-serif'
DroidSansFallba
Not good.
I made a couple of changes to language-selector:
https:/ /launchpadlibra rian.net/ 170732046/ language- selector_ 0.124_0. 125~ppa. diff.gz
and uploaded to my PPA at https:/ /launchpad. net/~gunnarhj/ +archive/ fonts
$ LANG=zh_CN.UTF-8 fc-match 'sans-serif' ckFull. ttf: "Droid Sans Fallback" "Regular" ckFull. ttf: "Droid Sans Fallback" "Regular" ckFull. ttf: "Droid Sans Fallback" "Regular"
DroidSansFallba
$ LANG=zh_HK.UTF-8 fc-match 'sans-serif'
DroidSansFallba
$ LANG=zh_TW.UTF-8 fc-match 'sans-serif'
DroidSansFallba
Looks promising, doesn't it? :)
I'd like a few Chinese users to test the language-selector version in my PPA.
Then there are a few questions:
* Should this change make it to the archive, or are there drawbacks? selector- zh-*.conf files to be safe?
* Should we add 'binding="strong"' to all the
69-language-
* Should we add 'binding="strong"' to serif and monospace as well?