GNOME Bugzilla – Bug 89453
Failure to follow-up to articles with 8-bit headers
Last modified: 2009-08-15 18:40:50 UTC
Pan (0.12 fix from CVS at 20020727) is not able to send a follow-up to messages with 8-bit headers. When I follow-up to such article and try to send it later on, I get the following message: ERROR: message uses characters not specified in charset 'ISO-8859-1' - possibly use '(null)' instead? My guess is that Pan should send that message with the default encoding and forget the rest :-) Here is my pan.sendlater.mbox file: ----------------8>----------------------- From sgm@voornaamachternaam.nl Tue Jul 30 21:10:10 2002 Subject: Re: wat voor motor From: "Bas Mevissen" <sgm@voornaamachternaam.nl> Date: Tue, 30 Jul 2002 21:10:10 +0200 Message-Id: <pan.2002.07.30.19.10.10.445212.20629@voornaamachternaam.nl> References: <Aci%8.4677$6O6.430250@zonnet-reader-1> <ahkc6i$jqj$1@reader1.tiscali.nl> <ahkf8o$ogg$3@sokrates.r1> <ahkihk$of0$1@reader1.tiscali.nl> <ahkmfl$uob$5@sokrates.r1> <ahlpog$9i3$1@reader1.tiscali.nl> <ahlto1$v9c$5@sokrates.r1> <Xns92558D6B24139Sander@216.168.3.40> <ahm5n1$6kh$2@sokrates.r1> X-Comment-To: "Bonzo ²ºº²" <Suffie@xt5000.demon Newsgroups: nl.motorfiets Pan-Reverse-Path: sgm@voornaamachternaam.nl Pan-Charset: ISO-8859-1 Pan-Server: Euronet Pan-Attribution: On Wed, 24 Jul 2002 14:18:41 +0200, Bonzo ²ºº² wrote: Status: O On Wed, 24 Jul 2002 14:18:41 +0200, Bonzo����� wrote: > > > Ja zeg, moet ik jou geloven Sander pasterkamp ? > > Nou ik denk er het mijne van... > > > > (-: Twee weken geleden een tweedehands K 100 gekocht, m'n eerste motor. Bevalt > (-: uitstekend tot nog toe. Wat hebben jullie tegen BMW? > > Dat het gewoon teveel geold kost, da's meestal het enige echte argument. Waarbij je nog kunt gaan beargumenteren of het te duur is of te veel geld.. Bas. ----------------8>-----------------------------
0.12 branch is probably complete, so bumping these for investigation in 0.13.1
Bas wrote in mail: > Please fix it in 0.12! It keeps me from having a usable pan > right now :-( Someone posted a patch already. I'll try it > and let you know. I don't know what patch you're referring to. I'm trying to get 0.13.0 out in the next week or so; please upgrade to 0.12.92 and see if following up to 8bit messages works there. There have been a lot of charset/8bit/etc. fixes in the 0.12.91 branch.
Holger Hoffstatte <holger@wizards.de> wrote in mail: Charles, I just found bug #89453 in bugzilla where you asked for confirmation with 0.13. I can confirm that follow-ups to 8-bit postings are still posted as UTF but wrongly labeled as latin1 with 0.13 (RH 7.3 rpm). I tried to confirm this via bugzilla but could not find a way to do this? In my case, the posting I followed up to was: http://groups.google.com/groups?selm=alj41n%24f0q%2405%241%40news.t-online.com&oe=UTF-8&output=gplain New postings in latin1 work just fine. regards Holger
Bumped remaining bugs to 0.13.2.
Bumped remaining bugs to 0.13.3.
chris: ping
Haven't had too much time to look into this, but so far I've been unable to reproduce this in 0.13.2.92. Tried following up to various source messages (quote-encoded, 8bit), but all of them were posted in the specified charset, not UTF-8. Will try to look more closely 2nd half of the week.
*** Bug 101010 has been marked as a duplicate of this bug. ***
Chris: in poking around Pan for #101074 (The show-all-headers X-Pan-Internal-CharSet bug), I found that X-Pan-Internal-CharSet is written in message-window.c::create_reply_window(), but not _read_ anywhere. http://cvs.gnome.org/bonsai/cvsblame.cgi?file=pan%2Fpan%2Fbase/article.h&rev=&root=/cvs/gnome Says that X-Pan-Internal-CharSet was added to "sync with pan-0-12-fix's changes for charsets in follow-ups." Is there some code from pan-0-12-fix that reads this variable that wasn't merged back in, and if so, could that be the cause of this problem?
charles: Setting X-Pan-Internal-CharSet is a brainfart on my part (one of many :)). I'm backing this out today.
bumping for 0.13.3 freeze.
Bas: do you still see this in 0.13.2.93?
Bas: ping.
as of 0.13.4 it looks like ok.
Didn't see the problem for some time now. So I guess it to be solved. Thanks for fixing!
Paperwork: moving to 0.13.4, since that's apparently when Chris fixed it. :)