From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Pereira <danielmaraboo@gmail.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>, Alex Shi <alexs@kernel.org>,
Yanteng Si <si.yanteng@linux.dev>,
Dongliang Mu <dzm91@hust.edu.cn>,
Chen-Yu Yeh <chenyou910331@gmail.com>, Weijie Yuan <wy@wyuan.org>,
Federico Vaga <federico.vaga@vaga.pv.it>,
Akira Yokosawa <akiyks@gmail.com>,
Carlos Bilbao <carlos.bilbao@kernel.org>,
Avadhut Naik <avadhut.naik@amd.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] docs: doc-guide: add a guide for translators
Date: Tue, 27 Oct 2026 09:49:10 -0600 [thread overview]
Message-ID: <87pkwvrvnt.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20261015125644.12908-2-danielmaraboo@gmail.com>
Daniel Pereira <danielmaraboo@gmail.com> writes:
> The documentation has seven translations, but nothing in the English
> documentation explains how to contribute to them. The only guide that
> exists, Documentation/translations/zh_CN/how-to.rst, is written in
> Chinese and covers the zh_CN translation only.
>
> As a result, the same problems come up over and over in the review of
> translation patches: labels and citations copied from the original,
> which are global in Sphinx and collide with the English ones; partial
> builds with SPHINXDIRS that hide those collisions; lines over 80
> columns; translations not added to any toctree; missing commit
> descriptions, tags separated by blank lines, HTML email rejected by the
> lists, and the documentation maintainer left out of the recipients.
>
> Add Documentation/doc-guide/translations.rst, a guide that covers the
> whole workflow of a translation:
So I finally managed to read through this ... sorry for taking so long.
Thanks for putting this together, I think it will be useful.
I don't have a lot of comments beyond what others have particularly
said. I would definitely echo Federico's suggestion about not
duplicating the material found in the other process documents. Length
and verbosity makes documents less approachable, so anything you can do
to make this one more concise will help. I'd just tell people to read
and understand the relevant process documents.
One little thing I might add: anybody who spends time with our
documentation will surely find things that can be improved in the
original as well. I'd encourage all translators to send fixes to the
English versions when they find these things; that will make it better
for everybody.
Thanks,
jon
next prev parent reply other threads:[~2026-10-27 15:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 12:56 [PATCH v2 0/2] docs: " Daniel Pereira
2026-10-15 12:56 ` [PATCH v2 1/2] docs: doc-guide: " Daniel Pereira
2026-10-18 0:03 ` Federico Vaga
2026-10-22 17:09 ` Daniel Pereira
2026-10-26 23:01 ` Federico Vaga
2026-10-18 3:40 ` Weijie Yuan
2026-10-19 4:11 ` Alex Shi
2026-10-19 4:37 ` 慕冬亮
2026-10-22 17:09 ` Daniel Pereira
2026-10-23 2:10 ` Dongliang Mu
2026-10-23 20:18 ` 葉宸佑
2026-10-24 13:28 ` Daniel Pereira
2026-10-25 3:22 ` Dongliang Mu
2026-10-25 13:10 ` Daniel Pereira
2026-10-25 13:57 ` Akira Yokosawa
2026-10-25 16:11 ` Weijie Yuan
2026-10-27 15:49 ` Jonathan Corbet [this message]
2026-10-15 12:56 ` [PATCH v2 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=87pkwvrvnt.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=alexs@kernel.org \
--cc=avadhut.naik@amd.com \
--cc=carlos.bilbao@kernel.org \
--cc=chenyou910331@gmail.com \
--cc=danielmaraboo@gmail.com \
--cc=dzm91@hust.edu.cn \
--cc=federico.vaga@vaga.pv.it \
--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 \
--cc=wy@wyuan.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®