From: Weijie Yuan <wy@wyuan.org>
To: Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
Chen-Yu Yeh <chenyou910331@gmail.com>,
Dongliang Mu <dzm91@hust.edu.cn>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC] Plans for zh_TW: prioritize maintainability over coverage
Date: Mon, 27 Jul 2026 16:42:13 +0800 [thread overview]
Message-ID: <amcZ5SI3-Hzw4HkJ@wyuan.org> (raw)
Hi Jon and Chinese documentation folks,
Recently I reviewed Jon's talk titled Kernel documentation: update
and future directions. In short, he said we Chinese people are
active, and he "even" thought why somebody is willing to read some
kinds of stuff in Chinese ;-) This led me to reflect on our current
situation.
Translations
+-------------------+-------+----------------------+
| Language | Files | General state |
+-------------------+-------+----------------------+
| Chinese | 332 | Active |
| Chinese (trad) | 97 | Almost abandoned |
| Korean | 5 | Abandoned |
| Italian | 67 | Occasional updates |
| Japanese | 7 | Abandoned |
| Spanish | 37 | Rare updates |
+-------------------+-------+----------------------+ Dec 2025
https://www.youtube.com/watch?v=JXtx_zOHFgo (31:52)
As of July 2026, checktransupdate.py reports the following:
zh_TW: 51 translated files are out of date, involving 221
distinct upstream commits in total.
zh_CN: 171 translated files are out of date, involving 617
distinct upstream commits in total.
First of all, I definitely would love to show my truly respect to
our friendly contributors, but considering the sustainability and
maintainability of the translation work, and more importantly, its
forward-looking nature (in line with the original English version),
I think we need to make some trade-offs.
It comes to me what the maintainer of Sqlite D. Richard Hipp said
about open-source or free software: there's free as in beer and free
as in speech. But there's another one: free as in puppies. When
people send you puppies as the gift, you're morally obligated to
take care of them. So, it's basically what's going on with our work:
Nice and friendly contributors show up and give us their
translations and walk away. If the original English page gets
updated, you'll find that for most of the cases our friendly
contributors won't show up again and maintain it, i.e. update it
as expected.
The facts could certainly have been exaggerated. For both zh_CN&TW,
some articles have indeed remained unchanged for decades. So a
single translation is definitely a one-time solution, which means
they don't need to be touched often.
That's fine with zh_CN right now. But for zh_TW, we have a
significant gap and lag behind. You can easily see it from the above
table. So now we need to prioritize and get things done.
Therefore, for zh_TW, our expected plan is to monitor a list
containing important documents or folders (such as process/
submitting-patches.rst), and set a certain deadline for the latest
update (which can be discussed later, maybe 1/2 months): If no
contributors would like to update it, we as the maintainers will be
responsible for making the updates to ensure that readers who come
across this translation can be assured that the translation is
reliable and not worried about being out of sync with the English
documentation for too much/a long time. We may make the supported
set in the index page, and list out the current "well-cared"
directories or files.
That is to say, we will deliberately select relatively important
articles for translation and hope to maintain this consistently
first. By avoiding the large expansion of the translation coverage
we can't handle, it is possible to truly ensure the quality of each
article that has a translation.
Since the goal set for zh_TW was to catch up with zh_CN first, when
Chen-yu was working on the common articles this period, I was
extensively reviewing the existing content to determine the priority
of traditional Chinese docs, according to the importance and reading
volume, etc, and thereby deciding which specific parts should be
marked unmaintained temporarily.
Sorry for being so lengthy. In summary, our primary goal is to
ensure the timeliness and quality of the translations, and we will
also strive to expand our coverage.
Please feel free to leave your comments.
Thanks,
Weijie & Chen-Yu
next reply other threads:[~2026-07-27 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 8:42 Weijie Yuan [this message]
2026-07-27 13:18 ` [RFC] Plans for zh_TW: prioritize maintainability over coverage Jonathan Corbet
2026-07-28 15:59 ` Weijie Yuan
2026-07-28 16:05 ` Weijie Yuan
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=amcZ5SI3-Hzw4HkJ@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=skhan@linuxfoundation.org \
/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