|
From: Erwin W. <wat...@xs...> - 2012-11-23 12:11:46
|
Op 23-11-2012 11:57, Yongwei Wu schreef: > > I did not mean not to use consoles. However, probably you do not want > to write anything that depends on the console and also is able to > handle non-default encodings well. That is why I use Unicode. It should work anywhere, provided the appropriate font is available and the console can handle it. But this also counts for Linux. There are problems in Linux too. > > I have some old GNU tools like ls.exe, grep.exe, which used to work on > Windows XP, but is now broken on Windows 7 to display Chinese > correctly. It is different from your current issue, but also shows > Microsoft made poor design choices/changes when dealing with non-ASCII > characters. > Unicode works well (mostly). But there are some things I find weird with the non-Unicode stuff. For instance on a Dutch 64 bit Windows 7 the default code page in Console is the OEM (DOS) page CP850. This makes no sense, because you can't run DOS programs on 64 bit Windows, because NTVDM has been removed. To start with, Microsoft could have removed all the DOS code pages from 64 bit Windows, and make the default console code page equal to the system code page. Next they should switch to UTF-8, but I understand also they want to stay backwards compatible. regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ |