googlefonts / oxidize

Notes on moving tools and libraries to Rust.
Apache License 2.0
173 stars 7 forks source link

What Rust crates are part of this project? #36

Closed ctrlcctrlv closed 1 year ago

ctrlcctrlv commented 1 year ago

I read the slides, but it is unclear. Yes, read-fonts and write-fonts, but what crates do they use?

Is MFEK/pathops potentially part of this? What about MFEK/feaparser.rlib? Doubtful that MFEK/glifparser.rlib will be unless MFEKglif gets more popular and more people want to automatically compile its special .glifjson format. (I'm probably only one in the world that does so currently.)

cmyr commented 1 year ago

This stuff is very low-level, and would generally be below anything else in the font-stack. For instance the font-types crate has no dependencies, and the read-fonts crate only depends on that and bitflags; same with write-fonts, but it also depends (currently optionally) on read-fonts.

An actual font compiler would sit on top of write-fonts, and would likely have various other dependencies, to be determined. :)

ctrlcctrlv commented 1 year ago

Thank you, I thought this was a fontmake replacement.