Linux Documentation
 help / color / mirror / Atom feed
From: Alex Shi <seakeel@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
	CHEN-YOU-0331 <chenyou910331@gmail.com>,
	Hu Haowen <2023002089@link.tyut.edu.cn>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	alexs@kernel.org, Dongliang Mu <dzm91@hust.edu.cn>,
	Yanteng Si <si.yanteng@linux.dev>
Subject: Re: [PATCH] docs: zh_TW: process: localize terminologies and improve fluency in 8.Conclusion
Date: Fri, 29 May 2026 12:04:14 +0800	[thread overview]
Message-ID: <c26e8fce-de82-4fed-a749-41c4f051eacd@gmail.com> (raw)
In-Reply-To: <87cxyfllhr.fsf@trenco.lwn.net>



On 2026/5/28 21:19, Jonathan Corbet wrote:
> CHEN-YOU-0331<chenyou910331@gmail.com> writes:
> 
>> Translate PRC tech terms into Taiwanese tech terms (e.g.,
>> 內核 -> 核心, 代碼 -> 程式碼, 軟件 -> 軟體) to improve
>> readability for local developers. Also, rephrase several
>> awkward sentences to make the document more fluent.
>>
>> Signed-off-by: CHEN-YOU-0331<chenyou910331@gmail.com>
>> ---
>>   .../zh_TW/process/8.Conclusion.rst            | 45 +++++++++----------
>>   1 file changed, 22 insertions(+), 23 deletions(-)
> I, of course, am in no position to judge these changes, and I worry
> about getting into some sort of turf war over differences in
> terminology.  Alex, are you able to give me a recommendation on this
> change?
> 
CC to Dongliang and Yanteng,

Yes, we could take care of tradition Chinese translation in Haowen's 
absence.

thanks!
Alex

> Meanwhile, the signoff should have your proper name, please.
> 
> Thanks,
> 
> jon
> 


  reply	other threads:[~2026-05-29  4:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28  4:13 [PATCH] docs: zh_TW: process: localize terminologies and improve fluency in 8.Conclusion CHEN-YOU-0331
2026-05-28 13:19 ` Jonathan Corbet
2026-05-29  4:04   ` Alex Shi [this message]
2026-05-29  4:33 ` Dongliang Mu
2026-05-29 11:25   ` 葉宸佑
2026-05-29 11:33     ` Dongliang Mu

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=c26e8fce-de82-4fed-a749-41c4f051eacd@gmail.com \
    --to=seakeel@gmail.com \
    --cc=2023002089@link.tyut.edu.cn \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox