From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 7925@debbugs.gnu.org, cyd@stupidchicken.com
Subject: bug#7925: 23.2.91; report-emacs-bug doesn't like curly quotes
Date: Sun, 30 Jan 2011 09:26:59 -0500 [thread overview]
Message-ID: <E1PjYF1-00035b-Fg@fencepost.gnu.org> (raw)
In-Reply-To: <AANLkTikwR9PO+Fg71y-A+NSUKrTU3yJx7-h-TFSB1UvY@mail.gmail.com> (message from Reuben Thomas on Sun, 30 Jan 2011 13:33:02 +0000)
> Date: Sun, 30 Jan 2011 13:33:02 +0000
> From: Reuben Thomas <rrt@sc3d.org>
> Cc: Chong Yidong <cyd@stupidchicken.com>, 7925@debbugs.gnu.org
>
> > Also, various MUAs, even in Emacs, might convert
> > non-ASCII characters into illegible mess.
>
> Then they should be fixed to encode the text properly and specify the
> encoding. It's a bit late in the day to be working around programs
> that can't cope with non-7-bit encodings!
The goal is to make dug reporting and analysis as simple and efficient
as possible. Not to fix all the possible bugs that are unrelated to
the one being reported.
> > Maybe
> > some kind of list of allowed non-ASCII characters will be good enough.
>
> It would be better than nothing, but the list will never be long
> enough.
We have Unicode character properties to help us out (see "Character
Properties" in the ELisp manual), and also charset properties. So it
doesn't have to be a list of literal characters.
> For example, what's wrong with using symbols such as arrows or
> smileys, or, in your own example, ellipses?
That the fonts installed on the recipient's machine don't support
them?
next prev parent reply other threads:[~2011-01-30 14:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 21:57 bug#7925: 23.2.91; report-emacs-bug doesn't like curly quotes Reuben Thomas
2011-01-29 23:34 ` Chong Yidong
2011-01-30 11:13 ` Eli Zaretskii
2011-01-30 12:48 ` Štěpán Němec
2011-01-30 14:01 ` Eli Zaretskii
2011-01-30 14:08 ` Reuben Thomas
2011-01-30 14:19 ` Štěpán Němec
2011-01-30 14:42 ` Eli Zaretskii
2011-01-30 13:33 ` Reuben Thomas
2011-01-30 14:26 ` Eli Zaretskii [this message]
2011-01-30 22:15 ` Reuben Thomas
2011-02-01 19:58 ` Stefan Monnier
2011-02-06 15:05 ` Chong Yidong
2011-02-07 15:44 ` Reuben Thomas
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=E1PjYF1-00035b-Fg@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=7925@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=rrt@sc3d.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).