Content globalization combines reusable source content with the work needed to serve different languages and locales. A useful workflow tracks what changed, which versions are affected and who has approved each one. Start with one important reader journey and make that journey complete in every supported locale.
Separate language from the broader locale
A language identifies the text being used. A locale can also affect dates, numbers, addresses, currencies and expectations about a service. Two audiences using the same language may need different examples, availability information or contact routes.
The W3C distinction between internationalization and localization is useful: internationalization prepares a system for adaptation, while localization adapts it for a particular audience. Decide which parts of your system must support variation before sending text for translation.
List supported audiences, the tasks they must complete and the person who can validate each locale. Include forms, error messages, image text, downloads and follow-up emails. A translated landing page with an untranslated essential form leaves the journey incomplete.
Prepare a stable source package
Give content a stable identifier and revision number. Resolve ambiguous terminology, define product names and record words that should remain unchanged. Supply a brief explaining the audience, task, tone, relevant service limits and any space constraints.
Separate changeable facts from repeated prose where that makes maintenance clearer. Avoid embedding important instructions only in images. Provide the translator with screenshots or a preview showing where the words appear, plus explanations for variables and placeholders.
A glossary records approved terms and context. A translation memory stores previously translated segments for possible reuse. Reused text still needs review when the surrounding task, product or meaning changes. Record the tool and process used without treating a match percentage as approval.
Track review for each version
| Field | Example | Why it matters |
|---|---|---|
| Content identity | HELP-001 | Connect all language versions to the same task. |
| Source revision | Revision 7 | Identify the facts being translated. |
| Target language or locale | fr-CA | Define the intended audience. |
| Translation status | In linguistic review | Make the next action visible. |
| Local reviewer | Named service representative | Check service details and local suitability. |
| Published source revision | Revision 6 until release | Expose a lag behind the source. |
Move a locale through translation, linguistic review, factual/local review and publication verification. Combine roles only where the people have the required competence. If machine translation or an AI assistant supplies a first draft, keep the same checks for meaning, omissions, terminology and sensitive information.
Agree whether releases must be synchronized. Some changes can wait for every locale; an urgent correction may require a temporary notice or withdrawal in an affected language. The accountable owner should decide how readers will receive accurate guidance during the gap.
Follow one source change through two locales
Track the fact dependency as well as the page. A reused instruction can appear in several guides; a translation queue based only on whole-page titles may miss those copies.
Check the delivered page in context
Use the correct lang attribute for the page and mark language changes where appropriate, following W3C language declaration guidance. For right-to-left content, configure direction explicitly and test mixed text such as product codes and phone numbers using W3C directionality guidance.
Test long headings, expanding buttons, numbers, dates, line wrapping and navigation at narrow widths. Check that language switches lead to the corresponding content where available and explain missing equivalents. Have a competent reviewer read the actual rendered page and downloaded files, since a translation spreadsheet cannot show every layout problem.
Download the localization brief and release checklist. Record the source revision, glossary, reviewers, pending changes and public verification. Review the workflow whenever a new locale, content type or publishing channel is added.