Re: [PATCH v2 01/16] docs/zh_TW: process: localize terminology in 7.AdvancedTopics.rst

[Weijie Yuan <wy@wyuan.org>]

On Fri, Jul 31, 2026 at 01:14:03PM +0800, 葉宸佑 wrote:
> > A small gripe: what is the best practice for reviewing a new revision
> > of a patch series after it has been rerolled?
> 
> Sorry about that -- a 16-patch Chinese series is about the worst case
> for this, and it is my problem to make easier, not yours.

That's OK, no need to say sorry. :-)

> For v3 I will use "git format-patch --range-diff=<v2-tag>", which puts
> a per-patch range-diff in the cover letter. That should at least show
> you which patches actually changed and how, without you having to
> reconstruct it.

Yes, that's how Git project is always recommending to do, while I'm not
familiar with the convention or requirements in Kernel series rerolls:

https://youtu.be/p79IjNay4mY?t=995&si=qgTDTBL9UzRH0eBx

And as I said, b4 diff could also do that, even though reading Chinese
diffs are not easy. Feels like that Git cannot recognize the inline
changes in Chinese very well. (i.e. & e.g. cannot recognize the actual
'word-diff' [1], such as: This is a [-bad-]{+good+} example.) And also,
this time many line breaks and reordering have been added.

[1] https://git-scm.com/docs/git-diff#Documentation/git-diff.txt---word-diffmode

So I'm fine with it, such situations are not too frequent.

> Longer term this feels like something the zh_TW how-to should cover:
> how to send and review Chinese translation series specifically. I have
> been collecting notes while doing this one (line-width handling for
> CJK, why checkpatch miscounts Chinese lines, the reflow pitfalls) and
> would be happy to draft that section once this series lands.

Very much appreciated! Kind of like 'Writing docs for how to write
docs'! ;-)

Constantly summarizing and improving such documents will undoubtedly be
very useful for us and future contributors.

Thanks!