![]() ![]() I have another example of Microsoft Yahei font being drastically better on 200% with MacType but I couldn't find it at the moment. This approach apparently ruined every diagonal strokes like 丿 and 丶, making those strokes even fainter. MS Gothic has a very large character design, but on the first line of paragraph, 口 from "口周辺" is not reaching the the height it supposed to do, because of Window's approach of fitting that stroke into a line of pixels. Left: AppleWin | Right: Chromium | 15px MS Gothic on 200% system scale Left: AppleWin (Safari for Windows) | Right: Chromium | 12px PingFang SC on 200% system scaleĪs you can clearly see, Apple's font rendering makes every glyph clear enough while ensuring every stroke has the same weight, while Chromium, relying on Windows's font rendering makes the font jagged (stroke width varies), baseline not level (遵守 on the 3rd last line, component 辶's bottom is way up) The antialiasing could do its job without relying the heavily hinted result. On a low DPI settings (130), IMO under normal font sizes (>=10pt) the font has enough pixel realestate to behave like what it was designed. Windows's font rendering tends to fit glyph strokes into pixels (tint). ![]() This tool is more important in Chinese/Japanese/Korean environment as CJK glyphs have more strokes per character as compared to Latin languages. MacOS does tend to handle that situation a little bit better. The other ones will look blurry on the non-primary display. Only applications designed to take advantage of the right scaling API's will look crisp on both displays in that case. the laptop is 150% scaling but the monitor is 100%, or vice versa), then only one display will be perfectly crisp for all apps, and that's the primary display at login. When you hook up a monitor of a different dpi than the laptop (e.g. Update: I totally forgot about the mixed dpi situation. Personally I find the macOS way of rendering on standard dpi displays a bit too blurry.Īs for images, the only difference I can imagine is a different handling of color profiles. You can also disable cleartype entirely to get standard anti-aliasing, which is what macOS does on non-retina screens. Have you tried to use the windows ClearType Text Tuner to improve the font rendering? Windows tries to take advantage of subpixels to improve crispness but it can cause color fringing which makes text harder to read. That means system must render the glyph in correct variant, like in the example of Source Han Sans Chinese, then Chinese content will render correctly with correct Chinese system font PingFang.Īnother issue that is also very important is that Chinese (Simplified or Traditional), Korean and Japanese share amount of the same characters but written differently. It's different on macOS or iOS however, if you set a system locale order as 1. However UWP apps using the new UI framework (like Unigram, Intel Command Centre etc) behave correctly if setting Chinese/Korean as secondary language. ![]() ![]() This is largely true for traditional Win32 programmes, like Chrome, Edge, Explorer.exe, etc. Many programmes runs properly only in designed locales, not that programmes run well in any locale.Ĭhinese/Korean rendered incorrectly on English UI because system hardcoded a font fallback, which put Japanese font first, regardless of how languages are ordered in the Settings. I believe Windows's approach is localisation not globalisation. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |