On Thu, 2018-03-29 at 22:37 +0200, Kevin Kofler wrote: > Adam Williamson wrote: > > AIUI, this means it really only works for simplified Chinese users > > (which means, approximately, mainland China; other Chinese-speaking > > territories tend to use traditional Chinese). > > AIUI, WQY MicroHei actually tries to cover the traditional-only, > Japanese-only or Korean-only glyphs, too. According to > http://wenq.org/wqy2/index.cgi?action=browse&id=Home&lang=en they cover the > whole GBK set and 80% of CJK Extension A. According to > http://wenq.org/wqy2/index.cgi?MicroHei_BigBang_README the 2009 release > claimed support for 99% of Japanese, 100% of Korean, and 99% of Traditional > Chinese. > > The main issue, as I was told, is those CJK Unified codepoints that are > normally rendered/drawn differently in the different countries, but were > unified into a single Unicode codepoint. I was told by the experts that WQY > MicorHei (like all WQY fonts) only contains one rendering (the Simplified > Chinese one) for those, and Wikipedia confirms it: > https://en.wikipedia.org/wiki/WenQuanYi#Glyph > > So in short, if you point it to Traditional Chinese, Japanese or Korean > text, you should see SOME glyph for each character in the text. (I tested it > on the KDE Live image some time ago and I did not get the feared black > boxes.) But that glyph is not necessarily what a speaker of those languages > expects to see and might in some cases be hard or impossible for them to > read. Thanks for the clarification. That does make the case more debatable. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
