Skip to content

Technical Translation: Terminology, Units, and Version Control

Review technical translations for approved terminology, numbers, units, tolerances, warnings, and source-version changes before release.

Share

A technical translation can read well and still contain an incorrect component name, measurement, or source revision. Review terminology, technical data, and document versions separately so fluency does not conceal a specification error.

Direct Answer

Confirm the source revision, translation scope, and approved terminology before work begins. Check numbers, units, tolerances, and warnings against that source. Track later changes and assign technical approval to someone with the relevant product knowledge.

Key Takeaways

  • Source and terminology: Identify the correct revision and approved terms.
  • Technical data: Verify values, unit symbols, tolerances, and warnings; do not convert units without agreed instructions.
  • Approval: Record changes, reviewers, and the source version linked to the final translation.
Technical Translation Measurement Accuracy

1. What Should Be Prepared Before Starting a Technical Translation Project?

Start by checking the source documents, scope, and technical requirements. A short brief should identify the documents, intended users, source revisions, and approval responsibilities.

Key information to confirm includes:

  • Document types, such as user manuals, technical specifications, drawings, operating procedures, or parts lists;
  • Source and target languages;
  • Intended users, such as engineers, operators, or maintenance personnel;
  • Source document version and release date;
  • Content to be translated and excluded from translation;
  • Previously approved terminology glossaries or translations;
  • Requirements for numerical values and measurement units;
  • Required output formats;
  • The person responsible for technical approval.

Gather the source documents, approved glossaries, previous translations, intended users, target languages, and deadlines before confirming the scope.

Verifying the correct source version is particularly important. If translators work from an outdated document, the translation may be accurate at the sentence level but fail to reflect current designs, specifications, or operating procedures.

2. How Should Technical Terminology Be Standardized and Changes Controlled?

Terminology affecting component names, functions, and operating procedures should be standardized before translation begins, and any subsequent changes must be documented and approved.

In technical documentation, a word may have a very different meaning in a specialized field than in everyday language. Green Sun’s article on Japanese technical document translation provides examples of Japanese terms whose general meanings differ from their meanings in mechanical engineering. This highlights why translators must rely on subject-specific context rather than everyday definitions.

A terminology glossary should include at least the following:

FieldDescription
Source termWord or phrase appearing in the source document
Approved translationStandardized translation to be used consistently
Prohibited termTranslation or wording to avoid
ContextEquipment, component, or function
ApproverSubject-matter expert responsible for approval
Approval dateDate from which the approved term applies

If a component name changes during the project, record the old and new terms, affected documents, approver, and the revision in which the change takes effect.

Technical translation workflows can use terminology glossaries and translation memories to maintain consistency across documents. Previously approved content can also be reused in future projects or document revisions.

However, translation memories do not replace terminology glossaries. A translation memory stores previously translated segments, while a terminology glossary defines how individual critical terms should be used and records their approval status.

3. How Should Numerical Values, Units, Tolerances, and Warnings Be Verified?

Numerical values and measurement units should be treated as technical data requiring independent verification rather than simply as elements of a sentence.

Verifying measurement specifications in technical translation should cover:

  • Numbers and decimal values;
  • Negative signs;
  • Value ranges;
  • Tolerances;
  • Lengths and dimensions;
  • Temperatures;
  • Pressures;
  • Torque values;
  • Voltage and current;
  • Unit symbols;
  • Conditions associated with warnings or operating limits.

Drawings and technical specifications require careful verification of numbers, measurements, symbols, and tolerances. Automated quality assurance checks can also help identify numerical inconsistencies, measurement unit errors, missing content, and formatting issues.

Even when translators leave numerical values unchanged, those values must still be checked against the source. Errors can occur during copying, file conversion, optical character recognition (OCR), table editing, or document layout.

The NIST Guide to the SI explains unit-symbol conventions, including capitalization and plural forms. Symbols such as mm, MPa, V, and N·m should be checked as technical notation rather than edited as ordinary prose.

Therefore, symbols such as “mm,” “MPa,” “V,” and “N·m” should not be treated as ordinary text strings that can be freely modified for stylistic reasons.

4. Can Measurement Units Be Converted Without Prior Approval in Technical Translation?

Measurement units should not be converted simply because another unit is more familiar to the target audience. Any conversion must follow confirmed project requirements or established technical rules.

This is particularly important for technical specifications, drawings, operating limits, and approved values. Converting units without authorization introduces an additional layer of numerical processing that was not present in the source document.

Illustrative example: A source document specifies 25.4 mm. The translator should not independently convert this to 1 in or add both units unless the project requirements explicitly define how conversions should be handled.

If the client requests that both measurement systems be displayed, the following should be established before translation begins:

  • Which unit is the primary unit;
  • Which unit should appear in parentheses;
  • Conversion rules;
  • Number of decimal places;
  • Rounding conventions;
  • How tolerances should be handled.

This is especially important because a unit conversion may be mathematically correct, while the rounding method or number of displayed digits may still fail to meet the technical document’s requirements.

Check both the conversion and its presentation against the agreed requirements. A mathematically correct value may still use the wrong rounding or number of displayed digits.

5. How Can Translation Versions Be Tracked When Source Documents Change?

Every translation must be linked to a specific source document version, and each source revision should be compared with the previous version to identify exactly what needs to be updated.

Tracking source document revisions in technical translation can be managed using a simple table:

Source VersionDateChanges MadeTranslation VersionApproverStatus

When a new source version is received, retranslating the entire document may not be necessary. A more effective workflow is to:

  1. Compare the new source document with the previous version.
  2. Identify added, deleted, or modified content.
  3. Review the affected sentences or tables.
  4. Update the corresponding translations.
  5. Recheck terminology, numerical values, and cross-references.
  6. Release a new translation version.

Previously approved translations can be reused through translation memories. When a product changes, the revised source document can be compared with the previous version to determine which sections require translation and verification.

Beyond clearly revised passages, attention should also be paid to smaller changes, including:

  • Figure and table numbers;
  • Part numbers;
  • Product model numbers;
  • Button names or labels;
  • Cross-references to other sections;
  • Technical specifications;
  • Warnings;
  • New terminology.

Keep terminology decisions linked to document revisions. Do not apply a newly approved term to older versions unless the scope requires it.

6. Who Should Review and Approve Technical Translations Before Release?

A technical translation should only be finalized once its language, terminology, technical data, and version information have been verified by the appropriate personnel.

ISO 17100:2015 sets requirements for translation-service processes and resources to meet applicable specifications. Agree on the review activities for the project rather than treating translation and approval as a single step.

In a technical translation project, responsibilities can be assigned as follows:

Review RoleMain Responsibilities
TranslatorMeaning, terminology, and consistency
ReviserSource-text comparison, omissions, additions, and wording
Subject-matter expertTechnical specifications, functions, component names, operating procedures, and warnings
Project managerCorrect files, project scope, document versions, and approval status

Not every project requires the same team structure. The scope of review should be established from the outset based on the document type, client requirements, and level of technical expertise needed.

A pre-release checklist may include:

  • Correct source document version confirmed;
  • Translation scope verified;
  • Terminology glossary updated;
  • Numerical values checked against the source;
  • Units and tolerances verified;
  • Warnings reviewed;
  • Changes from the latest revision incorporated;
  • Subject-matter experts have approved content requiring technical verification;
  • Final translation version locked.

These are also important considerations when selecting technical translation services, rather than comparing providers solely on price or delivery time.

Conclusion

Review the correct source revision, approved terms, technical data, and final approval together. For recurring updates, maintain the glossary and change history so reviewers can identify what needs attention.

The process can be summarized as follows:

Correct Source → Consistent Terminology → Accurate Specifications → Correct Version → Appropriate Reviewer

FAQ

Q1. Can measurement units be converted without prior approval in technical translation?

Unit conversions should not be made without authorization. Any conversion must follow client requirements, applicable standards, or established project rules. If conversions are necessary, rounding conventions and formatting requirements must also be agreed upon in advance.

Q2. How should translations be managed when source documents change?

The new source document version should be identified and compared with the previous version to determine exactly what has changed. Only the affected sections should then be updated, with any related content reviewed as necessary. Each translation should clearly indicate which source document version it corresponds to.

Q3. Who should approve a technical terminology glossary?

Terms affecting component names, functions, or operating procedures should be verified by someone with product knowledge or appropriate technical authority. Translators may propose terminology, but they should not independently finalize terms that require client approval.

Q4. Do numerical values need to be checked even if the numbers are not translated?

Yes. Numerical values can be altered during copying, file conversion, optical character recognition (OCR), editing, or document layout. Therefore, checking numbers and measurement units against the source remains an essential quality assurance (QA) step.

Q5. Can a translation memory replace a terminology glossary?

No. A translation memory stores previously translated segments for reuse, while a terminology glossary defines how individual terms should be used. The two tools complement each other but serve different purposes.

Q6. Does the entire document need to be retranslated when the source version changes?

Not necessarily. If the changes can be identified precisely, only the affected sections may need to be updated, followed by verification of related content. Green Sun also compares revised source documents with previous versions to determine the scope of translation and quality checks required for document updates.

Ensure Technical Document Quality with Green Sun Japan

Working with manuals, specifications, drawings, or parts lists? Share the current source revision, terminology, and review requirements with Green Sun Japan.

Green Sun Japan provides technical translation services to help businesses manage content throughout different stages of their projects:

  • Terminology Standardization: Compile and apply terminology glossaries tailored to specific products or projects.
  • Technical Data Verification: Check numerical values, measurement units, component names, and warnings against source documents.
  • Document Update Management: Reuse approved translations and identify affected content when source documents are revised.
  • Pre-Delivery Quality Review: Perform quality checks and revisions according to the scope agreed upon with the client.

Contact Green Sun Japan to discuss your technical documents and approval requirements.

Share

Written by

Thao Huynh Thi Ngoc · Green Sun Japan

Green Sun Japan provides translation and localization between Japanese, English, Vietnamese and other Asian languages, with offices in Tokyo and Ho Chi Minh City.

Keep reading

Related Articles

Ready to talk about your project?

Tell us the language pair, the field and the deadline. We will reply with a quote and a plan.

10%OFF for first-time orders!