unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dave Love <d.love@dl.ac.uk>
Cc: Richard Stallman <rms@gnu.org>,  emacs-devel@gnu.org,  pmr@pajato.com
Subject: Re: Rmail changes for Emacs 22
Date: 21 Oct 2002 16:33:41 +0100	[thread overview]
Message-ID: <rzqheffajsa.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: Pine.SUN.3.91.1021016080428.20518C-100000@is

Eli Zaretskii <eliz@is.elta.co.il> writes:

> Personally, I think emacs-mule is not a good idea in this case, since 
> mbox is not Emacs-private format, so some other software should be able 
> to read it.

I don't see how that follows, but any file that has to represent the
full range of Emacs characters has to be stored in the internal
encoding.  I don't know what the rationale is for any of this, or why
rmail uses emacs-mule now.

> A good alternative would be to encode each message as what 
> the charset= header says (and add/fix such a header if there is none, or 
> if the one that's there lies).

I doubt you should do anything to them, especially as you have no
assurance any headers are correct.

  parent reply	other threads:[~2002-10-21 15:33 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <rzqu1jseva6.fsf@albion.dl.ac.uk>
2002-10-13  4:08 ` Rmail changes for Emacs 22 Richard Stallman
2002-10-15 17:40   ` Dave Love
2002-10-16  4:38     ` Richard Stallman
2002-10-16  6:09       ` Eli Zaretskii
2002-10-16  7:19         ` Kenichi Handa
2002-10-19  4:25           ` Paul Michael Reilly
2002-10-19  4:55           ` Richard Stallman
2002-10-20  7:03             ` Eli Zaretskii
2002-10-18 22:59         ` Richard Stallman
2002-10-20 19:40           ` Stefan Monnier
2002-10-22  3:12             ` Richard Stallman
2002-10-22  6:33               ` Kai Großjohann
2002-10-22 18:48                 ` Eli Zaretskii
2002-10-22 14:32               ` Stefan Monnier
2002-10-23  7:12                 ` Richard Stallman
2002-10-23  8:13                   ` Kenichi Handa
2002-10-25  5:36                     ` Richard Stallman
2002-10-23  9:57                   ` Paul Michael Reilly
2002-10-23 16:58                     ` Eli Zaretskii
2002-10-24  7:29                       ` Stefan Monnier
2002-10-24 17:30                         ` Eli Zaretskii
2002-10-21 15:33         ` Dave Love [this message]
2002-10-21 16:37           ` Kai Großjohann
2002-10-21 20:50             ` Stefan Monnier
2002-10-22  6:28               ` Kai Großjohann
2002-10-22  6:31         ` Kai Großjohann
2002-10-22 18:40           ` Eli Zaretskii
2002-10-23  5:24             ` Kai Großjohann
2002-10-16 12:21       ` Paul Michael Reilly
2002-10-19  4:56         ` Richard Stallman
2002-10-21 15:34       ` Dave Love
2002-10-22 16:36         ` Richard Stallman
2002-10-24 21:37           ` Dave Love
2002-10-16  4:38     ` Richard Stallman
2002-10-21 15:31       ` Dave Love

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=rzqheffajsa.fsf@albion.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    --cc=emacs-devel@gnu.org \
    --cc=pmr@pajato.com \
    --cc=rms@gnu.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).