<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - 65-nonlatin should be updated for CJK fonts" href="https://bugs.freedesktop.org/show_bug.cgi?id=20911#c116">Comment # 116</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - 65-nonlatin should be updated for CJK fonts" href="https://bugs.freedesktop.org/show_bug.cgi?id=20911">bug 20911</a> from <a class="email" href="mailto:arthur200126@gmail.com" title="Mingye Wang (Arthur2e5) <arthur200126@gmail.com>"> Mingye Wang (Arthur2e5)</a> <pre>Jeff Bai <<a href="mailto:jeffbai@aosc.xyz">jeffbai@aosc.xyz</a>> and I are currently working on a newer ordering of this file for the CJK part at <a href="https://github.com/AOSC-Dev/aosc-os-abbs/issues/201">https://github.com/AOSC-Dev/aosc-os-abbs/issues/201</a>. Hopefully we will come up with a modernized version this weekend or so. We are mainly focused on these points: * Separate sans (hei), serif (ming/song) and cursive (kai). Like the current git version of the file, we are now only adding strongly monospace (i.e. monospace for non-han parts too) fonts as monospace, but this is actually worth a discussion IFF the font is only going to provide CJK chars. (We know at least FW kanas and hanzi/kanjis are always 1em wide (good), while some hanguls are like .93 em (oops).) * Font weight matching. Many old CJK serifs (e.g. UMing, SimSun) look too thin to match common serifs, but the TeX community have good fonts to remedy this -- cwTeX and Fandol fonts. We add [kind of prepend, in CJK ranges] these fonts to the list accordingly. As a bonus, these are all FOSS. Some CJK sans on the other hand is too heavy (e.g. SimHei[1]), but now we have Noto Sans CJK/Source Han Sans to remedy this. * Sans-serif monospace is better than serif monospace, at least for computer screens. Additionally, monospace CJK serifs are often old and have the very-thin-weight issue. Note that we are not supposed to nor intending to fix any of these "locale mix" problems like what was shown in the description of <a href="attachment.cgi?id=24321" name="attach_24321" title="mixture of Han glyphs from Japanese and Chiense fonts under en locale">attachment 24321</a> <a href="attachment.cgi?id=24321&action=edit" title="mixture of Han glyphs from Japanese and Chiense fonts under en locale">[details]</a>. Locale matching problems should be done via in-browser detection schemes like html lang tags, with appropriate locale-aware requests to fc, which hopefully will be handled by other distro-specific config wiles. We are only trying to make sure the styles of CJK part matches latin fonts matched for the generic family names, as well as themselves. (This is actually a terrible problem on MS Windows, where they consider SimSun a sans-serif.) (Well, considering the widths of some glyphs like 复 in Japanese fonts (they are often not actually using the glyphs in the language but using it as some glyph to be referenced by other glyphs), I will go with TW, KR or CN fonts as the preferred source of Chinese glyphs. Choosing the traditional locales is just for "going back the roots and be acceptable to as many locales as possible". (KR glyphs are kind of old/kangxi-ish-style -- lack of use lead to lack of evolution.)) [1]: In Chinese, Hei (黑) stands for black. This actually caused some confusion and resulted in many people calling bold weights "Hei". I have no idea on how to fix the bad "ja" language tags in Chinese fonts though. (why are they trying to <s>eat</s> manage everything?)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>