touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #06998
[Bug 1351092] Re: Configuration of the Droid Sans Fallback font
On 2014-08-04 12:24, Iain Lane wrote:> laney@iota
> LANG=zh_TW.UTF-8 fc-match -s sans-serif | head -5
> DejaVuSans.ttf: "DejaVu Sans" "Book"
> DejaVuSans-Bold.ttf: "DejaVu Sans" "Bold"
> DejaVuSans-Oblique.ttf: "DejaVu Sans" "Oblique"
> DejaVuSans-BoldOblique.ttf: "DejaVu Sans" "Bold Oblique"
> Verdana.ttf: "Verdana" "Normal"
Hmm.. That would indicate that zh_TW.UTF-8 is not generated on your
system.
--
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:
In Progress
Status in “language-selector” package in Ubuntu:
In Progress
Status in “fonts-android” source package in Trusty:
Triaged
Status in “language-selector” source package in Trusty:
Triaged
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
References