localization not working in 6.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!

sharky-
Posts: 5
Joined: Wed Mar 12, 2008 3:17 pm

localization not working in 6.2

We have a project in Advanced installer for quite some time now, but since I installed AI 6.2, the license agreement dialog is suddenly empty for all languages but the default (english), in both language-per-file and multilanguage installs.

Also, the 'localization' button besides the filename in the licenseagreement dialog has disappeared, although right-click -> localization does show and seems to function.

I have checked that the localization ID is correct and available in a translation file and that the 'UI' option is checked in the localization options.

Even in a totally new project, I seem to be unable to localize the license agreement in 6.2.

Maybe I'm missing a new option in 6.2 ?
sharky-
Posts: 5
Joined: Wed Mar 12, 2008 3:17 pm

To clarify, the dialog itself shows OK but the localized RTF is not placed inside the scroll window. In english, it works ok (our default language), but in any other language, the scrollwindow remains empty as if the RTF file itself were empty.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,

This happens because we changed some things in the localization feature. In order to update your AIP, please follow these steps:
- go to the "Translations" page and click the "Select" button
- in the "Localization Options" dialog check the "User Interface" option
- go to the "Dialogs" page and set a RTF file for the License Agreement
- click the localization button and modify the localization identifier (for example set it to "LicenseAgreement")
- go to the "Translations" page and use the "Create" button to generate a custom dictionary
- open the generated AIL file with a text editor
- for the "LicenseAgreement" ID make sure you have valid paths to valid RTF files for each language (you can use the same RTF for all languages if you want)

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
sharky-
Posts: 5
Joined: Wed Mar 12, 2008 3:17 pm

I got it to work ... kind of


We have (and need) relative paths in the ail file, but I can only get the translations to work with absolute paths.

The dangerous part is that I seem to have to restart AI and then rebuild to see if the changes in the AIL file have been taken into account.

So in short, I have two problems:
1) relative paths seem to be ineffective in .ail files
2) the .ail file is only reloaded when you restart AI
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,
1) relative paths seem to be ineffective in .ail files
If you are referring to using the paths of some files from your project in a dictionary file, please note that this is not possible because their installation path has not been set yet. If this is not what you are referring to then please give me more details.

Also, I'm not sure why you would need this since the paths of the RTF files for example are needed only at buildtime, not at runtime.
2) the .ail file is only reloaded when you restart AI
We are aware of this problem in Advanced Installer and we will implement a fix for it as soon as possible.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
sharky-
Posts: 5
Joined: Wed Mar 12, 2008 3:17 pm

We need the paths to the RTF files to be relative because we use an automated build which checks out all the files from a subversion repository. If you use absolute paths to the RTF files, then the build would only work if you check out your files into a specific location.

My AIL file now says

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DICTIONARY type="multilanguage" ignore="en">
  <ENTRY id="LicenseAgreement"> 
    <STRING lang="en" value="licenseagreement\eula.rtf"/> 
    <STRING lang="nl" value="licenseagreement\eula_nl.rtf"/> 
    <STRING lang="de" value="licenseagreement\eula_de.rtf"/>
    <STRING lang="fr" value="licenseagreement\eula_fr.rtf"/>
    <STRING lang="it" value="licenseagreement\eula_it.rtf"/>
    <STRING lang="pt" value="licenseagreement\eula_pt.rtf"/>
    <STRING lang="pt_BR" value="licenseagreement\eula_pt.rtf"/>
    <STRING lang="es" value="licenseagreement\eula_es.rtf"/>
    <STRING lang="sv" value="licenseagreement\eula_se.rtf"/>
  </ENTRY>
</DICTIONARY>
This doesn't work in 6.2, but works fine in 6.1.1

in 6.2 it works, but only if I specify a full path:

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DICTIONARY type="multilanguage" ignore="en">
  <ENTRY id="LicenseAgreement"> 
    <STRING lang="nl" value="c:\checkout\licenseagreement\eula.rtf"/> 
   ...
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,

This doesn't work because the paths of the other RTF files are relative to the main RTF file (the one for the start-up language of the dictionary).

For example, if you used English as a start-up language for your dictionary then the dictionary should look like this:

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DICTIONARY type="multilanguage" ignore="en">
  <ENTRY id="LicenseAgreement">
    <STRING lang="en" value="licenseagreement\eula.rtf"/>
    <STRING lang="nl" value="eula_nl.rtf"/>
    <STRING lang="de" value="eula_de.rtf"/>
    <STRING lang="fr" value="eula_fr.rtf"/>
    <STRING lang="it" value="eula_it.rtf"/>
    <STRING lang="pt" value="eula_pt.rtf"/>
    <STRING lang="pt_BR" value="eula_pt.rtf"/>
    <STRING lang="es" value="eula_es.rtf"/>
    <STRING lang="sv" value="eula_se.rtf"/>
  </ENTRY>
</DICTIONARY>
In this case all the RTF files and in the licenseagreement folder next to the AIP file.

Also, please note that this is a rule for both 6.1.1 and 6.2 versions of Advanced Installer. Therefore I'm not sure if you are using the same file configuration like you used before the upgrade.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
sharky-
Posts: 5
Joined: Wed Mar 12, 2008 3:17 pm

Thanks, I was probably confused with 6.0.1 and 6.1.1

Return to “Common Problems”