Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Importing translations

Updated on February 7, 2022

Create multiple language versions of your application by localizing translation packages and then importing them into your application. You can upload a newly translated package by using the localization wizard, which offers a convenient way to manage language versions of your application.

Before you begin: Obtain a .zip file containing the translated files.
  1. In the header of Dev Studio, click ConfigureUser InterfaceApplication readinessLocalizationTranslations in progress.

  2. In the Wizards in progress list, select the work item for which you want to add a translation.

  3. In the Select a RuleSet list, select the ruleset to which you want to save the translation.

    If you pick a non-localized ruleset, the wizard creates a new localized ruleset and version. If the ruleset already exists, the wizard imports the translations to the existing localized ruleset. If a ruleset version exists but is not in the list, the ruleset is locked.

    If your language pack includes standard Pega Platform field values, import the pack to a top-level (organization) application ruleset so that it can be shared across your applications.

  4. Select the ruleset versions for HTML paragraphs, correspondences, and correspondence fragments.

    The full ruleset version consists of three pairs of numbers that are separated by dashes, for example 01-01-01.
  5. Click Next.

  6. On the Open Wizard tab, click Choose File, and then navigate to the ZIP file that contains the translation.

  7. Click Next.

    Result: The system imports the translation and displays an import log.
  8. Click Finish.

  9. For translations that are included in the Translation.html files, create the rules in the localized ruleset and paste the translated text into the fields.

    For example: The TextToTranslate.xml file does not include correspondence rules. Each correspondence rule generates a separate Translation.html file. To localize a correspondence rule, you must create a separate correspondence rule for the target language, and add the translated text manually to the rule.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us