
- Table of Contents
-
- 1. A New Translation Workflow Supporting Multilingual Deployment of Technical Documents
- 2. Background of Adopting AsciiDoc and Technical Advantages
- 3. Translation Workflow Utilizing Phrase TMS
- 4. Key Points in Multilingual Expansion
- 5. Expectations for Introducing Translation Proxy
- 6. Summary
- 7. FAQ
💡Overview of This Article
In this case study, technical documents in AsciiDoc format were directly imported into Phrase TMS, translated from Japanese to English, and then expanded into 9 languages based on English. We introduce an initiative that reduced the previously necessary file conversion process and improved efficiency in translation work and revision handling by finalizing the English manuscript before multilingualization.
1. A New Translation Workflow Supporting Multilingual Deployment of Technical Documents

Our company supports the translation and localization of technical documents across various fields. This case introduces a multilingual deployment project targeting technical documents created in the AsciiDoc format.
In this project, we carried out large-scale localization that included translation from Japanese to English, followed by deployment into nine additional languages using English as the master language.
A distinctive feature was the adoption of AsciiDoc as the foundation for document creation. Unlike traditional Word-based manual production, a document management method closer to software development was employed, requiring a new approach to the translation process.
Additionally, we utilized Phrase TMS for translation and built an efficient workflow that leverages its compatibility with AsciiDoc. A major feature of this project is the optimization achieved from both the technical documentation production and localization perspectives.
2. Background of Adopting AsciiDoc and Technical Advantages

AsciiDoc is a lightweight markup language that allows documents to be written in plain text.
While offering the ease of editing with a text editor, it can manage structured information such as headings, tables, images, and links, making it widely used in recent years in the fields of software development and technical documentation.
Traditional formats like Word are excellent as final manuscripts, but when managing large-scale technical documents over the long term, update history and difference management can become challenges. On the other hand, AsciiDoc allows for managing the content itself in a structured way, making it a format highly compatible with technical documentation.
3. Translation Workflow Utilizing Phrase TMS

Our company usually uses Trados as the CAT tool for translation.
However, for this project, we adopted Phrase TMS instead of Trados.
The basic features of Phrase TMS and the differences from CAT tools are explained in detail in the following article.
One of the major reasons is support for the AsciiDoc format (.adoc).
Trados, which is commonly used by our company and is generally standard in the industry, cannot directly read AsciiDoc files and requires prior conversion to formats such as XML.
Of course, handling files in that format is also possible, but additional conversion and verification work will occur, potentially increasing operational workload.
On the other hand, Phrase TMS can directly import AsciiDoc files without any conversion work. Although there are some points to be aware of, it can be handled much more smoothly compared to Trados, allowing us to build a simpler translation workflow.
Also, in actual operation, there were the following differences compared to Trados.
* This is from the perspective of this project.
| Perspective | Trados | Phrase TMS |
|---|---|---|
| File Support | .adoc is not supported by default (preprocessing is required) | Handling of AsciiDoc is relatively easy |
| Usability | High functionality but requires proficiency | Simple and intuitive |
| Performance | Dependent on local environment | Lightweight and operates smoothly |
For features of each CAT tool and points to consider when selecting, please also see the following article.
>Related Blog: Professionally Selected! Top 5 CAT Tool Comparisons – What Points Should You Choose?
4. Key Points in Multilingual Expansion

In this project, we adopted a workflow where the Japanese original text is first translated into English, and then the English version serves as the basis for expansion into nine languages.
An important point at this stage is to finalize the translated manuscript at the English stage.
If revisions are made after translation, the reflection work must be done for all nine languages. This increases both cost and workload, and there is also a risk of errors occurring.
If all changes are fully reflected at the English stage, the process can proceed smoothly when multilingual expansion is carried out.
The approach to multilingual deployment based on English and key points when requesting translations are also explained in detail in the following article.
5. Expectations for Introducing Translation Proxy

The client for this project is considering the introduction of a translation proxy as a future prospect.
A translation proxy is a system that detects content updates on websites or applications and automatically links them to the translation workflow.
Traditionally, file extraction and translation requests were required each time an update occurred, but by utilizing a translation proxy, it becomes possible to manage multilingual content in a manner closer to real-time.
If the implementation is realized, the following effects can be expected.
• Automation of update tasks
• Reduction of operational burden from manual work
• Shortening of lead time from translation request to publication
• Realization of continuous localization
• Improvement in the speed of global deployment
We believe it offers great value, especially for technical documents and online manuals that undergo frequent updates.
Our company is conducting research on companies that support translation proxies.
6. Summary
In the case introduced this time, we efficiently achieved multilingual deployment by combining technical document creation using AsciiDoc with translation via Phrase TMS.
In particular,
• Structured document management with AsciiDoc
• Smooth translation workflow with Phrase TMS
• Deployment in 9 languages using English as the hub
This combination proved to be highly effective for localizing large-scale technical documents.
As methods for creating technical documents evolve, new approaches are also required for translation and localization. Our company will continue to support our clients' global expansion by combining translation technology with document management technology.
Furthermore, in the future, we aim to incorporate new mechanisms such as translation proxies to realize a more efficient and sustainable localization environment.
For multilingual deployment of technical documents and manuals, please consult Human Science
At Human Science, in addition to translating technical documents and manuals, we support the design and operation of translation workflows tailored to target languages, document formats, and update methods. Please feel free to contact us about multilingual deployment using structured documents like AsciiDoc and Phrase TMS.
Related Services
7. FAQ
- QWhat are the benefits of using Phrase TMS for AsciiDoc translation?
- QCan AsciiDoc tags and formatting be preserved during translation?
- QWhat are the points to keep in mind when expanding into multiple languages based on English?










