topper_harley
Posts: 24
Joined: Fri Aug 24, 2007 1:13 pm

Non-Latin shortcuts (cyrillic, greek,etc.)

Hi!

I'm having a problem creating shortcuts with non-latin characters, such as cyrillic, greek and most eastern-europe languages. Also in the AIP all the strings als displayed properly, the installed shortcut's names are nothing but boxes.

(Dev-machine and target machine both are German Win XP Pro SP 2, all codepages installed).

Try a project, using country names for your shortcuts (Российская Федерация, Ελληνική Δημοκρατία oder Česká republika (not the v over the C in "Česká"). It will all end in something like "" or "Ceská republika" (without the v on the C).

How to solve this?
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,

Please note the Windows Installer can handle only a single codepage during an installation (the codepage of the language in which the installation is performed).

Therefore, you cannot use strings from the Greek codepage (for example) in an installation performed in German. This is because the characters you use must belong to the codepage of the package language.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
topper_harley
Posts: 24
Joined: Fri Aug 24, 2007 1:13 pm

Oh, that is a big problem...
Is this a limitation of certain Windows Installer versions?

My company's policy says that there's only one installation UI (in english) for all localized installations.
That has the benefit that I need to manage just one AIP, while the shortcuts were merged using an AIC file (formatted as unicode litte endian, btw).

I know that I can have multiple localizations in just one AIP, but I have not found out how to localize shortcut names.
For my company's policy, the installation UI must not be another languange than english. I would need to replace the build-in translations by an english one, wouldn't I?

Another thing is that with the setting "Create separate packages", AI always builds packages for all translations, even if I need just a certain one. Or did that change in 6.1?

FYI: My company deploys highly personalized software, so for each customer a new MSI file is build (using the same AIP, but with different files included).
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,

This is not a Windows Installer limitation, it is actually the way it has been designed. Because the MSI packages also need to run on Windows 9x systems (which do not support Unicode), an ANSI codepage is used for all the strings in the MSI package (the codepage corresponding to the package language).

This means that if you create an English MSI, you can use only characters from the English codepage (1252).

The only way to localize elements in the installation package is to create a separate package for each language or a multi-language package (a multi-language package will select the language automatically based on the system locale).
Another thing is that with the setting "Create separate packages", AI always builds packages for all translations, even if I need just a certain one. Or did that change in 6.1?
Please note that the "Create separate packages" option creates a specific MSI package for each language selected in the "Translations" page. If you need only one package for multiple languages then you can use the "Create only a multilingual package" option.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
topper_harley
Posts: 24
Joined: Fri Aug 24, 2007 1:13 pm

I understand that.

So in the "Translations" dialog, I check all the languages I need and select the "Create separate packages" option.
When I now build the project, a lot of MSI packages is build, one for each language. That's what I do not want. I need just a certain localized package (and NO multilanguage package).
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,
I need just a certain localized package (and NO multilanguage package).
In order to generate a single localized package you need to choose the base language of the package when you create the Advanced Installer project (use the "Language" combo in the "New Project" dialog). Note that this project must use only the base language in order to generate only one package.

Also, you can simply use the package generated with the other packages when you use the "Create separate packages" option. .

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
topper_harley
Posts: 24
Joined: Fri Aug 24, 2007 1:13 pm

I do not want to create a sepatare project for each localization.

One projekt with all the localizations wohld be fine. But when I build the package, I don't want AI to build all localized packages, but just a certain one.

As I said, my company deploys personalized software. So when a customer orders a copy, we personalize the application executable and the database. So for each customer a new MSI package has to be build, also the AI project remains unchanged.
To make it easily scaleable, I do not wat to have a set of localized AI projects, but just a single one.

When a copy is to be deployed, I replace the exec and the db in the setup-project-files-folder by the customized ones and build the MSI package. Thats the point where I neet to tell AI, not to build all localized MSIs, but the one the customer needs.

Hope, you understand my problem...
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,

There are two solutions for this:
1) build all the packages (for the languages you use) and give your client the one he needs

2) go to the "Translations" page and select only the language in which you want to build the package; note that the project language cannot be deselected

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
topper_harley
Posts: 24
Joined: Fri Aug 24, 2007 1:13 pm

topper_harley wrote:I don't want AI to build all localized packages, but just a certain one.
cosmin wrote:1) build all the packages (for the languages you use) and give your client the one he needs
D'oh!
I think I am to find a solution for that by myself...

BTW: I build the package using a command line with a configuration file (AIC), so I can not "go to the Translations page"...
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,

Please note that this cannot be done the way you need because Advanced Installer cannot generate just one package for the selected language.

This is because it automatically generates a package for the language of the project (the one set when creating the project). If you need a package in another language (other than the one used by the project), you must build two packages: one in the language of the project, and one in the selected language.

Also, what you want can be done through the command line only by building all the packages and selecting the one you need (for example the one in the "de" folder for the German language).

We already have on our TODO list a feature which will allow you to build a package just for the selected language and this feature will be available in a future version of Advanced Installer.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
topper_harley
Posts: 24
Joined: Fri Aug 24, 2007 1:13 pm

cosmin wrote:We already have on our TODO list a feature which will allow you to build a package just for the selected language and this feature will be available in a future version of Advanced Installer.
That sounds great! :-)
So I'll wait patiently for that release.

Finally, there remains one problem: When I add all the localizations to the project, AI automatically adds the build-in dictionaries. So a russian setup has a russian interface - what is great for most people but not me. The setup interface must be english regardless of the setup's language.
I cannot get the already translated strings replaced by a custom dictionary file.

What codepage is used, when the project language is "neutral"? Win1252, isn't it?
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,
The setup interface must be english regardless of the setup's language.
I'm not sure why you need this. If you need the interface in English then why are you building the package in another language?
What codepage is used, when the project language is "neutral"? Win1252, isn't it?
Please note that an Advanced Installer project cannot have the "neutral" language. This is possible only for merge modules.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
topper_harley
Posts: 24
Joined: Fri Aug 24, 2007 1:13 pm

cosmin wrote:I'm not sure why you need this. If you need the interface in English then why are you building the package in another language?
That wasn't my idea, it's my company's policy. I've been said: all the technical stuff (what menas the setup, too) is in english. What the user (not the administrator) sees (what means the shortcuts), is in the user's language.
cosmin wrote:Please note that an Advanced Installer project cannot have the "neutral" language. This is possible only for merge modules.
Excuse me, but when I click "File | New" and set the "New Project type" as an "Enterprise" project I can select Language: "Language Neutral" (AI v6.0.1).
What am I doing wrong?
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,
I've been said: all the technical stuff (what menas the setup, too) is in english. What the user (not the administrator) sees (what means the shortcuts), is in the user's language.
You can try to modify the dictionary used by the languages of your package to use English strings. However, please note that the codepage of the installation package may not support all the English characters you use.

You can find the dictionaries used by Advanced Installer in the "dictionaries" directory in it's installation folder.
Excuse me, but when I click "File | New" and set the "New Project type" as an "Enterprise" project I can select Language: "Language Neutral" (AI v6.0.1).
I cannot reproduce this behavior on my test machine. Perhaps you are using a corrupted version of Advanced Installer (you can try to reinstall it). Note that the "Language Neutral" option can be used only for merge modules.

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

Return to “Common Problems”