Bug 318471 - Image quality sucks and 'do not convert' option is missing
Summary: Image quality sucks and 'do not convert' option is missing
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: 4.10
Platform: Debian unstable Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-16 23:39 UTC by Josef Kufner
Modified: 2017-01-07 21:31 UTC (History)
1 user (show)

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


Attachments
Example of source and result photo (899.33 KB, image/png)
2013-04-16 23:43 UTC, Josef Kufner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Josef Kufner 2013-04-16 23:39:27 UTC
Hello,
when assigning a photo to a contact, KAddresBook converts image to JPG of some max resolution. Problem is, that result image is badly damaged. Quality of the result image should be set to a significantly higher level and there should be option to store image as-is with no conversion at all.

I have nice photos for my contacts prepared (and optimized to reasonable size) but KAddressBook makes them ugly :(


Reproducible: Always

Steps to Reproduce:
1. Attach nice big photo.
Actual Results:  
Ugly photo is attached.

Expected Results:  
Nice big photo is attached.
Comment 1 Josef Kufner 2013-04-16 23:43:13 UTC
Created attachment 78973 [details]
Example of source and result photo

Left half is part of original photo. Right half is the ugly result. There was no modification (no jpeg re-compression, no resize) except cuting and pasting.
Comment 2 Denis Kurz 2016-09-24 20:52:43 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 kaddressbook (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 21:31:23 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.