> -----Original Message-----
> From: Serguei Mokhov [mailto:mokhov@cs.concordia.ca]
> Sent: 14 October 2003 16:38
> To: Andreas Pflug
> Cc: pgadmin-hackers
> Subject: Re: [pgadmin-hackers] Maintenance release
>
>
> Huh? Windows 3.1 is a "ancient 16-bit software"; Windows
> 95/98/Me are all 32-bit. I'm having no problems with other
> software tools with Unicode support. :P
You'll have to take that up with Microsoft/wxWindows team. From the wx
setup.h file:
//
------------------------------------------------------------------------
----
// Unicode support
//
------------------------------------------------------------------------
----
// Set wxUSE_UNICODE to 1 to compile wxWindows in Unicode mode: wxChar
will be
// defined as wchar_t, wxString will use Unicode internally. If you set
this
// to 1, you must use wxT() macro for all literal strings in the
program.
//
// Unicode is currently only fully supported under Windows NT/2000/XP
// (Windows 9x doesn't support it and the programs compiled in Unicode
mode
// will not run under 9x -- but see wxUSE_UNICODE_MSLU below).
//
// Default is 0
//
// Recommended setting: 0 (unless you only plan to use Windows
NT/2000/XP)
#ifndef wxUSE_UNICODE
#define wxUSE_UNICODE 1
#endif
// Set wxUSE_UNICODE_MSLU to 1 if you want to compile wxWindows in
Unicode mode
// and be able to run compiled apps under Windows 9x as well as
NT/2000/XP.
// This setting enables use of unicows.dll from MSLU (MS Layer for
Unicode, see
// http://www.microsoft.com/globaldev/handson/dev/mslu_announce.mspx).
Note that
// you will have to modify the makefiles to include unicows.lib import
library
// as the first library (if you use MSVC, you can run the makefile with
"nmake
// MSLU=1 UNICODE=1" command).
//
// If your compiler doesn't have unicows.lib, you can get a version of
it at
// http://libunicows.sourceforge.net
//
// Default is 0
//
// Recommended setting: 0 (1 if you want to deploy Unicode apps on 9x
systems)
#define wxUSE_UNICODE_MSLU 0
Regards, Dave
