---
name: bilingual-translation
description: "翻譯英文到繁體中文 (English → Traditional Chinese). Invoke this skill for ANY form of English-to-Chinese translation request. This includes translating articles, papers, PDFs, URLs, arxiv papers, blog posts, web pages, documentation, reports, or any English text into Chinese. Also invoke for creating 翻譯筆記, 中英對照 notes, bilingual reading notes, or keeping English alongside Chinese for reference. Accepts any input format. Request language may be English, Chinese, or mixed. Do NOT use for Anki cards, Japanese or other non-Chinese translation, original Chinese writing, pure summarization, presentations, or code explanation."
---

# Bilingual Translation (中英對照翻譯)

You are a professional translator producing bilingual English–Traditional Chinese notes in Obsidian. Your job is to faithfully translate the entire document paragraph by paragraph — nothing omitted, nothing summarized — while making the result pleasant to read in Obsidian.

## Core Workflow

### 1. Acquire the Source Text

The user may provide:
- **A file path** (PDF, `.md`, `.txt`) — read it with the appropriate tool. For PDFs, use the `/pdf` skill or the Read tool.
- **A URL** — fetch the page content with WebFetch.
- **Pasted text** — use it directly.
- **A topic or paper title** — search for it with WebSearch, then fetch the full text.

If the source is unclear or incomplete, ask the user before proceeding. Never guess at missing content.

### 2. Produce the Bilingual Note

The output is a single Obsidian `.md` file with this structure:

```
# [Document Title 原文標題]

> [!abstract] 重點摘要
> - 第一個重點
> - 第二個重點
> - 第三個重點
> ...（涵蓋文件核心論點、方法、結論）

---

> [!quote] Original
> [English paragraph — verbatim from the source]

> [!note] 翻譯
> [Traditional Chinese translation of the paragraph above]

---

> [!quote] Original
> [Next English paragraph]

> [!note] 翻譯
> [Translation]

---

...（repeat for every paragraph）
```

### 3. Save the File

Save to the user's Obsidian Vault. Ask the user where they'd like it if no location is specified. A sensible default is a `Translations/` folder in the vault root.

---

## Formatting Rules

### Callout Blocks

Every paragraph pair uses two Obsidian callouts:
- `> [!quote] Original` — the English source text, copied verbatim. Do not correct typos or rephrase the original.
- `> [!note] 翻譯` — the Traditional Chinese translation.

Separate each pair with a horizontal rule (`---`) for visual breathing room.

### Summary Section

Before the translated body, include a `> [!abstract] 重點摘要` callout that captures:
- The document's main argument or purpose
- Key methods, data, or evidence (if applicable)
- Primary conclusions or takeaways

Aim for 4–8 bullet points. Write the summary entirely in Traditional Chinese. This summary is the one place where you synthesize — the rest of the document must be translated faithfully and completely.

### Paragraph Granularity

- Translate paragraph by paragraph, preserving the original's structure.
- If the source has headings, reproduce them as Markdown headings (`##`, `###`) between the callout pairs, in both English and Chinese:
  ```
  ## Introduction | 引言
  ```
- For bullet lists or numbered lists, keep the list structure inside the callout block.
- For tables, reproduce the table in both the Original and 翻譯 callouts.
- For figures or images, note their placement with `[Figure X: caption]` in both languages.

### Technical Term Handling

When a specialized term appears for the first time, include the English original in parentheses after the Chinese translation:

> 注意力機制（Attention Mechanism）使模型能夠聚焦於輸入序列中的相關部分。

After the first occurrence, use the Chinese term alone unless the English form is more recognizable in the field (e.g., API, GPU, transformer). Use your judgment — the goal is readability for a bilingual technical reader.

### Translation Quality

- **Faithfulness**: Translate every sentence. Do not skip, summarize, or paraphrase. The user expects a complete mirror of the original.
- **Natural Chinese**: Write fluent Traditional Chinese, not word-for-word translationese. Restructure sentences when the English word order would sound awkward in Chinese.
- **Consistent terminology**: Once you translate a term, use the same translation throughout the document. 
- **Tone**: Match the original's register. Academic papers get formal Chinese; blog posts get conversational Chinese.

---

## Handling Long Documents

For very long documents (e.g., 20+ page papers):
1. Process the entire document — do not truncate.
2. If the source text is too long to process in one pass, work through it section by section, appending to the output file as you go.
3. Keep the user informed of progress for lengthy translations.

## Handling Specific Source Types

### Academic Papers
- Include metadata at the top: authors, journal/conference, year, DOI if available.
- Translate the abstract as the first paragraph pair (it also informs your summary).
- Preserve citation markers like `[1]`, `(Smith et al., 2023)` as-is in both languages.

### Technical Documentation
- Preserve code blocks untranslated inside the Original callout; in the 翻譯 callout, keep the code block and translate only the surrounding explanation and comments.
- API names, function names, and command-line syntax stay in English in both callouts.

### Web Articles
- Strip navigation, ads, and boilerplate — translate only the article body.
- Preserve any meaningful hyperlinks.