unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: mew-int@mew.org, kazu@iijlab.net, d.love@dl.ac.uk, emacs-devel@gnu.org
Subject: Re: [mew-int 01596] Re: windows 1252
Date: Thu, 13 Nov 2003 10:01:57 +0900 (JST)	[thread overview]
Message-ID: <200311130101.KAA04554@etlken.m17n.org> (raw)
In-Reply-To: <87ekwdilwx.fsf@tleepslib.sk.tsukuba.ac.jp> (stephen@xemacs.org)

In article <87ekwdilwx.fsf@tleepslib.sk.tsukuba.ac.jp>, "Stephen J. Turnbull" <stephen@xemacs.org> writes:
>>>>>>  "Kenichi" == Kenichi Handa <handa@m17n.org> writes:
>>>  7.  The UTF-8 encoding
Kenichi>  [...]
>>>  How about using this to encode mule-unicode-0100-24ff?

Kenichi>  That's a good idea.  I'll work on it.

> AFAIK this is an XFree86-only extension.  As of X11R6.4 such
> extensions were forbidden in X.org Compound Text Encoding.  Is it
> really a good idea?

I think so.  Currently we encode mule-unicode-0100-24ff by
ESC $ - 1 ...  which is also an invalid code, and only Emacs
can decode it.  If we use UTF-8 encoding, more clients can
decode it.

> On the other hand, even if extended segments are ugly, we must support
> extended segments to handle ISO-8859-15 selections on XFree86.  At
> least it is a standard mechanism on all versions of X, going back to
> at least X11R5.

Emacs decodes extended segment for ISO-8859-15 correctly,
but doesn't use it for encoding.  According to Dave, Latin-9
(ISO-8859-15) users don't want it.  See this code in
mule.el.

;; If you add charsets here, be sure to modify the regexp used by
;; ctext-pre-write-conversion to look up non-standard charsets.
(defvar ctext-non-standard-designations-alist
  '(("$(0" . (big5 "big5-0" 2))
    ("$(1" . (big5 "big5-0" 2))
    ;; The following are actually standard; generating extended
    ;; segments for them is wrong and screws e.g. Latin-9 users.
    ;; 8859-{10,13,16} aren't Emacs charsets anyhow.  -- fx
;;     ("-V"  . (t "iso8859-10" 1))
;;     ("-Y"  . (t "iso8859-13" 1))
;;     ("-_"  . (t "iso8859-14" 1))
;;     ("-b"  . (t "iso8859-15" 1))
;;     ("-f"  . (t "iso8859-16" 1))

I think Dave is correct because CTEXT spec has this
paragraph.

	Extended segments are not to be	used for any character set
	encoding that can be constructed from a	GL/GR pair of
	approved standard encodings. For example, it is	incorrect to
	use an extended	segment	for any	of the ISO 8859	family of
	encodings.

---
Ken'ichi HANDA
handa@m17n.org

  reply	other threads:[~2003-11-13  1:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031029.160819.120233945.kazu@iijlab.net>
     [not found] ` <20031029.082403.193886873.wl@gnu.org>
     [not found]   ` <20031030.175736.39971315.kazu@iijlab.net>
2003-10-30 14:41     ` [mew-int 01581] Re: windows 1252 Werner LEMBERG
2003-10-31 11:04       ` [mew-int 01579] " Kenichi Handa
2003-10-31 12:39         ` [mew-int 01583] " Kazu Yamamoto
2003-11-01 15:36           ` [mew-int 01584] " Eli Zaretskii
2003-11-02  6:41             ` [mew-int 01582] " Stephen J. Turnbull
2003-11-04  2:13               ` [mew-int 01586] " Kazu Yamamoto
2003-11-04  5:55                 ` [mew-int 01585] " Eli Zaretskii
2003-11-04  6:13                   ` [mew-int 01587] " Kazu Yamamoto
2003-11-04  6:23                   ` [mew-int 01589] " Stephen J. Turnbull
2003-11-04 15:13                 ` [mew-int 01590] " Stefan Monnier
2003-11-04 15:55                   ` [mew-int 01591] " Kazu Yamamoto
2003-11-04 17:04                     ` [mew-int 01590] " Stefan Monnier
2003-11-04 18:45                     ` Stephen J. Turnbull
2003-11-05  1:59                       ` [mew-int 01594] " Kazu Yamamoto
2003-11-05  5:00                         ` [mew-int 01593] " Stephen J. Turnbull
2003-11-07  7:30                           ` Kenichi Handa
2003-11-07  7:28                         ` [mew-int 01597] " Kenichi Handa
2003-11-07  8:21                           ` [mew-int 01599] " Kazu Yamamoto
2003-11-07  7:13                 ` [mew-int 01596] " Kenichi Handa
2003-11-10  7:11                   ` [mew-int 01607] " Kazu Yamamoto
2003-11-10  7:42                     ` [mew-int 01608] " Kenichi Handa
2003-11-12 16:36                       ` [mew-int 01596] " Stephen J. Turnbull
2003-11-13  1:01                         ` Kenichi Handa [this message]
2003-11-13 16:32                           ` Stephen J. Turnbull
2003-11-14  2:57                             ` Kenichi Handa
2003-11-14 11:20                               ` Stephen J. Turnbull
2003-11-14 12:02                                 ` Kenichi Handa
2003-11-13 19:49                           ` Eli Zaretskii
2003-11-14  3:39                             ` [mew-int 01621] " Kenichi Handa

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=200311130101.KAA04554@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=d.love@dl.ac.uk \
    --cc=emacs-devel@gnu.org \
    --cc=kazu@iijlab.net \
    --cc=mew-int@mew.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).