From: Junio C Hamano <gitster@pobox.com>
To: Marc Branchaud <marcnarc@xiplink.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Specify UK English for the documentation source files.
Date: Tue, 30 Jul 2013 09:40:57 -0700 [thread overview]
Message-ID: <7vppu0vw4m.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1375197114-10742-1-git-send-email-marcnarc@xiplink.com> (Marc Branchaud's message of "Tue, 30 Jul 2013 11:11:54 -0400")
Marc Branchaud <marcnarc@xiplink.com> writes:
> This will hopefully avoid questions over which spelling and grammar should
> be used. Translators are of course free to create localizations for other
> English dialects.
>
> Signed-off-by: Marc Branchaud <marcnarc@xiplink.com>
> ---
>
> Although I'm Canadian I figured en_CA would be a little too parochial. I
> don't have a strong preference for en_UK over en_US though.
If we were to specify one, I would have to say we should standardise
on en_US. Like it or not, that is the lingua franca in the CS world
(I'd also admit that most of the extra 'u' in words like "behaviour"
are my typoes, not even coming from a conscious decision to choose
en_UK).
I'd appreciate "typofix" patches to address genuine typoes like
"s/filesytem/filesystem/" done separately, so that we do not even
have to get into language bikeshedding. Even if we did decide to
stick to en_US, the typofix patches and en_US patches should be
separate to ease reviews.
next prev parent reply other threads:[~2013-07-30 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 21:15 [PATCH] Documentation: fix typos in man pages Øystein Walle
2013-07-30 14:51 ` Marc Branchaud
2013-07-30 15:05 ` Junio C Hamano
2013-07-30 15:11 ` [PATCH] Specify UK English for the documentation source files Marc Branchaud
2013-07-30 15:52 ` Fredrik Gustafsson
2013-07-30 16:40 ` Junio C Hamano [this message]
2013-08-01 15:10 ` [PATCH v2] Provide some linguistic guidance for the documentation Marc Branchaud
2013-08-01 15:14 ` Marc Branchaud
2013-08-01 18:21 ` Junio C Hamano
2013-08-01 18:49 ` [PATCH v3] " Marc Branchaud
2013-08-02 6:25 ` [PATCH v2] " Jonathan Nieder
2013-08-02 14:16 ` Marc Branchaud
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vppu0vw4m.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=marcnarc@xiplink.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).