Skip to main content
LinkedIn
Copied!

Table of Contents

Creating a translation package

Applicable to Theme UI-Kit applications

Expand the user base of your application by translating it into different languages. By creating a translation package, you bundle all the text in your application into a single .zip file, which translators can then process more conveniently.

The system exports the majority of the text in your application to a TextToTranslate.xml file. The file does not include custom rules, such as correspondence rules and HTML fragments. For each of these rules, the system creates a separate folder with a pair of files called Translation.html and Base.html. Both files initially contain the same text, but during the localization process, the translator puts the target text into the Translation.html file.

If you use a language pack, you typically translate only application layer rulesets, which saves translation effort. For more information, see Installing Pega language packs.
  1. In the header of Dev Studio, click Configure User Interface Application readiness Localization Translate to new language .

  2. In the Select a Language list, pick a target language, and then click Add.

    You can select more than one language.
  3. If your application already has a translation, select the Re-translate existing translations? check box to overwrite the previous translation.

  4. Click Next.

  5. Select the rulesets that represent the text that you want to localize:

    Choices Actions
    Application-specific text
    1. Select the Include application layer ruleset check box.

    2. In the list of rulesets, select the rulesets that you want to include in the translation package.

    General Pega text: no language pack
    1. Select the Include all PegaRULES application rulesets check box.

    2. Select the Include Pega translation and export for custom translation check box.

    General Pega text: rewriting the language pack translation
    1. Select the Include all PegaRULES application rulesets check box.

    2. Select the Override Pega translation and export for custom translation check box.

    Text from another ruleset Select Include field value from other rulesets, and then select the source ruleset.
  6. Click Next.

  7. Click Enable records for translation.

    The wizard might display a list of errors related to ruleset dependencies and custom code. You can click on a rule to open it in a new tab and resolve the error. For custom code, such as HTML fragments, you can use the getLocalizedTextForString(String, String) method to make the code translatable.
  8. Click Next.

  9. Select whether you want to include example files in the translation package.

  10. Click Download for translation, and then click Next.

  11. Note the Work ID number for the translation, and then click Close.

    The Work ID number helps you identify the translation task when the translation package is ready.
Prepare the translation file for localization. For more information, see Preparing a translation package for a translator.
Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us