mactype VS source-han-sans

I'm curious - when you were doing research into the mechanics of hinting options, did you stumble onto any relevant discussion around allowing custom pixel geometries to be defined, to enable hinting on modern OLED / WRBG displays? There's a good thread on the topic here[0], with some people referring to it as 'ClearType 2' on the MS side [1]. On the oss side I know FreeType theoretically supports this[2], but I can't quite figure out how relevant the FreeType backend is to this most recent work.

This is great work btw.

[0]: https://github.com/snowie2000/mactype/issues/932

[1]: https://github.com/microsoft/PowerToys/issues/25595

[2]: https://freetype.org/freetype2/docs/reference/ft2-lcd_render...

HDMI 2.0 is capable of doing 4k @ 120Hz, but only up to YCbCr 4:2:0 8bit instead of the full YCbCr 4:4:4 10bit (though I'm not sure how close wayland is to 10bit support). It will be fine for gaming, just not for everyday PC use.

FWIW I also didn't realise this until just now. I've been running my desktop at 4k@120hz recently for the buttery smooth neovide, but have been noticing that text rendering, especially syntax-highlighted text, looks awful. I'd seen the same oled panel render text way better in WSL/Windows (both using a custom pixel geometry[0] via Mactype, but also without), so I spent more time than I'm willing to admit to wrapping my head around custom pixel layouts and hinting in freetype. But no, turns out it was this all along.

If you want to see the effect of 420 vs 444 chroma subsampling on text rendering, this writeup[1] has some great test images and is well worth a read. Also, if you happen to have an LG OLED panel, you can get a little debug window that confirms your signal format and refresh rate, by pressing the green button on the remote 7-8 times.

[0]: https://github.com/snowie2000/mactype/issues/720

Mactype is an application used to improve font rendering on Windows. Install Mactype from here: https://github.com/snowie2000/mactype/releases/download/v1.2023.5.31/mactype-20230531.zip

Download Mactype. If you download the beta version (warning: it will trip windows defender) you can use one of the QD-OLED profiles, if you download the last stable version (has an installer and will not trip Windows defneder), use a grayscale rendered font like this one. It doesn't work on chromium browsers though so you're gonna have to use Firefox if you want it to be on your browser.

If only. There's a ticket open with Microsoft's PowerToys to improve the anti-aliasing situation:

https://github.com/microsoft/PowerToys/issues/25595

And heres an explanation from the dev of MacType about how DirectWrite can cause different applications to perform text rendering differently from each other:

https://github.com/snowie2000/mactype/wiki/DirectWrite-vs-GD...

There's an open source text rendering engine called MacType, it does what you'd think (make it look like Mac). Fonts are a visual delight after that, and it's highly configurable.

Already supported in WPF and DirectWrite. AFAIK DirectWrite by default only uses y-axis at large font sizes. I think MacType enables it system-wide.

I'm using standalone mode (load with tray). It can definitely work with browsers, as mentioned here: https://github.com/snowie2000/mactype/issues/931. Their github has considerations and workarounds for each, such as this page for Chrome: https://github.com/snowie2000/mactype/wiki/Google-Chrome

Step 2: Install it from the MacType homepage, it is an open-source project so it seems safe to me. I recommend installing it in "Load with MacTray" -> "Standalone Mode".

Moreover, I see a roughly 50/50 split of the glyph standard in traditional Chinese texts; it is not uncommon for "Jiu Zixing" and Taiwan MOE styles to appear on the same page. The HK version (middle) is a recent addition per the "Splitting TWHK into TW & HK" issue on GitHub. I have never seen any print text following the HK standard, though you may see them occasionally in online media due to preinstalled HK fonts such as PingFang or Noto Sans.

Babelstone Han or [Source Han Sans](https://github.com/adobe-fonts/source-han-sans} are probably your best bets? Couldn't find any other typefaces that might cover obscure characters like these

Try Source Han fonts (https://github.com/adobe-fonts/source-han-sans or https://github.com/adobe-fonts/source-han-serif) from Google/Adobe. It's the default font on Android and should display it wonderfully: 𰻝 (simplified) or 𰻞 (traditional).

I believe Windows's approach is localisation not globalisation. Many programmes runs properly only in designed locales, not that programmes run well in any locale.

Chinese/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. This is largely true for traditional Win32 programmes, like Chrome, Edge, Explorer.exe, etc. However UWP apps using the new UI framework (like Unigram, Intel Command Centre etc) behave correctly if setting Chinese/Korean as secondary language.

It's different on macOS or iOS however, if you set a system locale order as 1. English, 2. Chinese, then Chinese content will render correctly with correct Chinese system font PingFang.

Another issue that is also very important is that Chinese (Simplified or Traditional), Korean and Japanese share amount of the same characters but written differently. That means system must render the glyph in correct variant, like in the example of Source Han Sans

https://github.com/adobe-fonts/source-han-sans/raw/release/S...

According to people from adobe its even a JIS standard to make those two kanji narrower