That is a good tip. I will try to reproduce with 7.30. Other differences I have found: 

1. Block start with different chars::
Linux:
 HEX            ASCII
FF E1 0B 24     .$

Win:
FF E1 0B 25     .%


2. After the slash in "/xap/1.0/ - And before the tag <?xpacket
I have this:

Linux:
  - HEX -    -   ASCII  -
2F  00 3C    -  /.<

Win:
2F  20 00 3C - / .<


When I change 20 to 00 in a hexeditor, i get this:

$ exiv2 -p x fromwin.jpg
XMP Toolkit error 201: XML parsing failure
Warning: Failed to decode XMP metadata.
fromwin.jpg: No XMP data found in the file

[download]
Strange. Ill get back with testresult on 7.30. It would be intresting if this bug/feature is reproducable on other systems.

In reply to Re^4: XMP, Image::ExifTool, strawberryperl by mrkjell
in thread XMP, Image::ExifTool, strawberryperl by mrkjell

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.