documentation-packages team mailing list archive

[Gunnar Hjalmarsson <1227034@xxxxxxxxxxxxxxxxxx>]

Well, the default font configuration can't reasonably cover all cases.
It's much easier to control which font is used when you use a related
locale, and if you switch to Traditional Chinese as the display
language, you'll find that they show up in the order you say is the
preferred.

Actually, Chinese is a special case. As a result of this bug report, we
added an extra config file to the fonts-droid package in order to give
DroidSansFallbackFull.ttf precedence over other fonts that claim an
ability to render Chinese, and with that make it easy to view Chinese
contents also in case of a non-Chinese locale. But that kind of
configuration, which affects all users, must not be too obtrusive.

You may want to file a new bug about the chrome issue.

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