How to Translate an E-learning Course into Multiple Languages
7 min read Czytaj po polsku
Translating a course looks like a text job: export the words, send them to a translator, put them back. Then the German version overflows its buttons, the Polish quiz rejects correct answers typed without diacritics, the screenshots still show English software, and the LMS lists the course under its English title. This guide covers what to translate, how to prepare, how to review, and how to package several languages for an LMS.
What needs translating, including what people forget
| Element | Where it hides | Often forgotten? |
|---|---|---|
| Slide text and headings | Every slide | No |
| Answer options and quiz feedback | Question settings, per option | Yes |
| Accepted answers in fill-in questions | Question settings | Yes |
| Labels in matching, ordering and sorting exercises | Exercise settings | Sometimes |
| Scenario choices and endings | Branching scenario | Sometimes |
| Alt text of images | Image properties | Yes |
| Captions, transcripts, narration | Audio and video blocks | No, but costly |
| Text inside images and screenshots | The image files | Yes |
| Player interface: Next, Submit, Try again, Completed | The course player | Yes |
| Certificate text | Certificate block or template | Yes |
| Course title in the LMS | <title> in imsmanifest.xml, LMS catalogue |
Yes |
| Numbers, dates, currency, units | Throughout | Yes |
| Legal references, contacts, links | Policy slides, summary | Yes |
Two items deserve a closer look.
Fill-in answers. If the English question accepts "password manager", the Polish version must accept "menedżer haseł" and decide about "menadżer haseł" (a common spelling) and "menedzer hasel" (typed without diacritics). Decide per language whether case and diacritics matter, and list the variants.
Localized content, not only translated content. A GDPR course in Polish refers to RODO and the Polish supervisory authority, UODO. A course about reporting incidents needs the local helpdesk number. Examples with names, currencies and situations should feel local. This is adaptation, and the subject-matter expert in each country has to own it.
Prepare before anyone translates
Translation goes faster and cheaper when the source is final and the decisions are written down.
- Freeze the source. Every change after translation starts has to be made in every language.
- A glossary of the 20–50 terms that must always be translated the same way.
- A do-not-translate list: product names, system names, the company name.
- A style guide per language: formal or informal address, gender-neutral phrasing, number and date formats.
- Context for the translator: screenshots or a preview link, so "Submit" isn't translated as "surrender".
A glossary can be a simple table:
| English | Polish | German | Note |
|---|---|---|---|
| data breach | naruszenie ochrony danych osobowych | Datenschutzverletzung | Legal term, don't paraphrase |
| learner | kursant | Teilnehmer | |
| report (verb) | zgłosić | melden | In the sense of reporting an incident |
| Acme Cloud | Acme Cloud | Acme Cloud | Product name, don't translate |
On address: German courses must choose between "Sie" and "du", French between "vous" and "tu". Polish adds a twist: past-tense verbs carry gender, so "You answered correctly" can't be translated without choosing one. Write feedback in neutral forms instead, such as "Poprawna odpowiedź" ("Correct answer") rather than "Odpowiedziałeś poprawnie" ("You [masc.] answered correctly").
Audio, video and captions
Narration is the most expensive part of a translation, so decide early whether each language gets recorded audio, synthetic speech or captions only. Re-recorded narration rarely has the same length as the original, so anything timed to the audio, such as animations or slide advances, needs checking. Keep captions as separate text files (WebVTT .vtt is the web standard, SRT is common too) rather than burned into the video: a text file can be translated and corrected, pixels can't. And when a screenshot shows software, take a new one in the localized version of that software instead of translating labels on top of the old image.
Plan for longer text
Text usually grows in translation from English. As a working budget, assume around a third more space for languages such as German or Polish, and more for short strings: a four-letter button label can easily double. Fixed-size boxes, buttons and hotspot labels are where it breaks.
- Design the source layout with spare room, especially on buttons and flip cards.
- Review the longest language first. If it fits, the others usually do.
- Avoid text in images. Every image with text is one more file to recreate per language.
Translate with AI, review with people
A good workflow mixes both:
- Machine or AI draft, with the glossary and the do-not-translate list applied, in a tool that keeps the course structure, so translated text goes back into the same slides, questions and feedback fields.
- Linguistic and subject review by a bilingual expert who knows the subject. They check terminology, legal references, tone and the correctness of every answer.
- In-context review in the running course, not in a spreadsheet: overflowing text, awkward line breaks, images that still contain English, feedback that no longer matches its question.
- LMS test per language: complete, fail, resume, and read the report.
AI drafts are reliable for plain explanatory text and much weaker on legal terms, product terminology without a glossary, and humour. Give reviewers the time the review deserves; a mistranslated rule in a compliance course is worse than no translation.
One multi-language package or one package per language
This decision changes how the LMS handles the course, so make it before you translate.
| One multi-language package | One package per language | |
|---|---|---|
| LMS activities | One | One per language |
| Reports | One report across languages | Per language; combine for totals |
| How the language is chosen | In the course, or from the LMS preference | By which activity the learner is enrolled in |
| Updates | One upload; all languages must be updated together | Each separately, so versions can drift apart |
| Package size | Larger | Smaller |
| Best for | Mixed-language teams, one policy across countries | Different content or deadlines per country |
Whichever you choose, keep interaction IDs identical across languages. If question 3 is q3-sender in every language, and answer options use IDs like a, b, c rather than their text, the LMS's interaction reports can be compared and combined across languages. Fill-in answers are the exception: they're stored as the learner typed them.
Reading the learner's language from the LMS
SCORM has a field for the learner's preferred language: cmi.student_preference.language in SCORM 1.2 and cmi.learner_preference.language in SCORM 2004. A course can read it at launch:
// SCORM 2004
var pref = api.GetValue("cmi.learner_preference.language"); // "", "pl", "pl-PL", "en-GB"…
var lang = (pref || "").toLowerCase().slice(0, 2);
if (available.indexOf(lang) === -1) {
showLanguagePicker(); // no preference, or a language the course doesn't have
}
In practice, many LMSs leave the field empty, and in SCORM 1.2 it's free text, so treat it as a hint. Always let the learner choose and change the language, and remember the choice in the course's saved state so they aren't asked again.
Test each language before release
- Every slide reviewed in the running course, in the longest language first
- Quiz feedback and fill-in answers checked in each language
- No English left in images, captions, the player or the certificate
- Course title in the LMS translated, or bilingual for a multi-language package
- Same pass mark and same question IDs in every language
- One full LMS test per language: complete, fail, resume, report
Translating courses in Scormbee
Scormbee's AI translation creates a translated copy of the course as a linked project. Text fields are translated, including slides, questions, answers, feedback and image descriptions, while the layout, question IDs, correct answers, images, theme and settings stay the same, so reports line up across languages. You can pick several of 25 languages at once, and list names and terms that must stay as written (your company, products, standards). When the original changes later, translating again updates the existing language versions and sends only the texts that changed, so you pay only for those. It costs 1 credit per started 4,000 characters, shown before you start. The player's own buttons and messages follow the course language, and when the LMS passes the learner's preferred language, a multi-language package opens in it. Language versions can then go into one multi-language package: learners pick the language on first launch and can switch it in the top bar, and the LMS sees a single course. The course translation page shows an example. The review steps above still apply, because a translation tool keeps the structure but can't know your glossary unless you check it.
Frequently asked questions
Should I make one multi-language SCORM package or one per language?
One package when the same course goes to a mixed-language audience and you want a single report. One package per language when countries need different content, different deadlines or separate reports. Either way, keep question IDs identical across languages.
Can the course start in the learner's language automatically?
It can read the learner's language preference from the LMS: cmi.student_preference.language in SCORM 1.2 or cmi.learner_preference.language in SCORM 2004. Many LMSs leave it empty, so always offer a language choice as well.
Is AI translation good enough for e-learning?
As a first draft, often yes, especially when the tool keeps the course structure and you give it a glossary. It still needs a review by a bilingual subject-matter expert, because terminology, legal references and tone are where machine translation goes wrong.
How much longer does translated text get?
It depends on the language pair. Plan for noticeably longer text from English into languages such as German or Polish, around a third more as a working budget, and expect short labels and buttons to grow the most.
Do I need to translate the quiz feedback?
Yes. Feedback is where the course explains why an answer is right or wrong. Untranslated feedback is the most common gap in translated courses, together with alt text and fill-in answers.