From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 21471@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#21471: 25.0.50; bug report with text from Info has spurious escape chars
Date: Mon, 14 Sep 2015 06:41:51 -0700 (PDT) [thread overview]
Message-ID: <1b2518bd-4049-423f-a32e-85d5b3adc3f4@default> (raw)
In-Reply-To: <<83si6ha5dd.fsf@gnu.org>>
> > But Unicode chars were not used all over the place previously,
> > which makes it a regression of sorts, in observed behavior.
> > This will bite lots more users a lot more, even if the problem
> > was potentially present previously as well.
> >
> > It's a bad bug, interfering considerably with usability,
> > regardless of whether we want to call it a regression.
>
> You can always copy/paste manually, replacing the text that Emacs put
> in the clipboard for you, if you care.
>
> Or you can make the text an attachment.
>
> And please recall that the instructions for writing the bug report
> explicitly asked for avoiding non-ASCII characters.
Excuse me? That sounds like a complete cop-out, to me.
But if you're fine with pasted text from manuals not being
readable, who am I to say that this is a problem?
Telling users to avoid non-ASCII characters flies in the
face of spreading non-ASCII characters all over the manuals.
Do you honestly expect users to strip out all of the curly
quotes or replace them all with ASCII quotes, just to be
able to cite text in the manuals?
next parent reply other threads:[~2015-09-14 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<55F5CBA0.90406@cs.ucla.edu>
[not found] ` <<065d972a-464a-4d55-9b67-29b3827caeb9@default>
[not found] ` <<83si6ha5dd.fsf@gnu.org>
2015-09-14 13:41 ` Drew Adams [this message]
2015-09-14 16:38 ` bug#21471: 25.0.50; bug report with text from Info has spurious escape chars Paul Eggert
2015-09-14 18:20 ` Eli Zaretskii
2015-09-14 21:10 ` Paul Eggert
2015-09-15 6:56 ` Eli Zaretskii
[not found] <<cde9bbc9-378e-4656-8d10-caf2b8e208b7@default>
[not found] ` <<83wpvu9jf1.fsf@gnu.org>
2015-09-13 20:58 ` bug#21471: 25.0.50; REGRESSION: " Drew Adams
2015-09-14 6:22 ` Eli Zaretskii
[not found] ` <<ad82df82-fa76-4fcf-bd11-0b15de8dcb3a@default>
[not found] ` <<83r3m1a5bf.fsf@gnu.org>
2015-09-14 13:47 ` Drew Adams
2015-09-13 15:07 Drew Adams
2015-09-13 19:16 ` bug#21471: 25.0.50; " Paul Eggert
2015-09-13 20:55 ` Drew Adams
2015-09-14 6:21 ` Eli Zaretskii
2015-09-13 20:02 ` bug#21471: 25.0.50; REGRESSION: " Eli Zaretskii
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=1b2518bd-4049-423f-a32e-85d5b3adc3f4@default \
--to=drew.adams@oracle.com \
--cc=21471@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).