The zh_TW (Traditional Chinese) translations were originally converted
from the zh_CN tree, so they still use mainland Chinese terminology
(e.g. 內核, 軟件, 接口) that reads unnatural to Taiwanese readers, and
most of the process/ documents have fallen behind their English
originals.

This series localizes the terminology of the existing zh_TW process/
documents to Taiwanese Mandarin and, in the same pass, syncs each
document with its current English original, so that the "update to
commit" markers stay honest for tools/docs/checktransupdate.py.

Each patch covers one document and does both the terminology
localization and the content sync for it. Notable content syncs
include:

  - code-of-conduct-interpretation: new "Enforcement for Unacceptable
    Behavior" section and updated TAB voting language
  - stable-kernel-rules: retranslated from the heavily restructured
    English text (three submission options, stable tag variants)
  - submitting-patches: interleaved-reply etiquette, reworked Acked-by
    semantics, tagging-people permission rules, Assisted-by:, canonical
    patch format subsections and the b4 tooling section
  - embargoed-hardware-issues: "Early access" section and the current
    ambassadors list
  - index: mirrors the reworked English process index layout
  - programming-language: Rust is no longer experimental

The final patch adds Documentation/translations/zh_TW/glossary.rst,
which documents the terminology mapping used across the series (with
zh_CN equivalents for cross-reference) so that reviewers can check the
replacements against a single reference, and future translations can
stay consistent.

A short summary of the main mappings (English / zh_TW / old zh_CN-style):

  kernel      核心   (內核)      software    軟體   (軟件)
  interface   介面   (接口)      memory      記憶體 (內存)
  process     行程   (進程)      queue       佇列   (隊列)
  network     網路   (網絡)      server      伺服器 (服務器)
  default     預設   (默認)      user        使用者 (用戶)
  code        程式碼 (代碼)      file        檔案   (文件)
  community   社群   (社區)      documentation 文件 (文檔)

  - 8.Conclusion: carries a Reviewed-by from an earlier standalone
    review; see the note under --- in that patch for what changed since.

The zh_TW documents were built with "make SPHINXDIRS=translations
htmldocs" without new warnings, and tools/docs/checktransupdate.py -l
zh_TW now reports the series' documents as up to date.

Chen-Yu Yeh (16):
  docs/zh_TW: process: localize terminology in 7.AdvancedTopics.rst
  docs/zh_TW: process: localize terminology in 1.Intro.rst
  docs/zh_TW: process: localize terminology in
    code-of-conduct-interpretation.rst
  docs/zh_TW: process: localize terminology in license-rules.rst
  docs/zh_TW: process: localize terminology in email-clients.rst
  docs/zh_TW: process: localize terminology in programming-language.rst
  docs/zh_TW: process: localize terminology in coding-style.rst
  docs/zh_TW: process: localize terminology in stable-kernel-rules.rst
  docs/zh_TW: process: localize terminology in 5.Posting.rst
  docs/zh_TW: process: localize terminology in 2.Process.rst
  docs/zh_TW: process: localize terminology in howto.rst
  docs/zh_TW: process: localize terminology in
    embargoed-hardware-issues.rst
  docs/zh_TW: process: localize terminology in submitting-patches.rst
  docs/zh_TW: process: localize terminology in 8.Conclusion.rst
  docs/zh_TW: process: localize terminology in index.rst
  docs/zh_TW: Add a glossary for Traditional Chinese translations

 Documentation/translations/zh_TW/glossary.rst | 145 +++++
 Documentation/translations/zh_TW/index.rst    |   5 +-
 .../translations/zh_TW/process/1.Intro.rst    | 211 +++----
 .../translations/zh_TW/process/2.Process.rst  | 304 +++++----
 .../translations/zh_TW/process/5.Posting.rst  | 226 ++++---
 .../zh_TW/process/7.AdvancedTopics.rst        | 103 ++--
 .../zh_TW/process/8.Conclusion.rst            |  51 +-
 .../code-of-conduct-interpretation.rst        | 162 +++--
 .../zh_TW/process/coding-style.rst            | 580 +++++++++---------
 .../zh_TW/process/email-clients.rst           | 184 +++---
 .../process/embargoed-hardware-issues.rst     | 194 +++---
 .../translations/zh_TW/process/howto.rst      | 343 +++++------
 .../translations/zh_TW/process/index.rst      |  99 ++-
 .../zh_TW/process/license-rules.rst           | 200 +++---
 .../zh_TW/process/programming-language.rst    |  94 ++-
 .../zh_TW/process/stable-kernel-rules.rst     | 256 ++++++--
 .../zh_TW/process/submitting-patches.rst      | 503 ++++++++-------
 17 files changed, 2125 insertions(+), 1535 deletions(-)
 create mode 100644 Documentation/translations/zh_TW/glossary.rst

-- 
2.43.0

Sorry to be wordy,

In our zh_CN/how-to.rst, our template for commit message is:

---
docs/zh_CN: Add self-protection index Chinese translation

Translate .../security/self-protection.rst into Chinese.

Update the translation through commit b080e52110ea
("docs: update self-protection __ro_after_init status")
# 请执行 git log --oneline <您翻译的英文文档路径>，并替换上述内容

Signed-off-by: Yanteng Si <si.yanteng@linux.dev>
# 如果您前面的步骤正确执行，该行会自动显示，否则请检查 gitconfig 文件
---

So the ref for previous commit is wrapped, while in:

  https://docs.kernel.org/process/5.Posting.html#patch-formatting-and-changelogs

It asks do not wrap the ref of a certain commit, i.e. keep it as-is, in
the "Fixes:" trailer.

But our case is not about the "Fixes:" trailer, so my understanding is
that we should wrap the ref of previous commit in this series.

Hope there can be a consensus on this matter.

Thanks.

On Wed, Jul 22, 2026 at 11:09:49PM +0800, Weijie Yuan wrote:
> So the ref for previous commit is wrapped, while in:
>   https://docs.kernel.org/process/5.Posting.html#patch-formatting-and-changelogs
> It asks do not wrap the ref of a certain commit, i.e. keep it as-is, in
> the "Fixes:" trailer.
> But our case is not about the "Fixes:" trailer, so my understanding is
> that we should wrap the ref of previous commit in this series.

Agreed. The no-wrapping rule is specific to the Fixes: trailer, which
is machine-parsed, while "update to commit ..." is matched by
checktransupdate.py on the hash only, so wrapping the title does not
break it. The zh_CN how-to template wraps it, and keeping commit
messages within ~72 columns is the general rule, so I will wrap it in
v2 across the series.

Thanks for the thorough review.

Chen-Yu