How interesting.

Duncan, as you already know the language ID is made up in two parts,
the language and the dialect. It seems that your computer does not look
at the second part and select a default (do not ask me why that is USA,
I would have chosen English Italian :-)
I am not familiar with windows9X, I used only NT and 2K, sorry for that,
but in the M$ web site you can find a lot of documentation about how 
W9x handles differently from 2K (that is their favorite platform right now).

How do you access your res file from the languageID? Maybe I can
say you more.

m.
 

> -----Original Message-----
> From:	Duncan Faulkner [SMTP:DuncanF@r...]
> Sent:	Wednesday, July 25, 2001 4:37 AM
> To:	professional vb
> Subject:	[pro_vb] RE: Multi-language support implementation
> 
> Marco
> 
> I've had a look at the GetUserDefaultLangID() API call 
> and that returns 2057 which is english UK. 
> I've also checked it out on a windows 98 machine and that
> returns 2057. now why should a windows 98 machine read from
> the English USA string and not the English UK string table in my app, if 
> the GetUserDefaultLangID() API call is returning English UK.
> 
> could the problem stem from the fact that we have all the languages in
> one resource file, and not a seperate dll with specific languages.
> 
> Just a thought
> 
> Duncan
> 
> 
> > -----Original Message-----
> > From: Marco Straforini [mailto:marco.straforini@c...]
> > Sent: 25 July 2001 01:12
> > To: professional vb
> > Subject: [pro_vb] RE: Multi-language support implementation
> > 
> > 
> > Duncan,
> > 
> > I had your same first question years ago when I started working on M$
> > (I was always working on Unix before), and the sad answer is: make
> > your gui components big enough. Big enough means twice the size
> > of the English string (English is one of the most concise languages).
> > This is also what M$'s "The Windows Interface Guidelines For Software
> > Design" says...
> > 
> > There are third party components that resize the components, 
> > but most of the
> > time they do not do what you want. But you can check them out.
> > And our problem is even bigger, because we have Asian customers,
> > and Asian languages need fonts with bigger height...
> > 
> > So this is what we do: design a gui that looks good in 
> > English (with plenty
> > of extra space), send the files to be translated, check them 
> > back, run the
> > other language, check if all the strings have enough space 
> > and if not..
> >  make the component bigger or send the files back to the translator
> > asking to shorten the long string.
> > Ugly isn't it.
> > 
> > As for you second question, I am afraid I did not understand it.
> > We check for the locale at run time when the application starts, and
> > again in the SettingChanged event of a SysInfo object. We get the
> > current language using the GetUserDefaultLangID() API.
> > 
> > There is a lot on localization in the MSDN help, but it is not easy to
> > find because it is spread all around. For documentation, better to
> > check the official M$ web page at
> > 
> > http://www.microsoft.com/globaldev/default.asp
> > 
> > m.