From: Weijie Yuan <wy@wyuan.org>
To: 葉宸佑 <chenyou910331@gmail.com>
Cc: Dongliang Mu <dzm91@hust.edu.cn>,
Yanteng Si <si.yanteng@linux.dev>, Alex Shi <alexs@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/13] docs/zh_TW: process: add translations of 13 documents
Date: Tue, 10 Nov 2026 00:13:21 +0800 [thread overview]
Message-ID: <avHxIaArNRciqEqz@wyuan.org> (raw)
In-Reply-To: <CAKspUh+n2giArsUzKeHq1F-D8VkV89kUNevc-hFnpxjWFWNZsw@mail.gmail.com>
Chen-Yu Yeh <chenyou910331@gmail.com> writes:
> > In the current stage, it would be more important
> > to fix all severe issues in the translation other than adding more
> > translation.
>
> Thanks for sharing your plan. I think you are right that fixing
> existing translations and making them reference each other matters more
> than adding new ones, and I'd like zh_TW to work that way too.
>
> zh_TW is at an earlier stage, though: it has only a few dozen
> translations, most of them converted from zh_CN, so there are few zh_TW
> documents for references to point at yet. Much of what needs fixing
> also only became visible while translating; that is how the terminology
> issues and these unused labels came up.
>
> So my plan is to first finish process/, the area the scope RFC commits
> us to maintaining. After that I'll follow your approach: resolve the
> references so they point at zh_TW documents where a translation exists,
> fix the remaining issues in the existing translations, and only then
> add new translations. The terminology cleanup will go in alongside.
Sure, so in conclusion and for later reference:
* We hope and aim to finish the process directory in this cycle.
Since this has been decided long ago and has been kicked off recently,
let's finsih process first. During this period, we try to link to
existing tw translations first; if there's no translations existing,
fall back to English original for now.
When finished, we can check what's the status of referencing: how many
we can refer to tw_docs, how many we are refering outside of our
translations. Then, depending on the actual situation, a decision will
be made as to whether the translation scope needs to be expanded.
* Finish "Working with the development community", i.e. cover maintainer
directory.
If possible, we can finish it in 7.4 cycle. But there's no hurry, we
can also leave it for 7.5 cycle to prevent last-minute changes.
We could also do the reference check and decide how our translation will
expand when the above is all done.
That being said, now I'm not at my workstation, I'll try to review
Chen-Yu's patch bomb ;) within this week. And check how much left here
for process (or finished?), then push forward to our goal. A big thank
to Chen-Yu for taking the most arduous work!
And yes, I think most of the translation of tw for now do have
references to the original English text, which is an inevitable
situation at present. That's our intention, isn't it? If we cannot
guarantee the quality of the translations, the best we can do is to
temporarily keep them referring to the original text to avoid any
misunderstandings or errors. Of course, it would be wonderful if all the
content could be included in a native language, just like zh_CN. But for
now, let's finish our first goal of zh_TW, and then catch up with CN.
So I fully agree and support what zh_CN is doing, we can do that for
zh_TW after this goal finished.
By the way, I've started collecting signatures from k.org developers
weeks ago for putting our dev tree on git.k.org as soon as possible to
improve our efficiency. Hope I can get it done soon, but nevermind. This
way, we won't have to bother Alex too much for help. :) Thanks Alex so
much for taking care of us recently, there are enough work for him in
the zh_CN side. :)
Thank you all for pushing this forward.
next prev parent reply other threads:[~2026-11-09 16:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 11:35 Chen-Yu Yeh
2026-11-06 11:35 ` [PATCH 01/13] docs/zh_TW: process: add researcher-guidelines.rst translation Chen-Yu Yeh
2026-11-06 11:35 ` [PATCH 02/13] docs/zh_TW: process: add cve.rst translation Chen-Yu Yeh
2026-11-06 11:35 ` [PATCH 03/13] docs/zh_TW: process: add applying-patches.rst translation Chen-Yu Yeh
2026-11-06 11:35 ` [PATCH 04/13] docs/zh_TW: process: add maintainer-pgp-guide.rst translation Chen-Yu Yeh
2026-11-06 11:35 ` [PATCH 05/13] docs/zh_TW: process: add changes.rst translation Chen-Yu Yeh
2026-11-06 11:35 ` [PATCH 06/13] docs/zh_TW: process: add handling-regressions.rst translation Chen-Yu Yeh
2026-11-06 11:35 ` [PATCH 07/13] docs/zh_TW: process: add deprecated.rst translation Chen-Yu Yeh
2026-11-06 11:35 ` [PATCH 08/13] docs/zh_TW: process: add kernel-docs.rst translation Chen-Yu Yeh
2026-11-06 11:35 ` [PATCH 09/13] docs/zh_TW: process: add maintainer-handbooks.rst translation Chen-Yu Yeh
2026-11-06 11:35 ` [PATCH 10/13] docs/zh_TW: process: add contribution-maturity-model.rst translation Chen-Yu Yeh
2026-11-06 11:35 ` [PATCH 11/13] docs/zh_TW: process: add conclave.rst translation Chen-Yu Yeh
2026-11-06 11:35 ` [PATCH 12/13] docs/zh_TW: process: add threat-model.rst translation Chen-Yu Yeh
2026-11-06 11:35 ` [PATCH 13/13] docs/zh_TW: process: add maintainers.rst translation Chen-Yu Yeh
2026-11-07 12:44 ` [PATCH 00/13] docs/zh_TW: process: add translations of 13 documents Dongliang Mu
2026-11-08 10:13 ` Dongliang Mu
2026-11-09 13:11 ` 葉宸佑
2026-11-09 16:13 ` Weijie Yuan [this message]
2026-11-09 16:25 ` Weijie Yuan
2026-11-09 13:10 ` 葉宸佑
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=avHxIaArNRciqEqz@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 \
/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®