I'm using AI 7.7 build 28804
My project is configured for a web-based / online install.
I recently switched from supporting a single language (English) to supporting multiple languages, and I'm struggling with how to localize the URL for the main MSI. As mentioned in some of my other posts concerning localization, I've read all of the AI localization documentation, created a custom dictionary, etc. I've done my homework.
I am building one installer per language, so the URL for the main MSI must include some kind of language code / id / tag.
As a simple test, I created a new property "L10N_TEST". The default value is "EnglishTest". I then localized the value of that property, choosing "Always translate this string" and "Using specified localization identifier". I closed my AIP project, added a new entry to my custom dictionary, saved the dictionary, and reopened my AIP project. I checked that my custom dictionary is listed first on the "Dictionaries" tab. My custom dictionary looks like this:
Code: Select all
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DICTIONARY type="multilanguage" ignore="en">
<ENTRY id="Property.L10N_TEST">
<STRING lang="en" value="EnglishTest"/>
<STRING lang="de" value="GermanTest"/>
</ENTRY>
</DICTIONARY>
Code: Select all
[|L10N_TEST]
1) added logging to the MSI Command Line and checked the log
2) checked the value of MainAppURL directly inside the bootstrapper EXE (assuming "Include install files in EXE" option)
3) checked the value of MainAppURL inside the setup INI (assuming "Leave install files outside" option)
Just to be sure it wasn't a problem with project segments, I went to the Languages page and selected *all* project segments for translations. This added the following line to my AIP file:
Code: Select all
<ATTRIBUTE name="TranslateSegments" value="58405516501581819"/>
What I want is to generate URLs like:
Code: Select all
http://MyDownloadServer/en/MyProduct.msi
http://MyDownloadServer/de/MyProduct.msi
http://MyDownloadServer/fr/MyProduct.msi
Is there another way to achieve this? (Building a single multi-language package is not an option for me, unfortunately, as the file-size would be too large)
Thanks for any help you can provide,
Todd
FOLLOW US
Get the latest news in Application Packaging