From: Kenichi Handa <handa@etl.go.jp>
Cc: kazu@iijlab.net, mew-int@mew.org, emacs-devel@gnu.org
Subject: Re: [mew-int 00737] Re: (no subject)
Date: Mon, 25 Feb 2002 16:10:20 +0900 (JST) [thread overview]
Message-ID: <200202250710.QAA01605@etlken.m17n.org> (raw)
In-Reply-To: message from Eli Zaretskii on Mon, 25 Feb 2002 08:55:36 +0200 (IST)
Eli Zaretskii <eliz@is.elta.co.il> writes:
> Handa-san, it sounds like the new encoding with ICCM Extended Segments
> support should not be called ctext, because ctext is used in file I/O, at
> least by Mew. It sounds like we should leave ctext as it was working
> before, including the fact that it didn't support the ICCCM Extended
> Segments, and use another name (e.g., compound-text-with-extensions) for
> the new coding system. We will then have to make that new coding system
> be the default for X selections in CVS head.
> Do you agree?
>> So, to my best knowledge, ctext is only the character set which can
>> survive in the old Emacs world and the multilingual Emacs world.
> It was IMHO an unfortunate decision to use ctext for file I/O, since
> ctext must support the ICCCM spec which is inappropriate for encoding
> anything but X selections. However, given that Mew uses that for quite
> some time, Emacs shouldn't break it, I think.
Considering this situation, I agree with the name change.
---
Ken'ichi HANDA
handa@etl.go.jp
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next reply other threads:[~2002-02-25 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 7:10 Kenichi Handa [this message]
2002-02-26 16:52 ` [mew-int 00737] Re: (no subject) Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2002-02-23 16:11 ctext-pre-write-conversion barfs Tak Ota
2002-02-23 18:51 ` (no subject) Eli Zaretskii
2002-02-23 23:11 ` Tak Ota
2002-02-25 1:11 ` [mew-int 00737] " Kazu Yamamoto
2002-02-25 6:55 ` 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=200202250710.QAA01605@etlken.m17n.org \
--to=handa@etl.go.jp \
--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 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.