Bug #799: Exiv2 returns wrong XMP type for nested XMP keys - Exiv2

Bug #799

Exiv2 returns wrong XMP type for nested XMP keys

Added by Andreas Huggel almost 10 years ago. Updated over 9 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Andreas Huggel

Category:

xmp

Target version:

0.23

Start date:

11 Jan 2012

Due date:

% Done:

100%

Estimated time:

Description

The type of a nested Exiv2 XMP key (one which contains a "/"), like Xmp.MP.RegionInfo/MPRI:Regions, is not properly detected. Exiv2 tries to find an XMP "RegionInfo/MPRI:Regions" property in the lookup table for namespace "MP". Since that doesn't exist it uses the default XmpText type. Instead, t should look for the type of the innermost property, MPRI:Regions in the example.

This bug was unearthed in a discussion about how to add new XMP namespaces and use them from pyexiv2.

Related issues

Associated revisions

Revision 2644 (diff)
Added by Andreas Huggel almost 10 years ago

#799: Fixed type-determination for nested properties,
XmpBag::read: don't do anything if the string is empty,
Added Iptc4xmpCore and Iptc4xmpExt as possible prefixes

Revision 2649 (diff)
Added by Andreas Huggel almost 10 years ago

#799: Added regression test (using the example provided by Benjamin H. in connection with #798).

Revision 2651 (diff)
Added by Andreas Huggel almost 10 years ago

#799: Added command file for tests.

Revision 2652 (diff)
Added by Andreas Huggel almost 10 years ago

#799: Moved check for nested property to XmpProperties::propertyInfo.

Revision 2653 (diff)
Added by Andreas Huggel almost 10 years ago

#799: Improved doc, tweaks.

Revision 2690 (diff)
Added by Andreas Huggel over 9 years ago

#799: Tweak to make tests pass on MSYS/MinGW.