adestis
Posts: 4
Joined: Thu Aug 28, 2008 11:02 am
Location: Nuremberg, Germany
Contact: Website

Problem with Project for Multi Language Install with Patches

First of all, I am pretty new to the Windows Installer system (and AI). So it is possible that I may use the wrong term, or I didn't gasp the idead behind the the details...

We are currently working on a project with the following requirements:
1) Multi Language Setup: the user must be able to select the installation language
2) A main program and some tools
3) Many "media" files, some databases... just a bunch of data files
4) Patches for all the above

The main program and the tools are language "neutral" (we have our own logic in the program files and database for all the supported languages).

Actually we only need to have the setup in different languages. There is no need to have different "packages" for the program or data files.

The question is, how should we organize the AI (Enterprise) project? The basic setup using multi-language MSI works, but patch creation fails (I have read the posting "thanks, now problem with patch for a multilanguage setup"). There should be an easy way to generate the patch files (msp or exe?).

The media files are somewhat large (even for a DVD as target). (Currently) We have 14 languages, so it wouldn't be a good idea to have 14 copies of the same files. Is it possible to put those "data files" in its own package? Is it still possible to generate patch files.

Sometimes we need to update the data files only, and sometimes we need to update the program files (and their DLLs) only. Maybe we need to update both of them.

How can all of this accomplished, please?
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Problem with Project for Multi Language Install with Patches

Hi,
Actually we only need to have the setup in different languages. There is no need to have different "packages" for the program or data files.
This can be done by using the Languages tab of the "Translations" page. Please note that the "Create only a multilingual package" option will make Advanced Installer create a package which contains all the selected languages. Additionally, you can make the package show a language selection dialog by using the "Display language selection dialog (for multi-language packages)" option in the Bootstrapper tab of the "Media" page.
The question is, how should we organize the AI (Enterprise) project? The basic setup using multi-language MSI works, but patch creation fails (I have read the posting "thanks, now problem with patch for a multilanguage setup"). There should be an easy way to generate the patch files (msp or exe?).
Since Windows Installer doesn't support patching for multilingual packages, the solution is to create a patch for each language. After the user installs the multilingual packages he can also install the patch which corresponds to the language he used. Please note that you can use the "Create separate packages and a multilingual package" option in order to obtain a multilingual package for distribution and a package in each language for creating patches.
We have 14 languages, so it wouldn't be a good idea to have 14 copies of the same files. Is it possible to put those "data files" in its own package? Is it still possible to generate patch files.
Please note that you don't need to have 14 copies of the same files. A patch is represented by a MSP or EXE file and it can contain the update for a language. First you can distribute the multilingual package and then distribute a patch for each language (14 patches). Since the concept of patch represents a small update and a small size, the 14 patches shouldn't have a very large size.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
adestis
Posts: 4
Joined: Thu Aug 28, 2008 11:02 am
Location: Nuremberg, Germany
Contact: Website

Re: Problem with Project for Multi Language Install with Patches

First of all, thanks for Your reply.
This can be done by using the Languages tab of the "Translations" page. Please note that the "Create only a multilingual package" option will make Advanced Installer create a package which contains all the selected languages. Additionally, you can make the package show a language selection dialog by using the "Display language selection dialog (for multi-language packages)" option in the Bootstrapper tab of the "Media" page.
I tried this, but the bootstrapper didn't show up the "language selection combobox". When I called the bootstrapper with the option "/listlangs" it displayed only one language. But directories for all the languages were generated. But I will have a look at this again.
Since Windows Installer doesn't support patching for multilingual packages, the solution is to create a patch for each language. After the user installs the multilingual packages he can also install the patch which corresponds to the language he used. Please note that you can use the "Create separate packages and a multilingual package" option in order to obtain a multilingual package for distribution and a package in each language for creating patches.
Do we have to generate 14 different patch files, or is it possible to generate just one patch file?

I tried the "separate packages" and put each of them into the patch project. The generated patch was very small, but, as noted above, I didn't get the bootstrapped language selection dialog.
The question is, how should we organize the AI (Enterprise) project? The basic setup using multi-language MSI works, but patch creation fails (I have read the posting "thanks, now problem with patch for a multilanguage setup"). There should be an easy way to generate the patch files (msp or exe?).
Please note that you don't need to have 14 copies of the same files. A patch is represented by a MSP or EXE file and it can contain the update for a language. First you can distribute the multilingual package and then distribute a patch for each language (14 patches). Since the concept of patch represents a small update and a small size, the 14 patches shouldn't have a very large size.
The problem with the 14 copies is not the patch itself, but the initial setup. In one of my first shots there were 14 directories with 1 GB data in each folder. When I switched to "only a multilangual package", we just had a single 1 GB file.


I will try to build a small test project, with your hints and for another try...
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Problem with Project for Multi Language Install with Patches

Hi,
I tried this, but the bootstrapper didn't show up the "language selection combobox".
Please note that this combo box is shown only if your package contains multiple languages. The languages in the package are set in the "Languages" tab of the "Translations" page. If the problem persists please send us the AIP file you are using to support at advancedinstaller dot com so we can investigate it.
Do we have to generate 14 different patch files, or is it possible to generate just one patch file?
Since you need a patch for each language, I'm afraid that you need to generate 14 different patch files. This is necessary because Windows Installer doesn't support creating a patch for a multilingual package.
The generated patch was very small, but, as noted above, I didn't get the bootstrapped language selection dialog.
Please note that a patch can be created only for one language (for example, a patch for English, another one for French etc.). Since there is only one language in the patch there is no need to show a language selection dialog.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
adestis
Posts: 4
Joined: Thu Aug 28, 2008 11:02 am
Location: Nuremberg, Germany
Contact: Website

Re: Problem with Project for Multi Language Install with Patches

It looks like I got it working... But, I am not sure if it is the "correct way".

I am using a "Create separate packages and a multilingual package". After the build process is complete, I only use the output in the "all" sub-folder for the DVD or as setup for the user (In previous tests I only used to top level bootstrapper).

For the patch project I added all "matching MSIs" as families in the "Images" section, including the "all" MSIs. Each language is a family entry.

I haven't tested all languages, yet, but the resulting MSP works with an installation language that is different to the projects "main/default" language (project uses en-US, setups tested were German, and French).

I just hope I don't use an unsupported feature/bug, when I create a MSP this way...
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Problem with Project for Multi Language Install with Patches

Hi,
I just hope I don't use an unsupported feature/bug, when I create a MSP this way...
Since this approach works, then there should be no problem. Each family should be treated like an update for each language, therefore it should work as expected.

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

Return to “Common Problems”