InstallAware

Something really needs to be done with the localization process.

My project began to only install one component. After exporting and not preserving existing translations the issue was fixed.

Strange behavior occurs if you export translations (new entries) preserving existing translations.

It is a real pain to have to reedit the translation files multiple times.

We would like to improve the localization feature. Would you be able to provide a test case to illustrate this problem?

I would love too but unfortunately selecting not preserve the translations cleared it.

I am having and issue with LOCMODE=VARSONLY is resulting in shortcuts not being translated.

Without LOCMODE=VARSONLY I get all kinds of strange behavior. I have been fighting this for the entire day and am about to simply write a program and not use InstallAware to do it.

Seems that we have an all or nothing sort of situation with LOCMODE=VARSONLY

It would be good to have more control over localization. A mode that uses

Localized variables, Shortcut and Component definitions

So, you'd want something like an option that allows you to choose what to translate? Options like:

Translate:
[] GUI strings
[] Variable values
[] Variable names
[] Paths
[] (perhaps an option for all paths or to include or exclude shortcuts?)
[] Feature names

Does that sound right?

What I would like to be able to translate are

Dialogs,
Localized variables,
Define components, and
Shortcuts

For me paths are not necessary. However an option to allow and disallow I could see being useful. If not for me then others.

If I could ask for the world I would like options to include/exclude every section of the translation file. Options that would allow for all possible combinations. For example

LOCMODE=LocalizedVars,Shortcuts,DefComponents,Dialogs,.....

Do you understand what I mean. It is a bit complicated but would allow very fine control over what is translated.

When using anything other than LOCMODE=VARSONLY I get strange behavior.

I ended up resolving my issue by creating language specific sections of my script. Then duplicate the code in each language specific section. Putting the translated text directly into the script instructions. This works but is some what defeating of the translation software that makes InstallAware attractive.

Seems like I may be able to handle most issues by using localized variable translation only.

So for me and my current project I found a solution. It was just frustrating that I was not able to get it to work as I expected it should.

Thank you for your consideration on this topic.

Also don't get me wrong, I am still very happy that I switched from InstallShield to InstallAware.