E-Learning Translation: How to Localize Courses Right
E-learning translation means converting a course’s on-screen text, narration, video, subtitles, assessments and interface strings into another language, then rebuilding and testing the course so it works for the learner. The translation is the easy part to describe. The hard part is everything around it: file formats, text that grows past its text box, audio that no longer matches the slides, and quiz logic that breaks. This guide covers what to translate, when to localize instead, how to prepare your files, what changes for Hungarian, and how to test the result.
TL;DR
Translate when the content is procedural or technical and learners share a cultural context. Localize when the course spans countries or relies on tone, examples and scenarios.
Plan for translation while you build the course: clean source text, a glossary, editable layers and room in the layout.
Translate everything the learner meets: slides, narration, captions, images with text, quizzes, feedback messages, downloads and the player’s own buttons.
Hungarian is an agglutinative language with long words and case endings, so test every text box, button and quiz option in the finished course.
Always review in the real course, not only in a spreadsheet. Language quality, function and usability are three separate checks.
Table of Contents
Translation or localization: which one does your course need?
Translation carries meaning from one language to another. Localization goes further and adapts the whole learning experience, including tone, cultural references, imagery and examples, to the expectations of a specific audience. Articulate describes localization this way, and it matches what we see in practice.
A simple rule of thumb comes from Adobe’s e-learning team: choose translation when learners share a similar cultural context or the content is highly technical or procedural. Choose localization when training spans several countries or cultural relevance matters, especially in customer service, marketing, leadership and ethics.
Here is how that plays out:
Course type | Usual approach | Why |
Machine operation, equipment maintenance | Translation | Steps and part names are the same wherever the machine runs |
Software walkthrough | Translation plus interface check | Screens must match the localized product |
Compliance and safety procedures | Translation, with local rules checked | Law and terminology differ by country |
Sales, service or leadership training | Localization | Scenarios, names, humor and etiquette must feel local |
Onboarding for a global workforce | Localization | Company culture is conveyed through tone and examples |
Most real courses are a mix. A compliance course can have strictly translated procedures and a localized scenario section. Decide per module, not per course.
When the law pushes you to translate
For US employers, language can be a compliance matter. OSHA’s policy statement says training required by its standards must be presented in a manner employees can understand, using language and vocabulary they understand. If an employee does not speak or comprehend English, instruction has to be in a language that employee can understand. If you have a Hungarian-speaking workforce, whether in a US plant or at a Hungarian subsidiary, a translated safety course is part of doing the training properly. Confirm how this applies to your standards with your safety or legal team.
What actually needs translating in an e-learning course
The visible slide text is usually less than half of what a learner encounters. A complete scope list looks like this:
On-screen text: titles, body copy, callouts, tooltips, button labels, menu and navigation.
Narration and voice-over: scripts, plus re-recording or synthetic voice in the target language.
Video: subtitles or dubbing, and on-screen graphics inside the footage.
Images with embedded text: screenshots, diagrams, charts and infographics. These need the source file, not the flattened image.
Assessments: questions, answer options, feedback for correct and incorrect answers, score messages and certificates.
Interactions: drag-and-drop labels, hotspots, branching scenarios, “Try again” messages.
Supporting material: job aids, PDFs, glossaries, transcripts, notes pages.
Metadata: course title and description in the LMS, completion messages, email notifications.
If you skip any of these, the learner meets English in the middle of a Hungarian course. That reads as carelessness and undermines the rest of the training.
Captions and accessibility
Translated video should be captioned, and captions are also an accessibility matter in the US. In a 2018 settlement, the Department of Justice required an online test-prep provider to caption all online video content consistent with WCAG 2.0 AA. That case is specific to one company, but it shows how seriously captioning is taken. Budget for caption files in every language you ship, not just English.
Prepare the course before it goes to the translator
The cheapest translation is one that does not need rework. A few decisions made in the design phase save time and money later. Course development guidance stresses clear objectives, a defined audience, and multi-stage QA with subject-matter experts and instructional designers. Add translation readiness to that list.
Write source text that translates well
Use short, direct sentences. Avoid idioms, sports metaphors and jokes that depend on English.
Keep terminology consistent. If a “learner” is sometimes a “user” and sometimes a “trainee”, the translator has to guess whether these are the same thing.
Avoid text assembled from fragments, such as “You have completed” + variable + “modules”. Word order and endings in Hungarian make this unreliable.
Put narration scripts in a separate, final document. Do not translate scripts that are still being edited.
Build a flexible layout
Leave room in text boxes, buttons and tabs. Translated text is rarely the same length as the English.
Keep text as live, editable text, not baked into images.
Keep source files for graphics, video and audio together in one folder.
Avoid placing captions or labels over images in positions that cannot move.
Create a glossary and style guide first
Before translation starts, agree on key terms: product names that stay in English, terms with an established Hungarian equivalent, and your preferred tone. Decide on formal or informal address, which matters in Hungarian (more on that below). A glossary of even 50 terms prevents hundreds of inconsistencies and gives reviewers something objective to check against.
Choose the file workflow
Most authoring tools can export text for translation. Storyline, Captivate, Rise, Lectora and similar tools generally export to Word or XLIFF, and the translated file is imported back into the original course so layout and logic stay intact. Translators who work in CAT tools can load XLIFF directly, keep translation memory for repeated phrases, and run consistency checks. That is the workflow we use. It also means a later update to the course only costs you the changed segments.
Translating e-learning into Hungarian: what changes
Hungarian is not a language you can treat as a drop-in replacement for English. Several features affect e-learning in particular.
Longer words and different text length. Hungarian builds meaning by adding suffixes, so one word can carry what English expresses with a short phrase. Button labels, tab titles and multiple-choice options are the usual casualties. Plan to shorten or resize, not to cut meaning.
Case endings and variables. If a course inserts a name, a number or a product into a sentence, the surrounding words may need different endings. Hard-coded templates produce errors. We flag these during translation so they can be restructured.
Formal or informal address. Hungarian distinguishes between formal and informal forms of “you”. Corporate compliance training often uses a polite, formal register. Onboarding for a young team or a game-like course may use a friendlier tone. Choose once and keep it consistent across every module and the interface.
Name order, dates and numbers. Hungarian writes family name first, dates as year, month, day (2026. október 28.), and uses a comma as the decimal separator and a space for thousands. Quiz questions with numbers, units and currency need conversion and checking. Forints, metric units and local examples are usually more useful than dollars and miles.
Terminology. Many technical, medical, legal and software terms have an established Hungarian form. Others are used in English by practitioners. Correct choice depends on your audience. A nurse trainer, a CNC technician and a software developer will each expect different vocabulary. A translator who works in your subject area makes these decisions quickly and consistently.
Fonts and characters. Hungarian uses the letters ő and ű, which are different from ö and ü. Some fonts and older tools replace them or render them incorrectly. Check this early, because a font fix can require touching every slide.
Terminology, culture and expert review
Three layers of review keep translated training credible.
Terminology control
Start with the glossary, load it into the CAT tool and let the software flag deviations. For each new term, record the decision and the reason. When a client’s subject-matter experts later disagree with a term, the record makes the discussion short.
Cultural adaptation
Go through the course asking what would sound foreign to a Hungarian learner:
Names and characters in scenarios, and workplaces that look distinctly American.
Holidays, sports, food and brands used as examples.
Legal and regulatory references that do not apply, such as US-specific rules in a course for a Hungarian site. Replace them with the local equivalent, or mark them clearly as US requirements.
Images of people, offices and gestures. Check that they suit the audience.
Humor and idiom. Adapt it or remove it.
This is where localization earns its cost. A purely literal translation of a customer-service scenario can be correct word by word and still unconvincing to the person doing the training.
Subject-matter expert review
Have a Hungarian-speaking expert in your field read the translated script, ideally in context. Give them a clear brief: check terminology and accuracy, not personal style. Collect feedback in one place, and send it to the translator so the glossary and translation memory are updated. Otherwise the same correction will be needed again in the next course.
Perspective: what we see in real course projects
We are a one-person studio, and that shapes how we handle e-learning. The same translator who reads your script also works in the CAT tool, checks terminology and answers your questions. Nothing is passed between departments, so nothing gets lost between them.
The pattern we see most often is that the translation itself is not what goes wrong. Problems appear when the files arrive without context: a spreadsheet of strings with no screenshots, a script that is still changing, a quiz whose correct answers are not marked. A translator who sees only a string cannot tell whether “Close” is a button or an instruction. We ask for the course preview, or at least screenshots, at the start. It saves rounds of corrections.
Our second recommendation: do not skip the in-course review. We can deliver a perfectly good translation and a Hungarian text can still clip in a button. We would rather see that on the first import than hear about it from your learners. Urgent projects are part of our work, and we are often reachable outside regular business hours. Realistic deadlines and confidentiality are non-negotiable for us, which matters when your training covers internal procedures or unreleased products.
Our third point is about machine translation. For large volumes of routine material, machine translation with human post-editing can be a sensible choice. For safety, medical, legal or customer-facing content, we recommend full post-editing or a fresh human translation. We will tell you honestly which fits which module.
— Bernadett
Testing the translated course
Three kinds of testing are needed, and they catch different problems. Run them in this order.
1. Language quality
A second linguist, or the client’s expert, reads the full text in context. They check accuracy, terminology against the glossary, tone and register, consistency between narration and on-screen text, and typos. Include quiz feedback and error messages, which are easily forgotten.
2. Technical function
Publish the translated course to the format your LMS uses and test it there, not only in the authoring tool. Check:
Every slide, layer and state: no clipped or overflowing text, no leftover English.
Special characters (ő, ű, á, é, í, ó, ú) in every font and in the player.
Audio and video sync, caption timing and caption line length.
Quiz scoring, branching logic, triggers, variables and completion tracking in the LMS.
Downloads, links and printable certificates.
3. Learner usability
Ask two or three real learners to take the course without help. Watch where they hesitate. A term can be correct and still unfamiliar on the shop floor. A native-speaking pilot group often finds the issues no checklist covers, such as an instruction that sounds stiff or a scenario that does not seem plausible.
Keep a defect log with screenshots, label each item as language, technical or design, and fix them in one batch. Then retest the fixes, not only the item that was reported, because changing text length can disturb something nearby.
What e-learning translation costs
Translation is usually priced per source word, with extras for multimedia work such as recording, subtitling or layout fixes. Our published per-word rates are:
Service | Rate |
Translation into Hungarian | from €0.05 per word |
Translation into English, German or French | from €0.07 per word |
Machine translation post-editing, full | from €0.04 per word |
Machine translation post-editing, light | from €0.03 per word |
Localization is quoted per project, because the scope depends on how much of the course needs cultural adaptation. The final price depends on subject matter, volume, file format and deadline. Repeated and previously translated segments reduce the effort, which is why a CAT workflow matters when you update courses over time.
To estimate your own budget, count the words in the exported file, add narration scripts and quiz text, and ask for a quote on that total. Add a small allowance for in-course review time.
Work with us on your Hungarian course
If you are bringing a course to Hungarian-speaking learners, or need English, German or French versions of Hungarian training, we can handle the text, the terminology and the review in one workflow. We work in technical, medical, legal, automotive, financial, software and video game content, and we use CAT tools and quality checks suited to high-volume projects. Send us a sample export and the course preview on our translation and localization services page and we will tell you what the project involves and quote it.
If you are comparing options, ask for the same things from any provider: a glossary process, a clear approach to the in-course check, confidentiality terms and a realistic deadline.
FAQ
How long does e-learning translation take?
It depends on word count, subject matter and what else is included. Text translation moves fast, while voice-over, video and in-course testing add time. Tell us your deadline when you send files, and we will give you a realistic schedule rather than an optimistic one.
Can I use machine translation for my course?
Sometimes. Machine translation with post-editing suits large volumes of routine content and lowers cost. For safety, medical, legal or customer-facing modules, full post-editing or human translation is the safer option. A mixed approach, by module, is common.
Do I need to translate videos and audio too?
Yes, if learners need them to complete the course. At minimum, provide translated captions or subtitles. For narration, the choice is dubbing, a new voice recording or a text-only alternative. Any video you publish in the US should also be captioned for accessibility.
Should I localize or just translate?
Translate technical, procedural content for learners in a similar context. Localize when scenarios, tone, examples or regulations differ by country. Most courses benefit from a split decision, module by module.
What files should I send to a translator?
Send the exported XLIFF or Word file from your authoring tool, the narration scripts, source files for graphics with text, a glossary if you have one, and a course preview or screenshots. Context is what turns a good translation into a correct one.
Sources
Comments