translate-docs-zh

Translate Apache Fory docs into Simplified Chinese and sync i18n/zh-CN content.

28|35|Updated May 23, 2023
One-click install
npx skills add https://github.com/apache/fory-site --skill translate-docs-zh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translate-docs-zh
Source: https://github.com/apache/fory-site/tree/main/.claude/skills/translate-docs-zh
Command: npx skills add https://github.com/apache/fory-site --skill translate-docs-zh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Translate Apache Fory docs into Simplified Chinese and keep existing Chinese docs aligned with English source updates by diffing changes to ensure parity.

Core Features & Use Cases

  • Diff-based synchronization of i18n/zh-CN content with English sources to minimize drift.
  • Terminology consistency: apply standard Chinese terminology from references/terminology.md.
  • In-place updates to translations with guardrails that prohibit external translation services and preserve code identifiers and anchors.
  • Use Case: When English docs change, quickly align zh-CN translations and remove placeholder notices.

Quick Start

Clone English docs and update the Chinese translations in i18n/zh-CN by applying changes from English sources while preserving terminology and avoiding external translation tools.

Frequently Asked Questions about translate-docs-zh

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I align Simplified Chinese docs with English source updates?

To align Simplified Chinese docs with English source updates, apply diff-based synchronization to the i18n/zh-CN directory. This process minimizes content drift by identifying changes in the English files and applying in-place updates to the corresponding translations.

How does terminology consistency work when translating documentation to zh-CN?

Terminology consistency during zh-CN translation is maintained by applying standard Chinese terminology from a dedicated terminology reference file. This ensures uniform translations across all documents and prevents divergent localized terms for the same English concepts.

Can I use external translation services to update i18n/zh-CN content?

No, you cannot use external translation services to update i18n/zh-CN content. The translation process enforces constraints that prohibit external tools, requiring Codex reasoning to perform in-place edits while preserving code identifiers and anchors.

What is the best way to remove placeholder notices from existing Chinese translations?

The best way to remove placeholder notices from existing Chinese translations is to update them using in-place edits guided by the terminology reference. This action syncs the translated content with English sources and automatically clears outdated placeholders.

Do I need to manually diff English markdown files to sync i18n content?

No, you do not need to manually diff English markdown files to sync i18n content. The process automatically performs diff-based synchronization between English sources and the i18n/zh-CN directory to identify updates and maintain content parity.