unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, 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: Tue, 15 Sep 2015 16:48:20 -0700 (PDT)	[thread overview]
Message-ID: <0cbdd1c7-cc2c-4684-bc1e-fec7db72cf45@default> (raw)
In-Reply-To: <83y4g77io1.fsf@gnu.org>

> > Although the manual was correct as it was, it could be written to avoid
> > the need for the quotes, and this should help avoid confusion like the
> > problem Drew reported.  I went through the Emacs, Elisp, and Elisp
> > intro manuals looking for this sort of problem and fixed the ones that
> > I found in commit ef7dbdf5873bf0a1f3f0e64e5d019e74d5b15b9e.
> 
> After looking through these changes, I must say I don't like too many
> of them.  Phrases like "foo (or “bar”)" now lost their quotes, which
> makes them less correct English-wise, AFAIK.  Even worse, we lost
> quotes in phrases like "foo (a.k.a. “bar”).
...
> Etc., etc. -- I think a large portion of these changes goes too far,
> and replaces perfectly correct English with less correct one.
> 
> I think most of these changes should be reverted.

To be clear, and to _repeat_: _THIS_ bug is about the quoting of
_these particular terms_: whether they should be quoted (and why),
and if so, whether (and why) they should be changed to lowercase.

The bug Subject line indicates that I even mistakenly interpreted
these terms as intended to be Lisp strings, so much was it unclear
to me what these quotations are all about.  These are not the
usual terms ("UNIX", "DOS", and "Mac").





  parent reply	other threads:[~2015-09-15 23:48 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 [this message]
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
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=0cbdd1c7-cc2c-4684-bc1e-fec7db72cf45@default \
    --to=drew.adams@oracle.com \
    --cc=21472@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    /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).