Re: [Celestia-developers] Win32 and gettext

[Christophe T. <ch...@te...>]

Le Jeudi 23 F=E9vrier 2006 17:37, Chris Laurel a =E9crit=A0:
> > To avoid character map issues, the generated resource files use UTF-8
> > (code_page 65001), this appears to not be supported by VS 6, is that a
> > problem?
> >
> > Chris, can I commit the win32 i18n patch?
>
> Yes, you should commit the patch.

Ok, I'll commit everything tonight, including the perl scripts.

> > Here is the TO DO list to have i18n working on Windows:
> > - automatic loading of the appropriate resource file
> > - conversion of utf8 strings to the current local in dialogs
> > - unicode input (supported by celestiacore, but not used by winmain).
>
> I *think* that we'll need to start building the Windows version with
> UNICODE defined. Or is this not necessary if we use UTF-8 encoded strings
> instead of wide characters?

I've seen that there are two modes for windows apps: ANSI or UNICODE, but I=
'm=20
not sure what the effect of UNICODE is. My understanding is that the win32=
=20
API then expects all GUI strings to be wide character strings? does that al=
so=20
affect IO operations?

Otherwise, I think we can get away with the current ANSI mode, converting t=
he=20
UTF8 string to wide caracters and then to the current CP. That will work if=
=20
the LANGUAGE you're running Celestia with is supported by your current CP.

=2D-=20
Christophe