[Bug 793231] New: GIMP "save as" no longer allows usual image formats (PNG JPEG etc.) other than XCF; must use "Export"
https://bugzilla.novell.com/show_bug.cgi?id=793231 https://bugzilla.novell.com/show_bug.cgi?id=793231#c0 Summary: GIMP "save as" no longer allows usual image formats (PNG JPEG etc.) other than XCF; must use "Export" Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: me@kalenz.eu QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Firefox/17.0 It used to be possible to open an image file (e.g.: JPEG, PNG) in GIMP, edit, then "save" (to the same name, in the same format), or "save as" (new name, same format, or new format). At present (GIMP 2.8.0 on KDE4) it is no longer possible to handle the usual image formats, such as JPEG and PNG, through the "Save" and "Save As" functions. These functions only allow the XCF format. To save an image as JPEG or PNG, the "Export" function must be used, even if saving in the same format as the originally opened image. When closing the image, even if it has just been "exported", the warning dialogue appears: "IMG_0001 has not been saved. All modifications of the past 3 minutes will be lost! Close without saving?" which is complete nonsense because the image was just "exported" so there is no loss of data on closing (other than restrictions imposed by the chosen output format). It seems clear that this is an upstream decision to "encourage" (/coerce?) users to use the XCF format. Which, let's be honest, nobody uses. In applications like web design and photography, GIMP is used routinely to edit JPEG and PNG files, which are the predominant formats for lossy and lossless image data, respectively. The insistence on "Export" and the nagging dialogues seriously reduce productivity, and increase accidental mis-saving or non-saving of images. Regardless of upstream choices, I strongly feel that openSUSE should choose for maximum flexibility, freedom of choice, and productivity (which I believe is the general spirit, anyway). As such, I suggest you return to the previous style, where the "Save As" dialogue allowed all supported image formats, and the "Save" function simply overwrites the same file in the same format. Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=793231 https://bugzilla.novell.com/show_bug.cgi?id=793231#c Jiaying ren <jren@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jren@suse.com AssignedTo|bnc-team-screening@forge.pr |bnc-team-gnome@forge.provo. |ovo.novell.com |novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=793231 https://bugzilla.novell.com/show_bug.cgi?id=793231#c1 David Liang <dliang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dliang@suse.com --- Comment #1 from David Liang <dliang@suse.com> 2012-12-11 10:15:17 UTC --- +1 very annoying change to me. at least, an original file format should be listed even set to default when we choose 'Save' or 'Save as'. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=793231 https://bugzilla.novell.com/show_bug.cgi?id=793231#c2 Vincent Untz <vuntz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |vuntz@suse.com See Also| |https://bugzilla.gnome.org/ | |show_bug.cgi?id=688849 Resolution| |UPSTREAM --- Comment #2 from Vincent Untz <vuntz@suse.com> 2012-12-11 10:28:35 UTC --- This is really an upstream change in gimp, and nothing openSUSE can control. This was mentioned in the 2.8 release notes, see http://www.gimp.org/release-notes/gimp-2.8.html See this upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=688849 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=793231 https://bugzilla.novell.com/show_bug.cgi?id=793231#c3 --- Comment #3 from Kalenz . <me@kalenz.eu> 2012-12-11 13:11:45 UTC --- Since when do upstream policy choices override openSUSE policy? Whatever GIMP developers decide, users will want openSUSE to remain a versatile, easy-to-use system. Surely it is within the power of openSUSE GIMP packagers to change this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=793231 https://bugzilla.novell.com/show_bug.cgi?id=793231#c4 --- Comment #4 from Vincent Untz <vuntz@suse.com> 2012-12-11 13:24:08 UTC --- (In reply to comment #3)
Since when do upstream policy choices override openSUSE policy?
Whatever GIMP developers decide, users will want openSUSE to remain a versatile, easy-to-use system.
Surely it is within the power of openSUSE GIMP packagers to change this?
Oh, sure, we can. But I don't want to, and I'm pretty sure everybody else working on the GIMP package agrees. I don't feel it's important enough to have a patch that we'll have to maintain forever, and that will conflict with all the GIMP documentation. FWIW, I'm using GIMP too, and I got used pretty quickly to the export feature. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com