|
|
Back to UserFriendly Strip Comments Index
|
Why can't people learn to use unicode?! | by Khaar | 2007-01-22 02:01:50 |
|
Because it is too bleeping cumbersome! | by vampire | 2007-01-22 07:30:34 |
| OK, I'll bite. |
by Khaar |
2007-01-22 10:20:04 |
Please, do explain how using unicode from the start increases one's workload. I'm curious.
In my field at least, one has to specify code page (or collation in SQL) one way or the other and all work that it adds is that extra "N" before strings in SQL queries. Selecting UTF-8 ensures at least some level of consistency throughout application and all connected systems and a very wide range of supported languages (whereas using a default or country-specific code page might not be enough for even two European languages). English works with most code pages just fine, but it's not the only language out there. One of the larger systems I'm responsible for includes over 20 languages, including Chinese.
If you *know* what you are doing, no one will care if you break a few rules if you can deliver the result. But if you just think you know what you're doing (and this goes for many developers I've worked with, in real life or online) and choose to ignore even the simplest advice from more seasoned developers, you're on your own when debugging starts. Most often people just don't concern themselves with which code page they pick -- "oh, this one will do" they'll say -- and if data has to be passed from one application to another (e.g. client-side HTML, server-side scripting, database and back again), simply returning just entered text might completely destroy some characters if code pages aren't consistent. And that happens unbelievably often.
Oh, and as for that comment, if your experience differs from mine, good for you. Really. |
|
[ Reply ] |
|
Well it sounds to me likw you all are | by vampire | 2007-01-22 21:31:19 |
|
|
[Todays Cartoon Discussion]
[News Index]
|
|
