3 ms·
Forgive my ignorance, but how do these actually enter the real world? Do browsers adopt these new characters?
by jstalin 12y ago
Forgive my ignorance, but how do these actually enter the real world? Do browsers adopt these new characters?
- mmastrac 12y agoTechnically the entirety of the unicode range is supported by browsers right now -- they just don't exist in fonts at all. What Unicode does is say that "this codepoint" means "this". At that point, fonts start adding glyphs to mean "this" and authors start adding codepoints that refer to "this". If you look at FontAwesome, it uses characters in the "unicode private use area" -- which are effectively undefined -- but putting those codepoints in your HTML document while having the appropriate font loaded will show the appropriate icon glyphs.
- greggman 12y agoActually AFAICT Chrome does not support the entirety of the unicode range right now. Safari and Firefox do. 🙅🎁４👨
- mmastrac 12y agoChrome does support these codepoints, but it doesn't support the format of Apple's PNG glyphs for emoji. Amusingly, it does support the android colored glyphs in Chrome for Android.
- dragonwriter 12y ago> Forgive my ignorance, but how do these actually enter the real world? Do browsers adopt these new characters? Browsers don't add characters, fonts do.
- sho_hn 12y agoYou should find http://pixelambacht.nl/2014/multicolor-fonts/ http://pixelambacht.nl/2014/multicolor-fonts/ an interesting read.
- masklinn 12y ago> Do browsers adopt these new characters? No, fonts ship with them. Browsers don't really care, they see codepoints and ask underlying font-rendering API for the corresponding glyphs, then display that. And these characters may not have anything to do with browsers, not are they restricted to browsers e.g. "emoji" originate in pre-smartphones cellphone-based text and email messages in japan for instance.