Linux Documentation
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Chen-Yu Yeh <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 01/16] docs/zh_TW: process: localize terminology in 7.AdvancedTopics.rst
Date: Thu, 30 Jul 2026 00:08:35 +0800	[thread overview]
Message-ID: <amolg7NpObNT8Gnb@wyuan.org> (raw)
In-Reply-To: <20260728091038.171033-2-chenyou910331@gmail.com>

On Tue, Jul 28, 2026 at 05:10:23PM +0800, Chen-Yu Yeh wrote:
> Localize mainland terms to Taiwanese Mandarin (內核→核心, 軟件→軟體,
> 高級→進階, 項目→專案, 用戶→使用者, ...) and sync with the English
> original (Github → GitHub).
> 
> update to commit 5ce70894f6ca ("Doc: correct spelling and wording
> mistakes")

Reviewed-by: Weijie Yuan <wy@wyuan.org>

> Signed-off-by: Chen-Yu Yeh <chenyou910331@gmail.com>
> ---
>  .../zh_TW/process/7.AdvancedTopics.rst        | 110 +++++++++---------
>  1 file changed, 56 insertions(+), 54 deletions(-)

A small gripe: what is the best practice for reviewing a new revision of
a patch series after it has been rerolled?

For this series, I found the output of b4 diff rather difficult to read,
so I had to split out the individual patches and inspect them using git
mailinfo and interdiff. That, however, means losing the built-in
highlighting provided by b4 diff.

In this case, I would say a range-diff/interdiff for each patch seems to
be a good solution in general, while obviously that's not that
convenient for the patch sender.

Perhaps there is no best solution to this problem; Git may simply not be
expected to handle Chinese text particularly well.

I would appreciate it if some one more experienced could give me some
tips. But this series is however quite special. Usually we won't meet a
large series which contains many diffs in it like this.

Then I suppose we'll just have to ride out these growing pains. ;-)

  reply	other threads:[~2026-07-29 16:09 UTC|newest]

Thread overview: 21+ 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 [this message]
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-28  9:10 ` [PATCH v2 04/16] docs/zh_TW: process: localize terminology in license-rules.rst Chen-Yu Yeh
2026-07-28  9:10 ` [PATCH v2 05/16] docs/zh_TW: process: localize terminology in email-clients.rst Chen-Yu Yeh
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-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-07-28  9:10 ` [PATCH v2 11/16] docs/zh_TW: process: localize terminology in howto.rst Chen-Yu Yeh
2026-07-28  9:10 ` [PATCH v2 12/16] docs/zh_TW: process: localize terminology in embargoed-hardware-issues.rst Chen-Yu Yeh
2026-07-28  9:10 ` [PATCH v2 13/16] docs/zh_TW: process: localize terminology in submitting-patches.rst Chen-Yu Yeh
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=amolg7NpObNT8Gnb@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