ValueType<T> constructor makes assumptions of the endianness of the machine
If I use the following code on Intel (little endian) machines:
exifData["Exif.Image.XResolution"] = Exiv2::ShortValue(37);
I get an expected resolution of 37 in the final image. However on
PowerPC (big endian) the bytes are swapped and the resolution value is
a lot bigger.
Reported by Dimitri in http://uk.groups.yahoo.com/group/exiv2/message/1449
The idea is that Exiv2 doesn't need to know the endianness of the machine in the first place - only that used in the TIFF data. This case violates this principle and makes an assumption for the endianness of the machine.