I know this bug was closed as wontfix, but it should be noted
that this means that exifautotran can no longer be used on
images that were resized with ImageMagick, GraphicsMagick, or PIL
(Python Imaging Library): they all produce files that exifautotrans
silently ignores, breaking scripts that
Control: tag -1 wontfix
Hi all,
On So 22 Dez 2019 17:57:27 CET, Ondřej Surý wrote:
Hi Anselm,
see https://datatracker.ietf.org/doc/draft-iab-protocol-maintenance/
why this is a very bad idea.
I am not going to apply the patch to the Debian, nor should it be
applied upstream. The
Hi Anselm,
see https://datatracker.ietf.org/doc/draft-iab-protocol-maintenance/ why this
is a very bad idea.
I am not going to apply the patch to the Debian, nor should it be applied
upstream. The program violation specification (Digikam) should be fixed
instead. Applying robustness
Package: libjpeg-turbo-progs
Version: 1:1.5.2-2+b1
Severity: normal
Tags: patch
Dear Maintainer,
according to the EXIF standard, the APP1 segment (which contains the EXIF data)
must
occur immediately after the SOI (start of image) marker at the beginning of a
JFIF file.
The jpegexiforient
4 matches
Mail list logo
