You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should be able to load a font from the file system or scan a directory for fonts, rather than only having FS access via system. (We should be able to let the text stack memory map arbitrary font files without having to load them into a blob.)
In fontdb, this is easy to do by using Database::load_font_file or Database::load_font_dir.
In font-kit, this can be done with the sources::fs::FsSource.
The text was updated successfully, but these errors were encountered:
Having register_fonts take a Blob instead of Vec<u8> would be one step in this direction. We could add register_fonts_from_path to solve the rest, but we’d want to consider whether these should be fully loaded or just parsed and added to a source path map to be lazily loaded later.
Also, since memory mapping is considered generally unsafe in Rust, we should offer the option to disable it, even for system collections.
We should be able to load a font from the file system or scan a directory for fonts, rather than only having FS access via
system
. (We should be able to let the text stack memory map arbitrary font files without having to load them into a blob.)In
fontdb
, this is easy to do by usingDatabase::load_font_file
orDatabase::load_font_dir
.In
font-kit
, this can be done with thesources::fs::FsSource
.The text was updated successfully, but these errors were encountered: