I have a quite specific usage case where the fonts are defined at run-time by the translation, and then should be used in order of decreasing priority, e.g., look in font 0 for a glyph, if fails, go to font 1, etc…
One of the motivations for this is the different in CJK languages where even though, for example, Chinese and Japanese can use the same symbols, they have different fonts and our Japanese translators have indicated that iced seems to use Chinese fonts by default.
Now, while it’s possible to define extra fonts to use in iced, it’s only possible to refer them via font family, with which is not known at runtime and would require manually parsing and trying to extract the family name. Furthermore, if the fonts have different family names, I’m not sure if it would work.
I believe this could be solved by:
- give an option to disable using system fonts and only use provided fonts
- make the default font name optional and have it just default to the fonts in order when not specified
However there are likely to be other ways to handle this. However, from my investigation, it seems like iced used to have file-based fonts and was switched to a more high-level definition. It would likely be good to allow for more fine-grained control for applications that need it in an easier way than just defining fonts at a high-level.