Bug 184443 - Digikam save as "JPEG" appends a ".JPEG" file extension. Bad!
Summary: Digikam save as "JPEG" appends a ".JPEG" file extension. Bad!
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-DImg-JPEG (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-15 20:08 UTC by Joe Biden
Modified: 2018-08-19 17:19 UTC (History)
4 users (show)

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


Attachments
An attachment of the issue (191.75 KB, image/png)
2009-02-15 20:14 UTC, Joe Biden
Details
KColorPaint saveas file dialog... (376.85 KB, image/png)
2009-02-15 20:27 UTC, caulier.gilles
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Biden 2009-02-15 20:08:01 UTC
Version:           0.10.0-rc2 (using 4.2.00 (KDE 4.2.0), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.27-11-generic

See attached screenshot. Please, let's not geek out and use the "proper" extension, but let's use the "99% of the world" extension...JPG, not JPEG.
Comment 1 caulier.gilles 2009-02-15 20:14:12 UTC
As you can see in wikipedia page '.jpeg" is fine.

http://en.wikipedia.org/wiki/Jpeg

Also, this file extension is provided by KFileSaveDialog, not digiKam. It's relevant of KDELibs...

Gilles Caulier
Comment 2 Joe Biden 2009-02-15 20:14:46 UTC
Created attachment 31339 [details]
An attachment of the issue
Comment 3 Joe Biden 2009-02-15 20:19:06 UTC
I didn't say anything about it being proper or fine. I just said that it wasn't what most people say or use, so it's going to cause lots of trouble. I am actually going to patch it myself, because this will cause insane problems with the rest of my workflow, since I automate a lot of it.

Comment 4 Joe Biden 2009-02-15 20:20:15 UTC
Also, it's new behavior for no real reason. If people were screaming for the .jpeg extension, it should be configurable. Otherwise, it's just going to cause trouble because someone thinks it's more "proper" or something.
Comment 5 caulier.gilles 2009-02-15 20:22:10 UTC
No. new configuration for standard file extension will _bloat_ settings...

Gilles Caulier
Comment 6 caulier.gilles 2009-02-15 20:27:21 UTC
Created attachment 31342 [details]
KColorPaint saveas file dialog...

Same problem with KColorPaint... I confirm: it's KDELibs problem...

Gilles Caulier
Comment 7 Joe Biden 2009-02-15 20:29:21 UTC
Well, this is a regression. New behavior just for some guys idea of what is more "right" is foolishness. Ugh, so to KDElibs I go, I guess.
Comment 8 Andreas Hartmetz 2009-04-09 17:46:11 UTC
The idea is that the extension .jpeg is indeed more right because it matches the name of the format. UNIX-ish filesystems don't know the concept of filename extensions, they just happen to allow dots in the name.
So, while I'm not the one who implemented it this way, I think it's a feature.
Is there any problem in practice?
Comment 9 Joe Biden 2009-04-09 18:16:28 UTC
Yes, it's a problem.

Lots of programs do not look for .jpeg, only for .jpg. The backup scripts for my NAS don't see them. 

It's also a change with no real benefit, so it's a change, just to have a change. Are any other large systems magically switching over to .jpeg in the middle of a semi-stable release? No! To break things for the user for no reason is not a good plan because someone things it's "more proper", even though on the wiki page, they are interchangeable, so let's just stick with the one that has been used for oh, two decades, thanks?
Comment 10 Dario Andres 2009-05-20 21:35:35 UTC
This seems related to bug 176737. (which includes a patch to use "jpg" as default instead of "jpeg"). Thanks!
Comment 11 Joe Biden 2009-05-20 21:44:23 UTC
Furthermore, this changes my perfectly-good filenames of .jpg to .jpeg, overriding my choice! I have to change the extension back every time. This is ridiculous!
Comment 12 Dario Andres 2009-06-15 22:35:28 UTC
In a similar KolourPaint bug I applied a behaviour-patch: bug 193339. I don't know if this can be applied here too.
Thanks
Comment 13 Christoph Feck 2010-08-31 05:15:09 UTC

*** This bug has been marked as a duplicate of bug 176737 ***
Comment 14 caulier.gilles 2018-08-19 17:19:44 UTC
Not reproducible with 6.0.0