Author Topic: Gimp warning  (Read 494 times)

Offline malc

  • Sr. Member
  • ****
  • Posts: 387
    • Malcolms Home Website
Gimp warning
« on: September 05, 2012, 03:27:47 PM »
Please be aware that when you export a jpeg image, with Gimp 2.8, the XMP metadata is lost even if you ensure the "Save XMP data" option is ticked.

I have not yet found a workaround but I will keep experimenting.

Offline malc

  • Sr. Member
  • ****
  • Posts: 387
    • Malcolms Home Website
Re: Gimp warning
« Reply #1 on: October 09, 2012, 01:35:01 PM »
OK, it seems that Gimp is saving the aforementioned data BUT it is no longer readable by Gwenview or Digikam.  Which is as useful as chocolate fireguard.  Exif data is OK but anything else becomes "invisible" to other apps.  Well those two at least.

Will get back if I can identify any apps that "see" Gimp saved XMP data.

> You can add eog to the list of apps that won't read the data.
« Last Edit: October 09, 2012, 02:43:46 PM by malc »

Offline bullet_trap

  • Jr. Member
  • **
  • Posts: 35
Re: Gimp warning
« Reply #2 on: October 09, 2012, 03:43:09 PM »
Hi:
   I think the link below may help clarify the Gimp saving situation--

http://shallowsky.com/blog/gimp/gimp-save-export-clean.html


Offline malc

  • Sr. Member
  • ****
  • Posts: 387
    • Malcolms Home Website
Re: Gimp warning
« Reply #3 on: October 10, 2012, 02:16:02 PM »
Thanks bullet_trap but its not the save/export difference that's the issue here. Gimp is saving (or rather exporting) the XMP metadata but no other apps can read it back.  Now I have opened up the jpeg files and discovered that Gimp saves quoted text within single quotes whereas all the other apps enclose relevant text in double quotes.  The XMP standard allows for either single or double but not a mix.

I have come to the following conclusions:
* Gimp can read single or double quoted XMP text data
* Gimp saves XMP using single quotes
* Linux apps (via libraries) can only read XMP that uses double quotes.

The fault lies with the linux libraries, however, I suspect there may be regional/character set issue here. More investigation coming.........