Define the scope first
Adapt website, software and digital-product content to the target market, interface context and release environment.
Tell us the target language, purpose, receiving audience and desired timing. Related files for the same matter can share a contact, spellings, terminology and delivery plan; main text, attachments and supplementary records are checked separately.
Restoring user tasks behind strings
Website and software text must work in real pages and interactions. Content structure, interface states and resource formats need to be considered together to avoid wording that looks correct in a spreadsheet but confuses users.
Page purposes and information paths
Organize copy by page purpose, such as introduction, comparison, help or request submission, checking headings, links and actions together. List search snippets, form prompts and errors separately. Query missing product facts rather than add unconfirmed capabilities during localization.
Dynamic grammar and resource structure
Distinguish actions, states and sentences by key and use sample variable values to assess word order, plurals and optional segments. Preserve placeholders, tags, escapes and keys. Suggest separate resources when one source string cannot serve all contexts, with developer confirmation instead of unnatural concatenation.
Forms, help and state feedback
Review field labels, examples, validation and submission results as a set against the real flow. Suggest understandable date, number and measurement wording, but let product owners confirm format or rule changes. Updated copy must not conflict with the format the interface actually requires.
Connecting import and release checks
After translation, identify who imports resources and which environment can be checked. Handoffs by key, page and revision connect language feedback to development or content maintenance.
Resource handoff and protected fields
Confirm resource format, encoding, ordering and non-translatable fields. Supply reference and query files where agreed. Parseable files establish readable structure, but missing entries, duplicate keys and actual screens still need checks; parsing alone does not confirm release behavior.
Screen review and issue location
In the supplied preview environment, check truncation, wrapping, terms and context within scope, logging routes, keys and screenshots. Assign wording separately from code or layout issues and recheck the new version. Do not claim coverage of inaccessible states, devices or flows.
Incremental updates and content status
Identify updates by keys and source differences and track removed and pending entries. Maintain impact lists where pages, help articles and email templates share feature descriptions. Separate additions after a freeze so some languages do not silently retain obsolete product information.
Materials and content
Websites
Confirm pages, strings, help content and other product assets within the release scope.
Interfaces
Use screenshots and context to check variables, placeholders, length limits, actions and terminology.
Digital products
Agree language checks, file reintegration, version updates and the process for collecting feedback.
Translation and review priorities
- Confirm pages, strings, help content and other product assets within the release scope.
- Use screenshots and context to check variables, placeholders, length limits, actions and terminology.
- Agree language checks, file reintegration, version updates and the process for collecting feedback.
Delivery, 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.
What should I prepare?
Provide a clear, complete source and relevant references. Include approved translations, required terms or name spellings where available. Share special receiving formats, statement or signature requirements and other supporting needs for individual confirmation.
Explore related services
Confirm the project details
Is an Excel string table enough to start?
Start by checking keys, context and variable examples and request missing screenshots or action descriptions. Text work can be staged, but length, dynamic composition and runtime display need an appropriate environment. Spreadsheet completion does not complete import or screen review.
What if variable order must change in the target language?
Check whether the resource supports numbered or named placeholders, then propose grammatical target wording. Preserve immutable code fragments. If the format cannot support natural language, refer affected keys to developers instead of deleting variables or replacing them with fixed values.
Does truncation after release require retranslating the whole site?
Locate the page, device, language and key to distinguish wording length from layout limits. Shorten affected text or adjust space, then recheck relevant states. Shared components need checks across affected pages; neither a full restart nor closure from one screenshot is automatically justified.