This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Can't make the license agreement locale
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 03, 2009
07:36 AM
Can't make the license agreement locale
Hi all,
I'm trying to make a multi language installer, and the license agreement file is different for each locale.
I have tryed editing the locale file and changing the license agreement file name, but the installer says it can't find the file.
Also, I try to change the label of a panel, but it allways goes back to "Get User Input". The funny thing is that in English it says a different thing, but in the second locale, it won't change.
Thanks for the help
Alberto E.
I'm trying to make a multi language installer, and the license agreement file is different for each locale.
I have tryed editing the locale file and changing the license agreement file name, but the installer says it can't find the file.
Also, I try to change the label of a panel, but it allways goes back to "Get User Input". The funny thing is that in English it says a different thing, but in the second locale, it won't change.
Thanks for the help
Alberto E.
(11) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 03, 2009
08:54 AM
Quoting from the manual (localization section) (it's from an older manual, you should check your manual, maybe it got updated):
Localizing Resources
InstallAnywhere 8.0
The developer may find that they want to localize resources (such as License Agreements, side panels, billboards, and custom icons) for specific countries. This is possible in InstallAnywhere. Actions such as the License Agreement Panel and LaunchAnywhere serialize the paths and filenames to their resources as well as their dynamic strings to the locale files. The developer can then change these paths and the filenames. For example, to localize the License Agreement:
Make sure to include every resource in the Install task. Installers will not have access to resources not specified in this task.
Find the line in the locale file that contains the text LicenseAgr.#.FileName. Specify the filename of the file that contains the localized license agreement (for instance, License_fr.html). Do not type the fully qualified absolute pathname to the file—just the filename itself.
Find the line that contains the text LicenseAgr.#.Path. Specify the path name to the file that contains the localized license agreement (on the local filesystem).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 06, 2009
03:34 AM
Thanks pv7721,
That's what I'm doing, I change the file name in the locales file, but when I try the installer, it says "Unable to locate the selected file." instead of showing my locale license file.
The file I'm using it's in the Install task, and the path is the same as the other license agreement (the english one) but I can only see the english license agreement, not the locale.
That's what I'm doing, I change the file name in the locales file, but when I try the installer, it says "Unable to locate the selected file." instead of showing my locale license file.
The file I'm using it's in the Install task, and the path is the same as the other license agreement (the english one) but I can only see the english license agreement, not the locale.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 06, 2009
02:46 PM
Would it be possible for you to post your project or at least a sample project that reproduces your issue?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 07, 2009
03:34 AM
Thanks for helping pv7721,
I have attached a zip file containing a sample project that reproduces my problem.
There are two sample license files, one in english and the other one in spanish. I set the default license file with the english file, and then in the locales file, I change it for the spanish locale. Both files are in the install action, so both are going to be installed in the client.
By the way, there is a "Get User Input" panel, and I've changed the panel's label, but it only works in english. In the spanish locale it allways says "Get User Input".
Thanks a lot for everything
Alberto E.
I have attached a zip file containing a sample project that reproduces my problem.
There are two sample license files, one in english and the other one in spanish. I set the default license file with the english file, and then in the locales file, I change it for the spanish locale. Both files are in the install action, so both are going to be installed in the client.
By the way, there is a "Get User Input" panel, and I've changed the panel's label, but it only works in english. In the spanish locale it allways says "Get User Input".
Thanks a lot for everything
Alberto E.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 20, 2009
11:17 AM
No one has any other idea?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 21, 2009
08:42 AM
Hey something similar issue.
For all the locale related strings, i am using the Project->Locales->Resource Bundle.Which basically uses a properties file for locale messages.
How this resource bundle can be used for license agreement.?
For all the locale related strings, i am using the Project->Locales->Resource Bundle.Which basically uses a properties file for locale messages.
How this resource bundle can be used for license agreement.?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 22, 2009
02:50 AM
I finally found a solution. I placed both license agreement files in the project directory, named licence_en.txt and licence_es.txt.
I added both of them in the install task, and set the destination to the magic folder "Do not install".
I set the english version as the default license agreement file in the license agreement panel.
Last, I changed the locale_es file, and changed the filename from licence_en to licence_es.
I built my project, and voila!, it works now.
qqqqqq, if you want to try like this, maybe some of this may help you, good luck!
Thanks to everybody that spent some time reading this.
Alberto E.
I added both of them in the install task, and set the destination to the magic folder "Do not install".
I set the english version as the default license agreement file in the license agreement panel.
Last, I changed the locale_es file, and changed the filename from licence_en to licence_es.
I built my project, and voila!, it works now.
qqqqqq, if you want to try like this, maybe some of this may help you, good luck!
Thanks to everybody that spent some time reading this.
Alberto E.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 28, 2009
12:34 AM
even resource bundle thing seems to work..
just for license agreement panel path to the file would be something like..->
$L{mylocale.licensePath}
and in your locale files add a property like
english locale file: licensePath=C:\\license_en.txt
french locale file: licensePath=C:\\license_fr.txt
🙂
just for license agreement panel path to the file would be something like..->
$L{mylocale.licensePath}
and in your locale files add a property like
english locale file: licensePath=C:\\license_en.txt
french locale file: licensePath=C:\\license_fr.txt
🙂
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 14, 2009
03:17 PM
In the Project phase under Locale task check all the languages from Locale List that you would like to support.
In the pre-Install Phase chose the License Agreement file from 'path' option.
In the Install Phase add other files that you would like to be added as external resources (License Agreement files), make sure that the destination of these files is chosen as $DO_NOT_INSTALL$ folder.
Before Building In the Installer project directory, under corresponding Locale directory you will find the list of custom_ files. For each of this file, find a line LicenseAgrAction..resourceName=
put the name of the file added as external resource in the Install Phase , that represents the License Agreement of this
In the pre-Install Phase chose the License Agreement file from 'path' option.
In the Install Phase add other files that you would like to be added as external resources (License Agreement files), make sure that the destination of these files is chosen as $DO_NOT_INSTALL$ folder.
Before Building In the Installer project directory, under corresponding Locale directory you will find the list of custom_
put the name of the file added as external resource in the Install Phase , that represents the License Agreement of this
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 03, 2009
03:49 AM
Before Building In the Installer project directory, under corresponding Locale directory you will find the list of custom_ files. For each of this file, find a line LicenseAgrAction..resourceName=
put the name of the file added as external resource in the Install Phase , that represents the License Agreement of this
Hi,
This one seems i cant follow..can you please tell more about this one what will i do with the LicenseAgrAction line?:confused:
TIA
put the name of the file added as external resource in the Install Phase , that represents the License Agreement of this
Hi,
This one seems i cant follow..can you please tell more about this one what will i do with the LicenseAgrAction line?:confused:
TIA
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 03, 2009
09:12 PM
I got it, i need to build first so i can get the custom locale file.then add it to the licenseAgrAction line...
Thanks.
Thanks.
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)