Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Balker Rasmussen <lbr@mjolner.dk>
Subject: Re: Charset problem when using agent in Pterodactyl Gnus 0.27
Date: 16 Sep 1998 11:27:22 +0200	[thread overview]
Message-ID: <0fsohspfut.fsf@fenris.mjolner.dk> (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:
> Sorry for not having tested on a newer version. I am currently working 
> offline due to bandwidth restrictions. Please ignore if already fixed.
> I am using GNU Emacs 20.3
> 
> I have observed two problems when using agent:
> 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.
> 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.
> 
> You can probably see the result in this post.

Yep, I have reported this too (I think :-) ).

Also, I had some problems with a newsserver this morning, where it hung
when I tried to post an article while plugged (precisely because of the
font problem).  After Ctrl-G'ing frantically, it eventually got unhung,
and I tried reposting, same result.  Third time lucky, and I enter the
group only to my horror to see three identical articles by yours truly.

Funny thing is that the articles which had hung are marked has CT
us-ascii, and the article that didn't hang has CT iso-8859-1.
-- 
Lars Balker Rasmussen, Software Engineer, Mjolner Informatics ApS
lbr@mjolner.dk


  reply	other threads:[~1998-09-16  9:27 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 [this message]
1998-09-16 10:07 ` Lars Magne Ingebrigtsen
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=0fsohspfut.fsf@fenris.mjolner.dk \
    --to=lbr@mjolner.dk \
    /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).