On Tue, Jul 29, 2014 at 5:51 PM, Rex Tsai <email address hidden> wrote:

> On the phone, the LANG/LANGUAGES env value are not changed. It's always
> en_US.UTF-8.
>

I'm not sure I follow that: the LANG variable should change (as the
LC_MESSAGES) should, otherwise you wouldn't be able to switch languages.
Same for the LANGUAGE env var.

Could you be a bit more specific on which environment variable you don't
see changing? What's the output of the 'locale' command from the terminal
app?

Thanks!


>
> If fonts-wqy-microhei only, it rendered correctly.
>
> ** Attachment added: "fonts-wqy-only.png"
>
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1346766/+attachment/4165235/+files/fonts-wqy-only.png
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1346766
>
> Title:
>   Chinese in Ubuntu Touch should use Heiti style sans serif font
>
> Status in “ubuntu-touch-meta” package in Ubuntu:
>   Triaged
>
> Bug description:
>   Ubuntu Touch uses Kaiti style font as the main UI font for displaying
>   Chinese, which is not optimal as nowadays operating systems all use
>   Heiti style font for the UI, we should really change it asap.
>
>   Currently there are two choices on Ubuntu, fonts-droid and wqy-
>   microhei. Below I will list out the pros and cons.
>
>   wqy-microhei (DroidSansFallbackFull.ttf, modified):
>   - Pros:
>     - The advantage of wqy-microhei being its wider codepoint coverage,
> for example it also contains Japanese Kanas and Korean Hanguls in one font.
> The downside is it may be of lower quality than the original
> DroidSansFallbackFull.ttf due to its lack of maintenance in recent years.
>   - Cons:
>     - I am not too much in favour of using wqy-microhei, the reason being
> that it is basically a font that based on the Droid font
> (DroidSansFallbackFull.ttf to be exact).
>     - Upstream has not updated wqy-microhei for long time, so it lacks any
> new updates from the Droid font, although it may not be obvious to users.
>     - Another possible disadvantage of wqy-microhei is it includes more
> latin characters, which may result to inconsistent glyphs being used.
>
>   fonts-droid (DroidSansFallbackFull.ttf, original):
>   - Pros:
>     - The advantage is it has coverage of CJK ext. A [1], which
> wqy-microhei does not provide.
>   -Cons:
>    - On the other hand, wqy-microhei has added some glyphs that the droid
> font does not provide, I don't have the exact number of that but I believe
> it's just a small number.
>    - The disadvantage is it does not include Korean Hangul, which can be
> remedied with another Korean font, and it's not our current concern anyway.
>
>   As an additional alternative, just a few days ago, Google released the
>   Noto Sans CJK fonts [2][3]:
>
>   fonts-noto (Noto Sans CJK fonts):
>   - Pros:
>     - It takes care of different writing standards of Traditional Chinese,
> Simplified Chinese, Japanese and Korean, which makes everyone happy (see
> slide 13-14 of [3])
>     - It covers Japanese and Korean as well
>   - Cons:
>     - Needs to be tested
>     - Bigger size than the other alternatives as a result of catering for
> both Traditional and Simplified Chinese
>     - Not yet packaged [4]
>
>   [1] https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_A
>   [2]
> http://googledevelopers.blogspot.de/2014/07/noto-cjk-font-that-is-complete.html
>   [3]
> https://docs.google.com/presentation/d/1xIBCsqwrSxowmLQS7kJm9gM58-FmOIYlZWoRlgqtqE4/edit#slide=id.g36327fada_643
>   [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1346766/+subscriptions
>