> The NodeConfig utility can be internationalised, but there's some work > involved. [...] > One approach would be to isolate all the strings into a separate header > file, a version of which can be written for each language. > Also, if required, the CConfigFile:: class will need to be changed, to > translate all the canned comment text into the various languages. > I've never done multilingual applications, so ideally it would require > someone bi-lingual with experience in MSVC and multilingual programming.
Hmmmm, I do it on a daily basis. What you're suggesting is to recompile the code for each separate language? Yirk. What we generally do is create sets of language DLLs (just resource DLLs) - depending on the job we either use string tables (i.e. yr standard resources) or compiled message tables (i.e. what you get when you run the standard "mc" compiler on a ".mc" file - check MSDN for "Message Compiler") Then at runtime you load the appropriate DLL, applying suitable fallback code if the required DLL isn't available for your language. It means that every string reference becomes a reference to a string resource ID (e.g. with CString::LoadString) or a call to ::FormatMessage (note, that isn't CString::FormatMessage, but a different Win32 API) - so the code does a bit more work each time it needs to access a string. But the performance hit is pretty negligable. > I could do it myself, but I can't guarantee as good a job. > Volunteers? I'll do the necessary C/C++/DLL stuff if you like. (piece of cake, to be honest). Dave _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
