Version: 0.9.91 (using KDE 3.4.91 (beta1, >= 20050910) Level "a" , SUSE 10.0.42) Compiler: Target: i586-suse-linux OS: Linux (i686) release 2.6.13.2-2-default I´ve subscribed to a german news server. Now the specia german characters ("umlauts") aren´t displayed correctly in the messages. They look like two rectangles.
Do you have set View -> Charset to 'Automatic'? If yes, the message most likely contains a wrong Content-Type header. Could you paste the source (View -> View Source) of such an article here?
That´s the source. I read on another bug report that it occurs with Outlook Express users. Path: news.h3.stusta.mhn.de!not-for-mail From: "Zonk" <Zonk1982@wolke7.net> Newsgroups: local.allerlei Subject: Felge für Fahrrad Date: Tue, 11 Oct 2005 15:21:24 +0200 Organization: StuStaNet e.V. Lines: 11 Message-ID: <dige95$oad$1@neu-gesine.stusta.mhn.de> NNTP-Posting-Host: r064064.stusta.swh.mhn.de X-Trace: neu-gesine.stusta.mhn.de 1129036901 24909 10.150.64.64 (11 Oct 2005 13:21:41 GMT) X-Complaints-To: usenet@news.h3.stusta.mhn.de NNTP-Posting-Date: 11 Oct 2005 13:21:41 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Xref: news.h3.stusta.mhn.de local.allerlei:32751 Ich hatte einen kleinen aber spektakulären Unfall mit dem Rad. Unter anderem sieht die vordere Felge aus wie ein großer Knoten und ich bräuchte Ersatz. Falls irgendwo noch ein halbwegs intaktes 28 Zoll Vorderrad günstig abzugeben wäre.... bitte melden. lg Johann
Well, there isn't even a Content-Type header, so there is no way of determining the correct encoding. The best thing you can do for now is manually changing the encoding (probably ISO-8859-15 in this case). The only possible 'fix' for this problem in KNode would be to implement a configurable fallback encoding for these cases (I think KMail has something like this).
This would be great sicne I don´t want to set the encoding for every message I receive. And because many users are using Outlook Express, this does mattter IMHO.
I agree, this would be great. Many messages in common groups have foreign characters in subject and / or sender, and if Outlook Express sent them, odds are that no Content-type header was specified. That also means that such characters are shown as "empty" in the Article List, which doesn't look very nice.
KNode is behaving just like KMail: it decodes the message as "locale encoding" when no encoding is given. It just so happens that on Linux we're all moving to UTF-8 locales instead of Latin 1 or Latin 9 (ISO-8859-15). Hence, "ü" is represented by two bytes, and the single-byte 0xFC doesn't mean anything. That's why you see two squares.
kmail has an option to define a fallback character encoding, which seems to be not possible in knode. Changing to wish.
Should be set to "resolved" and closed.
SVN commit 966237 by otrichet: Try to properly decode 8bit string coming from XOVER listing - Use the default charset of the group (or the global posting charset -- need to add a global default reading charset --) to decode 8bit data (From and Subject). This restore the behaviour from KDE3 - The from and subject line in the message view should also be fine when the message is not what we usually expect. This needs that either the global charset or the charset of the group to be defined to the local legacy encoding to do something usefull. Viva UTF-8. BUG: 85473 BUG: 114898 BUG: 179703 BUG: 188783 BUG: 114199 BUG: 163114 M +12 -2 knarticle.cpp M +16 -8 kngroup.cpp M +34 -2 utils/locale.cpp M +34 -3 utils/locale.h WebSVN link: http://websvn.kde.org/?view=rev&revision=966237