Did you know that an InDesign translation can be linguistically complete while an entire paragraph is invisible in the exported PDF? People searching for Adobe InDesign IDML translation, translating INDD files with CAT tools, or checking translated InDesign layouts are facing a production problem, not merely a vocabulary problem. The target words may have been imported correctly but overflowed a text frame, used a font without the necessary glyphs, become disconnected from a linked story or escaped the export through a hidden layer.
This guide focuses on InDesign IDML translation QA and localized production handoff. One dominant reader job controls the article: exchange editable InDesign content for translation and return a complete, visually checked document without destroying stories, links, styles, page logic or print requirements. It does not promise a universal one-click translator for every INDD file, and it does not replace a broad tutorial on translating PDFs. A PDF is an output artifact; the job here is to protect the editable source and prove that the output contains what readers need.
The mechanism is easiest to understand as a chain: an InDesign document contains text stories and formatting instructions, linked graphics, layout geometry and export settings. A controlled handoff exposes approved translatable content while preserving structural references. Translated content is reassembled into a document, composed with language-appropriate typography, reviewed page by page, preflighted, packaged and exported. Each step has its own failure mode. The method below makes the checkpoints visible so that teams can repair the right layer instead of blindly shortening every sentence.
Quick answer: test the text path and the final page
Begin with an untouched copy of the approved INDD source. In InDesign, inspect missing links, fonts, overset text, hidden content, conditional text and the intended print or digital export profile. Package relevant assets where permitted and create an IDML copy if the translation workflow supports it. Supply translators with a controlled export or compatible localization exchange rather than asking them to edit page geometry. Preserve stories, paragraph styles, inline objects and protected identifiers. Reassemble the approved target in InDesign, then inspect every page and run preflight before exporting the final PDF.
The final test has two parts. First, content integrity: every required source story and segment has a target counterpart, protected facts and links remain accurate, and nothing vanished because it was hidden, overflowed or mis-mapped. Second, rendering integrity: the target text is readable at the intended size, uses appropriate glyphs and line breaks, stays within frames, and produces the correct page count, output colour settings and linked assets. A clean CAT-tool completion bar cannot establish either result alone.
Understand what an INDD file and IDML file do
An INDD document is InDesign’s editable project format, including text, styles, frames, graphics references and layout logic. IDML, the InDesign Markup Language format, is an interchange representation often used for compatibility and structured processing. Adobe documents IDML export and the option to include IDML when packaging files. An IDML file is not simply a Word document containing paragraphs; it represents a complex publication. Extracting strings without considering their associated structure can disconnect text from its formatting or reading order.
A translator may work through a CAT tool that understands a supported InDesign exchange workflow, or through editorial collaboration such as approved copy decks or InCopy-based processes. There is no universal guarantee that every plugin or converter preserves all special features. Test the chosen pipeline on a representative file before committing a large magazine or textbook. Save the original INDD, the exported interchange file, the returned file and the reconstructed final INDD as separate versioned artifacts. Identity and traceability matter as much here as they do in software localization.
Establish which edition is authoritative
Before handoff, freeze a defined source edition. Ask the editorial owner to approve copy, images, tables, captions, disclaimers, page size and the intended output. Record document filename, modification or revision reference, page count, locale and release purpose. If the same brochure exists in English, Chinese and Malay, decide which file is the source of truth for this translation cycle. Avoid translating from a PDF screenshot while the original INDD continues to change under a designer’s hands.
Late source changes can create a particularly expensive kind of rework. Imagine that a warranty paragraph is updated in the English file after the French translation is completed. The French layout may still pass preflight but contain the old promise. A versioned content map makes that difference detectable. Keep a change log with affected pages and stories, not just a message saying ‘minor edits’. Some changes alter meaning, some only affect punctuation or layout. Review effort should follow the semantic risk rather than forcing every target page to be rebuilt from scratch.
Inventory the document beyond ordinary body paragraphs
InDesign projects contain more than obvious text frames. Inventory headings, running headers, table cells, footnotes or endnotes as applicable, captions, labels inside diagrams, callouts, page furniture, buttons, hyperlinks, alt text, hidden layers, conditional text and text inside linked graphics. Identify master or parent-page elements that repeat. A translator who receives only visible body stories may complete every assigned segment while the title bar, safety icon and image labels remain in the source language.
Make an ownership map. Text that exists as editable InDesign type can enter an approved text exchange. Words embedded in a Photoshop or Illustrator asset may need a separate editable source and graphics review. Automatically generated page numbers should remain dynamic where possible. Brand names and legal marks may be intentional exceptions. A useful inventory captures element, page or component, source, translation owner and required target treatment. It also prevents duplicated effort when a shared parent-page title appears on many spreads but should be translated only once in its authoritative source.
Package the source without sharing unnecessary assets
Adobe’s packaging workflow can gather the InDesign file, linked graphics, eligible fonts and an output report, with options to include IDML and PDF. Use it to establish a reproducible handoff when the team needs the assets and has the rights to share them. Review preflight warnings before packaging. Missing graphics, inaccessible fonts and broken links are not language problems, but they can make a localized document impossible to verify. The package is a snapshot of production dependencies; it is not proof that every item should be sent to every translator.
Font licences and confidentiality still apply. A packaged font may not be transferable under its licence, and a client document may contain private pricing or unapproved illustrations. Give linguists the text and necessary visual context under appropriate permissions, while reserving full production assets for authorized layout specialists. Include a contact for missing resources, not a folder of unrelated project archives. If the target language requires a different font family, source packaging preserves the original but does not automatically provide legal, technically suitable target-language typefaces.
Decide how translation content will leave InDesign
Choose an interchange workflow compatible with the document and the team’s tools. Some CAT systems can extract strings from IDML while protecting structural tags; others use specialized InDesign plugins or editorial exports. A tagged-XML workflow is also possible for appropriately tagged InDesign content, but Adobe notes that exporting XML includes only tagged items. Selecting the wrong extraction path can silently omit text frames. Test content coverage on a small representative spread, then compare the extracted inventory with the source.
Define the return path before translation begins. Can the translated segments be imported back without losing styles, tables, text-variable behavior or anchored objects? Can the layout specialist open the returned document in the relevant InDesign version? Does the process preserve segment order and meaningful comments? If the answer is uncertain, conduct a round-trip test with pseudotranslation or a brief real sample. A translation workflow that extracts text easily but cannot reconstruct a usable document is not efficient; it has merely postponed the hardest work.
Protect inline structure without freezing the prose
InDesign stories may contain formatting runs, anchored objects, special characters, forced breaks, references and text variables. A CAT export may represent some of these as inline tags. Those tags can be essential to rebuilding the page, but their position in the target may need to move with the meaning. Do not ask translators to delete markup they do not recognize or to preserve English word order simply to keep tags in place. Provide visible tag protection and an escalation path for cases where reordering interacts with a graphic or reference.
Imagine the phrase ‘See Figure 3 before installing the part’ with the figure reference generated by the document system. In another language the reference may appear earlier in the sentence. The text must remain natural while the correct figure reference survives. A corrupted tag could make the reference disappear or display literal formatting syntax in the PDF. Validate tags structurally before import, then visually confirm the rendered references. Treat a parser’s success as necessary but not sufficient evidence of correct layout and reader navigation.
Translate at the level of meaning, not arbitrary text frames
Text frames are geometric containers; sentences can flow through threaded frames and across pages. Exporters may segment words according to formatting or story boundaries that do not match meaningful sentences. A translator needs sufficient context to understand pronouns, instructions, headings and relationships. Supply page previews and source screenshots, especially for isolated short labels, tables and text adjacent to graphics. Do not assume that a string in the extraction file tells its whole story.
For example, an isolated ‘Open’ next to a diagram might describe an open valve, a user instruction to open a cover, or an item status. A literal translation can be wrong in two of those contexts. Attach the text to the relevant page location, note whether it is a command or label, and provide a glossary for product parts. After import, check that the target still refers to the correct object. Good translation shortens the cycle of clarifications by making the visual context available early, not by forcing translators to guess quickly.
Plan for text expansion without mutilating meaning
Different languages require different amounts of space for the same meaning. A compact English heading can expand into a longer phrase in German; a Chinese sentence may use fewer visible characters but need different font metrics and line breaking. The amount varies with subject, grammar, font and layout, so treat percentage estimates as planning aids rather than guarantees. Do not promise that every language fits the English grid if the grid has no flexibility.
Before translation, locate the most constrained boxes: narrow tables, buttons, callouts over images and multi-column captions. Mark which components may grow and which must retain fixed dimensions. After import, use frame and paragraph-style adjustments before asking for abbreviation. Sometimes a legitimate shorter synonym is possible; sometimes the proper fix is to increase the frame height, adjust column width, move a callout or use an alternate layout. A target that fits only because it drops a medication warning or technical qualifier has failed its purpose.
Treat overset text as a content-integrity defect
Overset text occurs when a story contains more text than its frames can display. InDesign may show an overset indicator, but the final PDF will not magically include the hidden overflow. This is one of the most important localization QA checks. A translated paragraph can exist in the document, be approved by a reviewer, and still be absent from the file a customer reads. Check overset indicators and preflight results after importing target text, after significant reflow changes and again before export.
Do not resolve overset by deleting the end of the paragraph without checking its function. Determine whether the frame can expand, the story can flow to another frame, the layout can use an additional page or the copy can be rewritten with approval. Test the effect of changing leading, tracking or font size on readability. A tighter setting may solve a minor overflow but create an unreadable legal note. Record every substantive copy change and route it back to the language reviewer. Layout adaptation and translation approval must meet in the final rendered artifact.
Understand threaded stories and reading sequence
Threaded text frames allow one story to continue across multiple containers and pages. A designer can make a target paragraph fit by changing a thread, but an incorrect connection can skip a column or send content to the wrong page. The PDF may still look superficially tidy. Follow the story from start to finish, checking section order, paragraph transitions, page breaks and captions. Consider what a reader will actually read, not just whether each frame contains words.
On a textbook page, a worked example might begin beside a diagram and continue into the next column. If the translated explanation expands, the continuation could push a safety note onto a later page, separating it from the relevant exercise. Decide whether to redesign the example rather than relying on automatic flow. Use story-oriented review alongside page-oriented review. The page inspection finds visual errors; the story inspection finds missing or reordered meaning. Both are needed because InDesign documents simultaneously encode reading sequences and spatial presentation.
Use styles as semantic tools, not accidental decoration
Paragraph and character styles can carry hierarchy, emphasis, spacing, language-related hyphenation settings and export semantics. Preserve their intended relationships through the translation workflow. A heading should remain a heading, a warning should remain identifiable as a warning, and a caption should not become ordinary body text because a tag was lost. Avoid local manual formatting changes on dozens of target paragraphs when a well-designed style can solve the issue consistently.
Check the target language’s typography requirements and use language-appropriate style variants where necessary. A font that looks similar to the source may lack script coverage, weights or punctuation behavior. InDesign’s compositor may treat words and breaks differently across languages. Test at the final size and resolution. A designer should be able to explain why a particular style changed and whether it affects every occurrence. Small, systematic style adjustments are more maintainable than 100 individual emergency fixes before a print deadline.
Verify fonts and glyph coverage in the real target script
A font family that supports English does not necessarily contain the characters, combining marks or shaping behavior required for Arabic, Hindi, Thai or other scripts. Missing characters may appear as blank boxes, substituted glyphs or inconsistent fallback. A target page can look acceptable at a glance while displaying a broken accent or diacritic that changes meaning. Test the exact approved typeface, font version and output method with representative target-language sentences, numbers and punctuation.
Do not convert all text to outlines simply to hide a missing-font problem. Outlining can damage accessibility, searchability and editability, and it makes later corrections difficult. Find a legitimate font and composition approach compatible with the script. Check bold, italic, numerals, superscripts and special symbols, not only ordinary letters. If a project uses brand typefaces with narrow script coverage, document authorized fallback families and ensure their visual hierarchy remains clear. Typography is part of communicating the translation accurately, not an afterthought.
Address right-to-left and mixed-direction content deliberately
Arabic and Hebrew layouts require more than translating the words. Text direction, alignment, punctuation, number runs, captions and relationships between icons and text may need attention. Mixed-direction content such as a Latin model number inside an Arabic instruction can create visually confusing order if the story is not composed correctly. Review the actual InDesign capabilities and language-specific settings of the installation in use, and test representative content rather than assuming that changing paragraph alignment is sufficient.
Do not mirror every object automatically. Photographs, logos, numeric charts and physical product diagrams can have intrinsic direction that should remain unchanged. A ‘turn clockwise’ instruction must describe the real direction of movement even if layout flow changes. Check arrows, sequence steps and page navigation as a reader would. Verify that exported PDF text remains selectable and intelligible and that accessibility reading order is not contradicted by the visual arrangement. This is an editorial-design decision with technical consequences, not a simple word substitution.
Keep tables numerically and semantically intact
Tables combine text, labels, measurements and relationships. A translated header may expand, making columns too narrow and forcing data onto unexpected lines. A number may be carried with an incorrect unit, a decimal separator may be changed inconsistently, or a footnote marker may become detached from the result it qualifies. Test the table as a whole. Compare row and column identities, totals, units, legends and notes against the approved source data. Translation should clarify the table, not recompute its quantities without authorization.
Take an equipment specification table with a maximum load of 25 kg and operating range of 5–35°C. The target may need different word order and typographic spacing, but 25 must not become 2.5 and the operating interval must not reverse. If an imported decimal separator is converted by spreadsheet software, resolve it before typesetting. Check cell overflow, border alignment and wrapped headings. When a table has dense measurements, a qualified technical reviewer is essential; a good-looking page is not proof that every figure or qualifier survived.
Review images, captions and diagrams together
A caption’s meaning depends on the picture it describes. If a diagram is replaced, renumbered or moved during reflow, a perfectly translated caption can now point to the wrong part. Maintain a stable reference to each visual asset and verify that every callout remains attached to the correct object. Inspect text baked into placed images separately from InDesign text frames. Some graphics may need localization in their original editable application rather than being retouched destructively inside a PDF.
For a consumer safety leaflet, imagine a red arrow labeled ‘Release latch’ near a drawing. The Arabic label is translated, but the arrow now points to the locking tab because the diagram was mirrored without checking physical operation. That is a serious failure even if the text and icon both render cleanly. Compare diagram semantics with actual product instructions. Use screenshots and expert review for high-risk visuals. Never assume that the visual side of translation is merely cosmetic because the translator worked on text only.
Keep generated page numbers and running text functional
Publications often use text variables or other mechanisms for page numbers, section names, dates and running headers. Adobe documents that text variables update from document context. A translator should not replace an automatic page number with a literal numeral or make a dynamic running title into an unmaintained copied phrase. Once the target text changes length and pages reflow, hard-coded numbers become wrong. Identify generated content before export and preserve its role through reconstruction.
After target layout changes, inspect the table of contents if present, page references, cross-references and running headers. A heading that moves from page 14 to page 15 must not leave a translated instruction saying ‘See page 14’ merely because the reference was plain text. Use live references where the publication workflow supports them, otherwise run a deliberate manual verification. The correct page count is not merely the same as the English source; it is the count that the approved target layout actually needs while preserving navigational correctness.
Check hyperlinks and destinations for digital exports
Digital brochures and accessible PDFs may contain live links, bookmarks, buttons and cross-document references. Translating the visible anchor text is separate from verifying where the link goes. An English URL might remain the correct canonical resource; a localized destination may exist; or the link may need a redirect approved by the site owner. Do not translate a path segment by guesswork. Check that every important link in the exported PDF works in a clean viewing environment.
Take a parent guide with a button labeled ‘Register here’. If the English target goes to an outdated form, a beautiful Chinese translation merely sends more users to the wrong destination. Confirm the intended destination and any language preference on that page. Check footnotes with URLs, QR codes embedded as images and links attached to diagrams. Ensure that visible and accessible link names describe the action accurately. A link can be technically clickable yet semantically misleading if the translated label promises a different resource than the destination provides.
Use preflight as a gate, not an editorial substitute
InDesign’s preflight facilities can identify classes of technical output problems, including missing resources and overset text when the profile is configured accordingly. Adobe recommends addressing preflight issues before packaging. A clear report reduces the chance that a localized document contains a missing font or broken graphic. But preflight cannot decide whether the translated caution is factually equivalent or whether a diagram’s arrow points to the right component. Give it a defined technical role rather than pretending it is a universal quality score.
Create an appropriate profile for the output: print-ready PDF, digital accessible PDF or another production target. Document what the profile checks and which issues remain manual. Run it on the original source to establish a baseline, then after target reconstruction and immediately before export. Unexpected new warnings deserve investigation even when the PDF seems visually normal. Record accepted exceptions with reasons. Never approve an overset warning because ‘the rest is probably just whitespace’ without inspecting the hidden content.
Confirm the PDF represents the final editable document
A layout reviewer may inspect one PDF while the printer receives a different export. Establish a release identity linking the approved InDesign file, exported PDF, output preset and timestamp. After export, open the PDF as a reader and check title page, last page, critical instructions, contents, embedded fonts where applicable, link behaviour and the actual page count. Compare against the final INDD state rather than relying on a previous proof. Re-export after every substantive change, even when only a punctuation mark was altered near a tightly composed line.
For print, assess intended trim, bleed, image resolution and colour handling with the production team. For digital distribution, text selection, bookmarks, links, reading order and alternate text may matter more. One file can serve both purposes only if it genuinely meets both sets of requirements. Translation QA should hand over evidence that the published artifact is the one examined, not simply that someone once ran preflight on a work-in-progress document.
A worked example: a multilingual school science booklet
A school publisher produces a 24-page English science booklet with diagrams, experiment instructions, tables and several boxed safety notes. It needs a Chinese edition. The source is an INDD document assembled from multiple linked illustration files. A localization vendor requests IDML. The designer exports it, the vendor returns a translated version, and the first reconstructed proof looks mostly attractive. Yet page 11 has a missing instruction, page 15 displays boxes instead of some Chinese characters, and the contents page still points to the English page numbers.
Start with page 11. The translator confirms that the safety instruction exists in the target text. Inspect the story thread and frame. The missing sentence is overset because the target paragraph expanded beyond the available column. It is not a translation omission, so retranslation will not restore visibility. Adjust the relevant frame layout or continuation while protecting the relationship between the caution and the experiment diagram. Re-run overset detection and read the reconstructed story in order. Preserve the safety instruction in full, not an abbreviated approximation.
Page 15 has a different cause. The original body font lacks glyphs required by the Chinese target. Replacing missing characters with screenshots would make the page difficult to edit and possibly inaccessible. Select an approved typeface with appropriate coverage, test weight variants and punctuation, and review line breaks at the final size. The result may require adjusting paragraph styles rather than patching individual lines. Record the font substitution as a target-edition design decision for future booklets.
The table of contents provides the third diagnosis. The translated stories changed page flow, so sections no longer start where English did. A literal translation of ‘Page 8’ cannot remain correct if the section now begins on page 9. Rebuild or verify page references through the publication’s supported methods, then check every link in the digital proof. Finally compare the science procedures, labels and measurements across the target pages; an aesthetically polished booklet still needs accurate diagrams and data. The release report lists one overflow fix, one font coverage fix and one reference update. None required rewriting the Chinese prose from scratch.
Failure mode: a CAT tool says 100% complete, but text is absent
First verify whether the absent phrase was included in the translation exchange. Compare the source inventory with extracted segments, including hidden or conditional content where approved. If the phrase is present in the returned data, inspect whether reconstruction placed it into the right story and whether overset, conditional visibility or layer settings hide it. If the phrase never entered the export, the extraction pipeline needs correction or a separate translation route for that element. The tool’s completion percentage applies only to its own extracted segment set.
Do not paste missing text at random positions in the final page. That can create duplicated content, break flow or detach instructions from figures. Trace the source element, target segment and reconstructed location as a single identity chain. Record what stage lost visibility. Once the pipeline is repaired, rerun extraction coverage for other pages of the same type. A missing caption on one page is a warning that other captions may share the same unsupported structure.
Failure mode: the returned IDML opens differently from the source
Version differences, unsupported features, converter behavior or damaged structure can produce unexpected changes during an IDML round trip. Compare a controlled no-translation round-trip first: export IDML from the approved source, reopen it in the intended InDesign installation and inspect representative complex features. If the page changes before target words are added, the translation cannot be blamed. Adobe’s release notes and troubleshooting guidance discuss IDML-specific behaviour, including conversion and document-recovery cases.
Use the actual target edition of InDesign for acceptance testing. Verify parent pages, conditional text, anchored objects, paragraph styles, cross-references and links. Keep the untouched INDD available for comparison. When a converter cannot preserve a particular object reliably, agree on a specialized editorial handoff rather than continuing with undocumented manual fixes. The objective is to maintain the publication, not to make one IDML file look valid at the expense of silent omissions elsewhere.
Failure mode: someone ‘fixes’ overflow by shrinking everything
A global font-size reduction may suppress overset warnings but make the localized booklet unpleasant or inaccessible. Examine the layout cause first. Is one heading unusually long? Has a narrow table cell inherited English dimensions? Did a required font change alter metrics? Could a caption or callout move while preserving reading order? Solve the constrained component rather than punishing the entire document. Use the smallest structural change that preserves the reader’s access to full information.
For a tightly controlled brand layout, the designer may be tempted to request shorter sentences in every language. Ask whether approved alternative wording can preserve the complete action and conditions. A sentence such as ‘Do not operate while the cover is removed’ must not become merely ‘Caution’. If shortening is accepted, send the change for linguistic and domain review, then test again in final context. The success condition is legibility and equivalence, not visual resemblance to every English line break.
Build a page-by-page proofing method
Reviewers need a manageable route through the document. Begin with automated technical checks and a completeness comparison. Then inspect every target page for missing or overlapping content, missing glyphs, incorrect reading sequence, unmatched captions, broken references and unexpected source-language residue. Prioritize high-risk locations: specifications, warnings, callouts, tables, footnotes and variable-driven text. Use side-by-side source and target proofs where helpful, but do not force identical page breaks when the target language legitimately needs different composition.
A good issue ticket identifies edition, page, text element or story reference, expected meaning, observed defect, severity, screenshot and proposed owner. The translator can resolve language questions; the designer can resolve composition; the technical editor can verify figures and units; the production specialist can resolve export settings. Explicit ownership prevents a common loop in which everyone edits the same page without knowing which requirement is failing. After corrections, inspect the affected page and adjacent flow rather than only the changed phrase.
A practical handoff checklist for the localization team
The source handoff should state the frozen document revision, target language, required output, included and excluded content, protected names and numbers, glossary, reference page previews, and return format. The return handoff should include the translated file, exceptions, unresolved queries, structural validation results and a clear mapping to the source edition. The layout handoff should record approved fonts, special composition rules, changes to page flow and outstanding production warnings. These are not separate bureaucratic artifacts; they are the minimum shared context needed to reconstruct reliably.
Establish a final sign-off in which the project editor approves meaning, the layout specialist approves visual completeness, and the output owner approves the exported file against the delivery specification. A small publisher may combine roles, but the questions remain distinct. If an urgent change is made after sign-off, reopen the checks relevant to it. The safest workflow is the one that can tell a colleague which edition was translated, which output was proofed and why a specific layout choice was accepted.
Transfer exercise: test a one-page flyer before a full catalogue
Create or select a nonconfidential flyer with a headline, table, image caption, two paragraphs and a hyperlink. Export a controlled interchange copy through the chosen InDesign workflow, perform a round trip with a longer target-language sample and reopen it. Identify which elements are represented as stories, which are linked graphics and which are automatic variables or references. Intentionally use a long heading and a script needing different glyph coverage. Ask the layout reviewer to spot missing text and tell you whether it is an extraction, import or composition problem.
Next export a PDF and verify links, text selection, page sequence and the exact meaning of the critical table. If anything breaks, explain the layer that owns the fault before changing content. This small rehearsal is more valuable than launching a hundred-page translation on the assumption that IDML means lossless. It builds a repeatable acceptance method that can be used for magazines, educational booklets, instruction manuals and multilingual annual reports without pretending they all have the same layout constraints.
Summary: preserve text, layout and delivered evidence
Fast InDesign localization is not achieved by sending more text through a translator. It comes from a stable source edition, complete content inventory, tested IDML or editorial exchange, structural protection, target-language typography, overset and story checks, appropriate preflight, and verification of the final PDF. Keep translation decisions separate from print mechanics while making the handoff between them explicit. The goal is an editable, correct target publication whose every important word is actually visible to the reader.
Frequently asked questions
Can I translate an INDD file directly in a CAT tool?
Support depends on the tool and version. Some workflows use IDML or specialized plugins. Test a round trip with representative complex pages before assuming that a format converter preserves every InDesign feature.
Is IDML the same as a plain text file?
No. IDML represents structured InDesign content. Editing extracted words without preserving the associated stories, markers and styles can corrupt reconstruction. Use a compatible controlled workflow.
Why did my translation disappear from the exported PDF?
The text may be overset, hidden by a layer or condition, missing from the extraction, misplaced during import or excluded from export. Follow its source-story and reconstruction path before rewriting the translation.
Should the translated booklet have the same number of pages as the original?
Not necessarily. Different language and font metrics can require different composition. Preserve content and navigation integrity, and obtain design approval for the target page plan rather than deleting meaning to match source pagination.
Does InDesign preflight prove the translation is correct?
No. Preflight can detect technical issues defined by its profile, such as missing resources or overset text. A human review is still required for language, instructions, figure relationships, measurements and reading order.
Can I package all fonts and share them with the translation vendor?
Packaging has font options, but font rights and project confidentiality still apply. Verify licences and share only the assets necessary for the recipient’s role. Select authorized fonts that support the target script.
Related eduKateSG reading and internal-link opportunities
The existing eduKateSG article Font Glyph Coverage and Fallback QA explores general script coverage problems, while Localization Build Validation explains parser and artifact checks. The InDesign-specific job here is an editable IDML/INDD production round trip with full-page and final-output verification, rather than generic PDF translation or text formatting.