Re:Allsorts: font parser and shaping engine implemented in Rust
by xvilka on Tuesday November 19, 2019 @09:28PM
(#21580615)
This would certainly be beneficial for the XeTeX "oxidation" efforts[1] for fonts parsing and shaping[2]. There is also a number of existing alternatives: font-kit[3], Skribo[4], RustType[5], ttf-parser[6]. Some of them are just parsers, some - font shapers. Still all of them are relevant to the subject.
Re:Allsorts: font parser and shaping engine implemented in Rust
by pcwalton on Tuesday November 19, 2019 @09:55PM
(#21580718)
Great to see more work in this space. Diversity of font parsing and shaping engines is important to make sure the ecosystem doesn't become reliant on bug-for-bug compatibility with the existing engines. (It's dangerously close already, due to the quirks of DirectWrite, GDI, and FreeType.)
Re:Allsorts: font parser and shaping engine implemented in Rust
by bjz_ on Tuesday November 19, 2019 @10:24PM
(#21580849)
Yeah! This was a big reason why we've invested in funding the work on https://github.com/n8willis/opentype-shaping-documents/ - hopefully this makes the barrier to entry to building font shaping engines a little lower for newcomers, and gives us a place to document findings, separate from any single implementation.
Re:Allsorts: font parser and shaping engine implemented in Rust
by adrianwongy on Wednesday November 20, 2019 @06:05PM
(#21589591)
Not bugs per se, but a couple of improvements were fed back to HarfBuzz's Indic shaper.
The first was a minor optimisation to the final reordering of pre-base matras; the second was an adjustment to the output of the Indic table generator.
Re:Allsorts: font parser and shaping engine implemented in Rust
by mikeday on Tuesday November 19, 2019 @09:36PM
(#21580646)
HarfBuzz is more complete (supports more scripts) and higher performance (we assume, haven't benchmarked yet), but the large C++ codebase can be a little intimidating to dive into. We plan to extend Allsorts to reach feature parity with HarfBuzz, so it will be an interesting comparison of tackling a complex problem in Rust!
Re:Allsorts: font parser and shaping engine implemented in Rust
by wezm on Wednesday November 20, 2019 @05:43PM
(#21589433)
pcwalton captures it pretty well in a comment above: https://news.ycombinator.com/item?id=21580718 that and wanting to have an implementation in a memory safe language that might prove useful to others.
[1] https://github.com/crlf0710/tectonic
[2] https://github.com/crlf0710/tectonic/issues/117
[3] https://github.com/servo/font-kit
[4] https://github.com/linebender/skribo
[5] https://gitlab.redox-os.org/redox-os/rusttype/
[6] https://github.com/RazrFalcon/ttf-parser
The first was a minor optimisation to the final reordering of pre-base matras; the second was an adjustment to the output of the Indic table generator.
Thanks for contributing in this space
[1] https://github.com/servo/pathfinder/blob/master/README.md
https://github.com/linebender/runebender
[0] https://gankra.github.io/blah/text-hates-you/
[1] https://news.ycombinator.com/item?id=21105625