vbgunz
24th December 2003 12:21 UTC

how to begin getting ready a script for future translations (different languages)?
Hello,

This really wasn't too high on the todo list but I've finally made it to the task. After reviewing some example scripts and actual scripts, I am at a pause, regarding how exactly or what exactly is the best approach to getting ready a script for translation.

I cannot provide translations other than english and that already seems to be done. I would like my script translated so to present it in different languages.

Is there a really good guide on a best approach to doing this? Basically, I would like the small popup at the beginning which prompts the user to pick a language. There after the magic.

What is the best approach as I have scripts both example and real which differ very much in their approach.

I would like to hear what a guru who is already doing this has got to say. I would like and really appreciate some tips and pointers. Thanks a million!

Joost Verburg
24th December 2003 13:59 UTC

NSIS 2 supports multilingual installers. See the example scripts like "Examples\Modern UI\MultiLanguage.nsi".

For you own strings, you can use langauge strings (see Users Manual). If you want other people to help translating, you might want to put these strings in include files.

See http://nsis.sourceforge.net/archive/...instances=0,44

vbgunz
24th December 2003 15:34 UTC

Thank you Joost
Thank you Joost,

I did dibble and dabble with the file you've mentioned and compared it to the HM NIS EDIT setup script. I've seen them differ in a few ways and just wanted some confirmation.

Also very much thanks for that link to the archive. I will work with it later on today. Am really tired and seriously need a break from work.

Thanks a million for your time Joost, hopefully all will go well :)

vbgunz
25th December 2003 12:20 UTC

Hello Joost,

Thanks a million! I've got 95% of the language work out of the way thanks to you and the help manual. I got one question in which I do not think there is a positive answer but a question I need to ask.

Creating a language file effects the .nsi and .nsh installation scripts only? I mean as far as INI files go for the custom screens, their language has to be *hardcoded* into the INI's?

Thanks again Joost

kichik
25th December 2003 12:29 UTC

You can write a LangString into the INI. For example:

LangString ls ${LANG_ENGLISH} "some ini text"
Function customPage
  WriteINIStr $PLUGINSDIR\myINI.ini "some section" "some value" $(ls)
FunctionEnd

vbgunz
25th December 2003 13:24 UTC

Hello Kichik,

I am so glad to know this did not need to be hardcoded! I successfully completed this task thanks to you and Joost.

This installer keeps amazing me... Excellent work!