i added to my setup project a license agreement dialog + the corresponding RTF document. everything works well for the english setup.msi file. for the german setup.msi no license agreement will be shown (only the default text, that an license agreement text should be added here can be seen).
info: the intial project language is english. under project definitions -> media -> language i selected a second checkbox (for german).
regards,
wolfgang
Suggested Articles
Hi Wolfgang
Here is how you could add the License Agreement for the install package in German:
- Go to the "Dialogs" page and add the "License Agreement" dialog.
- Go to the "Translations" page and select the "Languages" pane.
- Click the [ Select... ] button. In the "Localization Options" dialog check the "Enable per-element localization options" check box.
- Return to the "Dialogs" page. Click the button with the "flag" on it. In the "Localization" dialog copy the string from the text field.
- Return to the "Languages" pane from the "Translations" page. Click the [ Create... ] button. A wizard that will allow you to create a dictionary (AIL file) will be prompted. Click the [ Next... ] button twice. In the last dialog of the wizard use the [ ... ] button to specify the location and the name of your dictionary.
- Create a RTF file on your disk. The content of this file will be shown in the license agreement dialog.
- Go to the location where you saved the dictionary (AIL file) and open it in a text editor.
- Add a new entry to the document(<ENTRY> </ENTRY>) with the same structure as the above ones (you can use cut and paste if you want).
- Edit this entry as it follows:
<ENTRY id="the string you copied from the Localization dialog in the Languages pane">
<STRING lang="en" value="Your Application"/>
<STRING lang="de" value="path to the rtf file"/>
</ENTRY>
In the end you entry should look something like this:
<ENTRY id="Control.Text.LicenseAgreementDlg#AgreementText">
<STRING lang="en" value="Your Application"/>
<STRING lang="de" value="D:\license.rtf"/>
</ENTRY>
For more information of localization please check out our tutorial:
http://www.advancedinstaller.com/user-g ... guage.html
All the best,
Ciprian
Here is how you could add the License Agreement for the install package in German:
- Go to the "Dialogs" page and add the "License Agreement" dialog.
- Go to the "Translations" page and select the "Languages" pane.
- Click the [ Select... ] button. In the "Localization Options" dialog check the "Enable per-element localization options" check box.
- Return to the "Dialogs" page. Click the button with the "flag" on it. In the "Localization" dialog copy the string from the text field.
- Return to the "Languages" pane from the "Translations" page. Click the [ Create... ] button. A wizard that will allow you to create a dictionary (AIL file) will be prompted. Click the [ Next... ] button twice. In the last dialog of the wizard use the [ ... ] button to specify the location and the name of your dictionary.
- Create a RTF file on your disk. The content of this file will be shown in the license agreement dialog.
- Go to the location where you saved the dictionary (AIL file) and open it in a text editor.
- Add a new entry to the document(<ENTRY> </ENTRY>) with the same structure as the above ones (you can use cut and paste if you want).
- Edit this entry as it follows:
<ENTRY id="the string you copied from the Localization dialog in the Languages pane">
<STRING lang="en" value="Your Application"/>
<STRING lang="de" value="path to the rtf file"/>
</ENTRY>
In the end you entry should look something like this:
<ENTRY id="Control.Text.LicenseAgreementDlg#AgreementText">
<STRING lang="en" value="Your Application"/>
<STRING lang="de" value="D:\license.rtf"/>
</ENTRY>
For more information of localization please check out our tutorial:
http://www.advancedinstaller.com/user-g ... guage.html
All the best,
Ciprian
Last edited by ciprian on Mon May 28, 2007 8:28 am, edited 2 times in total.
-
dortmike2000
- Posts: 1
- Joined: Fri May 05, 2006 6:51 pm
Eula Translation
seems that the bug already exists, is this right?
thanks for your reply in advance
Mike
thanks for your reply in advance
Mike
-
Mark Preddy
- Posts: 3
- Joined: Tue Feb 13, 2007 8:48 pm
Can these instructions be updated for the current release? The list of instructions given above doesn't work because the UI has apparently changed. Also, will my single-package, multiple-language build show the correct, per-language EULAs when the installation is run under different locales?
Thanks!
Thanks!
-
Mark Preddy
- Posts: 3
- Joined: Tue Feb 13, 2007 8:48 pm