The setup extraction dialog (see attached image) is too small for the translated text. Is there a way to increase the size of this dialog?

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/exclu...

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

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 t...

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 re...

I use it and it is a significant improvement over the built in translation manager/editor program.

I suspect this is an issue with the translation program (mTranslator.exe) and not AI. In the attached screen capture you can see that Turkish is truncated and the rest of the list (Vietnamese) is mission.

Translation Manager Pro does not exhibit this issue.

I created a custom dialog and added a drop down list box. Is 9R2 does not allow provide enough space for the items in the list box when translated. The list is truncated.

Bar_BQ, have a look at the LOCMODE=VARSONLY option (search help for LOCMODE). That might do what you're looking for. Here is my wish list. 1. Have the Localization Wizard remember the folder last used for the associated project. 2. Be able to scroll through the script windows when running the setup ...

That is what I am doing now. It just means that the text returned is different for every language. For example the English installer displays English as English. But the French version displays (and returns) English as Anglais. It would be nice to have a value returned that does not change with lang...

Looks like I was a bit to quick to blame Translation Manager Pro. The problem manifested itself again, but this time using the built in translation editor (mTranslator.exe). Using the LOCMODE pre-defined compiler variable set to VARSONLY seems to have cleared up the issue. Only time will tell if tha...

Very good. Thank you for the information. It looks like some (if not all) of the issues I have been seeing are due to Translation Manager Pro (TMP). Not sure if the issue is due to the released version of TMP or the test version I obtained. The issue that I was seeing is as follows 1. Localize proje...

There are some strange issues going on with localization. I've been using the update option when localizing my project. It must have lost synchronization because portions of my script where not being run. I removed previous localizations and exported new (without appending to existing translations) ...

If statements are also translated. I suggest that they not be localized. If a localized string is needed in an if statement one can use the Set Localization Variable to get the localized text.

I have the following statement in my IA9 code Set Variable LanguageID to 1034 I localized my project. Then later changed this line to Set Variable LanguageID to 3082 When stepping through the installation in the debugger it skips over the following if statement if Variable LanguageID Equals 3082 Set...