3 ms·
What I tried to say is that dealing with ASCII is meaningless; it's not even a useful starting point. For the majority of people, a string format that accepts
by pavlov 14y ago
What I tried to say is that dealing with ASCII is meaningless; it's not even a useful starting point.
For the majority of people, a string format that accepts 100% of ASCII but 0.1% of Unicode is just as useless as one that only accepts 95% of ASCII. Therefore the goal should never be to get your ASCII coverage from 95% of 100%.
- kbolino 14y agoThere are two issues here: one is not accepting Unicode properly, and the other is making incorrect assumptions about the content of strings. Both need to be resolved, and all this cultural butthurt is not productive to solving either of them. Resolving the Unicode issues is undeniably a higher priority for speakers of foreign languages, but there are still plenty of languages and libraries whose support for Unicode ranges from nonexistent, to antiquated, to limited, to just plain broken. There's nothing application developers can do in the short term to fix those problems, but by examining their own code and removing fallacious assumptions they can better facilitate the proper handling of Unicode once it becomes available in their underlying technologies. In the mean time, though, they may only have ASCII, or ISO 8859-X, or KOI8-R, or Shift-JIS, etc. to test with.