Re: internationalisation

Tom,

This is whay I hinted that the devil is in the detail. There's always
something lurking about ready to pop up.

My point is that if you go down the official route then you end up with a
monumnetal maintenance overhead. You also end up with very well polished
applications.

I doubt if many of us do, or would want to, work on a software project that
has the luxury of enough time to make a really thorough job of translation.

And so I've tried to develop a workable framework for dealing with
localisation without putting the brakes on new development. It's far from
perfect and I'd love to hear alternatives.

KMA

"Tom Serface" <tserface@xxxxxxx> wrote in message
news:uQzafuJOGHA.3360@xxxxxxxxxxxxxxxxxxxxxxx
I do this the same way, but the big problem is the dialogs that come from
Windows (I.E., message boxes and MFC dialogs) are still in the language
that was loaded on the computer. It's tough to do *any* language on *any*
Windows load. We finally decided to just support our languages on the
native system. It works if you don't because we did what you illustrated
here, but if someone does File/Open they always get English if English is
loaded or French if French is loaded for MFC.

Tom

"KMA" <kma@xxxxxxxxxxxxxxx> wrote in message
news:dtkp3e$hmi$1@xxxxxxxxxxxxxxxxxxxx
Feel free to disregard, but I do it like this:

m_hLocalResource = AfxLoadLibrary(sLanguageDLLName);
AfxSetResourceHandle(m_hLocalResource);

This way you can set the resource language independent of the OS
language.

It looks really easy!

Ahhh, but the devil is in the detail. *Practical* internationalisation
means rationalising where you spend your efforts to get the most return
for your time investment.

It's a subject dear to my heart, and my wallet. If you want to discuss
more details, feel free.

KMA



"David Webber" <dave@xxxxxxxxxxxxxxxxxxx> wrote in message
news:O7rjuJJOGHA.2668@xxxxxxxxxxxxxxxxxxxxxxx
Is there a way of testing "satellite DLL's" for resources in different
languages in MFC programs on English Language systems?

I understand that one (eg) creates a resource DLL

MyAppFRA.dll

full of French resources and puts it in the same directory as

MyApp.exe

to get a localised French version of the program. It looks really easy!

[ I tried it and did a SetThreadLocale to French in my application class
constructor, but that didn't work. (AfxFindResourceHandle looked for
the Menu to load and homed straight in on the English resources in the
.exe - for reasons buried deep in MFC it didn't get as far as
considering to look anywhere else.)]

Dave
--
David Webber
Author MOZART the music processor for Windows -
http://www.mozart.co.uk
For discussion/support see
http://www.mozart.co.uk/mzusers/mailinglist.htm








.

Relevant Pages