From: Vegard Nossum <vegard.nossum@oracle.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org,
Federico Vaga <federico.vaga@vaga.pv.it>,
Akira Yokosawa <akiyks@gmail.com>,
Carlos Bilbao <carlos.bilbao@amd.com>,
Alex Shi <alexs@kernel.org>, Yanteng Si <siyanteng@loongson.cn>,
Hu Haowen <src.res.211@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: translations: add translations links when they exist
Date: Sat, 28 Oct 2023 20:51:36 +0200 [thread overview]
Message-ID: <bc41e32e-e899-427c-9aea-eba411e5bcef@oracle.com> (raw)
In-Reply-To: <20231028162931.261843-1-vegard.nossum@oracle.com>
This went a bit fast... corrections below.
On 28/10/2023 18:29, Vegard Nossum wrote:
> Add a new Sphinx extension that knows about the translations of kernel
> documentation and can insert links to the translations at the top of
> the document.
[...]
> Testing: make htmldocs with v7.3.0.
*Sphinx v7.3.0.
> +all_languages = {
> + # English is always first
> + None: 'English',
> +
> + # Keep the rest sorted alphabetically
> + 'zh_CN': 'Chinese',
> + 'it_IT': 'Italian',
> + 'ja_JP': 'Japanese',
> + 'ko_KR': 'Korean',
> + 'sp_SP': 'Spanish',
> + 'zh_TW': 'Taiwanese',
> +}
I went with my naive understanding of the language codes without double
checking but I think these might be better names:
'zh_CN': 'Chinese (simplified)'
'zh_TW': 'Chinese (traditional)',
Thoughts?
Vegard
next prev parent reply other threads:[~2023-10-28 18:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 16:29 [PATCH] docs: translations: add translations links when they exist Vegard Nossum
2023-10-28 18:51 ` Vegard Nossum [this message]
2023-11-03 2:00 ` Yanteng Si
2023-10-30 11:30 ` Federico Vaga
2023-10-30 17:11 ` Jani Nikula
2023-11-01 14:56 ` Akira Yokosawa
2023-11-02 11:07 ` Vegard Nossum
2023-11-03 0:09 ` Akira Yokosawa
2023-11-17 20:54 ` Jonathan Corbet
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=bc41e32e-e899-427c-9aea-eba411e5bcef@oracle.com \
--to=vegard.nossum@oracle.com \
--cc=akiyks@gmail.com \
--cc=alexs@kernel.org \
--cc=carlos.bilbao@amd.com \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siyanteng@loongson.cn \
--cc=src.res.211@gmail.com \
/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