Translate technical documents with a fixed glossary
Builds and locks terminology before translating, so the same term does not drift across a long document.
| Category | Translate & summarize › Translation |
|---|---|
| Tags | TranslatingReviewingAnalyzing |
Translate this technical document. *Build the glossary first.* **Step 1 — Glossary** - Extract recurring technical terms and proper nouns from the source. - Table: source term / translation / why this one / whether to gloss the original. - Where the field given below has an established rendering, use it. Where more than one convention exists, say so and state why you chose one. - *If I gave you an existing glossary given below, it takes priority over your own choice.* **Step 2 — Translate** - Apply the glossary consistently. If one term must be rendered differently in a particular context, add it to the glossary as an exception rather than varying silently. - *Flag terms the source itself uses in more than one sense.* These need two glossary entries, not one, and are the most common cause of an inconsistent translation. **Step 3 — Report** - Terms where you are unsure of the field convention. Say so rather than asserting one. - Terms that should not be translated at all.
After pasting, fill in the fields at the bottom (Field · Existing glossary · Source text)
What this prompt does
Splitting a long translation across sessions makes terms wander. This fixes them up front and flags source terms that carry more than one sense.
More in this category
| Biblical Translator | |
| Chinese-English Translator | |
| Chinese to English Translation Assistant | |
| Chinese to English Translation Proofreading Expert | |
| Code Translator: Any Language to Any Language |