From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Max Mikhanosha <max.mikhanosha@protonmail.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Bugfix for utf-8 XTerm/MinTTY and (set-input-meta-mode t)
Date: Tue, 01 Jun 2021 16:06:48 -0400 [thread overview]
Message-ID: <jwvim2xjqz8.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <C-hzVz5np2upcH8IBAZRHpYkg10OuQmyYQKucOL6ntbxtL205LtQQFXNfcipmcoavl0VReVkujYEqTCWXfLZiihuaOyEUZIPGU2ciyUYHqA=@protonmail.com> (Max Mikhanosha's message of "Tue, 01 Jun 2021 16:19:40 +0000")
> Both XTerm and MinTTY, when configured to send meta modifier as 8th
> bit while in utf-8 mode, will first add 8th bit, and then encode
> resulting character with utf-8. For example Meta-X is encoded
> as ?x+128 = #248 codepoint, encoded as 0xc3,0xb8
How did they end up with that weird design?
I mean they could have made meta toggle the 24th bit, for example, so it
doesn't collide with other existing characters.
This design is quite weird since it breaks all the latin-1 chars of
unicode plus all the uses of meta with non-ASCII chars.
How do they encode M-λ ?
Is it also sent as the same byte-sequence as `?λ + 128 = ?л` ?
Admittedly, it is better than the "original" meta-as-8th-bit which was
limited to ASCII, but it still seems unnecessarily limited and kludgey.
Stefan
next prev parent reply other threads:[~2021-06-01 20:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 16:19 Bugfix for utf-8 XTerm/MinTTY and (set-input-meta-mode t) Max Mikhanosha
2021-06-01 16:51 ` Eli Zaretskii
2021-06-01 17:28 ` Max Mikhanosha
2021-06-01 17:38 ` Eli Zaretskii
2021-06-01 18:01 ` Max Mikhanosha
2021-06-01 18:18 ` Eli Zaretskii
2021-06-01 18:35 ` Max Mikhanosha
2021-06-01 18:46 ` Eli Zaretskii
2021-06-02 9:22 ` Max Mikhanosha
2021-06-02 12:16 ` Andreas Schwab
2021-06-03 5:42 ` Max Mikhanosha
2021-06-05 14:20 ` Eli Zaretskii
2021-06-01 17:29 ` Eli Zaretskii
2021-06-01 17:45 ` Max Mikhanosha
2021-06-01 17:52 ` Eli Zaretskii
2021-06-01 18:10 ` Max Mikhanosha
2021-06-01 17:04 ` Andreas Schwab
2021-06-01 17:36 ` Max Mikhanosha
2021-06-01 20:06 ` Stefan Monnier [this message]
2021-06-02 10:21 ` Max Mikhanosha
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=jwvim2xjqz8.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=max.mikhanosha@protonmail.com \
/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).