Tag Info

New answers tagged

0

I'm not sure I like this answer, and even though it's my own, I'm not going to prefer it. But I can't rule out in my own mind that it is a good thing to do in some situations, so I'll offer it. If you've seen the movie "Gravity", you'll have seen Sandra Bullock's character trying to control a spacecraft whose controls are labelled in Russian. But those ...


2

Telastyn's answer already has some good points, to which I want to add a few: You're speaking of internationalization, at least for the UI. That means user-names etc.: Have a user named André Svónögrödäß (yes, him) and store his profile on the server: BOINK! translations and transscriptions everywhere., or tell him that his name is "wrong", while the ...


4

You can actually have both. Unicode supports an encoding where all characters are represented as a (variable length) sequence of 8-bit units: UTF-8. Assuming that you refer to ASCII with your 'old-fashioned 8-bit chars', then you can almost trivially support UTF-8, because UTF-8 is a proper superset of ASCII: All characters in the original 7-bit ASCII set ...


2

Are there any technical reasons to reject keeping the business logic part of an application ignorant of Unicode like this? While you're reasonably certain that your system doesn't need Unicode (now), I don't see what you gain by precluding it. Unless you're using an environment with horrible Unicode support, I imagine it'll be more work to go that ...



Top 50 recent answers are included