unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: gazally@runbox.com, eggert@cs.ucla.edu, 30405@debbugs.gnu.org
Subject: bug#30405: 26.0.91; Incorrect apostrophe translation in ImageMagick error message
Date: Sat, 10 Feb 2018 10:02:26 +0200	[thread overview]
Message-ID: <83vaf52rxp.fsf@gnu.org> (raw)
In-Reply-To: <52bmgxbsc0.fsf@fencepost.gnu.org> (message from Glenn Morris on Fri, 09 Feb 2018 19:29:03 -0500)

> From: Glenn Morris <rgm@gnu.org>
> Date: Fri, 09 Feb 2018 19:29:03 -0500
> Cc: Paul Eggert <eggert@cs.ucla.edu>, 30405@debbugs.gnu.org
> 
> Maybe a better example is:
> 
> (defun foo ()
>   (interactive)
>   (error "can't"))
> (set-buffer-multibyte nil)
> M-x foo

I applied (the obvious) band-aid to image.el, so it no longer shows a
garbled error message.

The more general issue should be fixed on master, as it's too late to
make such changes on the release branch.  Note also that
substitute-command-keys is affected as well, as can be seen by
evaluating the following:

  (progn
    (set-buffer-multibyte nil)
    (substitute-command-keys "can't"))

Basically, anything that produces non-ASCII characters and then shows
that in the echo area while the current buffer is unibyte will hit
this problem.  While Lisp programs that produce literal strings can be
told to take care of that when they use unibyte buffers, the cases
discussed in this bug report happen because we convert ASCII strings
to non-ASCII strings under the hood, so the Lisp programs cannot be
held accountable.





  reply	other threads:[~2018-02-10  8:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 21:13 bug#30405: 26.0.91; Incorrect apostrophe translation in ImageMagick error message Gemini Lasswell
2018-02-09 23:04 ` Glenn Morris
2018-02-10  0:10   ` Glenn Morris
2018-02-10  0:29     ` Glenn Morris
2018-02-10  8:02       ` Eli Zaretskii [this message]
2018-02-10 23:34       ` Glenn Morris
2018-02-11  3:38         ` Eli Zaretskii
2018-02-11  3:41           ` Eli Zaretskii
2018-02-11  5:08             ` Eli Zaretskii
2018-02-10  3:07   ` Noam Postavsky
2018-02-10  8:39     ` Eli Zaretskii
2018-02-10 14:15       ` Andreas Schwab
2018-02-10 16:43         ` Eli Zaretskii
2018-02-10 18:57       ` Paul Eggert
2018-02-10 21:24         ` Eli Zaretskii
2018-02-11 17:26           ` Paul Eggert
2018-02-11 18:04             ` Eli Zaretskii
2018-02-11 18:16               ` Eli Zaretskii
2018-02-11 20:36                 ` Paul Eggert
2018-02-12 18:21                   ` Eli Zaretskii
2018-02-12 19:34                     ` Paul Eggert
2018-02-12 19:59                       ` Eli Zaretskii
2018-02-12 20:31                         ` Paul Eggert
2018-02-13  5:03                           ` Eli Zaretskii
2018-02-13 17:43                             ` Paul Eggert
2018-02-13 19:58                               ` Eli Zaretskii
2018-02-17 12:29                                 ` Eli Zaretskii
2018-02-10 21:30         ` Richard Stallman

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=83vaf52rxp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=30405@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=gazally@runbox.com \
    --cc=rgm@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).