Issue with Portug(u)ese Language

[alibaba]

Hi,

I have a problem when updating my application. The updater of the previous version is calling the new setup. The updater respectively the previous application setup was built with IA < v14 and the new setup is built with IA15 (In this period IA has changed the language identifier for Portugal: in the old setup the language identifier for Portugal was "Portugese (Portugal)" and in the new version it is now "Portuguese (Portugal)".) The updater is calling the new setup and (in case Portugal was selected) is passing the value "Portugese (Portugal)" as LANGUAGE parameter.

The installation is running in semi-silent mode as IA has illustrated here: viewtopic.php?f=2&t=5703

The setup is crashing when the progress dialog should be displayed. Error message is attached (List index out of bounds).

I have already tried:

(1)to set LANGUAGE variable in setup in case "Portugese (Portugal)" was passed but it does not work, the value of LANGUAGE could not be changed! Why it is not possible to change the LANGUAGE variable with "set Variable"?

(2)to integrate also the ressource files for Portugese (Portugal) shared+standard but this does not fix the issue when the Updater is starting the setup. It fixes for standalone setup run (semisilent) but if the updater is calling the setup I still get the error.

Please let me know what you need for further investigation. We had to stop the rollout because of this issue...

[FrancescoT]

Dear Alibaba,

of course you can set the value of LANGUAGE pre-defined variable, but this have to be done at very beginning of your main script.
Are you sure you are doing it correctly?

Regards

[alibaba]

I did some tests and set LANGUAGE variable in first line of my script to a new value but it does not work at all! I tried also with compiler variable LOCMODE=VARSONLY but this also does not help. So for me it is obviously not possible to set the LANGUAGE property via script.

I found a workaround by setting the silent-value in my updates.ini to "No" to force the language selection dialog to appear and let the user select a supported language, then the strange error will not occur.

But it is of course very frustrating that IA did not take care what happens with setups (without language selection dialog) that were start with the obsolete language identifier "Portugese (Portugal)". This is definetly a bug in IA! In my opinion the whole migration scenario from setups using language "Portugese" to new setups using the new setup language "Portuguese" was not tested correctly and now I have the problems...

[FrancescoT]

Dear Alibaba,

please have a look at your other topic;
http://www.installaware.com/forum/viewtopic.php?f=2&t=9338

I have attached a sample where I set the LANGUAGE variable value.

Regards

[alibaba]

Ok, thanks for your work. Strange why I am not able to set LANGUAGE...Anyway...

But what about my second piont? What will happen if I build an installation with IA15 (localization included for Portuguese (Portugal)) an start it silent with parameter LANGAUGE="Portugese (Portugal)" (obsolete language) and show a progress dialog only. I can tell you what happens, the setup will crash. This scenario I could also reproduce with your sample project you posted in our other post.

Attached you can download the updated project (I just added 3 lines to support semisilent mode and localized again with Portuguese). Please start it with parameter:

localization_enfres.exe SEMISILENT LANGUAGE="Portugese (Portugal)" /s

You will get the error. This is exactly the scenario I am now faced with because IA changed the language identifier for Portuguese!

How to deal with it? Will IA provide a fix? I hope so....

[FrancescoT]

Dear Alibaba,

let me try the updated project ... but you should attach it.

Regards

[alibaba]

Sorry, my fault. Now you can find it.

[FrancescoT]

Ok ... I will be back as soon as possible.

Regards.

[FrancescoT]

Dear Alibaba,

the project you posted doesn't include the changes you made ... this because you stored these modifications using a personal local folder location.
Could you please include those with the project?
Please verify that the project includes correctly all the files and translations required, in order to make me able to replicate the exact behaviour you found before to post it ( ... use relative path if necessary).

By the way, I have also tried to force LANGUAGE variable to "Portugese (Portugal)" but I'm not able to replicate the same.

Let me know.

Regards.

[alibaba]

Hi Francesco,

I think it wil lbe easier if you just add the 3 lines of code to the project. Here is the code snipped:

Code: Select all

if Variable CMDLINE Contains SEMISILENT
  Set Variable Silent to FALSE
end


Insert this directly before the display dialog (progress dialog) command. Should be line 207.

I also attached the project again.

What did you test? interactive or silent will be no problem, only if you have a "semi-silent" setup with dialog(s) you will get the error.

[FrancescoT]

Dear Alibaba,

Finally I tested your project!

Yes you are right, the setup stops to work with an error ... but this is not a bug.
Unfortunately, this happens because the Language passed as command line parameter it is not correct and the same will occur, if any other possible misspelled string it is passed.

Currently, the string language identifier for Portuguese used by InstallAware it is "Portuguese (Portugal)" and this specific one must be used.
However, if you want to permit your users to continue to use the old string language identifier, you could include in your script a simple code as Language string parameter verification.
Doing this you could force (at the very beginning of your main script) the "LANGUAGE" IA pre-defined variable to a default language, if the passed command parameter is misspelled.

Hope this solves you issue.

Regards.

[alibaba]

As I said it is not possible (for whatever reason) to set the language in my script.
Also I think IA should had prevent this issue. YOU changed the language identiefier and did not matter what is happening in an update scenario! Also you did not say (in any document) that we (useres of "Portugese" language) have to insert a language verification code.
So how should I really deal with it?! I can do nothing while it would have been very easy for IA to hard-code such a language verification or even better set the language automatically to "Portuguese (Portugal)" if "Portugese (Portugal)" was passed. This would have told me that you IA folks really think before you change elemtar program features. But you just changed it and leave your customers alone with the resulting problems. I really can not understand this.
Again I have to write screeds in your forum until you realize this is a misfunction in your product. I am really tiered now.

Again I say: I don't want my customers to use the obsolete identifier but in an upgrade scenario this obsolete parameter is passed by the previous installation and so I have to deal with it.

I will now again try to implement such a "language verification" since IA does not want to solve this bug themselves...sad.

[FrancescoT]

Dear Alibaba,

As you can verify with the project I posted, the LANGUAGE pre-defined variable it is correctly assigned by the value returned by Selector Dialog I have implemented. Honestly, I don't know for which reason you are not able to assign the variable correctly ... I can only suppose that exist a problem with your project somewhere.

Regarding your other considerations, It is not my intention to convince you that we are on the right side, but I really believe that it is not such a big problem to use as workaround the approach I suggested. Of course, the approach used by IA to handle internally the LANGUAGE identifiers probably can be improved and I will try try to verify this possibility with the Dev team (... I suppose there are some drawbacks ... and due this reason this has not been implemented).

On the other hand, let me say that the changes introduced with the "Portugese" language identifier are reported with "List of Bug Fixes in InstallAware NX (65)". The full document list is available at: http://www.installaware.com/blog/?paged=2

Regards.