From: Paul Eggert <eggert@cs.ucla.edu>
To: Phil Sainty <psainty@orcon.net.nz>, emacs-devel@gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Documenting a preference for US English?
Date: Thu, 12 Oct 2017 22:48:41 -0700 [thread overview]
Message-ID: <103499a2-6ec8-05f2-9a56-e63e2d1b58bc@cs.ucla.edu> (raw)
In-Reply-To: <a633d011e2315d91860c98541a7cb51b@webmail.orcon.net.nz>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
Phil Sainty wrote:
> I had grepped for "english" and then for "american" and "US" within
> those results, and didn't turn up any instructions to this end.
$ grep -ri 'american spell' $(git ls-files)
ChangeLog.2: Rename using American spelling. Update all uses.
doc/lispref/ChangeLog.1: Prefer typical American spelling for "acknowledgment".
doc/misc/ChangeLog.1: Prefer typical American spelling for "acknowledgment".
lisp/ChangeLog.16: Prefer typical American spelling for "acknowledgment".
lisp/ChangeLog.16: Emacs uses American spelling.
lisp/gnus/ChangeLog.3: Use American spelling for 'normalize'
> Is there such a recommendation in the documentation that I missed,
> though? If not, it sounds like it would be a good thing to add
> somewhere.
Sure, why not? I installed the attached.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-CONTRIBUTE-Suggest-American-English.patch --]
[-- Type: text/x-patch; name="0001-CONTRIBUTE-Suggest-American-English.patch", Size: 952 bytes --]
From 53e95d01fd8865204fdedcf30f4629d1d0634129 Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert@cs.ucla.edu>
Date: Thu, 12 Oct 2017 22:38:28 -0700
Subject: [PATCH] * CONTRIBUTE: Suggest American English.
---
CONTRIBUTE | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/CONTRIBUTE b/CONTRIBUTE
index d01ac8b..78a2d51 100644
--- a/CONTRIBUTE
+++ b/CONTRIBUTE
@@ -195,7 +195,8 @@ them right the first time, so here are guidelines for formatting them:
sentences starting with a capital and ending with a period (except
the summary line should not end in a period). See
https://www.gnu.org/prep/standards/html_node/Comments.html
- or run 'info "(standards)Comments"'.
+ or run 'info "(standards)Comments"'. American English is preferred
+ in Emacs.
They are preserved indefinitely, and have a reasonable chance of
being read in the future, so it's better that they have good
--
2.7.4
next prev parent reply other threads:[~2017-10-13 5:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 14:10 bug#24837: 26.0.50; term.el: In char mode, displayed and executed commands can differ Philipp Stephani
2016-10-31 20:46 ` Phil Sainty
2016-11-23 19:44 ` Philipp Stephani
2016-11-23 20:08 ` bug#21609: " Phil Sainty
2016-11-23 20:21 ` Philipp Stephani
2017-09-02 14:14 ` Eli Zaretskii
2017-09-03 2:58 ` Phil Sainty
2017-09-03 3:09 ` bug#21609: " Phil Sainty
2017-09-04 9:55 ` Phil Sainty
2017-09-04 10:10 ` bug#24837: " Phil Sainty
2017-09-04 11:59 ` bug#21609: " Phil Sainty
2017-09-24 10:59 ` Philipp Stephani
2017-09-25 0:48 ` bug#21609: " Phil Sainty
2017-09-25 3:09 ` Phil Sainty
2017-09-29 8:37 ` Eli Zaretskii
2017-10-08 12:39 ` bug#21609: " Phil Sainty
2017-10-09 14:04 ` Phil Sainty
2017-10-09 15:32 ` Eli Zaretskii
2017-10-10 10:16 ` bug#28777: Clarifying the temporary documentation update marks in etc/NEWS Phil Sainty
2017-10-10 12:25 ` Eli Zaretskii
2017-10-10 11:11 ` bug#24837: bug#21609: bug#24837: 26.0.50; term.el: In char mode, displayed and executed commands can differ Phil Sainty
2017-10-10 12:35 ` Eli Zaretskii
2017-10-12 10:54 ` Phil Sainty
2017-10-12 12:04 ` bug#21609: " Eli Zaretskii
2017-10-12 21:24 ` Documenting a preference for US English? Phil Sainty
2017-10-13 5:11 ` Marcin Borkowski
2017-10-13 5:48 ` Paul Eggert [this message]
2017-10-13 6:29 ` Thien-Thi Nguyen
2017-10-13 8:35 ` Eli Zaretskii
2017-10-21 8:20 ` bug#24837: bug#21609: bug#24837: 26.0.50; term.el: In char mode, displayed and executed commands can differ Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=103499a2-6ec8-05f2-9a56-e63e2d1b58bc@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=psainty@orcon.net.nz \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.