All of lore.kernel.org
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: 葉宸佑 <chenyou910331@gmail.com>, "Dongliang Mu" <dzm91@hust.edu.cn>,
	"Hu Haowen" <2023002089@link.tyut.edu.cn>,
	"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 13:15:59 +0800	[thread overview]
Message-ID: <alMjD_dNWVgPKOlN@wyuan.org> (raw)
In-Reply-To: <87wlv1i985.fsf@trenco.lwn.net>

On Sat, Jul 11, 2026 at 02:04:26PM -0600, Jonathan Corbet wrote:
> Weijie Yuan <wy@wyuan.org> writes:
> 
> > 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.)
> 
> "Senior maintenance personnel" in this case is the people who actually
> step up to maintain this translation.  There is no higher level of
> authority that needs to somehow sign off on it.

Yeah, so, due to the current special circumstances, I actually mean that
I want to seek the opinions of the Simplified Chinese team, and then
finally have you Ack.

> The existing translation is essentially abandoned; if somebody wants
> to carry it forward -- and stay with it -- with a shift in focus, I
> think that is just fine.

Yes, hope that the following discussion will lead to a consensus.

Thanks,
Weijie

  reply	other threads:[~2026-07-12  5:16 UTC|newest]

Thread overview: 23+ 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 [this message]
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=alMjD_dNWVgPKOlN@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=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.