From: Christopher Dimech <dimech@gmx.com>
To: rms@gnu.org
Cc: Po Lu <luangruo@yahoo.com>,
eliz@gnu.org, rpluim@gmail.com, emacs-devel@gnu.org
Subject: Re: emacs-28 b7d7c2d9e9: Add cross-reference to alternative syntaxes for Unicode
Date: Mon, 24 Oct 2022 06:40:35 +0200 [thread overview]
Message-ID: <trinity-d86740f6-e7ab-4a7c-9de6-1f1354bdb851-1666586435232@3c-app-mailcom-bs13> (raw)
In-Reply-To: <E1omKkK-0002DO-4u@fencepost.gnu.org>
> Sent: Sunday, October 23, 2022 at 8:05 AM
> From: "Richard Stallman" <rms@gnu.org>
> To: "Po Lu" <luangruo@yahoo.com>
> Cc: eliz@gnu.org, rpluim@gmail.com, emacs-devel@gnu.org
> Subject: Re: emacs-28 b7d7c2d9e9: Add cross-reference to alternative syntaxes for Unicode
>
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> > 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.
>
> I suspect it varies from country to country.
>
> I would not know where to find the reports I got that people had
> trouble understanding these Latin abbreviations, since it was years
> ago, but I did get them. People who don't recognize "e.g." will
> certainly recognize "for example", so there's no harm in choosing the
> latter.
We could provide a list of abbreviations. Although I am not against the
use of "for example". An alternative to "for example" which is short would
be "as in".
The New York Times also uses e.g. and i.e. Although the Oxford Style Manual
has dropped the use a comma after e.g. and i.e. to avoid double punctuation.
The Guardian, The Economist and The Times of London use eg. and ie. Thusly,
their use is very common actually.
next prev parent reply other threads:[~2022-10-24 4:40 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 [this message]
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=trinity-d86740f6-e7ab-4a7c-9de6-1f1354bdb851-1666586435232@3c-app-mailcom-bs13 \
--to=dimech@gmx.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--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).