Re: [PATCH v2 10/16] docs/zh_TW: process: localize terminology in 2.Process.rst

On Tue, Aug 04, 2026 at 12:22:12AM +0800, Weijie Yuan wrote:
> Either: add a <space> before staging
> Or: remove the <space> after staging
>
> [A] Greg Kroah-Hartman 目前負責維護staging樹。
> [B] Greg Kroah-Hartman 目前負責維護 staging 樹。
>
> Which one do you prefer? I think the first option is more consistent
> with the usage throughout the text.

Sorry, I misread that as two separate changes. You are right that it
should be one or the other.

I went and counted across the whole zh_TW tree, matching a CJK
character directly adjacent to an ASCII alphanumeric with and without
a space:

  without space: 2581
  with space:     721

2.Process.rst itself is 69 without / 22 with. So [A] it is, both for
the file and for the tree as a whole. Fixed in v3.

For what it is worth, my own preference as a Taiwanese reader would
have been [B] -- a space between CJK and Latin text is easier to read
and is what most Taiwanese technical writing does nowadays. But the
existing translations overwhelmingly do not, and this series is about
terminology, not typography. Mixing the two would make it much harder
to review.

That said, it is probably worth writing the rule down rather than
leaving each contributor to guess. I would suggest:

  - no space between CJK and ASCII (following existing practice)
  - apply it to new translations and to paragraphs that are being
    rewritten anyway
  - do not go back and normalize existing files

The last point matters: a tree-wide whitespace pass would touch all 51
zh_TW files for no semantic gain, which is exactly the kind of churn
Jon objected to in the MAINTAINERS thread. I will add this to the
glossary in v3 unless you think it belongs in the how-to instead.

Chen-Yu

Weijie Yuan <[email protected]> 於 2026年8月4日週二 下午12:13寫道：
>
> On Tue, Jul 28, 2026 at 05:10:32PM +0800, Chen-Yu Yeh wrote:
> > Localize mainland terms to Taiwanese Mandarin (內核→核心, 社區→社群,
> > 郵箱→信箱, ...) and sync with the English original: rolling-release
> > wording with the 9.x example and Wikipedia link, 9.x-rc1 examples,
> > stable team now Greg Kroah-Hartman and Sasha Levin, LTS list moved to
> > kernel.org, linux-next maintained by Mark Brown, and mailing lists
> > hosted at subspace.kernel.org.
> >
> > update to commit 46298375477b ("linux-next: update maintainer info.")
> >
> > Signed-off-by: Chen-Yu Yeh <[email protected]>
> > ---
> >  .../translations/zh_TW/process/2.Process.rst  | 325 +++++++++---------
> >  1 file changed, 158 insertions(+), 167 deletions(-)
>
> [...]
>
> >  Staging 樹
> >  ----------
> >
> > -內核源代碼樹包含drivers/staging/目錄，其中有許多驅動程序或文件系統的子目錄
> > -正在被添加到內核樹中。它們在仍然需要更多的修正的時候可以保留在driver/staging/
> > -目錄中；一旦完成，就可以將它們移到內核中。這是一種跟蹤不符合Linux內核編碼或
> > -質量標準的驅動程序的方法，人們可能希望使用它們並跟蹤開發。
> > +核心原始程式碼樹包含drivers/staging/目錄，其中有許多驅動程式或檔案系統的子目錄
> > +正在被添加到核心樹中。它們在仍然需要更多的修正的時候可以保留在driver/staging/
> > +目錄中；一旦完成，就可以將它們移到核心中。這是一種追蹤不符合Linux核心編碼或
> > +品質標準的驅動程式的方法，人們可能希望使用它們並追蹤開發。
> >
> > -Greg Kroah Hartman 目前負責維護staging 樹。仍需要修正的驅動程序將發送給他，
> > -每個驅動程序在drivers/staging/中都有自己的子目錄。除了驅動程序源文件之外，
> > -目錄中還應該有一個TODO文件。TODO文件列出了驅動程序需要接受的暫停的工作，
> > -以及驅動程序的任何補丁都應該抄送的人員列表。當前的規則要求，staging的驅動
> > -程序必須至少正確編譯。
> > +Greg Kroah-Hartman 目前負責維護 staging樹。仍需要修正的驅動程式將發送給他，
>
> Oops, I guess I might not say it clearly last time, I said:
>
>  | 1) add a <space> before staging
>  | 2) remove the <space> after staging
>
> Actually I mean:
>
>  Either: add a <space> before staging
>  Or: remove the <space> after staging
>
> Which is..
>
> [A] Greg Kroah-Hartman 目前負責維護staging樹。仍需要修正的驅動程式將發送給他，
>
> [B] Greg Kroah-Hartman 目前負責維護 staging 樹。仍需要修正的驅動程式將發送給他，
>
> Which one do you prefer? I think the first option is more consistent
> with the usage throughout the text.
>
> So let's adopt option A in next re-roll.
>
> > +每個驅動程式在drivers/staging/中都有自己的子目錄。除了驅動程式原始檔之外，
> > +目錄中還應該有一個TODO檔案。TODO檔案列出了驅動程式需要接受的暫停的工作，
> > +以及驅動程式的任何補丁都應該抄送的人員列表。當前的規則要求，staging的驅動
> > +程式必須至少正確編譯。