Currently I am using an evaluation version of Advanced Installer (professional). We want to purchase the software for installing our freeware simulation authoring program SimQuest (http://www.simquest.nl). So far the program does exacly what we would like it to do, except for one thing. Our software is multilangual and we would like to make installers for all the languages we support. In our software the languages is set by a registry key.
Current user > Software > University of Twente > SimQuest > 5.2 > Language > [key] language [value] #english
I would like the installers to 'install' the right language value for this key (e.g. #english and #dutch). I tried to do this by:
- selecting the languages English (default) and Dutch
- set Enable per-element localization options
- Modify the registry key
- select the flag button
- select always translate this string
- select using specified ... (the text field displays: Registry.Value.language)
- open <ui_nl.ail> in a texteditor
- add: <STRING id="Registry.Value.language" value="#dutch"/>
- import ui_nl.ail
When running the setup however I get a message that the registry key cannot be set.
What am I doing wrong?
Jan van der Meij
University of Twente
Suggested Articles
Hi,
The way to do that is described in the "Other Languages" tutorial. Please visit:
http://www.advancedinstaller.com/user-g ... uages.html
The problem is that you should create a new dictionary using the "Create" button on the "Media" -> "Languages" page. You shouldn't modify the ui_nl.ail dictionary.
Hope this helps.
Regards,
Mihai
The way to do that is described in the "Other Languages" tutorial. Please visit:
http://www.advancedinstaller.com/user-g ... uages.html
The problem is that you should create a new dictionary using the "Create" button on the "Media" -> "Languages" page. You shouldn't modify the ui_nl.ail dictionary.
Hope this helps.
Regards,
Mihai
When creating a new dictionary, AI does not show the non-translated elements. It only gives:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DICTIONARY type="multilanguage" ignore="en">
</DICTIONARY>
In trying to 'translate' my registy key I added the following content:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DICTIONARY type="multilanguage" ignore="en">
<ENTRY id="Registry.Value.language">
<STRING lang="en" value="#English"/>
<STRING lang="nl" value="#Dutch"/>
</ENTRY>
</DICTIONARY>
I added the dictionary to my project and also imported it.
But it does not work. When installing my project I get the message:
(translated from the Dutch message)
Could not write language to key\Software\University of Twente\SimQuest\5.2\Language. Check if you have enough rights ...
What am I doing wrong?
Jan
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DICTIONARY type="multilanguage" ignore="en">
</DICTIONARY>
In trying to 'translate' my registy key I added the following content:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DICTIONARY type="multilanguage" ignore="en">
<ENTRY id="Registry.Value.language">
<STRING lang="en" value="#English"/>
<STRING lang="nl" value="#Dutch"/>
</ENTRY>
</DICTIONARY>
I added the dictionary to my project and also imported it.
But it does not work. When installing my project I get the message:
(translated from the Dutch message)
Could not write language to key\Software\University of Twente\SimQuest\5.2\Language. Check if you have enough rights ...
What am I doing wrong?
Jan
Hi,
You should follow the same steps as described in the tutorial. The difference is that you should check the "Registry -> Registry key and values" option in the "Localization Options" dialog tree, instead of the "Features" one.
AFTER you have added the registry key, use the wizard to generate the new dictionary. Edit the new dictionary. You don't have to add the dictionary as it will be automatically added after the wizard generates it.
Regards,
Mihai
You should follow the same steps as described in the tutorial. The difference is that you should check the "Registry -> Registry key and values" option in the "Localization Options" dialog tree, instead of the "Features" one.
AFTER you have added the registry key, use the wizard to generate the new dictionary. Edit the new dictionary. You don't have to add the dictionary as it will be automatically added after the wizard generates it.
Regards,
Mihai
Thanks for your support!
What I did wrong was create the dictionary at the wrong page. This is a bit confusing in the tutorial. I seems that you have to create the dictionary at the Media - Language page and not at the Translate page.
When following the tutorial and check registry - registry keys, IA made a mess of the registry when installing the program
I have no idea why.
The good news is that when I followed the following steps
- selecting the languages English (default) and Dutch
- set Enable per-element localization options
- Modify the registry key
- select the flag button
- select always translate this string
and then create the dictionary at the Media - Language page, specify the registry values for Dutch, save it and NOT import it again, all works great!
What I did wrong was create the dictionary at the wrong page. This is a bit confusing in the tutorial. I seems that you have to create the dictionary at the Media - Language page and not at the Translate page.
When following the tutorial and check registry - registry keys, IA made a mess of the registry when installing the program
I have no idea why.
The good news is that when I followed the following steps
- selecting the languages English (default) and Dutch
- set Enable per-element localization options
- Modify the registry key
- select the flag button
- select always translate this string
and then create the dictionary at the Media - Language page, specify the registry values for Dutch, save it and NOT import it again, all works great!
Hi,
Thank for the observation, we changed that section in the tutorial to make it more clear.
You have probably made a mistake a some point in one of the tutorial steps. The result should have been the correct one.
The solution you have used is correct too, although a bit more complicated.
Regards,
Mihai
Thank for the observation, we changed that section in the tutorial to make it more clear.
You have probably made a mistake a some point in one of the tutorial steps. The result should have been the correct one.
The solution you have used is correct too, although a bit more complicated.
Regards,
Mihai