Metamation Developer Notes

  • Developer Notes
  • Resource Map
  • Tools
    • Code Formatting
    • Configuring Git
    • Assignments
    • Testing with Windows Sandbox
    • Single Binary Applications
    • Self-Updating Applications
  • Flux Workflow
    • Flux Workflow
    • Flux Development Style Guide
    • Release notes for Flux
    • SonarCloud analysis for Flux
    • Build a Flux SDK Program
    • Shipping Flux
    • Flux.Test
      • BasicBendAuto Test
      • LaserAuto.cs Detailed Documentation
      • Laserexample:Test1
  • Technical Notes
    • File formats
      • .FX File Format
      • Au(Gold) streams
      • .GEO File Format
      • .LST File Format
      • .LST file - technology
      • .BNC File Format
      • .WAD Files: Flux Resource Packages
      • .Curl Files: ASCII config information
    • Folders App
      • Data\Bendtools
      • Data\Machines
    • FluxCode
      • Welcome & Repo Map
      • Architecture & System Context
      • Subsystem *Bend* (Press Brake)
      • Subsystem *BCell* (Bend Cell Automation)
      • API Maps
      • Data Model Catalog
      • Design Patterns -- A Reader's Guide
      • Tests and Golden Paths
      • Guided Code Tours
      • CAM Glossary with Code Mapping
      • Assignments
      • Flux Onboarding Handbook
    • Data flow
      • Part
        • Part.Dwg
        • Part.Load
        • Part.Load to Part.Dwg
      • BendTech.cs
      • Bend Technology
      • Laser Cutting Technology
    • LTS (Long term support mechanism)
    • Machine ID Scheme
  • FluxTester
    • Commands and Scripts
    • Command Cookbook
    • Script Commands
    • BendTooling.cs Test Inventory
    • LaserTooling.cs Test Steps
    • Fluxtester Recipe Book
    • Nesting.cs Overview
    • Nesting.cs Recipe Book
    • Job.cs Overview
    • Job.cs Recipe Book
  • Software license
  • 3d party software
    • Python
  • Documentation
    • Bento documentation
      • Structure of a Bento page
      • Attributes
    • Software
      • Software Requirement
      • Installation
      • Git workflow for documentation contributors
    • Quick start guide
    • Workflow
      • Roles and responsibilities
      • Analyze
      • Edit
      • Proofread
      • Pre-Publish
      • Publish
      • Release cycle
      • Information required for Documentation Team
      • Checklist for Documenters
    • Styleguide
    • Flavoring
    • Translation
      • Ordering translation for a new document
    • Citations
    • Annotation
Documentation
/
Translation

Translation

TINC software products are translated into 23 international languages.

Overview of TRUMPF software products are listed and the requirement for translation are marked in the following excel sheet:

Click here - Translation requirements list

For better viewability, open the excel sheet in the desktop application.

Translation is triggered twice a year for software products that require it. After each cycle, the excel sheet above is updated with the translation status of each product. Each cycle is recorded as a separate sheet, labeled Q1 or Q2 followed by the year — for example, Q1 2026 refers to the first translation cycle of 2026.

There are two translation activities handled at TINC.

  1. Translation of the UI elements used in the software supported by online Xlate tool.

  2. Translation of the bento documentation which has UI elements embedded in the documents.

Xlate tool is used to introduce citations in the bento documentation and these must exactly match the UI elements used in the actual software. This ensures that the translated documentation is consistent with the software UI and provides a seamless user experience for users in different languages.

Translation for a new document

For any new software product created at TINC, the initial version of the document is created in English language and the entire asciidoc files are sent to the translation agency for translation into all the supported languages. The translated asciidoc files are then stored in the corresponding GitHub documentation repositories language wise.

AI assisted translation using Copilot

For subsequent translation cycles, the diff between the previous and current versions of the asciidoc files is captured and translation tags are inserted to mark new or modified content.

##Check translation start##

This is a new or modified content that needs to be translated.

##Check translation end##

The tagged content is then translated into the required languages and added to the corresponding language files in the documentation repositories.

NPI review process

Review of the AI assisted translated content is done by the NPI team to ensure that the translation is accurate and consistent with the software UI. The NPI team also provides feedback to documentation team for any necessary changes or improvements in the translation process. This review process helps to maintain the quality of the translated documentation and ensures that it meets the needs of users in different languages.

Once the review is done and review comments are addressed, the translated content is published and made available to users in different languages. This ensures that users can access the documentation in their preferred language and have a better understanding of the software features and functionalities.

Review of the translated content

In order to make the review process simpler, the HTML file generated using Bento is then converted to a simple word document format and shared with the NPI team for review. This allows the NPI team to easily identify the translated content with the original English version and provide feedback on any discrepancies or issues they find. The NPI team can also suggest improvements to the translation to ensure that it accurately reflects the software features and functionalities.

Add review comments in Word document

The reviewer must use the track changes feature in the word document to provide feedback on the translation. This allows the documentation team to easily identify the changes suggested by the NPI team and make necessary adjustments to the translation accordingly. The review process is crucial to ensure that the translated content is accurate, consistent, and meets the needs of users in different languages.

  • Order translation

Contents

  • Translation for a new document
  • AI assisted translation using Copilot
  • NPI review process
  • Review of the translated content
  • Add review comments in Word document
Flavoring Ordering translation for a new document

      Copyright © 2025 TRUMPF Metamation. All rights reserved.

    Compiled by Bento