Bug 296113 - Regression: Can't transfer EXIF creation date to file date
Summary: Regression: Can't transfer EXIF creation date to file date
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-TimeAdjust (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-15 22:17 UTC by Andrzej
Modified: 2018-09-22 08:34 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrzej 2012-03-15 22:17:45 UTC
+++ This bug was initially created as a clone of Bug #207157 +++

I cloned the bug because the previous one was closed but not solved.

Below I repeat the most important information:

I use:
Use Time & Date * EXIF/IPTC/XMP
Update Time & Date v File last modified

When I click "OK" there is some activity of my HDD  but then a message appears:

"Unable to update file modification time in:
file1.jpg
file2.jpg
file3.jpg
"

I know what is the problem:
Apparently this plugin has problems with national characters e.g.
I had to change the directory name from "zdjęcia" to "zdjecia" in order to make it work.

Andrzej
Comment 1 Smit Mehta 2012-04-20 05:25:38 UTC
Hi Gilles

This seems to be an il8n(internalization) problem. what should be done here?

Smit
Comment 2 caulier.gilles 2012-04-20 07:03:09 UTC
It's not i18n. i18n want mean internationalization of GUI in KDE.

It's about UTF-8 strings support for file naming (non ASCII char used in file names).

I remember to have fixed some stuff like this in current implementation, but not tested really.

To trying to reproduce, we need to use file-naming scheme from Andrzej and look if file are processed with any error.

Gilles Caulier
Comment 3 Smit Mehta 2013-01-15 06:24:07 UTC
Hi Andrez

Is this bug still valid with 3.0.0 rc?

Smit
Comment 4 caulier.gilles 2015-05-17 13:05:03 UTC
Andrez,

Is this bug still valid using last kipi-plugins 4.10.0 ?

Gilles Caulier
Comment 5 caulier.gilles 2015-06-26 13:46:12 UTC
New Kipi-plugins 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier
Comment 6 caulier.gilles 2016-07-02 15:56:45 UTC
This plugin is now ported to digiKam BQM. Problem is not reproducible.

Gilles Caulier