unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: RMAIL, MIME clean-up, coding system
Date: Wed, 08 Oct 2003 00:49:31 +0200	[thread overview]
Message-ID: <8296-Wed08Oct2003004931+0200-eliz@elta.co.il> (raw)
In-Reply-To: <200310072136.h97La6dL004066@oak.pohoyda.family> (message from Alexander Pohoyda on Tue, 7 Oct 2003 23:36:06 +0200 (CEST))

> Date: Tue, 7 Oct 2003 23:36:06 +0200 (CEST)
> From: Alexander Pohoyda <alexander.pohoyda@gmx.net>
> 
> > > Using a message-global X-Coding-System header field is not an option
> > > anymore.
> > 
> > Sorry, I don't see why not; we could, for example, use emacs-mule,
> > right?
> 
> What do we do when we save an email to the file?

We encode it in emacs-mule (reagrdless of what X-Coding-System
says).  This is so with Emacs today.

> Am I right that the
> file encoded using emacs-mule will only be readable by Emacs?

The ASCII parts will be readable, unlike base64, for example.

> > Yuck!  (Sorry, couldn't resist: I _hate_ encodings that aren't
> > readable by humans outside specialized software.)
> 
> Do you mean base64 or emacs-mule encoding here?

base64, of course.  In too many cases, it makes human-readable text
incomprehensible.  We should at least allow to read the 7-bit ASCII.

  reply	other threads:[~2003-10-07 22:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200310051053.h95ArIwj001185@oak.pohoyda.family>
2003-10-07 21:20 ` RMAIL, MIME clean-up, coding system Eli Zaretskii
2003-10-07 21:36   ` Alexander Pohoyda
2003-10-07 22:49     ` Eli Zaretskii [this message]
2003-10-07 21:59   ` Stefan Monnier
2003-10-07 22:33     ` Alexander Pohoyda
2003-10-07 23:02       ` Stefan Monnier
2003-10-07 22:50     ` Eli Zaretskii
2003-10-07 23:04       ` Stefan Monnier
     [not found] <200310080542.h985gNkp000541@oak.pohoyda.family>
2003-10-09 14:44 ` Richard Stallman
2003-10-12 20:33   ` Alexander Pohoyda

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=8296-Wed08Oct2003004931+0200-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=emacs-devel@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).