From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 21472@debbugs.gnu.org
Subject: bug#21472: 25.0.50; REGRESSION: (emacs) `Coding Systems' uses curly quotes for Lisp strings
Date: Wed, 16 Sep 2015 13:07:51 +0300 [thread overview]
Message-ID: <83mvwm7k3s.fsf@gnu.org> (raw)
In-Reply-To: <55F91EF9.2000302@cs.ucla.edu>
> Cc: 21472-done@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Wed, 16 Sep 2015 00:49:13 -0700
>
> Eli Zaretskii wrote:
> > Shame on us for failing to write good expressive English for fear of
> > quotes.
>
> I didn't remove those quotes due to fear. I removed them because they made the
> manual harder to read. Quotes are important to get right in English, and part
> of getting it right is to avoid overusing them.
The problem is, you removed too many of them.
For example, any use of "magic" where no real magic (as in Gandalf
coming in and performing it) should be quoted, because the literal
meaning is too far-fetched. Likewise in other similar situations,
like with "future history". Likewise when using words that are not
correct English (flagged by spell-checker), such as "fullboth".
I attempted to fix the worst offenders I found in commit 31ff037.
next prev parent reply other threads:[~2015-09-16 10:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 15:45 bug#21472: 25.0.50; REGRESSION: (emacs) `Coding Systems' uses curly quotes for Lisp strings Drew Adams
2015-09-13 20:07 ` Eli Zaretskii
2015-09-13 21:11 ` Drew Adams
2015-09-14 6:24 ` Eli Zaretskii
2015-09-14 14:08 ` Richard Stallman
2015-09-15 15:57 ` Paul Eggert
2015-09-15 16:00 ` Eli Zaretskii
2015-09-15 16:22 ` Paul Eggert
2015-09-15 23:48 ` Drew Adams
2015-09-15 16:26 ` Eli Zaretskii
2015-09-15 19:15 ` Paul Eggert
2015-09-15 23:48 ` Drew Adams
2015-09-16 6:56 ` Eli Zaretskii
2015-09-16 7:32 ` Eli Zaretskii
2015-09-16 7:48 ` Paul Eggert
2015-09-16 10:02 ` Eli Zaretskii
2015-09-15 23:48 ` Drew Adams
2015-09-15 23:48 ` Drew Adams
2015-09-16 7:23 ` Eli Zaretskii
2015-09-16 7:49 ` Paul Eggert
2015-09-16 10:07 ` Eli Zaretskii [this message]
2015-09-16 15:31 ` Paul Eggert
2015-09-16 17:18 ` Eli Zaretskii
2015-09-16 18:27 ` Paul Eggert
2015-09-16 18:34 ` Eli Zaretskii
2015-09-16 20:31 ` Paul Eggert
2015-09-17 4:46 ` Eli Zaretskii
2015-09-17 5:21 ` Paul Eggert
2015-09-17 6:03 ` Eli Zaretskii
2015-09-17 7:21 ` Paul Eggert
2015-09-17 7:35 ` Eli Zaretskii
[not found] ` <<831tdz8yf8.fsf@gnu.org>
2015-09-15 23:48 ` Drew Adams
[not found] <<c7ebc07d-51c9-4d10-9238-d42b0b3845b7@default>
[not found] ` <<83vbbe9j7k.fsf@gnu.org>
[not found] ` <<661f3a80-cdaf-47f0-a096-4be744409150@default>
[not found] ` <<83pp1la58d.fsf@gnu.org>
2015-09-14 13:51 ` Drew Adams
2015-09-15 0:21 ` Richard Stallman
[not found] ` <<55F83FDF.2070202@cs.ucla.edu>
[not found] ` <<3aa1fafa-ed4d-4935-8a3e-cae7d0842c5f@default>
[not found] ` <<83r3ly7rpd.fsf@gnu.org>
2015-09-16 15:16 ` Drew Adams
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=83mvwm7k3s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21472@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).