coding-system for drafts (was Re: sending delayed articles bug)

[Katsumi Yamaoka <yamaoka@jpl.org>]

Hi,

If you have unfinished drafts, I recommend you send all of them
before updating Gnus.  I took care you don't have to do so,
though. :)

>>>>> In <84adl2llk6.fsf@crybaby.uni-duisburg.de>
>>>>>	kai.grossjohann@uni-duisburg.de (Kai Großjohann) wrote:

> Katsumi Yamaoka <yamaoka@jpl.org> writes:

>> By the way, why don't we use the universal coding-system, e.g.
>> iso-2022-7-bit, for saving and reading draft articles in both
>> FSF Emacs and XEmacs?  In the present, FSF Emacs uses emacs-mule
>> and XEmacs uses escape-quoted by default, so draft articles made
>> by FSF Emacs can't be handled by XEmacs and the contrary is also
>> bad. :-{

> That's a good idea!

Thanks.

Let's put a point at issue into the handling of the existing
draft files.  First of all, there's no problem if a user has set
mm-auto-save-coding-system to a certain value.  It is
satisfactory for using iso-2022-7bit to read draft files which
have been saved by escape-quoted either, since those coding
systems are mostly compatible under XEmacs.  However, a relief
measure should be taken in the case of FSF Emacs.  Then, I've
changed mm-util.el and nndraft.el with the following plans:

1. Set the default value for mm-auto-save-coding-system to
   iso-2022-7bit, except nil for non-Mule XEmacs.  The value is
   passed to message-draft-coding-system.

2. Simply read a draft file using the value of
   message-draft-coding-system under XEmacs.

3. Under FSF Emacs, read a draft file as raw-text into a buffer
   if the value of message-draft-coding-system is iso-2022-7bit,
   otherwise use the value of message-draft-coding-system itself
   to read a file.  In the former case, decode the buffer
   contents as emacs-mule if there are over-7-bit data in a
   buffer, otherwise decode the contents using the value of
   message-draft-coding-system.

I wish there were no problems.

Regards,
-- 
Katsumi Yamaoka <yamaoka@jpl.org>