Bug 236762

Summary: Messages that lack of charset are improperly displayed - there is no workaround
Product: knode Reporter: Arkadiusz Miskiewicz <arekm>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: knode and example message

Description Arkadiusz Miskiewicz 2010-05-07 21:23:27 UTC 
Version:            (using KDE 4.4.3)
OS:                Linux
Installed from:    Unlisted Binary Package

Some versions of Microsoft Outlook Express don't add charset information even if user enters non-ascii characters.

This is very common here in Poland (and likely other countries where non ascii/latin1 is used by default).

Example message (real) attached. You should find it on google news via message-id for example.

The fix (aka workaround for such common stupidity of outlook express) should be easy - allow to specify custom charset for messages that lack proper charset headers.

Path: news.onet.pl!news.nask.pl!news.nask.org.pl!newsfeed.pionier.net.pl!news.e-wro.pl!not-for-mail
From: "PW" <camden@pop.wytnijto.e-wro.pl>
Newsgroups: pl.pregierz
Subject: Po¿ytecznych idiotów
Date: Fri, 7 May 2010 01:50:28 +0200
Organization: Miejskie Sieci Informatyczne e-wro
Lines: 35
Message-ID: <hrvkjr$rk3$1@atena.e-wro.net>
Reply-To: "PW" <camden@pop.wytnijto.e-wro.pl>
NNTP-Posting-Host: h82-143-133-125-static.e-wro.net.pl
X-Trace: atena.e-wro.net 1273189819 28291 82.143.133.125 (6 May 2010 23:50:19 GMT)
X-Complaints-To: abuse@e-wro.pl
NNTP-Posting-Date: Thu, 6 May 2010 23:50:19 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Original
Xref: news.onet.pl pl.pregierz:1051244
Comment 1 Arkadiusz Miskiewicz 2010-05-07 21:25:27 UTC 
Created attachment 43353 [details]
knode and example message
Comment 2 Olivier Trichet 2010-05-24 17:57:29 UTC 
Hello,

you can force a charset as a fallback in the property of each group.
If no charset is set for a group, the charset specified in the "posting" section of the main settings is used.
Comment 3 Arkadiusz Miskiewicz 2010-05-24 18:44:19 UTC 
Riiight but the number of pl.* groups is over 200, so setting these per group is a very bad user experience.

I found out the second solution back then and accepted it for now becuse being 20-century and sending in iso8859-2 isn't worse experience than being 21-century by sending in utf-8 but seeing "improperly" displayed characters.

I hope that fallback setting for reading will be separated from fallback setting for posting in future knode versions.
Comment 4 Andrew Crouthamel 2018-09-04 18:34:19 UTC 
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.