Multilingual DTP
Multilingual DTP & Localization
Make every language version look native and match the source — RTL, CJK and Indic scripts handled by a specialist in-house production team.
Translation makes words readable; DTP makes the document usable
A translated file is rarely ready to publish. German and Finnish run longer and overflow layouts; Arabic, Hebrew and Urdu run right-to-left and flip tables and callouts; CJK scripts need their own line-breaking; figures, captions and cross-references all move. Multilingual DTP rebuilds the page so the translated document is accurate, consistent and native-looking — not just translated.
What we handle
- Right-to-left (RTL) — Arabic, Hebrew, Urdu, Farsi: contextual shaping, bidirectional text, kashida justification, mirrored tables and figures (see our Arabic & RTL typesetting guide).
- CJK & double-byte — Chinese, Japanese, Korean line-breaking and composition.
- Indic scripts — Hindi, Tamil, Telugu, Bengali, Marathi and more.
- European languages — with text-expansion handling so nothing overflows.
- Document types — IFUs, packaging and labeling, manuals, brochures, training/eLearning, clinical and scientific documents, books and journals.
Translation-first agency vs B2K
| Aspect | Translation-first agency | B2K (publishing-first) |
|---|---|---|
| DTP role | Final step, “formatting restored” | Core craft, specialist production team |
| Regulatory publishing | Usually outsourced | In-house eCTD/NeeS under one roof |
| STM / XML | Rarely | JATS/BITS XML-first production |
| Verification | Linguistic review | Read-free comparison against source |
| Delivery model | Often subcontracted | In-house only, one quality bar |
Source-matched delivery
Every language version is rebuilt to mirror the approved source page for page, then checked with read-free verification — comparing the typeset file element by element against the source — so errors are caught even in scripts the reviewer doesn’t read. Output is delivered print-ready and, where needed, as accessible (PDF/UA-aware) files and web formats.
Request a free sample or pilot
Send us a sample document (or tell us the languages, formats and deadline) and we will scope the work, run a short pilot, and commit to a date we can hold.
Request a sample →Frequently asked questions
What is multilingual DTP?
The layout and typesetting of translated documents so each language version matches the source and looks native, handling text expansion, RTL/CJK scripts, reflowed tables and cultural conventions.
Why can't we just use the translated file as-is?
Translation changes text length and direction; without DTP, layouts overflow, tables and figures misalign, and RTL/CJK text breaks incorrectly.
Do you handle Arabic and other right-to-left languages?
Yes - Arabic, Hebrew, Urdu and Farsi, with correct contextual shaping, bidirectional text and mirrored layouts, verified by native review.
Which scripts and languages do you cover?
40+ languages across RTL, CJK, Indic and European scripts.
Can you match the translated version to our source layout exactly?
Yes; we rebuild each version page for page to mirror the approved source.
Do you produce accessible output?
Yes; we produce PDF/UA-aware tagged output and accessible EPUB from XML-first workflows where required.
Is the work kept in-house?
Yes; B2K does not subcontract. One team handles the whole batch to one quality bar.
How fast can you turn around a large multilingual batch?
We run 24x6 and commit to an agreed date; as a benchmark we delivered 1,626 pages across 394 files in 3.5 days.