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
There are some use-cases, for example single-file executables, where it would be a great benefit to allow specifying a vector of font-names and the binary data for those fonts or a pointer to that data. This way app-developers can grab fonts from whichever place they prefer to store them and whichever way of storing them fits their needs best.
Something similar could be done for images, for the same use-case.
The text was updated successfully, but these errors were encountered:
The fontdata pointer could also be made a shared char pointer I guess.
As for what happens when it's called: The font data can be loaded from memory as in the patch I posted on Discord, the difficult part is adding this to the font map and extracting the font information out of it, as the fontconfig helpers apparently only accept directories to scan.
There are some use-cases, for example single-file executables, where it would be a great benefit to allow specifying a vector of font-names and the binary data for those fonts or a pointer to that data. This way app-developers can grab fonts from whichever place they prefer to store them and whichever way of storing them fits their needs best.
Something similar could be done for images, for the same use-case.
The text was updated successfully, but these errors were encountered: