This will hopefully avoid questions over which spelling and grammar should
be used. Translators are of course free to create localizations for other
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.
Documentation/CodingGuidelines | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
index 559d5f9..43af82e 100644
@@ -242,6 +242,9 @@ Writing Documentation:
processed into HTML and manpages (e.g. git.html and git.1 in the
+ 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
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