Since the end of October 2026 every article on our website goes live in Chinese and English at the same time, with the English version under /en/ and written for industrial buyers in Europe and North America. This is not a translation of the Chinese text; it is a separate workflow. The sections below describe the parts of it that actually make a difference, and why the two versions have to be published together.
The English version is not a sentence-by-sentence translation
A Chinese technical article and an English technical article do not read like the same piece of writing, and that is not a question of translation quality. The two languages address readers with different concerns. A Chinese reader is often already familiar with the machine, so the article can start with the mechanism and add a parameter afterwards. Many English readers are meeting the machine for the first time and need to know first what it does, what standard it is judged by and what the parameters are, and only then the mechanism behind them.
The result is that the English version usually leads with the conclusion and the parameters and then develops the reason. Read as Chinese it would feel abrupt; read as English it flows.
The parameters have to match word for word
This is the hardest rule in the whole workflow. If the Chinese version writes the working vacuum as -0.08 ~ -0.0999 MPa, the English version has to write -0.08 ~ -0.0999 MPa; if the Chinese version writes ≤3 ppm (GB/T 7600), the English version writes ≤3 ppm (GB/T 7600). Ranges are not collapsed into single values, units are not converted, standard numbers are not replaced, and no imperial conversion is added on top.
- Figures, symbols, units, model numbers, dimensions and standard numbers are copied over word for word; only the labels in front of them are translated.
- Temperatures are given in degrees Celsius and the values stay the same; the range separator is written as a dash and the values themselves are untouched.
- No name of any other manufacturer appears, and nothing is added that the Chinese version does not contain.
- The structure of the body text is identical to the Chinese version: the same number and the same order of headings, images, tables, lists and quotations.
None of this is a matter of style preference; these are rules that can be checked by a machine. The checking script compares the tag structure and the image attributes of the two versions item by item, and any single mismatch stops the release rather than going live with the problem still in it.
What readers of the two languages are concerned about
| Reader | Concerned with | Adjustment in the writing |
|---|---|---|
| Field engineer, Chinese | Basis for judgement and order of investigation | The symptom and the mechanism come first, with the parameters worked into the judgement |
| Procurement and asset management, Chinese | The definition of the indicators and the acceptance clauses | Emphasis on the standard numbers, the sampling responsibility and the records kept |
| Industrial buyer, English | Machine capability, specifications and the basis of compliance | The conclusion and the parameters first, the reason afterwards |
| Field maintenance technician, English | Operating sequence and method of judgement | The steps written as actions that can be carried out directly |
What publishing on the same day means
Publishing the two versions together has two practical consequences. For the search engines, the Chinese and English pages are indexed separately and each is marked with its language version, so a reader who enters the site in either language can find the other through the language switch. For the buyer, publishing on the same day means the two versions describe the same machine and the same set of parameters, and there is never a moment when one of them is out of date.
For the workflow it is only stable when the two go out together. If the Chinese version goes live first and the English version is added afterwards, there is a window in which a page points at nothing or in which the parameters do not match, and for technical content that is the state that should least of all occur.
Publishing the two versions together is not about having one more piece of content; it is about making sure that whenever one version is live, the other is already standing next to it.
