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 StringsWas this helpful?
Related Articles
Migrated Project Results in OnFirstUIBeforeValueAddedServices Function to Fail 3Number of Views How to Localize Product Name in Installscript MSI Project 4Number of Views How to Localize Messagebox in Basic MSI Project 3Number of Views Logging An InstallScript MSI Project 350Number of Views Build Error -6118 on Installscript MSI project migrated from IS2016 5Number of Views
Revenera Assistant - Beta
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago