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
Currently, StereoKit uses an explicit list of font files it can search through for glyphs. This is functional, but not ideal as it's much more specific than developers are accustomed to.
A better solution would be to list a high level font family name, or list of names like CSS does. This would likely need a number of different implementations due to differences in how this is done on various OSs.
StereoKit can then turn this font family into a list of concrete ttf files to search through for each character sets glyphs.
Each of these would result in a list of font files. Segoe UI would work on Windows, but not Linux, which would likely catch Ubuntu. Other systems would fall back to a generic sans-serif font that works well on the system. Other families including concrete font files would still need to fall back for glyphs not in the concrete font, so would add the concrete font at the top of the list, but then search the rest of the fonts for an appropriate fallback chain.
This needs to work on Windows, Android, and Linux.
The text was updated successfully, but these errors were encountered:
Describe the feature
Currently, StereoKit uses an explicit list of font files it can search through for glyphs. This is functional, but not ideal as it's much more specific than developers are accustomed to.
A better solution would be to list a high level font family name, or list of names like CSS does. This would likely need a number of different implementations due to differences in how this is done on various OSs.
StereoKit can then turn this font family into a list of concrete ttf files to search through for each character sets glyphs.
For example:
Each of these would result in a list of font files. Segoe UI would work on Windows, but not Linux, which would likely catch Ubuntu. Other systems would fall back to a generic sans-serif font that works well on the system. Other families including concrete font files would still need to fall back for glyphs not in the concrete font, so would add the concrete font at the top of the list, but then search the rest of the fonts for an appropriate fallback chain.
This needs to work on Windows, Android, and Linux.
The text was updated successfully, but these errors were encountered: