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:15 -0700 (PDT) [thread overview]
Message-ID: <9777edf8-a4b4-467f-9fd2-ee853877d389@default> (raw)
In-Reply-To: <<831tdz8yf8.fsf@gnu.org>>
> If this means that we should avoid quoting text just because
> Drew doesn't like a certain type of quotes, then I object.
I made it perfectly clear that this bug report has nothing
to do with my preference or lack thereof for any particular
kind of quoting.
For example:
This is *not* a general problem. It is not about the use of
^^^^^^^^^^^^^^^^^^^^^^^
curly double-quotes in, for example, the copyright statement
(e.g., "You have the freedom to copy and modify this GNU manual.
Buying copies from the FSF supports it in developing GNU and
promoting software freedom.").
...
The point of this bug is that those *particular* terms do
^^^^^^^^^^^^^^^^^^^^^^^^
not belong between curly double-quotes (IMHO). If they were
ordinary text being quoted then they would be (should be)
capitalized - "unix", "dos", etc. are written incorrectly
for such a usage.
This bug is not about other curly double-quoted text in the
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
manual. It is specific to these terms.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
and in another message:
Quoted text might end up with curly quotes. The question is
why these words should be quoted (using ordinary text quotes),
^^^^^^^^^^^^^^^
and if they should (no reason given so far) then why they
should be lowercase.
Yet you continue with your Drew-bashing, based on your spurious
claim. Why?
Why is quoting appropriate for _this particular text_ at all?
That's the first question posed, in effect, by the bug report.
You could have answered Paul's removal of the quotes by giving
a _reason why_ they are needed _here_, but you chose only to
dump on Drew for reporting the oddball use of quoting here.
Too bad. What a cop-out - attack the messenger.
What kind of quotes do you think are appropriate for "unix",
"dos", and "mac", none of which are proper names as lowercase?
And why?
What is the point of downcasing and then quoting them? That's
what the question underlying this bug report.
No answer, so far.
next prev 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
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 [this message]
[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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9777edf8-a4b4-467f-9fd2-ee853877d389@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.