all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Williams <jrw@pobox.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: 28790@debbugs.gnu.org
Subject: bug#28790: [PATCH] Replaced "which see" with "q.v.".
Date: Sat, 14 Oct 2017 18:03:31 -0700	[thread overview]
Message-ID: <CAEdRJLD+hakeVty7hW=nGBwkGkGF+zxL9WqbUerN1NGjG+p=Vg@mail.gmail.com> (raw)
In-Reply-To: <87po9pi7p4.fsf@gmail.com>

To replace "which see" with something more conventional, I think you'd
have to re-word the whole sentence in most cases. So like, "See also
cromulate-frobnicator, which is called by snarf-spavicle in GUI
environments", as opposed to something like "In GUI environments,
snarf-spavicle calls cromulate-frobnicator, which see." At the moment
I can't think of any any natural-sounding way to introduce a cross
reference in English prose that isn't some type of imperative verb
phrase.

Tangent: "which see" fails to parse for me because it sounds like
"cromulate-frobnicator" is supposed to be the subject of "see" rather
than the object. The only time I'd expect to see "which see" would be
as a modifier to a noun phrase like "the cameras, which see everything
that happens". I suspect you could get away with something like "quod
vide" because Latin is a lot more flexible about word order, and
English-speaking authors just blindly copied the Latin phrase without
accounting for the rather large grammatical differences between
English and Latin. It wouldn't be the first time English-speaking
academics tried to apply Latin rules to English grammar in a totally
silly way, like when they invented the concept of a split infinitive,
or when they started insisting you can't end a sentence with a
preposition.

I still maintain that "which see" is an anachronism that the vast
majority of English speakers will find meaningless at best, and
confusing at worst, but since RMS already said he disagrees, I don't
see much point in pressing the issue further without collecting some
hard data on English usage, and that seems like it would be an
excessively quixotic pursuit.

On Sat, Oct 14, 2017 at 5:19 PM, João Távora <joaotavora@gmail.com> wrote:
> Glenn Morris <rgm@gnu.org> writes:
>
>> Eli Zaretskii wrote:
>>
>>> The absolute majority of your proposed changes are in the doc strings,
>>> where we already have a direct link to the documentation of a symbol
>>> whose name precedes "which see".  So whether the reader understands
>>> that or doesn't, the link is already there to click on, and no harm is
>>> done by a relatively rare use of this phrase.
>>
>> IMO there is no benefit either, as you explain above. "which see" is an
>> anachronism in the age of hyperlinks.
>
> For me, it has the benefit that it allows me emphasize that the
> hyperlink preceding is more important than usual, almost a pre-requisite
> for understanding the current one.  I use "which see" because it's terse
> and a conventional phrase. Until this discussion I thought it was a
> widely accepted convention, even outside Emacs, I now understand that it
> is not, but if you "forbid it" I have to start writing things like "(the
> documentation of which is required/suggested to fully understand this
> item)" which says the same but is a bit long-winded.
>
> João





  reply	other threads:[~2017-10-15  1:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 21:22 bug#28790: [PATCH] Replaced "which see" with "q.v." John Williams
2017-10-12  1:44 ` Nick Helm
2017-10-12  3:51   ` Drew Adams
2017-10-12  6:48 ` Eli Zaretskii
2017-10-14 22:07   ` Glenn Morris
2017-10-14 22:52     ` John Williams
2017-10-15  2:36       ` Eli Zaretskii
2017-10-15  0:19     ` João Távora
2017-10-15  1:03       ` John Williams [this message]
2017-10-15 15:31         ` Drew Adams
2017-10-16  1:55           ` Richard Stallman
2017-10-16 21:47         ` Alan Third
2017-10-15  2:36     ` Eli Zaretskii
2017-10-13  0:26 ` bug#28790: " Richard Stallman
2017-10-13 18:34   ` John Williams
2017-10-13 18:55     ` Eli Zaretskii
2019-06-24 15:39   ` Lars Ingebrigtsen

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='CAEdRJLD+hakeVty7hW=nGBwkGkGF+zxL9WqbUerN1NGjG+p=Vg@mail.gmail.com' \
    --to=jrw@pobox.com \
    --cc=28790@debbugs.gnu.org \
    --cc=joaotavora@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.