From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: npostavs@users.sourceforge.net, 30405@debbugs.gnu.org,
gazally@runbox.com
Subject: bug#30405: 26.0.91; Incorrect apostrophe translation in ImageMagick error message
Date: Sun, 11 Feb 2018 09:26:41 -0800 [thread overview]
Message-ID: <fb16b76b-493d-0e5e-76ae-39fa3b614ac6@cs.ucla.edu> (raw)
In-Reply-To: <83wozk1qsy.fsf@gnu.org>
Eli Zaretskii wrote:
>> Cc: rgm@gnu.org, gazally@runbox.com, 30405@debbugs.gnu.org
>> From: Paul Eggert <eggert@cs.ucla.edu>
>> Date: Sat, 10 Feb 2018 10:57:28 -0800
>>
>> Eli Zaretskii wrote:
>>> We make the echo area
>>> buffer unibyte when the message is generated with the current buffer
>>> being unibyte.
>>
>> This made sense back in the 1990s when unibyte was commonly used for text.
>> Nowadays, though, wouldn't it make more sense to keep the echo area multibyte?
>> The echo area is intended for text, not for binary data.
>
> I don't see how the date outside could matter here.
What I was trying to say is that back in the 1990s it was relatively common for
people to run Emacs mostly in unibyte mode and to edit files in a Latin-1
locale, so it was natural for programmers to expect the echo area to be
consistent with the file being edited. Nowadays we live in a mostly-multibyte
world, where unibyte inside Emacs is intended only for binary data, and so it's
no longer a reasonable design choice to have the echo area (which is intended
for text messages to the user) to be unibyte (which is now intended for binary
data).
> I have a guess for why we did that: it's because in Emacs 21 we
> displayed raw bytes as Latin-N characters, so non-ASCII text in
> unibyte strings needed a unibyte buffer to display it as expected.
> But that feature is no longer available, as raw bytes are always
> displayed as octal escapes.
Sounds plausible.
> The question that bothers me is can a unibyte string inserted or
> printed into a multibyte buffer be converted to something that will
> display as a non-ASCII character, not as an octal escape.
Surely we can arrange for the latter.
next prev parent reply other threads:[~2018-02-11 17:26 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb16b76b-493d-0e5e-76ae-39fa3b614ac6@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=30405@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gazally@runbox.com \
--cc=npostavs@users.sourceforge.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.