From: Jonathan Corbet <corbet@lwn.net>
To: Carlos Bilbao <carlos.bilbao@amd.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
carlos.bilbao@amd.com, bilbao@vt.edu, ojeda@kernel.org
Subject: Re: [PATCH 0/2] Documentation: Start Spanish translation and include HOWTO
Date: Thu, 13 Oct 2022 15:09:59 -0600 [thread overview]
Message-ID: <871qrbig60.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221013184816.354278-1-carlos.bilbao@amd.com>
Carlos Bilbao <carlos.bilbao@amd.com> writes:
> Spanish is the second most spoken language in the world. This patch set
> starts the process of translating critical kernel documentation into the
> Spanish language.
>
> Carlos Bilbao (2):
> Documentation: Start translations to Spanish
> Documentation: Add HOWTO Spanish translation into rst based build system
>
> Documentation/translations/index.rst | 1 +
> .../translations/sp_SP/disclaimer-sp.rst | 6 +
> Documentation/translations/sp_SP/howto.rst | 619 ++++++++++++++++++
> Documentation/translations/sp_SP/index.rst | 80 +++
> 4 files changed, 706 insertions(+)
> create mode 100644 Documentation/translations/sp_SP/disclaimer-sp.rst
> create mode 100644 Documentation/translations/sp_SP/howto.rst
> create mode 100644 Documentation/translations/sp_SP/index.rst
I'm happy to see a Spanish translation of the docs, certainly. I do
worry, though, that the desire to create translations tends to exceed
the desire to keep them maintained and current over time. Is it your
plan to continue to maintain these going forward? Is anybody else
planning to help you with this task?
Along those lines, a MAINTAINERS entry for the Spanish translation would
be a good thing to add.
Thanks,
jon
next prev parent reply other threads:[~2022-10-13 21:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 18:48 [PATCH 0/2] Documentation: Start Spanish translation and include HOWTO Carlos Bilbao
2022-10-13 18:48 ` [PATCH 1/2] Documentation: Start translations to Spanish Carlos Bilbao
2022-10-13 18:48 ` [PATCH 2/2] Documentation: Add HOWTO Spanish translation into rst based build system Carlos Bilbao
2022-10-14 6:16 ` kernel test robot
2022-10-14 9:21 ` Bagas Sanjaya
2022-10-14 12:58 ` Carlos Bilbao
2022-10-14 13:57 ` Jonathan Corbet
2022-10-13 21:09 ` Jonathan Corbet [this message]
2022-10-14 13:01 ` [PATCH 0/2] Documentation: Start Spanish translation and include HOWTO Carlos Bilbao
2022-10-14 14:24 ` [PATCH v2 " Carlos Bilbao
2022-10-14 14:24 ` [PATCH v2 1/2] Documentation: Start translations to Spanish Carlos Bilbao
2022-10-14 15:21 ` Miguel Ojeda
2022-10-14 15:33 ` Carlos Bilbao
2022-10-14 15:36 ` Jonathan Corbet
2022-10-14 15:44 ` Carlos Bilbao
2022-10-14 15:51 ` Miguel Ojeda
2022-10-15 4:06 ` Akira Yokosawa
2022-10-17 14:41 ` Matthew Wilcox
2022-10-18 2:36 ` Akira Yokosawa
2022-10-24 13:40 ` Carlos Bilbao
2022-10-24 15:01 ` Matthew Wilcox
2022-10-24 15:22 ` Jonathan Corbet
2022-10-24 15:31 ` Jonathan Corbet
2022-10-24 15:33 ` Carlos Bilbao
2022-10-25 11:05 ` Alex Shi
2022-10-25 12:53 ` YanTeng Si
2022-10-24 15:19 ` Miguel Ojeda
2022-10-14 14:24 ` [PATCH v2 2/2] Documentation: Add HOWTO Spanish translation into rst based build system Carlos Bilbao
2022-10-15 3:37 ` Bagas Sanjaya
2022-10-15 3:40 ` [PATCH v2 0/2] Documentation: Start Spanish translation and include HOWTO Bagas Sanjaya
2022-10-24 14:53 ` Carlos Bilbao
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=871qrbig60.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.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