Hi,

I am the initial packager of google-noto-sans/serif-CJK-fonts and the
maintainer of our fonts-config.

In the early version of that package, I used region-specific variants. Later
Mr. hillwood replaced them with language-specific variants and accepted the
submit request by himself, then guoyunhe continued to update that package with
language specific ones

There is a known bug back in 2016 that Japanese variant wll always take effect
due to the alphabetical order so you can not see any chinese variant. Nowadays
in 2022, although pango/harfbuzz/freetype support opentype locl feature and
language tagging underlying, this regression still exists because:

1. All Qt applications don���������t support any opentype features because QFont
doesn���������t implemented such things
2. GTK supports them but rare application made use of that, eg: GIMP still
can���������t use opentype features although GTKFontChooser allows such usage since
3.24
3. Such usage needs programming, it does not mean users can simply set up font
variant in system settings and the Simplified Chinese variant will apply
everywhere. Every application/web page needs to enable opentype locl features
during programming. So only professional application like Adobe CS 6 may adapt
to it. We will not see it work out of the box in the foreseeable future.

So the only benefit of using language-specific variants is its code point
coverage, but seldom people needs to display Pan CJK everyday while everyone
hates to see Japanese variant in charge under non-Japanese locales

And openSUSE���������s fonts-config were implemented with region-specific font names eg
���������Noto Sans SC��������� not ���������Noto Sans CJK SC���������. such packaging nearly destroyed those
font configurations

Please fix