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

From: Marc Branchaud <marcnarc@xiplink.com>
Date: Jul 30, 2013, 15:11 UTC
Message-ID: <1375197114-10742-1-git-send-email-marcnarc@xiplink.com>
In-Reply-To: <51F7D2FA.7020208@xiplink.com>

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.

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