Bug 138575 - Custom file renaming has to *long* (6 digest) auto suffix like photo-000001.jpg
Summary: Custom file renaming has to *long* (6 digest) auto suffix like photo-000001.jpg
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: AdvancedRename-Import (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-09 10:31 UTC by sero4linux
Modified: 2022-01-27 16:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sero4linux 2006-12-09 10:31:12 UTC
Version:           0.9rc1 (using KDE KDE 3.5.5)
Installed from:    Gentoo Packages
OS:                Linux

In the use case of digikam that I can find here at home (my parents using it for their photo management on an merely amateurish level), the six digest suffix when using custom renaming in Camera UI (by providing a certain prefix) is much to long. I's say in most cases an album does have less then 100 photos in it - so *-001.jpg would be much better then *-000001.jpg. The longer file names have the disadvantage that often the last digest are truncated in certain views so that the file names are hard to destinguish (inside and outside digikam).

Possible solutions:

a) shorten the digest prefix to e.g. 3 digest (hardcoded)
b) add a field to let the user choose the desired digest length (with resonable default)
c) do some magic, so that the digest lenght is calculated from the number of selected photos in the Camera UI: e.g. 3 photos selected -> one digest (-1.jpg, -2.jpg, ...); 34 photos selected -> two digest (-01.jpg, ..., -34.jpg). Here one might give one "extra" digest by default in case the user wants to add more photos later (in the later example: -034.jpg instead of -34.jpg).

Don't know which solution is the best - if any ...
Comment 1 caulier.gilles 2007-12-22 12:59:40 UTC

*** This bug has been marked as a duplicate of 154463 ***
Comment 2 caulier.gilles 2022-01-27 16:16:59 UTC
Fixed with https://bugs.kde.org/show_bug.cgi?id=154463