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

Problems adding unsupported language

We are adding an unsupported language (arabic) to our product's existing install. As per the instructions provided here, I have run the new language wizard and sent the resulting strings out to be translated. There are however, still a large amount of strings that are still untranslated, and they do not appear in the string table (a notable example being the dialog that asks the user if they really want to exit the install before completing it). Is there any location other than the String Editor where InstallShield keeps strings that we were previously unaware of? Baring that, what is the cause of the absentee strings?

Thank you, AT
Labels (1)
0 Kudos
(1) Reply
MichaelU
Level 12 Flexeran
Level 12 Flexeran

I think the string you're referring to comes from Windows Installer, which would mean it's coming from the operating system itself. There are a few of these that you cannot translate yourself. So long as you're handling the runtime support strings (0xNNNN.ini) and the language files that show up in the string tables (NNNN (UNICODE).txt) you should be good on a machine set to display in that language.
0 Kudos