From: Weijie Yuan <wy@wyuan.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Daniel Pereira <danielmaraboo@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
Dongliang Mu <dzm91@hust.edu.cn>
Subject: Re: [PATCH 1/2] docs: doc-guide: add a guide for translators
Date: Thu, 15 Oct 2026 22:03:17 +0800 [thread overview]
Message-ID: <atDdJS0HxZZ7O92B@wyuan.org> (raw)
In-Reply-To: <87o6cvrs27.fsf@trenco.lwn.net>
+cc zh_CN maintainers
On 2026-10-15 07:50:40 -0600, Jonathan Corbet <corbet@lwn.net> wrote:
> Weijie Yuan <wy@wyuan.org> writes:
>
> >> > For the Translator field, zh_TW just did a cleanup to totally remove
> >> > them.
> >>
> >> Makes sense. I dropped the ":Translator:" line from the example, and the
> >> guide keeps the advice to leave contact information to MAINTAINERS.
> >
> > I personally think this is somehow a hard tradeoff, so my opinion is
> > rather neutral, and I respect your decisions.
> >
> > On the one hand, I think keeping this field is indeed a way to give
> > credit to the contributors, which can motivate more contributions and
> > contributors. On the other hand, over the years, this field has seemed a
> > bit cumbersome and inconsistent in both Chinese translations.
>
> I personally don't see why translations are different from any other
> contribution in this regard. The credit lives in the commit logs; we
> don't sprinkle our names throughout the source for every change we make.
Yes, very reasonable.
I haven't found out the reason why we had the "Translator" field at the
very beginning. I guess it might be something like translating a book.
Usually, the translator's name would be written below/near the original
author's name on the title page. (?) However, the difference is that we
have commit logs, so I totally agree.
Then perhaps we could also clean up zh_CN later.
Thanks!
next prev parent reply other threads:[~2026-10-15 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 0:37 [PATCH 0/2] docs: " Daniel Pereira
2026-10-13 0:37 ` [PATCH 1/2] docs: doc-guide: " Daniel Pereira
2026-10-15 11:32 ` Weijie Yuan
2026-10-15 12:55 ` Daniel Pereira
2026-10-15 13:31 ` Weijie Yuan
2026-10-15 13:50 ` Jonathan Corbet
2026-10-15 14:03 ` Weijie Yuan [this message]
2026-10-15 14:17 ` Dongliang Mu
2026-10-13 0:37 ` [PATCH 2/2] docs: pt_BR: translate doc-guide/translations.rst Daniel Pereira
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=atDdJS0HxZZ7O92B@wyuan.org \
--to=wy@wyuan.org \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=danielmaraboo@gmail.com \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®