[Digikam-devel] [Bug 118539] wish: lossless image-editor for JPEGs

[Sebastian Roeder]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=118539         




------- Additional Comments From sebastian.roeder uni-bielefeld de  2006-03-24 13:05 -------
I agree with Gilles as far as the the handbook thing goes. It can NOT be the task of a Save Dialog to inform a user about all the details in image file formats. It's only task is to make thinks transparent to the user as MArcel wrote above and I mentioned allready, too. In this case it seems important for me that the terms "lossy" and "lossless" appear on a reasonable place in the dialogues so the user should understand at the first look which file formats are lossy and which are not. But flashing warning messages everytime I save as jpg would just be a pain.

When the user sees in the interface that there are lossy and lossless file formats and he dosn't know what that means, then it is HIS task to search for the background knowledge (read a photoshop book, look at the digikam manual, search the net). You can not put all that infos in the save dialogue.

The help button that brings you to the right section in the handbook is a bonus (most commercial WIN software doesn't have it) but it's a good thing (TM) and easy to archive from the devels perspective. So it will be there once somebody (me?) wrote a good section about file formats in the handbook.

I will wait what changes are done to the save dialogue in 0.9 as Gilles recommented and then we can collect ideas on this problem again.

As far as the save as thing goes, I agree with you, this should be fixed to a real "save as". Please fill a seperate bug report for it. Thanks!

P.S. Regarding file formats I find it important which metadata types are supported by eacg, too. This is exspecially important for backups that you might use with other apps from the WIN world (like photoshop). I would not use PNG at that time cause the metadata can not be read by other apps.