[Pkg-fonts-devel] Bug#652516: ttf-wqy-zenhei: fontconfig priority should be separate from fontpackage itself

Osamu Aoki osamu at debian.org
Sun Dec 18 00:56:33 UTC 2011


Package: ttf-wqy-zenhei
Version: 0.9.45-3.1
Severity: normal

In order to preserve original behavior, I intentionary used
64-wqy-zenhei.conf instead of 66-wqy-zenhei.conf for NMU.

At least it solved problem of killing user configuration freedom.

But this package, along with 64-arphic-uming.conf still fight for
priority automatically, when font is installed.  This is very general
problem for all CJK fonts rooted in Unicode han unification problem.

No one have a simple answer to the following.
   * Japanese fonts first
   * Chinese (zh_CN) fonts first?
   * Chinese (zh_TW) fonts first?
(You can pick any other nations sharing fonts but with different tastes)
but each has some non-overlapping set of characters to cover large set
of characters.)

I realized this can be solved by providing a set of packages for each
nonlatin fonts.

  For nonlatin font bar, create 2 packages

  * fonts-bar
    normal font package
    install 66-bar.conf (current 64-wqy-zenhei.conf equivalent)
    Recommends: fonts-bar-priority

  * fonts-bar-priority
    Installing this package put it on the top of choice for nonlatin
    fonts.
    install 64-bar.conf (the same content as 66-bar.conf)
    Provides: fonts-priority
    Conflicts: fonts-priority

  This way, no normal font package is aggressive.
  When fonts-*-priority is installed, it becomes choice for nonlatin
  range.  Always one of them are installed to ensure user selected taste
  for the font.

  Once this is done properly for all font packages including we can
  remove 65-nonlatin.conf. (We loose MS Micho but that is not supported
  and whoever smart enough ti add it manually should have no problem
  configuring it.)

Also, some package hopes font name solution is done by fontconfig and
does not provide alias entry.  fonts-takao is an example.  With this
practice as above, the mess in 65-nonlatin.conf content may be solved.
It is hard for the maintainer of that package to keep track new nonlatin
fonts.  Some alias entry such MS Gothic in it should have been VL Gothic
but someone made mistake mixing them up and reordering.

Osamu

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (10, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ttf-wqy-zenhei depends on:
ii  fontconfig  2.8.0-3

Versions of packages ttf-wqy-zenhei recommends:
ii  x-ttcidfont-conf  32+nmu2

ttf-wqy-zenhei suggests no packages.

-- no debconf information





More information about the Pkg-fonts-devel mailing list