Media localisation is successful when audiences in the intended language receive the same meaningful, actionable content across speech, captions, graphics, controls and links. A translated subtitle file is not proof of a localised experience. The practical gold standard is content that people can understand and use through the actual device and publication route.
Start by defining the source edition, each intended audience, which language and accessibility features are promised, and the person authorised to accept them. Then verify the entire audience journey, including names, numerical conditions, on-screen graphics and corrections. This guide follows the fictional River Signals educational series across three Singapore language editions.
Its sector scope differs from specialist Subtitling Services, Dubbing and Localisation and Captioning Services. Those create individual formats; this article governs their consistent connection across an entire product.
Start with the decision that matters
- **Client:** Which languages and surfaces have we promised, and what evidence will constitute acceptance?
- **Translator:** Which source revision and glossary are authoritative, and where does expert review apply?
- **Producer:** Are audio, graphics, captions and player metadata all aligned with the same cut?
- **Audience:** Can I select my language, understand the important message, and reach the current official information?
Choose a practical reading route
20-chapter working index
Audience, source and standards · chapters 1–7
- Begin with a useful answer to the audience’s question
- State what ‘localised’ means for this product
- Separate language, locale, dialect and delivery territory
- Build one current authoritative source package
- Translate meaning, qualifiers and practical action
- Use ISO 17100 within its actual boundaries
- Distinguish machine-translation post-editing from human translation
Terminology, graphics and language media · chapters 8–13
- Maintain terminology and source authority across versions
- Localise graphical information, not only speech
- Adapt examples without falsifying the original story
- Separate subtitles, captions, dubbing and voiceover
- Direct localised performances for character and context
- Give subtitles realistic reading and layout rules
Platforms, updates and rights · chapters 14–17
Access, testing and evidence · chapters 18–20
1. Begin with a useful answer to the audience’s question
A fictional education publisher creates a short video series, River Signals, teaching families to interpret rainfall and public flood-warning information. An English edition works well during workshops. For Singapore audiences, the publisher plans Mandarin, Malay and Tamil versions, plus accessible text. The project is apparently ready after subtitles are translated, yet the Malay graphics still contain English warnings, the Mandarin voiceover describes an obsolete diagram and the Tamil information link directs viewers to the wrong-language page.
Localisation excellence means that people in the intended language can understand and use the same essential message through the actual experience. Translation of dialogue is one part. Screen graphics, navigation, sound, accessibility, rights, culturally relevant examples, dates, source updates and playback need to agree. River Signals is fictional, but the central mistake is common: counting translated files rather than verifying that an entire audience journey works.
Back to chapter index · Continue to chapter 2
2. State what ‘localised’ means for this product
A film, game, course, podcast and streaming interface do not require identical deliverables. A course may need exercises, quiz feedback, graphics and learner support localised along with lectures. A documentary may need subtitles, language-specific narration, public-source accuracy and distribution metadata. Specify which surfaces are within scope before commissioning translators, artists or developers.
For River Signals, the localisation package might include six short videos, on-screen captions, a downloadable glossary, a web landing page, transcript links and assessment questions. Write the languages, audience proficiency, devices and relevant locales into the brief. The client can then see which items are included, which remain source-language only and why. A general line saying ‘multilingual release’ is not an acceptance criterion.
Back to chapter index · Continue to chapter 3
3. Separate language, locale, dialect and delivery territory
A language name is not the same as a locale, and neither necessarily establishes legal rights to distribute a recording in a country. Language choices can affect terminology, script, pronunciation and cultural context. Service providers should establish the actual audience rather than automatically substitute a generic global market version.
A Mandarin version for Singapore families may include different references from a campaign prepared for another region. The goal is not to assume that every local speaker uses identical expressions; a reviewer should confirm naturalness and clarity for the intended use. Where multiple scripts or regional variants are commissioned, label them accurately. Do not confuse a valid language tag on a media file with verified translation quality.
Back to chapter index · Continue to chapter 4
4. Build one current authoritative source package
Localisers may receive video from an editor, captions from another agency, a website from marketing and an older slide deck from the educator. If those sources conflict, every resulting translation risks becoming a different lesson. An authoritative source package should identify approved picture, dialogue, on-screen claims, glossary, related links, dates and open issues.
Suppose the English video was updated to distinguish a weather forecast from an issued warning. The translation team must receive that change before producing a voiceover and captions. Record versions and effective dates. For consequential public-service information, consult the actual responsible authority rather than turn an old blog reference into a current official instruction. A localisation coordinator should be able to say exactly which source each finished claim represents.
Back to chapter index · Continue to chapter 5
5. Translate meaning, qualifiers and practical action
Literal equivalence is not always understandable equivalence. Languages can structure warnings, politeness and conditions differently. The translator needs the surrounding sequence and intended action, not isolated lines. Negations, dates, numbers and eligibility conditions must remain correct even when condensation is needed for on-screen reading.
A sentence meaning ‘check the official bulletin before deciding’ must not become ‘the bulletin confirms an emergency’ in another language. The project should include qualified review of high-impact phrasing, especially where safety or public eligibility is involved. Natural expression and factual discipline reinforce one another. A technically fluent sentence that instructs the wrong action is a localisation failure regardless of how elegant it sounds.
Back to chapter index · Continue to chapter 6
6. Use ISO 17100 within its actual boundaries
Translation-services quality depends on competent people, project specifications, resources and review processes. ISO 17100 can inform how a provider organises translation, but it does not certify an entire audiovisual programme simply because someone has used its vocabulary. Subtitling, narration, graphics and integration still need their own tests.
ISO 17100:2015, with its 2017 amendment, remains the current published translation-services standard as of October 2026; ISO’s replacement work item is still under development. Its scope excludes raw machine-translation output plus post-editing. The publisher should therefore ask which service process is actually being provided and avoid generic claims of ‘ISO localisation certification’ without verified scope or an appropriate basis.
Back to chapter index · Continue to chapter 7
7. Distinguish machine-translation post-editing from human translation
Machine translation can help with large quantities of repetitive content, but smooth output may conceal an incorrect qualifier, unexplained technical term or culturally inappropriate phrase. Some projects can responsibly use human post-editing, while others require more extensive expert work and source investigation. Procurement must name the method and review level honestly.
ISO 18587:2017 covers full human post-editing of machine translation output; its successor is a draft and has not replaced that edition. The standard is not evidence that a particular AI model produced accurate text or that untranslated screen elements were addressed. For River Signals, qualified reviewers still need to check numbers, official terminology, the speaker’s intended meaning and how the text actually appears in the video.
Back to chapter index · Continue to chapter 8
8. Maintain terminology and source authority across versions
A glossary helps multiple contributors use consistent names for warnings, places, units and educational concepts. It should identify preferred terms, source, allowed alternatives and who may approve a correction. Terminology management becomes especially valuable when several episodes or languages are released over time.
If a scientific term has two familiar target-language renderings, the specialist reviewer should select the one best aligned with the audience and authoritative curriculum or public guidance. Record the reasoning rather than force translators to guess. A controlled glossary reduces avoidable inconsistency but must remain open to correction when current official terminology changes. Consistency with an obsolete term is not accuracy.
Back to chapter index · Continue to chapter 9
9. Localise graphical information, not only speech
Many learning videos depend on maps, labels, charts, arrows, captions and numbers. A translated voice track cannot fix an on-screen label that communicates a contradictory or untranslated message. Graphics localisation may require editable artwork, suitable fonts, safe areas and a version of the design that leaves enough room for longer words.
In the fictional Malay edition, a rainfall diagram still uses English-only warning labels. The user who watches with sound muted cannot follow it. The publisher should either translate the labels accurately or provide an equally usable alternative within the agreed format. Validate the chart’s numerical and spatial meaning before approving a cosmetic design update. The best localisation treats pictures and language as parts of one explanation.
Back to chapter index · Continue to chapter 10
10. Adapt examples without falsifying the original story
Cultural adaptation may change a reference, measurement convention or everyday example to improve comprehension. It should not silently rewrite a documentary location, a speaker’s identity or the historical setting. Creative fiction and factual reporting offer different degrees of adaptation, and each needs agreed editorial authority.
A general example about a foreign river can be supplemented with a Singapore-relevant comparison if the publisher approves and labels it correctly. But a real interview about a particular flood should not be presented as a Singapore event merely to increase local interest. Give translators background notes and subject specialists a role in important changes. An accessible explanation can be local without pretending every source originated locally.
Back to chapter index · Continue to chapter 11
11. Separate subtitles, captions, dubbing and voiceover
These products provide different forms of access. Subtitles can translate dialogue, captions add meaningful non-speech audio information, dubbing involves adapted performance and voiceover narration has its own use cases. One does not automatically replace the others; some viewers need more than one form simultaneously.
W3C explains captions and subtitles, while Netflix’s localisation best practices show practical platform-specific challenges. A video described as available in Tamil should clarify whether that means translated subtitles, audio narration or both. The client should not discover that its promised accessible edition contains only partial dialogue translation and no meaningful sound descriptions.
Back to chapter index · Continue to chapter 12
12. Direct localised performances for character and context
A language-specific recording may be a straight informational narration or a character-based dub. The latter needs acting, rhythm, timing and emotional continuity as well as accurate words. A fluent performer can still sound wrong if a line is delivered with the opposite intention from the source scene.
For River Signals, clear, calm narration is more valuable than an exaggerated promotional voice. If the content includes characters, the team may need qualified direction and picture-aware adaptation. Netflix’s dubbing principles discuss authentic performances and natural phrasing, but are a partner-specific creative reference, not a universal certification. Performers must have clear permitted uses, suitable conditions and appropriate consent for any digital replica proposal.
Back to chapter index · Continue to chapter 13
13. Give subtitles realistic reading and layout rules
Translated text often expands or contracts compared with the source. The intended platform may limit line length, reading speed or safe display areas. Those constraints affect comprehensibility but must not excuse removing critical qualifiers or altering numerical values.
Review timed text in the actual video with a target-language specialist. A phrase may be linguistically correct yet disappear too quickly, divide an important name across lines or obscure the chart it explains. Different languages and scripts require different decisions. Netflix’s timed-text guidance is a useful example of a defined delivery specification, but the actual buyer’s requirements and user needs must govern.
Back to chapter index · Continue to chapter 14
14. Confirm fonts, interface controls and language tagging
Localisation extends to file names, language selection, player controls, chapter markers and accessible text descriptions. A language asset can be technically present yet unreachable if the interface has the wrong label or cannot display its characters. Fonts, line spacing and assistive-technology support are part of the delivered service.
The fictional Tamil edition has a correct language track but its dropdown sends users to the Mandarin audio. No amount of proofreading the Tamil file fixes the selection bug. Test each locale end to end through the real website or app, including captions on/off and basic keyboard or screen-reader controls where offered. W3C’s media player guidance explains why the actual player matters as much as the content files.
Back to chapter index · Continue to chapter 15
15. Synchronise source updates across every target language
An education series may need factual corrections after publication. A source amendment can affect narration, timed text, transcripts, figures, quizzes and linked guidance across several languages. Without version management, the English correction may be published promptly while other versions continue giving an obsolete instruction.
Use a change-impact register: which original claim changed, which target assets depend on it, who reviews each one and when the correction became visible. Do not present all releases as updated because the central spreadsheet has a green cell. The team should verify the actual published path for every affected locale and provide appropriately visible corrections if earlier information was consequential.
Back to chapter index · Continue to chapter 16
16. Protect rights, voices, music and translated material
Audio, images, scripts, photographs, songs, voice performances and translated text can have different owners and licence terms. A licence to use a song in one film or language may not automatically authorise a new translated lyric, advertising cut or voice model. Legal scope must be assessed separately from technical ability.
WIPO’s copyright resources outline protected creative works and the need for permission as applicable. A localisation provider should record translation and performance contracts, relevant territories and third-party assets without publishing private agreements unnecessarily. If a language vendor uses external AI tools, the owner must approve the data and rights conditions; ‘AI-assisted’ is not an exemption from a contractual obligation.
Back to chapter index · Continue to chapter 17
17. Make accessibility meaningful across languages
An English version may have verified captions and a descriptive transcript, while translated versions lack non-speech descriptions or useful screen text. That gap affects whether the new audience can access the same information. The accessibility plan should specify which features apply to each released language and what is not yet available.
W3C’s media-accessibility guidance addresses captions, description, transcripts and sign-language alternatives as distinct needs. A Deaf viewer reading another language may need full captions rather than dialogue-only subtitles. A screen-reader user should be able to locate the correct transcript without navigating untranslated buttons. A localised release should not claim equivalent access merely because its spoken words were translated.
Back to chapter index · Continue to chapter 18
18. Test the complete audience journey, not isolated files
A quality reviewer may approve translation in a document and audio in a studio while users cannot choose the correct language on a phone. Acceptance must cover the real flow: discover the relevant edition, understand its title, start playback, access the appropriate track, interpret graphics and follow important links.
Choose representative devices, users and scenes. For River Signals, a reviewer should be able to explain a rainfall chart, distinguish a forecast from a warning and locate the correct official information in each promised language. Record what failed with sufficient detail to reproduce it. Test comprehension, not merely the absence of spelling errors. A language pack without functioning navigation is an incomplete product.
Back to chapter index · Continue to chapter 19
19. Use useful metrics rather than counts of translated words
Word counts, languages released and files delivered can help with project planning. They do not establish that families understood the advice or received correct controls. Quality indicators might include unresolved source conflicts, material semantic errors, wrong-language selection, broken text rendering, access barriers and correction turnaround.
A provider should review problems by cause, not penalise every translator for an integration defect or hide a material mistranslation inside a high average accuracy score. Seek appropriate target-audience feedback without claiming a tiny focus group represents the entire language community. A useful acceptance scorecard should show the intended action, observable evidence and owner for remediation, with documented exceptions instead of promotional percentages.
Back to chapter index · Continue to chapter 20
20. The gold standard is one authoritative meaning across many languages
Return to River Signals. Its Malay, Mandarin and Tamil editions now use the current source, convey the actual warning distinction, display correct translated figures and route viewers to the appropriate guidance. Each language has the promised access features and a traceable rights and change history.
Media localisation earns its gold standard when audiences in different languages can reach reliable, culturally intelligible information without receiving contradictory content. The success is not a multilingual badge or the number of translated files. It is a single responsible publication system that keeps meaning, creative purpose and practical access consistent wherever the media is experienced.
Worked case: three languages, three different failures
The River Signals example is entirely fictional; its tests show why teams should not judge the number of completed translations as the end result. Each failure needs a qualified owner and a different kind of evidence.
| Edition | What appeared complete | Actual failure | Acceptance test |
|---|---|---|---|
| Malay | Subtitles delivered | Critical chart labels remain English-only | Malay reviewer explains chart with sound off |
| Mandarin | Voice track recorded | Audio refers to obsolete diagram | Latest picture and approved narration verified |
| Tamil | Translated content available | Wrong-language information link | Real device completes full information journey |
| English source | Corrected master uploaded | Other target versions not updated | Change-impact record and every public route checked |
Contract-ready localisation delivery matrix
The scope below can be copied into a vendor brief and adapted by language, accessibility need and platform. Blank cells are not evidence of completion and should be assigned or explicitly excluded.
| Deliverable | Who verifies meaning | Who verifies functionality | Critical evidence |
|---|---|---|---|
| Spoken or dubbed audio | Language lead + editor | Producer + sound QA | Picture and performance alignment |
| Subtitles / captions | Translator + access reviewer | Timed-text engineer | Natural reading, sound cues as scoped |
| Graphics / charts / units | Subject specialist + translator | Designer + device tester | Numbers and labels match source |
| Interface / landing page | Local language reviewer | Accessibility + web QA | Correct links and language selection |
| Source correction | Authorised editor | Release manager | Every dependent version updated |
An approval checklist that exceeds file-count reporting
- Define source version, programme purpose, intended audiences and actual locales.
- Use current published standards; distinguish ISO 17100 from ISO 18587 and drafts.
- Record rights, contributor permissions, languages, scripts and target devices.
- Verify proper names, numbers, warnings, conditions and specialist vocabulary.
- Review timed text, sound, graphics, accessibility and interface integration.
- Test one complete representative task in each promised language on supported devices.
- Retain source-to-target change mapping and the owner of corrections.
- Publish known limitations instead of claiming unsupported universal accessibility.
Frequently asked questions
These questions cover procurement, standards, language choice and post-publication responsibilities. They are additional decision guidance, not replacement text for the twenty chapters.
1. Is media localisation the same as translating subtitles?
No. Subtitle translation is one asset within a larger media service. A localised learning video can also require translated graphics, a suitable voice track, text descriptions, working language controls, source references, licensing and corrections. The practical distinction is whether the intended audience can complete the relevant experience. A flawless subtitle file attached to a player whose language button fails cannot deliver that result.
2. Should a Singapore project automatically create four language versions?
Not automatically. The right selection follows the audience, brief, public-service obligations if applicable and actual capability to maintain the editions. Singapore audiences are multilingual, but individuals differ in language proficiency, reading preference and accessibility needs. It can be better to deliver and maintain a clearly prioritised set of dependable versions than to promise more languages whose accuracy, navigation and support are not funded.
3. Does ISO 17100 certify every translated video?
No. ISO 17100:2015 sets requirements for specified translation services, their resources and processes. It does not automatically certify the whole audiovisual workflow, the device, sound performance or a particular broadcaster’s regulations. Its scope also excludes the raw-output-plus-post-editing model; ISO 18587:2017 addresses full human post-editing of machine translation. Ask which process and independently verified claim actually apply.
4. Can machine translation reduce the price without reducing quality?
It can sometimes improve efficiency, especially for repetitive structured content, but outcomes are dependent on source quality, language pair, subject and human review. It may mishandle negatives, proper names and cultural meanings. A responsible quotation identifies machine assistance and the review level, as well as the cost of audiovisual integration. An apparently cheap line-by-line translation may become expensive when graphics and voice tracks need correction.
5. What happens if an English source changes after other languages are released?
Record the change’s meaning, identify dependent subtitles, dubbing, narration, graphics, transcripts, quizzes, links and published metadata, then assign qualified owners. Correct the actual audience-facing editions and communicate material issues where appropriate. A source spreadsheet marked updated is not evidence that every player now serves the correct version. For consequential public information, record the verification date and source authority.
6. Why can a linguistically correct subtitle still fail?
It may be timed against the wrong cut, displayed too briefly, split across a confusing line break, cover critical on-screen information or contain unsupported characters in the destination player. The correct test is the target-language experience on the actual device, not only proofreading text. A multilingual rollout needs technical and content acceptance as distinct steps because either can invalidate the audience’s understanding.
7. Is dubbing preferable to subtitles for every audience?
No. Preferences and needs vary. Subtitles preserve original performances for readers who can use timed text, while dubbed or voiced editions may support others or particular storytelling aims. Captions for Deaf viewers carry meaningful sounds as well as speech and should not be conflated with dialogue translation. Some users benefit from transcripts or sign-language alternatives. Offer suitable choices where practicable rather than declare a single format universally best.
8. How should a client measure localisation quality?
Use defined tests tied to risk: source and terminology accuracy, consequential numbers and conditions, natural expression, language tagging, visual compatibility, player controls, access features and timely corrections. A practical pilot asks target users to explain a key event or complete the action the media is meant to support. Report limitations and exception owners. Translation volume and delivery speed alone are weak measures of public usefulness.
9. Who approves changing cultural references in a factual film?
The authorised editorial or rights owner should decide with qualified cultural and language input. Explaining an unfamiliar term is different from rewriting a real place or speaker’s history. Document material adaptations and whether they are narrations, subtitles, graphics or supplementary explanations. A documentary must not quietly turn an overseas event into a local event just to improve relatability.
10. What should accompany a final localisation handoff?
At minimum, specify the approved source and picture version, each language and locale, content files and roles, rights and performer use terms, accessibility features, technical delivery formats, responsible reviewers and known limitations. Include a way to request corrections and identify obsolete versions. These records let another team maintain the media without reconstructing why a phrase, font or audio track was selected.
Source library and exact standard applicability
- ISO 17100:2015 translation services, with 2017 amendment
- ISO replacement work item (under development)
- ISO 18587:2017 machine-translation post-editing
- W3C Making Audio and Video Media Accessible
- W3C Accessible Media Players
- Netflix Localisation Best Practices
- Netflix Dubbing Guiding Principles
- WIPO copyright and creative rights
- eduKate — Subtitling Services
- eduKate — Dubbing and Localisation
- eduKate — Video Accessibility Services
- Gold Standard Sectors & Services Directory
Standards note, October 2026: ISO 17100:2015 (with amendment) and ISO 18587:2017 remain published; replacement projects are in development. ISO standards have specified scopes and do not automatically certify a finished film, translation quality, player accessibility or the compliance of every provider. Platform partner guides are contractual examples rather than rules imposed universally.
