Multilingual InDesign Preflight Checklist for Publishers
A print job that ships with a missing glyph, an overset line, or a font that did not embed does not get a second chance — the press runs, the error prints, and the reprint is on you. For single-language files, a quick visual scan usually catches the obvious problems. For multilingual documents, the failure surface is larger: text expands and reflows, fonts lose glyphs, hyphenation rules change per language, and right-to-left scripts can reverse the reading order of threaded frames. A multilingual InDesign preflight checklist is the structured pass that catches those issues before the file leaves your desk, not after the proof comes back from the printer.
This checklist assumes you have already done the source-file prep — live text, named styles, native tables, real cross-references. If you have not, run our InDesign pre-translation checklist for IDML localization first; that post covers what to fix before you export. This one covers what to verify after translation, on the re-opened IDML, right before you send the job to print.
Why preflight is different for multilingual print
Preflight on a monolingual file is mostly mechanical: bleed, resolution, color mode, fonts embedded. Preflight on a multilingual file has to re-check things the translation step changed:
- Reflow. Translated copy is longer or shorter than the source, which pushes lines, pages, and threaded stories. A layout that was clean in English can overset in German and gap in Japanese.
- Glyph coverage. The font that rendered the source may not contain the accented characters, Cyrillic, or CJK glyphs the translated copy needs. Missing glyphs render as blank boxes or the wrong character.
- Hyphenation and line breaks. Hyphenation is per-language. If the document's language metadata is still set to the source language, hyphenation applies the wrong rules and produces ugly breaks or orphaned words.
- Reading direction. Right-to-left scripts (Arabic, Hebrew) reverse paragraph direction and can flip the expected flow of threaded frames. Mixed-direction paragraphs are the most common cause of a print proof that "looks wrong."
- Style integrity. Named paragraph and character styles are what make a translated IDML re-open with the layout intact. If the source had local overrides, translation will expose them.
Every one of these is cheaper to catch at your desk than at the press.
The multilingual InDesign preflight checklist
Run this pass on the translated IDML after you re-open it in InDesign, before you export the print-ready file. It is organized into pre-print and format checks.
| # | Check | What to verify | Why it fails in multilingual print |
|---|---|---|---|
| 1 | Font embedding | Every font used is embedded or outlined; no missing-font warnings | Translated copy often needs glyphs the source font lacks |
| 2 | Glyph coverage | Each font covers every script in the translated text (Latin Extended, Cyrillic, CJK, Arabic) | Missing glyphs render as .notdef boxes |
| 3 | Overset text | No overset frames in any language version | Text expansion after translation pushes copy out of its frame |
| 4 | Hyphenation language | Paragraph language matches the translated language for every story | Wrong language = wrong hyphenation and wrong spell-check |
| 5 | Line and page breaks | No widows, orphans, or awkward breaks introduced by reflow | Reflow from expansion shifts pagination |
| 6 | Reading direction | RTL scripts render right-to-left; mixed-direction paragraphs are set correctly | Default LTR flow reverses Arabic/Hebrew paragraphs |
| 7 | Bleed and margins | Bleed still set, margins still hold after reflow | Reflow can push content into the bleed or off the trim |
| 8 | Image resolution | All placed images ≥300 ppi at final size | Unchanged by translation but easy to skip when re-checking text |
| 9 | Color mode | CMYK for print, spot colors confirmed with the printer | RGB images slip through when focus is on text |
| 10 | Cross-references and TOC | TOC and cross-refs regenerate to correct pages after reflow | Page numbers shift when translated copy repaginates |
| 11 | Conditional text | Only the conditions meant to ship are visible | Hidden conditions can export and print unexpectedly |
| 12 | Links | All links present and updated, no modified/missing link warnings | Re-opening a translated IDML can lose link paths |
Twelve items is the minimum for a print-bound multilingual file. For a job going to multiple printers or regions, add a region-specific pass: paper size, bleed standards (3 mm vs 0.125 in), and any local regulatory marks. Adobe's InDesign Preflight panel can automate checks #1, #3, #8, and #12 as a saved profile — build one per language pair and reuse it across jobs.
The format step: export IDML, not INDD
Every check above runs on the translated file you re-open in InDesign. To get that file, the translation step needs a format that preserves stories, styles, and structural objects — and that format is IDML.
IDML (InDesign Markup Language) is Adobe's open, XML-based export of an InDesign document, produced via File → Export → InDesign Markup (IDML) inside Adobe InDesign. We accept IDML only — never INDD, never PDF, never DOCX. INDD is the proprietary binary InDesign format; we cannot parse it. After translation, we return a translated IDML file, ready to re-open in InDesign, at which point you run the preflight checklist above.
If the source you were handed is an .indd, open it in InDesign and export IDML before translation. If it is already IDML, you are ready.
Common preflight failures and how to catch them
A few failures account for most multilingual print rejections:
- Missing-glyph boxes in the proof. Caught by check #2. Open the translated IDML, select all, and use
Type → Find Fontto confirm every font covers every script. Substitute a font that has the glyphs, or embed a fallback. - Overset frames after German or Russian translation. Caught by check #3. German and Russian expand roughly 20–30% versus English; Arabic can contract vertically but expand horizontally. Resize frames or relax leading before print.
- Wrong hyphenation in the proof. Caught by check #4. Select each story and set the language in the Character or Control panel to the translated language; reflow and re-check breaks.
- Reversed Arabic/Hebrew paragraphs. Caught by check #6. Set the paragraph direction to right-to-left for those stories; verify the story board order matches the script's reading order.
- TOC points to the wrong pages. Caught by check #10. Regenerate the TOC and all cross-references after reflow settles, not before.
From checklist to translated IDML
The preflight pass above takes 20–40 minutes on a typical catalog or brochure and saves the cost of a reprint. The translation step that precedes it does not have to take an afternoon. TranslateInDesign accepts your IDML, translates every story, preserves styles and structural objects, and returns a translated IDML ready to re-open in InDesign — the file you then run this multilingual InDesign preflight checklist on. If you prepared the source with our InDesign pre-translation checklist, the round-trip is the clean part; the preflight is the part that makes it print-ready.
Upload your IDML and use code EARLYBIRD100 at checkout for $100 off your first translation. Then run the checklist, send it to press, and skip the reprint.