From: Stefan Kangas <stefankangas@gmail.com>
To: "Š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 01:49:13 -0700 [thread overview]
Message-ID: <CADwFkmmtaYYspemBv_WqP9FoM2uCtThFW+bLuLNP_mMkQyu-0w@mail.gmail.com> (raw)
In-Reply-To: <20220729074428.12D06C00095@vcs2.savannah.gnu.org>
Štěpán Němec <stepnem@gmail.com> writes:
> ; Correct the meaning of "cf." in tips.texi
>
> Cf. e.g. https://en.wiktionary.org/wiki/cf.
>
> * doc/lispref/tips.texi (Documentation Tips): Correct the meaning of
> "cf.".
> ---
> doc/lispref/tips.texi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi
> index a3f49c19bc..eddbbfe8b9 100644
> --- a/doc/lispref/tips.texi
> +++ b/doc/lispref/tips.texi
> @@ -845,7 +845,7 @@ find an alternate phrasing that conveys the meaning.
> @item
> Try to avoid using abbreviations such as ``e.g.'' (for ``for
> example''), ``i.e.'' (for ``that is''), ``no.'' (for ``number''),
> -``cf.'' (for ``in contrast to'') and ``w.r.t.'' (for ``with respect
> +``cf.'' (for ``compare''/``see also'') and ``w.r.t.'' (for ``with respect
> to'') as much as possible. It is almost always clearer and easier to
> read the expanded version.@footnote{We do use these occasionally, but
> try not to overdo it.}
I'm not sure about this change:
- I don't think "see also" is correct.
- 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.
next parent reply other threads:[~2022-07-29 8:49 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 ` Stefan Kangas [this message]
2022-07-29 9:13 ` emacs-28 2c6a94c5b8: ; Correct the meaning of "cf." in tips.texi Štěpán Němec
2022-07-29 9:50 ` Stefan Kangas
2022-07-29 9:29 ` Andreas Schwab
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmmtaYYspemBv_WqP9FoM2uCtThFW+bLuLNP_mMkQyu-0w@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=emacs-devel@gnu.org \
--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 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.