All of lore.kernel.org
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: 葉宸佑 <chenyou910331@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
	Dongliang Mu <dzm91@hust.edu.cn>,
	Yanteng Si <si.yanteng@linux.dev>,
	Hu Haowen <2023002089@link.tyut.edu.cn>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 03/16] docs/zh_TW: process: localize terminology in code-of-conduct-interpretation.rst
Date: Sun, 2 Aug 2026 00:26:15 +0800	[thread overview]
Message-ID: <am4eJ9ER0QPz-i1C@wyuan.org> (raw)
In-Reply-To: <CAKspUhKS64JTa8V=3K_v0fnGBn4CKRnmrReQD21WmA8srKw3cg@mail.gmail.com>

On Fri, Jul 31, 2026 at 01:19:58PM +0800, 葉宸佑 wrote:
> On Thu, Jul 30, 2026 at 12:45:25AM +0800, Weijie Yuan wrote:
> > If the following comments are due to my overthinking, then
> >
> > Acked-by: Weijie Yuan <wy@wyuan.org>
> 
> Not overthinking at all -- two of the three are real improvements.
> Thanks for the Acked-by, I will carry it over.
> 
> > > +當個人在違規發生的場合承認自己的行為並作出彌補時
> >
> > In zh_CN, I think we prefer '纠正' (纠正行为). Just a reference.
> 
> You are right, and this is not a cross-strait difference. 彌補 in
> Taiwanese usage takes a loss or a shortfall as its object (彌補損失,
> 彌補不足), so 彌補行為 reads oddly. The English is "makes amends",
> i.e. corrects the behaviour, so 糾正 is the right word here and is
> equally natural in Taiwan. Will change to:
> 
>   當個人在違規發生的場合承認自己的行為並加以糾正時

Nice. Thanks.

> > > +行為準則委員會有責任與所有相關方合作,調查並解決這些報告。
> >
> > 处理报告 or 解决报告?I don't know Taiwan's preference.
> > I would do this in zh_CN:
> > 行为准则委员会有责任与所有相关方合作,对这类报告进行调查并予以处理。
> 
> Also right, and again not a regional difference -- 解決 takes a
> problem as its object, not a report, so 解決報告 is simply wrong in
> both variants. Taiwan says 處理報告 / 處理申訴. I will follow your
> sentence structure:
> 
>   行為準則委員會有責任與所有相關方合作,對這類報告進行調查並予以處理。
> 
> > > +行為準則委員會衷心希望,需要要求公開道歉的不可接受行為,在未來仍然極為罕見。
> >
> > 行为准则委员会衷心希望,那些需要公开道歉的不可接受行为在未来能继续成为极为
> > 罕见的现象。
> >
> > .. seems more clear and coherent?
> 
> This one I would rather keep as is, if you do not mind. Both are
> understandable, so this is a style call rather than a
> correctness one.

Agreed that this is just style call, so doesn't make much sense. I'm
definitely fine with your decision.

Thanks!

  reply	other threads:[~2026-08-01 16:26 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28  9:10 [PATCH v2 00/16] docs/zh_TW: localize terminology and sync process/ documents Chen-Yu Yeh
2026-07-28  9:10 ` [PATCH v2 01/16] docs/zh_TW: process: localize terminology in 7.AdvancedTopics.rst Chen-Yu Yeh
2026-07-29 16:08   ` Weijie Yuan
2026-07-31  5:14     ` 葉宸佑
2026-07-31 18:12       ` Weijie Yuan
2026-07-28  9:10 ` [PATCH v2 02/16] docs/zh_TW: process: localize terminology in 1.Intro.rst Chen-Yu Yeh
2026-07-28  9:10 ` [PATCH v2 03/16] docs/zh_TW: process: localize terminology in code-of-conduct-interpretation.rst Chen-Yu Yeh
2026-07-29 16:45   ` Weijie Yuan
2026-07-31  5:19     ` 葉宸佑
2026-08-01 16:26       ` Weijie Yuan [this message]
2026-07-28  9:10 ` [PATCH v2 04/16] docs/zh_TW: process: localize terminology in license-rules.rst Chen-Yu Yeh
2026-08-03 16:08   ` Weijie Yuan
2026-07-28  9:10 ` [PATCH v2 05/16] docs/zh_TW: process: localize terminology in email-clients.rst Chen-Yu Yeh
2026-08-03 16:09   ` Weijie Yuan
2026-07-28  9:10 ` [PATCH v2 06/16] docs/zh_TW: process: localize terminology in programming-language.rst Chen-Yu Yeh
2026-07-28  9:10 ` [PATCH v2 07/16] docs/zh_TW: process: localize terminology in coding-style.rst Chen-Yu Yeh
2026-07-28  9:10 ` [PATCH v2 08/16] docs/zh_TW: process: localize terminology in stable-kernel-rules.rst Chen-Yu Yeh
2026-08-05 16:20   ` Weijie Yuan
2026-07-28  9:10 ` [PATCH v2 09/16] docs/zh_TW: process: localize terminology in 5.Posting.rst Chen-Yu Yeh
2026-07-28  9:10 ` [PATCH v2 10/16] docs/zh_TW: process: localize terminology in 2.Process.rst Chen-Yu Yeh
2026-08-03 16:22   ` Weijie Yuan
2026-08-04 18:48     ` 葉宸佑
2026-08-07 13:28       ` Weijie Yuan
2026-08-10  6:59         ` 葉宸佑
2026-08-10  8:32           ` Dongliang Mu
2026-08-11  4:04           ` Weijie Yuan
2026-07-28  9:10 ` [PATCH v2 11/16] docs/zh_TW: process: localize terminology in howto.rst Chen-Yu Yeh
2026-08-05  6:43   ` Weijie Yuan
2026-07-28  9:10 ` [PATCH v2 12/16] docs/zh_TW: process: localize terminology in embargoed-hardware-issues.rst Chen-Yu Yeh
2026-08-05  6:49   ` Weijie Yuan
2026-07-28  9:10 ` [PATCH v2 13/16] docs/zh_TW: process: localize terminology in submitting-patches.rst Chen-Yu Yeh
2026-08-05  7:06   ` Weijie Yuan
2026-07-28  9:10 ` [PATCH v2 14/16] docs/zh_TW: process: localize terminology in 8.Conclusion.rst Chen-Yu Yeh
2026-07-28  9:10 ` [PATCH v2 15/16] docs/zh_TW: process: localize terminology in index.rst Chen-Yu Yeh
2026-07-28  9:10 ` [PATCH v2 16/16] docs/zh_TW: Add a glossary for Traditional Chinese translations Chen-Yu Yeh
2026-07-28 13:36   ` Alex Shi
     [not found]     ` <CAKspUh+nRVUXxr9-S9D7jK9nTR3Emwer1ZFOdLQeChGBN+Hc-g@mail.gmail.com>
2026-07-28 18:24       ` 葉宸佑

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=am4eJ9ER0QPz-i1C@wyuan.org \
    --to=wy@wyuan.org \
    --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 \
    /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.