Translations - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

bvelke
Posts: 67
Joined: Fri Jun 10, 2011 6:36 am

Translations

I want my user to be able to choose between English, German, and Dutch (i.e., Netherlands) for the installation language and have the entire installation interface adjust accordingly using the default dictionaries. Those three languages are selected on the Translations screen. The Localization Options screen has User Interface checked and nothing else.

Now several things don't seem to be working properly:
1) The title on all of the windows says "MyProduct Setup", regardless of installation language. That is, the word "Setup" isn't translated.

2) The fast little "Extracting the files from the main application" message box IS translated properly but the next one that says "Preparing to install..." is not. The Dialogs screen does have a default PrepareDlg but it doesn't have any text objects on it (only a title and Back and Next buttons) so I don't know if that's even the dialog in question. It is also much bigger than the one that I see at runtime.

3) The second object on InstallTypeDlg says "Choose the installation type" and that's how it reads at runtime when the installation language is English. When the installation language is Dutch, it says "Install MyProduct for" (i.e., in English). When the installation language is German, it says the German equivalent of "Install MyProduct for" (i.e., translated). But I don't understand where it gets that string in the first place and why it is translated to one language but not to another. I thought that there might be two instances of InstallTypeDlg on the Dialogs screen but there's only one. I get the same result whether the "Translation Setting" for the object in question is "Inherit global settings", "Using default localization identifier" or "Using specified localization identifier". (In the latter case, I just use the value that is automatically inserted in that field).

4) The "Only me" and "Everyone" radio buttons on InstallTypeDlg are correct in English at runtime. But if the installation language is German or Dutch, they literally say:
RadioButton.Text.AI_InstallPerUser#1
RadioButton.Text.AI_InstallPerUser#1
I get the same result whether the "Translation Setting" for the objects in question are "Inherit global settings", "Using default localization identifier" or "Using specified localization identifier".

5) On LicenseAgreementDlg, the check box says "I accept the terms of this agreement" and it is correct in English at runtime. But if the installation language is German or Dutch, then it literally says:
Control.Text.LicenseAgreementDlg#EulaAgreeCheckBox
I get the same result whether the "Translation Setting" for the object in question is "Inherit global settings", "Using default localization identifier" or "Using specified localization identifier".

Subsequent dialogs have other instances of the same sort of translation problems.

Now I've obviously screwed something up and these problems are no doubt caused by the same thing but I am lost in the options. I just want all interface objects to translate to the selected language without having to customize them though the "Translation Setting" or elsewhere.

Thanks.
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Translations

Hi Bob,

1) The dialog title is built out of the name following two properties, ProductName and Setup. After a quick look through our dictionaries I can see our translators have used the same value for "Setup" property in the these languages, probably they considered this term is inherited as it is.

You can easily change its value, just go to the installation folder of Advanced Installer, locate "dictionaries" subfolder. There you will find two files, "ui_de.ail" and "ui_nl.ail". These are standard XML files, which you need to edit with an UTF-8 editor, for example Notepad++ which is free.

In these files locate the line "<STRING id="Property.Setup" value="Setup"/>" and change the value. After this restart Advanced Installer so the dictionaries are reloaded and everything should be changed as desired.

2) Can you give us a screen-shot with the dialog, or send us the .aip file? I am not sure to which dialog you are referring of.

3) The dictionary entry for this string (German) is the following: <STRING id="Control.Text.InstallTypeDlg#InstallTypeText" value="Installiere [ProductName] für:"/>
It seems the equivalent for this is missing from the Dutch translation. You can edit the dictionary as I mentioned above, insert the row and change the value.

4) Testing with the default settings shows the correct strings for English and German, indeed for Dutch it is used the English value because it is no translation available.
The identifiers used in the dictionary are "RadioButton.Text.InstallTypeDlg#1" and "RadioButton.Text.InstallTypeDlg#2". What theme is your package using, is it not the classic one?

5) These strings are correctly translated on both German and Dutch, tested with Classic theme. What you encountered could happened because you selected "User Interface"
under localization options from Translations page. Enabling this is not required if you don't add new custom dialogs, i.e. created by you. Predefined dialogs should be automatically translated as long as they have a translation, or use the English value if a value for the respective language is not found.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
bvelke
Posts: 67
Joined: Fri Jun 10, 2011 6:36 am

Re: Translations

Bogdan wrote:You can easily change its value, just go to the installation folder of Advanced Installer, locate "dictionaries" subfolder. There you will find two files, "ui_de.ail" and "ui_nl.ail". These are standard XML files, which you need to edit with an UTF-8 editor, for example Notepad++ which is free.
OK, I did that, thanks.
2) Can you give us a screen-shot with the dialog, or send us the .aip file? I am not sure to which dialog you are referring of.
This is it. Notice that the window title isn't translated either.
preparing.jpg
preparing.jpg (21.48 KiB) Viewed 18539 times
3) The dictionary entry for this string (German) is the following: <STRING id="Control.Text.InstallTypeDlg#InstallTypeText" value="Installiere [ProductName] für:"/>
It seems the equivalent for this is missing from the Dutch translation. You can edit the dictionary as I mentioned above, insert the row and change the value.

4) Testing with the default settings shows the correct strings for English and German, indeed for Dutch it is used the English value because it is no translation available.
The identifiers used in the dictionary are "RadioButton.Text.InstallTypeDlg#1" and "RadioButton.Text.InstallTypeDlg#2". What theme is your package using, is it not the classic one?
I am using Spring. If I switch to Classic, some of those strings are translated properly (e.g., "The Setup Wizard will install MyProduct on your computer. Click Next to continue or close the window to exit the Setup Wizard."). Don't all of the themes use the same dictionaries? How can the same string get translated in one theme and not in another?
Predefined dialogs should be automatically translated as long as they have a translation, or use the English value if a value for the respective language is not found.
OK, I guess I just don't understand how standard dialogs don't have standard translations in the dictionary for the languages that are offered as choices.
bvelke
Posts: 67
Joined: Fri Jun 10, 2011 6:36 am

Re: Translations

Sigh. This is very frustrating.

I switched to the Classic theme in order to test and compare (see above).

Then I switched back to Spring and instead of the "Preparing to install..." dialog in the screen shot above, I now get this one:
prepare2.jpg
prepare2.jpg (96.85 KiB) Viewed 18539 times
And the InstallTypeDlg which DID look like this at runtime:
install_type1.jpg
install_type1.jpg (109.32 KiB) Viewed 18539 times
now looks like this at runtme:
install_type2.jpg
install_type2.jpg (107.45 KiB) Viewed 18539 times
Notice that while the button text no longer displays the tokens, there is a graphic in the top-left corner, the second line of text is different, the buttons look different, and the words "Advanced Installer" is now in the top-right. How do I get the Spring theme dialogs back the way that they were but have them translated properly?
bvelke
Posts: 67
Joined: Fri Jun 10, 2011 6:36 am

Re: Translations

FWIW, InstallTypeDlg on the Dialogs window shows a third variation:
install_type3.jpg
install_type3.jpg (100.19 KiB) Viewed 18539 times
Notice that there is no graphic in the top-left, no "Advanced Installer" in the top-right, and the Back/Next button use the previous style ... and in those respects it is like install_type1.jpg which is what I want. But the second line of text is "Choose the installation type" which is the same as install_type2.jpg.

So how it used to look (install_type1.jpg), how it says it will look (install_type3.jpg), and how it actually looks at runtime (install_type2.jpg) are all different.

Can you understand why I am frustrated? I just wanted to give the user the ability to translate standard dialogs to German or Dutch. One would think that it wouldn't be this difficult.
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Translations

Hi,

The problems with the themed buttons and missing graphics appear because you are launching the MSI package, instead of the EXE generated by Advanced Installer.

Please note that all custom themes, except Classic, require Enhanced User Interface to be activate, therefore an EXE setup is generated as output. To make sure only the EXE is launched you can go to Media page, Bootstrapper tab and set it to include the installations files in it.

The correct UI is the one that presents the graphics and logo "Advanced Installer". Some problems could appear with the translations too because you launched the MSI instead of the EXE. After you make sure only the EXE is launched you should check the texts again.
Don't all of the themes use the same dictionaries? How can the same string get translated in one theme and not in another?
No, some strings are particular for each theme and some are shared, you can find them in the same dictionary. For example from what I can see the German dictionary uses the same strings form Spring and Azure themes, for PrepareDlg dialog. For Dutch the translation is missing, so English is used.

Spring is an HTML theme, so it uses a different implementation design. In order to find the localization IDs of the elements present on its dialogs you need to go
in the installation folders of Advanced Installer, "themes\spring\fragments" folder and open the file UI.aip in Notepad++. Here you will locate the component
"<COMPONENT cid="caphyon.advinst.msicomp.MsiPropsComponent">" under which you can find the localization IDs for text elements present on the dialogs, so you
can look for them in the dictionaries and modify/create them.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
bvelke
Posts: 67
Joined: Fri Jun 10, 2011 6:36 am

Re: Translations

Bogdan wrote:The problems with the themed buttons and missing graphics appear because you are launching the MSI package, instead of the EXE generated by Advanced Installer.
No, "Build Project" creates an .EXE and that's what I'm launching.
Please note that all custom themes, except Classic, require Enhanced User Interface to be activate, therefore an EXE setup is generated as output. To make sure only the EXE is launched you can go to Media page, Bootstrapper tab and set it to include the installations files in it.
On that page, "Create EXE setup file" is checked and "Include install files in EXE" is selected.
The correct UI is the one that presents the graphics and logo "Advanced Installer".
I don't know what you mean by the "correct" UI. I want the dialog design that I had before starting this thread.

We seem to be making negative progress here -- and given your limited support hours and lack of phone support, I'm now looking at going through the weekend without a solution.

Please just tell me how to restore the dialogs to the characteristics that they had before I started this thread (as reflected in preparing.jpg and install_type3.jpg above) ... and then I'll take another crack at my original questions about how to translate them.
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Translations

Hi,
No, "Build Project" creates an .EXE and that's what I'm launching.
Can you also check in Themes page, under Settings tab, if Enhanced User Interface option is enabled. As I said, the UI of the dialog visible in "install_type3.jpg" is not good.
The UI of the dialogs should look like the one from "install_type2.jpg".

The dialog from "preparing.jpg" usually appears when Advanced Installer automatically uninstalls a previous version of the same application that you tested on the machine,
this dialog will not be seen by your users. The first dialog they will see is "prepare2.jpg". Advanced Installer automatically uninstalls the old version when you launch the installer using the "Run" command from the toolbar.

If Advanced Installer would not perform the uninstall automatically you would see the following error message:
http://www.advancedinstaller.com/user-g ... question50

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
bvelke
Posts: 67
Joined: Fri Jun 10, 2011 6:36 am

Re: Translations

Bogdan wrote:Can you also check in Themes page, under Settings tab, if Enhanced User Interface option is enabled.
It is set to "Always".
As I said, the UI of the dialog visible in "install_type3.jpg" is not good.
I disagree; that's the design I want. Are you seriously telling me that the result of asking for help with translations is that I've lost the design for header and buttons that I prefer and I can't get them back??

Is it "good" that the design that is reflected on the Dialogs screen (which is what I want) is not what I get at runtime??
The dialog from "preparing.jpg" usually appears when Advanced Installer automatically uninstalls a previous version of the same application that you tested on the machine,
this dialog will not be seen by your users.
I believe you but I'm not sure how that's relevant to the issue at hand. I am not uninstalling anything.
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Translations

I attached a sample project created with version 8.6, with the original dictionaries (not custom changes), that uses Spring theme.
This package has the use UI I said is the correct one, i.e. from picture "install_type2.jpg".

I also included the option to show the language selection dialog, as my machine is in English, for easy testing.

Regards,
Bogdan
Attachments
sample.aip
(20.36 KiB) Downloaded 794 times
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
bvelke
Posts: 67
Joined: Fri Jun 10, 2011 6:36 am

Re: Translations

Could you please answer the questions in my previous message?

Can I please hear from Cosmin on this issue as we seem to be getting nowhere.
bvelke
Posts: 67
Joined: Fri Jun 10, 2011 6:36 am

Re: Translations

What am I supposed to be testing with your project? It works as we both expected it to -- with dialogs that you think look "good".

How is that responsive to my questions?
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Translations

Hi,

This is a complex discussions, so it may seem like you are not getting any answers. I will try to summarize what Bogdan was trying to explain:

1. We always add new features in functionality in each release. Some of them are predefined dialogs or UI elements. Since we offer support for a log of languages and rely on consultants for providing translations, some dictionaries may be out of date. This is why some strings are translated and some are not.

I'm afraid that we don't have a quick fix for this. But if you can get the translated strings, you can edit the dictionaries manually like Bogdan mentioned.

2. By default, if a string doesn't have a translation for a specific language, the English string is used. This is by design and cannot be changed. This is why you see English strings in a Dutch installation.

3. When clicking Select button in Translations page, you can specify which parts of your installation should always be localized. This is used when manually providing all strings for a language.

You mentioned that you selected "User Interface". Since some strings do not have translations, their localization identifier is used instead of an English string (for example "RadioButton.Text.AI_InstallPerUser#1"). This helps you provide a translation for that string (dictionaries use the localization IDs).

I assume you don't want to localize strings manually. So you should revert to the behavior from point 2 by unchecking "User Interface" in Translations page.

4. Our dialog editor cannot display dialogs in the exact same way they look during install. This is because most dialogs elements are dynamic. For example, PrepareDlg subscribes to installer events which are not accessible outside an installation process. This is why it contains empty text controls in our editor, but shows text during install.

There are also controls which are shown differently based on specific elements or environments. For example, radio buttons can be placed only in a radio button group control. The group control can be hidden so you see only radio buttons during install. But in our dialog editor you need to see the group control so you can edit its properties, even if it's hidden during install.

5. Some dialogs are shown by Windows Installer automatically, for example the "Preparing to install" dialog. These are internal Windows Installer dialogs and cannot be edited or translated. They are shown in the system language.

Bogdan and I suggest resetting your UI
- uncheck "User Interface" and any other segments you checked in Translations page
- switch to a different theme and switch back to reset it
- customize the installation dialogs the way you need, disregarding translations for now

After that, you can analyze our explanations and determine if the localization feature works in an acceptable way. We would also like to hear any suggestions you may have for making localization simpler.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
bvelke
Posts: 67
Joined: Fri Jun 10, 2011 6:36 am

Re: Translations

Thanks for stepping in, Cosmin.
cosmin wrote: 1. We always add new features in functionality in each release. Some of them are predefined dialogs or UI elements. Since we offer support for a log of languages and rely on consultants for providing translations, some dictionaries may be out of date. This is why some strings are translated and some are not.

I'm afraid that we don't have a quick fix for this. But if you can get the translated strings, you can edit the dictionaries manually like Bogdan mentioned.

2. By default, if a string doesn't have a translation for a specific language, the English string is used. This is by design and cannot be changed. This is why you see English strings in a Dutch installation.
I understand all that, thanks.
3. When clicking Select button in Translations page, you can specify which parts of your installation should always be localized. This is used when manually providing all strings for a language.

You mentioned that you selected "User Interface". Since some strings do not have translations, their localization identifier is used instead of an English string (for example "RadioButton.Text.AI_InstallPerUser#1"). This helps you provide a translation for that string (dictionaries use the localization IDs).

I assume you don't want to localize strings manually. So you should revert to the behavior from point 2 by unchecking "User Interface" in Translations page.
I've done that a while ago, thanks.
4. Our dialog editor cannot display dialogs in the exact same way they look during install. This is because most dialogs elements are dynamic. For example, PrepareDlg subscribes to installer events which are not accessible outside an installation process. This is why it contains empty text controls in our editor, but shows text during install.

There are also controls which are shown differently based on specific elements or environments. For example, radio buttons can be placed only in a radio button group control. The group control can be hidden so you see only radio buttons during install. But in our dialog editor you need to see the group control so you can edit its properties, even if it's hidden during install.
I understand that too but I've asked repeatedly for advice about how to restore the look of the headers and buttons to the way they were before I started this thread (as shown in install_type3.jpg) which is the way that they are STILL shown in the Dialog window of AI.

By sending me a sample project, etc., Bogdan seems determined to convince me that the defaults are otherwise (which I accept but is beside the point) and that what I want is not "good" (which I do not accept). Clearly, it is possible to get what I want because (1) I had them before I followed Bogdan's advice to switch to Classic and back again and (2) they are still shown the way that I want them in the Dialog window. So what factors would cause them to be changed at runtime and how do I stop them from doing that?
5. Some dialogs are shown by Windows Installer automatically, for example the "Preparing to install" dialog. These are internal Windows Installer dialogs and cannot be edited or translated. They are shown in the system language.
Thanks, that's the first that I've heard that explanation.
Bogdan and I suggest resetting your UI
- uncheck "User Interface" and any other segments you checked in Translations page
- switch to a different theme and switch back to reset it
I've done those things and that's when the problems with the graphic elements started. But I switched to Classic and back to Spring today for good measure.
- customize the installation dialogs the way you need, disregarding translations for now
OK, once again, how do I do that?

For instance, how do I change the Prev/Next buttons from the blue graphic buttons shown in install_type2.jpg to the small black text ones in install_type3.jpg? Keep in mind that the Dialog window in AI already looks like install_type3.jpg (i.e., with small black text buttons). Their Button Type attribute is "Text" and the Display Text is "[ButtonText_Back]" and "[ButtonText_Next]" which is they way that I want them. But the installer uses blue graphic buttons at runtime.

And while I'm focusing for the second day on how to restore the graphics to the way that I had them previously, it is worth noting regarding my original question that:
1) On the Dialog window, the title of the WelcomeDlg says "Welcome to the MyProduct Setup Wizard"
2) The display text for it is "Welcome to the [ProductName] [Wizard]"
3) The localization setting is "Always translate this string > Using specialized localization identifier" with a value of "Control.Text.WelcomeDlg#Title"
4) The "Control table" section of the English Dictionary (ui.en.ail) contains this value:
<STRING id="Control.Text.WelcomeDlg#Title" value="Welcome to the [ProductName] [Wizard]"/>
5) The "Control table" section of the Dutch Dictionary (ui.nl.ail) contains this value:
<STRING id="Control.Text.WelcomeDlg#Title" value="Welkom bij [ProductName] [Wizard]"/>
6) If the user selects Dutch (Nederlands) at runtime, the title of WelcomeDlg says "Welcome to the MyProduct Setup Wizard" (not "Welkom bij MyProduct Set-up Wizard").
7) The button text and a few other elements ARE being translated properly to Dutch.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Translations

Hi,
I've asked repeatedly for advice about how to restore the look of the headers and buttons to the way they were before I started this thread (as shown in install_type3.jpg)
The Spring theme uses mostly HTML controls. Since our dialog editor is not really an HTML editor, it's currently not very accurate when it comes to representing the HTML files. This is why there are differences between what you see in our dialog editor and what you see during install. As a side-note, in Dialogs page you can use the Test Installation UI toolbar button to see the actual installation UI.

Additionally, most of the customizing needs to be done by manually modifying the HTML files. You can find these files in "themes\spring\resources\html" subfolder from Advanced Installer installation folder.

We have on our TODO list some improvements which will offer the dialog editor a more accurate representation of the HTML files and offer more control over these dialogs.

Another approach would be to disable enhanced UI in Settings tab from Themes page. This way your installation UI will be more similar to what you see in our dialog editor. However, advanced features like control transparency and 32-bit color icons will not be supported (Windows Installer doesn't support them). So your dialogs will look like install_type1.jpg.
how do I change the Prev/Next buttons from the blue graphic buttons shown in install_type2.jpg to the small black text ones in install_type3.jpg?
A solution is to manually modify the HTML files and change the button styles. Another solution is to disable enhanced UI.
If the user selects Dutch (Nederlands) at runtime, the title of WelcomeDlg says "Welcome to the MyProduct Setup Wizard" (not "Welkom bij MyProduct Set-up Wizard").
This looks like a bug. We will investigate this behavior on Monday and post in this thread as soon as we have an answer.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”