# Translate pages with XLIFF, Phrase, Lokalise or Smartling

> Download a page or a folder as an XLIFF file for your translators, or send it to your translation service, and bring the translation back as a draft.

Source: https://docs.bifrostorbit.com/cms/editors/translate-with-xliff/

When your translators work in their own tool, you don't need to copy text by hand. CMS Orbit hands them the text of a page, or of every page in a folder, as an XLIFF file, and fills in the pages in the other language when the translation comes back. Translations always arrive as drafts, so nothing goes live until someone has reviewed and published it.

This needs CMS Orbit Growth or higher. The other language has to be a language of the same region, such as Norwegian next to English in Europe.

## What gets translated

- Text, long text and rich text fields, on the page and inside its blocks
- The SEO title and description

Pictures, links, prices, choices and other fields stay as they are in the other language. Rich text keeps its formatting: the tags travel with the text, so ask your translators to leave them in place. Anything unsafe in returned rich text is removed, as when you paste.

## Translate with a file

1. Open **Pages**, then open the menu (**…**) of a page or a folder and choose **Translate**.
2. Under **Translate into**, choose the language, such as Norsk (nb-NO).
3. Choose **Download XLIFF** and give the file to your translators. A folder gives one file with all its pages, including those in its subfolders, up to 200 pages.
4. When the translated file comes back, open **Translate** again, choose the same language and **Upload translated XLIFF**.

Each page in the other language now has a draft with the translation. If a page didn't exist there yet, CMS Orbit makes it first, as **Copy to** does. Open the pages in that language to review and publish them.

XLIFF 2.0 works with every common translation tool. Files in XLIFF 1.2 are read too.

## Send to your translation service

When an owner or admin has connected Phrase, Lokalise or Smartling in Orbit under **Connections**, the **Translate** window also shows the service.

1. Choose the language and **Send to Phrase** (or Lokalise or Smartling). CMS Orbit uploads the text and starts a job for that language in your project.
2. The job appears in the list with its status. Choose the refresh button to check it.
3. When it says **Translated**, choose **Get translations**. The pages in the other language get a draft with the translation.

You can get translations before a job has finished; texts that aren't translated yet are left as they are. Getting them again later updates the drafts.

The language has to exist in the project at your translation service. CMS Orbit matches languages by their code, such as nb-NO, or by the language alone when the project has only one version of it, such as nb.

## When a page isn't changed

- **It changed at the same time, or the text doesn't fit:** a page that changed while the translation came in, or whose translated text breaks a field's rules (such as its length), keeps its draft. The message names these pages, so you can import again or shorten the text.
- **Nothing matched:** a block that was removed or moved in the other language, or a text that's empty in the file, keeps what it had.
- **Wrong language:** a file translated from or into another language is refused, so it can't overwrite the wrong pages.

## Who can do this

Translating needs permission to edit pages in the other language. Sending to a translation service is recorded in the audit trail, as is every import.
