A translated IDML can look complete in a CAT tool and still reopen in InDesign with missing copy, clipped text, or a page layout that no longer works. A preflight check catches those problems before the client discovers them in a file they expected to use.
The checklist below separates content, layout, language, and packaging checks. Treating those as separate sign-off gates makes it easier to find the source of a problem and to explain what the delivered files do - and don’t - include.
What a translated IDML preflight checks¶
IDML is an XML-based interchange format for InDesign documents. The format specification describes an XML representation of document elements such as text and graphic frames, stories, and other layout components. That structure is why an IDML preflight needs to check both the content and the rendered pages: extracted text alone can’t show whether a story is visible, a frame is clipped, or an object has shifted on the page. The referenced specification is version 8.0 and corresponds to InDesign CS6, so it describes the format’s structure rather than guaranteeing full fidelity for every current InDesign feature (IDML File Format Specification).
A preflight is a final inspection of the returned file and its dependencies before handoff. For a translated InDesign document, that means more than scanning a PDF for typos. The file needs to reopen, display expected content, preserve a usable layout, and make its production dependencies clear to whoever receives it.
Keep the original native InDesign document available while you check the translated IDML. The native file gives you a reference for page structure, source content, and objects that may be difficult to diagnose from the translated return file alone. IDML is an interchange representation, not a reason to discard the source document.
A useful preflight has four separate gates:
- File gate: the final exported IDML opens in the InDesign version intended for client use.
- Content gate: expected sections, captions, tables, repeated elements, and translated passages are present.
- Layout and language gates: pages display correctly, and the translated text receives its own linguistic review.
- Handoff gate: the client knows which files are included and what fonts, links, or other assets may still be needed.
Those gates matter because one successful check doesn’t prove the others. A spellcheck can’t establish that every story is visible. A clean-looking PDF can’t establish that the editable IDML contains the same content. And an IDML that opens on the production workstation may still prompt the client to resolve missing fonts or links.
The formatting QA checklist for translated files covers checks that apply across document types. The IDML-specific checks below add the round-trip, InDesign, and asset questions that a general formatting review may not address.
Start with a clean round-trip¶
A returned IDML needs to be tested in InDesign after export, not just in the CAT tool or in the original InDesign document. The returned file is the artifact the client will open. Reopening that file gives you a chance to catch problems introduced during export, translation, or import.
Start by preserving an untouched copy of the translated IDML. Open the copy in the InDesign version intended for client use and note any prompts about links, fonts, or compatibility. Don’t save over the only returned copy while you investigate. Keep the native source and the untouched IDML available for comparison and recovery.
A reported round-trip problem shows why the reopen step isn’t optional. In an Adobe Community discussion dated September 11, 2024, a translator described translated text that wasn’t visible after reopening the returned IDML in InDesign. The report is anecdotal, but it documents a failure mode worth checking before delivery.
As the translator Miriam348 described in the Adobe Community discussion:
I discovered that some texts that I translated in Trados are missing in InDesign now.
The practical lesson isn’t that every missing passage has the same cause. The lesson is that completed translation work doesn’t prove that all translated content made it into the file the client will open. Compare the expected content with the reopened return file.
Check the document’s overall shape before reviewing individual words. Confirm that the expected pages, spreads, sections, and page order are present. A missing page can hide an entire content problem; a page that exists but has shifted elements still needs a visual review.
Then compare the translated file against the source and the agreed scope. Use a source-side reference, a translation export, or a page-by-page checklist to account for:
- Headings and section labels.
- Body copy, captions, footnotes, and callouts.
- Tables, including labels and repeated headers.
- Text in sidebars, running heads, and page furniture.
- Repeated instructions, warnings, or product names.
- Content on hidden or non-printing layers when the client needs it.
- Any sections intentionally left untranslated or excluded from delivery.
Mark each item as present, absent by design, or unresolved. That small bit of documentation prevents an excluded element from being confused with an accidental omission. It also makes review easier when the file contains repeated content or objects that appear on more than one page.
If a passage appears absent, inspect its story rather than immediately retranslating it. Text may exist in the document but fall beyond the visible area of its frame. The difference matters: one problem may call for layout adjustment, while another may point to the extraction, tag handling, or return process.
The safe IDML round-trip workflow explains the broader process of preparing and returning an InDesign file. For preflight, the key principle is simple: the reopened return file, not an earlier working copy, is the version that must pass review.
Check stories, frames, and every spread¶
A translated layout can fail even when all the words are present somewhere in the document. Text that no longer fits a frame may be hidden from the page, and longer or shorter translated copy can change how content flows between frames. A visual pass catches problems that a text-only comparison can’t.
Begin with a page-by-page review of the reopened file. Inspect every page and spread for omitted or clipped copy, text-frame overflow, displaced elements, and a sensible reading order. Don’t limit the pass to pages that look unusual at first glance. Repeated layouts can carry the same error across several pages, while a small frame on an otherwise clean spread can conceal an important note.
Look closely at:
- Text touching or running past a frame edge.
- Captions separated from the image or diagram they describe.
- Tables whose text is clipped, crowded, or difficult to follow.
- Headings left alone at the bottom of a page.
- Callouts that overlap another object or no longer point to the right item.
- Text that appears behind an image, shape, or other page object.
- Labels that have shifted away from the fields or graphics they identify.
- A reading sequence that no longer follows the intended order.
Overset text is text that exists in a story but doesn’t fit in the visible text frame. InDesign’s red plus indicator at the lower-right edge of a frame is a clue that the story may contain overset text. An Adobe Community Expert suggested checking that indicator and using Story Editor to inspect the story in a discussion dated September 11, 2024 (round-trip troubleshooting discussion). Treat that suggestion as a diagnostic step, not a guarantee that every missing-text problem is overset.
When you find a red plus, open the story in Story Editor and see what follows the visible text. If the missing passage appears there, the text may be present but not visible on the page. If the story doesn’t contain the expected translation, inspect the returned content and the translation pipeline instead. The IDML tag guide for Trados, memoQ, and Phrase can help when the problem points toward tags or segmentation rather than page flow.
A page-by-page review also needs a second look at visually dense areas. Tables, small captions, footnotes, and narrow sidebars can be harder to read after translation because a different word length or line break changes the available space. Check the complete passage, not just the first and last line. A sentence may appear to end cleanly even though a line has been clipped from the middle of a frame.
One designer described receiving translated datasheets with truncated text boxes and an unattractive layout. The report doesn’t establish how common the problem is, but it shows why translation quality and layout quality need distinct checks. As the participant gaurav_2111 wrote in an Adobe Community discussion dated March 11, 2025:
When we get the translated documents back, they are usually in a very bad shape. There are a lot of truncated text boxes, the layout is not very aesthetic, and so on.
A visually awkward page isn’t automatically a translation error, and a linguistically accurate sentence isn’t automatically ready for publication. Record layout defects separately from language findings. Doing so lets the person responsible for each kind of correction work from a clear list rather than trying to infer the issue from a vague comment such as “page looks wrong.”
Use the PDF proof as a visual aid if your workflow calls for one, but inspect the reopened IDML itself. Adobe’s InDesign API exposes separate package options for including an IDML file and a PDF, which supports treating the editable interchange file and its visual reference as distinct handoff components (Adobe InDesign UXP DOM API).
Run a separate language and content review¶
Layout inspection can’t replace linguistic QA. A page may be beautifully balanced while a caption is missing, a term is inconsistent, or a number has changed. Treat language and layout as separate gates, then check the final page again after any correction that affects text flow.
Compare the reopened layout with the approved translation or other authoritative text reference. Check names, terminology, numbers, dates, units, punctuation, and repeated phrases. Verify that each translated item belongs to the correct illustration, table, heading, or field. Text can be present and still appear in the wrong place.
Give extra attention to the parts that are easy to overlook during a visual pass:
- Footnotes and endnotes.
- Small labels inside diagrams.
- Table headers and repeated labels.
- Warnings, disclaimers, and safety statements.
- Running headers, page references, and section titles.
- Text on master pages or non-printing layers when those layers are part of the client’s workflow.
The source file can help you identify what should appear, but it can’t decide whether the translation is correct. A text comparison may find a missing phrase, while a qualified language reviewer checks whether the surviving phrase has the right meaning and terminology. Neither check can stand in for the other.
If review finds a wording change, inspect the reflowed page again after the edit. A corrected phrase may take more lines than the earlier version and create a new overflow or collision. This is especially important for a story threaded across several frames: changing one passage can alter where later text appears.
A translation project should also distinguish intentional omissions from accidental ones. If a brand name, legal notice, or product label stays in the source language by instruction, record that decision so a reviewer doesn’t “correct” it without context. If a passage was omitted from the translation scope, note that clearly rather than allowing the client to assume the file is complete.
For a closer look at how one sentence can become several CAT-tool segments, see why one sentence becomes many IDML segments. Segment boundaries can affect review and troubleshooting, but the final sign-off still belongs to the complete story and the rendered page.
Check fonts, links, and package dependencies¶
An IDML file isn’t a complete inventory of everything a client may need to continue production. Adobe’s InDesign package API treats fonts, linked graphics, reports, IDML, and PDF as separate package options. Its report can include printing instructions, print settings, font and link lists, required inks, and other production information (Adobe InDesign UXP DOM API).
Check fonts before describing the file as ready for continued editing. Note which fonts the document needs, whether they resolve in the delivery environment, and whether the client already has access to them. Don’t promise to include every font: Adobe’s API documentation describes a condition for fonts activated from Adobe Fonts. Confirm the applicable licensing and transfer arrangements instead of assuming that a font can be copied into a package.
Check linked graphics in the same way. Confirm that the expected images are available, that the links resolve in the intended environment, and that the displayed graphics match the document. If the client needs to keep editing, find out whether the links should be supplied with the handoff and where the client expects to place them.
Hidden layers deserve an explicit decision. A layer can contain content that isn’t visible in the ordinary page view, yet still matter to the recipient’s production workflow. Adobe’s package API provides an option to include assets from hidden layers. Decide whether hidden or non-printing content belongs in the handoff, and document the choice rather than assuming visible page objects tell the whole story.
A package report can make dependencies easier to review, but it doesn’t remove the need to check the actual returned file. Compare the report with the document and confirm that the files the client expects are present. For a book-level delivery, check the component documents and their assets as well as the overall package; a report or package option for books doesn’t establish that every chapter is complete.
| Handoff item | What to verify | Why it matters |
|---|---|---|
| Translated IDML | The final returned file opens and displays as expected | The client needs the editable interchange file, not just a previous working version |
| PDF proof, if agreed | The pages provide a clear visual reference | A proof helps review appearance but doesn’t replace the editable file |
| Fonts | Required fonts are identified and available through an agreed route | Missing fonts can change line breaks and page appearance |
| Linked graphics | Required links resolve or are supplied as agreed | The IDML alone shouldn’t be assumed to explain every linked asset |
| Package report or inventory | Fonts, links, and relevant production information are listed | The client can see dependencies and follow up on missing items |
| Hidden-layer content | The inclusion or exclusion decision is recorded | Non-visible material may still matter to editing or production |
The handoff should state what the client received and what remains their responsibility. If an asset is missing, identify it plainly. If a font can’t be transferred, say so and provide the available information about it. A clear inventory is more useful than implying that an IDML file is self-contained.
Common preflight failures and how to investigate them¶
A useful checklist doesn’t just flag a defect. It helps narrow down where to look next. Missing text, overflow, and missing assets can look similar to a client, but they call for different fixes.
Expected text isn’t visible. Check the relevant frame for the red plus indicator, then inspect the story in Story Editor. Compare the story with the translated reference. If the expected passage is absent from the story, investigate the IDML return and translation-tool settings, including tag handling. An Adobe Community discussion raised both overset text and XML-tag configuration as possible lines of investigation; neither suggestion proves a single cause for every case (Adobe Community round-trip discussion).
The text is present but clipped. Inspect the frame and the page around it, then review the passage in context. The cause may be a text-fit problem rather than missing translation. Check whether the story continues into another frame and whether the translated layout still communicates the intended reading order.
The page looks different after reopening. Compare the reopened return file with the native source and the agreed design reference. Check fonts, links, object placement, and page composition. Don’t assume that a PDF preview or an earlier working file will show what the client sees when they open the IDML.
A graphic or font is missing. Check the link and font inventory, then confirm what the client can access. Resolve the dependency where the delivery agreement permits it, or tell the recipient exactly what is missing and what they need to provide.
A visual proof looks fine, but the editable file has not been checked. Reopen and inspect the IDML anyway. The PDF and IDML are separate deliverables with different uses, so a clean proof can’t establish that the editable return file is ready for continued work.
A tempting shortcut is to mark the file as complete after a spellcheck or a quick PDF scan. Both checks can miss a story that didn’t return, an overset frame, or an unresolved link. The stronger approach is to record the finding, identify whether it belongs to content, language, layout, or packaging, and confirm the correction in the reopened file.
Keep the native source as a reference while you troubleshoot. When a problem is hard to reproduce, compare the source, translated text reference, untouched returned IDML, and any proof created from that return. Keeping those artifacts distinct makes it easier to tell whether the issue began in the source, the translation round-trip, or the final page layout.
Before you close the preflight, ask someone who hasn’t been looking at the same page for hours to review the checklist and the file. A fresh reviewer can follow the page order, read the visible content, and check whether the handoff inventory makes sense without relying on assumptions from the production team.
FAQ¶
How do I check a translated IDML file before sending it to a client?¶
Reopen the final exported IDML in the InDesign version intended for client use. Compare the expected content with the reopened pages, inspect overflow and visual layout, review the language separately, and confirm that the handoff explains fonts, links, and any PDF proof.
How can I find overset text in a translated InDesign IDML?¶
Look for the red plus indicator at the lower-right edge of a text frame. Open the story in Story Editor to see whether the expected passage exists outside the visible frame; the indicator is a diagnostic clue, not a complete explanation of every missing-text problem.
Why is translated text missing after reopening an IDML file?¶
Overset text is one possible cause, but missing content can also point to the translation or return pipeline, including tag handling. Compare the reopened story with the expected translation and investigate both InDesign layout and the process that returned the IDML.
Should I send a PDF proof with a translated IDML file?¶
Send a PDF proof when the client needs a visual reference for review or approval. The PDF shows rendered pages, while the IDML is an editable interchange file; checking one doesn’t replace checking the other.
What should be included with an IDML file at handoff?¶
Agree on the translated IDML, any requested PDF proof, and an inventory or report of relevant fonts and links. Add supporting assets or instructions when the client needs them, and state any limits on font transfer or missing dependencies.
Do fonts and linked images travel inside an IDML file?¶
Don’t assume that an IDML alone contains every font and linked graphic needed for continued production. Check required fonts and link status separately, and agree how any dependencies will be made available to the client.