Bug #628: exiv2 puts comments directly after SOI - Exiv2

Bug #628

exiv2 puts comments directly after SOI

Added by Andreas Huggel over 12 years ago. Updated over 12 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

jpeg parser

Target version:

0.18.2

Start date:

27 Apr 2009

Due date:

% Done:

100%

Estimated time:

Description

Reported by Johannes Hofmann
http://www.ecademix.com/JohannesHofmann/gipfel.html

I just noticed an issue with JPEG comments.
exiv2 puts a comment directly after the SOI.
If I interpret the Exif standard correctly, the exif marker
should be first. Also the fltk library (www.fltk.org) no longer
recognizes the resulting image.

hofmann@blob:/tmp >hexdump -C test.jpg | head -n 1
00000000 ff d8 ff e1 ff fe 45 78 69 66 00 00 4d 4d 00 2a |ÿØÿáÿþExif..MM.*|
hofmann@blob:/tmp >exiv2 -c foo test.jpg
hofmann@blob:/tmp >hexdump -C test.jpg | head -n 1
00000000 ff d8 ff fe 00 06 66 6f 6f 00 ff e1 ff fe 45 78 |ÿØÿþ..foo.ÿáÿþEx|

Associated revisions

Revision 1785 (diff)
Added by Andreas Huggel over 12 years ago

#628: Write COM segment (JPEG comment) last, after all APPn segments.

Revision 1787 (diff)
Added by Andreas Huggel over 12 years ago

#628: Improved version: insert comments just before SOFn. Updated test cases accordingly.

History

Updated by Andreas Huggel over 12 years ago

I agree that the resulting files are probably not "Exif images" according to the Exif standard.

In practice, such not-quite-JFIF JPEG files with or without an Exif APP1 segment are quite common, this is the first time I hear it upsets a JPEG image reader.