mactype VS harfbuzz

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".

For C/C++ projects that use meson as the build system, there is an excellent way to manage dependencies:

https://mesonbuild.com/Wrapdb-projects.html

https://mesonbuild.com/Wrap-dependency-system-manual.html

meson will download and build the libraries automatically and give you a variable which you pass as a regular dependency into the built target:

https://github.com/qemu/qemu/tree/005ad32358f12fe9313a4a0191...

https://github.com/harfbuzz/harfbuzz/tree/main/subprojects

https://github.com/harfbuzz/harfbuzz/blob/37457412b3212463c5...

Or, if you're using proper operating systems, they're managed by the usual package manager, just like everything else.

If you sympathize with the travails of people working on text rendering in applications, please consider supporting (among other projects):

1. The LibreOffice project (libreoffice.org), the free office application suite. This is where the rubber hits the road and developers deal with the extreme complexities of everything regarding text - shaping, styling, multi-object interaction, multi-language, you name it. And - they/we absolutely need donations to manage a project with > 200 million users: https://www.libreoffice.org/donate

2. harfbuzz (https://harfbuzz.github.io), and specifically Behdad Esfahood the main contributor. Although, TBH, I've not quite figured out whether you can donate to that or to him. At least star the project on GitHub I guess.

As for text, it depends very heavily on what exactly you need. Simple ASCII text and bitmap fonts? Just do it yourself or get a .bdf parser. Simple Latin/Cyrillic-like writing with ok-looking vector fonts (ttfs)? stb_truetype has all you need. Font hinting, subpixel rendering? You use freetype. More complex writing like Arabic? You will have to do shaping as well, say with HarfBuzz. Need right-to-left or unidirectional text? Hypenation? Go for platform APIs if you can (DirectWrite om Windows, CoreText on Mac).

Gold standard? Even though serious bugs are not fixed [1] because "the code is too fragile to touch at this point"? Looks like Android uses HarfBuzz, if so it can't be that bad.

[1] https://github.com/harfbuzz/harfbuzz/issues/2814

The linked libraries are not even close to solving limited subsets of problems solved by FreeType or HarfBuzz. No test is needed if they do not even have a working implementation of particular requisites: Do they work on heterogeneous layouts, directions, languages, locales, scripts, symbols and composites, extensions, variations, legacy, missing, partial or corrupted instructions, standards interpretations, platforms, output devices, nonstandard point structures and grids?

They do not. What they solve is almost a toy problem compared to the size, scope and breadth of these libraries.

Just because some project is implemented in Rust does not make it comparable never mind superior by default.

There is a world out there and it is not homogeneous format and standards-compliant Latin fonts in English LTR text in linear disposition with some generic rectangular subpixel rendering on a regular rectangular grid.

I warmly welcome you to browse closed issues of FreeType [1] and also the closed issues of HarfBuzz [2]. If you feel inspired please do also look into mailing lists and discussion pages related to the development, building, tracking and patching of packages of these projects in any of the numerous places it is used.

The only argument Rust people have is in relation WASM but if you insist in targeting WASM why not fork FreeType, strip it to the strict subset of features your application needs and target it?

Why do it in the first place? Why reinvent the wheel?

As such I will restate my view: I see no gain in using any of these subpar libraries.

[1] https://gitlab.freedesktop.org/freetype/freetype/-/issues/?s...

[2] https://github.com/harfbuzz/harfbuzz/issues?q=is%3Aclosed