Publishing services
Multilingual Desktop Publishing Services
Techniwords rebuilds your translated manuals, catalogs, and datasheets in InDesign, FrameMaker, and the other tools your documents were authored in, so every language edition matches the source layout page for page. You send packaged source files and get back fully typeset editions, print-ready PDFs included, with nothing left for your design team to fix.
Every project ships with the working IDML, INDD, or FrameMaker files plus a press-quality PDF. Your documents stay yours, and you are never locked into our workflow.
Kinsoku shori rules in Japanese, correct character-level line breaking in Chinese, and word-boundary breaks in Korean. No inserted spaces, no orphaned punctuation.
Light formatting is part of the translation rate. Full page production is quoted by the hour, with a per-page estimate you approve before work starts.
What Our Multilingual Desktop Publishing Service Covers
Translation gives you the words. Desktop publishing puts them back on the page. When a 180-page maintenance manual comes back from translation into German, the text is 30 percent longer than the English it replaced, tables have burst their columns, callout arrows point at nothing, and the index page numbers are wrong. Our multilingual desktop publishing services close that gap: we take the translated text and produce finished, formatted language editions inside your original authoring files.
The service covers page make-up and reflow after translation, replacement of embedded screenshots and figure labels, regeneration of tables of contents and indexes, typographic adaptation for languages that follow different composition rules, and final output as print-ready or web-optimized PDF. It applies whether we did the translation or you bring translated text from elsewhere and only need production. Most clients bundle the two, because the same team managing both removes an entire round of file handoffs.
We have been producing multilingual technical documents for 15 years from our base in Texas, and DTP has been part of the offer from the first year, for a simple reason: a technically accurate translation delivered as raw text still costs your team days of layout work. If the project also involves adapting units, standards references, or regional conventions, our technical document localization service handles that layer, and this page's production work sits on top of it. You can see how the two fit together with the rest of our services.
From Packaged Source to Print-Ready File: The Workflow
Every DTP project follows the same eight steps. The sequence matters, because most layout disasters we are hired to repair come from doing these out of order, usually by translating in a PDF and retyping into the layout afterward.
- Intake and preflight. We open your packaged files, verify links and fonts, flag missing assets, and note any text living inside images.
- Structured export. Text is extracted through IDML or MIF filters into our translation environment, with formatting tags protected so bold, cross-references, and index markers survive the round trip.
- Translation and independent revision. The linguistic phase runs under our ISO 17100-compliant process, with a second specialist reviewing every segment before anything touches a page.
- Reimport. The translated text flows back into the original file, styles intact, at which point the layout is broken by design: text has grown or shrunk, and pages need rebuilding.
- Page make-up. A DTP operator reflows every page, adjusts frames and tables, repositions callouts, and applies the language's composition rules.
- TOC, index, and cross-reference regeneration. Automated lists are rebuilt so page references match the new pagination.
- In-context proof. A linguist rereads the formatted pages, because errors invisible in a translation grid, like a heading truncated mid-word, only appear in layout. You receive an annotated approval proof PDF.
- Final production. After your sign-off, we output final PDFs and package the sources.
Step 7 is the one most agencies skip. We treat it as non-negotiable, since a proof cycle costs an hour per 40 pages and a reprinted catalog costs thousands of dollars.
Text Expansion, Reflow, and the Rules We Apply
Languages do not occupy the same space. German and Russian typically run 25 to 35 percent longer than English; Spanish and French add 15 to 25 percent; Chinese contracts by 30 to 40 percent, leaving pages that look strangely empty if nobody rebalances them. Expansion is not a nuisance to absorb by shrinking the font. It is a design problem with rules.
Our reflow standards for technical documents: body text never drops more than half a point from the source design without written approval. Warnings and cautions stay on the same page or spread as the step they govern, a principle borrowed from ANSI Z535.6 practice for collateral safety messages. Part numbers, model codes, and torque values never hyphenate across lines. Tables keep their column logic; when a German compound noun outgrows a column, we rework the column widths or rotate the header rather than letting one cell force a nine-point font on the whole table. Hyphenation dictionaries are switched per language, because InDesign left on English hyphenation will happily break a Finnish word anywhere.
Plan for growth before translation, not after. A page designed at 85 percent text density in English has no room for German at +30 percent. When we handle a document family repeatedly, we feed density guidelines back to your authors, and the next edition reflows in half the hours.
Where page-for-page correspondence matters, as with user manuals that service teams reference by page number across languages, we hold pagination to the source at the cost of extra fitting work, and we tell you up front which pages will be tight.
CJK Typography Without the Usual Mistakes
Chinese, Japanese, and Korean expose weak DTP work faster than any European language, because their composition rules are invisible to anyone who cannot read them. Chinese is written without spaces between words; a line may break between almost any two characters, but certain characters may not start a line and others may not end one. Japanese formalizes this as kinsoku shori, the rule set that keeps small kana and closing punctuation from landing at a line head. Korean uses spaces, and lines should break at them, not inside a word as default justification settings often force.
Our CJK pages are set by operators who work in these scripts daily, with composer settings, punctuation hanging, and line-breaking classes configured per language, then checked by a native reader on the formatted proof. The difference shows in dense documents first. A specification table set with wrong break rules scatters lone brackets at line heads; a well-set one reads cleanly at a glance. This matters most on export documentation into Simplified Chinese, where a US manufacturer's manual is often the first printed contact a buyer has with the brand. For Korean projects, the same applies to spacing and the mixed use of Hangul with Latin part numbers; learn more here.
Right-to-left production for Arabic and Hebrew follows its own path: mirrored master pages, reversed reading order for step sequences and table columns, and careful handling of numerals and embedded English terms that still read left to right. We scope RTL work explicitly at quote time because the mirroring hours are real and should be visible in the price.
Fonts, Licensing, and Character Coverage
The font question sinks more multilingual print jobs than any other production detail. Your brand typeface probably does not contain Chinese glyphs, and possibly not even the full Latin Extended set that Polish or Turkish require. Substituting whatever the operator's system suggests produces tofu boxes, silent fallbacks, or a license violation embedded in your PDF.
Our approach has three layers. First, a coverage audit at preflight: we test your specified fonts against the actual character inventory of the translated text and report gaps. Second, licensed pairings: for CJK and other scripts we maintain licensed families chosen to sit well next to common corporate typefaces, and where your brand team has already licensed a global family, we use exactly that. Third, the Noto family as the documented safety net: when no licensed match exists and the budget excludes buying one, Noto's coverage across scripts gives a clean, print-safe result at no license cost. Every substitution is recorded in a font map delivered with the project, so your next print vendor knows precisely what to install.
File Formats We Work In
We work in the native format of your source document whenever one exists. The table below shows the most common inputs and what you get back.
| Source format | How we process it | Deliverables |
|---|---|---|
| Adobe InDesign (INDD, IDML) | IDML round-trip, styles and markers preserved | Packaged INDD + IDML, PDF/X, web PDF |
| Adobe FrameMaker (FM, MIF, book files) | MIF filter, conditional text and variables kept | FM book, MIF, PDF outputs |
| Microsoft Word / PowerPoint | Direct processing, styles honored, fields relinked | Formatted DOCX / PPTX, PDF |
| Adobe Illustrator (AI) figures | Text layers translated and refit per figure | AI files + linked assets updated |
| Structured XML / DITA | Translation at the source, output via your pipeline or ours | Translated XML, generated PDF |
| PDF only (source lost) | Layout recreated, scoped and quoted separately | New editable source + PDF |
Graphics deserve a specific word. Technical documents hide text in figures: dimension labels, screenshots of software, scanned nameplates. At preflight we inventory this embedded text, and you decide per category whether it gets translated in the artwork, handled through a numbered legend, or left in English. Nothing is discovered on page 143 during final proof.
Deliverables: Approval Proof, Print Files, and Sources
A DTP project ends with a package, not a single PDF. The standard delivery contains three tiers. The approval proof comes first: a screen-resolution PDF with our queries annotated, which functions as your sign-off document. After approval, we generate production files: PDF/X-1a:2001 or PDF/X-4 depending on what your printer specifies, with bleeds, crop marks, and embedded fonts verified in preflight, plus a lighter optimized PDF for download portals and service tablets. Finally, the source package: the full working files, linked assets, and the font map described above.
For catalog work feeding both print and e-commerce, we can additionally return the translated text as structured data extracted from the final layout, so your PIM system receives exactly the wording that went to press. Teams producing a product catalog translation in four or five languages each year tend to find that this one deliverable pays for the DTP line on its own by ending the copy-paste reconciliation between print and web.
How DTP Is Priced, and When It Costs Nothing
Most agencies fold DTP invisibly into the word rate, which means simple jobs subsidize complex ones and nobody can check the math. We split it instead. Light formatting is included in the translation price: Word and PowerPoint documents with standard styles, straightforward reflow, no charge and no line item. Full page production in InDesign or FrameMaker is billed hourly, currently $65 to $85 per hour depending on script complexity, with a per-page estimate stated in the quote. Typical technical material runs 4 to 6 pages per hour for European languages and 3 to 5 for CJK; dense technical datasheets with parameter tables sit at the slower end, and running text at the faster end.
Because the estimate is per page and visible, you can make real decisions: print languages get full production, while a language used only for internal reference might get clean reflow without fine typography, at a fraction of the hours. When the source design leaves no room for expansion, we say so at quote time and price the rework honestly rather than absorbing it into a padded word rate.
Where This Service Earns Its Keep
The heaviest users of our DTP capacity are manufacturers publishing operator and parts documentation in many languages at once. Last year a crane attachment manufacturer sent us a 240-page InDesign parts catalog for Korean and Simplified Chinese editions: 60 tables, 300 callout labels in Illustrator figures, and a hard requirement that page numbers match the English edition their dealers train against. The Chinese text contracted enough to leave 30 pages visibly sparse, so we rebalanced figure sizes page by page instead of letting white space accumulate. Both editions shipped as PDF/X-4 with matched pagination, and the follow-up edition a year later took 40 percent fewer production hours because the density guidelines were already in place.
The same mechanics apply across sectors we serve, from heavy machinery OEMs with operator manuals in eight languages to instrument makers whose entire sales collateral is tables. As a member of ATA and GALA, we also take production-only work handed off by other language vendors when a project outgrows their layout capacity; the source package requirements are identical either way.
Multilingual DTP: Questions We Hear Most
Do you deliver the InDesign source files, or only PDFs?
Both, always. Every project closes with the packaged INDD and IDML files, all linked assets, the font map documenting any substitutions, and the final PDFs. We do not hold sources hostage to keep your next edition captive. If your brand team or print vendor wants to take over the files the day after delivery, they can open the package and work immediately. The only exception is fonts we license ourselves, which we identify by name so you can license them on your side.
How do you handle line breaks in Chinese, Japanese, and Korean?
Each language gets its own composition settings, never a copy of the English ones. Chinese breaks between characters under prohibition rules for punctuation, so no spaces are ever inserted to force justification. Japanese follows kinsoku shori, keeping forbidden characters off line heads and line ends. Korean breaks at word spaces only. After page make-up, a native reader checks the formatted proof specifically for bad breaks, orphaned brackets, and truncated headings, because these faults are invisible to operators who do not read the script.
What if our brand fonts do not support the target language?
We find out at preflight, not at page 90. The coverage audit tests your fonts against every character in the translated text. Where gaps exist, we propose a licensed family that pairs visually with your brand typeface, or the Noto family as a no-cost, print-safe alternative with wide script coverage. You approve the pairing before typesetting starts, and the substitution is recorded in the delivered font map so future vendors reproduce the same result.
How is multilingual desktop publishing priced?
In two visible tiers. Light formatting, meaning Word or PowerPoint reflow with standard styles, is included in the translation rate at no charge. Full production in InDesign or FrameMaker is billed at $65 to $85 per hour, with a per-page estimate in the quote: typically 4 to 6 pages per hour for European languages, 3 to 5 for CJK or heavy tables. The estimate is itemized separately from translation, so you can compare it, trim it, or assign print languages and reference languages different levels of finish.
How long does DTP take on a 200-page catalog?
Count production separately from translation. Once translated text is approved, a 200-page catalog typically needs 6 to 8 working days per language for page make-up, plus 2 days for the in-context proof cycle and corrections. Languages run in parallel with separate operators, so three languages finish in roughly the same calendar window as one. Compressed schedules are possible by splitting the document between operators against a shared style sheet, which we do routinely for trade-show deadlines.
Can you work from a PDF if we lost the source files?
Yes, though it changes the job. We rebuild the document as a new editable source, recreating styles, tables, and figure callouts before translation even starts. Reconstruction is scoped and quoted as its own line, typically adding 30 to 60 percent to production hours depending on density. The upside is permanent: you end the project owning clean source files, so every future language or revision starts from a real document instead of another PDF excavation.