Public bug reported:
Unity8 on Ubuntu Touch doesn't load Japanese font in Japanese
environment.
How to reproduce:
1. Install Ubuntu Touch
2. Set environment to Japanese at first boot
3. Reboot system (option)
4. Check whether a glyph come from Japanese font
Expected result:
Use Japanese gothic font (Droid Sans Japanese), and no Mojibake.
Actual result:
Use "AR PL Ukai CN" (Chinese serif font), and some glyphs are missing.
Please refer attached image.
Other information from phablet-shell:
$ strings /proc/`pidof unity8`/environ | grep 'LANG\|LC'
LANGUAGE=ja
LC_TIME=ja_JP.UTF-8
LC_MONETARY=ja_JP.UTF-8
GDM_LANG=ja
LC_ADDRESS=ja_JP.UTF-8
LANG=ja_JP.UTF-8
LC_TELEPHONE=ja_JP.UTF-8
LC_NAME=ja_JP.UTF-8
LC_MEASUREMENT=ja_JP.UTF-8
LC_IDENTIFICATION=ja_JP.UTF-8
LC_NUMERIC=ja_JP.UTF-8
LC_PAPER=ja_JP.UTF-8
=> It seems that LANG env is vallid.
For "音" (U+97F3), the glyph is visible in unity8, but use "AR PL UKai CN".
$ fc-match 'sans:charset=!!(Dl !!rW+'
DroidSansJapanese.ttf: "Droid Sans" "Regular"
$ fc-match 'sans:lang=ja:charset=!!(Dl !!rW+'
DroidSansJapanese.ttf: "Droid Sans" "Regular"
$ fc-match 'sans:lang=en:charset=!!(Dl !!rW+'
ukai.ttc: "AR PL UKai CN" "Book"
=> Both of ukai and droid sans have U+97F3,
all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid.
For "楽" (U+697D), the glyph is invisible in unity8.
$ fc-match 'sans:charset=!!%g9 /?6HG '
DroidSansJapanese.ttf: "Droid Sans" "Regular"
$ fc-match 'sans:lang=ja:charset=!!%g9 /?6HG '
DroidSansJapanese.ttf: "Droid Sans" "Regular"
$ fc-match 'sans:lang=en:charset=!!%g9 /?6HG '
DroidSansJapanese.ttf: "Droid Sans" "Regular"
=> Because ukai doesn't have U+697D,
all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid.
$ sudo lsof -p `pidof unity8` | grep font
unity8 2592 phablet mem REG 7,0 17151049 113683
/usr/share/fonts/truetype/arphic/ukai.ttc
unity8 2592 phablet mem REG 7,0 415552 113610
/usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-L.ttf
unity8 2592 phablet mem REG 7,0 333616 113622
/usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf
unity8 2592 phablet mem REG 7,0 353824 113613
/usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-R.ttf
=> Why loads ukai.ttc instead of DroidSansJapanese.ttf?
** Affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "font_test.png"
https://bugs.launchpad.net/bugs/1352142/+attachment/4169106/+files/font_test.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1352142
Title:
Doesn't load Japanese font on Ubuntu Touch
Status in “unity8” package in Ubuntu:
New
Bug description:
Unity8 on Ubuntu Touch doesn't load Japanese font in Japanese
environment.
How to reproduce:
1. Install Ubuntu Touch
2. Set environment to Japanese at first boot
3. Reboot system (option)
4. Check whether a glyph come from Japanese font
Expected result:
Use Japanese gothic font (Droid Sans Japanese), and no Mojibake.
Actual result:
Use "AR PL Ukai CN" (Chinese serif font), and some glyphs are missing.
Please refer attached image.
Other information from phablet-shell:
$ strings /proc/`pidof unity8`/environ | grep 'LANG\|LC'
LANGUAGE=ja
LC_TIME=ja_JP.UTF-8
LC_MONETARY=ja_JP.UTF-8
GDM_LANG=ja
LC_ADDRESS=ja_JP.UTF-8
LANG=ja_JP.UTF-8
LC_TELEPHONE=ja_JP.UTF-8
LC_NAME=ja_JP.UTF-8
LC_MEASUREMENT=ja_JP.UTF-8
LC_IDENTIFICATION=ja_JP.UTF-8
LC_NUMERIC=ja_JP.UTF-8
LC_PAPER=ja_JP.UTF-8
=> It seems that LANG env is vallid.
For "音" (U+97F3), the glyph is visible in unity8, but use "AR PL UKai CN".
$ fc-match 'sans:charset=!!(Dl !!rW+'
DroidSansJapanese.ttf: "Droid Sans" "Regular"
$ fc-match 'sans:lang=ja:charset=!!(Dl !!rW+'
DroidSansJapanese.ttf: "Droid Sans" "Regular"
$ fc-match 'sans:lang=en:charset=!!(Dl !!rW+'
ukai.ttc: "AR PL UKai CN" "Book"
=> Both of ukai and droid sans have U+97F3,
all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid.
For "楽" (U+697D), the glyph is invisible in unity8.
$ fc-match 'sans:charset=!!%g9 /?6HG '
DroidSansJapanese.ttf: "Droid Sans" "Regular"
$ fc-match 'sans:lang=ja:charset=!!%g9 /?6HG '
DroidSansJapanese.ttf: "Droid Sans" "Regular"
$ fc-match 'sans:lang=en:charset=!!%g9 /?6HG '
DroidSansJapanese.ttf: "Droid Sans" "Regular"
=> Because ukai doesn't have U+697D,
all results of default lang (ie. LANG=ja), lang=ja, lang=en is valid.
$ sudo lsof -p `pidof unity8` | grep font
unity8 2592 phablet mem REG 7,0 17151049 113683
/usr/share/fonts/truetype/arphic/ukai.ttc
unity8 2592 phablet mem REG 7,0 415552 113610
/usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-L.ttf
unity8 2592 phablet mem REG 7,0 333616 113622
/usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf
unity8 2592 phablet mem REG 7,0 353824 113613
/usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-R.ttf
=> Why loads ukai.ttc instead of DroidSansJapanese.ttf?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1352142/+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
