From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Charset problem when using agent in Pterodactyl Gnus 0.27
Date: 16 Sep 1998 12:07:57 +0200 [thread overview]
Message-ID: <m3zpc0pdz6.fsf@sparky.gnus.org> (raw)
In-Reply-To: "Bjørn Mork"'s message of "Wed, 16 Sep 1998 09:02:45 GMT"
"Bjørn Mork" <bmork@dod.no> writes:
> 1) when I enter the nndraft:queue group I see those ugly \201's. If I edit
> one of the articles there, the \201 will temporarily go away in this
> article after reposting it.
You get \201's only in the queue group? I'm unable to reproduce this
bug.
> 2) when I post online, the Content-Type header is fine (iso-8859-1). In the
> agent queue the CT header is still fine. But when I look at my own
> posts after having uploaded them, the charset is suddenly changed to
> us-ascii. Weird.
I think I've located and fixed this bug. Could you check after
Pterodactyl Gnus v0.32 has been released to see whether things start
working?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-09-16 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-16 9:02 Bjørn Mork
1998-09-16 9:27 ` Lars Balker Rasmussen
1998-09-16 10:07 ` Lars Magne Ingebrigtsen [this message]
1998-09-24 16:08 ` Bjørn Mork
1998-09-29 10:15 ` 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=m3zpc0pdz6.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).