On 2014-07-23 17:14, Alex Yu wrote: > "fc-match -a 'sans-serif'" shows that ukai.ttc is before uming.ttc > and after Droid Sans. DroidSansFallbackFull.ttf is before > ukai/uming.ttc.
Yes, that's what I see too. > ukai (AR PL UKai) should be after uming. Considering that DroidSansFallbackFull.ttf is installed by default on all machines, whether Chinese language support has been explicitly installed or not, why would it make a difference? The default configuration makes DroidSansFallbackFull.ttf be used for rendering Chinese contents irrespective of the order of UKai and UMing, doesn't it? -- You received this bug notification because you are a member of Documentation Packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1227034 Title: Default Chinese font changed to fonts-arphic-ukai after completing language support installation for zh-* locales Status in Ubuntu Kylin: Fix Released Status in “fonts-android” package in Ubuntu: Fix Released Status in “fonts-takao” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “fonts-android” package in Debian: Fix Committed Bug description: After completing language support installation, fonts-arphic-ukai and fonts-arphic-uming are pulled into user's system and then fontconfig chooses Ukai over Droid Sans Fallback for the default sans-serif font. This is not the desired behavior as Ukai doesn't fit well into the category of screen fonts comparing to Droid Sans. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1227034/+subscriptions -- Mailing list: https://launchpad.net/~documentation-packages Post to : documentation-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~documentation-packages More help : https://help.launchpad.net/ListHelp
