From: waterlan <wat...@xs...> - 2012-11-19 11:37:42
|
Maximus schreef op 2012-11-19 07:57: > Erwin Waterlander <waterlan@...> writes: > >> I think that Windows is very well capable of handling DBCS >> (double-byte >> character set). I'm not testing a DBCS ANSI page like CP936 >> (Simplified >> Chinese GB2312) but I'm using Unicode wide chars to test. In theory >> it >> should be possible to print Chinese Unicode while keeping my Dutch >> locale setting (like I can print Greek or Russian), but I notice >> that >> printing Chinese in the Console is very hard in practice on a >> Western >> localised Windows. > > Hm. I don't think that european builds of Win are DBCS capable in > mind of > console. But I have not check this thoroughly. There are many > differences in > console processing wich may break your app functionality. For > example, in EU > versions "one cell - one unicode symbol". > But this rule is broken in Chinese builds. > Hieroglyphes uses TWO cells (DBCS yes?) while latin chars uses only > one. > Some functions (which works normally in EU) will fails on DBCS > consoles. > And so on. > DBCS just means character sets where ALL characters are encoded in two bytes. This does not mean that the width of all the characters is two cells. CP936 is actually a MBCS (multi-byte character set). The ASCII characters take only one byte. But this is all not Unicode. See also http://en.wikipedia.org/wiki/DBCS regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |