Translation memory (TM) systems — tools like SDL Trados or memoQ that store previously translated sentence pairs and suggest them for reuse — are standard practice in professional localization. Most clients who commission recurring translation work understand the basic value: consistent terminology, faster turnaround on repeated content, and lower cost per word over time.
What fewer clients realize is that TM has an equally significant — sometimes larger — impact on the desktop publishing (DTP) step that follows translation.
The DTP problem with fresh translation every time
When a translated document arrives in InDesign or FrameMaker for typesetting without TM context, the DTP engineer is working from a cold start. Every text expansion or contraction (German typically runs 20–30% longer than English; Chinese runs shorter but requires different line-break handling), every font substitution, every layout reflowing has to be resolved manually.
For a 60-page technical catalog updated quarterly, this means the DTP step takes nearly as long the second time as it did the first — even if 70% of the content is unchanged from the previous version.
How TM-integrated DTP changes the workflow
When translation and DTP operate from a shared TM, unchanged segments from the previous version are flagged and pre-placed in the layout. The DTP engineer’s job shifts from rebuild to review-and-adjust. For a document with high repetition across versions — product catalogs, equipment manuals, regulatory submissions — this can reduce DTP hours by 35–50% on revision cycles.
The compound effect is more significant over time. A client we have worked with for ten years now has a translation memory of over 4,000 terms and thousands of approved segment pairs. New catalog versions — even with new product lines added — go through DTP significantly faster than the first edition did, because the stable content carries forward automatically.
Why this matters for the export document workflow
The most common use case for TM-accelerated DTP in our client base is:
- Annual product catalog updates: 60–80% of content unchanged; updates concentrated in specifications and pricing
- Equipment manual revisions: New regulatory sections added; existing procedural content unchanged
- Multi-language simultaneous release: Same TM applied across 5–8 language versions with shared layout templates
In each case, the TM is not just saving translation cost — it is compressing the total time from “content updated” to “print-ready files across all languages.”
What a TM-integrated workflow requires
Setting it up properly takes investment at the start:
- Terminology extraction and approval: The first pass requires a structured review of domain-specific terms by the client’s technical team. This is the foundation of the termbase.
- Segment-level source document preparation: Translation-ready source files (clean, editable, ideally with XLIFF export capability) allow the TM to segment properly.
- Layout template creation: InDesign or FrameMaker master files with language-specific typographic rules (character styles, hyphenation exceptions, text frame overrides for expansion languages) that carry forward across versions.
The upfront effort is real. On ongoing programs with regular document revisions across multiple languages, it typically pays back within the first two update cycles.
For clients currently running recurring multilingual DTP without TM
If you are commissioning translation and typesetting of recurring documents — manuals, catalogs, datasheets — and your vendor is not maintaining a translation memory for your account, you are paying full cost for content that has already been translated and typeset.
We maintain dedicated TM and termbase infrastructure for every ongoing account. Contact us if you would like to discuss how this applies to your document program.