documentation-packages team mailing list archive

[Gunnar Hjalmarsson <1227034@xxxxxxxxxxxxxxxxxx>]

Well, if you run fc-match with the zh_TW.UTF-8 locale (which in fact
simulates the use of Traditional Chinese as the display language), it
indeed should make a difference if you install version 0.129.2 of
language-selector-*.

OTOH, if you actually are using English as the display language, a more
adequate test is:

fc-match -a 'sans-serif'

That should result in a long list, and you ought to see a bunch of Droid
Sans fonts (including DroidSansFallbackFull.ttf) before AR PL UMing TW.

-- 
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