fontdue

Oh! I have a prefix sum laying around in SIMD in Rust, I use it for bitmap rasterization for fonts. Looking at the comments I guess this isn't a popular usecase, but useful nonetheless. Doing it on the GPU looks really fun https://github.com/mooman219/fontdue/blob/master/src/platfor...

So for sub-pixel accurate font rasterization in Rust there are [1], [2], [3] and now the one from Typist, [4]. Possibly there are more (I know Raph Linus stopped maintaining [5] so that one is out). All of these crates are actively maintained. Are people re-inventing the wheel? [1] https://gitlab.redox-os.org/redox-os/rusttype [2] https://github.com/alexheretic/ab-glyph [3] https://github.com/mooman219/fontdue [4] https://github.com/typst/pixglyph [5] https://github.com/raphlinus/font-rs

I agree that no_std is incredible. I really want to see more crates embrace it and encapsulate their no_std logic away from their standard logic. I very often see crates that are like 95% of the way to no_std but then choose to bundle some standard only features without flagging them. I wrote fontdue [0] (which is very incomplete spec wise) because there just wasn't another font library that was no_std at that time. It felt like the existing libraries were in an arms race for gpu caches and bundling file loading. Like if I wanted to commit to a running on a platform I'd do the sane thing and use harfbuzz or the platform APIs. It's very naive because I don't understand all of the complexity, but I'd really like to see the standard library being easier to piecewise implement from crates. Like a standard trait library and a standard implemen

I work on a SIMD optimized font library [0] and have stumbled into the same situation of hand writing SIMD intrinsics. Some things are just kinda hard to make sure they get optimized correctly, and there is enough difference between the platforms where that matters when fiddling with bits. I also kinda have fun writing SIMD code like this too. [0]: https://github.com/mooman219/fontdue/blob/master/src/platfor...

Subpixel text rendering also requires intimate knowledge of the display being rasterized for, and becomes a mess once you enter multiple displays with different pixel layouts. I was working on support in my font library https://github.com/mooman219/fontdue/, but it quickly becomes not worth it. I'm interested to see your approach to the problem if your project is online!