Open stevendejong opened 11 years ago
I'm having a similar issue on Android; 5 digit unicode characters aren't recognised. Tried Chrome and Firefox on Android 4.2 and neither display these characters when inserted as CSS content in a pseudo element. Characters with a 4 digit unicode value work fine.
There is a workaround, which is to use the excellent website http://icomoon.io/ where you can create your own icon font based on libraries of icons, including Entypo and quite a few others. You can then choose to map the glyphs to basically any Unicode value you want. If you don't have any issues with screen readers, you can even map them to the range starting at 0x0000. Then, instead of the Entypo font, use the font you downloaded from IcoMoon. I hope this helps, while also hoping anyone involved in the development of Entypo ever reads this issue page so people can use Entypo without first having to remap the font.
I've forked this repo at https://github.com/RaphaelBossek/entypo and fixed this issue: https://github.com/RaphaelBossek/entypo/commit/4b6a8c5122f23a93b6402b78931798ad40e86d11#config.yml
I've also renamed the icon names to their original.
What the heck! You mean to say many platforms m.m. programming languages support the Unicode standard’s Basic Multilingual Plane, only? There are 15 more planes in Unicode… They are all constitutively part of the international standard by which we encode semantics through glyphs.
It’s NO option to encode semantical characters on meaningless PUA codepoint slots, or likewise hacks. Platforms that dont support Unicode’s full character set, do not support Unicode. Hence, they suck, are obsolete and need to be driven into oblivion.
There are more characters between the West and the East coast than are dreamt of in your realm, Uncle Sam. Time you devs need to learn some basic typography and linguistics, too.
Thanks for the fantastic work on the entypo icon set.
I have a problem with it though, and cannot seem to get it working fully, because quite a number of icons use five-digit unicode values.
How to deal with those? As visible in my screenshot, even my programming environment (IntelliJ) considers, for instance, "\u1F464" as "\u1F46" followed by a 4.
As for programming languages affected: I am working in Flex (ActionScript) and Java at the moment, but extensive Googling told me people using many other programming languages have similar problems addressing Unicodes above 0xFFFF. I did not find any solutions, though.
Maybe there is a simple solution. If so, I would love to hear it.
Or if the solution is in fact not simple for many programming languages, maybe you could consider releasing a version that uses only unicode values below 0xFFFF?
Hoping for a reply, and thanks for your time!