unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org,  rpluim@gmail.com,  emacs-devel@gnu.org
Subject: Re: emacs-28 b7d7c2d9e9: Add cross-reference to alternative syntaxes for Unicode
Date: Sat, 22 Oct 2022 15:43:45 +0800	[thread overview]
Message-ID: <87bkq45mmm.fsf@yahoo.com> (raw)
In-Reply-To: <83ilkcv0qm.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 22 Oct 2022 09:19:45 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> 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, even living in a country where the average level of proficiency in
English is very low, I find that most people are able to understand
abbreviations such as "i.e." and "e.g."; they are taught in the
education system and are in fact used quite often on the internet.

So I don't see why using any of those abbreviations (which may as well
be called colloquialisms) would be a problem.



  reply	other threads:[~2022-10-22  7:43 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 [this message]
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             ` [External] : " Drew Adams
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=87bkq45mmm.fsf@yahoo.com \
    --to=luangruo@yahoo.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).