Translations - Page 2 - 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

Re: Translations

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.
Can you confirm that this is a bug and tell me what the prospects might be for a fix? It may dramatically affect if/how I move forward.

Thanks.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Translations

Hello,

This is not a bug, but a missing translation in our dictionaries.

The HTML based Spring theme uses most of the Azure theme's localization IDs. Because some of these strings may not be translated, you can generate a dictionary from Dictionaries tab of the Translations page by clicking on the [ Create... ] button. The wizard will create a dictionary file containing all the strings without translation in one of the build languages.

In this particular case, the string you are mentioning has the following localization id:

Code: Select all

Azure.Control.Text.WelcomeDlg#Title
The solution is to find it among the untranslated strings from the dictionary and specify the NL translation. After changing and saving the dictionary, please be sure to restart your project before building, to ensure the changes are applied.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
bvelke
Posts: 67
Joined: Fri Jun 10, 2011 6:36 am

Re: Translations

mihai.petcu wrote:The HTML based Spring theme uses most of the Azure theme's localization IDs.
...
In this particular case, the string you are mentioning has the following localization id:

Code: Select all

Azure.Control.Text.WelcomeDlg#Title
The section of the Dutch dictionary (ui_nl.ail) that is labelled "<!-- Azure theme strings -->" has 12 entries, all of which start with "Azure.Control." The same section in the English dictionary (ui_en.ail) has more than 80 such entries.
mihai.petcu wrote:Because some of these strings may not be translated, you can generate a dictionary from Languages tab of the Translations page by clicking on the [ Create... ] button. The wizard will create a dictionary file containing all the strings without translation in one of the build languages.
OK, I did that. On the Languages tab are selected English and Dutch. I clicked on the [Create...] button and went through the wizard. On the second step ("Select Start Language"), only English is selected. The resulting .ail has a grand total of 4 records, none of which start with "Azure."

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DICTIONARY type="multilanguage" ignore="en">
  <ENTRY id="Spring.Control.Text.ExitDialog#Description">
    <STRING lang="en" value="[ProductName] has been successfully [Finish1]."/>
    <STRING lang="nl" value=""/>
  </ENTRY>
  <ENTRY id="Property.ARPCOMMENTS">
    <STRING lang="en" value="This installer database contains the logic and data required to install [|ProductName]."/>
    <STRING lang="nl" value=""/>
  </ENTRY>
  <ENTRY id="Property.Manufacturer">
    <STRING lang="en" value="MyCompany"/>
    <STRING lang="nl" value=""/>
  </ENTRY>
  <ENTRY id="Property.ProductName">
    <STRING lang="en" value="MyProduct"/>
    <STRING lang="nl" value=""/>
  </ENTRY>
</DICTIONARY>
Am I misunderstanding or shouldn't that new .ail file contain (among others) all of the "Azure.Control." lines from the English dictionary that are not in the Dutch dictionary?

Thanks.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Translations

Hi,
The section of the Dutch dictionary (ui_nl.ail) that is labelled "<!-- Azure theme strings -->" has 12 entries, all of which start with "Azure.Control." The same section in the English dictionary (ui_en.ail) has more than 80 such entries.
This is because the Dutch dictionary contains only the strings for which Advanced Installer has translations in Dutch. The missing entries are not translated, so they will default to English. There's no point in duplicating the English strings by also adding them in the Dutch dictionary
On the Languages tab are selected English and Dutch. I clicked on the [Create...] button
It's actually the Create button in Dictionaries tab. I updated Mihai's post.

Unfortunately not all strings are translated to Dutch. This is because we don't have enough resources to immediately update all languages. We mostly rely on consultants and users which are willing to translate strings in exchange for maintenance.

If you want to update our Dutch dictionary, we can extend your maintenance plan for free. Let us know if you are interested.

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

On the Languages tab are selected English and Dutch. I clicked on the [Create...] button
It's actually the Create button in Dictionaries tab. I updated Mihai's post.
Uh....I want to generate "a dictionary containing just the strings that need to be translated into the build languages," right? That's the description from the help file for the button on the Languages tab. Dutch and German are listed on the Languages tab and their dictionaries are on the Dictionaries tab. Doesn't that mean that they are registered languages?

The button on the Dictionaries tab is to "create a dictionary for an unregistered language" and contains every string in the installer, right? When I used that feature, I got a .ail with more than 3300 lines.

Dutch may not be a good example because so little of it has apparently been translated. So I ran the same tests with German. Note that the translation to the string on ExitDialog ("MyProduct has been successfully installed") is known to come out in English at runtime so it is missing a translation.

ATTEMPT #!: So I ran the [Create..] option on the Languages tab, choose "German (Germany)" as the target language and got a file with 5 records, including "Spring.Control.Text.ExitDialog#Description" :

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DICTIONARY type="multilanguage" ignore="en">
  <ENTRY id="Spring.Control.Text.ExitDialog#Description">
    <STRING lang="en" value="[ProductName] has been successfully [Finish1]."/>
    <STRING lang="de" value=""/>
  </ENTRY>
  <ENTRY id="Property.ARPCOMMENTS">
    <STRING lang="en" value="This installer database contains the logic and data required to install [|ProductName]."/>
    <STRING lang="de" value=""/>
  </ENTRY>
  <ENTRY id="Property.Manufacturer">
    <STRING lang="en" value="Wholly Genes Software"/>
    <STRING lang="de" value=""/>
  </ENTRY>
  <ENTRY id="Property.ProductName">
    <STRING lang="en" value="The Master Genealogist v8"/>
    <STRING lang="de" value=""/>
  </ENTRY>
</DICTIONARY>
ATTEMPT #2: Then I ran the [Create...] option on the Dictionaries tab and chose "German (Germany)" as the target language. I got a file with 3 records, NONE of which make any reference to ExitDialog :

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DICTIONARY type="multilanguage" ignore="en">
  <ENTRY id="Control.Text.FatalError#LogCheckBox">
    <STRING lang="en" value="Show log"/>
    <STRING lang="de" value=""/>
  </ENTRY>
  <ENTRY id="UIText.InstallMessage">
    <STRING lang="en" value="Installing files."/>
    <STRING lang="de" value=""/>
  </ENTRY>
  <ENTRY id="UIText.SharePointLogActivatingFeature">
    <STRING lang="en" value="Activating feature [1]."/>
    <STRING lang="de" value=""/>
  </ENTRY>
</DICTIONARY>
ATTEMPT #3: I noticed in the previous attempt that the target language selector now has four sub-choices for German:
German (Switzerland)
German (Austria)
German (Luxembourg)
German (Liechtenstein)
Those options were not selected in ATTEMPT #2 so I checked them (plus the parent record of "German (Germany)") and ran it again. This time I got a file with more than 11000 lines. I won't post it all here in the interest of space but here are three notable records:

Code: Select all

 <ENTRY id="Control.Text.FatalError#LogCheckBox">
    <STRING lang="en" value="Show log"/>
    <STRING lang="de" value=""/>
    <STRING lang="de_AT" value=""/>
    <STRING lang="de_CH" value=""/>
    <STRING lang="de_LU" value=""/>
    <STRING lang="de_LI" value=""/>
  </ENTRY>
  <ENTRY id="UIText.InstallMessage">
    <STRING lang="en" value="Installing files."/>
    <STRING lang="de" value=""/>
    <STRING lang="de_AT" value=""/>
    <STRING lang="de_CH" value=""/>
    <STRING lang="de_LU" value=""/>
    <STRING lang="de_LI" value=""/>
  </ENTRY>
  <ENTRY id="UIText.SharePointLogActivatingFeature">
    <STRING lang="en" value="Activating feature [1]."/>
    <STRING lang="de" value=""/>
    <STRING lang="de_AT" value=""/>
    <STRING lang="de_CH" value=""/>
    <STRING lang="de_LU" value=""/>
    <STRING lang="de_LI" value=""/>
  </ENTRY>
These are the _only_ records in the file that have a line for lang="de".

SUMMARY: So ATTEMPT #1 (the Create option on the Languages tab) seems to do what I want for German. That is, it generates a file with English strings that haven't yet been translated to German. But (a) you tell me that it is not the feature I want and (b) per my previous message, if I do the same thing for Dutch, then I get a trivial file that doesn't include the known English lines for which Dutch translations are missing.
ATTEMPT #2 (the Create option on the Dictionaries tab), the feature which you tell me I shoudl use, doesn't include a string that is known to be missing a German translation. When generated for Dutch, it includes 3300 lines which I am reluctant to ask anyone to translate until I'm confident that it is going to help. For that, I need to understand why the same process doesn't work for German.
I don't know what to make of ATTEMPT #3 since it doesn't help to translate the missing strings to "German (Germany)", i.e., lang="de".
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Translations

Hi,
I want to generate "a dictionary containing just the strings that need to be translated into the build languages," right? That's the description from the help file for the button on the Languages tab.
It doesn't work that way. When localizing for a specific language you have the following options:

1. In Advanced Installer configure the elements you want to localize to use custom localization identifiers. You can then use Create button in Languages tab to create a dictionary which localizes only those elements. This is the hard way because you need to manually identify all untranslated strings and set custom localization identifiers for them. This feature is designed for custom localization, not for updating dictionaries.

2. Another approach is to use Create button in Dictionaries tab to set the strings you want for an entire dictionary. You can of course get the already translated strings manually from our Dutch dictionary to skip some translations. This works better for what you need because it gives you direct access to all strings.

If you want to update a dictionary (only the strings which are not translated), we can send you the appropriate files. There is no built-in functionality for this.

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

Return to “Common Problems”