GNOME Bugzilla – Bug 526331
EoG can't read XMP tags created with F-SPOT whereas Nautilus can
Last modified: 2010-05-13 21:33:59 UTC
Please describe the problem: EoG doesn't displays keywords added with F-Spot Here is a sample file http://launchpadlibrarian.net/9849461/DSC_0407-2.JPG : i've added "vacances" and "Saint-tropez" as keyword to that picture in F-Spot Eog doesn't display them (see http://launchpadlibrarian.net/11746648/Screenshot.png ) I was not sure if it was a F-Spot or a EoG bug, but since Nautilus displays keywords while right clicking on the file (Image tab), therefore i guess it is an EoG bug i'm running Ubuntu Hardy beta (GNOME 2.22) (From https://bugs.launchpad.net/ubuntu/+source/eog/+bug/146288/ that bug report on Launchpad was first about EoG in Ubuntu 7.10 showing no metadata at all. While Ubuntu 8.04 fixed it, EoG still doesn't show all metadata) Steps to reproduce: Open the sample file or any file with keywords added with F-Spot Actual results: EoG doesn't display these keywords Expected results: EoG should display these keywords like F-Spot or nautilus do Does this happen every time? yes Other information:
This is caused by bug 519127. F-Spot doesn't write an xpacket conforming to the XMP standard. We were skipping the first xpacket tag and were thus relying on the standard conformance (means length) of it. I've changed that now as Exempi seems to have no problem with getting fed with the whole xpacket. Committed the fix to trunk and to gnome-2-22 (only the JPEG part): 2008-04-06 Felix Riemann <> * src/eog-metadata-reader-jpg.c: * src/eog-metadata-reader-png.c: Don't skip the XMP xpacket tag. Exempi seems to handle it just fine. Increases compatibility with non-standard xpackets. Fixes bug #526331. ---------------------------------------------------------------------------------- This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.
excellent, thank you very much :-)
Created attachment 159025 [details] file tagged with pyexiv2 1.x (no XMP support)
Created attachment 159026 [details] File tagged with pyexiv2 2.x (with xmp support)
I'd like to re-open that bug but maybe shall i open another one, tell me. I'm running Ubuntu Lucid beta 2 with EOG 2.30 and i've noticed that metadatas that i've added once through phraymd (1) are not displayed in EOG whereas Nautilus does the job. Recent phraymd versions work with pyexiv2 2.0 (based upon libexiv2 0.19) (2) and add XMP support. I'm using both latest versions of phraymd and pyexiv2 at present time. I've noticed taht if i change metadatas, then they show up in EOG. Photos that i've tagged with older phraymd versions may have IPTC tags. I guess that newer versions of phraymd make the IPTC-XMP sync when changing metadatas : that would explain why EOG show metadatas only for modified files. Maybe that EOG could support both IPTC and XMP, just like Nautilus ? (1) https://launchpad.net/phraymd (2) https://launchpad.net/~pyexiv2-developers/+archive/ppa see above attached files
(these bugs may be related : Bug 349222 & Bug 515265)
(and Bug 341653)
(In reply to comment #5) > I'd like to re-open that bug but maybe shall i open another one, tell me. > > I'm running Ubuntu Lucid beta 2 with EOG 2.30 and i've noticed that metadatas > that i've added once through phraymd (1) are not displayed in EOG whereas > Nautilus does the job. > > Recent phraymd versions work with pyexiv2 2.0 (based upon libexiv2 0.19) (2) > and add XMP support. I'm using both latest versions of phraymd and pyexiv2 at > present time. > > I've noticed taht if i change metadatas, then they show up in EOG. > > Photos that i've tagged with older phraymd versions may have IPTC tags. I guess > that newer versions of phraymd make the IPTC-XMP sync when changing metadatas : > that would explain why EOG show metadatas only for modified files. > > Maybe that EOG could support both IPTC and XMP, just like Nautilus ? nautilus isn't showing anything eog doesn't (I guess you mean the description string) here. Regarding IPTC-IIM you are correct, this would be bug 341653. But as IPTC-XMP is the preferred format I'd rather not add specific support for it but would look into supporting it on the way to exiv2 support (bug 515265).
ok, thanks