unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 7925@debbugs.gnu.org, cyd@stupidchicken.com, rrt@sc3d.org
Subject: bug#7925: 23.2.91; report-emacs-bug doesn't like curly quotes
Date: Sun, 30 Jan 2011 15:19:35 +0100	[thread overview]
Message-ID: <87bp2yeao8.fsf@gmail.com> (raw)
In-Reply-To: <E1PjXpt-0001lY-9a@fencepost.gnu.org> (Eli Zaretskii's message of "Sun, 30 Jan 2011 09:01:01 -0500")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Štěpán Němec <stepnem@gmail.com>
>> Cc: Chong Yidong <cyd@stupidchicken.com>,  7925@debbugs.gnu.org,  rrt@sc3d.org
>> Date: Sun, 30 Jan 2011 13:48:46 +0100
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > Actually, this was added in Emacs 20 or 21, when Emacs got support for
>> > multi-lingual editing.  the reason was to make sure bug reports are
>> > written in English and not in some other languages that maintainers
>> > could not command.  Also, various MUAs, even in Emacs, might convert
>> > non-ASCII characters into illegible mess.
>> 
>> If this is the reason, IMO it is pretty silly. You already say "please
>> write in English" in the template message. If somebody can ignore that,
>> they can certainly ignore this mystery meat message, too -- e.g. I had
>> no idea what it meant and I doubt most other people understand "convert
>> non-ASCII letters to hexadecimal?" as "please write in English" either.
>
> The non-ASCII characters could be part of a Lisp backtrace (from a
> byte-compiled function).  In that case, conversion to hex is a
> reasonable thing to d.

I don't see why mangling any kind of information would be reasonable,
unless of course you mean proper encoding of non-ascii content which any
functional MUA does, but that should be (and is) done automatically
without any kind of user intervention. In any case, this reasoning is
quite different from the one stated in your previous message (although
it doesn't make much more sense to me).

  Štěpán





  parent reply	other threads:[~2011-01-30 14:19 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 [this message]
2011-01-30 14:42           ` Eli Zaretskii
2011-01-30 13:33     ` Reuben Thomas
2011-01-30 14:26       ` Eli Zaretskii
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=87bp2yeao8.fsf@gmail.com \
    --to=stepnem@gmail.com \
    --cc=7925@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=eliz@gnu.org \
    --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).