Re: [mew-int 00737] Re: (no subject)

[Kenichi Handa]

Eli Zaretskii <address@hidden> 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
address@hidden