From: Andreas Schwab <schwab@linux-m68k.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: "Štěpán Němec" <stepnem@gmail.com>, emacs-devel@gnu.org
Subject: Re: emacs-28 2c6a94c5b8: ; Correct the meaning of "cf." in tips.texi
Date: Fri, 29 Jul 2022 11:29:38 +0200 [thread overview]
Message-ID: <87sfmk8dx9.fsf@igel.home> (raw)
In-Reply-To: <CADwFkmmtaYYspemBv_WqP9FoM2uCtThFW+bLuLNP_mMkQyu-0w@mail.gmail.com> (Stefan Kangas's message of "Fri, 29 Jul 2022 01:49:13 -0700")
On Jul 29 2022, Stefan Kangas wrote:
> - In Bug#40011, I quote Writing for Computer Science by Justin Zobel
> (2004), which says:
>
> "It is often tempting to use abbreviations such as 'no.', 'i.e.',
> 'e.g.' 'c.f.' and 'w.r.t.' These save little space on the page,
> but slow readers down. It is almost always desirable to expand
> these abbreviations, to 'number', 'that is', 'for example',
> 'compared with' (or more accurately 'in contrast to', since that
> is the sense in which 'c.f.' should be used), and 'with respect
> to', or synonyms of these expressions.
The wiktionary refers to
https://dictionary.cambridge.org/us/dictionary/english/cf, which prefers
`cf.' over `c.f.', and uses the meaning `compare with'.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-07-29 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165908066777.10020.10943301720600410977@vcs2.savannah.gnu.org>
[not found] ` <20220729074428.12D06C00095@vcs2.savannah.gnu.org>
2022-07-29 8:49 ` emacs-28 2c6a94c5b8: ; Correct the meaning of "cf." in tips.texi Stefan Kangas
2022-07-29 9:13 ` Štěpán Němec
2022-07-29 9:50 ` Stefan Kangas
2022-07-29 9:29 ` Andreas Schwab [this message]
2022-07-29 10:04 ` Gregory Heytings
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=87sfmk8dx9.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@gmail.com \
--cc=stepnem@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).