On Saturday, 8 April 2017 02:09:53 PDT，Takashi Iwai wrote：
On Sat, 08 Apr 2017 10:21:34 +0200,
Marguerite Su wrote:
Hi, Takashi,
On Sat, Apr 8, 2017 at 3:50 PM, Takashi Iwai <tiwai@suse.de> wrote:
Heh, so this answers your question in the beginning "how to display CJK chars right in a Latin environment"? Answer: "they don't care" :)
Apart from kidding, IMO, we still need a fontconfig help no matter whether CJK fonts are split or not. The same problem still appears when you install both Chinese and Japanese fonts on a single system, for example.
Yes...we need to use that fontconfig configuration to prepend sans-serif, serif and monospace.
I think your concern is that one installed:
* noto-sans-cjkjp-* * noto-sans-cjksc-*
on the same system.
But that assumption isn't real actually...because:
noto-sans-cjkjp-* actually covers all CJK chars...the only difference is the order of the glyphs, that is, Chinese displays Kanji in Chinese glyph...
So far I didn't see concern like "I'm Chinese but I want to display Kanji in Japanese style."
why would you want to install SC if you can display Simplified Chinese?
Well, suppose you install only noto-sans-cjksc-fonts for Simplified Chinese locale, and visit a Japanese web page. Would it be shown correctly with Japanese glyphs even for the CJK unified ideographs?
If my understanding is correct, it wouldn't. When you install noto-sans-cjkja-fonts in addition and choose it explicitly, then you can show the Japanese glyphs for such letters properly, though.
Of course it may seem duplicate in size.
But so far I didn't see any concern about this, that is:
Why a Japanese wants all the Chinese chars bundled in a Japanese font.
Maybe some years later a Korean will raise such questions...because their language contains much more difference than the one between JP and Chinese.
Answers to all the questions:
The only way to solve this, is to increase the source size.
That is, use the four 115mb source, just to get monospace fonts.
And use region specific font for JP, KR, SC and TC separately :-)
Sorry, I'm confused by the argument here. I supposed that splitting to subpackages for each region and weight is for reducing the size as the primary goal?
We might need to reach to some compromise between the reasonable size reduction and the easy installation / management, but the above doesn't look well-explaining to me.
BTW, please keep Frederic in the loop, as he's involved in SLE-Desktop side.
thanks,
Takashi Certain characters are shared among CJK in the sense that they have same unicode.
The problem is, they have same unicode, but differnt countries write them in the different way. For example, "骨". (Taken from https://en.wiktionary.org/wiki/%E9%AA%A8) Chinese: http://i.imgur.com/trR8UTH.png Japanese: http://i.imgur.com/UgTOdDN.png Hope you noticed the difference in the image above. But if you try to copy paste the character from webpage to your desktop app (kwrite for example), you'll see it "changes" to a certain shape depends on your system configurtaion. And how the webpage deals with that? They use lang="ja" in the html tag to force it to use the Japanese standard, and lang="zh" to force the Chinese standard. The problem is, unlike the webpage which allows you force the font usage with "lang", the font used by your desktop doesn't take "LANG" or "LC_*" into consideration (problaby you can take that as a bug in fontconfig ? I don't know). When OTC is installed (and without any fontconfig configuration), even under the "zh_XX.UTF-8", it will use the style of second image to display "骨". Not to mention the character that looks totally different https://en.wiktionary.org/ wiki/%E9%97%A8 . (and sadly they share the same unicode, not possible for desktop app to distinguish them). -- To unsubscribe, e-mail: opensuse-m17n+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-m17n+owner@opensuse.org