| Summary: | Digikam save as "JPEG" appends a ".JPEG" file extension. Bad! | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Joe Biden <mailinglist> |
| Component: | Plugin-DImg-JPEG | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ahartmetz, andresbajotierra, caulier.gilles, mailinglist |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 6.0.0 | |
| Sentry Crash Report: | |||
| Attachments: |
An attachment of the issue
KColorPaint saveas file dialog... |
||
|
Description
Joe Biden
2009-02-15 20:08:01 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 Created attachment 31339 [details]
An attachment of the issue
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. 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. No. new configuration for standard file extension will _bloat_ settings... Gilles Caulier Created attachment 31342 [details]
KColorPaint saveas file dialog...
Same problem with KColorPaint... I confirm: it's KDELibs problem...
Gilles Caulier
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. 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? 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? This seems related to bug 176737. (which includes a patch to use "jpg" as default instead of "jpeg"). Thanks! 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! In a similar KolourPaint bug I applied a behaviour-patch: bug 193339. I don't know if this can be applied here too. Thanks *** This bug has been marked as a duplicate of bug 176737 *** Not reproducible with 6.0.0 |