unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, "rms@gnu.org" <rms@gnu.org>
Cc: "rpluim@gmail.com" <rpluim@gmail.com>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: emacs-28 b7d7c2d9e9: Add cross-reference to alternative syntaxes for Unicode
Date: Sat, 22 Oct 2022 17:22:01 +0000	[thread overview]
Message-ID: <SJ0PR10MB548838F2A0B56947A156F0F1F32C9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83ilkcv0qm.fsf@gnu.org>

> > From: Richard Stallman 
> > We try to avoid the Latin abbreviations (such as "e.g.") that used to
> > be customary in erudite writing.  Many readers don't know them.
> > It is better to say "such as" instead.
> 
> We use "such as" and "like" and "for example" and others, but we also
> use "e.g.".  I find nothing wrong with that; technical literature out
> there is full of those, and people who use and develop software should
> be familiar with this abbreviation.  (And if they aren't, there's
> always Wikipedia, and our Glossary also explains it.)  That is part of
> everyone's education, if you will.
> 
> I'm sorry, but I refuse to give in to such "winds of change".  Where
> it feels natural to say "e.g.", we will not avoid saying that just
> because someone might need to go look it up.  Of course, we shouldn't
> use it too much: for example, using more than one in places too close
> to one another should be definitely avoided.

FWIW, I agree with Eli here (and Po Lu).

Pretty much everyone who understands most of the
common words used in our doc understands "e.g."
(and "etc."). That's not a reason to overuse such
abbreviations.  It's a reason not to overly avoid
their use.
___

It's more important to be sure to use "such as"
and "like" correctly than it is to avoid "e.g.".

Unfortunately, readers won't necessarily get the
difference.  "such as X" includes X.  "like X"
doesn't necessarily include X - and X need not
even be an includable value - it could be a
pattern/exemplar that describes possible values.
___

On the other hand, there are plenty of people who
confuse "i.e.", thinking it means the same as
"e.g.".  I, for one, avoid using "i.e.", in favor
of "that is".



  parent reply	other threads:[~2022-10-22 17:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 15:56 emacs-28 b7d7c2d9e9: Add cross-reference to alternative syntaxes for Unicode Eli Zaretskii
2022-10-14 16:17 ` Robert Pluim
2022-10-14 17:42   ` Eli Zaretskii
2022-10-18 15:05     ` Robert Pluim
2022-10-18 15:18       ` Eli Zaretskii
2022-10-18 15:58         ` Eli Zaretskii
2022-10-18 16:06           ` Robert Pluim
2022-10-21 19:42         ` Richard Stallman
2022-10-22  6:19           ` Eli Zaretskii
2022-10-22  7:43             ` Po Lu
2022-10-22 20:05               ` Richard Stallman
2022-10-24  4:40                 ` Christopher Dimech
2022-10-24 13:06                   ` Eli Zaretskii
2022-10-22 17:22             ` Drew Adams [this message]
2022-10-24  3:05               ` RE: [External] : " Christopher Dimech
2022-10-22 20:06             ` Richard Stallman
2022-10-23  5:15               ` Eli Zaretskii
2022-10-24 19:31                 ` Richard Stallman
2022-10-24 19:44                   ` Eli Zaretskii
2022-10-24 19:57                   ` Christopher Dimech

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=SJ0PR10MB548838F2A0B56947A156F0F1F32C9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=rpluim@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).