From: Dongliang Mu <dzm91@hust.edu.cn>
To: "Weijie Yuan" <wy@wyuan.org>, 葉宸佑 <chenyou910331@gmail.com>
Cc: Hu Haowen <2023002089@link.tyut.edu.cn>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Dongliang Mu <mudongliangabcd@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Yuchen Tian <cat@malon.dev>, Alex Shi <alexs@kernel.org>,
Yanteng Si <si.yanteng@linux.dev>
Subject: Re: [PATCH v2] docs: zh_TW: process: localize terminologies and improve fluency in 8.Conclusion
Date: Fri, 10 Jul 2026 21:15:12 +0800 [thread overview]
Message-ID: <57e42f43-44dd-4b22-8d81-c88e20016138@hust.edu.cn> (raw)
In-Reply-To: <alDs8bnIK8bWApIr@wyuan.org>
On 7/10/26 9:00 PM, Weijie Yuan wrote:
> On Fri, Jul 10, 2026 at 04:49:30PM +0800, 葉宸佑 wrote:
>> Gentle ping.
>>
>> This v2 addressed the review comments from Alex and Dongliang.
>> Is there anything else I should improve, or is it queued somewhere
>> I might have missed?
> Hi Chenyou,
>
> I think currently having Alex apply your patch is a temporary measure,
> because the maintainer of traditional Chinese seems unlikely to be
> available in the near future.
I can help review patches in traditional Chinese. With the help of LLM,
it is fine for me to handle local terminologies in zh_TW.
Dongliang Mu
>
> Outside the patch itself, I noticed that Traditional Chinese is actually
> in a state of stagnation, which makes me think that receiving such
> patches is a temporary solution rather than a long-term fix.
>
> As Jonathan said, "...But there does come a point where a translation
> is so obsolete that it does more harm than good and there are no
> prospects of it being updated."
>
> So, after a period of about two years of stagnation, the Traditional
> Chinese documents seem to have really reached an unreadable state. This
> is something we don't want to see, but we must accept the reality and
> then take action. Please note that I have no intention of offending
> Haowen. On the contrary, I am definitely grateful for all that he has
> done.
>
> I did some interactions with one of the L10n Taiwan team (who are
> involved with Git L10n) [1] in their telegram channel a few days before,
> but sadly they said the biggest problems are:
>
> 1. No one is willing to take over. (hey, I totally understand)
> 2. There are different opinions on translation. (I don't know the
> deeper details)
>
> Besides, I'm also very curious about how exactly we define the position
> of traditional Chinese or zh_TW. From my rough observation, the existing
> documents merely performed a simple conversion between simplified and
> traditional Chinese, without taking into account the local expressions
> specific to Taiwan. Therefore, that's why we are receiving the patch
> here and commit aba18be23f14 ("docs/zh_TW: replace 接口 with 介面 in stable-api-nonsense.rst")
> (Please correct me if I'm wrong, as I have not got into many
> translated pages)
>
> So if we are doing zh_TW instead of a direct simplified and traditional
> Chinese conversion, I don't think we can handle this properly without
> the help of Taiwanese friends.
>
> Of course, I feel quite ashamed that I'm saying these above here without
> having made any substantial contributions to this community, sorry.
>
> Could we discuss this matter in another thread? Very sorry Chenyou, what
> I'm saying is completely unrelated to the patch itself.
>
> Finally, I would like to express my sincere gratitude to Haowen.
>
> Thanks,
> Weijie
>
> [1] https://l10n.tw/
next prev parent reply other threads:[~2026-07-10 13:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 8:25 Chen-Yu Yeh
2026-07-10 8:49 ` 葉宸佑
2026-07-10 13:00 ` Weijie Yuan
2026-07-10 13:07 ` Weijie Yuan
2026-07-10 13:15 ` Dongliang Mu [this message]
2026-07-10 18:01 ` 葉宸佑
2026-07-11 17:21 ` Weijie Yuan
2026-07-11 20:04 ` Jonathan Corbet
2026-07-12 5:15 ` Weijie Yuan
2026-07-12 4:33 ` Alex Shi
2026-07-12 7:23 ` Weijie Yuan
2026-07-13 2:44 ` 葉宸佑
2026-07-13 3:49 ` Dongliang Mu
2026-07-13 5:33 ` Weijie Yuan
2026-07-13 6:35 ` 葉宸佑
2026-07-13 9:03 ` 葉宸佑
2026-07-13 9:41 ` Dongliang Mu
2026-07-13 10:23 ` Weijie Yuan
2026-07-13 19:47 ` 葉宸佑
2026-07-14 6:22 ` Alex Shi
2026-07-14 7:42 ` Weijie Yuan
2026-07-10 13:05 ` Dongliang Mu
2026-07-11 5:21 ` 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=57e42f43-44dd-4b22-8d81-c88e20016138@hust.edu.cn \
--to=dzm91@hust.edu.cn \
--cc=2023002089@link.tyut.edu.cn \
--cc=alexs@kernel.org \
--cc=cat@malon.dev \
--cc=chenyou910331@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mudongliangabcd@gmail.com \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=wy@wyuan.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