Previous versions of XnViewMP* stored 'content location name' values into a iptc4xmp:location field (in case of the IPTC/XMP Editor is set to xmp). If you typed many 'content location name', XnViewMP 0.38 created a list of text (i.e. bag list) : iptc4xmp:location[1], iptc4xmp:location[2],...
But both IPTC Core 1.0 and IPTC Core 1.1 define the iptc4xmp:location field as a single text property. So 0.38 was not compliant with IPTC Core ! Hopefully most softwares are able to display and find the values of the list as probably they use a generic xml parser which is not "IPTC aware". On the other side, Photoshop Bridge CS6 is not able to display this field in its IPC Core Editor since it expect a single text and it find a list.
* I'll not speak about 0.39 and 0.40 since these version are "broken" in this area.
0.38 (and previous) could generate non-compliant IPTC files
Moderators: helmut, XnTriq, xnview, Dreamer
-
mahikeulbody
- Posts: 140
- Joined: Sun Dec 13, 2009 4:54 pm
-
mahikeulbody
- Posts: 140
- Joined: Sun Dec 13, 2009 4:54 pm
Re: 0.38 (and previous) could generate non-compliant IPTC fi
0.48 has another bug in this area so I am not sure of the answer. Anyway I cannot (re)test it before 3 weeks since I have not a Windows computer right now.