Translating a document is not the same as rebuilding it successfully for print or PDF. A target-language text may be accurate in a translation editor and still fail in production because headings overflow, footnotes collide, tables break, a font lacks glyphs, right-to-left paragraphs reorder badly, captions detach from figures, line breaks change meaning, or a final PDF cannot be searched, copied or read accessibly.
Searches for multilingual desktop publishing, DTP localization, translated PDF layout, localization typesetting, InDesign translation workflow, multilingual typography, right-to-left PDF, translated brochure layout, complex script typesetting and post-translation DTP QA all point to a production job that begins after the words have been translated. The target document must still function as a designed artifact.
This guide explains how to rebuild multilingual documents safely from translation through final PDF. It covers source packages, linked assets, fonts, styles, text expansion, line breaking, hyphenation, complex scripts, right-to-left composition, tables, charts, footnotes, page references, text in images, indexes, cross-references, accessibility, PDF export, preflight, proofreading and final sign-off. The goal is not pixel-for-pixel imitation of the source. The goal is faithful meaning, readable typography, stable hierarchy and a document that works in its target language.
This article belongs inside eduKateSG’s Master Art of Translation architecture. It complements the existing owners for file preparation, right-to-left localization, Unicode integrity, regression testing and release gating. This page owns multilingual document composition after translation has entered a page-layout environment.
Quick answer: preserve the design system, not the source-language line breaks
Good multilingual DTP keeps the document’s hierarchy, visual logic, brand system and information relationships while allowing the target language to occupy space naturally. The source page is a design reference, not a cage. Professional layout work uses flexible paragraph and character styles, script-capable fonts, locale-aware composition, controlled reflow, page-reference checks and final proofreading in the exported document.
- Collect: package source files, fonts, links and reference PDFs.
- Protect: preserve styles, tags, anchors and non-translatable structure.
- Compose: use fonts and text engines that support the target script.
- Reflow: let translated text expand or contract without distorting hierarchy.
- Inspect: tables, figures, footnotes, references and page-dependent content.
- Export: create the correct PDF variant with embedded fonts and accessibility where required.
- Proof: review the final PDF, not merely the translation file or InDesign story.
1. Start from the complete source package
A PDF alone is often insufficient for professional localization. The production team may need the original InDesign, Illustrator, PowerPoint or other source document; linked images; fonts; logos; charts; style references; color profiles; and any data files used to generate tables or figures.
Before translation begins, package the document so links are not missing and the correct source version is identifiable. Record whether images contain editable text, whether fonts can legally and technically be used for target scripts, and whether the document depends on plugins or proprietary assets.
If editable source cannot be obtained, the workflow changes. Recreating layout from PDF may be possible, but it should be treated as reconstruction rather than ordinary translation. The estimate, QA plan and expectations should reflect that extra work.
2. Use the source PDF as visual evidence, not as the only source of truth
A reference PDF is valuable because it shows intended hierarchy, page breaks, object placement and final appearance. But it may not reveal the structure underneath. A heading can look like bold body text while actually using a heading style. A footnote marker can be a live reference or manually typed text.
Work from editable structure where possible, then compare against the approved source PDF. The editable file tells you how the document is built; the PDF tells you how the approved source looked. Both are useful and neither should automatically override a newer authoritative content revision.
Keep source-version identity throughout the job. A beautifully typeset target based on an obsolete source is still wrong.
3. Preserve paragraph and character styles
Styles are the document’s grammar. They encode heading levels, body text, lists, captions, quotations, table cells, warnings and emphasis. Manual formatting may look acceptable on one page but becomes impossible to maintain across a long multilingual document.
Keep semantic styles intact through translation and DTP. Adapt style definitions globally for target-language typography instead of fixing each paragraph by hand. A target script may need different fonts, leading, hyphenation or justification, but the relationship between heading levels should remain coherent.
When local production requires new styles, name them by function and document why they exist. Avoid creating “Heading 2 Arabic Fix Final” as a permanent style system. Temporary hacks multiply quickly.
4. Choose fonts for the actual script, not brand appearance alone
A Latin brand font may not contain Arabic, Devanagari, Thai, CJK or other required glyphs. Even when a font technically supports the characters, shaping, mark placement, weight range and readability may be inadequate.
Test the complete character repertoire used by the target language, including diacritics, combining marks, punctuation, numerals and specialist symbols. Check all weights and italics used in the document. One font weight can have good coverage while another silently falls back to a mismatched system font.
Where the brand font cannot support the target script, use an approved companion font with comparable visual role rather than forcing unsupported characters. The design system should define script pairings intentionally.
5. Use a text composer that understands the script
Complex scripts require more than glyph availability. Letter shaping, joining, ligatures, reordering, contextual forms, mark positioning and line breaking can depend on the text engine. Adobe’s World-Ready Composer, for example, is designed to support multilingual composition across Middle Eastern, South Asian and Southeast Asian scripts, including bidirectional text and language-specific typographic behavior.
Do not treat script rendering as a visual afterthought. A correct Unicode string can display incorrectly if the composition engine or language setting is wrong. Set paragraph language and composer appropriately, then verify with native-script examples.
When moving files between layout applications, recheck composition. Different engines can produce different line breaks and shaping even with the same text and font.
6. Expect text expansion and contraction
Translation changes length unpredictably. Short source labels can expand dramatically. Long English phrases can become shorter in another language. Compound words, script width and grammatical structure all affect line length.
Do not impose one universal expansion percentage as if it were a law. Instead, design text frames and page structures that tolerate realistic variation. Let frames grow where possible, adjust column widths carefully, use alternate approved wording only when linguistically justified, and re-balance pages rather than crushing target text.
When a document has a fixed page count because of printing signatures, regulatory form constraints or manufacturing requirements, the limitation must be known early. Translation and design may need coordinated decisions rather than emergency font reduction at the end.
7. Never preserve source line breaks blindly
Manual line breaks in titles, slogans and captions often encode one source-language rhythm. The same break can split a target-language phrase at an unnatural grammatical boundary or leave one short word stranded on a line.
Remove unnecessary hard returns before translation or allow DTP specialists to recompose them after translation. Preserve deliberate semantic breaks only when they still make sense. Target-language line breaking should respect grammar, readability and script conventions.
Poetry, advertising and highly designed display copy may require closer editorial collaboration because lineation itself can carry meaning. In ordinary technical and educational documents, readability usually outranks visual mimicry.
8. Review hyphenation language by language
Automatic hyphenation depends on language dictionaries and typographic convention. Wrong language settings can create illegal breaks. Some scripts or document types may avoid hyphenation entirely; others use it extensively.
Assign the correct language to text and review high-visibility hyphenation manually. Avoid using discretionary hyphens from the source as a universal layout tool. They can become visible or create poor breaks after translation.
For technical terms, names and URLs, define exception rules where needed. A line-break fix should not change the underlying spelling or identifier.
9. Recompose right-to-left pages by meaning
RTL localization can require mirrored page relationships, but not everything should flip. Reading sequence, columns, navigation arrows and callout placement may mirror, while logos, charts, maps, physical diagrams or media controls may retain their original orientation.
Use correct paragraph direction and bidirectional composition rather than manually reversing text. Test inline Latin names, numbers, URLs and punctuation. The existing RTL and bidirectional localization owner explains the underlying text behaviour; DTP adds page-level composition around it.
Review reading order both visually and logically. An RTL page can look plausible yet export a confusing copy order or tagged-PDF reading sequence.
10. Treat tables as miniature layouts
Tables often fail before body paragraphs because cells have fixed widths and short source labels. Translation can force row growth, awkward wrapping, overlapping footnotes or unreadable column widths.
Prioritize meaning over preserving identical row height. Widen important columns, reduce unnecessary padding, rotate headers only when appropriate, move dense notes outside the table, or redesign the table when the target language cannot fit responsibly.
Verify numeric alignment, decimal separators, units and column association. A visual reflow must not detach a value from its heading.
11. Rebuild charts and figures with translated labels carefully
Charts can contain editable text, rasterized text, legends, data labels, axis titles and notes. Determine whether the text lives in the source design file, the charting application, a spreadsheet or an image. Translate the authoritative layer rather than painting over a screenshot unless reconstruction is the only option.
Do not change data to make labels fit. Preserve units, scale, color meaning and series identity. If translated legend labels become longer, redesign the legend or allocate more space.
For scientific and financial graphics, separate language edits from data edits so the review trail remains clear.
12. Translate text inside images only when the image itself is localized
Images containing embedded source-language text create hidden localization work. Product screenshots, diagrams, infographics and photographs of signs may all contain words the main translation workflow never sees.
Inventory these assets before DTP. Where editable source artwork exists, create locale-specific versions and keep the original asset ID or relation so the CMS or document package can select the correct file. Where text is incidental and should remain as part of the photograph, provide translated captions or explanatory text if the reader needs the meaning.
Avoid placing translated text over an image in a way that hides important visual evidence or creates accessibility problems.
13. Keep captions attached to the correct figures
Text expansion can move figures and captions across pages. Anchored objects may detach, manual numbering may become wrong and “see figure above” can become false after reflow.
Use live cross-references and automatic numbering where the source application supports them. After target reflow, verify every caption, table number and in-text reference. Replace direction-dependent wording such as “above” or “on the opposite page” if the new layout changes position.
Do not rely on source page numbers after translation. Pagination is a target artifact.
14. Recheck footnotes and endnotes after reflow
Footnotes can create severe page-balance problems because target text expands in both the body and the note. A note can split awkwardly, push paragraphs to the next page or create an isolated heading.
Keep footnote markers live and linked where possible. Review numbering, separator rules, note direction in RTL documents and whether a note belongs to the same page after reflow. In long documents, endnotes may have their own index or cross-reference requirements.
Never shorten substantive note content merely to preserve the source page. Adjust layout first.
15. Rebuild indexes from target-language content
An index is not just a translated list of source terms and page numbers. Target terminology can sort differently, one source entry can map to several target terms, and all page references change after reflow.
Preserve index markers or rebuild them in the target document, then regenerate the index after pagination is final. Use locale-appropriate collation rather than source-language alphabetical order.
Review cross-references such as “see” and “see also” in the target language. An index is a navigation system and needs linguistic QA, not just mechanical regeneration.
16. Check running headers, folios and section titles
Running headers can pull text from section headings automatically or contain manually maintained labels. A translated section title may be too long for the header, and a mirrored book may move page numbers or margin elements.
Use target-specific running-head styles where necessary and verify odd/even pages, chapter openers, blank pages and landscape sections. Do not reduce a long header to illegible size; create an approved short running title if the publication design supports it.
Page furniture should be reviewed on the exported PDF because master-page overrides can behave differently from normal text stories.
17. Preserve mathematical and scientific notation
Equations, chemical formulas, units, variable names and symbols may coexist with translated prose. Do not convert scientific notation into ordinary language merely to make the page look consistent. Preserve established notation and localize explanatory labels around it.
Check decimal separators, minus signs, multiplication symbols, superscripts, subscripts and fonts. Math rendered as embedded artwork can fail font substitution even when body text is correct.
Where equations are numbered, regenerate or verify cross-references after pagination. A translation layout change should never alter the mathematical relationship being explained.
18. Manage widows, orphans and bad breaks without rewriting meaning
Professional typesetting pays attention to isolated lines, headings stranded at page bottoms, short final lines and visually disruptive breaks. The temptation is to edit translation until the page fits. That can become dangerous if layout convenience starts changing meaning.
Use typographic controls first: keep options, tracking within approved bounds, frame adjustments, paragraph spacing, column balancing and page reflow. Only request a linguistic alternative when the translator can produce an equally accurate and natural form.
Document significant editorial shortening. The target text should not become a mysterious layout variant outside the translation record.
19. Do not solve overflow by shrinking everything
Reducing font size across an entire target document is a common emergency response to expansion. It damages hierarchy, accessibility and brand consistency, and it unfairly treats target-language readers as if their language deserves smaller type.
Fix the actual layout constraint. Increase frame capacity, adjust grid decisions, allow extra pages, change image crop or spacing, or create a target-specific layout where the publication permits it. Use smaller type only when the design system and readability standards support the change.
Compare print size physically. A font that looks acceptable at 100% zoom on a monitor may be too small on paper.
20. Build target-language preflight profiles
Preflight can catch missing fonts, missing links, overset text, low-resolution images, incorrect color spaces, hidden objects and other mechanical problems before export. Multilingual production should add target-language concerns such as unsupported glyphs or unapproved font substitutions where tooling permits.
Run preflight before linguistic proof so reviewers are not spending time on pages that still contain obvious production defects. Run it again before final export because late corrections can introduce new problems.
Automation should narrow human attention, not replace proofreading. Preflight knows that text is overset; it does not know whether a translated heading says the wrong thing.
21. Export PDF with the delivery purpose in mind
A print-ready PDF, screen-reading PDF, archive PDF and downloadable marketing PDF can have different requirements. Define target standard, bleed, crop marks, image resolution, color conversion, font embedding, transparency and tagging before export.
For digital documents, selectable text, bookmarks, links and accessibility tags may be essential. A workflow that converts translated pages to raster images can preserve appearance while destroying search, copy, text extraction and screen-reader access.
Keep export presets versioned and owned. A correct layout can still fail when the final PDF uses the wrong preset.
22. Check tagged-PDF reading order where accessibility matters
Visual reading order and assistive-technology reading order are not automatically identical. Multi-column layouts, sidebars, captions, footnotes and RTL content can create confusing tag sequences.
Where accessible PDF is required, inspect language metadata, heading structure, alternate text, table tagging, link descriptions and logical reading order. Test with assistive technology on representative pages.
Translation can alter reading order because frames reflow or move. Accessibility therefore belongs in target DTP QA, not only in source-document certification.
23. Proof the exported PDF, not only the layout file
The final export can introduce problems absent from the working document: font substitution, transparency issues, broken links, incorrect bookmarks, missing characters or unexpected image downsampling. The deliverable itself must be reviewed.
Linguistic proofreading should inspect target text in final context, including page breaks, captions, headings and cross-references. Production proofreading should inspect alignment, spacing, fonts, images, color, trim and interactive elements.
Use a change-controlled correction loop. Late PDF comments should feed back into the editable source, not be patched only in an untracked PDF copy.
24. Archive the editable target package
Final PDF is a delivery artifact, not a complete localization asset. Future revisions are far easier when the organization preserves the editable target layout, links, fonts or licensed-font references, final bilingual translation assets and source-version manifest.
Package the target document according to license and retention rules. Record application version, plugin dependencies and export preset. If fonts cannot legally be redistributed, document how an authorized user can obtain or activate them.
A recoverable target package turns next year’s update into a revision. Without it, every edition can become a reconstruction project.
A repeatable multilingual DTP workflow
- Confirm the authoritative source version and collect editable files, fonts and links.
- Preflight the source package before translation.
- Identify embedded text, complex scripts and fixed-page constraints.
- Export or prepare translation content without breaking styles, tags and anchors.
- Import the approved translation into the layout environment.
- Assign target-language fonts, language settings and appropriate composers.
- Reflow text while preserving hierarchy and semantic relationships.
- Repair tables, charts, captions, footnotes and cross-references.
- Regenerate indexes and page-dependent references after pagination stabilizes.
- Run target-language preflight and overset checks.
- Export the required PDF variant with correct fonts and settings.
- Proof the final PDF linguistically and visually.
- Verify accessibility and reading order where required.
- Apply corrections in the editable source, then re-export.
- Archive the final editable target package with provenance.
Worked scenarios
Scenario 1: German brochure expands beyond the source grid
A six-page English brochure becomes crowded in German. The first impulse is to reduce type from 10 pt to 8.5 pt. Instead, the DTP team removes unnecessary fixed-height frames, slightly reduces decorative spacing, lets one feature panel grow and adds a seventh page under the print plan. The target remains readable and the translation does not need artificial shortening.
Scenario 2: Arabic annual report has mixed-direction financial codes
The Arabic prose is correct, but account codes and Latin abbreviations move beside the wrong punctuation. Manual reversing fixes one line and breaks another. The team enables proper RTL composition and directional isolation, then checks logical copy order in the exported PDF. The source strings remain in normal logical order.
Scenario 3: Japanese PDF loses characters only in bold headings
Body text is correct, but the bold font weight lacks required glyph coverage. The PDF shows boxes in several headings. The team confirms the Unicode text is intact, replaces the unsupported bold face with an approved companion font and adds a script canary to preflight. Translation is not changed because the failure belongs to typography.
Scenario 4: translated table destroys numeric association
A French technical table has longer headers. Narrow columns wrap into four lines, making users misread which values belong to which category. Instead of shrinking the entire table, the team widens key columns, moves a long explanatory note below the table and keeps numeric alignment consistent. Data relationships remain clear.
Scenario 5: index page numbers are translated manually
The source book contains a manually typed index. After translation, pagination changes but the old page numbers remain. The repair rebuilds the index from target markers and target-language collation. Future editions can regenerate rather than manually repair hundreds of references.
Scenario 6: accessible English PDF becomes inaccessible after localization
The source document has good tags, but target reflow moves frames and inserts translated sidebars. The exported Spanish PDF reads captions before headings and misses language metadata on several pages. Target QA includes tagged-PDF reading order and language properties, restoring accessibility instead of assuming source compliance carried over automatically.
Twenty DTP checks for translated documents
- All linked assets are present.
- The target is based on the correct source revision.
- Fonts support every required script and weight.
- Paragraph language settings are correct.
- Complex-script composition is enabled where needed.
- No target text is overset or hidden.
- Hard line breaks remain only where semantically justified.
- Hyphenation uses the target language.
- RTL direction and inline LTR tokens render correctly.
- Tables preserve value-to-heading relationships.
- Charts preserve data, units and legend identity.
- Embedded image text is translated or intentionally retained.
- Captions remain attached to the correct figures.
- Footnote numbers and notes remain connected.
- Cross-references and page-dependent wording are correct.
- Indexes are regenerated using target-language entries and collation.
- Mathematical and scientific notation is intact.
- PDF fonts are embedded as required.
- Accessible reading order is verified where required.
- The final exported PDF receives linguistic and visual proof.
Release checklist
- The source package is complete and versioned.
- Paragraph and character styles remain coherent.
- Target fonts and script composition are approved.
- Text expansion has been solved through layout before linguistic compromise.
- Line breaking and hyphenation are target-language appropriate.
- RTL pages are reviewed for both visual and logical order.
- Tables, charts and embedded text are checked.
- Captions, notes and cross-references are updated after reflow.
- Indexes and page references are regenerated after pagination.
- Preflight reports no missing links, fonts or overset text.
- The correct PDF export preset is used.
- Search, copy and text extraction work where expected.
- Accessibility requirements are verified.
- Final proofing occurs in the exported PDF.
- An editable target package is archived for future revisions.
Frequently asked questions
What is multilingual DTP?
It is the production work that recomposes translated content in page-layout or design software so typography, hierarchy, figures, tables, scripts and final output work correctly in the target language.
Why can’t a translated PDF simply keep the same line breaks?
Languages differ in word length, grammar, script and line-breaking rules. Preserving source line breaks can create unnatural or misleading target text.
Should font size be reduced when translation expands?
Not as the default solution. First fix layout flexibility, spacing, frame capacity and page structure. Font reduction must remain readable and consistent with the approved design system.
What is Adobe World-Ready Composer?
It is InDesign’s multilingual composition engine for complex scripts, including bidirectional text and script-specific shaping, spacing and line behavior across Middle Eastern, South Asian and Southeast Asian languages.
Should an index be translated or rebuilt?
Usually both linguistic and structural work are needed. Target entries need translation, page references must be regenerated after target pagination and sorting should follow target-language collation.
Why proof the final PDF instead of only the InDesign file?
Export can introduce font, link, image, tagging or transparency defects. The deliverable users receive is the final evidence of quality.
Can a PDF be localized without editable source?
Sometimes, but it becomes a reconstruction workflow. Expect additional layout recreation, asset extraction and QA, and preserve the limitation in the project estimate and provenance.
What should be archived after delivery?
The final PDF plus the editable target source, linked assets, version information, bilingual translation assets, font/license notes and export settings needed to reproduce the document.
Selected references
- Adobe: World-Ready Composer overview — multilingual text composition and complex-script behavior in InDesign, updated August 18, 2026.
- Adobe: Set up World-Ready composers for Arabic and Hebrew.
- W3C Internationalization — international text, language and script guidance.
- eduKateSG: Localize Right-to-Left and Bidirectional Text.
Conclusion: target typography is part of translation quality
A translated document is not finished when every source sentence has a target sentence. It is finished when the reader can move through the target artifact without typography, page structure or production defects interfering with meaning. That requires linguistic and visual systems to agree.
Professional multilingual DTP therefore protects hierarchy rather than line-for-line appearance, uses script-capable fonts and composers, rebuilds page-dependent references after reflow, validates tables and figures, proves the final PDF and archives an editable target package. The source design remains respected, but the target language is allowed to become a real document rather than a squeezed copy of somebody else’s page geometry.