Project

General

Profile

Bug #501

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

Added by Andreas Huggel over 12 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Category:
iptc
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

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 exceptionClosed

Actions

History

Also available in: Atom PDF