>>3
Little-endian UTF-16, big-endian UTF-16, or UTF-16 with byte-order-markers?
Name:
Anonymous2006-11-17 17:06
>>7
Again, any Unicode Transformation Format is fine; preferrably with BOM, but it can be detected without; and when working on Windows, it's always UTF-16 LE anyways.
That is, unless you have a small penis. For example, to read from the console, you can call either:
ReadConsoleA <-- For small or "Asian" penis
ReadConsoleW <-- For big or "Westerner" penis
Name:
Anonymous2006-11-17 17:08
>>7
Use UTF-128, you'll have less problems recompiling your code in a million years.
Name:
Anonymous2006-11-17 18:28
>>9
In the future we won't need unicode because letters will be deprecated.
Name:
Anonymous2006-11-17 19:03
>>10
In the future we won't need code because computers will be deprecated.
Name:
Anonymous2006-11-17 19:37
To people reading japanese code
STOP BEING SUCH A WEEABOO and go do something other than looking at a game's source code
Name:
Anonymous2006-11-17 19:41
I was not looking at games source code. I was having problems running games because they expect my 8-shits locale to use Shit_JIS, while I'm using Shitdows-1252. Hence, stuff is broken because of poor programmers not doing Unicode.
Name:
Anonymous2006-11-17 20:15
Will never happen since the larger of the computer corps. want to create regons like the dvd regons but for computers.
Especially Macintosh, Microsoft and those dumbasses trying to preserve the ANSI.
You bitch about Japanese programmers, but English programmers are just as fucking stupid. For instance, try finding a free file shredder than can recognize files with multi-byte characters. Even better, FreeCommander still cannot deal with Unicode file names correctly--and it's a fucking file browser.
In short: bitches don't know shit outside their tiny penis world.
Name:
Anonymous2009-01-14 9:41
When the hell are they going to increase CHAR_BIT beyond 8 so we don't have to bother with this bullshit, anyway?
Profs at university here will tell you: OKAY GUYS, THIS IS A STRING: const char* string = "HELLO WORLD!". (Most of the time they will even omit const and let their studends figure out the hard way that writing to such a string is a bad idea). Anyway, in 4 years of university, not a single person ever mentioned wchar_t, character encoding, character set conversion or anything else you'd need in a post-90's programming environment.
I figure that Japanese people would have the same problems. It works fine on their computer, so why bother and change it? Those westerners can fuck themselves, right?
>>25
wtf r u takin about?
It's a fucking command-line program, so unless your terminal can handle multi-byte characters, there's no way to pass it a UTF-16 string. And even if you could, I'm willing to bet my e-penis that it will choke on its POSIX bullshit.