Faticouni / xee

Automatically exported from code.google.com/p/xee
0 stars 0 forks source link

Better parsing of XMP values #219

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
First of all, if you have any Haxies, InputManagers, SIMBL plugins or
similar operating system hacks installed, please remove them first, restart
the program, and make sure the bug is reproducible without them.

What steps will reproduce the problem?
1. Open the attached JPEG.
2. Look at the XMP metadata.
3. You can see that some fields (e.g., IPTC creator contact info) show the
XML instead of the data.

What is the expected output? What do you see instead?
Is this the intent?

What version of the product are you using? On what operating system?
2.1.1 on OS X 10.4

Please provide any additional information below.

Original issue reported on code.google.com by mrochk...@gmail.com on 6 Mar 2010 at 8:07

Attachments:

GoogleCodeExporter commented 9 years ago
Well, the fact that some of the empty entries are shown as XML gibberish is 
bug, and that is fixed now.

However, Xee doesn't make all that much of an effort to support all the various 
forms of data that can exist in an XMP record, so it just dumps the XML instead 
and hopes you can figure it out. Ideally it should do more work to parse it but 
realistically that's a lot of work, and I don't have good test cases.

Hopefully I will have time to work on it at some point. Anybody who wants 
better XMP support, post some test case files here, that would help a lot.

Original comment by paracel...@gmail.com on 10 Apr 2011 at 2:50

GoogleCodeExporter commented 9 years ago
Xee 3.0 uses a new metadata engine, and it seems to handle this a bit more 
gracefully now. It still seems a bit fragmentary, though, but at least it 
doesn't show XML.

Original comment by paracel...@gmail.com on 11 Jan 2013 at 1:55