Considering the outcome of bug #1581151, I rest my case as regards this
bug report too. Given that we now have 64-language-selector-prefer.conf,
it would be possible to move the UKai/UMing stuff to that file, and with
that get back in sync with Debian. OTOH, the packages are not updated
very often... Wouldn't be worth the effort.

(I'm going to keep 64-language-selector-prefer.conf in the language-
selector package for now instead of moving it into fonts-noto-cjk. Since
we seem to keep needing Ubuntu specific font configuration for CJK, it's
more convenient to have it in l-s IMO.)

** Changed in: fonts-arphic-ukai (Ubuntu)
       Status: Confirmed => Won't Fix

** Changed in: fonts-arphic-uming (Ubuntu)
       Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fonts-arphic-ukai in
Ubuntu.
https://bugs.launchpad.net/bugs/1560548

Title:
  Redundant fontconfig files

Status in fonts-arphic-ukai package in Ubuntu:
  Won't Fix
Status in fonts-arphic-uming package in Ubuntu:
  Won't Fix

Bug description:
  The fontconfig files 65-fonts-arphic-ukai.conf and 65-fonts-arphic-
  uming.conf are Ubuntu specific. Why do we ship those, considering that
  the default font for Chinese is neither "AR PL UKai" nor "AR PL
  UMing"?

  The files seem to make it more difficult to fix a sensible default
  configuration for Chinese/Japanese rendering under a non-CJKV locale.
  Currently we try to compensate for it via 64-language-selector-
  prefer.conf.

  Shouldn't 65-fonts-arphic-ukai.conf and 65-fonts-arphic-uming.conf be
  dropped?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-ukai/+bug/1560548/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to