"com.apple.FinderInfo" xattr data copy to O3X not faithful?

The result of Finder copies, copies via commandline, or ChronoSync, the xattr "com.apple.FinderInfo" does not seem to be entirely faithful.
My understanding is that it's a binary fixed length of 32 bytes.
When I copy using the Finder, using the command line, or via ChronoSync the result is that there is extra "info" added to the 32 bytes.
For example:
the ORIGINAL SOURCE might be:
com.apple.FinderInfo (32 bytes):
<50545820 5054756c 00000000 00000000 00000000 00000000 00000000 00000000>
String content:
PTX PTul
And the RESULTANT COPY would be:
com.apple.FinderInfo (32 bytes):
<50545820 5054756c 00000000 00000000 00000000 5ceae387 00000000 00000000>
Binary data as string:
«PTX PTul\êã»
See the screenshot where I used the xattred application to compare two files, one on an original APFS volumes, the other on a O3X zfs volume.
Also, using "rsync -rlptDvnihxHEXN" to compare the directories, it also reveals a difference in the xattr consistent with this assessment.
Platform:
OS X 10.14.5 (Mojave)
Tested using release:
O3X 1.8.2
Also tested using Beta:
O3X 1.9.0 RC3
Same result with both.
Thanks!
-- madison
My understanding is that it's a binary fixed length of 32 bytes.
When I copy using the Finder, using the command line, or via ChronoSync the result is that there is extra "info" added to the 32 bytes.
For example:
the ORIGINAL SOURCE might be:
com.apple.FinderInfo (32 bytes):
<50545820 5054756c 00000000 00000000 00000000 00000000 00000000 00000000>
String content:
PTX PTul
And the RESULTANT COPY would be:
com.apple.FinderInfo (32 bytes):
<50545820 5054756c 00000000 00000000 00000000 5ceae387 00000000 00000000>
Binary data as string:
«PTX PTul\êã»
See the screenshot where I used the xattred application to compare two files, one on an original APFS volumes, the other on a O3X zfs volume.
Also, using "rsync -rlptDvnihxHEXN" to compare the directories, it also reveals a difference in the xattr consistent with this assessment.
Platform:
OS X 10.14.5 (Mojave)
Tested using release:
O3X 1.8.2
Also tested using Beta:
O3X 1.9.0 RC3
Same result with both.
Thanks!
-- madison