Bug #501

IPTC field parsing is still too strict: shouldn't fail if the type is not as expected

Added by Andreas Huggel almost 11 years ago. Updated almost 9 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Andreas Huggel% Done:

0%

Category:iptc
Target version:0.13

Description

When exiv2 parses an IPTC field which is expected to contain a date or time value, it will fail with an "Unsupported time/date format" error if the format can't be parsed and not read the field.
Instead it should not depend on the content to be a time or date value and fallback on a string type if the first attempt fails.

Reported by Elsa Nordh.


Related issues

Related to Exiv2 - Bug #440: IPTC time without timezone raises exception Closed

History

Also available in: Atom PDF

Redmine Appliance - Powered by TurnKey Linux