Technical
Technical translation, operated like an expert agency
Technical documentation — user manuals, API docs, engineering specs — demands consistent terminology and precise formatting. Every tag, number, and unit must be preserved exactly.
Technical Translation Challenges
1XML/HTML tag preservation within translated text
2Code snippets and variable names must remain untranslated
3Unit conversions (metric/imperial) with precision
4Version-specific terminology consistency across releases
5Structured content (tables, lists, steps) format preservation
How the Agency Cockpit handles this
1Translatable segments extracted while preserving all tags and markup
2Tag integrity, numbers, and formatting validated automatically
3Consistent technical term usage enforced via project glossary
4Previous version translations leveraged for consistency
5XLIFF 2.0 output preserves inline formatting and metadata
What must stay consistent
These names, terms, and domain expressions must stay consistent. leapCAT proposes a glossary, shows why each term matters, and keeps approved wording aligned through the project.
Product-specific termsUI stringsError messagesAPI endpoints
What gets stricter review
Technical QA (15%) weighted higher — tag and format integrity critical