Community Forums
Results 1 to 3 of 3

Thread: Localization problem after migrating from InstallAnywhere2009 to InstallAnywhere2012

  1. #1
    Join Date
    Dec 2011
    Posts
    13

    Localization problem after migrating from InstallAnywhere2009 to InstallAnywhere2012

    Hi,
    Recently we have migrated our project from InstallAnywhere2009 to InstallAnywhere2012.
    As part of our script(not install anywhere), we merge and generate custom_xx(xx is language like en,es,de,jp etc), which should be used by InstallAnywhere project.

    As per the new InstallAnywhere2012, it expects custom_xx files to be in <project>locales_Migrated_Configuration (as default configuration name is Migrated Configuration).

    But we have seen a behavior during building the installer project.
    Just before calling build.exe, custom_xx(under <project>locales_Migrated_Configuration) contains our localized strings which is generated from external .properties files.
    During build process, installanywhere2012 generates custom_xx with default strings, which overwrites our localized strings.

    You may notice, during build process it saves the project and generates external properties(custom_xx). Can we skip this somehow?

    User guide does not say anything about it.

    Is there any solution to following threads:
    http://community.flexerasoftware.com...t=localization
    http://community.flexerasoftware.com...t=localization


    Kindly provide proper documentations for migration from InstallAnywhere2009(project is having external resource bundles)?

  2. #2
    Join Date
    Dec 2011
    Posts
    13

    Thumbs up

    As localized strings present in InstallAnywhere project(xml_iap) is referred by installAnywhere during build.
    We changed our implementation and added new strings into xml_iap.
    Now it works fine.
    So the only source of localized string is the xml_iap project file.

  3. #3
    Join Date
    Nov 2013
    Posts
    7

    Smile Kindly please tell me the process how you can localized custom action messages

    Quote Originally Posted by bidyapatip View Post
    As localized strings present in InstallAnywhere project(xml_iap) is referred by installAnywhere during build.
    We changed our implementation and added new strings into xml_iap.
    Now it works fine.
    So the only source of localized string is the xml_iap project file.
    Hi bidyapatip,

    Kindly please tell me the process how you can localize custom action messages as we are also facing same issue in our project.

    Thanks in advance,
    Lakshmi

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •