🚀 go-pugleaf

"Thorsten Kettner" <QUESTIONBYthorsten.kettner@otto.de> wrote in message
news:41f5ffbc$1@newsgroups.borland.com...
>
> Hi all,
> my program is being used in UK and in Germany. To get a string
> in the appropriate language, I use
>
>   MyAnsiString.LoadString(HInstance, MYRESID);
>
> This works fine in Win NT and Win 98, but in Win XP and Win 2000
> I always get the German string.
>
> My resource file contains two string tables:
>
> STRINGTABLE DISCARDABLE
> LANGUAGE LANG_ENGLISH, SUBLANG_NEUTRAL
> BEGIN
> MYRESID "Some text in English."
> END
>
> STRINGTABLE DISCARDABLE
> LANGUAGE LANG_GERMAN, SUBLANG_NEUTRAL
> BEGIN
> MYRESID "Ein Text in deutsch."
> END
>
> I checked GetUserDefaultLangID() and GetUserDefaultLCID(), and
> both work correctly under 98, NT, 2000 and XP. (German/Germany
> is code 1031, English/Great Britain is 2057).
>
> Any idea what's going wrong?

Windows 2K and XP have changed the way they load resources.  See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300680.  In a
nutshell, instead of using the thread locale, LoadString always uses the
default language ID of the OS.  It's kind of silly in my estimation, but
that's what they did.

You could write your own version of LoadString() that would take an argument
specifying the language, and then load the string using the FindResourceEx,
LoadResource, and LockResource API functions.

- Dennis