public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: dewar@gnat.com (Robert Dewar)
To: J.A.K.Mouw@its.tudelft.nl, tommy@mensa.se
Cc: gcc@gnu.org
Subject: Re: Typo.
Date: Sat, 02 Feb 2002 14:42:00 -0000	[thread overview]
Message-ID: <20020202224243.65A1EF28AD@nile.gnat.com> (raw)

>>"optimised" is the correct British English spelling.

This is a common misconception, but it is that, a misconception. While the
's' spellings are definitely standard in Australia, in England there is
still considerably unclarity on this issue. In particular, the OED second
edition lists ONLY the 'z' spelling and does not even recognize the
possibility of the 's' spelling (optimise) as an acceptable alternative.

It is indeed the case that many educated british writers use the 's' spelling
and for example the Economist usually seems to prefer the 's' spelling (a
fact implicitly recognized in the OED, since there is a quote from the
Economist with the 's' spelling).

So it is a bit over-reaching to say that optimise is wrong, whatever the
OED says, but to declare that "optimise" is *the* correct British English
spelling is also definitely over-reaching.

The bottom line is that you should always use the 'z' spelling for all
these words all the time, and you are then not wrong in either American
or British usage.

This is of course off-topic, but since documentation styles and rules are
at least remotely connected, it is useful for people to know this. I often
find that non-british writers are the most adamant in making the above
claim (sort of like the French being adamant in stating that upper case
letters do not have accents in French).

             reply	other threads:[~2002-02-02 22:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-02 14:42 Robert Dewar [this message]
2002-02-02 15:23 ` Typo Erik Mouw
2002-02-02 18:45 ` Typo John Levon
  -- strict thread matches above, loose matches on Subject: below --
2002-02-02 15:24 Typo Robert Dewar
2002-02-02 15:35 ` Typo Kevin Handy
2002-01-31 15:30 Typo Tommy Dugandzic
2002-02-02 18:23 ` Typo Tom Tromey
2002-01-31 15:26 Typo Tommy Dugandzic
2002-02-02 13:24 ` Typo Erik Mouw
2002-02-02 15:57   ` Typo Alexandre Oliva
2002-02-02 18:22 ` Typo Tom Tromey
2002-02-02 18:48   ` Typo Craig Rodrigues
2002-02-02 18:55     ` Typo Tom Tromey

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=20020202224243.65A1EF28AD@nile.gnat.com \
    --to=dewar@gnat.com \
    --cc=J.A.K.Mouw@its.tudelft.nl \
    --cc=gcc@gnu.org \
    --cc=tommy@mensa.se \
    /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).