Technical Translation

---
name: technical-translation
description: "Translates technical documents (manuals, specs) with terminology management, QA, and style-guide compliance for accurate, consistent results."
metadata:
  tags: "writing-literature, translation, technical-translation, localization, terminology-management, quality-assurance, cat-tools"
  source: "https://skilldb.dev/skills/translation-localization-skills/technical-translation"
  pack: "translation-localization-skills"
  category: "Writing & Literature"
---

# Technical Translation

## When to use this skill
Use when the user says things like:
- "Translate a technical manual or specification."
- "Localize engineering documents for a new market."
- "Develop and enforce domain glossaries."
- "QA safety-critical translations with expert review."


## Core Philosophy

Technical translation prioritizes accuracy and clarity above all. A mistranslated technical
manual can cause equipment failure, safety hazards, or legal liability. The technical
translator must combine linguistic skill with domain expertise — understanding not just the
words but the concepts, processes, and standards that underpin the content. Consistency in
terminology is not optional; it is the foundation of usability.

## Key Techniques

- **Terminology management**: Build and maintain glossaries of approved terms for each domain and client.
- **CAT tool utilization**: Use computer-assisted translation tools for consistency and efficiency.
- **Source text analysis**: Identify the document type, audience, and purpose before translating.
- **Domain research**: Consult reference materials, standards, and parallel texts in the target language.
- **Quality assurance**: Run automated and manual checks for terminology consistency and completeness.
- **Style guide compliance**: Follow client and industry style guides for formatting and conventions.

## Best Practices

1. Never guess at technical terminology. Research or ask the client when uncertain.
2. Use approved glossaries consistently. A valve must always be called a valve, not sometimes a tap.
3. Preserve the structure and formatting of the source document precisely.
4. Translate units, measurements, and standards according to target market conventions.
5. Verify numerical accuracy — transposed digits in specifications can have serious consequences.
6. Understand the technical process being described. Translation without comprehension introduces errors.
7. Have domain experts review critical translations, especially for safety-related content.

## Common Patterns

- **Translation memory leverage**: Reuse previously translated segments for consistency and efficiency.
- **Termbase-driven workflow**: Glossary created before translation begins, enforced throughout.
- **Review cycle**: Translation → self-review → peer review → client review → final delivery.
- **Parallel text research**: Studying equivalent documents already published in the target language.

## Anti-Patterns

- Translating technical terms literally without verifying the standard target-language equivalent.
- Ignoring the existing translation memory and creating inconsistencies with previous deliveries.
- Skipping domain research, producing translations that are linguistically correct but technically wrong.
- Reformatting or restructuring the document beyond what localization requires.