From: Florian Weimer <fw@deneb.enyo.de>
To: Dale Johannesen <dalej@apple.com>
Cc: gcc@gcc.gnu.org
Subject: Re: spelling
Date: Wed, 10 Oct 2001 02:37:00 -0000 [thread overview]
Message-ID: <87adyzn7ep.fsf@deneb.enyo.de> (raw)
In-Reply-To: <F0EDAE27-BD11-11D5-8895-003065C86F94@apple.com>
Dale Johannesen <dalej@apple.com> writes:
> 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.)
Fowler suggets that the '-s-' is the consequence of gallofication,
and recommends using the '-ize' variants were possible (usually
if the word is of remote Greek descent). Of course, some kind of
verbing disease exists, and sometimes, '-ize' is used in this context,
although it should be avoided.
next prev parent reply other threads:[~2001-10-10 2:37 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 ` spelling Joe Buck
2001-10-10 2:37 ` Florian Weimer [this message]
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=87adyzn7ep.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--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).