skills: rename dharma-translation→translation, delete mpi-project-conventions, move references
- dharma-translation → translation: stripped conventions, kept only technique - Deleted mpi-project-conventions: all content now in AGENTS.md - References moved: meditation-translation, markdown-to-djot → translation/ translation-pitfalls, proofreading-patterns → translation-review/ - Updated AGENTS.md, readme.dj, memory, pdf skill cross-reference - 7 skills → 6 skills
This commit is contained in:
iacore
@@ -1,100 +0,0 @@
|
||||
---
|
||||
name: dharma-translation
|
||||
description: Translate Chinese↔English Buddhist/Dharma content using the MPI term database and Mindfulness Bell corpus for register guidance.
|
||||
category: research
|
||||
---
|
||||
|
||||
# Dharma Translation
|
||||
|
||||
When translating Chinese↔English Buddhist/Dharma content, consult TWO resources before producing output:
|
||||
|
||||
1. **Terms database** — for established term translations
|
||||
2. **Mindfulness Bell corpus** — for register/style patterns in English Buddhist prose
|
||||
|
||||
## Resources
|
||||
|
||||
### Terms DB
|
||||
- DB: `/home/user/documents/mpi/terms-search/termlib.duckdb`
|
||||
- CLI: `/home/user/documents/mpi/terms-search/search.py <query>`
|
||||
- Source tables priority: DoT定稿 > 内部特色词 > 佛教术语 > 经论名
|
||||
- See `terms-search` skill (via `skill_view`) or `AGENTS.md` for full usage
|
||||
|
||||
### Mindfulness Bell Corpus
|
||||
- Location: `/home/user/meta/www.files/public/The Mindfulness Bell/`
|
||||
- 6 issues: MB92–MB97 (2023–2026), each ~84–116 pages
|
||||
- Index: `index.yaml` (article titles, authors, pages)
|
||||
- **Articles**: `~/documents/jingxin-lessons/Mindfulness Bell/articles/MB{92..97}/*.md` — 93 individual markdown files with YAML frontmatter. Read directly with `read_file`.
|
||||
- Extraction script: `/tmp/extract_mb_articles.py` (re-run if PDFs change)
|
||||
|
||||
## Register Reference (from MB corpus analysis)
|
||||
|
||||
Four registers observed, useful as style targets:
|
||||
|
||||
| Register | Example | Key features |
|
||||
|----------|---------|-------------|
|
||||
| Dharma talk | Thầy (MB94 "Roses and Garbage", MB97 "Go as a River") | Short sentences, concrete images, coined terms ("interbeing"), oral address ("It's clear?"), Sanskrit kept with narrative explanation |
|
||||
| Teaching lineage | Sister Đoan Nghiêm (MB93 "Our Patriarch Liễu Quán") | "We" voice, terms explained, cultural bridging ("like Jesus"), dates woven into narrative, still oral |
|
||||
| Personal narrative | Mick McEvoy (MB94 "Touching the True Nature") | First-person, confessional, borrowed Dharma vocabulary, emotional directness, vernacular |
|
||||
| Editorial | Brother Pháp Lưu (MB94 welcome letter) | Polished but warm, conceptual framing, "we" address |
|
||||
|
||||
## Translation Principles (observed from MB corpus)
|
||||
|
||||
1. **Terms**: Either keep Sanskrit w/ narrative explanation (bodhisattva, Māra) OR coin new English (interbeing, inter-are). Avoid clunky calques.
|
||||
2. **Cultural bridging**: Add bridges for Western readers. A Chinese text mentioning 孔子 can stay; explain the function. Đoan Nghiêm's "like Jesus" is the pattern.
|
||||
3. **Tone**: Chinese Dharma texts are typically more formal than English equivalents. Decide consciously: keep formality or warm up (Thầy style).
|
||||
4. **Voice**: Direct address ("you"), concrete images, and oral rhythm make Dharma land in English. Abstract noun chains (common in Chinese→English translationese) kill it.
|
||||
5. **Sutra quotes**: Use standard English Buddhist idiom. Check terse-idiom conventions (e.g., Diamond Sutra "lives" not "bodies").
|
||||
|
||||
## Workflow
|
||||
|
||||
1. Load both `terms-search` and `dharma-translation` skills (and `mpi-project-conventions` for output conventions)
|
||||
2. **Search terms DB FIRST — before producing any output.** Use the CLI: `/home/user/documents/mpi/terms-search/search.py <query>`. Query every key Buddhist/MPI term in the source. Prefer DoT定稿 > 内部特色词 > 佛教术语 > 经论名. Pitfall: skipping this step and translating from general knowledge produces incorrect terms that must be patched later.
|
||||
3. For register decisions: consult the register table above (scanning MB articles is optional)
|
||||
4. Translate directly — never call external translation APIs. Agent IS the model.
|
||||
5. Write `target.dj` alongside `source.dj`. Match source line count exactly.
|
||||
6. **TOC**: strip link targets, render as bullet list (`- I. ...`). No `[text](#anchor)` markup — those are pandoc artifacts. The target is a standalone document.
|
||||
7. **Em-dash convention**: AGENTS.md mandates `—` (Unicode em-dash) → `---` (three hyphens) in English djot. When drafting, type `---` for em-dashes, not `—`. The Chinese source often uses `------` (six hyphens) as its em-dash equivalent — translate to `---`, never to `—`. Before declaring done, run a sanity check: `grep -c '—' target.dj` should be 0.
|
||||
8. After translation, offer to align against the terms DB for verification
|
||||
|
||||
## Sanskrit Italicization\n\nSanskrit/foreign loan words must be italicized on **first occurrence** in the body text. Use `*term*` (djot emphasis). This applies to all non-English Buddhist terms:\n\n- Common: bodhisattva, bodhicitta, samsara, karma, nirvana, Sangha, sutra, Dharma\n- Less common: Mahayana, Sravaka, Vinaya, Lamrim, Ksitigarbha, Samantabhadra, Chan, Arhatship, Theravada\n\nDo NOT italicize subsequent occurrences of the same term. Track which terms have been italicized as you process the body. Only italicize in the running body text, not in TOC, headings, or title lines.\n\nPitfall: some terms like \"karma\" and \"Dharma\" are common enough in English Buddhist\npublishing to appear unitalicized. Follow the convention of the target publication;\nwhen in doubt, italicize on first use.\n\n## Diacritics Convention
|
||||
|
||||
Follow the terms DB, not academic Sanskrit. See `references/diacritics-convention.md` for the full rule table. Summary:
|
||||
|
||||
- No diacritics: `Mahasthamaprapta`, `Yogacarabhumi-Sastra` (matches 佛教术语 / 经论名)
|
||||
- With diacritics: `Kṣitigarbha` (DoT定稿 uses this form)
|
||||
|
||||
When in doubt, search the DB and use whatever form appears in the highest-priority source.
|
||||
|
||||
## Bilingual Output
|
||||
|
||||
After `target.dj` is finalized, create `bilingual.dj`: interleave source and target, one line at a time. Format:
|
||||
|
||||
```
|
||||
source line
|
||||
|
||||
target line
|
||||
|
||||
source line
|
||||
|
||||
target line
|
||||
```
|
||||
|
||||
Use Python: `terminal("cat")` on both files, split on newlines, zip and interleave.
|
||||
|
||||
## DOCX Output
|
||||
|
||||
`.docx` files go to `/tmp/` — never commit binaries. Use `scripts/dj2docx.fish`:
|
||||
|
||||
```fish
|
||||
fish scripts/dj2docx.fish path/to/target.dj
|
||||
```
|
||||
|
||||
Pandoc auto-converts `---` → em dash, `--` → en dash in docx.
|
||||
|
||||
## MB Article Quick-Find
|
||||
|
||||
Common article types to search for register examples:
|
||||
- Thầy's Dharma talks: search index for "Thích Nhất Hạnh" + page ≤ 10
|
||||
- Sister/brother teachings: search for "Sister" or "Brother" + "DHARMA TEACHING"
|
||||
- Personal narratives: first-person voice, often pages 8–60
|
||||
- Lineage/history: "Patriarch," "ancestor," dates in text
|
||||
@@ -1,133 +0,0 @@
|
||||
---
|
||||
name: mpi-project-conventions
|
||||
description: Use when working in the MPI project (~/documents/mpi) — translation skill management, terms database, djot conventions, and skill relocation workflow.
|
||||
---
|
||||
|
||||
# MPI Project Conventions
|
||||
|
||||
Project directory: `/home/user/documents/mpi/`
|
||||
|
||||
## Skill management
|
||||
|
||||
Translation-related skills live in `./skills/` (canonical source). Hermes discovers
|
||||
them via `skills.external_dirs` in `~/.hermes/config.yaml`:
|
||||
|
||||
```yaml
|
||||
skills:
|
||||
external_dirs:
|
||||
- /home/user/documents/mpi/skills
|
||||
```
|
||||
|
||||
Set with: `hermes config set skills.external_dirs '[/home/user/documents/mpi/skills]'`
|
||||
|
||||
Pitfall: `hermes config set` stringifies list values. After running it, verify the
|
||||
YAML has proper list syntax (`- /path`, not `'[/path]'`). Edit manually if needed.
|
||||
|
||||
The old symlink approach (`~/.hermes/skills/dharma-translation` → `./skills/`) is
|
||||
deprecated. `skills/install.fish` has been replaced by `skills/readme.dj`.
|
||||
|
||||
## Terms database
|
||||
|
||||
- **Module (preferred)**: `from search import search` — call directly in `execute_code` scripts.
|
||||
`search("空性", limit=5, loc="...", src="DoT定稿")` → list of `{zh, en, loc, source}` dicts.
|
||||
No subprocess, no text parsing. Import after `sys.path.insert(0, '/home/user/documents/mpi/terms-search')`.
|
||||
- CLI: `/home/user/documents/mpi/terms-search/search.py <query> [limit]`
|
||||
- Server: `terms-search/server.py` (Flask, port 8910) — use only when module/CLI is insufficient
|
||||
- Start: `python3 /home/user/documents/mpi/terms-search/server.py &`
|
||||
- Query: `http://localhost:8910/search?q=...`
|
||||
|
||||
## Djot conventions
|
||||
|
||||
- Comments use `{% ... %}` syntax
|
||||
- Emphasis: `*text*` (single asterisks). `**text**` is Markdown, NOT Djot — never use it.
|
||||
- Em dashes: `---` (three hyphens in English text). Pandoc converts to proper em dash in docx output.
|
||||
- En dashes: `--` (two hyphens). Pandoc converts to proper en dash in docx output.
|
||||
- Preserve source formatting level exactly: if the source has no emphasis on a label, the translation must have none. Do not add or remove formatting.
|
||||
- TOC in both `source.dj` and `target.dj`: use clean bullet lists (`- *Section*` / ` - N．item`), not `[text](#anchor)` link markup. Those links are pandoc markdown artifacts. Both files should use the same TOC format.
|
||||
- Bilingual files: create `bilingual.dj` alongside `source.dj` and `target.dj`. No new 对照.dj files — existing ones in old projects are artifacts, don't delete them. Generate with `fish scripts/gen-bilingual.fish <article-dir>`. Format: see Bilingual file format section below.
|
||||
|
||||
### Markdown → Djot conversion (pandoc)
|
||||
|
||||
```bash
|
||||
pandoc input.md -f markdown -t djot --wrap=none -o output.dj
|
||||
```
|
||||
|
||||
Pitfall: pandoc strips `{#id}` attributes from headings but leaves behind stray
|
||||
`{#...}` lines. Pre-strip heading anchors from the markdown before conversion:
|
||||
|
||||
```bash
|
||||
sed 's/ {#[^}]*}//g' input.md | pandoc -f markdown -t djot --wrap=none -o output.dj
|
||||
```
|
||||
|
||||
Follow up by removing any remaining standalone `{#...}` lines from the djot output:
|
||||
|
||||
```bash
|
||||
sed -i '/^{#.*}$/d' output.dj
|
||||
```
|
||||
|
||||
Pitfall — combined documents: When the source `.docx.md` contains multiple articles,
|
||||
the TOC at the top often covers all articles. After splitting into per-article
|
||||
`source.dj` files, verify each TOC only lists headings that belong to that article.
|
||||
Remove entries for sibling articles — the combined TOC is a print-document artifact.
|
||||
|
||||
### Bilingual file format (bilingual.dj)
|
||||
|
||||
Structure: interleave Chinese source and English target paragraph-by-paragraph.
|
||||
|
||||
**Preferred workflow**: when the DOCX manuscript has both languages in 1:1\ncorrespondence, extract directly from DOCX. No PDF needed — the DOCX English IS\nthe target. Adapt `scripts/gen-bilingual-docx.py` as a starting point.\n\nPitfall: DOCX manuscripts sometimes order CN content before EN content within a\nsection (CN heading → CN body → EN heading → EN body) rather than strict\nCN→EN→CN→EN alternation. The simple extraction in `gen-bilingual-docx.py` fails\nfor these. Use block-based extraction instead — see\n`references/proofreading-patterns.md` for the approach.
|
||||
|
||||
**Title & subtitle**: adjacent pair (source, target, no blank between), then a single blank line before the next pair.
|
||||
|
||||
**TOC**: source TOC block, blank line, target TOC block — NOT interleaved line-by-line.
|
||||
|
||||
**Body**: source line, target line (adjacent — NO blank between them), then a single blank line between pairs.
|
||||
|
||||
Pitfall: do NOT put a blank between source and target within a body pair.
|
||||
|
||||
**Edit suggestions**: after generating bilingual.dj, scan for issues (garbled text,
|
||||
numbering mismatches, translator notes, repeated words) and write
|
||||
`edit-suggestions.dj`. Follow the original document's section layout — group
|
||||
suggestions under chapter headings, not by issue type. Use diff `-/+` notation.
|
||||
|
||||
## Translation skills
|
||||
|
||||
Skills tracked in this project:
|
||||
- `terms-search` — full-text search across the MPI term database
|
||||
- `translation-review` — review CN↔EN translations (CSV/XLSX + .dj comparison)
|
||||
- `pptx-translate` — translate PowerPoint files
|
||||
- `dharma-translation` — translate Buddhist Dharma talks
|
||||
- `chinese-text-normalize` — normalize Chinese markdown line breaks
|
||||
- `pdf-to-docx-conversion` — convert PDFs to DOCX with layout preservation
|
||||
|
||||
See `references/meditation-translation.md` for lighter workflow when translating
|
||||
guided meditation / mindfulness exercise content (vs. Dharma talks).
|
||||
|
||||
See `references/translation-pitfalls.md` for recurring CN→EN mistranslation patterns
|
||||
(关爱→compassion, 生生增上, 因病返贫, 生存层面, etc.) — review this before starting
|
||||
any translation review.
|
||||
|
||||
See `references/markdown-to-djot.md` for converting `.docx.md` source files to djot,\nincluding splitting combined articles and cleaning pandoc heading anchors.\n\nSee `references/proofreading-patterns.md` for common manuscript-vs-typeset\ndifferences (term substitutions, numbering changes, typesetting artifacts in\npdftotext output) and the bilingual-from-PDF workflow.
|
||||
|
||||
## Utility scripts
|
||||
|
||||
Project scripts live in `~/documents/mpi/scripts/`. Write them in fish shell for
|
||||
CLI wrappers, Python for data processing.
|
||||
|
||||
**Naming**: generic reusable scripts get descriptive names (`dj2docx.fish`,
|
||||
`proofread-pdf.py`). Article-specific one-off scripts use `<name>-<hash>.<ext>`
|
||||
to signal they're not general-purpose. Don't name a single-article script as if
|
||||
it were reusable.
|
||||
|
||||
**Agent workflow**: when doing repetitive Python processing (text extraction,
|
||||
diffing, data transforms), write the logic to a script in `scripts/` and run it
|
||||
via `terminal`. Don't regenerate the same Python in `execute_code` across turns.
|
||||
This keeps the agent's output concise — the user sees the results, not the code.
|
||||
|
||||
- `dj2docx.fish` — convert `target.dj` → `/tmp/<dirname>-英文.docx` via pandoc.
|
||||
Usage: `fish scripts/dj2docx.fish <path-to-target.dj>`
|
||||
- `proofread-pdf.py <docx> <pdf>` — compare manuscript DOCX against typeset PDF.
|
||||
- `gen-bilingual-docx.py` — template for generating `bilingual.dj` directly from DOCX manuscript.
|
||||
Adapt for each article by changing paths and article-specific metadata.
|
||||
For articles with mixed CN→EN ordering, use block-based extraction instead
|
||||
of simple alternation (see `references/proofreading-patterns.md`).
|
||||
- `gen-bilingual.fish <article-dir>` — generate `bilingual.dj` from `source.dj` + `target.dj`.
|
||||
+1
-1
@@ -18,8 +18,8 @@ skills:
|
||||
|
||||
| Name | What it does |
|
||||
|---|---|
|
||||
| `translation` | Translate Chinese↔English Buddhist/Dharma content |
|
||||
| `terms-search` | Full-text search across MPI term database |
|
||||
| `dharma-translation` | Translate Chinese↔English Buddhist content |
|
||||
| `translation-review` | Review translations for quality issues |
|
||||
| `chinese-text-normalize` | Normalize Chinese markdown line breaks |
|
||||
| `pptx-translate` | Translate PowerPoint files |
|
||||
|
||||
@@ -56,7 +56,23 @@ One entry per problem category, not per row. Mention affected row numbers.
|
||||
|
||||
## Workflow B: .dj comparison file review
|
||||
|
||||
Use when input is a `.dj` comparison file (Chinese/English alternating line pairs). Produces `translation-findings.dj` and applies patches.
|
||||
Use when input is a `.dj` comparison file (Chinese/English alternating line pairs).
|
||||
|
||||
### Two modes — always clarify which one
|
||||
|
||||
AGENTS.md defines two workflows. Before starting, determine which mode you're in:
|
||||
|
||||
1. **Translation review** (Workflow A in AGENTS.md): agent translated the text.
|
||||
Authoritative `target.dj` does not exist yet. Review everything:
|
||||
terminology, grammar, formatting, em-dashes, consistency, calques, missing content.
|
||||
Produces `translation-findings.dj` and applies patches.
|
||||
|
||||
2. **Proofread** (Workflow B in AGENTS.md): English comes from an existing DOCX
|
||||
manuscript. It is authoritative. Only flag manuscript-level mechanical issues:
|
||||
typos, double words, numbering mismatches, garbled text, duplicate text.
|
||||
Produces `edit-suggestions.dj` ONLY — do NOT apply patches without asking.
|
||||
Do NOT flag: terminology choices, djot formatting (em-dashes, italics),
|
||||
translation style, calques, word order. These are translation-review concerns.
|
||||
|
||||
### 1. Read the full file
|
||||
|
||||
@@ -173,9 +189,9 @@ Do not run extraction pipelines until scope is clear.
|
||||
- **Never delete .dj comparison files** — intentional work artifacts
|
||||
- **Verify patches with `cat`** — `read_file` dedup makes it unreliable
|
||||
- **Re-read before fixing** — user may have made interim edits
|
||||
- **Em-dash drift**: AGENTS.md mandates `—` (Unicode em-dash) → `---` (three hyphens) in English djot. The Chinese source often uses `------` (six hyphens) as its em-dash equivalent; converters or translators may preserve it as a Unicode `—` in the target, which is a convention violation. Run a single find/replace `—` → `---` over the target. Long files typically have 30–50 such instances.
|
||||
- **Em-dash drift (translation mode only)**: AGENTS.md mandates `—` (Unicode em-dash) → `---` (three hyphens) in English djot for the translation workflow. When proofreading an existing DOCX manuscript, do NOT flag em-dashes — the manuscript's English is authoritative and this is a formatting concern for the translation workflow. If you're in translation mode and the target has Unicode em-dashes, run a single find/replace `—` → `---`. Long files typically have 30–50 such instances.
|
||||
- **Batch terminology lookups** — when checking many terms against the terms DB, run them in one `execute_code` script that loops over a query list and calls `search.py` via `subprocess.run`. One terminal call per term floods the context with repetitive output.
|
||||
- **Clunky idioms aren't translation errors, they're review items** — a literal calque of a Chinese idiom can read as a typo to a native English reader. Flag these under "Cleanup needed", not "Real errors", and suggest a standard rendering rather than trying to fix in place without confirmation.
|
||||
- **Proofread ≠ translation review** — when the user says "校对" or "proofread" and the input is a DOCX manuscript with existing English, you are in proofread mode. Do NOT flag translation quality, terminology, or djot formatting. Do NOT apply patches to bilingual.dj unless asked. Write `edit-suggestions.dj` with manuscript-level issues only. If the user later asks for translation review of the same article, write findings to a separate `translation-findings.dj`.
|
||||
|
||||
## References
|
||||
|
||||
|
||||
+16
-1
@@ -1,6 +1,10 @@
|
||||
# Proofreading: Manuscript vs Typeset
|
||||
|
||||
## Two workflows
|
||||
AGENTS.md defines two workflows: Translation (A) and Proofread (B).
|
||||
The workflows below are Proofread mode — English comes from an existing
|
||||
manuscript and is authoritative. Only flag mechanical/manuscript-level issues.
|
||||
|
||||
## Two extraction workflows
|
||||
|
||||
### A. Bilingual from DOCX (standard)
|
||||
|
||||
@@ -92,3 +96,14 @@ On first occurrence in body text, wrap with `*term*`. Track seen terms across
|
||||
the full body. Terms: bodhisattva, bodhicitta, samsara, Dharma, karma, nirvana,
|
||||
Sangha, sutra, Mahayana, Sravaka, Vinaya, Lamrim, Ksitigarbha, Samantabhadra,
|
||||
Chan, Arhatship, Theravada.
|
||||
|
||||
## Proofread scope boundary
|
||||
|
||||
When proofreading a DOCX manuscript:
|
||||
- **DO flag**: typos, double words, double punctuation, numbering mismatches,
|
||||
garbled text, translator notes, duplicate names, capitalization errors.
|
||||
- **Do NOT flag**: em-dash formatting (`—` vs `---`), terminology choices,
|
||||
translation style, calques, word order. The manuscript English is authoritative.
|
||||
- **Do NOT apply fixes** — write `edit-suggestions.dj` only.
|
||||
- If the user asks for translation review separately, write findings to
|
||||
`translation-findings.dj`.
|
||||
@@ -0,0 +1,59 @@
|
||||
---
|
||||
name: translation
|
||||
description: Translate Chinese↔English Buddhist/Dharma content — register guidance from Mindfulness Bell corpus, tone, voice, cultural bridging technique.
|
||||
---
|
||||
|
||||
# Translation
|
||||
|
||||
Core translation technique for Buddhist/Dharma content. Conventions (djot format,
|
||||
terms DB query, workflows, output format) are in AGENTS.md.
|
||||
|
||||
## Mindfulness Bell Corpus
|
||||
|
||||
Register/style patterns in English Buddhist prose.
|
||||
|
||||
- Location: `/home/user/meta/www.files/public/The Mindfulness Bell/`
|
||||
- 6 issues: MB92–MB97 (2023–2026), each ~84–116 pages
|
||||
- Index: `index.yaml` (article titles, authors, pages)
|
||||
- **Articles**: `~/documents/jingxin-lessons/Mindfulness Bell/articles/MB{92..97}/*.md` — 93 individual markdown files with YAML frontmatter. Read directly with `read_file`.
|
||||
- Extraction script: `/tmp/extract_mb_articles.py` (re-run if PDFs change)
|
||||
|
||||
## Register Reference
|
||||
|
||||
Four registers observed, useful as style targets:
|
||||
|
||||
| Register | Example | Key features |
|
||||
|----------|---------|-------------|
|
||||
| Dharma talk | Thầy (MB94 "Roses and Garbage", MB97 "Go as a River") | Short sentences, concrete images, coined terms ("interbeing"), oral address ("It's clear?"), Sanskrit kept with narrative explanation |
|
||||
| Teaching lineage | Sister Đoan Nghiêm (MB93 "Our Patriarch Liễu Quán") | "We" voice, terms explained, cultural bridging ("like Jesus"), dates woven into narrative, still oral |
|
||||
| Personal narrative | Mick McEvoy (MB94 "Touching the True Nature") | First-person, confessional, borrowed Dharma vocabulary, emotional directness, vernacular |
|
||||
| Editorial | Brother Pháp Lưu (MB94 welcome letter) | Polished but warm, conceptual framing, "we" address |
|
||||
|
||||
## Translation Principles
|
||||
|
||||
1. **Terms**: Either keep Sanskrit w/ narrative explanation (bodhisattva, Māra) OR coin new English (interbeing, inter-are). Avoid clunky calques.
|
||||
2. **Cultural bridging**: Add bridges for Western readers. A Chinese text mentioning 孔子 can stay; explain the function. Đoan Nghiêm's "like Jesus" is the pattern.
|
||||
3. **Tone**: Chinese Dharma texts are typically more formal than English equivalents. Decide consciously: keep formality or warm up (Thầy style).
|
||||
4. **Voice**: Direct address ("you"), concrete images, and oral rhythm make Dharma land in English. Abstract noun chains (common in Chinese→English translationese) kill it.
|
||||
5. **Sutra quotes**: Use standard English Buddhist idiom. Check terse-idiom conventions (e.g., Diamond Sutra "lives" not "bodies").
|
||||
|
||||
For register decisions: consult the register table above (scanning MB articles is optional).
|
||||
|
||||
## Quick-Find in MB Corpus
|
||||
|
||||
Common article types to search for register examples:
|
||||
- Thầy's Dharma talks: search index for "Thích Nhất Hạnh" + page ≤ 10
|
||||
- Sister/brother teachings: search for "Sister" or "Brother" + "DHARMA TEACHING"
|
||||
- Personal narratives: first-person voice, often pages 8–60
|
||||
- Lineage/history: "Patriarch," "ancestor," dates in text
|
||||
|
||||
## Meditation / Mindfulness Content
|
||||
|
||||
When translating guided meditation scripts, exercise guides, or posture instructions
|
||||
(rather than Dharma talks), use a lighter workflow. See `references/meditation-translation.md`.
|
||||
|
||||
## References
|
||||
|
||||
- `references/meditation-translation.md` — lighter workflow for meditation/mindfulness content
|
||||
- `references/markdown-to-djot.md` — converting .docx.md to .dj for translation prep
|
||||
- `references/diacritics-convention.md` — diacritics rules
|
||||
Reference in New Issue
Block a user