From: Richard Stallman <rms@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: gazally@runbox.com, 30405@debbugs.gnu.org,
npostavs@users.sourceforge.net
Subject: bug#30405: 26.0.91; Incorrect apostrophe translation in ImageMagick error message
Date: Sat, 10 Feb 2018 16:30:55 -0500 [thread overview]
Message-ID: <E1ekcjX-000860-24@fencepost.gnu.org> (raw)
In-Reply-To: <2061ef0c-de4d-d8c1-aea8-786223e59c7e@cs.ucla.edu> (message from Paul Eggert on Sat, 10 Feb 2018 10:57:28 -0800)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> 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 agree in principle. But I don't know how much work the change would
be.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.
prev parent reply other threads:[~2018-02-10 21:30 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
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 [this message]
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=E1ekcjX-000860-24@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=30405@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--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 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).