From: Alex Shi <seakeel@gmail.com>
To: Weijie Yuan <wy@wyuan.org>, Daniel Pereira <danielmaraboo@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
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>,
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,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v2 1/2] docs: doc-guide: add a guide for translators
Date: Mon, 19 Oct 2026 12:11:50 +0800 [thread overview]
Message-ID: <966ea621-9d1e-4d52-8351-5dcbf88f93b7@gmail.com> (raw)
In-Reply-To: <atQ_mXYNqs4tnDpW@wyuan.org>
On 2026/10/18 11:40, Weijie Yuan wrote:
> Oh, btw. There's a comment about ":Original:" from Jani [1]:
It's good to remove them if no one needs this. But I didn't know other
type documents...
>
> | I'm wondering, are these :Original: fields useful anymore since the
> | translations extension adds the button to switch between languages?
> |
> | The pretty much hard-coded expectation is that the English version at
> | path/to/foo.rst is the original, and its translations are at
> | translations/xx_YY/path/to/foo.rst.
> |
> | I.e. neither the HTML nor the RST benefit from it, and it's just
> | repetition.
>
> Perhaps we could have a bit of discussion here?
next prev parent reply other threads:[~2026-10-19 4:11 UTC|newest]
Thread overview: 7+ 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-18 3:40 ` Weijie Yuan
2026-10-19 4:11 ` Alex Shi [this message]
2026-10-19 4:37 ` 慕冬亮
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=966ea621-9d1e-4d52-8351-5dcbf88f93b7@gmail.com \
--to=seakeel@gmail.com \
--cc=akiyks@gmail.com \
--cc=alexs@kernel.org \
--cc=avadhut.naik@amd.com \
--cc=carlos.bilbao@kernel.org \
--cc=chenyou910331@gmail.com \
--cc=corbet@lwn.net \
--cc=danielmaraboo@gmail.com \
--cc=dzm91@hust.edu.cn \
--cc=federico.vaga@vaga.pv.it \
--cc=jani.nikula@linux.intel.com \
--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®