From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-26 0feb673: Display raw bytes as belonging to 'eight-bit' charset
Date: Fri, 27 Jul 2018 15:03:48 -0400 [thread overview]
Message-ID: <jwvin50r08h.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 2499AA9B-E194-4EE0-BF2B-97F082B999EB@gnu.org
> The above change is safe, more-or-less, because it only affects how we
> display information about characters. Making an equivalent change
> inside char-charset would affect all users of that API.
Yes, clearly this would be for `master`.
> In the Thai language environment, that just might make sense.
I don't see why it would ever make sense.
Actually, I don't understand why
(char-charset (unibyte-char-to-multibyte #x90))
should return `tis620-2533`, since the tis620.2533 standard defines
a coding-system similar to those of iso8859 and the corresponding chars
all exist in the BMP of Unicode (the "Thai block" U+0E01 through
U+0E7F), so I can't see any obvious reason why they should affect the
3x3fffxx private space used by Emacs for "eight-bit chars".
Could it be just a bug?
Stefan
next prev parent reply other threads:[~2018-07-27 19:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180727064907.6305.13029@vcs0.savannah.gnu.org>
[not found] ` <20180727064909.85288203C0@vcs0.savannah.gnu.org>
2018-07-27 12:38 ` [Emacs-diffs] emacs-26 0feb673: Display raw bytes as belonging to 'eight-bit' charset Stefan Monnier
2018-07-27 13:10 ` Robert Pluim
2018-07-27 13:46 ` Eli Zaretskii
2018-07-27 15:00 ` Andreas Schwab
2018-07-27 17:54 ` Eli Zaretskii
2018-07-27 17:59 ` Andreas Schwab
2018-07-27 20:50 ` Eli Zaretskii
2018-07-27 19:03 ` Stefan Monnier [this message]
2018-07-27 21:04 ` Eli Zaretskii
2018-07-28 14:15 ` Stefan Monnier
2018-07-28 15:15 ` Eli Zaretskii
2018-07-28 16:49 ` Stefan Monnier
2018-07-28 17:37 ` Eli Zaretskii
2018-07-28 7:53 ` Andreas Schwab
2018-07-27 13:53 ` Eli Zaretskii
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=jwvin50r08h.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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 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.