From: Simon Josefsson <simon@josefsson.org>
Cc: ding@gnus.org
Subject: Re: \201 irritation! :-)
Date: 08 Sep 2000 19:49:47 +0200 [thread overview]
Message-ID: <iluzoliu62s.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <xkn4s3rw7qj.fsf@tahkokari.cs.Helsinki.FI>
Janne Rinta-Manty <rintaman@cs.helsinki.fi> writes:
> Another \201 report: I get \201s in the Summary buffer if the
> message's headers have unencoded iso-8859-1 characters (with and
> without "correct" Content-Type etc. headers). Article buffer has no
> \201s.
Fixed, thanks.
(Unencoded non-ascii characters in headers are invalid. But now you
shouldn't get \201's at least. What symbols the character codes will
show up as will depend on what Mule implementation and configuration
you use, but that is as you would expect.)
next prev parent reply other threads:[~2000-09-08 17:49 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-27 17:21 François Pinard
2000-08-27 21:13 ` François Pinard
2000-08-28 8:44 ` Kai Großjohann
2000-08-28 19:14 ` Stainless Steel Rat
2000-08-28 19:54 ` François Pinard
2000-08-28 21:36 ` Stainless Steel Rat
2000-08-28 22:46 ` François Pinard
2000-09-05 14:29 ` Dave Love
2000-09-05 16:19 ` Stainless Steel Rat
2000-09-08 23:32 ` Dave Love
2000-09-09 2:49 ` Stainless Steel Rat
2000-09-06 14:56 ` François Pinard
2000-09-08 22:40 ` Dave Love
2000-09-16 18:14 ` Florian Weimer
2000-09-18 14:07 ` Dave Love
2000-09-20 16:56 ` Florian Weimer
2000-09-20 19:26 ` Kai Großjohann
2000-11-11 16:35 ` Florian Weimer
2000-11-15 5:38 ` Karl Eichwalder
2000-11-27 13:40 ` François Pinard
2000-11-27 14:35 ` tick and backtick in unicode Alan Shutko
2000-11-27 16:56 ` François Pinard
2000-11-27 19:47 ` Karl Eichwalder
2000-11-27 20:57 ` Stainless Steel Rat
2000-11-28 6:01 ` François Pinard
2000-11-29 5:45 ` Karl Eichwalder
2000-11-30 1:57 ` Kai Großjohann
2000-11-30 4:19 ` Karl Eichwalder
2000-11-30 6:33 ` Graham Murray
2000-11-30 12:38 ` Per Abrahamsen
2000-11-30 11:23 ` Toby Speight
2000-09-21 19:33 ` \201 irritation! :-) Dave Love
2000-09-23 11:14 ` Florian Weimer
2000-09-25 11:55 ` Dave Love
2000-09-28 12:22 ` Florian Weimer
2000-09-29 19:18 ` QP encoding is now unibyte (was: " Florian Weimer
2000-10-03 23:17 ` Dave Love
2000-09-05 14:16 ` Dave Love
2000-09-06 14:49 ` François Pinard
2000-09-06 20:15 ` Kai Großjohann
2000-09-07 7:34 ` Yair Friedman (Jerusalem)
2000-09-08 9:31 ` Janne Rinta-Manty
2000-09-08 17:49 ` Simon Josefsson [this message]
2000-09-08 23:44 ` Dave Love
2000-09-12 8:51 ` Yair Friedman (Jerusalem)
2000-09-12 12:02 ` Kai Großjohann
2000-09-13 19:25 ` Dave Love
2000-09-14 7:49 ` Yair Friedman (Jerusalem)
2000-09-14 12:18 ` ShengHuo ZHU
2000-09-14 21:50 ` Dave Love
2000-09-14 23:06 ` ShengHuo ZHU
2000-09-18 13:51 ` Dave Love
2000-09-18 14:39 ` ShengHuo ZHU
2000-09-22 14:23 ` Dave Love
2000-09-14 21:42 ` Dave Love
2000-09-15 3:29 ` ShengHuo ZHU
2000-09-20 9:34 ` Yair Friedman (Jerusalem)
2000-09-20 13:06 ` ShengHuo ZHU
2000-09-20 14:55 ` Yair Friedman (Jerusalem)
2000-09-20 14:16 ` ShengHuo ZHU
2000-09-21 8:35 ` Yair Friedman (Jerusalem)
2000-09-21 19:02 ` Dave Love
2000-09-23 6:35 ` Karl Eichwalder
2000-09-25 11:33 ` Dave Love
2000-09-25 18:50 ` Karl Eichwalder
2000-09-27 21:56 ` Dave Love
2000-09-08 22:33 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=iluzoliu62s.fsf@barbar.josefsson.org \
--to=simon@josefsson.org \
--cc=ding@gnus.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.
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).