From: Marc Branchaud <marcnarc@xiplink.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH] Specify UK English for the documentation source files.
Date: Tue, 30 Jul 2013 11:11:54 -0400 [thread overview]
Message-ID: <1375197114-10742-1-git-send-email-marcnarc@xiplink.com> (raw)
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
next prev parent reply other threads:[~2013-07-30 15:21 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 ` Marc Branchaud [this message]
2013-07-30 15:52 ` [PATCH] Specify UK English for the documentation source files Fredrik Gustafsson
2013-07-30 16:40 ` Junio C Hamano
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=1375197114-10742-1-git-send-email-marcnarc@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).