Translating a course

A translated course remains one course: the original language is the source, and each language you add is a translation of that source. When the source changes, Elabora tells you which translations need another look.

Open Translation from the course title’s menu. The toolbar has a Slide button to go back to the screens, three views (Table, In context, Versions) and the language menu.

Adding a language

Add language (or, once the course has one, Add language… in the language menu) asks Which language?: pick one from the list, or Another language… to type its code (pt-BR, uk, ko…).

Translating

Three ways, which you can mix:

• With your AI. The quickest:

  Translate the course into French, keeping the tone and the trade’s terms.

• With a translator: File for a translator, in the language menu, gives you the language’s file in XLIFF format (.xlf), which translation tools read.

• Yourself, in the Table: the course, its approved plan and each screen, the source on the left and the translation on the right, written in place. Each translation is one step ⌘Z undoes.

What the table points out

The table only highlights what asks for something:

• To review: a translation written elsewhere (by a translator or your AI). Looks good confirms it.
• Changed since: the source changed since the translation. Its old words show on hover; Keep this translation confirms it as it is.
• Overflows on screen: with this translation, the slide runs past the window. View in context takes you there.
• What breaks the text: a link, a formula or a value in braces from the source that is missing, or a text too long for its place.

To do keeps only those rows.

Reviewing in context

In context shows the screen as learners of that language will see it; choose the screen in the toolbar. Texts to review, changed or broken are outlined. A click on a text opens it beside the slide: the source, the translation to correct in place, Looks good and Keep this translation.

When a translation makes the slide overflow, Elabora says so above it and outlines the texts that grew. Shorten asks your AI for a shorter translation that keeps the meaning and tone.

Versions, translated plan and packages

Versions shows the languages side by side and where each one stands. Pick one: the right panel shows its progress, with Open table and View in context, then:

• The translated course plan: have it reviewed, then Record approval… to note who approved it and when. This approval goes into the package, and stays valid as long as the plan does not change. As for the original plan, recording it is yours to do, not your AI’s.
• The package: each language publishes as its own SCORM package, for the course’s LMS and media quality. When everything is translated and reviewed, the Build … package button (with the language’s name) builds it; meanwhile, Build a draft version: whatever is not translated yet stays in the source language. If the package is too heavy for the LMS, Elabora says so as in Publish.

Translated narration

Narration lines are translated like any other text. Each speaker can have one voice per language (Voice cast…); a line waits for its translation before getting its voice in that language. See voices and narration.

Elabora’s interface language changes nothing in your courses: an English interface can perfectly well edit a French course.