All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 11 Aug 2026 12:04:22 +0800	[thread overview]
Message-ID: <anqfRvYGG5-mvKt4@wyuan.org> (raw)
In-Reply-To: <CAKspUhJryJv0ebW2cjGzcAPHRE4AtFjGKF7aZbpdS4R7AhXdkQ@mail.gmail.com>

On Mon, Aug 10, 2026 at 02:59:55PM +0800, 葉宸佑 wrote:
> On Fri, Aug 07, 2026 at 09:28:20PM +0800, Weijie Yuan wrote:
> > 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.
> 
> Fair enough -- I put that entry in the v3 glossary before seeing this,
> so let me pull it back to a description rather than a rule.

Agreed.

Just like what Dongliang said, a clearly and explicitly stated rule for
this is not necessary now, because we need more contributors, obviously
;-)

> Here is what the other locales look like, same measurement (a CJK
> character directly adjacent to an ASCII alphanumeric):
> 
> zh_CN    有空格   3624 / 無空格  11022
> ja_JP    有空格    128 / 無空格     70
> ko_KR    有空格     93 / 無空格      0

wow, thanks for the statistics.

> > Or: for new articles, we can start to require spaces between.
> 
> I am sympathetic, since spaces are what I would write myself. My worry
> is that it makes the tree inconsistent in a way that is visible within
> a single document -- a reader opening howto.rst would see one style in
> the paragraphs we have rewritten and another in the ones we have not.
> Right now the inconsistency at least correlates with nothing in
> particular.

So apparently I guess this is without doubt: we keep the same style in
current _existing_ articles. And then we are discussing what would be
the preferred style in new translations.

> So I would suggest either:
> 
>   (a) describe current practice in the glossary without making it a
>       rule, and revisit once we have more contributors, or
>   (b) agree on spaces as the target style, and let it spread naturally
>       as files get rewritten -- accepting mixed files in the interim
> 
> I lean towards (a) for now, but I do not feel strongly. If you or the
> zh_CN side prefer (b) I will follow. Either way I can adjust the
> glossary in v4 or as a follow-up.

Both fine I guess, since it's not a big deal.

Correct me if I'm wrong: having spaces or not *does not* affect
rendering as HTML. So, (kind of out of topic, sorry) I'm quite curious,
Do people prefer to view the HTML version of the webpages or the plain
text version? (For the whole documentation, not only translations)

I happened to be reminded that I missed some interesting and useful docs
just because I preferred to read docs on docs.kernel.org, while that
file is not listed in the index.rst file, so I didn't notice it before.
But this seems to be an issue more for English Documentation though. [1]

[1] https://lore.kernel.org/linux-doc/amjsCufED-hm3ixe@wyuan.org/

  parent reply	other threads:[~2026-08-11  4:04 UTC|newest]

Thread overview: 37+ 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
2026-08-10  6:59         ` 葉宸佑
2026-08-10  8:32           ` Dongliang Mu
2026-08-11  4:04           ` 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=anqfRvYGG5-mvKt4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.