unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.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 10:04:59 +0000	[thread overview]
Message-ID: <bf6b6a6fd30194432afe@heytings.org> (raw)
In-Reply-To: <CADwFkmmtaYYspemBv_WqP9FoM2uCtThFW+bLuLNP_mMkQyu-0w@mail.gmail.com>


>>  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:
>

The reference on these matters is the CMOS, in which "cf." is defined as 
follows (section 10.43, p. 505): "{\it confer}, compare ("see, by way of 
comparison"; should not be used when {\it see} alone is meant)".



      parent reply	other threads:[~2022-07-29 10:04 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
2022-07-29 10:04     ` Gregory Heytings [this message]

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=bf6b6a6fd30194432afe@heytings.org \
    --to=gregory@heytings.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).