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
Rather than using a custom format to store the font, is it viable to instead parse a webfont?
I'm sure the webfont formats are already light weight compared to the format used by this library, so there would surely be savings there.
In my mind this would effectively cut out the need to do font conversion, and open the library to easily accessing many more fonts. There could be download savings if the font is used on other parts of the site already.
Looks like there's already js libraries to do parsing: https://opentype.js.org.
It might just be a matter of creating some kind of transformer that takes their data and converts it to txtjs form.
The text was updated successfully, but these errors were encountered:
Rather than using a custom format to store the font, is it viable to instead parse a webfont?
I'm sure the webfont formats are already light weight compared to the format used by this library, so there would surely be savings there.
In my mind this would effectively cut out the need to do font conversion, and open the library to easily accessing many more fonts. There could be download savings if the font is used on other parts of the site already.
Looks like there's already js libraries to do parsing: https://opentype.js.org.
It might just be a matter of creating some kind of transformer that takes their data and converts it to txtjs form.
The text was updated successfully, but these errors were encountered: