Llynix
15th January 2005 04:17 UTC

Globalization of install files
Our application has many international users. I've got the installer working for multiple languages and have included them all in the installer. But I would like to know how to define the messages I have for the message boxes etc in other languages.

Thank you,
Llynix

Llynix
15th January 2005 04:58 UTC

I do believe I figured out the answer to my own question.

LangString VAR_NAME ${LANG_ENGLISH} "text goes here."

Now what kind of bugged me. Was the multiple language install example script didn't use this AT ALL. It makes a vague reference to it while setting up a description, but doesn't utilize it.

It wasn't until I gave up on my language question and went to look up what the description thing was all about when I found the LangString reference.

Dkom
15th January 2005 08:06 UTC

Try to switch system language preferenses to every included language before launching uninstaller (or installer) - and you will see, that all messages will be in right language.

kichik
15th January 2005 11:30 UTC

Take a look at Exampes\languages.nsi. Almost all of the first 100 lines of it is for defining language strings.

Llynix
16th January 2005 08:06 UTC

Perhaps you guys missed it:

I've got the installer working for multiple languages and have included them all in the installer.

That was all from MultiLanguage.nsi which was helpful in that respect. My problem was that certain messages were defined by me in message boxes etc.. These messages show up in English regardless of the language used.

There is no reference in MultiLanguage.nsi on how to use LangString to provide your own translated strings.

Perhaps I'm not looking at the right file.

pengyou
16th January 2005 13:51 UTC

Perhaps I'm not looking at the right file.

LangString Message ${LANG_ENGLISH} "English message"
LangString Message ${LANG_DUTCH} "Dutch message"
LangString Message ${LANG_FRENCH} "French message"
..
..
MessageBox MB_OK $(Message)