unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: kazu@iijlab.net, mew-int@mew.org, emacs-devel@gnu.org
Subject: Re: [mew-int 00737] Re: (no subject)
Date: Tue, 26 Feb 2002 18:52:59 +0200	[thread overview]
Message-ID: <1858-Tue26Feb2002185258+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <200202250710.QAA01605@etlken.m17n.org> (message from Kenichi Handa on Mon, 25 Feb 2002 16:10:20 +0900 (JST))

> Date: Mon, 25 Feb 2002 16:10:20 +0900 (JST)
> From: Kenichi Handa <handa@etl.go.jp>
> 
> >>  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.

I made the change in CVS head.  (It isn't required in the RC, since I
didn't change the names there to begin with.)

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  reply	other threads:[~2002-02-26 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-25  7:10 [mew-int 00737] Re: (no subject) Kenichi Handa
2002-02-26 16:52 ` Eli Zaretskii [this message]
  -- 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

  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=1858-Tue26Feb2002185258+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --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).