cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Migrated project does not localize

Migrated project does not localize

Summary

After migrating a project from Developer 9 or older, if additional languages are added, the new strings are not translated.

Symptoms

After migrating a project from Developer 9 or older, if additional languages are added, the new strings are not translated. This can occur if the project was originally created in the older version even it was migrated multiple times in the development cycle.

Cause

The string identifier format from the Developer versions are different from the format from InstallShield. The English strings are tried as custom strings rather than predefined English strings shipped with InstallShield, so no translation takes place.

Resolution

  • Importing the English string table from a new project will allow the strings to be localized.

InstallShield stores string entries in the ISString table of the main project file (.ism file). InstallShield lets you export the string entries of a language to a text file, which you can send out for translation. After the strings have been translated, you can import the text files into the InstallShield project file.


Workaround

  • The localized string table entries from the Developer version originally created project can be imported into InstallShield so the Identifiers will match.
  • The English string identifiers can be changed to match the identifier from the localized strings.

Additional Information

Importing and Exporting Strings
Was this article helpful? Yes No
No ratings
Version history
Revision #:
1 of 1
Last update:
‎Jul 18, 2018 10:20 PM
Updated by: