Bug 146346 - ISO-8895-1 HTML attachments are displayed as UTF-8
Summary: ISO-8895-1 HTML attachments are displayed as UTF-8
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: messageviewer (show other bugs)
Version: 1.9.6
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-04 11:54 UTC by Marco Costantini
Modified: 2015-04-12 10:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
example (2.25 KB, application/mbox)
2007-06-06 00:24 UTC, Marco Costantini
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Costantini 2007-06-04 11:54:02 UTC
Version:           1.9.6 (using KDE 3.5.6, Kubuntu (feisty) 4:3.5.6-0ubuntu14)
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.17-10-generic

ISO-8895-1 HTML attachments, for instance starting as

<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Barzellette</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<style type="text/css">

are displayed as UTF-8. Is I save the attachment, and see it with konqueror, it is displayed correctly.
Comment 1 Marco Costantini 2007-06-04 12:00:55 UTC
This happens with Kubuntu, which uses UTF-8.
Comment 2 Thomas McGuire 2007-06-05 22:32:56 UTC
Please attach such a message.
Comment 3 Marco Costantini 2007-06-06 00:24:39 UTC
Created attachment 20786 [details]
example
Comment 4 Josh Berry 2009-04-05 21:29:50 UTC
Hi,

I looked at the email you attached, and it does not correctly specify the character set in the Content-Type mail header.  The sender must set the charset in the mail header, otherwise KMail will fall back on the default encoding (which is UTF-8 for you).  It's not enough to specify it in the HTML header.

That said, there's definitely some room for improvement in how KMail handles this -- I'll forward to the KMail devs and see what they think.  Perhaps if KMail doesn't find an appropriate charset in the Content-Type header, it can fall back on the HTML before trying the system default.

But for maximum compatibility, the sender should still set the charset in the Content-Type header.

Thanks,
Josh (BugSquad)
Comment 5 Björn Ruberg 2010-01-07 02:38:00 UTC
Is this still an issue?
Comment 6 Laurent Montel 2015-04-12 10:25:42 UTC
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.