From: Weijie Yuan <wy@wyuan.org>
To: 葉宸佑 <chenyou910331@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
Dongliang Mu <dzm91@hust.edu.cn>,
Yanteng Si <si.yanteng@linux.dev>,
Hu Haowen <2023002089@link.tyut.edu.cn>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 10/16] docs/zh_TW: process: localize terminology in 2.Process.rst
Date: Fri, 7 Aug 2026 21:28:20 +0800 [thread overview]
Message-ID: <anXddDML5sw8loCQ@wyuan.org> (raw)
In-Reply-To: <CAKspUhL-1fh8o19aEvLzxVGMqvnFtmP0XksS7ni5QCYNBWqSKw@mail.gmail.com>
On Wed, Aug 05, 2026 at 02:48:35AM +0800, 葉宸佑 wrote:
> 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.
Yes, I think a space between CJK and Latin text is more "proper", or
a more "universal" way.
> 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
I might be more inclined to remain neutral, so I would prefer to hear
the opinions of others. Or we could take a look at how zh_CN and jp_JP
handle it.
Or: for new articles, we can start to require spaces between.
> - do not go back and normalize existing files
Of course.
next prev parent reply other threads:[~2026-08-07 13:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 9:10 [PATCH v2 00/16] docs/zh_TW: localize terminology and sync process/ documents Chen-Yu Yeh
2026-07-28 9:10 ` [PATCH v2 01/16] docs/zh_TW: process: localize terminology in 7.AdvancedTopics.rst Chen-Yu Yeh
2026-07-29 16:08 ` Weijie Yuan
2026-07-31 5:14 ` 葉宸佑
2026-07-31 18:12 ` Weijie Yuan
2026-07-28 9:10 ` [PATCH v2 02/16] docs/zh_TW: process: localize terminology in 1.Intro.rst Chen-Yu Yeh
2026-07-28 9:10 ` [PATCH v2 03/16] docs/zh_TW: process: localize terminology in code-of-conduct-interpretation.rst Chen-Yu Yeh
2026-07-29 16:45 ` Weijie Yuan
2026-07-31 5:19 ` 葉宸佑
2026-08-01 16:26 ` Weijie Yuan
2026-07-28 9:10 ` [PATCH v2 04/16] docs/zh_TW: process: localize terminology in license-rules.rst Chen-Yu Yeh
2026-08-03 16:08 ` Weijie Yuan
2026-07-28 9:10 ` [PATCH v2 05/16] docs/zh_TW: process: localize terminology in email-clients.rst Chen-Yu Yeh
2026-08-03 16:09 ` Weijie Yuan
2026-07-28 9:10 ` [PATCH v2 06/16] docs/zh_TW: process: localize terminology in programming-language.rst Chen-Yu Yeh
2026-07-28 9:10 ` [PATCH v2 07/16] docs/zh_TW: process: localize terminology in coding-style.rst Chen-Yu Yeh
2026-07-28 9:10 ` [PATCH v2 08/16] docs/zh_TW: process: localize terminology in stable-kernel-rules.rst Chen-Yu Yeh
2026-08-05 16:20 ` Weijie Yuan
2026-07-28 9:10 ` [PATCH v2 09/16] docs/zh_TW: process: localize terminology in 5.Posting.rst Chen-Yu Yeh
2026-07-28 9:10 ` [PATCH v2 10/16] docs/zh_TW: process: localize terminology in 2.Process.rst Chen-Yu Yeh
2026-08-03 16:22 ` Weijie Yuan
2026-08-04 18:48 ` 葉宸佑
2026-08-07 13:28 ` Weijie Yuan [this message]
2026-07-28 9:10 ` [PATCH v2 11/16] docs/zh_TW: process: localize terminology in howto.rst Chen-Yu Yeh
2026-08-05 6:43 ` Weijie Yuan
2026-07-28 9:10 ` [PATCH v2 12/16] docs/zh_TW: process: localize terminology in embargoed-hardware-issues.rst Chen-Yu Yeh
2026-08-05 6:49 ` Weijie Yuan
2026-07-28 9:10 ` [PATCH v2 13/16] docs/zh_TW: process: localize terminology in submitting-patches.rst Chen-Yu Yeh
2026-08-05 7:06 ` Weijie Yuan
2026-07-28 9:10 ` [PATCH v2 14/16] docs/zh_TW: process: localize terminology in 8.Conclusion.rst Chen-Yu Yeh
2026-07-28 9:10 ` [PATCH v2 15/16] docs/zh_TW: process: localize terminology in index.rst Chen-Yu Yeh
2026-07-28 9:10 ` [PATCH v2 16/16] docs/zh_TW: Add a glossary for Traditional Chinese translations Chen-Yu Yeh
2026-07-28 13:36 ` Alex Shi
[not found] ` <CAKspUh+nRVUXxr9-S9D7jK9nTR3Emwer1ZFOdLQeChGBN+Hc-g@mail.gmail.com>
2026-07-28 18:24 ` 葉宸佑
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=anXddDML5sw8loCQ@wyuan.org \
--to=wy@wyuan.org \
--cc=2023002089@link.tyut.edu.cn \
--cc=alexs@kernel.org \
--cc=chenyou910331@gmail.com \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=si.yanteng@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).