2 ms·
I try UTF characters in everything which displays text, especially when it's graphically manipulated. It's slightly amazing how few handle it, even if there's
by Groxx 16y ago
I try UTF characters in everything which displays text, especially when it's graphically manipulated. It's slightly amazing how few handle it, even if there's little reason not to (unless a library along the pipeline only reads ASCII).
I think it's just that most people are used to dealing with / have encountered C char arrays, and 8 bits per character just makes sense to programmers. 'Tis why I jump for joy when I hear about framework-X fully supporting UTF - IMO, they all should, from day one, but I realize it can sometimes be a lot of work, and is always a performance hit.
- mahmud 16y agoYou don't know how right you are. Google Web Toolkit has the most impressive support for Arabic, but it's ASCII only out of the box, even though it runs on Java, a thorough-bred Unicode language.
- caf 16y agoThere's another issue with the "graphically manipulated" case - typefaces. There's no fonts that support every Unicode code point.