News:

2023-08-10 - ExifTool version 12.65 released

Main Menu

Adding XMP

Started by Archive, May 12, 2010, 08:54:02 AM

Previous topic - Next topic

Archive

[Originally posted by ron on 2007-04-17 11:33:27-07]

Hello Phil,

I'm sending you the XMP that I was inserting. After I run the StripBOM, double encoding is still there, but running the option that you gave, exiftool can now read the XMP format and it was successfully inserted.

Viewing of XMP data now works with Adobe Bridge, before I'm using PhotoShop CS and it cannot view those data and I don't know why.

Thanks for your help Phil.

btw, using option -w, does it works if there is an error in inserting XMP? I notice that -w only write console output if it is successfully inserted, is there a way that error prompted in console be included in -w?

-Ron

Archive

[Originally posted by ron on 2007-04-17 11:36:45-07]

Hello Phil,

I'm sending you the XMP that I was inserting. After I run the StripBOM, double encoding is still there, but running the option that you gave, exiftool can now read the XMP format and it was successfully inserted.

Viewing of XMP data now works with Adobe Bridge, before I'm using PhotoShop CS and it cannot view those data and I don't know why.

Thanks for your help Phil.

btw, using option -w, does it works if there is an error in inserting XMP? I notice that -w only write console output if it is successfully inserted, is there a way that error prompted in console be included in -w?

-Ron

Archive

[Originally posted by exiftool on 2007-04-17 12:24:52-07]

Hi Ron,

Thanks for the sample.  Yes, this XMP is still double-UTF8 encoded.  This
means that the "xpacket begin" attribute contains an invalid BOM marker
(which is probably the reason that PS CS had a problem with it), and likely
means that any special characters in the text will be corrupted.

Rather than use your SripBOM utility, you can use the new version of exiftool
(6.87) to fix this properly.  You can download a 6.87 pre-release
https://exiftool.org/Image-ExifTool-6.87.tar.gz" target="_blank">here.

You can rewrite the file with a command like this:

Code:
exiftool original.xmp -o fixed.xmp

You will get a warning message that the XMP is double UTF-encoded, and
exiftool 6.87 will double-decode it.  I still haven't received a sample containing
any special characters, but I have assumed that they will be double-encoded
like the BOM, so this should fix them too.

About your -w question:  The -w output is redirected from STDOUT, and
should not contain error or warning messages since they are sent to STDERR.

- Phil

Archive

[Originally posted by ron on 2007-04-25 01:31:28-07]

Hello Phil,

I've tested your new version(6.87) several times in different format (tif, jpg, and eps) and its working fine. Thanks for your continuous support.

-Ron