[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (no subject)
From: |
Tak Ota |
Subject: |
Re: (no subject) |
Date: |
Sat, 23 Feb 2002 15:11:06 -0800 (PST) |
Yamamoto-san,
We find that there is a small conflict in a recent change made to the
developer version of emacs with the coding system used in Mew package.
Could you answer to the following question? What I can tell is
mew-mule3.el defines as:
;; ctext for consistency --unibyte, -unix for XEmacs's ^M
(defvar mew-cs-m17n (if (mew-coding-system-p 'ctext-unix) 'ctext-unix 'ctext))
Therefore many buffers in Mew sets ctext-unix as the default coding
system. However, I have no idea how this decision was made.
-Tak
Sat, 23 Feb 2002 13:51:54 -0500: Eli Zaretskii <address@hidden> wrote:
> Tak Ota on Sat, 23 Feb 2002 08:11:49 -0800 (PST))
> Subject: Re: ctext-pre-write-conversion barfs
> Reply-to: Eli Zaretskii <address@hidden>
> References: <address@hidden>
> <address@hidden> <address@hidden>
> --text follows this line--
> > Date: Sat, 23 Feb 2002 08:11:49 -0800 (PST)
> > From: Tak Ota <address@hidden>
> >
> > BTW, I just now tried to save this buffer and noticed that
> > ctext-pre-write-conversion was invoked. It is called 3 times for
> > each save-buffer. Here is the output from describe-coding-system.
> >
> > Coding system for saving this buffer:
> > x -- ctext-unix
>
> Could you please find out how come the buffer's encoding got set to
> ctext-unix? It's a very unusual coding system for buffers.
> Compound-text is normally used for X selections only.
>
> The reason I'm asking you to look into this is that the assumption
> behind the code I wrote for the ctext extensions is that ctext is not
> normally used for file I/O. There are limitations of the pre-write
> and post-read conversions that make the modified ctext coding system
> inappropriate for reading and writing text to/from multibyte buffers.
> If ctext is used for file I/O, I will have to revert the decision to
> call the new encoding `ctext', and will find some other name.
>
> So please look into this. Thanks in advance.
>
> _______________________________________________
> Emacs-devel mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/emacs-devel