From: Simon Josefsson <jas@pdc.kth.se>
Cc: Gnus Mailing List <ding@gnus.org>
Subject: Re: [Tony Graham <tgraham@mulberrytech.com>] Re: XT: I/O of iso-8859-1 characters?
Date: 13 Aug 1999 13:34:55 +0200 [thread overview]
Message-ID: <iluvhajdicg.fsf@badis.pdc.kth.se> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "13 Aug 1999 12:32:22 +0200"
Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
> The following message wasn't decoded properly when I saw it on the XSL
> mailing list. Wonder why? The MIME tags seem to be correct.
The list server appended a string (non-MIME-ish) to the article which
break base64 encoding. I see this quite often, perhaps base64-decode-*
could have a parameter to make it return what has been decoded (and
update the buffer) when it fails, instead of just aborting the
decoding and return nil. A patch looks pretty straightforward.
(One could fix the mailing list software too :-))
next prev parent reply other threads:[~1999-08-13 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-13 10:32 Kai Großjohann
1999-08-13 11:34 ` Simon Josefsson [this message]
1999-09-24 18:09 ` Lars Magne Ingebrigtsen
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=iluvhajdicg.fsf@badis.pdc.kth.se \
--to=jas@pdc.kth.se \
--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).