unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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 10:15:39 -0400	[thread overview]
Message-ID: <jwvbmarqwt3.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 83zhycqtk7.fsf@gnu.org

>> > In the Thai language environment, that just might make sense.
>> I don't see why it would ever make sense.
> because users of the Thai language environment most probably know and
> understand what this charset is for.

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).

I believe this happens only by accident: it seems to be the only charset
of its kind defined with `:superset (... eight-bit-control ...)` and
without :supplementary-p.

But maybe the real source of the problem is that eight-bit-control is
defined as :supplementary-p (hard to tell, because I only see doc of
how/when :supplementary-p should be used, but not what it does).

> You are asking why we have this charset in the first place?

No, I understand why we have it, what I don't understand why it should
be considered anything but a bug that eight-bit-control chars should be
considered as belonging to that charset instead of to the
eight-bit-control charset: they belong to both charsets (and to many
others as well), but the "canonical" charset to which they belong should
be eight-bit-control.


        Stefan




  reply	other threads:[~2018-07-28 14:15 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 [this message]
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

  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=jwvbmarqwt3.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 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).