From: Joe Buck <jbuck@synopsys.COM>
To: dalej@apple.com (Dale Johannesen)
Cc: gcc@gcc.gnu.org
Subject: Re: spelling
Date: Tue, 09 Oct 2001 19:00:00 -0000 [thread overview]
Message-ID: <200110100159.SAA26637@atrus.synopsys.com> (raw)
In-Reply-To: <F0EDAE27-BD11-11D5-8895-003065C86F94@apple.com>
> As long as we [i.e. Joseph Myers] are fixing this, do we want to establish
> consistent spellings for "initializ/se" and "optimiz/se"? Both variants
> occur in the sources. There are probably others. (I know, this is a case
> for i18n, but it's not there.)
These things have a way of turning into petty wars. But if we must
choose: Since the original gcc manual is by RMS, it seems reasonable
follow the style he established and therefore choose the American
spellings: -ize not -ise, -or not -our etc.
(Ideally in cases where the UK and US spellings differ for a command line
switch, the compiler would accept both to minimize user frustration).
next prev parent reply other threads:[~2001-10-09 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 17:01 spelling Dale Johannesen
2001-10-09 19:00 ` Joe Buck [this message]
2001-10-10 2:37 ` spelling Florian Weimer
2001-10-09 23:55 spelling dewar
2001-10-10 5:21 ` spelling Joseph S. Myers
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=200110100159.SAA26637@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=dalej@apple.com \
--cc=gcc@gcc.gnu.org \
/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.
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).