Translation Guides
How to Prepare Files for Translation
Prepare source documents, spreadsheets, design files, PDFs, and software strings so translators can work with the correct content and return usable multilingual deliverables.
A Translation-Ready Handoff
Package the source, context, and review requirements together.
Preparing files for translation is not only a format issue. It prevents ambiguity about the approved source, reduces needless rework, protects identifiers and formulas, and makes downstream review more predictable. The right package will depend on whether you are translating a simple document, a complex technical manual, or a structured digital product.
Key Takeaways
- Provide the latest approved editable source whenever possible, plus a reference export for layout.
- Identify protected numbers, formulas, identifiers, and variables before translation starts.
- Supply target locales, glossary, context, and clear review ownership.
- Check handoff completeness and delivery requirements before requesting a final quote.
Confirm the Approved Source Files and Version
Before requesting translation, confirm the audience, target languages, content owner, and final source version. Remove obsolete sections, unresolved tracked changes, duplicate documents, and contradictory terminology. If the material is still being edited, identify a source freeze or a process for notifying translators of changes.
Collect helpful references: approved prior translations, product glossaries, terminology preferences, style guidance, screenshots, brand names, and legal or regulatory context. Where exact wording is mandatory, note it explicitly. Do not assume translators can infer the correct market or product version from the filename alone.
A Translation-Ready File Set
Illustrative package structure. Provide the actual source and references needed by your project; do not duplicate outdated material.
Prepare Word and PowerPoint Content
Word files are easier to process when text uses real styles, headings, tables, and lists rather than manual spaces or screenshots. Accept or reject tracked changes according to the approved source, resolve comments that are not intended for translation, and keep tables editable whenever possible.
For PowerPoint, identify text in shapes, speaker notes, charts, embedded documents, and images. Translated text may expand and require slide reflow, so leave reasonable space and clarify whether final deliverables must preserve the original design. Hidden slides and notes should be included or excluded explicitly.
- Use real headings, lists, captions, and table structures.
- Resolve comments and tracked changes or clearly identify what should remain.
- Provide editable diagrams and embedded text where available.
- Check hidden slides, speaker notes, and excluded material in the scope.
Prepare Excel and Structured Files
Excel workbooks can include worksheets, hidden sheets, formulas, data validations, defined names, pivot tables, and linked data. Specify which text fields should be translated and which cells must remain unchanged. Never assume that every visible value is text or that replacing words will preserve formulas.
For structured files such as JSON, YAML, XML, CSV, XLIFF, and software resource formats, define translatable fields, encoding, variable placeholders, HTML tags, and schema requirements. Provide a sample round-trip file if a system will import translated data automatically.
| Element | What to clarify |
|---|---|
| Text cells | Which ranges are translatable and which values are protected |
| Formulas and references | What must stay unchanged after translation |
| Sheet names and comments | Whether they are in scope |
| Variables and tags | How placeholders and string keys must be preserved |
Prepare PDF and Desktop Publishing Assets
An exported PDF may be useful for visual reference but harder to translate than the original Word, InDesign, Illustrator, or other editable source. Whenever possible, supply the editable source plus linked fonts and graphics permitted for use. For scanned PDFs, clarify OCR requirements and whether the client can supply original text.
Text embedded in diagrams and product screenshots needs separate identification. Teams should decide whether to translate image text, replace graphics, add captions, or leave original text in place. Layout reconstruction and multilingual typesetting should be scoped separately from pure translation.
Where available, provide both the editable source and the exported PDF reference. The PDF helps reviewers validate layout, while the source allows translators and layout specialists to work without recreating every graphical element.
For scanned or image-only documents, the team may need text extraction and additional layout work before translation. Identify those files early so the scope and turnaround can be estimated correctly.
Prepare Website and Software Exports
For website and software content, provide exported strings or structured content with context: stable IDs, screenshots, string descriptions, page location, placeholders, and character limits. Clarify whether URLs, metadata, alt text, forms, or email templates are included in the scope.
Keep source-language and target-language paths separated and identify which publishing system will receive the translated files. Technical QA should confirm that keys, markup, encoding, and variables survive export and reimport without changing the application behavior.
Useful Context for Structured Strings
- Stable content or string identifiers and the current source version
- Screenshots or a reference environment showing where the text appears
- Variable and placeholder rules and character-length constraints
- Target locales, content exclusions, and test ownership
Document Languages, Files, Instructions, and Review Owners
A useful delivery brief should specify file list, source language, target locales, intended readers, subject matter, tone, format, timeline, approval contacts, security needs, and whether the translated files will be reviewed by internal specialists. Include the expected output format rather than assuming the provider will return the same file type.
After translation, check completeness, numbers, terminology, preserved formatting, functional links, file names, variable syntax, and layout. Have the organization’s specialist approve high-impact technical, legal, financial, or regulated content before distribution.
| Brief field | Required decision |
|---|---|
| Languages | Source language and each target locale or regional variant |
| Audience | User, customer, regulator, employee, or other intended reader |
| File scope | Exact files, excluded items, and protected data |
| Language assets | Approved glossary, style guide, TM or reference materials |
| Review | Named owner for questions, linguistic review, and final approval |
| Delivery | Formats, deadlines, update cadence, and acceptance checks |
Example: Preparing a Technical Manual
For a product manual, supply the editable Word or InDesign source, an exported reference PDF, approved glossary, image assets and labeling instructions, target-language list, destination markets, and the person responsible for technical approval. Confirm whether the finished deliverable is an editable publication file, a final PDF, or both.
A complete package should let the translation team identify the editable source, understand where the text appears, preserve technical identifiers, resolve terminology questions, and validate the final PDF or publishing output. An exported PDF alone often omits the editable structure needed for reliable updates.
Final File-Preparation Checklist
- Confirm the final source version and review ownership.
- Identify translatable and excluded material.
- Supply editable source files and reference exports.
- Include glossary, screenshots, style guidance and variable rules.
- Verify file manifests, links, images, and handoff dates.
- Specify target locales and required deliverable formats.
Frequently Asked Questions
Should I send the PDF or the editable source?
Send the editable original when available, plus a reference PDF if layout must be preserved. A PDF alone can require additional extraction or rebuilding.
Can formulas and spreadsheet structure be preserved?
The project should identify translatable ranges and protected formulas, numbers, identifiers, and workbook functions. Verify the actual workbook after translation.
How should tracked changes and comments be handled?
Resolve or clearly scope tracked changes and comments before translation, and identify the approved source version.
What information belongs in a translation brief?
Audience, target locales, document purpose, file formats, terminology, style, deadlines, source version, security needs, and approval owners.
Prepare Your Translation Project
Share the document formats, language requirements, reference files, and review needs so we can evaluate the appropriate workflow.