Bug #19032 for Image-ExifTool: ImageExifTool

Tue May 02 13:33:27 2006 Guest - Ticket created

Subject:

ImageExifTool - EPS XMP bug

Hi Phil .... I am very pleased with the EPS functionality ... Works a treat... However... Here is something you may not have realised... Adobe Photoshop exports what it calls Photoshop EPS, this contains XMP metadata. Adobe In-Design exports what it calls Generic EPS, this does not contain XMP meta-data. I have successfully added a workflow which plugs into In-Design and re- inserts the IPTC/XMP back into an exported EPS, for all it's component links. This uses ImageExifTool 6.0. In-Design CS2 exports the EPS with a header defining ADO_ContainsXMP: NoMain If you use ImageExifTool to insert XMP into an EPS file and the header defines, ADO_ContainsXMP: NoMain, you need to also replace, ADO_ContainsXMP: NoMain with ADO_ContainsXMP: MainLast Otherwise Adobe CS2/Photoshop will not read the ImageExifTool inserted values.. For the moment I just fix this myself but it you want to make ImageExifTool, Adobe friendly, then you may wish to correct the header. Furthermore.... A suggestion ... The way you read the exiftool config file from a users home directory does not lend itself to a multi-user environment.. With each release of ImageExifTool I have to change the code to pick up the config from the install directory. This way multiple users can share the same config and you do not have to be a specific user to run ImageExifTool. I suspect you should probably be checking both locations, not just the users home directory. This way you can have a site config which can be overrided by the users config. Keep up the good work, hope you enjoyed that well earned holiday. Thanks Mark

Tue May 02 15:46:40 2006 EXIFTOOL [...] cpan.org - Correspondence added

Hi Mark, Thanks for the bug report. I have added support to write the %ADO_ContainsXMP comment. On question though: My reading of the XMP specs would suggest that I should use "MainFirst", not "MainLast" since I write the XMP immediately after the header section. This is the way I have implemented it. I had also realized about the .ExifTool_config directory limitation, but hadn't done anything about it because 1) nobody complained, and 2) I didn't want to slow down processing by checking another directory unless necessary, 3) I didn't know how to define a central directory to use for the common config file. However, I have an idea which could work: How about if I allow an EXIFTOOL_HOME environment variable to be defined to override the default HOME location for the .ExifTool_config file? I have implemented this too. I have placed a pre-release version of 6.16 at http://owl.phy.queensu.ca/~phil/exiftool/ Image-ExifTool-6.16.tar.gz for you to test out. It includes both the %ADO_ContainsXMP and the EXIFTOOL_HOME updates. Let me know how it works for you. If everything goes well, I will leave these changes in when the official 6.16 release is made.

Tue May 02 15:46:41 2006 The RT System itself - Status changed from 'new' to 'open'

Thu May 04 08:22:05 2006 Guest - Correspondence added

From:

mark.tate [...] newsint.co.uk

Hello The EXIFTOOL_HOME code is working fine... The %ADO_ContainsXMP still has problems.... It appears to insert a new %ADO_ContainsXMP MainFirst tag at the end of the header but leaves the original %ADO_ContainsXMP NoMain in place.. In-Design is reading the first %ADO_ContainsXMP value (NoMain) and assuming it does not have any XMP... Do you need me to send some example postscript ? Thanks Mark On Tue May 02 15:46:40 2006, EXIFTOOL wrote: Show quoted text

> Hi Mark, > > Thanks for the bug report. > > I have added support to write the %ADO_ContainsXMP comment. On > question though: My > reading of the XMP specs would suggest that I should use "MainFirst", > not "MainLast" since I > write the XMP immediately after the header section. This is the way

I Show quoted text

> have implemented it. > > I had also realized about the .ExifTool_config directory limitation, > but hadn't done anything > about it because 1) nobody complained, and 2) I didn't want to slow > down processing by > checking another directory unless necessary, 3) I didn't know how to > define a central > directory to use for the common config file. However, I have an idea > which could work: How > about if I allow an EXIFTOOL_HOME environment variable to be defined > to override the > default HOME location for the .ExifTool_config file? I have > implemented this too. > > I have placed a pre-release version of 6.16 at > http://owl.phy.queensu.ca/~phil/exiftool/ > Image-ExifTool-6.16.tar.gz for you to test out. It includes both the > %ADO_ContainsXMP and > the EXIFTOOL_HOME updates. Let me know how it works for you. If > everything goes well, I > will leave these changes in when the official 6.16 release is made.

Thu May 04 08:31:15 2006 Guest - Correspondence added

Hi Mark, Thanks for the feedback. There must be something different with your EPS sample because this worked with the files I used for testing. I could figure out what the problem is if you make a sample available. If you could make it available for download or email it to phil at owl.phy.queensu.ca that would be great.

Tue May 09 11:44:27 2006 EXIFTOOL [...] cpan.org - Correspondence added

The problem was that (contrary to Adobe's own XMP documentation), Adobe InDesign leaves out the colon in the line: %ADO_ContainsXMP: NoMain which resulted in ExifTool not recognizing the comment. I have changed ExifTool to make the colon optional, and this update appears in version 6.16 which solves the problem that Mark observed.

Tue May 09 11:47:20 2006 EXIFTOOL [...] cpan.org - Status changed from 'open' to 'resolved'

Tue May 09 11:47:22 2006 EXIFTOOL [...] cpan.org - Fixed in 6.00 deleted

Mon May 15 20:25:30 2006 EXIFTOOL [...] cpan.org - Fixed in 6.17 added

Bug #19032 for Image-ExifTool: ImageExifTool - EPS XMP bug