3 ms·
It's not that different from how a lot of international details are handled for fonts. As someone used to latin letters, you have a giant set of foundry-made fo
by WorldMaker 8y ago
It's not that different from how a lot of international details are handled for fonts. As someone used to latin letters, you have a giant set of foundry-made fonts with cool names, interesting histories, and visible distinctions between families.
If you use a more complicated script such as Chinese/Japanese/Korean ideograms, or more rare script like Cherokee, you not only have fewer choices, maybe a font or three. In those cases those fonts are often more closely tied to the system manufacturer than what in the latin script world we'd think of as a foundry or type designer. Some scripts wish they could afford designers/type-foundries to explore playful variants like or similar to the vast variety we see of latin characters. (I've seen kickstarters/indiegogo campaigns for exactly that.)
Then there are Unicode fallback fonts. A font "Times New Roman" doesn't (and likely couldn't) include _all_ of Unicode. It's a big sea of characters. Not just because it would take a lot of work for every font to cover all of Unicode, but because for most fonts it doesn't even make sense. What's the difference between say "Arial" and "Helvetica" outside of latin/latinate letters? How would you apply that to CJK ideograms or Cherokee letters? So for a lot of Unicode codepoints, the systems all fall back to common system fonts (a dedicated Cherokee font, a rotation of CJK fonts based on all sorts of things like region and some rare hints from the font being falled back from).
It's possible for classic foundry fonts like "Times New Roman" to ship with full emoji sets, and to have outside font choices to shift emojis. The one non-technical question remains: what would that even mean for "Times New Roman" emoji versus "Arial" emoji, "Arial" versus "Helvetica"? It's possible we might figure out a use for something like a "serif" versus "non-serif" emoji and the fallback can send that as a hint of sort like some other scripts have, but never need anywhere near as wide a variety of emoji.
It's also possible systems could provide options of fallback emoji font based on user preference, if there were enough emoji font options. For now it's easiest for the system manufacturers to just bundle one and only one of their choice, such as they do with a script like Cherokee.
There are a few technical obstacles to allowing that. The big technical issue is how systems handle color rendering. Microsoft is currently to my knowledge the only system handling emoji entirely in the font rendering stack, with color data embedded as extensions into otherwise ordinary OpenType font files. [1] (Microsoft's emoji fallback font actually has a traditional foundry-style name, it is "Segoe UI Emoji", and can even be seen in font lists, not that it is that useful on its own as a latin font choice, and Character Map hasn't been updated to render color fonts nor show Unicode emoji ranges.) Many other systems have custom renderers that intercept Unicode emoji and replace with raster bitmaps of one form or another, rather than relying on "true" font fallback techniques.
[1] https://docs.microsoft.com/en-us/windows/desktop/DirectWrite/color-fonts https://docs.microsoft.com/en-us/windows/desktop/DirectWrite...
- bambax 8y agoVery informative, thanks!!!