oo

Translating Content Pages

Liferay 7.4 U15+ and GA15+

Liferay provides integrated tools for translating Content Pages, so you can create engaging, localized experiences for your global users. With these tools, you can manually translate Content Page experiences or import translations as XLIFF files.

important

When translating a Content Page, users can only translate a Page’s name and inline fragment text (e.g. HTML, Header, etc.). They cannot translate Widgets or mapped fragment fields.

If desired, you can enable a custom workflow to direct the review and publishing process for translations.

note

The languages available for translation are determined by your instance’s localization settings. See Initial Instance Localization and Virtual Instance Localization for more information.

Manually Translating Content Pages

note

To manually translate Content Page experiences, users must have either View and Update permissions for Content Pages or Translation permissions for one or more languages. See Managing Translation Permissions for more information.

Follow these steps to manually translate Content Page experiences:

  1. Open the Site Menu (Site Menu), expand Site Builder, and go to Pages.

  2. Click the Actions button (Actions Button) for the Content Page you want to translate and select Translate.

    This redirects you to the translation interface, where you can view the content’s original text alongside your translation.

    The left column displays the language you’re translating from, and the right column provides editable fields you can use for your translation.

    Selecting Translate redirects you to the translation interface.

  3. Select the experience and language you want to translate.

    Users with Page Update permissions can translate the original text into any language.

    Users with translate permissions can only translate the origin text into languages for which they have permission.

    important

    Switching between Page experience discards all unsaved changes. To avoid losing work, save your changes before switching to a different experience.

    Select the experience and language you want to translate.

  4. Enter your translation for available fields.

  5. Click Publish or Save as Draft.

    Publishing your translations applies them to the Content Page and saves it as a draft.

    Also, if a workflow is enabled, publishing translations initiates the review process before they’re applied to the Page and saved as a draft.

    Alternatively, you can click Save as Draft to apply your translations at a later time.

Exporting and Importing Translations

note

To export pages for translation or import XLIFF translations, you must have View and Update permissions for the selected page. See Managing Translation Permissions for more information.

With Liferay, you can export Content Page experiences for translation as .xliff or .xlf files. You can send these files to translators and then import the translations together as a .zip file or individually as .xliff or .xlf files.

important

Liferay supports both XLIFF 1.2 and 2.0 files. However, it may not support all features and capabilities those formats provide.

Exporting Pages for Translation

Follow theses steps:

  1. Open the Site Menu (Site Menu), expand Site Builder, and go to Pages.

  2. Click the Actions button (Actions Button) for the Content Page you want to translate and select Export for Translation. This opens a modal window for configuring your export.

    Select Export for Translation.

  3. Select an export format: XLIFF 1.2 or XLIFF 2.0.

  4. Select the Content Page’s original language.

  5. Select the languages you want to translate to.

  6. Select the experiences you want to translate.

    Configure the export.

  7. Click Export.

Liferay generates a ZIP archive that contains an XLIFF file for each selected experience. You can then use these files with compatible translation software.

Importing Page Translations

Follow theses steps:

  1. Open the Site Menu (Site Menu), expand Site Builder, and go to Pages.

  2. Click the Actions button (Actions Button) for the translated Content Page and select Import Translation.

    Select Import Translation.

  3. Select the .xliff, .xlf, and .zip files you want to import.

    Select the translation files you want to import.

    important

    While Liferay supports importing XLIFF files created using the Export for Translation action, it cannot guarantee the successful import of files generated by other means.

  4. Click Publish.

    If import is successful, Liferay displays a success message with the imported files. The translations are applied to the Content Page and the Page is saved as a draft. If workflow is enabled, the translations must be approved before they’re applied to the Page.

    If import is successful, Liferay displays a success message with the imported files.

    However, if errors occur during import, Liferay notifies you of the failing files and provides a downloadable CSV error report.

    If errors occur during import, Liferay notifies you of the failing files and provides a downloadable CSV error report.

Translating Content Pages Using Third Party Services

If you’ve enabled Liferay’s integration with Google Cloud Translation, Amazon Translate, or Microsoft Translator, you can use them to automatically translate Web Content. See Using Third Parties for Translation for more information.