Recent searches
Search options
Administered by:
Dear software people,
Unicode is older now than ASCII was when Unicode was introduced. It’s not a weird new fad.
It’s complicated but so is the domain it represents. We recognize that we have to think about time zones and leap days and seconds, for instance. And it’s a cleaner abstraction when you aren’t halfhearted about it.
Sincerely,
Charlie
@vruba Dear software people : *DO NOT* dare to use UNICODE in Windows / VS or such, there's NO such "standard" as "the standard". Just use UTF-8 encoding for it and be sure NOWHERE in your code there's WCHAR and/or wchar_t ! .. otherwise NOTHING will EVER work the way it SHOULD. You may end up with "WCHAR" at 32 bits still encoded in UTF-8 ( i.e. instead of bytes8 using long32 but still with UTF-8 encoding ). Also beware of BOM and such and compiler options. It's a PROPER MESS ! ( CONT ).
@vruba ( CONT ) also NOT even L"string" will guarantee you that string is really UNICODE ( 16 ? 32 ? ) I've seen all sort of unbelievable things happening. Beware also at exchanging "files with translations" between people .. already just saving a ".txt" or ".csv" file may cause lot of problems. Beware of those "I use Office, no I use OpenOffice, no I use some Office-clone something on Mac" .. UNICODE .. is a standard .. often BADLY implemented !