From: Weijie Yuan <wy@wyuan.org>
To: Alex Shi <seakeel@gmail.com>
Cc: 葉宸佑 <chenyou910331@gmail.com>, "Dongliang Mu" <dzm91@hust.edu.cn>,
"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: Sun, 12 Jul 2026 15:23:51 +0800 [thread overview]
Message-ID: <alNBB1Ju2GGk6Uqu@wyuan.org> (raw)
In-Reply-To: <40155119-b6c1-40cc-bbf2-5d1bbe5743e8@gmail.com>
On Sun, Jul 12, 2026 at 12:33:36PM +0800, Alex Shi wrote:
> On 2026/7/12 01:21, Weijie Yuan wrote:
> > > For what it's worth, I am from Taiwan and a native zh_TW speaker.
> > > That is actually what motivated this patch: much of the current text
> > > reads like converted zh_CN rather than natural Taiwanese Mandarin,
> > So, back to my confusion again, and quote myself:
> >
> > How exactly we define the position of Traditional Chinese or zh_TW?
> >
> > 1. Simple conversion between simplified and traditional Chinese
> > characters
> > 2. Taiwanese localized traditional Chinese
> >
> > This issue needs to be confirmed by the senior maintenance personnel.
> > (I will review the archives to confirm. If there is already a clear
> > definition, please forgive me.)
>
> Hi Weijie,
>
> Regarding this issue, we also have Hong Kong and Macau Traditional
> Chinese. While they are mutually intelligible with Taiwanese Chinese,
> there are slight differences. If a Taiwan-specific Traditional Chinese
> translation is required, does this imply that we would also need other
> corresponding localized translations? This is similar to English-the
> English used in the UK, the US, Australia, and so on all differ
> slightly, yet the kernel documentation does not maintain separate
> versions for different countries.
Hi Alex,
Agreed, so I can understand that your point is that Traditional Chinese
(Taiwan) actually doesn't have much practical use?
> Furthermore, aside from a few differences in computing terminology,
> there are no significant differences between Taiwanese Chinese and
> Mainland Chinese that would lead to misunderstandings.
Agreed.
> In fact, many of the current Simplified Chinese translations were
> contributed by people from Taiwan, like Haowen and others.
Sorry, but I guess he is very likely not from Taiwan.
1. Based on the recent several patches, his initial translation was
merely a simple conversion between simplified and traditional Chinese
characters, without taking into account the local language expressions
specific to Taiwan. If he were from Taiwan, many obvious linguistic
habits would surely have been noticed, such as "软件" vs. "軟體".
2. His previous email domain shows he is studying in the mainland.
3. His personal blog is written in simplified chinese.
Of course, I have no intention of intruding on others' privacy. I just
merely made a brief observation.
> To avoid scattering our efforts, I suggest we minimize fragmentation
> as much as possible. When it comes to technical documentation
> translation, not literary translation, a straightforward, unadorned,
> and free from misunderstandings is the best translation and easy to
> maintain. Let's keep thing simple, unless sth is really necessary.
Absolutely agreed. These minor issues in expression habits, of course,
will not have much impact on reading.
Given that this document has not been maintained for ~2 years and these
patches to the terminology actually don't have much significance, it
might be more appropriate to directly declare the status of Traditional
Chinese as "Orphan" provisionally for now, and remove it directly in the
near future, until Hao Wen's return and opinion. Or maybe, waiting for a
new good soul to take over, which is unpredictable.
Thanks,
Weijie
next prev parent reply other threads:[~2026-07-12 7:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 8:25 [PATCH v2] docs: zh_TW: process: localize terminologies and improve fluency in 8.Conclusion 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
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 [this message]
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=alNBB1Ju2GGk6Uqu@wyuan.org \
--to=wy@wyuan.org \
--cc=2023002089@link.tyut.edu.cn \
--cc=alexs@kernel.org \
--cc=cat@malon.dev \
--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=mudongliangabcd@gmail.com \
--cc=seakeel@gmail.com \
--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