🚀 go-pugleaf

Rob Kennedy wrote:

> Could you just send the numeric error code, and let the client machine 
> generate the error message using the local language?

Yes but since OS error messages are not too instructive somtimes, in many
cases the final error message is generated combining information from
inside the project and from the OS, as in

Can't open the %s project, OS reports this error: %s - Try again later.

OTOH, the same happens on the client: If the computer has a german OS
installed, and my software is switched to english, OS messages still appear
in german language.

> You can pass a language identifier as the fourth parameter to 
> FormatMessage. The OS needs to know that language.

I tried this but all I get is, depending on the language id, either the one
installed language or an empty string.

I assume that on a 'normal' Windows there is only one language available
per module, and that seems to be true for the kernel modules, too. However,
I've found two promising CDs labelled 'multilingual user interface' at my
MSDN heap, and I'm going to try these in a Vmware box the next days.

-Michael