mekanophil
Posts: 14
Joined: Wed May 12, 2010 9:06 pm

Localization Frustrations

Hi,

Aside from the localization process, I love your product. I have found, however, that localizing the installer can be quite a headache. My overall impression is that localization was an afterthought, as it seems to be very disorganized and disconnected. I have a couple questions and observations.

1) I am using the Modern theme, with English as my default language. When I originally ran the installer in Danish, I found that almost all of the installer was not translated. However, I took a look at the dictionaries\ui_da.ail file and found it already contained many of the translated strings. The UI was just not set to use them. This is where it got really confusing. Let me use the "WelcomeDlg" as an example. The "Description" control's Translation Settings were set to use the localization identifier "Modern.Control.Text.WelcomeDlg#Description", which is not translated. When I changed it to use the default localization identifier (which I believe is just "Control.Text.WelcomeDlg#Description") it appeared correctly in Danish. So, I thought I would do this for the rest of the controls (even though the default setting should be the one that is already translated). But, when I did the same thing for the BottomNote control on the same dialog, it instead showed the localization identifier when I ran the installer. In this case, where no Danish translation exists, it must be set to "Modern.Control.Text.WelcomeDlg#BottomNote" in order to use the English version (which is clearly desirable over the localization id). What is going on here? I can't figure out how to get it to work with any type of consistency. What I want is to show the translated version if there is one, otherwise show English.

2) I have a custom control on the ExitDialog that is not translated. Ultimately it will be, so I have it set to "Always Translate", but until then I want it to show English. I can only get AI to display the localization identifier. How do I get it to show English (that I have entered in the UI) until it is translated?

This seems to be a very manual process, am I missing something? I would think that the Modern theme should be translated out-of-the box with at least the translations that you already support in your product. I really like your product, and I apologize for my frustration. Hopefully you can provide me with some answers.

Regards,
Sam
Last edited by mekanophil on Tue Oct 05, 2010 11:54 pm, edited 2 times in total.
mekanophil
Posts: 14
Joined: Wed May 12, 2010 9:06 pm

Re: Localization Frustrations

I'm seeing that there are no translations for the Modern theme in the Danish dictionary, which is odd since much of the text should be the same as in the "Classic" theme. In any case, when I generate a dictionary for untranslated project strings via the Languages tab, the untranslated localization identifiers from the Modern theme are not there. For instance, the "Description" control on the "PrepareDlg" is set to use localization identifier "Modern.Control.Text.PrepareDlg#Description", but this identifier is not in the dictionary. Why is that? I would think that if AI is not going to fall back to use the existing translation of the same text from the Classic theme, it would at least be included as part of the untranslated dictionary.

Please still address my previous questions as well. Thank you.

Regards,
Sam
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Localization Frustrations

Hello Sam,

The new themes' strings haven't been translated yet for all languages. You can translate the ui_da.ail strings for the modern theme. You can use the english strings in ui.ail as a reference by copying them to ui_da.ail and translate them. The modern theme LocIds start with "Modern.". If you wish, you can also send the translations to support at advancedinstaller dot com in order to expedite the danish translation in a future version of Advanced Installer.
2) I have a custom control on the ExitDialog that is not translated. Ultimately it will be, so I have it set to "Always Translate", but until then I want it to show English. I can only get AI to display the localization identifier. How do I get it to show English (that I have entered in the UI) until it is translated?
On the Translations page, Languages tab use the "Generate dictionary for untranslated project strings" "Create" button on the bottom.

Also, if you have not yet read our tutorial on localization, it might help:
http://www.advancedinstaller.com/user-g ... uages.html

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
mekanophil
Posts: 14
Joined: Wed May 12, 2010 9:06 pm

Re: Localization Frustrations

Thanks Gabriel. I have read the tutorial, but it really didn't help to answer the questions that I have. I have already created a dictionary for the untranslated project strings, and I have the following problems:

1) My custom controls show up in the dictionary I created. However, before they have been translated they appear as the localization id, i.e. "Control.Text.ExitDialog#WelcomeCheckBox", instead of the English that I have entered in the UI. I want them to show as English until they are translated. How do I do that?

2) I understand that the Modern theme has not been translated to Danish. What I don't understand is why the strings from the Modern theme are not in the dictionary I created for untranslated project strings. If they have not been translated, why aren't they in the untranslated dictionary?

Sam
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Localization Frustrations

Hi again Sam,
1) My custom controls show up in the dictionary I created. However, before they have been translated they appear as the localization id, i.e. "Control.Text.ExitDialog#WelcomeCheckBox", instead of the English that I have entered in the UI. I want them to show as English until they are translated. How do I do that?
Below is the corresponding generated section in the dictionary for a user button control:

Code: Select all

  <ENTRY id="Control.Text.VerifyReadyDlg#PushButton_1">
    <STRING lang="en" value="PushButton"/>
    <STRING lang="da" value=""/>
  </ENTRY>
The 'id' attribute idicates the id of the control.
The "<STRING lang="en" value="PushButton"/>" element is for reference only, so that you know the english translation.
the "<STRING lang="da" value=""/>" element represents the danish translation. The translated text goes into the value attribute, between the quotes.
Let me know if I misunderstood your question.
2) I understand that the Modern theme has not been translated to Danish. What I don't understand is why the strings from the Modern theme are not in the dictionary I created for untranslated project strings. If they have not been translated, why aren't they in the untranslated dictionary?
The generated dictionary is only for user controls and user text. Default texts usually reside in the prepackaged dictionaries.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/

Return to “Common Problems”