XMP tags are not good UTF-8

[GoogleCodeExporter]

I have filed a bug http://trac.yorba.org/ticket/2247 because it seemed to me 
that Shotwell doesn't import UTF-8 tags correctly. It turns out that the 
problem is not in shotwell, but in jbrout. See the ticket for more info and 
especially great explanation in the thread on 
http://dev.exiv2.org/boards/3/topics/590

Could you do something about it please? (with possibility how to fix already 
corrupted metadata if possible)

Original issue reported on code.google.com by matej.c...@gmail.com on 20 Aug 2010 at 1:57

[GoogleCodeExporter]

It seems it comes from pyexiv2 (or between jbrout and pyexiv2)
I opened the bug in pyexiv2 tracker : 
https://bugs.launchpad.net/pyexiv2/+bug/621201

In all cases, jbrout will provide a way to correct all xmp tags (using iptc 
ones) when the bug will gone.

Original comment by manat...@gmail.com on 20 Aug 2010 at 3:22

• Changed state: Accepted

[GoogleCodeExporter]

In fact, older jbrout used an external tools to write xmp keywords.
Since recent release, jbrout is able to use "pyexiv2 >= 0.2" to write XMP tags. 
And it works well (AFAIK).

I close this issue.

Original comment by manat...@gmail.com on 27 Aug 2010 at 4:58

• Changed state: Invalid

[GoogleCodeExporter]

Correct. Question now is what to do once the metadata are corrupted 
(https://code.google.com/p/jbrout/issues/detail?id=161 and I have made new post 
on exiv2 forum http://dev.exiv2.org/boards/3/topics/590#message-612

Original comment by matej.c...@gmail.com on 27 Aug 2010 at 5:22