Setting the language on .myGuiInit

[bennaloz]

I saw I think every thread about this. I understood that I can get parameters in .myGuiInit with ${GetParameters}. When I run a .exe file from another setup I write this


ExecWait '" $DESKTOP\myfolder\myexefile.exe" $LANGUAGE' $0

because I want that myexefile.exe is of the same language of the main setup.
in myexefile.exe in .myGuiInit function I wrote this code


Function .myGuiInit
${GetParameters} $0
FunctionEnd

In $0 variable I find the language code sent by exec for example for italian I found 1040, for spanish 1034 of for french 1036 anyway I found the right code of the chosen language.
I tried setting $LANGUAGE with this code or with ${LANG_SPANISH} if I found the spanish code but this way doesn't work. Installation files page is shown in italian.(my OS language)
How can I make the language change according to the code in .myGuiInit?

I hope I was clear my english sucks
Thnks

[Yathosho]

1. i'd probably add a switch to make sure you get only the language code (eg /L=$LANGUAGE)

2. according to languages.nsi (http://nsis.sourceforge.net/Examples/languages.nsi), you should set the language in the onInit function

[bennaloz]

So have I to load the correct language file corresponding to the input language code?

Edit: I didn't say I am using MUI_LANGDLL_DISPLAY onInit to set the installer language

[Yathosho]

I didn't say I am using MUI_LANGDLL_DISPLAY onInit to set the installer language

you didn't, but it still demonstrates how to do it: StrCpy $LANGUAGE <LANG_ID>

or

;commandline should contain /L=<LANG_ID>
${GetParameters} $0
${GetOptions} $0 "/L=" $LANGUAGE

[bennaloz]

StrCpy $LANGUAGE <LANG_ID>

<LANG_ID> means 1040 for italian or means ${LANG_ITALIAN}?
Because I tried but it seems not work. I did it in .onInit function.

[bennaloz]

;commandline should contain /L=<LANG_ID>
${GetParameters} $0
${GetOptions} $0 "/L=" $LANGUAGE

Instead when I write this code on .onInit function $LANGUAGE is empty and $0 contains the language code.
If I chose spanish in $0 I find 1034 and writing
StrCpy $LANGUAGE $0
the installer remain in italian. I can't understand where I am wrong

[bennaloz]

Function .onInit
StrCpy $LANGUAGE 2057 ;to set the english setup language does not work
FunctionEnd
or
Function .onInit
${GetParameters} $0
${GetOptions} $0 "/L=" $LANGUAGE
FunctionEnd

I think $0 must contain <LANG_ID> (for example 1040,2057 it depeds) but it's empty.
So how can i get it work?

[Afrow UK]

How have you run your setup executable? As Yathosho says you need to give it /L=#.

Stu

[bennaloz]

I run ExecWait '"MySetup.exe" <LANG_ID>' without /l. I thought it was the same retrieving the <LANG_ID> on .onInit function and put it in $LANGUAGE without look for /l. Ok now it works with
ExecWait '"mysetup.exe" /l $LANGUAGE'
and onInit ${GetOptions} $0 /l $LANGUAGE
but If I chose French when I exec mysetup.exe I found in $LANGUAGE 1036 (french lang_id), but mysetup.exe is in english -.-'' and my OS is italian. Mmm boh. :confused:
Am I forgetting something?

Edit: When I run mysetup.exe I found the right languade id onInit but then I checked again $LANGUAGE while installation is in progress and I found 1033 (english U.S.) I tried with different languages and the result is the same. I found during the installation 1033. I think I am forgetting something to set the language.
Another clarification... I am using Unicode nsis. If it makes some difference

[Afrow UK]

Look at section 4.10.1 in the manual.

Stu

[bennaloz]

Look at section 4.10.1 in the manual.


Already read it.Infact my first language is english like it sais. I am sorry I was sure english means UK english and not US english. Now I tried to print $LANGUAGE if I chose english and it's 1033. Solved. I didn't put !insertmacro MUI_LANGUAGE in every setup -.-'' I didn't think it was necessary surely you thought it was obvoius. Thanks for the patience. Anyway How can I load UK English? I checked in MultiLanguages.nsi but I found only English (1033 is US english while 2057 is UK english).I should need 2057. Do you know or somebody else know it?

[Afrow UK]

You need to create your own nlf and nsh file for it (you can submit it as well in the translations forum).

Stu

[bennaloz]

You need to create your own nlf and nsh file for it (you can submit it as well in the translations forum).

Ok I'll see. Thank you again