Yes, it's weird. Right now I suspect that the configuration file 65
-droid-sans-fonts.conf (attached), which the current fonts-droid package
installs, is the root cause of this mess. That file seems to imply that
if you install fonts-droid, you want Droid Sans fonts be used for all
languages, while we are currently only interested in Droid Sans
Fallback. In other words, it does not fit well with Ubuntu's default
font configuration.
I have modified the packages in my PPA a little. From the changelogs:
fonts-android (1:4.3-3ubuntu1.1~ppa2) trusty; urgency=medium
* Binary package split:
- fonts-droid split into fonts-droid-cjk, which installs the Droid
Sans Fallback font, and fonts-droid-general, which installs the
rest. fonts-droid converted to a transitional dummy package
which depends on fonts-droid-cjk.
* debian/local/65-droid-sans-fonts.conf:
- Recipes affecting Droid Sans Fallback dropped.
language-selector (0.129.3~ppa2) trusty; urgency=low
* fontconfig/69-language-selector-zh-??.conf:
Reverse changes in version 0.129.2.
* data/pkg_depends:
Replace fonts-droid with fonts-droid-cjk.
65-droid-sans-fonts.conf is installed by the new fonts-droid-general
package, but the Droid Sans Fallback related entries have been removed.
I think that the packages in my PPA are now in a state which makes them
uploadable to the archive.
You may ask: Do we really need this package split? Wouldn't it be
sufficient to modify (or drop) 65-droid-sans-fonts.conf? Honestly I'm
not sure. To test that theory, you can simply install both fonts-droid-
cjk and fonts-droid-general from my ppa. When I do so on my 14.04
desktop, it seems to work. At least for the moment...
@Lukas: Can you please do the same, and let us know if Chinese is still
rendered correctly in the qt apps?
OTOH: Is it sensible to have to install all those fonts just to be able
to use Droid Sans Fallback for Chinese? And what about the phone?
@Iain: Your comments on all this would be appreciated. Apparently
something needs to be done, also in trusty.
** Attachment added: "65-droid-sans-fonts.conf"
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+attachment/4168348/+files/65-droid-sans-fonts.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fonts-android in Ubuntu.
https://bugs.launchpad.net/bugs/1351092
Title:
Configuration of the Droid Sans Fallback font
Status in “fonts-android” package in Ubuntu:
New
Status in “language-selector” package in Ubuntu:
New
Bug description:
There are currently several open issues related to the use of Droid
Sans Fallback for rendering Chinese content:
* Two mixed fonts when rendering Chinese in KDE/QT apps with Droid
Sans fonts
https://launchpad.net/bugs/1334495
* Droid Sans no longer preferred font for Chinese
https://launchpad.net/bugs/1335482
* Chinese in Ubuntu Touch should use Heiti style sans serif font
https://launchpad.net/bugs/1346766
Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a
bunch of fonts, of which only one is needed for Chinese. In an attempt
to sort things out I have built the fonts-android source package in my
PPA with the DroidSansFallbackFull.ttf font broken out to a separate
binary package named fonts-droid-cjk. The PPA also includes a version
of language-selector where the changes in version 0.129.2 have been
reverted.
To test it in Trusty, you should:
* Uninstall the fonts-droid package
* Install fonts-droid-cjk and language-selector-common from my PPA
at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test
My own tests indicate that the change to language-selector due to bug
#1335482 was a step in the wrong direction. With
DroidSansFallbackFull.ttf as the only installed font from the Droid
Sans family, you get rid of possible confusion that might have
resulted in the issue reported in that bug.
$ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5
DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular"
uming.ttc: "AR PL UMing CN" "Light"
uming.ttc: "AR PL UMing HK" "Light"
ukai.ttc: "AR PL UKai CN" "Book"
DejaVuSans.ttf: "DejaVu Sans" "Book"
Also, if we would take this route, it might be easier to fix a
configuration that makes Droid Sans Fallback work well with qt apps.
(This is pure theory/hope so far.)
Looking forward to your comments.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+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
