From: Weijie Yuan <wy@wyuan.org>
To: Chen-Yu Yeh <chenyou910331@gmail.com>
Cc: corbet@lwn.net, alexs@kernel.org, dzm91@hust.edu.cn,
si.yanteng@linux.dev, srcres258@furdevs.cn,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] docs/zh_TW: mark translations that are not kept in sync
Date: Sat, 3 Oct 2026 12:37:49 +0800 [thread overview]
Message-ID: <asCGnSMAh_XFnWMD@wyuan.org> (raw)
In-Reply-To: <20260929131142.266819-1-chenyou910331@gmail.com>
On 2026-09-29 21:11:37 +0800, Chen-Yu Yeh <chenyou910331@gmail.com> wrote:
> As agreed in the zh_TW scope discussion [1], process/ is the part of
> zh_TW that is kept current; everything else now says in the file
> itself that nobody keeps it in sync, and points readers at the English
> original. The rule is per file: the two documents that moved into
> process/ with the relocation series are marked until someone updates
> them.
>
> 1/3 adds the notice and applies it to those two files
> 2/3 applies it to the other 58 translations (one line each)
> 3/3 links filesystems/ and cpu-freq/, which nothing linked before, via
> a translated subsystem-apis.rst, as the English tree does
>
> The notice deliberately has no :orphan: marker: included after
> disclaimer-zh_TW.rst, a second one renders as an empty "orphan" field.
> (Two existing pages already show that field, because something precedes
> the disclaimer include: a stray byte-order mark in
> process/kernel-enforcement-statement.rst and a highlight directive in
> gdb-kernel-debugging.rst. Not fixed here.)
>
> One consequence worth knowing: checktransupdate.py reads the "update to
> commit" line of a translation's latest commit only, so any tree-wide
> patch like 2/3 makes it report every touched file as current. The
> contact-block cleanup already had that effect on most of the tree.
> Fixing it belongs in the tool, not in the translations.
Agreed.
> This applies on top of the relocation series sent alongside it,
> "[PATCH 0/4] docs/zh_TW: relocate translations to follow the English
> layout".
I figured out the applying sequence by myself and then came across this
sentence... :-| ;-)
Thanks.
prev parent reply other threads:[~2026-10-03 4:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 13:11 Chen-Yu Yeh
2026-09-29 13:11 ` [PATCH 1/3] docs/zh_TW: add a notice for translations " Chen-Yu Yeh
2026-10-03 4:45 ` Weijie Yuan
2026-10-03 10:23 ` 葉宸佑
2026-09-29 13:11 ` [PATCH 2/3] docs/zh_TW: mark translations outside the maintained set Chen-Yu Yeh
2026-10-03 4:51 ` Weijie Yuan
2026-09-29 13:11 ` [PATCH 3/3] docs/zh_TW: link filesystems/ and cpu-freq/ from the index Chen-Yu Yeh
2026-10-03 4:54 ` Weijie Yuan
2026-10-03 4:37 ` Weijie Yuan [this message]
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=asCGnSMAh_XFnWMD@wyuan.org \
--to=wy@wyuan.org \
--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 \
--cc=srcres258@furdevs.cn \
/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
all inboxes | Powered by JetHome®