InDesign Translation: How to Translate InDesign and Illustrator Files Without Rebuilding the Layout
InDesign translation means extracting the live text from your InDesign files, usually through IDML, translating it against your translation memory and glossary, and importing it back into the original layout, so nobody retypes a word. A DTP specialist then adapts each language and a linguist checks the result in context. DEMA Solutions works this way in InDesign and Illustrator, which keeps layouts intact and translation memories clean.
Who this guide is for
This guide is for the people who own the files: technical documentation managers whose manuals, spare parts catalogues and quick start guides are laid out in InDesign, marketing managers who publish brochures and datasheets in five to fifteen languages, and graphic designers who receive translated text and are asked to make it fit. It is also for procurement and operations managers who see the same layout invoice come back every edition and want to know why.
The questions behind it are practical. What should you send, and in which format? Why does one supplier return an open file that prints first time while another returns text in a spreadsheet? Which habits in the source file make every future edition cheaper, and which ones quietly multiply the cost? The sections below answer each one.
How InDesign translation works
An InDesign document is not a text file. The words sit inside threaded frames, tables, anchored callouts and parent pages, styled through paragraph and character styles and surrounded by linked images, some of which carry text of their own. Copying that text into a word processor and pasting the translation back is slow, error-prone and destroys the link between the layout and your translation memory. A professional InDesign translation keeps the layout and the text connected from start to finish.
The connection runs through IDML, the InDesign Markup Language. IDML is an XML-based package that describes the whole document: stories, styles, frames, tables and page geometry. Translation software can read it, show translators only the translatable text, protect everything else as tags and write the translated text back into the same structure. When the file returns to InDesign, the frames, styles and graphics are exactly where the designer left them, and only the language has changed.
That is why IDML translation is the standard route for InDesign files. It also has a practical side effect: IDML is the usual way to open a document in an earlier version of InDesign, so it smooths over version differences between you, your supplier and your designer. The native INDD file is still worth sending alongside it, because it is the reference against which the round trip is checked.
Why the package matters more than the file
The single most useful thing you can send is a packaged InDesign document, not a lone INDD. The Package command collects the document, the fonts it uses and every linked graphic into one folder, together with a report of what is in it, and it can also add an IDML copy and a PDF. Each part has a job in the translation. The package is only part of the brief, and our checklist on what to send a translation supplier covers the memories, glossary and deadlines that complete it.
Fonts decide line breaks, hyphenation and how much text fits in a frame. Without the original fonts, InDesign substitutes others, the text reflows and every page has to be checked twice: once to restore the source and once for the translation. Font licences vary, so check what yours allow; if a font cannot be shared, agree on how your supplier will obtain it before the project starts.
Linked graphics are often where the hidden text lives. Diagrams created in Illustrator, exploded views with callout numbers, screenshots of a control panel and labelled photographs are placed as links, and their text is invisible to an export of the InDesign file. If the links are missing, that text is missed too, and someone finds out at print stage.
The PDF is the visual reference. Translators who can see where a string appears, in a table header, a warning box or a figure caption, translate it better than translators working from a list of segments.
How the file is built decides what it costs
Two InDesign files can look identical on paper and behave completely differently in translation. The difference is in how they were built, and it decides how much text your translation memory recognises in the next edition, how many tags translators have to handle and how many hours the layout takes. This is where the clean memory and the cost come together.
Paragraph and character styles. Text formatted through styles exports as clean sentences. Local overrides, such as a word made bold by hand or a size changed in one paragraph, turn into tags inside the sentence. The same warning formatted two different ways is stored as two different segments, so the memory sees a near match where it should see an exact one. Over a product range, those small differences add up to text you pay to have reviewed again.
Hard returns, soft returns and spaces. A designer who forces a line break to make a heading wrap nicely, or uses spaces and tabs to line up text, splits sentences in the export. Translators receive half a sentence per segment, the target language needs a different break anyway, and the memory stores fragments that will never match cleanly again. Line breaks belong to the layout of each language, not to the source text.
Text frames and threading. Text that flows through threaded frames exports as whole stories. Text typed into separate, unthreaded frames, one line per frame, exports as unrelated fragments in an unpredictable order. Translators lose context, and every frame has to be repositioned by hand once the translation is longer than the source.
Anchored objects and inline graphics. Callouts, icons and small images anchored in the text move with it when it expands. Objects placed freely on the page stay where they are, so a German paragraph that runs three lines longer than the Italian one slides underneath a warning symbol that no longer belongs to it.
Tables. Real InDesign tables translate and reflow cleanly. Tables simulated with tabs and text boxes break as soon as a cell’s text grows, and tables split across separate frames have to be rebuilt in every language.
Live text instead of outlines. Headlines converted to outlines, text flattened into images and labels drawn as paths cannot be extracted. They have to be found, retyped and rebuilt for each language, which is slow, costly and invisible to your memory.
The effect on cost is simple arithmetic. Imagine a 200-page manual in which a recurring safety sentence appears in sixty places, but has been typed with three different manual breaks and two different overrides. Instead of one sentence translated once and reused fifty-nine times, the memory holds several versions, and each edition brings fuzzy matches that need a linguist’s attention. Multiply that by every repeated instruction, by every language and by every revision, and file quality becomes one of the largest levers on what technical manual translation costs. Fixing it once, in the source, pays back in every edition.
What changes in the layout when the language changes
Even a perfectly built file has to be adapted for each language. That adaptation is the core of multilingual desktop publishing, and InDesign gives the specialist the controls to do it properly rather than by shrinking type.
Text expansion and overset text. German, French and Spanish often need noticeably more room than English or Italian. When a frame cannot hold its text, InDesign marks it as overset, and the hidden text simply does not print. Overset text is the classic silent error in translated layouts: a sentence of a warning, a table row or the last step of a procedure that exists in the file but not on the page. Preflight reports it, and a careful DTP specialist resolves every instance by adapting frames, tables and pagination rather than reducing point sizes until the text is no longer legible.
Fonts and scripts. A font that works for English may not include the characters of Polish, Czech, Romanian or Turkish, and may not cover Greek or Cyrillic at all. Missing glyphs appear as highlighted boxes on screen and as gaps or substitutions in print. Chinese, Japanese and Korean need fonts and composition settings of their own, and right-to-left languages such as Arabic and Hebrew use InDesign’s World-Ready composer, with paragraph direction, table direction and page binding adjusted for the language. These are decisions to make before the first translation, not after the proofs come back.
Language settings and hyphenation. Every paragraph and character style in InDesign carries a language attribute that controls hyphenation and spell checking. If the translated text keeps the source language setting, German words break according to Italian rules, and the spell checker approves text it cannot read. Assigning the right language to the styles of each version is a small step that prevents a lot of visible errors.
Composer, justification and line breaks. The paragraph composer evaluates whole paragraphs to balance spacing, which helps long translated paragraphs, but it can also move breaks in ways that separate a value from its unit or leave a single word on the last line. Non-breaking spaces between numbers and units, and the review of headings and table cells in each language, keep technical text readable.
Parent pages, variables and generated content. Running footers, document numbers and revision fields usually sit on parent pages (called master pages in older versions) or in text variables. They are translated once but appear everywhere, so a mistake there repeats on every page. Tables of contents, indexes and cross-references must be regenerated after translation, because their text comes from headings and markers that have just changed language.
Text in graphics. Linked Illustrator files and images with labels need their own handling. Text in Illustrator stays translatable if it is live point or area text on a clear layer; text converted to outlines has to be rebuilt. For technical illustrations, the cleanest approach is a numbered callout in the image and a translated legend in InDesign, which removes the illustration from the translation cycle altogether.
Version compatibility and other practical checks
InDesign does not open documents saved in a newer version, which is where IDML earns its place again: exported from the newer version, it opens in an older one. Tell your supplier which version your team uses and ask for the translated files to come back in a format your designers can open. If you work with InCopy assignments for editorial text, mention it at the start, because the translation route has to fit how your team edits the files afterwards.
Also note conditional text, hidden layers and notes. Content that is hidden in the source view may or may not be included in the export, and either outcome can be wrong. Decide which conditions and layers are in scope, and say so in the request.
A step-by-step InDesign translation workflow
The workflow that consistently produces print-ready files has seven stages, and each one has a reason.
First, receive and inspect the package. The DTP specialist opens the document with its fonts and links, runs preflight and checks for missing fonts, broken links, overset text in the source, outlined headings and text in images. Problems found here cost minutes; the same problems found at proof stage cost days.
Second, prepare the file. Manual line breaks are removed, stray overrides cleaned up, unthreaded frames threaded where it makes sense and fake tables identified. This is the work of DTP file preparation, and it is what keeps the memory clean for every future edition. The preparation never changes your design; it changes how the text underneath it is organised.
Third, export and analyse. The prepared document is exported to IDML, linked graphics with text are extracted separately, and the text is analysed against your existing translation memory. The analysis shows how much is new, how much is a fuzzy match and how much is already approved, which is the honest basis for a quote.
Fourth, translate and revise. Translators work segment by segment with your glossary and memory applied and the PDF beside them for context, and a second qualified linguist revises the translation against the source. Tags that carry styles, cross-references and anchored objects are protected, so the structure survives the round trip.
Fifth, import and typeset. The translated IDML is opened in InDesign and the DTP specialist adapts each language: language attributes, fonts for the script, overset text, tables, anchored objects, parent pages, regenerated contents and index, and the rebuilt or re-linked graphics.
Sixth, check the language in the layout. A linguist reviews the typeset PDF, not just the translation file, because some errors only exist on the page: a broken hyphenation, a truncated table cell, a label that no longer points to the right part, a heading that wraps badly. Corrections are made in the layout and written back to the memory, so the memory and the printed document stay identical.
Seventh, deliver. You receive open InDesign files, an IDML copy, linked graphics and print or screen PDFs for each language, and the updated translation memory. Next edition, the cycle starts from what is already approved. Screen PDFs that must work with assistive technology also need tagging and reading order checked in every language, as our guide to accessible PDF manuals and PDF/UA explains.
What to send, and what to ask a supplier
A complete request saves a round of questions and makes the quote accurate. Send:
- the packaged InDesign document (INDD, fonts, links) plus an IDML export and a PDF of the source
- linked Illustrator or Photoshop files that contain text, and a note of any text you do not want translated
- your existing translation memories and glossaries, in TMX and TBX if you have them
- the target languages, the InDesign version your team uses and the PDF output you need
Then ask the supplier a few questions before you commit. Do they work in the native files and return open InDesign documents, or only translated text? Who checks the language in the final layout? How do they handle fonts and scripts for languages your designers have never typeset? Will they show you how much of each edition comes from reuse, and will the memory be delivered to you? Our guide to choosing a technical translation company covers the wider set of questions, and how to check a supplier’s quality before you hire them explains how to test the answers.
Keeping the translation memory clean over time
The memory built from your InDesign files is an asset that grows with every edition, but only if what goes into it is clean. Whole sentences, consistent formatting and approved terminology produce segments that match again and again. Fragments, overrides and late corrections made only in the layout produce a memory that drifts away from the printed documents.
Three habits keep it healthy. Make corrections in the translation and push them through the layout, never the other way round, so the memory reflects what was printed. Approve terminology once in a shared glossary, which is how you keep terms consistent across translators and suppliers. And make sure the memory belongs to you, in a portable format, so it moves with you whoever lays out the next edition; owning your translation memory is what turns clean files into savings that last.
How DEMA Solutions handles InDesign translation
Our in-house DTP team works directly in your InDesign and Illustrator files. We inspect and prepare each package, export it for translation, typeset every language in the original design and check the final layout before delivery. Translation follows an ISO 17100 certified process in which a second qualified linguist revises every translation, and the language check is repeated on the typeset pages. Our teams in Italy, Serbia and Spain cover the layout and the languages in one workflow, so problems are solved in one place rather than passed between a translator and a designer. When the original file is not available, the team can also turn a PDF back into an editable layout.
Your translation memory and glossary stay yours and are delivered in TMX and TBX, and every quote shows how much of the edition comes from reuse. The full scope of our multilingual desktop publishing services is described on the service page.
For one Italian manufacturer, translation and layout of its marketing brochures run as one workflow, and its advertising agency approved the translated layouts instead of rebuilding them, as the brochure translation and DTP case study describes.
Where TUBE fits
For manufacturers who publish new editions of their catalogues and manuals every year, TUBE keeps the language of each edition under control. Your glossary and translation memory control machine translation, every approved translation goes into a memory you own and can export, and leverage reporting shows how much of each update comes from text you have already approved. Clean InDesign files make that reuse visible from the first update.
Frequently asked questions
The text is exported from the prepared InDesign file, usually as IDML, translated with a translation memory and glossary while the layout structure is protected, and imported back into the original document. A DTP specialist then adapts each language and a linguist checks the typeset pages.
IDML is InDesign's XML-based exchange format. It describes the text, styles and layout of a document in a form translation software can read and write back, and it can be opened in earlier versions of InDesign, which makes it the standard format for InDesign file translation.
It can be opened, but InDesign substitutes missing fonts, which changes line breaks, spacing and how much text fits. Send the fonts in the package where the licence allows it, or agree on licensed substitutes, especially for languages with special characters or other scripts.
Overset text is text that does not fit in its frame and therefore does not print. It is common after translation into longer languages and easy to miss on screen. Preflight reports it, and every instance should be resolved in the layout before the PDF is produced.
Yes, if it is live text. Text converted to outlines or flattened into an image has to be rebuilt by hand in every language. For technical illustrations, numbered callouts with a translated legend in the InDesign document are the most efficient approach.
They split sentences into fragments when the text is exported. Translators lose context, the target language needs different breaks anyway, and the memory stores fragments that will not match cleanly in the next edition, so more text has to be reviewed again.
Yes. Some errors only appear on the page, such as broken hyphenation, truncated table cells, wrong language settings or labels that no longer match a figure. A language check of the typeset PDF catches them before printing.
Send us an InDesign file
If your translated layouts need rework before they can be printed or published, send us a sample InDesign package. Our DTP team will tell you how the file should be prepared and how much of the next edition could come from text you have already approved.
FREE Download: Desktop Publishing (DTP) Project Checklist
Use this quick self-assessment to spot gaps in your DTP process. You’ll see where quality drops, where delays come from, and how you can cut costs when managing multilingual documents.
FREE Download: Desktop Publishing (DTP) Project Checklist
Use this quick self-assessment to spot gaps in your DTP process. You’ll see where quality drops, where delays come from, and how you can cut costs when managing multilingual documents.
