unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: 20011@debbugs.gnu.org
Subject: bug#20011: etc/PROBLEMS: updates, wording, typos
Date: Sat, 04 Apr 2015 20:25:07 +0000	[thread overview]
Message-ID: <87bnj3tzdo.fsf@violet.siamics.net> (raw)
In-Reply-To: <dra8zqxdtt.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 06 Mar 2015 11:58:38 -0500")

>>>>> Glenn Morris <rgm@gnu.org> writes:
>>>>> Ivan Shmakov wrote:

 >> AIUI, there's nothing wrong with using “which” there, either.

 > I disagree.  Eg
 > http://blog.apastyle.org/apastyle/2012/01/that-versus-which.html

	There, it documents the in-house style.  As for the English at
	large, Wikipedia quotes [1] Merriam-Webster’s (1995) thus:

    […] the facts of usage are quite simple.  Virginia McDavid’s 1977
    study shows that about 75 percent of the instances of /which/ in
    edited prose introduce restrictive clauses; about 25 percent
    nonrestrictive ones.  We conclude that at the end of the 20th
    century, the usage of /which/ and /that/ — at least in prose — has
    settled down.  You can use either /which/ or /that/ to introduce a
    restrictive clause — the grounds for your choice should be stylistic
    — and /which/ to introduce a nonrestrictive clause.

[1] https://en.wikipedia.org/wiki/English_relative_clauses

-- 
FSF associate member #7257  http://boycottsystemd.org/  … 3013 B6A0 230E 334A





  reply	other threads:[~2015-04-04 20:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 21:49 bug#20011: etc/PROBLEMS: updates, wording, typos Ivan Shmakov
2015-03-06  8:43 ` Eli Zaretskii
2015-03-06  9:10   ` Ivan Shmakov
2015-03-06 10:23     ` Eli Zaretskii
2015-04-04 20:20       ` Ivan Shmakov
2015-04-04 21:23         ` Eli Zaretskii
2015-04-07 17:47           ` Ivan Shmakov
2015-03-06 16:58     ` Glenn Morris
2015-04-04 20:25       ` Ivan Shmakov [this message]
2015-04-05  9:10         ` 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=87bnj3tzdo.fsf@violet.siamics.net \
    --to=ivan@siamics.net \
    --cc=20011@debbugs.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.
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).