On Fri, Sep 16, 2005 at 04:58:03PM +0100, Neil Mitchell wrote:
In Windows both the WinHugs "fake" console and the standard console are already unicode compliant on NT/2K/XP and have wrapper functions such as wprintf which are unicode and tprintf which is either ASCII or Unicode depending on some #define's.
If you change the user-default ANSI code page, can it print out non-ASCII Chars, and read them in? (Identifiers are restricted to Latin-1, though.)
How does Hugs deal with unicode, i.e. are the filenames etc. stored by the program as unicode, or is it just the Haskell elements that are Unicode.
Module filenames, no. Filenames in H98 library calls are String, which is Unicode. String literals are byte-encoded Unicode, though.
Attatched is a patch which includes the unicode compliant header along with commented out definitions for unicode in WinHugs. If you uncomment those definitions it will not work, but then I can work on converting files one by one and when they are all done hopefully a Unicode enabled Hugs on windows will result :)
This process should not alter the non unicode code paths at all, beause of various defines in Windows.
I fear you may be opening a can of worms, and you may end up having to change things everywhere.