Open losfair opened 2 years ago
@losfair I was just thinking about this yesterday. I think I will want to generate the font atlas and all the font and glyph metrics in a build script, serialize it to my own format, and just load that. Also nice, that it would make fontdue
a build-only dependency.
Would be interesting if this could have been done in const fn
and stored in a static
, but probably won't be possible anytime soon.
Hello,
Thanks for your work on this crate! I'm using
fontdue
in Blueboat for drawing text onto a canvas and would like to reduce the memory usage after loading a large font file (e.g.NotoSerifSC
). Found this in readme:But it seems possible to write the
glyphs
field of aFont
to a file after initial parsing, and memory-map the file back to a slice so that the OS kernel manages swapping of unused parts?