unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
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: Tue, 08 Mar 2005 11:24:14 +0100	[thread overview]
Message-ID: <x5zmxeqvu9.fsf@lola.goethe.zz> (raw)
In-Reply-To: <16941.26379.290951.460068@farnswood.snap.net.nz> (Nick Roberts's message of "Tue, 8 Mar 2005 21:49:15 +1300")

Nick Roberts <nickrob@snap.net.nz> writes:

>  > [Discussion of "`foo' is an obsolete function since 21.4;"]
>  > 
>  > >> .  This combination of "is" and "since" is incorrect English usage.
>  > 
>  > >I think "is ... since" is pretty common usage actually, and certainly
>  > >makes sense.
>  > 
>  > <Gnashes teeth>
>  > 
>  > Yes, it does make sense and it is regrettably common usage, but it is
>  > WRONG.  It is something that a native English speaker would never say.
>  > In this case, it is just as easy to be correct.
>
> 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.

> 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.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-03-08 10:24 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 [this message]
2005-03-08 11:45         ` Nick Roberts
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=x5zmxeqvu9.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).