Skip to main content

Translate an experience

Translate every field in an experience side by side, track what's still missing, and hand work to an external translator with XLIFF.

Written by Cody Iddings

The Translation page is where you translate an experience. When your organization has multi-language and the experience has more than one language, Translation appears in the experience's sidebar, with Content, Email and Settings. The experience's sidebar starts folded to icons and stays the way you leave it: hover an icon to see its name, or click the logo or drag its edge to open it.

The experience's sidebar with Translation highlighted below Content and Email

It has two views: Content for text, and Media for files. Media is covered in Use media in other languages.

The Content view

Every translatable field in the experience appears as a row, grouped by section and activity, with one column per language. The English column is read-only — that's your source. Every other column can be edited directly.

To translate a field, click its cell and type. An untranslated cell is empty and shows the English text faintly behind it. That way you can tell "not translated yet" apart from "translated to the same words".

The Content view of the Translation page: field rows grouped by section, with English and other language columns

Read the badges

Each cell can show one badge, in its corner:

Three translation cells showing the amber globe, amber warning and gray pencil badges in their top right corners
  • Amber globe — untranslated. This cell is falling back to English.

  • Amber warning — out of sync. The English text has changed since this was translated, so the translation is probably out of date.

  • Gray pencil — custom. Someone edited this by hand, so auto-translate will leave it alone.

If your organization has auto-translate, the badges become buttons. Click an amber badge to translate that single field. To discard hand-written text and translate the field again from English, click its gray pencil. See Auto-translate your content.

Find what's left

These controls help you find the work that's left:

  • Only untranslated, next to Show:, hides every row that's already done, so you're left with the work.

  • Only custom narrows to the fields someone has hand-edited. It's there if your organization has auto-translate.

  • Show or hide language columns, in the English column header, hides languages you're not working on. It's useful when an experience has more than two or three.

  • Collapse all, next to the Field header, collapses every section and activity at once. Click it again to expand them.

The Translation page toolbar with Only untranslated and Only custom switches, Auto-translate and XLIFF

Emails

After the content rows, the Emails section covers your post-experience email sequence. Subject lines are editable in place; bodies are shown read-only and are edited under Email in the experience's sidebar. See Translate post-experience emails.

The Emails section of the Translation page, with a Subject line row and a read-only Body row

Use an external translator

If a translation agency or a colleague is doing the work outside Makeshapes, use XLIFF — a standard file format that translation tools understand.

  1. Click XLIFF > Export .xlf, and then choose a language.

    The XLIFF menu open on the Translation page, with Export .xlf and Import .xlf, and a list of languages
  2. Send the downloaded file to your translator.

  3. When the file comes back, click XLIFF > Import .xlf, and then choose the same language.

  4. In the file picker that opens, select the translated file.

You'll get a summary of how many translations were applied. Anything the translator changed is marked as custom, so a later auto-translate run won't overwrite their work.

An XLIFF file carries text only — content fields plus email subjects and bodies. Media isn't included; language versions of files are added separately.

Edit in another language outside this page

The Translation page is built for bulk work. You can also work in one language and see the experience as you build it. To do that, switch your editing language with the Editing language menu (a globe and the current language's name) on the Content, Email or Settings page. Those pages then show and save that language.

The Editing language menu open on the Content page, listing the experience's languages with one selected
Did this answer your question?