Hacker News new | ask | show | jobs
by bruhsfx2 1781 days ago
Good to see MacType discussed here.

This tool is more important in Chinese/Japanese/Korean environment as CJK glyphs have more strokes per character as compared to Latin languages. Windows's font rendering tends to fit glyph strokes into pixels (tint).

On a low DPI settings (<100), fonts on Windows look more sharp and clear, while on macOS, which discards the bitmaps altogether, the result is blurry (albeit I still prefer to be able to appreciate the original design).

On a higher DPI settings (>130), IMO under normal font sizes (>=10pt) the font has enough pixel realestate to behave like what it was designed. The antialiasing could do its job without relying the heavily hinted result.

Here are some comparisons.

https://pbs.twimg.com/media/EhoCr9GUYAAjzMG?format=webp Left: AppleWin (Safari for Windows) | Right: Chromium | 12px PingFang SC on 200% system scale As 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)

https://pbs.twimg.com/media/EJUJZL8UYAAC7sC?format=webp&name... Left: AppleWin | Right: Chromium | 15px MS Gothic on 200% system scale 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. And Windows makes the font thinner. This approach apparently ruined every diagonal strokes like 丿 and 丶, making those strokes even fainter.

I have another example of Microsoft Yahei font being drastically better on 200% with MacType but I couldn't find it at the moment.

It's suffice to say that MacType will recovered the font rendering for Windows in 200% scale. However, in 100% scale, it provides fixes when Windows messed up with fonts in some cases when it purposefully fit the strokes into pixels.

https://pbs.twimg.com/media/DrJStIiU0AA01uT?format=webp&name... Safari for Windows, 100% scale https://pbs.twimg.com/media/DrJStMyV4AE_b6f?format=webp&name... Vivaldi, 100% scale Font rendered on Vivaldi is thin, not equal stroke width, with jagged curves. It's miles better on Safari on Windows. Just look at the "产品" on the bottom left, Windows makes the upper 口 in the 品 painfully short in height.

While i appreciate Windows's effort to make glyphs more legible for lower pixel density displays, but at least provide a toggle to turn it off as it literally ruins everything else. Fonts MS used in every Office/Windows/even Windows Terminal showcase video are not hinted font yet the glyphs look pretty legible, and even gorgeous (if you appreciate the curves of Segeo UI) in a 4:2:0 subsampled video, animated, yet average Windows users can't find a way to experience this on daily basis without MacType.

1 comments

Thanks, the second image was by far the clearest demonstration of rendering issues that are well-beyond just aesthetic preference and verging on actually changing the meaning. The first character of "口周辺" looks as if someone cut out an entire row or two of pixels from where the top stroke is, and once I'd seen that it was easier to spot similar flaws - the first character on each of the lines after the first almost looks worse than the character above it!