---- Reported by jim@yorba.org 2012-07-16 14:42:00 -0700 ----

Original Redmine bug id: 5560
Original URL: http://redmine.yorba.org/issues/5560
Searchable id: yorba-bug-5560
Original author: Jim Nelson
Original description:

Because there are cameras out there adding EXIF date/times with goofy formats,
Shotwell has a method that detects these problems and works around them so the
dates can be read.

Now that gexiv2 has GObject introspection support, other languages (and
applications) can start using gexiv2. This date/time logic might be better
placed inside gexiv2 so all programs can benefit from it. Otherwise, each
application will need to code around these bogus date formats.

Ticket #5524 is a gexiv2 ticket to add this logic to the library. This ticket
is to remove the logic from Shotwell and rely on gexiv2.

Related issues:
related to gexiv2 - 5524: Some date formats in the wild do not conform to
EXIF stan... (Moved)



---- Additional Comments From shotwell-maint@gnome.bugs 2013-09-19 13:04:00 -0700 ----

### History

####

#1

Updated by Adam Dingle over 1 year ago

Should this date/time logic instead be pushed into libexiv2 itself so that all
programs using libexiv2 (not just those going through gexiv2) can take
advantage of it?

####

#2

Updated by Jim Nelson over 1 year ago

I considered that. It would be an API/ABI change, so I don't know how warm the
maintainer would be to that. It's less of an issue with gexiv2 because our
user base is so small. I've posted a proposal here:
http://dev.exiv2.org/boards/3/topics/1221

Also, my thought was that gexiv2 could return a GDateTime object, which saves
the caller the trouble of parsing the EXIF string properly (GDateTime won't do
it automatically). Exiv2 could only do that with a standard C/C++ time format,
such as time_t, but we've seen the problems of using UNIX time to represent
EXIF dates. The best Exiv2 could probably do is fix-up the EXIF string before
returning it.

####

#3

Updated by Jim Nelson 11 months ago

  * **Target version** set to _0.14.0_

####

#4

Updated by Jim Nelson 11 months ago

  * **Category** set to _metadata_

####

#5

Updated by Jim Nelson 10 months ago

  * **Target version** changed from _0.14.0_ to _0.15.0_

####

#6

Updated by Jim Nelson 8 months ago

  * **Subject** changed from _Move EXIF data handling logic into gexiv2_ to _Move EXIF date handling logic into gexiv2_

####

#7

Updated by Jim Nelson 8 months ago

  * **Target version** changed from _0.15.0_ to _0.16.0_

####

#8

Updated by Jim Nelson 6 months ago

  * **Target version** changed from _0.16.0_ to _0.15.0_

####

#9

Updated by Jim Nelson 2 months ago

  * **Target version** changed from _0.15.0_ to _0.16.0_



--- Bug imported by chaz@yorba.org 2013-11-25 21:57 UTC  ---

This bug was previously known as _bug_ 5560 at http://redmine.yorba.org/show_bug.cgi?id=5560

Unknown milestone "unknown in product shotwell. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution