GNOME Bugzilla – Bug 723153
JPG export - don't select progressive by default
Last modified: 2014-09-29 19:49:52 UTC
Please make the default for JPG export options to have the "Progressive" option not selected. It seems to be causing a constant stream of requests for help as progressive mode isn't universally supported, especially on embedded systems (TVs etc)
> It seems to be causing a constant stream of requests for help Where?
Here's a few examples: http://gimpforums.com/thread-2-8-jpg-and-png-files-not-recognized http://gimpforums.com/thread-jpeg-exports-not-recognized-by-windows http://gimpforums.com/thread-images-not-displaying-in-mobile-after-editing-with-gimp-2-8 http://gimpchat.com/viewtopic.php?f=8&t=6616&p=82686 https://mail.gnome.org/archives/gimp-user-list/2014-January/msg00178.html
*** Bug 730773 has been marked as a duplicate of this bug. ***
There was someone in #gimp who asked about how to get started in fixing this issue (it's marked as a GNOME Love bug). Just reverting commit 4b3a1c6680ba6890b5b35fb8ba6e3e46e7257097 should be enough to bring back the old behaviour.
What we should do there: more aggressively communicating that - GIMP uses progressive by default, and - people should contact the manufacturers of devices that don't support it Those "hey, we can save 5c per unit"-manufacturers won't suddenly add support on their own.
Created attachment 287241 [details] [review] A patch to solve bug #723153
Mukund: I tried to revert that commit but while applying other commits over it after removing that commit caused a few errors. So I saw the changes that were made in commit 4b3a1c6680ba6890b5b35fb8ba6e3e46e7257097 and added the above patch after reverting those changes. Its just a single line change from TRUE to FALSE :D
(In reply to comment #7) > Mukund: I tried to revert that commit but while applying other commits over it > after removing that commit caused a few errors. So I saw the changes that were > made in commit 4b3a1c6680ba6890b5b35fb8ba6e3e46e7257097 and added the above > patch after reverting those changes. Its just a single line change from TRUE to > FALSE :D After talking to other developers, it seems we'll not be reverting this change, i.e., progressive will continue to be the default setting.
Oh.. (In reply to comment #8) > (In reply to comment #7) > > Mukund: I tried to revert that commit but while applying other commits over it > > after removing that commit caused a few errors. So I saw the changes that were > > made in commit 4b3a1c6680ba6890b5b35fb8ba6e3e46e7257097 and added the above > > patch after reverting those changes. Its just a single line change from TRUE to > > FALSE :D > > After talking to other developers, it seems we'll not be reverting this change, > i.e., progressive will continue to be the default setting. Oh.. okay. :(
If there has been a decision not to act on this bug please close it with a suitable comment so that it can be referred to every time someone comes along with this problem in future.
Indeed.