Websites and software
Check context using pages, strings and screenshots, considering variables, placeholders, length and interface actions; define reintegration and linguistic checks.
Explore this topicPut 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.
Games and audiovisual content
Align narrative, characters, terms and voice, using visual, audio and timing context to coordinate subtitles, voice scripts and updates.
Explore this topicContent and release coordination
Distinguish translation, transcreation, original writing and technical work, defining markets, channels, format constraints and customer review roles.
Explore this topicDelivery, price and timing
Price and timing are assessed against language direction, word or page volume, subject matter, source clarity, editability, layout, review and supporting requirements. Changes to the source, languages or supporting work require a revised scope and plan.
Agree Word, PDF, Excel, subtitle or other formats, including any editable files, paper copies, statements or signatures actually needed. Supporting arrangements are defined for the particular purpose and receiving requirements.
A clear process at every stage
- 01
Define the purpose
Specify files, languages, volume, receiving requirements and timing.
- 02
Agree the plan
Confirm scope, references, review responsibilities, supporting work and delivery.
- 03
Translate and review
Use subject references and check terms, numbers, tables and versions.
- 04
Deliver and coordinate
Deliver the agreed files, consolidate feedback and confirm later updates.
Explore related services
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.