Why should they understand something that violates the spec? It's probably going to work 'most of the time' - especially on *nix platforms and probably harmless on Windows. However, you cannot assume that other applications will understand this. If I were encoding 'unicode', I would use UTF-8 without a BOM marker. And you can store binary bytes (128-255) in a ASCII field. You can change the value to be a different type. BYTE is not required to have an ascii nul trailer.Īlthough Exiv2 implements the standard, it doesn't enforce it.

BYTE is binary (all bytes 0-255 are valid).

I believe there are two differences between BYTE and ASCII. The count of 20 includes the ascii nul trailer.

Tested for JPEG, TIFF 8- and 16-bit using queue and direct save.įor x in amsterdam* do echo '$x' exiv2 -pv '$x' 2>/dev/null | grep 'Exif ' doneĠx010e Image ImageDescription Ascii 22 Exif ImageDescriptionĠx8298 Image Copyright Ascii 15 Exif CopyrightĠx9286 Photo UserComment Ascii 22 Exif Exif.UserCommentīuild flags: -Wno-unused-result -march=native -fopenmp -O3 -DNDEBUGĦ03 $ exiv2 -pv -grep date/i ~/Stonehenge.jpgĠx0132 Image DateTime Ascii 20 2015:07:16 20:25:28Ġx9003 Photo DateTimeOriginal Ascii 20 2015:07:16 15:38:54Ġx9004 Photo DateTimeDigitized Ascii 20 2015:07:16 15:38:54Ġx0003 NikonWt DateDisplayFormat Byte 1 0Ġx001d GPSInfo GPSDateStamp Ascii 11 2015:07:16Īs you can see, Image.DateTime is an Ascii tag (0x0132) of 20 bytes as documented on page 83.

Rawtherapee vs darktable 2017