From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47416@debbugs.gnu.org
Subject: bug#47416: Strange sentence in documentation of 'insert-file-contents'
Date: Sat, 27 Mar 2021 07:09:26 +0000 [thread overview]
Message-ID: <b299646274c09c285b7f@heytings.org> (raw)
In-Reply-To: <83a6qpp2aa.fsf@gnu.org>
>> What about replacing "which see" with "quod vide"? It's not longer
>> (eight letters and one space), and is easier to look up than both
>> "which see" and "q.v.".
>
> ISTR that past discussions concluded that q.v. would be even more
> cryptic. With "which see", at least native English speakers and those
> who are used to scientific literature would immediately understand what
> it means.
>
The only thing I see in that discussion (bug#28790) is: ""Quod vide" (qv)
is arguably more conventional, but for those who haven't encountered the
abbreviation or learned its meaning, it's a much tougher nut to crack."
So it's about the abbreviation, not about the expression in full. I just
tried, finding the meaning of "q.v." is difficult, but finding the meaning
of "quod vide" is immediate.
I tried to find recent occurrences of "which see" in Google Books and
Google Scholar, there are none. There are some occurrences of "on which
see <reference>" or "for {examples, a discussion, an overview, an
assessment, ...} of which see <reference>". It seems that all occurrences
of "which see" are from the 19th century.
next prev parent reply other threads:[~2021-03-27 7:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 18:12 bug#47416: Strange sentence in documentation of 'insert-file-contents' Tim Lee
2021-03-26 18:32 ` Philipp
2021-03-26 18:34 ` Gregory Heytings
2021-03-26 18:42 ` Glenn Morris
2021-03-26 19:09 ` Eli Zaretskii
2021-03-26 20:27 ` Gregory Heytings
2021-03-27 5:57 ` Eli Zaretskii
2021-03-27 7:09 ` Gregory Heytings [this message]
2021-03-27 8:05 ` Eli Zaretskii
2021-03-27 18:31 ` 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=b299646274c09c285b7f@heytings.org \
--to=gregory@heytings.org \
--cc=47416@debbugs.gnu.org \
--cc=eliz@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).