From: Nick Roberts <nickrob@snap.net.nz>
Cc: miles@gnu.org, Alan Mackenzie <acm@muc.de>,
snogglethorpe@gmail.com, emacs-devel@gnu.org
Subject: Re: English usage bug in bytecomp.el
Date: Wed, 9 Mar 2005 00:45:43 +1300 [thread overview]
Message-ID: <16941.36967.646660.525697@farnswood.snap.net.nz> (raw)
In-Reply-To: <x5zmxeqvu9.fsf@lola.goethe.zz>
> >
> > I don't know if it's correct or not but I think it is effective use of
> > English.
>
> "efficient" you mean probably . Let us just replace every "is not"
> and "was not" and "has not" with "ain't". That is also efficient.
This is a bit surreal! No, I mean effective as in "it conveys the meaning"
which is what language is intended for, although it might not impress
professors of English. If I had meant efficient, I would have said so. What
is efficient English anyway? Using the minimum number of words/letters?
> > I think its important to remember that English may not be the first
> > language for many Emacs users. "`foo' is an obsolete function since
> > 21.4" is concise: it tells the user that foo *is* obsolete and then
> > that it became obsolete in version 21.4. He doesn't have to
> > understand the many forms of past tense that English can have.
>
> We are not talking about whether it is impossible to make sense out of
> what is written. But I don't see how the non-first language speaker
> actively gains anything if we switch to a bastardized version of
> English. We don't require the readers of the manual to write correct
> English themselves, we just strive to be understandable even for
> non-native speakers. But I don't see that the correct English usage
> here would have any detrimental effects.
If I remember correctly, "has been an obsolete function" is the perfect tense,
and suggests a completed action i.e it has been obsolete but what is its
status now. It has some ambiguity.
Anyway, lets not delude ourselves, the international language is American
English, perhaps it also sounds natural on that side of the Atlantic.
Nick.
next prev parent reply other threads:[~2005-03-08 11:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 20:17 English usage bug in bytecomp.el Alan Mackenzie
2005-03-07 23:09 ` Miles Bader
2005-03-08 8:02 ` Alan Mackenzie
2005-03-08 8:49 ` Nick Roberts
2005-03-08 10:24 ` David Kastrup
2005-03-08 11:45 ` Nick Roberts [this message]
2005-03-08 9:57 ` Miles Bader
2005-03-08 10:33 ` David Kastrup
2005-03-08 15:37 ` John S. Yates, Jr.
2005-03-08 16:08 ` Bill Wohler
2005-03-08 17:26 ` Andreas Schwab
2005-03-08 21:10 ` Nick Roberts
2005-03-08 22:15 ` Miles Bader
2005-03-08 22:36 ` Bill Wohler
2005-03-09 16:59 ` Richard Stallman
2005-03-09 3:12 ` Richard Stallman
2005-03-09 9:49 ` David Kastrup
2005-03-09 10:22 ` Miles Bader
2005-03-08 13:08 ` Stefan Monnier
2005-03-09 3:12 ` Richard Stallman
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=16941.36967.646660.525697@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=snogglethorpe@gmail.com \
/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.