From: Weijie Yuan <wy@wyuan.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
Chen-Yu Yeh <chenyou910331@gmail.com>,
Dongliang Mu <dzm91@hust.edu.cn>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Plans for zh_TW: prioritize maintainability over coverage
Date: Tue, 28 Jul 2026 23:59:31 +0800 [thread overview]
Message-ID: <amjR4_X_C1mEPtfY@wyuan.org> (raw)
In-Reply-To: <87wlugk1ty.fsf@trenco.lwn.net>
On Mon, Jul 27, 2026 at 07:18:49AM -0600, Jonathan Corbet wrote:
> Weijie Yuan <wy@wyuan.org> writes:
>
> > 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.
>
> This seems like a good approach in general.
Thanks for your support.
> Of course, somebody is sure to point out that the *English*
> documentation is often not maintained to such a standard. We have a lot
> of stuff that somebody dropped into the tree years ago and nobody has
> updated since.
That's very modest of you to say so. The English documentation is much
larger in scale, involves more complex workflows, and passes through
many more hands, so maintaining it is by no means an easy task.
The kernel community encompasses so many subsystems and people, and
reaching consensus is not always easy, so I completely understand the
constraints you are working under. (Yeah, The assisted-by trailer
discussion may be an example) By comparison, we have it much easier on
our side.
> I shall continue to try to get the community to live up to your level
> of diligence!
You're giving us too much credit. But it may be a little early to praise
us - we're only just getting started. ;-)
Since I´m new here, I´ve had to dig through the history of this part to
get up to speed quickly, and just watched Kernel Recipes 2016 - Kernel
documentation again, how time flies!
Thank you, Jon, for a decade of tireless dedication.
next prev parent reply other threads:[~2026-07-28 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 8:42 [RFC] Plans for zh_TW: prioritize maintainability over coverage Weijie Yuan
2026-07-27 13:18 ` Jonathan Corbet
2026-07-28 15:59 ` Weijie Yuan [this message]
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=amjR4_X_C1mEPtfY@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 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.