Terminology governance · pipeline demo
From a raw manual to Chinese and English outputs: a term is registered once, body text only carries references, and release checks compare the same six numbers every time.
Press “Run demo” to walk the pipeline
// terms.json — single source of truth [ { "id": "battery_module", "zh": "电池模块", "en": "battery module", "status": "preferred", "category": "hardware", "blocked": ["battery pack", "battery assembly"] } ]
The battery module must be replaced.
Before using the gimbal, make sure the gimbal is calibrated.
Tap the Return to Home button.
若 电池模块 温度超过 40℃,应停止操作。
电池模块 不得在高温下充电。
If the battery module temperature exceeds 40°C, stop the operation.
Do not charge the battery module at high temperature.
How Chinese and English both benefit
Chinese is the source; English is the main output. Consistency between the two is where terminology governance actually pays off.
Chinese · source governance
Terms and sentence patterns are locked while writing, before translation starts.
- Three variants merged into one preferred term
- One action per sentence, no ambiguity
- Long sentences flagged in real time
- Safety warnings must state risk, consequence and mitigation
English · output verification
Translation quality is decided by the Chinese source and enforced by the termbase.
- Terms are locked during translation, not left to the translator
- Sentence length and wording follow Simplified Technical English
- Residual Chinese in English output is blocked
- UI button labels match the app resource files word for word
How this differs from a generic termbase
A termbase alone is not an advantage. The advantage is the combination: terms share the content source, body text only references, usage drives publishing, and checks are repeatable.
Any generic terminology tool can do this
- Central glossary management
- Term candidate extraction
- Terminology consistency checks
- Blocked-term checks
- Glossary export
What this design adds
- Terms share the content source and version: terms.json derives everything
- References only in body text: change a term once, translate it once
- Usage drives publishing: unused terms never enter the glossary
- Checks are repeatable: the same six numbers on every commit