This is an automated email from the ASF dual-hosted git repository.
chaokunyang pushed a commit to branch fix_translate
in repository https://gitbox.apache.org/repos/asf/fory-site.git
The following commit(s) were added to refs/heads/fix_translate by this push:
new 1bf9175a29 fix lint
1bf9175a29 is described below
commit 1bf9175a297f8cfb63d9a67ca0f38c06c28cacb7
Author: chaokunyang <[email protected]>
AuthorDate: Tue Feb 10 15:42:03 2026 +0800
fix lint
---
skills/translate-docs-zh/SKILL.md | 15 ++++++
skills/translate-docs-zh/references/terminology.md | 60 +++++++++++-----------
2 files changed, 45 insertions(+), 30 deletions(-)
diff --git a/skills/translate-docs-zh/SKILL.md
b/skills/translate-docs-zh/SKILL.md
index 1e2b3c712c..4c46c06173 100644
--- a/skills/translate-docs-zh/SKILL.md
+++ b/skills/translate-docs-zh/SKILL.md
@@ -25,18 +25,22 @@ Translate documentation into Simplified Chinese and keep
existing Chinese docs a
Map source and target paths with these rules:
1. Current docs:
+
- Source: `docs/<subpath>.md`
- Target: `i18n/zh-CN/docusaurus-plugin-content-docs/current/<subpath>.md`
2. Versioned docs:
+
- Source: `versioned_docs/version-X/<subpath>.md`
- Target: `i18n/zh-CN/docusaurus-plugin-content-docs/version-X/<subpath>.md`
3. Category labels:
+
- Source: `docs/**/_category_.json`
- Target: `i18n/zh-CN/docusaurus-plugin-content-docs/**/_category_.json`
4. Sidebar top-level label i18n keys:
+
- Target: `i18n/zh-CN/docusaurus-plugin-content-docs/current.json`
- Optional version keys:
`i18n/zh-CN/docusaurus-plugin-content-docs/version-*.json`
@@ -74,17 +78,21 @@ Otherwise classify as `translated`.
1. Find source changes since last Chinese update baseline.
2. Prefer this baseline method:
+
- `zh_last_commit = git log -1 --format=%H -- <zh_file>`
- `git diff --unified=0 <zh_last_commit>..HEAD -- <source_file>`
+
3. If no source diff, keep Chinese file unchanged.
4. If source diff exists, decide update strategy:
Use **partial update** when all are true:
+
- Changes are local and limited.
- Document structure mostly unchanged.
- No widespread terminology shifts.
Use **full rewrite** when any is true:
+
- Large structural edits (section reordering/splitting/merging).
- Significant rewrite of core semantics.
- Many scattered edits across the document.
@@ -99,8 +107,10 @@ Use **full rewrite** when any is true:
2. Keep terminology consistent across files.
3. Avoid awkward literal phrases (for example avoid unnatural jargon calques).
4. Keep technical precision:
+
- Distinguish encoding format vs transport framework concepts.
- Keep units, ranges, and bit layouts exact.
+
5. Preserve examples and command behavior exactly.
## Validation Checklist
@@ -108,20 +118,25 @@ Use **full rewrite** when any is true:
Run checks after edits:
1. Placeholder cleanup:
+
- `rg -n "中文导读|中文章节导读" i18n/zh-CN -S`
2. Markdown integrity:
+
- Ensure code fences are balanced.
- Ensure tables render (pipes/alignment valid).
- Ensure frontmatter remains valid YAML.
3. MDX safety:
+
- Avoid standalone lines that MDX may parse as ESM (`import ...`, `export
...`) in prose.
4. Link/anchor sanity:
+
- Preserve existing inbound anchors where possible.
5. Optional build verification (recommended):
+
- `npm run build -- --locale zh-CN`
## Decision Heuristics for Rewrite vs Patch
diff --git a/skills/translate-docs-zh/references/terminology.md
b/skills/translate-docs-zh/references/terminology.md
index 1caff3a64e..00b4d38322 100644
--- a/skills/translate-docs-zh/references/terminology.md
+++ b/skills/translate-docs-zh/references/terminology.md
@@ -12,39 +12,39 @@ Use these terms consistently across all translated docs.
## Canonical Terms
-| English Term | Preferred Chinese | Notes |
-| --- | --- | --- |
-| wire format | 编码格式 | Do not use `线协议` in this repo context. |
-| serialization format | 序列化格式 | Use for data layout/encoding docs. |
-| protocol | 协议 | Use only when discussing protocol semantics. |
-| transport | 传输 | Use only for network transport context; do not replace
encoding semantics with this term. |
-| schema evolution | Schema 演进 | Keep `Schema` as-is in mixed technical
headings when already used by repo style. |
-| compatible mode | 兼容模式 | |
-| type meta | 类型元信息 | |
-| meta string | 元字符串 | |
-| reference tracking | 引用跟踪 | |
-| shared reference | 共享引用 | |
-| circular reference | 循环引用 | |
-| field tag ID | 字段 tag ID | Keep `tag ID` mixed for precision. |
-| nullable | 可空 | |
-| optional field | 可选字段 | |
-| fixed-width | 定长 | |
-| variable-width | 变长 | |
-| little-endian | 小端序 | |
-| big-endian | 大端序 | |
-| offset | 偏移量 | |
-| payload | 载荷 | |
-| runtime | 运行时 | |
-| codegen | 代码生成 | |
-| cross-language | 跨语言 | |
+| English Term | Preferred Chinese | Notes
|
+| -------------------- | ----------------- |
-----------------------------------------------------------------------------------------
|
+| wire format | 编码格式 | Do not use `线协议` in this repo
context. |
+| serialization format | 序列化格式 | Use for data layout/encoding docs.
|
+| protocol | 协议 | Use only when discussing protocol
semantics. |
+| transport | 传输 | Use only for network transport
context; do not replace encoding semantics with this term. |
+| schema evolution | Schema 演进 | Keep `Schema` as-is in mixed
technical headings when already used by repo style. |
+| compatible mode | 兼容模式 |
|
+| type meta | 类型元信息 |
|
+| meta string | 元字符串 |
|
+| reference tracking | 引用跟踪 |
|
+| shared reference | 共享引用 |
|
+| circular reference | 循环引用 |
|
+| field tag ID | 字段 tag ID | Keep `tag ID` mixed for precision.
|
+| nullable | 可空 |
|
+| optional field | 可选字段 |
|
+| fixed-width | 定长 |
|
+| variable-width | 变长 |
|
+| little-endian | 小端序 |
|
+| big-endian | 大端序 |
|
+| offset | 偏移量 |
|
+| payload | 载荷 |
|
+| runtime | 运行时 |
|
+| codegen | 代码生成 |
|
+| cross-language | 跨语言 |
|
## Terms to Avoid (Unless User Explicitly Requests)
-| Avoid | Use Instead | Reason |
-| --- | --- | --- |
-| 线协议 | 编码格式 / 协议 | `线协议` is unnatural in this project style. |
-| 传输格式 (for wire encoding semantics) | 编码格式 | Fory is not a transport
framework. |
-| 类定义元数据 (when referring to `type meta`) | 类型元信息 | Keep terminology short and
consistent. |
+| Avoid | Use Instead | Reason
|
+| -------------------------------------------- | --------------- |
-------------------------------------------- |
+| 线协议 | 编码格式 / 协议 | `线协议` is unnatural
in this project style. |
+| 传输格式 (for wire encoding semantics) | 编码格式 | Fory is not a
transport framework. |
+| 类定义元数据 (when referring to `type meta`) | 类型元信息 | Keep terminology short
and consistent. |
## Style Notes
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
