Bug 103410 - Bad charset in printed message.
Summary: Bad charset in printed message.
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.8
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-07 10:01 UTC by Andrey Cherepanov
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Cherepanov 2005-04-07 10:01:24 UTC
Version:           1.8 (using KDE 3.4.0, compiled sources)
Compiler:          gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
OS:                Linux (i686) release 2.4.26-01-NeTraverse-i686-SMP-64GB

I use Unicode TTF fonts both for show and print messages from KMail. Print works fine in early version of KDE. Now I install KDE 3.4.0 and can see russian messages correctly, but printout is broken - there are umlault instead cyrillic letters. Possible, HTML for printout has not apropriate charset.
Comment 1 Andrey Cherepanov 2005-04-07 11:42:17 UTC
Oh! This is kdeprint subsystem from KDE 3.4. bug!

There is line from KMail log:
kdeprint: kde-fonts = AvantGarde-Book,AvantGarde-BookOblique,AvantGarde-Demi,AvantGarde-DemiOblique,Bookman-Demi,Bookman-DemiItalic,Bookman-Light,Bookman-LightItalic,Courier,Courier-Bold,Courier-BoldOblique,Courier-Oblique,Helvetica,Helvetica-Bold,Helvetica-BoldOblique,Helvetica-Narrow,Helvetica-Narrow-Bold,Helvetica-Narrow-BoldOblique,Helvetica-Narrow-Oblique,Helvetica-Oblique,NewCenturySchlbk-Bold,NewCenturySchlbk-BoldItalic,NewCenturySchlbk-Italic,NewCenturySchlbk-Roman,Palatino-Bold,Palatino-BoldItalic,Palatino-Italic,Palatino-Roman,Symbol,Times-Bold,Times-BoldItalic,Times-Italic,Times-Roman,ZapfChancery-MediumItalic,ZapfDingbats

All my TTF fonts disappeared from this list. In KDE 3.3.2 all TTF fonts are used for display and prining without any problem.

I get warning during kdebase ./configure about FreeType 2.x  absence (but freetype was insatalled). I will try to rebuild fresh freetype.
Comment 2 Andrey Cherepanov 2005-04-07 14:36:55 UTC
Oops! It's KMail specific bug. All other application print cyrillic well. And in KMail header and attachment names with cyrillic letters print correct. It seems problem is in decode MIME parts and print them.
Comment 3 Andrey Cherepanov 2005-04-08 10:05:09 UTC
There is a problem of overriding charset of MIME part on print. This is occured only for print, on show part charset doesn't overrided. Please, commit followed patch or remove charset overriding for printing.

Patch:
--- kdepim-3.4.0/kmail/old/objecttreeparser.cpp 2005-04-08 12:01:28.000000000 +0400
+++ kdepim-3.4.0/kmail/objecttreeparser.cpp     2005-04-08 12:00:58.000000000 +0400
@@ -2507,8 +2507,6 @@

   const QTextCodec * ObjectTreeParser::codecFor( partNode * node ) const {
     assert( node );
-    if ( mReader && mReader->overrideCodec() )
-      return mReader->overrideCodec();
     return node->msgPart().codec();
   }
Comment 4 Andrey Cherepanov 2005-05-13 10:05:05 UTC
Oops! My last patch break changing charset in preview, but fix on printing. I work at correct patch...
Comment 5 Andrey Cherepanov 2005-06-02 11:08:40 UTC
Fixed in KDE 3.4.1.
Comment 6 Gilles Schintgen 2005-06-02 14:58:25 UTC
On Thursday 02 June 2005 11:08, Andrey Cherepanov wrote:
> Fixed in KDE 3.4.1.

No, not really. I really appreciate that you're working on this. I've just 
upgraded kdelibs and kdepim to 3.4.1. Unfortunately KMail still doesn't get 
it right :-(
I just tested this with an UTF-8 encoded mail I sent. The utf-8 content is 
incorrectly decoded as ISO-8859-1. In other words, exactly the same behavior 
as in 3.4.0.

Thanks again for working on this!
Comment 7 Andrey Cherepanov 2005-06-02 15:02:32 UTC
Ok! This bug is still alive. I continue my work over patch for this bug.
Comment 8 Gilles Schintgen 2006-04-09 12:22:05 UTC
Apparently everything's fine in KDE 3.5.0. Thanks a lot!

I'd say this bug is FIXED.
Comment 9 Philip Rodrigues 2006-04-09 18:44:06 UTC
if you say so :-)