Bug 287945 - special html chars displayed incorrectly
Summary: special html chars displayed incorrectly
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.7
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-30 21:34 UTC by Danjel Jungersen
Modified: 2016-09-26 17:36 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Danjel Jungersen 2011-11-30 21:34:09 UTC 
Version:           4.7 (using KDE 4.7.2) 
OS:                Linux

When viewing an html email, containing for instance a "å" (å) character, it displays "& #229;" instead of "å", if the code is broken by a linebreak.
The character is used several time in the same email, all displayed correctly, only 1 is bad.
If I check the source the line ends with "&", and the next line starts with "#229;"

Reproducible: Always

Steps to Reproduce:
Have only seen it a few times, but all cases are containing linebreaks

Actual Results:  
It displays "& #229;"

Expected Results:  
Should have displayed "å"

OS: Linux (x86_64) release 3.0.0-13-generic
Compiler: gcc
Comment 1 Laurent Montel 2011-12-01 09:01:18 UTC 
could you send in private this email please ?
(perhaps it's a webkit problem don't know)
Comment 2 Torgny Nyblom 2011-12-01 11:02:56 UTC 
Probably related to the soft line break feature.
Either the split is done with a hard line break -> Sender is broken
Or we fail to reassemble -> Viewer is broken
(Or both :))
Comment 3 Denis Kurz 2016-09-24 18:02:38 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 4 Danjel Jungersen 2016-09-26 06:32:13 UTC 
Have not seen it for awhile....
//Danjel
Comment 5 Denis Kurz 2016-09-26 17:36:33 UTC 
Danjel, thanks for the feedback.