Desktop publishing in localization is the process of placing translated text into designed source files and rebuilding the layout so that localized deliverables look native, remain readable, and match the original design intent across languages. It involves adjusting fonts, line breaks, spacing, graphics, tables, and pagination to accommodate target-language text expansion, contraction, and script-specific needs before final QA or delivery.
Angel Translation editorial reference · Confirm the rendering against your source and approved project terminology.
Check source meaning → confirm the preferred term → record approved variants and references.
DTP occurs after translation and editing, especially for brochures, user manuals, packaging, e-learning modules, and web content. DTP specialists use layout applications to rebuild localized files, then return them for QA; this step is critical when text length changes and when target scripts require different fonts or direction, such as right-to-left scripts.
A frequent issue is applying the source file’s fonts to a target language that lacks those glyphs, causing missing characters or font fallback problems. Another is overlooking text expansion, which can result in clipped text, overflowing boxes, or incorrect pagination; if not caught, the localized file may be unusable for print or publishing.
Creative and consumer content needs accurate meaning as well as tone and context. Subtitles, interfaces and voice scripts also require checks for timing, character limits and pronunciation.
Provide approved terms and previous translations with the source files. Agree how variants, ambiguous wording and revisions will be reviewed. Terminology maintenance and any termbase handback are confirmed in the project scope. See the 8-step AI + expert workflow.
Employee-training video transcription and dubbing.
Read the published project →Brand documentation.
Read the published project →Published scope shows related industry experience; it does not confirm that this specific term was used or reviewed in the project.
Include the source and target languages, file types, intended use, deadline and any approved termbase. Agree handling before sending sensitive files. Acknowledged in 4 hours, quoted in 24.
Prepare an inquiry email →Content Globalization solutions →File handling →A glossary entry is not an official standard or evidence of regulatory acceptance. Confirm current requirements for your project separately.