From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: coding-system for drafts
Date: Tue, 29 Oct 2002 15:27:11 +0100 [thread overview]
Message-ID: <84y98htj5s.fsf@crybaby.uni-duisburg.de> (raw)
In-Reply-To: <yotlvg3l8t2u.fsf_-_@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> 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.
Why can't you read a draft as iso-2022-7bit? After all, that's the
coding system that was used for saving it, too.
And then, you could write the encoding of the draft into a header.
Then a missing header means to do what has been done up to now so we
stay backwards compatible. WDYT?
kai (not an expert on Mule)
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-10-29 14:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 12:25 sending delayed articles bug Katsumi Yamaoka
2002-10-25 13:01 ` Kai Großjohann
2002-10-29 9:58 ` coding-system for drafts (was Re: sending delayed articles bug) Katsumi Yamaoka
2002-10-29 14:27 ` Kai Großjohann [this message]
2002-10-30 1:36 ` coding-system for drafts Katsumi Yamaoka
2002-10-30 10:15 ` Kai Großjohann
2002-10-30 12:28 ` Katsumi Yamaoka
2002-10-30 16:14 ` Kai Großjohann
2002-10-31 4:44 ` Katsumi Yamaoka
2002-10-31 7:35 ` Katsumi Yamaoka
2002-10-31 17:35 ` Kai Großjohann
2002-11-01 4:32 ` Katsumi Yamaoka
2002-11-05 12:36 ` Kai Großjohann
2002-10-31 17:30 ` Kai Großjohann
2002-11-01 17:49 ` Kai Großjohann
2002-11-05 9:23 ` Katsumi Yamaoka
2002-11-05 12:38 ` Kai Großjohann
2002-11-08 7:25 ` Katsumi Yamaoka
2002-11-13 16:14 ` Reiner Steib
2002-11-02 15:34 ` TSUCHIYA Masatoshi
2002-11-05 12:23 ` Kai Großjohann
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=84y98htj5s.fsf@crybaby.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.de \
/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.
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 NNTP newsgroup(s).