Language in context
Localization goes beyond the text. It considers interface space, dates and numbers, visual context, button labels and the steps a user takes. Websites, apps, help centres and campaigns can share the same terminology and style rules.
Put language into its page, interface and playback context
Website, software, game and audiovisual teams need more than a text table removed from its context. Provide content locations, user actions and publishing methods so language work connects with development, design and editorial tasks. Identify which outputs are text files and which require reintegration or checks in a working environment.
Organise website content around page relationships
For corporate websites and campaign pages, supply a page list, navigation relationships, heading hierarchy, link destinations and text embedded in images. Identify body copy, buttons, form messages and page descriptions. Existing keywords, brand language and approved product facts can guide the work, with translation distinguished from audience-focused rewriting. Deliverables can map to pages or content fields. CMS entry, link changes and post-publication language checks require separate agreement on access and publishing responsibilities.
Keep software UI and game text connected to function
Provide resource files with stable keys, screenshots, length limits, variable descriptions and steps that reproduce the relevant interaction. The same word can mean different things in a menu, status message or quest description, so a glossary alone cannot justify global replacement. Preserve placeholders, tags, escape sequences and plural rules according to the project format. Games also need character, world and quest references. Record locations, versions and reproduction steps for truncation or reference issues so developers can address them.
Distinguish subtitles, voice scripts and finished media
For audiovisual work, provide playable footage, approved dialogue, speaker details, on-screen text and any existing timing files. State whether the material supports subtitles, voice performance or visual replacement. Subtitle text, timed subtitle files, voice scripts, recordings and final video are distinct outputs. Define line limits, placement and treatment of off-screen speech. Compositing or release previews require agreement on material rights, source projects and production contacts; delivery of translated text does not itself complete production.
Built for updates
At the outset, we review file formats and content structure, including protected terms, variables, tags and character limits. Where a preview or test environment is available, we check the translated content in context and retain version and feedback records.
Copy shaped for the market
Product descriptions, brand stories and search content should reflect how local audiences look for information. We adapt phrasing, information order and terminology while preserving facts, brand voice and agreed compliance requirements.
Make release checks traceable and repeatable
- Retain string keys, file paths and versions in the delivery list; agree which content is imported into the system and which is advisory.
- Log the page or key, screenshot, proposed wording and retest status for language issues; route functional issues to product or development staff.
- Track new, repeated and revised strings separately after release, using the approved market, terminology and review rules.
Confirm the project details
Can work start with a string table but no test environment?
Text work can be assessed first, supported wherever possible by screenshots, field descriptions and interaction context. Identify material that cannot be checked in the interface. Confirming button meaning, length or dynamic variable display may still require a later screenshot review or access to an appropriate environment.
How should updates be specified across language versions?
Provide the baseline version, changed fields and a list of additions and deletions, identified by page or resource key. Existing translations, terminology decisions and screenshots should refer to that same version. Even a small source edit can affect connected messages or other pages, so agree the related review scope as well.
