Custom dialog and translations (6.1.1)

[Alpicus]

Hi Support,

I created a custom dialog (PKLDataFolderDlg) then add a new static text with "Data folder" as text and PKLDataFolderLabel as Name and Property Name. Then I generated a dictionary and added the new localization identifier so it look like this :

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DICTIONARY type="multilanguage">
<ENTRY id="Control.Text.PKLDataFolderDlg#PKLDataFolderLabel">
<STRING lang="en" value="Data &folder:"/>
<STRING lang="fr" value="&Répertoire Data:"/>
<STRING lang="de" value="XXXXXXXXXXXXXXXXXXXXXX"/>
</ENTRY>
</DICTIONARY>

I the Translation dictionaries, it's on the first position before these below :
<ui.ail>
<ui_fr.ail>
<ui_de.ail>
<ui_en.ail>

After building, the original text from dialog is displayed during the runtime in french. I guess I made a mistake Which one ?

Thanks for ur future answer,

Phil

[Cosmin]

Hi,

After building, the original text from dialog is displayed during the runtime in french.

Can you please give me more details about this? By "original text" you mean only the static text or all the text in the dialog?

Regards,
Cosmin

[Alpicus]

Hi Cosmin,

I mean the text I wrote in "Display" > "Text" propety of the static text control.

Regards,

Phil

Hi,

After building, the original text from dialog is displayed during the runtime in french.

Can you please give me more details about this? By "original text" you mean only the static text or all the text in the dialog?

Regards,
Cosmin

[Cosmin]

Hi,

We have tested this scenario and we cannot reproduce the behavior you encountered. Can you please send us a small test case which shows this problem (the AIP, the resulted MSI and the custom dictionary file) to support at advancedinstaller dot com so we can investigate it?

Regards,
Cosmin

[Alpicus]

Thanks for ur fast reply,

Email sent.

Regards,

Phil

Hi,

We have tested this scenario and we cannot reproduce the behavior you encountered. Can you please send us a small test case which shows this problem (the AIP, the resulted MSI and the custom dictionary file) to support at advancedinstaller dot com so we can investigate it?

Regards,
Cosmin

[Cosmin]

Hi,

Please note that you have not created the dictionary correctly. Here are the steps to create a custom dictionary:
- go to the "Languages" tab in the "Translations" page
- click the "Select" button and check the "User Interface" and "Enable per-element localization options" checkboxes
- go to the "Dialogs" page and select your custom text control
- click in the "Text" field in the "Properties" section
- click the button with the flags next to the "..." button in the "Text" field
- in the "Localization" dialog select the "Always translate this string" and "Using specified localization identifier" options
- got to the "Languages" tab in the "Translations" page
- click the "Create" button
- follow the wizard and create a new custom dictionary
- open the generated AIL file with a text editor
- write the strings for the other languages
- save the AIL file (you must save it in UTF-8 format)
- save your Advanced Installer project, close it and reopen it
- build and run the project

We have tutorials for this, please take a look:
http://www.advancedinstaller.com/user-g ... uages.html
http://www.advancedinstaller.com/user-g ... guage.html

Let me know if the problem persists after creating a dictionary by following these steps.

Regards,
Cosmin

[Alpicus]

Many Thanks Cosmin,

It works great !

I'm excited to finish my tests with the trial version to purchase the enterprise version

Regards,

Phil