From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: 0.48 doesn't encode my jpegs
Date: 16 Nov 1998 16:01:43 +0100 [thread overview]
Message-ID: <m3lnlbvfzc.fsf@sparky.gnus.org> (raw)
In-Reply-To: Lee Willis's message of "16 Nov 1998 13:17:59 +0000"
Lee Willis <lee@gbdirect.co.uk> writes:
> I've edbugged the source briefly, it seems to recognize that it should
> be base64 but then doesn't do it for some reason ...
This may be a uni/multibyte problem. 0.49 might fix it.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-11-16 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-16 13:17 Lee Willis
1998-11-16 13:23 ` Steinar Bang
1998-11-16 13:27 ` Lee Willis
1998-11-16 15:01 ` Lars Magne Ingebrigtsen [this message]
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=m3lnlbvfzc.fsf@sparky.gnus.org \
--to=larsi@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).