Page 1 of 1

translation of EULA, and testing localized installers?

Posted: Thu Jul 17, 2008 3:34 pm
by fxtech
This is my first localized installer - I have translations for 5 different languages. But I don't see anything in the documentation about how to do the different translations of the EULA or Readme.

Also, I'd like to run the installer "in French mode" for example to make sure all the strings are right, but no my English system. I didn't see a language selection menu when I ran the installer. Is there some command-line switch I can use to force a language?

Posted: Fri Jul 18, 2008 11:16 am
by Alex_Ronquillo
The language of the EULA is changed by adding the different EULA's as creatives in the form license.<language>.txt. This is the help file, topic "Localization Wizard".

For your second question, when you localize your project, you get a "Display Language Selection Dialog Box" checkbox in the project properties in design view. You can check it to get to choose the language at the beginning. Also, if you would like to set the language from command line, You can always run your installer and add as parameter LANGUAGE=French for example.

Posted: Fri Jul 18, 2008 11:59 am
by fxtech
Aha, indeed the info was there - silly me!

After importing my translations and hooking up my license files, if I select a non-English language, I get this error:

Runtime error in setup script:
Line 50: List index out of bounds (407)

Any idea what that means?

Posted: Fri Jul 18, 2008 12:08 pm
by Alex_Ronquillo
Sorry, please described the whole process you followed.

Posted: Fri Jul 18, 2008 1:42 pm
by fxtech
Ok, I had originally exported all my strings using the translation wizard - I sent those off to the translator, who returned them translated (French, Spanish, German, Japanese). They also translated my license file.

I used the wizard to import the new translations. I renamed the license files as you suggested, and added them to my resources. I enabled the language selection menu in the Project options.

When I first did this, English did not show up as an option in the installer. The translation wizard had brought in Translations.Original, as well as the other 4 translation files, but hadn't made a Translations.English file, so I added that file into the resources manually. Now English shows up properly as the default translation in the installer menu. If I use English, it works fine.

If I pick any of the other languages, I get that error.

My MSI is pretty stock - line 50 in my script has nothing to do with that error as far as I can tell (it's an else statement).

Posted: Fri Jul 18, 2008 1:56 pm
by Alex_Ronquillo
I think the manual addition of a language is the problem. Instead, try importing your language files again including English.

Posted: Fri Jul 18, 2008 2:40 pm
by fxtech
Tried that - this time I checked off all 5, including English. It asked me if I wanted to replace my previous translations, which I did.

Same error. :cry:

Posted: Mon Jul 21, 2008 11:35 am
by fxtech
Found it. The translators missed a couple of strings at the end of the non-English files.

BTW - what encoding do the strings need to be in?