Hello
I got some trouble if I translate the component selection to German.
In my compopnent tree I want to show "Druckertreiber" not the english word "Printer driver"
But if I do this with the translation tool , later in the setup and in German language the selection is not recognized
So which of these strings can I translate that it still works?
SetComonentSelectionCommand
GetComponentSelectionCommands
DefineComponentCommands
can you helpme?
thanks a lot
kind regards
Hans
Component Commands Translation
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Component Commands Translation
Dear User,
of course "Define Component" Command.
Regards
of course "Define Component" Command.
Regards
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Component Commands Translation
Dear Hans,
Assuming that this can be helpful to other user as well, I have realized a sample project that uses features in a localized scenario.
To have localized features correctly handled it is just required to assign the name parameter of "Define Component" command, to a previously defined Localized Variable with the script.
In the same way each time you want to verify a component selection state with "Get Component State" command, you should refer to a particular feature name using a defined Localized variable.
The Localized Variables used with the attached sample have been translated to English, French and German (I just appended the language name identifier to each variable value), using the InstallAware Translation Wizard Tool.
That's it ... and no other additional steps are required to have localized features to work correctly.
Hope this helps you and many other.
Regards
Assuming that this can be helpful to other user as well, I have realized a sample project that uses features in a localized scenario.
To have localized features correctly handled it is just required to assign the name parameter of "Define Component" command, to a previously defined Localized Variable with the script.
In the same way each time you want to verify a component selection state with "Get Component State" command, you should refer to a particular feature name using a defined Localized variable.
The Localized Variables used with the attached sample have been translated to English, French and German (I just appended the language name identifier to each variable value), using the InstallAware Translation Wizard Tool.
That's it ... and no other additional steps are required to have localized features to work correctly.
Hope this helps you and many other.
Regards
- Attachments
-
- Localized Features.rar
- (2.19 MiB) Downloaded 324 times
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
Who is online
Users browsing this forum: No registered users and 101 guests