Bug 311105 - Crippled printing: KMail treats text emails as graphics - horizontally cut lines at page ends
Summary: Crippled printing: KMail treats text emails as graphics - horizontally cut li...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: 4.9.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-03 19:23 UTC by csbugs
Modified: 2017-01-07 22:51 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 csbugs 2012-12-03 19:23:23 UTC
Apparantly kmail treats emails as some kind of graphics or something, at least the printing dialog is not one I would expext in a text based application (like f.x. KWrite).

Due to this, the last text line in prints is split *horizontally*. This makes reading sometimes really hard.

Since the last few options to use KDE3 in a reasonable way are fading now, I will have to migrate my small enterprise (~15 people) to KDE 4 soon. They will not be amused to have to cope with this crippled functionality.

Reproducible: Always

Steps to Reproduce:
1. Print an email from KMail which is more than one page long
2. 
3.
Actual Results:  
In most cases, the page is cut where the page margin ends - and be it the vertical middle of a line of text

Expected Results:  
The page is split *between* two lines of text.
Comment 1 Denis Kurz 2016-09-24 18:08:12 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 2 Denis Kurz 2017-01-07 22:51:06 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.