[digikam] [Bug 477470] File name timestamp formats
https://bugs.kde.org/show_bug.cgi?id=477470 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||8.3.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477470] File name timestamp formats
https://bugs.kde.org/show_bug.cgi?id=477470 --- Comment #7 from ratounade --- Hi I just tested 8.2, on windows. Seems great. In particular, I can confirm that files with format "MMDD HHmmss WHATEVERAFTER.XXX" can now be managed, using the great feature allowing to change dates in the metadatas of the photos. Thank you so much again. Not related to digiKam : answering to the initial question from Erik, about names "November 23, 2016 at 1002PM". I strongly suggest first of all you align the naming of your photos and suggest the "Ant Renamer" free tool you can easily find on the web. Ant Renamer can modify the names of multiple files with rules. As an example, it allows to change "November" to "11" in the files that selected. It allows to move X characters to the position Y allowing wou to move the 2016 at the beginning. Then once you have homogeneous names such, you can use DigiKam and all its features Best -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477470] File name timestamp formats
https://bugs.kde.org/show_bug.cgi?id=477470 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #6 from caulier.gil...@gmail.com --- Erik, The 8.2.0 official bundles are already available for production (official announcement will be posted this week end). Look here : https://download.kde.org/stable/digikam/8.2.0/ Please test and report Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477470] File name timestamp formats
https://bugs.kde.org/show_bug.cgi?id=477470 --- Comment #5 from ratounade --- thank you so much Maik and team Let's wait for next version ! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477470] File name timestamp formats
https://bugs.kde.org/show_bug.cgi?id=477470 --- Comment #4 from Maik Qualmann --- Git commit 0baec12ad941bccfaae4a8ba4bc30089cf90599a by Maik Qualmann. Committed on 28/11/2023 at 06:28. Pushed by mqualmann into branch 'master'. add “MMDD hhmmss” variant detection to the TimeAdjust tool M +2-1core/libs/timeadjust/timeadjustcontainer.cpp https://invent.kde.org/graphics/digikam/-/commit/0baec12ad941bccfaae4a8ba4bc30089cf90599a -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477470] File name timestamp formats
https://bugs.kde.org/show_bug.cgi?id=477470 --- Comment #3 from ratounade --- As there is a french IT in the loop : spéciale dédicace bravo Gilles c'est du super super boulot, merci -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477470] File name timestamp formats
https://bugs.kde.org/show_bug.cgi?id=477470 ratounade changed: What|Removed |Added CC||rc...@free.fr --- Comment #2 from ratounade --- Hi, DigiKam is great but indeed, it is not clear how ."adjust time" with "File name timestamp" does work. All my +50K photos are under file name "MMDD hhmmss BLABLA!WHATEVER" DigiKam seems ok on 20190526 122104 IMG_1245 -> GOOD time stamp as it is 20190526 122104 but on does not work on 20190526 122104 P1160146 -> BAD time stamp as it is 20190526 160146 Quite surprising. And no way to find out your algorithm does work -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477470] File name timestamp formats
https://bugs.kde.org/show_bug.cgi?id=477470 Maik Qualmann changed: What|Removed |Added Component|Metadata-Date |Plugin-Generic-TimeAdjust -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477470] File name timestamp formats
https://bugs.kde.org/show_bug.cgi?id=477470 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Text is not recognized, we would have to support all languages in the world. That's out of scope. Maik -- You are receiving this mail because: You are watching all bug changes.
