A translated document looks broken because the layout was designed for one language, and translation changes the text in ways the original design cannot automatically accommodate. Text expands or contracts, fonts change, special characters appear, and the visual structure falls apart as a result. The sections below walk through the most common causes and what you can do about them.
What actually causes a document to break during translation?
A document breaks during translation when the translated text no longer fits the space, formatting, or font structure of the original layout. The root cause is almost always a mismatch between the source design and the target language’s text properties. Translation is not a simple word-for-word swap; it changes the physical characteristics of the content itself.
The most common culprits are text expansion, font incompatibility, and encoding issues. When a sentence translates from English into German, for example, it can grow by 30% or more. That extra text pushes buttons out of place, breaks table cells, and overflows text boxes. At the same time, fonts used in the original document may not support the characters needed in the target language, causing symbols to appear as squares or question marks. Right-to-left languages like Arabic or Hebrew flip the entire reading direction, which most design templates are not built to handle.
Embedded text inside images is another frequent problem. If a graphic contains words that were never extracted into a translatable format, those words stay in the source language while everything around them changes, creating an inconsistent and unprofessional result.
Why do some languages cause more layout problems than others?
Some languages cause significantly more layout problems because they differ from the source language in script, reading direction, character set, or typical sentence length. The further a target language sits from the source in these dimensions, the more likely the layout is to break.
Languages that expand text substantially, such as German, Finnish, or Dutch, stress layouts built around concise English copy. A short English button label like “Submit” can become a much longer word in German, pushing interface elements out of alignment. On the other end of the scale, Chinese, Japanese, and Korean often produce shorter text, which can leave awkward gaps in designs that relied on longer copy to fill visual space.
Scripts that require special rendering, such as Arabic, Hebrew, Thai, or Devanagari, introduce additional complexity. Arabic and Hebrew run right to left, which means the entire document flow needs to be mirrored. Thai and Devanagari use stacked characters and diacritics that sit above or below the baseline, requiring more vertical line spacing than Latin scripts. Without adjustments to the layout, these elements collide or get clipped.
What is DTP and how does it fix translated documents?
DTP stands for Desktop Publishing, and in the context of translation, it is the process of reformatting a document after translation so that the layout looks correct in the target language. DTP specialists adjust text boxes, resize elements, reflow content, swap fonts, and correct spacing so the translated document matches the quality and appearance of the original.
When a translator delivers a finished translation, the text is linguistically accurate but the visual result is often unusable. DTP is what bridges that gap. A skilled DTP specialist works inside the original design file, whether that is InDesign, FrameMaker, Word, or another format, and manually corrects every layout issue introduced by the translation. This includes resizing text frames to fit expanded copy, replacing fonts with versions that support the target script, adjusting line spacing for languages with complex characters, and mirroring layouts for right-to-left languages.
The goal of DTP is to produce a document that a reader in the target market would never recognise as a translation. The formatting, visual hierarchy, and overall design should feel native. This is why translation and localisation done well always treats DTP as an integral part of the process rather than an optional finishing step.
Which file formats are most likely to break after translation?
File formats that embed layout and design information alongside text are the most likely to break after translation. These include PDF, InDesign files, FrameMaker documents, PowerPoint presentations, and HTML files with complex CSS styling. Plain text or simple Word documents tend to be more forgiving, though they are not immune.
PDFs are particularly problematic because they are not designed to be edited. Text in a PDF is locked into position, and extracting it for translation and then reinserting it almost always disrupts the layout. Many clients make the mistake of sending a PDF for translation expecting a clean result, when in reality the original editable source file is always the better starting point.
InDesign and FrameMaker files are widely used for technical documentation, product manuals, and marketing materials. They handle complex layouts well, but that complexity also means there is more that can go wrong when text length changes. PowerPoint files break frequently because each slide is essentially a fixed canvas with manually placed text boxes, none of which automatically resize when content grows.
HTML and web-based formats introduce their own challenges. CSS rules often define fixed widths, heights, or character limits that work perfectly in the source language but clip or overflow translated text. Responsive designs help, but they do not eliminate the problem entirely.
How can broken formatting be prevented before translation starts?
Broken formatting can be prevented before translation starts by preparing your source files correctly, using translation-friendly formats, and briefing your language service provider on any layout constraints before the project begins. Prevention is always faster and cheaper than fixing problems after the fact.
The most effective steps to take before translation starts are:
- Provide editable source files rather than PDFs or image exports. The closer your provider gets to the original design file, the more control they have over the layout.
- Use styles and stylesheets consistently in your documents. Inconsistent manual formatting makes it much harder to apply global adjustments after translation.
- Leave breathing room in your design. If you know a document will be translated into languages that expand text, build layouts with roughly 30% extra space in text areas from the start.
- Avoid text inside images. Any text embedded in graphics needs to be recreated separately for each language, which adds time and cost. Keep text as live, editable content wherever possible.
- Share a target language brief. Let your provider know which languages are involved before design finalises. A layout that works for English and French may need significant rethinking for Arabic or Japanese.
These steps do not eliminate the need for DTP, but they reduce the amount of remedial work required and lower the risk of costly delays.
Should translation and DTP be handled by the same provider?
Yes, translation and DTP should ideally be handled by the same provider. When one team manages both the linguistic and the layout work, communication is faster, quality checks are more thorough, and the risk of errors falling between two separate workflows is significantly reduced.
When translation and DTP are split between different vendors, the handover between them becomes a vulnerability. The translator delivers text without seeing the final layout context, and the DTP specialist adjusts the layout without being able to query the translator if a text change is needed to fit the space. This back-and-forth adds time and creates opportunities for inconsistency.
A single provider who handles both stages can make informed decisions in real time. If a translated phrase is three words too long for a text box, the linguist and DTP specialist can work together to find a solution that is both accurate and visually correct. This integrated approach is especially valuable for complex documents like technical manuals, product catalogues, and multilingual marketing materials where both precision and presentation matter.
We handle translation, localisation, and DTP as a seamless end-to-end process, which is exactly why clients come to us when previous attempts at keeping these services separate have led to the kind of broken documents this article describes. If your translated documents are not looking the way they should, request a quote to see how we can help, or get in touch and we will be happy to talk through your specific situation.
Frequently Asked Questions
How much does DTP typically add to the overall cost of a translation project?
DTP costs vary depending on the complexity of the document, the number of target languages, and how well the source files were prepared. As a rough guide, DTP can add anywhere from 15% to 40% on top of the base translation cost for complex formats like InDesign or FrameMaker. Investing in clean, well-structured source files upfront is the most effective way to keep DTP costs down, since less remedial work is needed when the layout has been designed with translation in mind.
What if I only have a PDF and no access to the original source file?
Working from a PDF is possible but comes with significant limitations. A DTP specialist can extract the text, translate it, and rebuild the document from scratch in a tool like InDesign, but this reconstruction process takes considerably more time and cost than working from an editable source file. If you are in this situation, it is worth checking whether the original designer or agency still holds the source files before committing to a full rebuild — even an older version of the source file is usually better than starting from a PDF.
How do I know whether my translated document needs DTP or just minor text corrections?
A good rule of thumb is that any document intended for professional distribution — whether printed, published online, or shared with clients — should go through DTP after translation. If the translated text has caused even minor layout shifts, such as text running outside a box, font substitutions, or misaligned columns, those issues will be visible to readers and reflect poorly on your brand. Minor text corrections alone cannot fix structural layout problems; DTP is the appropriate solution for anything beyond a simple single-column Word document.
Can translation memory tools help prevent layout problems in future projects?
Translation memory (TM) tools help with consistency and speed on the linguistic side, but they do not directly prevent layout problems — that is a design and file preparation issue. However, TM tools can indirectly reduce layout disruption by ensuring that previously approved translations of recurring phrases are reused, which means text length stays predictable across updates and new versions. When used alongside well-prepared source files and a DTP workflow, translation memory is a valuable part of a streamlined multilingual content process.
What is the difference between localisation and simply translating a document's text?
Translation converts the words from one language to another, while localisation adapts the entire document — including images, colours, date formats, units of measurement, cultural references, and layout direction — to feel natural for the target audience. A translated document might be linguistically accurate but still feel foreign if local conventions have not been applied. Localisation is what makes a document genuinely usable and credible in a new market, rather than just readable.
Are there any design tools or software features that make documents easier to translate and reformat?
Yes — several design practices and software features can make a significant difference. In InDesign, using paragraph and character styles consistently (rather than manual overrides) allows global font and spacing changes to be applied in seconds rather than hours. Tools like memoQ, SDL Trados, and Phrase (formerly Memsource) integrate with common file formats to extract text cleanly while preserving layout tags. For web content, using a well-structured CMS with language-specific templates rather than hardcoded layouts will save considerable DTP effort across every language you publish in.
How should I brief a translation and DTP provider if I have strict brand guidelines to maintain?
Share your brand guidelines document alongside the source files at the very start of the project, not after issues arise. Specifically highlight approved fonts and their fallback alternatives for non-Latin scripts, any colour or logo usage rules, and examples of previously approved translated materials if they exist. The more context your provider has before work begins, the less back-and-forth is needed mid-project, and the more likely the final output is to match your brand standards across every language.
Related Articles
- How do I create a brochure in 12 languages without it becoming a layout nightmare?
- How do I make a translated document look as good as the original?
- What sustainable printing options are available for my product documentation?
- Am I required to provide my manuals in print, or is digital sufficient?
- How do you ensure inclusive localisation?