Adobe InDesign the preparation of PDF files for translation

← Back to Resources
‍

Translating PDF Files: Why Layouts Break and What to Do Instead

DTP Insights

PDF is one of the most common file formats agencies receive from clients, and one of the worst starting points for a translation project. Knowing why, and what to do instead, saves money and avoids DTP problems that surface at the end of a project, when they cost the most to fix.

Free Tool · DTP Services Berlin
Check your project's DTP risk before it starts
50 languages · file format scoring · instant checklists · no signup
Run the Risk Checker →

Why PDF is fragile

PDF was designed to look the same on every screen and every printer. That same design makes it hard to edit and translate.

A PDF does not store text as a flowing document. It stores lines and fragments of text at fixed positions on the page. An untagged PDF has no paragraphs or headings at all. A tagged PDF does mark headings and paragraphs, but only to describe the structure for assistive technology; the text still does not flow from one line or frame to the next as it does in Word or InDesign.

This is why editing a PDF directly is fragile, even in Adobe Acrobat, which does allow text editing. When a translated sentence is longer than the original, its text box grows or the text is squeezed, and neighbouring boxes do not move out of the way. Each box is independent, so nothing reflows.

Key insight

PDF is built for fixed output. Translation needs a file in which text can flow, and that file is the source the PDF was exported from.

The PDF-to-Word route: common but costly

The most widespread approach in translation agencies is converting the PDF to a Word document, sending it to a CAT tool for translation, then converting the translated Word back to a formatted file. This works up to a point.

The conversion from PDF to Word is imperfect by design. Conversion software has to guess at the document structure. It reads coordinates and tries to reconstruct a flowing document from a fixed layout. The result is often:

  • Multi-column layouts that break apart or read in the wrong order
  • Headings extracted as individual text fragments rather than coherent paragraphs
  • Tables split into disconnected cells
  • Line ends turned into paragraph breaks, which split sentences into separate segments in the CAT tool
  • Paragraph order that does not match the visual reading order of the original

For a translator, this means a single sentence may appear as three separate segments, a heading appears twice, and translation memory suffers. The DTP work afterwards is far heavier than it would need to be.

Watch out

Careful cleanup before the CAT tool reduces some of these problems: removing line breaks, joining split paragraphs, correcting the reading order. It is manual work, and the effort grows with the size and complexity of the document.

When PDF-to-Word is acceptable

Not every project justifies a full InDesign workflow. For short, simple, text-heavy documents (a one-page letter, a simple form, a short press release), PDF to Word conversion is often the simplest route. It works when:

  • The document has a simple, single-column layout with no complex tables or graphics
  • The page count is low enough that manual cleanup is manageable
  • The final delivery does not need to precisely match the original visual layout
  • The client has no source files and cannot provide them
Tip

When converting, enable "Retain Flowing Text" rather than "Retain Page Layout" where available. Flowing text gives cleaner CAT tool output: the layout is lost, but sentences stay together, and that is what the translator needs.

The right approach: work from source files

If the client has InDesign source files, use them. InDesign exports to IDML (InDesign Markup Language), which CAT tools such as Trados Studio and memoQ process directly. The translation happens inside the actual layout. Paragraph styles, fonts, spacing, and structure are preserved. Post-translation DTP is minimal.

Fixing the most common Trados error

When receiving IDML files for translation, a common error appears: Trados Studio refuses to open the file with the message:

Trados error message

"The selected IDML file was created by an unsupported version of Adobe InDesign and will not be processed."

The fix is simple and takes thirty seconds. There are two ways depending on whether you want to fix it for one project or for all future projects:

For a specific project

  1. Go to Project Settings
  2. Expand File Types
  3. Select Adobe InDesign CS4-CC IDML
  4. Click Common
  5. Check "Process unsupported file versions"
  6. Do this before adding files; the setting does not apply to files already in the project

For all future projects

  1. Go to File → Options
  2. Expand File Types
  3. Select Adobe InDesign CS4-CC IDML
  4. Click Common
  5. Check "Process unsupported file versions"
Result

Trados will now process the IDML regardless of which InDesign version created it. In practice, it works correctly almost every time.

Free browser tool

Need to prepare a DTP project brief?

Create a structured project brief in your browser before contacting a DTP provider. Add your file format, page count, languages, deliverables, and common production risks. No upload, no storage, no sign-up.

Prepare project brief

You can use the generated brief with DTP Services Berlin or any other agency.

When there are no source files: consider redesigning

If the document is short, up to fifteen or twenty pages, and the client cannot provide source files, it is often worth rebuilding it in InDesign from scratch instead of working from a converted PDF. This sounds counterintuitive but the maths work out.

A clean InDesign rebuild takes a few hours. The resulting IDML can be translated cleanly in a CAT tool. Post-translation DTP is minimal. Compare that with the hours spent cleaning up a broken PDF conversion, fixing missegmented CAT output and correcting the layout at the end, often in several languages.

Rule of thumb

Under 20 pages with no source files → consider rebuilding in InDesign. Over 20 pages → PDF to Word with thorough cleanup is usually the only realistic option.

Designing for translation from the start

The cleanest projects are those where the document was designed with translation in mind before anyone opened InDesign. A designer who understands multilingual DTP will:

  • Use paragraph and character styles throughout instead of manual overrides
  • Avoid forced line breaks (Shift+Enter) inside paragraphs; CAT tools split the segment there or show a tag mid-sentence
  • Avoid typed hyphens for line breaks; they stay inside the word after translation and spoil translation memory matches
  • Leave room in text frames: most European languages need about 30% more space than English
  • Design in InDesign from the start and hand over the source files with the PDF

The last point carries the most weight in multi-language projects. A document going into thirty languages should be a clean, style-driven InDesign file. The IDML goes to translation, comes back, and the DTP work in each language is straightforward. A PDF converted, cleaned up, translated and reformatted thirty times repeats every problem thirty times.

A note on forced line breaks

Forced line breaks are one of the most common problems designers leave in translation files. A forced line break (Shift+Enter in InDesign) looks like a paragraph break on screen, but CAT tools treat it differently. Depending on the tool and its settings, the sentence is split into two segments at that point, or the break appears as a tag in the middle of the sentence. Either way, translation memory matches suffer, and the break ends up in the wrong place in the translated line.

The break is invisible unless hidden characters are shown, so it often goes unnoticed until the project is in translation.

How to check

Before any IDML file goes to a CAT tool, turn on Type → Show Hidden Characters (Ctrl+Alt+I / Cmd+Option+I); forced line breaks show as a bent arrow. To find them all, search for ^n in Find/Change, then remove each one or replace it with a space.

Summary: how to choose your approach

Situation Best approach
Client has InDesign source files Export to IDML, translate in CAT tool directly
No source files, short simple document Rebuild in InDesign, export IDML
No source files, long or complex document PDF to Word with thorough cleanup before CAT
New project, will be translated to multiple languages Design in InDesign from day one, style-driven, no forced breaks
Further Reading & Resources