question about non-standard language IDs

[Jonathan Wilson]

i.e. LANG_ESPERANTO, LANG_WALON, LANG_CORNISH, LANG_WELSH, LANG_BRETON
Where are these comming from? Are these Wine only or does some variant of 
windows (or some language list somewhere) define these?

If they are Wine only (I cant find them in any MS headers), then something 
should be added in the places they are used to say:
#ifdef LANG_WALON
#include "wa.rc"
#endif

This will enable wine stuff (such as notepad) to compile under win32 using 
the MS or W32API headers.

[Sylvain Petreolle]

They arent Wine only, and they doesnt match any MS headers sinxce
windows has no support for these languages.
> LANG_ESPERANTO, LANG_WALON, LANG_CORNISH, LANG_WELSH, LANG_BRETON
> Where are these comming from? Are these Wine only or does some
> If they are Wine only (I cant find them in any MS headers), then

This wont work.
You will break the nls functionality which gives you the windows
programs in your own language without recompiling.
A better choice would be : #ifndef WIN32 ... #endif
> something should be added in the places they are used to say:
> #ifdef LANG_WALON
> #include "wa.rc"
> #endif
>
> This will enable wine stuff (such as notepad) to compile under win32
> using 
> the MS or W32API headers.

=====
Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) 
ICQ #170597259

alias upsf='false ; while [ $? -ne 0 ] ; do cvs update -APd ; done 2>&1 |tee cvslog'

"What if tomorrow the War could be over ?" Morpheus, in "Reloaded".

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

[Jonathan Wilson]

My point is this:
1.these language IDs are in the WINE header files.
They are not in the MingW or MS SDK header files.
If you are building with WineLib and WineGCC and the Wine header files, 
then these IDs will be defined and it will work.
But if you are building with MingW or MS SDK (e.g. building a dll or exe on 
windows for testing), it wont work because of compiler errors.
Basicly, we add code that says "if the resource compiler can find a 
definition for these "non-standard" (acording to the wine header files) 
language IDs, it will use them. If not, it wont pull in those header files.

For someone building wine, they would get the resources.
For someone building on Win32 with MingW, they wouldnt get the resources 
unless they added the definitions somewhere (AFAIK windows doesnt know 
about those language IDs or those languages anyway)

IMO, any compiler claiming to compile win32 programs and providing header 
files and libraries for the win32 API should be defining WIN32, regardless 
of what executable format it spits out at the end. I have at least one 
piece of code that uses
#ifdef WIN32
//win32 specific code including calls to win32 API
#else
//other code
#endif