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: Sat, 28 Jul 2018 12:49:10 -0400 [thread overview]
Message-ID: <jwvfu03paut.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 83effntmr3.fsf@gnu.org
>> I know and understand what this charset is for. Yet I don't see why
>> eight-bit-control chars should be reported as belonging to this charset
>> (any more than they should be reported to belong to any of the other
>> charsets to which they may also belong, such as all the iso8859
>> charsets).
>
> Because ISO-8859 charsets don't include bytes between 128 and 159
> (inclusive), I guess.
According to the info I found, tis620 doesn't include those codes either
(and doesn't include 160 either, contrary to iso8859-11 which is
otherwise identical).
> We actually don't want to expose eight-bit-control to users at all, we
> want there to be a single charset called 'eight-bit' covering all the
> raw bytes.
Fair enough, then the chars in eight-bit-control should have `eight-bit`
as their canonical charset (no matter the user's language environment).
Stefan
next prev parent reply other threads:[~2018-07-28 16:49 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
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 [this message]
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=jwvfu03paut.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.