[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#30405: 26.0.91; Incorrect apostrophe translation in ImageMagick erro

From: Paul Eggert
Subject: bug#30405: 26.0.91; Incorrect apostrophe translation in ImageMagick error message
Date: Mon, 12 Feb 2018 12:31:55 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0

On 02/12/2018 11:59 AM, Eli Zaretskii wrote:
explicitly requests display of raw bytes as Latin-1 characters, and it
requests that everywhere, including the echo area and whatnot.

That's not how Emacs works, at least not in my experience. For example, on current emacs-26:

   emacs -Q
   M-x set-variable RET unibyte-display-via-language-environment RET t RET
   (defun foo ()
     (message "cannot \xA2\u00A2")) C-j
   M-x foo RET

This displays "\242¢", not "¢¢".

No doubt this isn't documented as well as it should be, but from looking at the source code get_next_display_element it's clear that unibyte-display-via-language-environment does not simply display every raw byte as a Latin-1 character; instead, the code also takes context into account, and if the context is multibyte then unibyte-display-via-language-environment is ignored. Since the echo area's context is text and not binary data, the display of raw bytes in the echo area should be unaffected by unibyte-display-via-language-environment.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]