Bug 186496

Summary:	kmail and knode message subjects default encoding
Product:	[Unmaintained] kmail	Reporter:	g.veniamin
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	g.veniamin, nive, onyx
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	FreeBSD Ports
OS:	FreeBSD
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description g.veniamin 2009-03-07 23:03:03 UTC

Version:            (using KDE 4.2.0)
Compiler:          gcc FreeBSD/i386 system compiler version 4.2.1 20070719  [FreeBSD]  
OS:                FreeBSD
Installed from:    FreeBSD Ports

This is not a FreeBSD specific problem, and it is similar to
http://bugs.kde.org/show_bug.cgi?id=169411 bug. Last comments makes me think it
is not fixed in kde4.2.0
KNode and KMail problems (looks like ??????? instead of
characters in subject) with default encoding in message subject when the message
in different (many) encodings. Message body is ok, only subject is corrupted.
Many people confirmed bug starts from kde4.1. It seems to be in kcharsets.cpp, "ISO " must be replased with "ISO-".

Comment 1 Inge Wallin 2009-03-08 19:12:03 UTC

Not a kchart bug

Comment 2 g.veniamin 2009-03-08 20:04:54 UTC

Sorry for that. But it's also not a kmail bug, and not a knode bug - i think it is more systemwide. Encoding names should be written correctly.

Comment 3 g.veniamin 2009-03-08 21:22:23 UTC

Additional comment:
Some pictures for that bug
1. http://imagebin.ca/view/eXS59_71.html
KNode mainwindow with selected message. "?????" is a problem. As you see messages around selected have a normal koi8-r encoding in subject-they was imported form knode on kde3.5.10.

2. http://imagebin.ca/view/uzu9Mc.html The message source - comming directly from server. As see, subject encoding not defined in here, but it looks like it's something real, similar to message content (little down), koi8-r encoded in fact. But it's not "??????" for sure.

3. http://imagebin.ca/view/OTPdgiZ.html The message header (with descriptors and staff), stored on the disk, just after displaying message on the screen. It is a hexdump. As you can see, the series of 3f (code for "?" sign) is in left part of dump, and "?" signs in other side. It saves normal koi8-r encoded text to "??????" just because subject encoding not defined in the message and user unable to define the default one.

Comment 4 g.veniamin 2009-03-17 19:36:26 UTC

Please, make the default charset for message to be a default charset for message subject, if not specified! At least for knode (from kdepim).
Thanks in advance!

Comment 5 g.veniamin 2009-03-26 11:05:46 UTC

Dear Inge Wallin!
Please review this bug and make a comment, or fix, or delete bug report!

Comment 6 Pino Toscano 2009-03-26 11:08:27 UTC

(In reply to comment #5)
> Please review this bug and make a comment, or fix, or delete bug report!

Please be patient.

Comment 7 g.veniamin 2009-03-26 11:34:20 UTC

I found the same behavour in KHelpCenter in left panel:
http://imagebin.ca/view/y_K2dIpM.html

Comment 8 Dmitry Kolosov 2009-04-25 12:27:31 UTC

I can confirm that bug. Default encoding charset for message is not applied to message header, and if message header encoding is not specified directly, knode tries to display it in unicode (or what?) that looks like multiply '?' signs in non-unicode OS, such as Freebsd.

Comment 9 Dmitry Kolosov 2009-05-17 12:00:26 UTC

Why this bug is still unconfirmed? Somebody working on it?

Comment 10 Olivier Trichet 2009-05-17 13:33:16 UTC

This report has turned into a meta bug where most of the problems that are described should be fixed for KDE 4.3 ("ISO 8859-1" bug, subject encoding when none is used in original message, ...).
For this reason, I'm closing this report.

If you encounter any bug as of KDE 4.3, please open NEW reports.