mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Carlos Bilbao <carlos.bilbao@amd.com>,
	bilbao@vt.edu, corbet@lwn.net, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, miguel.ojeda.sandonis@gmail.com
Subject: Re: [PATCH v2 1/2] Documentation: Start translations to Spanish
Date: Mon, 17 Oct 2022 15:41:22 +0100	[thread overview]
Message-ID: <Y01pkubcT7FOwCjL@casper.infradead.org> (raw)
In-Reply-To: <48b4a5a1-2a52-4159-699b-9db73a012892@gmail.com>

On Sat, Oct 15, 2022 at 01:06:36PM +0900, Akira Yokosawa wrote:
> Hi,
> Minor nit on language code.
> 
> On Fri, 14 Oct 2022 09:24:53 -0500, Carlos Bilbao wrote:
> > Start the process of translating kernel documentation to Spanish. Create
> > sp_SP/ and include an index and a disclaimer, following the approach of
> > prior translations. Add Carlos Bilbao as MAINTAINER of this translation
> > effort.
> IIUC, the language code for "Spanish (Spain)" should be "es-ES", as is
> listed at e.g., http://www.lingoes.net/en/translator/langcode.htm.
> 
> The other translations use directory names found in the table, with
> "-" replaced with "_".  It would be better to be consistent.

I don't know what standard we're actually following.  RFC5646 suggests
simply using "es", with "es-419" for Latin America specialisation or
"es-ES" for Spain.  I don't know how much variation there is between
different Spanish dialects for technical documents; as I understand it,
it's worth supporting two dialects of Chinese, but we merrily mix &
match en_US and en_GB spellings.  Similarly, I wouldn't suggest that we
have separate translations for fr_CA, fr_CH, fr_FR, just a single 'fr'
would be fine.

We do need to be careful here; people are rightfully sensitive about
being incorrectly grouped together.  If possible we should find a
standard to follow that's been defined by experts in these matters.
https://en.wikipedia.org/wiki/IETF_language_tag may be a good place to
start looking.

  reply	other threads:[~2022-10-17 14:41 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 ` [PATCH 0/2] Documentation: Start Spanish translation and include HOWTO Jonathan Corbet
2022-10-14 13:01   ` 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 [this message]
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=Y01pkubcT7FOwCjL@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akiyks@gmail.com \
    --cc=bilbao@vt.edu \
    --cc=carlos.bilbao@amd.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@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

all inboxes | Powered by JetHome®