Marguerite Su changed bug 1202037
What Removed Added
CC   i@marguerite.su

Comment # 12 on bug 1202037 from
Hi, all,

A. the misleading state of "we don't support zh-MO":

zh-MO is an official locale defined by ISO organization. 
https://salsa.debian.org/iso-codes-team/iso-codes/-/blob/main/data/iso_3166-1.json

the GNU C Library doesn't support zh-MO locale.
https://sourceware.org/git/?p=glibc.git;a=tree;f=localedata/locales;h=cdd948688e068b1741b01b29b3110d5fcdbbb48f;hb=HEAD

gnome follows glibc so it doesn't support zh-MO.

kde uses ki18n which refers to iso-codes and timezone data so it supports
zh-MO.

for openSUSE, the situation is complicated:

our filesystem package doesn't even have zh_SG:
https://build.opensuse.org/package/view_file/Base:System/filesystem/languages?expand=1

fcitx/fcitx5 package introduced zh_SG to /usr/etc/X11/xim.d

for SUSE, SLED uses gnome desktop but it also has fcitx (I think because I
don't have a registration code) :-D

for fonts-config part, I prefer to fix zh-MO instead of removing it. because
that handler was introduced back in 2018, many users may have adapted to it
already. Zhao said we need government official documents to support font type
variants, I doubt because Singapore government may not have such documents too,
no need to mention Malaysia or South Thailand. Google/Adobe develop Noto font
glyphs based on such standard, but they never prevent usage in other cases.

B. I agree that Macau should bind to Hongkong. Because the Traditional Chinese
standard in Taiwan region is not so traditional. Other Chinese areas uses Kang
Xi glyph variants(. that is, the HK variant is more traditional than Tiwan's,
and more like what people in Macau see daily. The physically and culturally
saying on github is not wrong actually.

I myself didn't do such tweaks before because back to 2018 there's no Noto CJK
HK variant at all I think.

So, please go ahead if you have better solutions, we can continue the talk on
github.

C. the Fedora fontconfig configuration should not be applied to openSUSE. they
use "Noto Sans CJK SC" but we should use language specific variants instead of
CJK variants whose name is "Noto Sans SC" (that's a bug since revision 2, I
need to fix it later), so they can remove the redundant language matches. the
CJK variants will always display Japanese variant.


You are receiving this mail because: