Markdown En Zh Pro

• single file translation
• directory batch translation
• in-place replacement or output to another root
• optional second-pass review for terminology and tone

3. Run structural QA.

• Script: scripts/qa_markdown_translation.ps1
• Compare source and translated Markdown for:
  • heading count
  • code fence count
  • link count
  • table row count

Command Examples

Set Baidu Translate credentials (Windows PowerShell):

setx BAIDU_TRANSLATE_APP_ID "your_baidu_appid"
setx BAIDU_TRANSLATE_API_KEY "your_baidu_appkey"

Translate one file in place:

pwsh ./scripts/translate_markdown.ps1 `
  -Path "D:\docs\spec.md" `
  -InPlace `
  -AppId $env:BAIDU_TRANSLATE_APP_ID `
  -ApiKey $env:BAIDU_TRANSLATE_API_KEY `
  -AuthMode bearer `
  -ModelType llm `
  -GlossaryCsv "./references/glossary-template.csv"

Translate a directory to another output root:

pwsh ./scripts/translate_markdown.ps1 `
  -Path "D:\docs" `
  -Recurse `
  -OutputRoot "D:\docs_zh" `
  -AppId $env:BAIDU_TRANSLATE_APP_ID `
  -ApiKey $env:BAIDU_TRANSLATE_API_KEY `
  -AuthMode bearer `
  -ModelType llm `
  -GlossaryCsv "./references/glossary-template.csv"

QA check:

pwsh ./scripts/qa_markdown_translation.ps1 `
  -Source "D:\docs\spec.md" `
  -Translated "D:\docs_zh\spec.md"

Quality Policy

• Use concise, professional Chinese.
• Do not over-translate product names, APIs, register names, constants, paths, and code identifiers.
• Preserve all fenced code blocks verbatim.
• Preserve anchor text behavior in links.
• If text is ambiguous, prefer literal + precise translation over creative rewriting.

Read references/translation-style-guide.md for detailed style and term rules.