all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juanma Barranquero'" <lekktu@gmail.com>,
	<1476@emacsbugs.donarmstrong.com>
Cc: 'Lawrence Mitchell' <wence@gmx.li>,
	bug-gnu-emacs@gnu.org, emacs-pretest-bug@gnu.org
Subject: bug#1476: 23.0.60; spelling of (un)writeable should be (un)writable
Date: Wed, 3 Dec 2008 07:03:07 -0800	[thread overview]
Message-ID: <007a01c95558$417a31e0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <f7ccd24b0812030608m4fc07e60w4851d30d28bbc5dc@mail.gmail.com>

> > It's about general usage, in practice. Whether "both are 
> > fine" is really beside the point.
> 
> Googling for "writable -writeable" gets about 2,6 Mhits, while
> "writeable -writable" gets around 0,9 Mhits. Fewer, but still sizable.

Yes, and googling for "labour -labor" gets 56.4 million, versus 173 million for
"labor -labour". Only about three to one.

But Emacs has standardized on American spelling. American usage generally drops
a final "e" when adding suffix "able".

Here is a bit from the Cambridge Guide to Australian English Usage:

-eable  This ending is really a composite of the final e of a root word and the
-able suffix. It is a matter of necessity for some words, and of choice for
others. It is the necessary ending for words such as changeable and traceable,
because -eable serves to preserve the "j" or "s" sounnd in them (see -ce/-ge).
But for others such as lik(e)able, liv(e)able, siz(e)able and us(e)able, it's
possible to use either -eable or just -able. Broadly speaking, the Oxford
Dictionary tradition maintains the first spelling (except for usable), while
American English (Webster's 1986) is squarely behind the second. It is more in
line with the major rule over dropping fine e (see e)...

For more of the quote:
http://books.google.com/books?id=nV8h0gnU1UEC&pg=RA1-PA237&lpg=RA1-PA237&dq=suff
ix+eable+able+spelling&source=web&ots=ztUmc45nwi&sig=YnjusFpRwdJo9_eQm8aCPrlBheo
&hl=en&sa=X&oi=book_result&resnum=9&ct=result

> I don't think anyone has trouble understanding "writeable".

No, of course not. That's not the point.







  reply	other threads:[~2008-12-03 15:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <878wqykkb2.fsf@cyd.mit.edu>
2008-12-02 23:02 ` bug#1476: 23.0.60; spelling of (un)writeable should be (un)writable Drew Adams
2008-12-02 23:48   ` Stephen Berman
2008-12-03  3:35   ` bug#1476: marked as done (23.0.60; spelling of (un)writeable should be (un)writable) Emacs bug Tracking System
2008-12-03 11:03   ` bug#1476: 23.0.60; spelling of (un)writeable should be (un)writable Lawrence Mitchell
2008-12-03 13:43     ` Drew Adams
2008-12-03 14:00       ` Lawrence Mitchell
2008-12-03 15:00         ` bug#1476: 23.0.60; spelling of (un)writeable should be(un)writable Drew Adams
2008-12-03 14:08       ` bug#1476: 23.0.60; spelling of (un)writeable should be (un)writable Juanma Barranquero
2008-12-03 15:03         ` Drew Adams [this message]
2008-12-03 15:06           ` Juanma Barranquero
2008-12-03 15:25             ` Drew Adams
2008-12-03 14:13       ` Jason Rumney
2008-12-03 15:09         ` Drew Adams
2008-12-03 21:46     ` Stefan Monnier

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='007a01c95558$417a31e0$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=1476@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=wence@gmx.li \
    /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.