https://bugs.kde.org/show_bug.cgi?id=415460
Bug ID: 415460
Summary: JFIF files have APP0 marker after SOI where there
should be APP1
Product: digikam
Version: 5.9.0
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Plugin-Generic-SendByMail
Assignee: digikam-bugs-n...@kde.org
Reporter: anselm+...@anselms.net
Target Milestone: ---
SUMMARY
When Digikam writes resized JFIF files to be sent by e-mail, the resulting
files have a JPEG APP0 marker (starting with `ff e0 0010 4a 46 49 46 00 …’
immediately after the SOI marker (ff d8). This breaks programs like
jpegexiforient which expect the APP1 marker (with EXIF data) immediately after
the SOI marker, as the EXIF standard stipulates.
STEPS TO REPRODUCE
1. Use the “Send by Mail” feature of Digikam to create an e-mail message
containing a JFIF attachment.
2. Save that attachment to a file.
3. Inspect the file with a hex-dump editor.
OBSERVED RESULT
Bytes 3 and 4 of the file are FF E0.
EXPECTED RESULT
Bytes 3 and 4 of the file should be FF E1 (and the EXIF data should follow
these bytes as per the EXIF standard).
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: 5.9.0
(available in About System)
KDE Plasma Version: as in Debian 10.1
KDE Frameworks Version: as in Debian 10.1
Qt Version: as in Debian 10.1
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
