[PATCH] Specify UK English for the documentation source files.

2013-07-30 Thread Marc Branchaud
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 marcn...@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.

On 13-07-30 11:05 AM, Junio C Hamano wrote: 
 I'd rather not to see any change that turns one accepted form into
 another accepted form at all (like parseable vs parsable in this
 patch).  For that purpose, asking What is parseable to Google and
 seeing if there is a hit is good enough ;-)

I think choosing a dialect for git will help mitigate such changes.  But
perhaps it's a bit too draconian.

M.


 Documentation/CodingGuidelines | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
index 559d5f9..43af82e 100644
--- a/Documentation/CodingGuidelines
+++ b/Documentation/CodingGuidelines
@@ -242,6 +242,9 @@ Writing Documentation:
  processed into HTML and manpages (e.g. git.html and git.1 in the
  same directory).
 
+ The human lanuage of the documentation source files is UK English (en_UK).
+ Please follow UK English norms for spelling and grammar.
+
  Every user-visible change should be reflected in the documentation.
  The same general rule as for code applies -- imitate the existing
  conventions.  A few commented examples follow to provide reference
-- 
1.8.3.1

--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH] Specify UK English for the documentation source files.

2013-07-30 Thread Fredrik Gustafsson
On Tue, Jul 30, 2013 at 11:11:54AM -0400, Marc Branchaud wrote:
 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 marcn...@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.
 

Since the settings (for example color) use en_US, I suggest _not_ to
specify en_UK as documentation language. Either set en_US or rather
don't set anything at all but go after google correct. That's the most
populair alternative. For example colour gets 422 000 000 hits and color
gets 2 260 000 000 hits. We should use color even if it's not en_UK.

It's a more pragmatic approach and most git users aren't native english
speakers anyway.

-- 
Med vänliga hälsningar
Fredrik Gustafsson

tel: 0733-608274
e-post: iv...@iveqy.com
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [PATCH] Specify UK English for the documentation source files.

2013-07-30 Thread Junio C Hamano
Marc Branchaud marcn...@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 marcn...@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.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html