all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: \201 back again
Date: Sat, 21 Sep 2002 00:54:04 +0300	[thread overview]
Message-ID: <3028-Sat21Sep2002005404+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <shhegkzj68.fsf@tux.gnu.franken.de> (message from Karl Eichwalder on Fri, 20 Sep 2002 19:04:47 +0200)

> From: Karl Eichwalder <keichwa@gmx.net>
> Date: Fri, 20 Sep 2002 19:04:47 +0200
> 
> > Here's the header I see on my system:
> >
> >   Content-Type: text/plain; charset=iso-8859-15
> >
> > This is perfectly valid, AFAICS.
> 
> Maybe, some mail gateway did add those lines for you.
> 
> But these lines were missing from the original posting -- RMS never
> ever bothers to add such stuff, I guess ;) :

Sorry,  I now see that I looked at a wrong message, not the one you
had in mind.

Richard's message indeed shows \201 characters, but that's only
because they were present in the message itself:

      (re-search-forward "[=C2=81=C2=AB=C2=81=C2=BB{}()]" nil t)

See those 0xC2 characters before each 8-bit Latin-9 code?

As for the encoding, it says this:

   Content-Type: text/plain; charset=utf-8

So the question now is how come Richard's Emacs sent such a badly
encoded message, and why did it think it was in UTF-8 when in fact it
was in emacs-mule?

  parent reply	other threads:[~2002-09-20 21:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-07  9:00 \201 back again Karl Eichwalder
2002-09-20 16:22 ` Eli Zaretskii
2002-09-20 17:04   ` Karl Eichwalder
2002-09-20 21:47     ` ShengHuo ZHU
2002-09-20 21:54     ` Eli Zaretskii [this message]
2002-09-21 12:47       ` Karl Eichwalder
2002-09-21 15:00         ` Eli Zaretskii
2002-09-21 15:16           ` Karl Eichwalder
2002-09-22  4:42             ` Eli Zaretskii
2002-09-22 22:44           ` Stefan Monnier
2002-09-23  9:33             ` Andreas Schwab
2002-09-21 19:39       ` Richard Stallman

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=3028-Sat21Sep2002005404+0300-eliz@is.elta.co.il \
    --to=eliz@is.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.