A danmei translation style guide for honorifics, era titles, censorship-era euphemisms, and untranslatable tropes — a decision framework, not one standard.
A danmei translation style guide answers one question per term: romanize it, translate it, or gloss it? The rule of thumb: romanize texture, translate information, gloss what has no equivalent. This guide turns that into a rule set — one decision per term class, plus a style sheet you can build in about 30 minutes. No single standard is declared.
Two problems hide behind "translation quality." The first is mechanical: names and terms must stay identical across 200 chapters — engines solve that with named entity recognition and per-novel glossaries. The second is editorial: should this term stay in pinyin, become English, or get a one-time note? No engine answers that, because no answer fits every novel and audience.
Danmei makes the editorial layer unavoidable: the genre packs an address system that encodes relationships (shizun, shixiong, gege), era titles that encode rank (dianxia, bixia), and a euphemism layer born from censorship-era publishing. Each is a style decision before it is a translation decision.
Division of labor: the AI translation workflow guide covers session mechanics — pronouns, register, platform steps — and my MTL comparison documents failure modes. This style guide sits one layer up: the editorial rules you apply first.
Three options cover every term.
Romanize keeps the pinyin: shizun, dianxia, gege. You keep relationship texture — the word itself carries the social structure. You pay in comprehension: readers who do not know the term stop.
Translate renders an English equivalent: Master, Senior Brother, Your Highness. You gain fluency and lose texture — English equivalents flatten distinctions the Chinese keeps, so shifu and shizun both collapse into "Master."
Gloss keeps the meaning and adds a one-time note — "white moonlight (白月光)" plus a short parenthetical on first use. The middle path for culture words with no equivalent.
| Decision | Keeps | Costs | Default for |
|---|---|---|---|
| Romanize | Relationship texture | Reader comprehension | Core address terms, fandom vocabulary |
| Translate | Fluency | Texture and register | Functional titles, plain nouns |
| Gloss | Both, once | One note in the text | Culture words with no equivalent |
The test: does the term carry information or relationship texture? If a dictionary lookup returns the full meaning, translate it. If the term encodes who respects whom and who is close to whom, romanize or gloss it. Fan-translator glossaries follow this split: Spicy Chicken Translations' honorifics glossary, published in 2019, renders functional titles like 陛下 as "Your Majesty" and relationship terms like 师兄 as the descriptive "Senior (Martial) Brother." CVM Sekai's shifu and shizun explainer puts it in one line: "the title is storytelling."
Three disciplines keep any choice consistent: first use locks the rendering, switches are events, and uncertainty gets flagged.
The address system is where danmei translations most often flatten what the source carefully builds. Start with the most confusing pair: 师父 (shifu) and 师尊 (shizun).
They are not synonyms. Shifu reads closer to a familial master — the warmth of a teacher who raised you. Shizun carries reverence and distance; the character is more authority than family. That register difference is exactly what disappears when both render as "Master."
The switch is the stronger signal. When a character moves from shizun to shifu, or from a title to a given name, the relationship changed — CVM Sekai notes such a switch signals deep emotional bonding. Translate the words and keep the switch; flatten it and you have removed a plot beat. English readers do get confused: r/2HA_immortality has a long-standing thread asking when shizun is used.
The family metaphor extends sideways: 师兄 (shixiong), 师弟 (shidi), and 师姐 (shijie) treat the sect as one household. "Senior Brother" keeps the hierarchy and loses the intimacy the romance leans on. 哥哥 (gege) is intimacy first, kinship second.
The licensed-edition data point: Seven Seas kept shizun in the English title of its flagship license, The Husky and His White Cat Shizun, rather than rendering it "Master"; the licenseddanmei roster (updated 2026-08-02, as of August 2026) lists the series complete across 11 volumes. Pinyin-first is not fringe.
This guide's rule: core address terms stay in pinyin with a first-use gloss, and every register switch must survive translation. If a term is doing plot work — it always is — do not flatten it.
Era titles translate cleanly: 殿下 (dianxia) → Your Highness, 陛下 (bixia) → Your Majesty, 大人 (daren) → Sir or My Lord. The mapping is functional — both sides signal rank. But Chinese honorifics are a subsystem, not a look-up table: they encode status, generation, and self-deprecation, as speakers lower themselves while raising the other party. "Your Highness" carries the rank and erases the rest.
Some titles carry weight beyond their dictionary meaning. Dianxia is the canonical example: in the MXTX fandom, Xie Lian being addressed as dianxia became shorthand for his whole character. Such titles earn pinyin-plus-note treatment.
Default: functional equivalence — titles with narrative or fandom weight get pinyin plus a first-use gloss. The ancient-romance translation guide keeps a comparable title table of functional equivalents.
攻 (gong) and 受 (shou) rarely appear in dialogue; they live in tags, blurbs, and metadata. That changes the decision: in metadata, keep the pinyin — danmei readers are as fluent in these terms as English readers are in "top" and "bottom," and they are load-bearing for finding what to read. Fanlore's record of Chinese-speaking fandom documents 0 and 1 mapping to bottom and top and CP meaning pairing; the wider vocabulary adds 主攻/主受 for gong-centric and shou-centric narrative perspective, and 互攻 for pairs who switch roles. In prose the audience decides: danmei-native readers tolerate pinyin; a general romance reader needs top and bottom. Write the choice into the style sheet instead of improvising per chapter.
The split is worth naming: Iris Liang's explainer on gong and shou covers what the words mean to readers; this guide covers what to do with them in translation.
The euphemism system danmei writers developed under platform self-censorship is the layer English coverage almost never touches. Three terms carry most of the load. 拉灯 (lādēng, "turn off the light") means a scene fades to black at the crucial moment. 开车 (kāichē, "drive a car") means writing explicit content at all. 脖子以下 ("below the neck") is how writers and readers shorthand the boundary of what could be described — a line Wang's study traces to Jinjiang's own self-censorship standard.
These are documented language facts: 拉灯 circulates as fandom-wide vocabulary, while kaiche and the censorship mechanism have academic treatment. Aiqing Wang's study "Censorship and Circumvention in China: How Danmei Writers 'Drive a Car' on Jinjiang" (International Journal of Media Culture and Literature 6(2), 2020, pp. 137–168) documents Jinjiang's automated keyword detection and multi-round manual review, and the circumvention strategies authors developed in response: metaphor, code-switching between registers, and satire. Kaiche, Wang notes, became the internet neologism for danmei erotic writing because plainer terms were caught by the keyword filters. The paper is openly available.
The translation rule follows the same test. When the euphemism does narrative work — a scene that fades out — translate the function: "fade to black" needs no note. When the text discusses the euphemism as a word, keep the pinyin with a one-line gloss, because the joke is about the word. This section states a language phenomenon, not a position on any platform's policy.
白月光 (báiyuèguāng, "white moonlight") names a person one hopes for but cannot have — the first love who never became anything. English has no single word for it: the chinese.stackexchange discussion of the term offers only periphrastic answers like "unforgettable first love." Fandom practice is to keep the literal image and explain on first use.
The same shape applies to 朱砂痣 (zhūshāzhì, "cinnabar mole" — the unforgettable past love) and 替身 (tìshēn, "stand-in" — the person who resembles the beloved and gets substituted). The class is bigger than any list: any trope word with cultural weight and no English equivalent.
For this class, the defensible default is a literal translation plus one parenthetical gloss on first use, then the English term unmarked; incidental terms can take a plain translated phrase. The tropes explainer covers what these words mean to readers; this section only covers rendering.
The whole style guide compresses into one deliverable: a per-novel style sheet, built in about 30 minutes, that turns every decision above into a reusable rule. Five steps, each with a synthetic example — not quoted from any published work.
Step 1 — Inventory terms from the opening chapters. Scan the first three chapters and list every address term, era title, and trope word with the chapter where each first appears. Example: a cultivation novel yields shizun (ch. 1), shixiong (ch. 2), dianxia (ch. 3).
Step 2 — Classify each term by decision rule. Run the information-versus-texture test and write the decision next to the term. Shizun carries texture → romanize. 陛下 carries plain rank information → translate to "Your Majesty." White moonlight has no equivalent → gloss.
Step 3 — Lock first-use renderings. The first-use rendering is the book-wide standard. Example entry: "shizun — keep pinyin, gloss once: 'master-teacher, carries reverence and distance.'"
Step 4 — Audit address switches. Recheck the translation and confirm every shift — shizun to shifu, title to given name — survived. Each switch is a relationship event; the sheet names it. Example: "ch. 12: shizun → shifu after confession; keep the switch."
Step 5 — Flag uncertain items. Mark terms with no established rendering as "no standard, using X, overridable." Example entry: "替身 — no English standard; using 'stand-in', overridable." The flag keeps the choice visible and makes later revision a search, not a re-read.
That sheet is what TeaNovel's terminology management consumes: terms are extracted automatically, browsable per novel, and applied across chapters. Your style decisions become the glossary; the engine executes the consistency.
Baseline from my own testing: the MTL comparison showed raw machine translation dropping "shizun" on second mention — the model carries no state about which terms matter. A dedicated pipeline with a per-novel glossary holds the term stable across 300 chapters. Consistency is solved; that is the mechanical layer.
What an engine will not do is decide taste. "Keep shizun or render Master" is an editorial call; no default fits every novel and audience. TeaNovel's default keeps honorifics in pinyin with a first-use note, overridable in settings — a starting point, not a verdict. Terminology editing shares the boundary: the public workflow centers on visibility and consistency, with broader controls still expanding. The engine executes your sheet; it does not write it.
That is the division: the style sheet is your editorial layer; the tool makes it stick. Testing is cheap: 1,000 free credits cover about 30 chapters, enough to test the first three and revise before committing to the book.
There is no single correct answer — the rule is whether the term carries relationship texture or plain information. Texture terms stay in pinyin with a first-use gloss; information terms translate; both are defensible if the sheet says so and the book holds to it.
Shifu reads closer to a familial master, while shizun carries reverence and distance, and a translation should keep that distinction visible; flattening both to "Master" erases a relationship signal. A switch between the two is a narrative event and must survive translation.
Keep gong and shou in pinyin for fandom metadata and danmei-native readers; switch to top and bottom only for a general romance readership. The choice belongs in the style sheet, not per-chapter improvisation.
Render them as functional equivalents — Your Highness for dianxia, Your Majesty for bixia — and keep pinyin with a note for titles that carry narrative or fandom weight. Functional equivalence is the default; exceptions are documented in the sheet.
拉灯 (lādēng, literally "turn off the light") is a censorship-era euphemism for a scene that fades out at the crucial moment, and the standard rendering is "fade to black." When the text discusses the euphemism as a word, keep the pinyin with a one-line gloss.
Yes. Terms are extracted automatically per novel, and the renderings you decide are applied consistently across chapters — you make the style decisions; the engine executes them. The default honorific handling, pinyin with a first-use note, can be overridden in settings. Editing controls are still expanding: the current public workflow centers on visibility and consistency.
Put This Guide Into Practice
Translate Chinese web novels as you read. 1,000 free credits monthly — install the extension and start.