Package: exiv2
Version: 0.7-9
Severity: normal

exiv2 fails to recognize a file after jbrout adds an IPTC tag.

Before tagging:
  [EMAIL PROTECTED]:/tmp$ exiv2 1109-212314.jpg 
  Filename        : 1109-212314.jpg
  Filesize        : 1948912 Bytes
  Camera make     : CASIO COMPUTER CO.,LTD 
  Camera model    : EX-P600
  Image timestamp : 2005:11:09 21:23:14
  Image number    : 
  Exposure time   : 1/8 s
  Aperture        : F2.8
  Exposure bias   : 0
  Flash           : No, compulsory
  Flash bias      : 
  Focal length    : 7.1 mm (35 mm equivalent: 33.0 mm)
  Subject distance: 
  ISO speed       : 
  Exposure mode   : Auto
  Metering mode   : Matrix
  Macro mode      : 
  Image quality   : 
  Exif Resolution : 2816 x 1872
  White balance   : 
  Thumbnail       : JPEG, 8206 Bytes
  Copyright       : 
  Exif comment    : 


After tagging (and renaming):
  [EMAIL PROTECTED]:/tmp$ exiv2 p20051109_212314.jpg 
  Exiv2 exception in print action for file p20051109_212314.jpg:
  This does not look like a JPEG image

However, file, gqview, xli, display, and gimp all recognize the file
as a jpeg image.  gqview and jhead can read its EXIF headers.
  
The jbrout author writes:

  Date: Wed, 30 Nov 2005 14:16:34 +0100
  From: manatlan <[EMAIL PROTECTED]>
  To: "James R. Van Zandt" <[EMAIL PROTECTED]>
  Subject: Re: jbrout/exiv2 incompatibility
  In-Reply-To: <[EMAIL PROTECTED]>
  MIME-Version: 1.0
  Content-Type: text/plain; charset=ISO-8859-1
  Content-Transfer-Encoding: quoted-printable
  Content-Disposition: inline
  References: <[EMAIL PROTECTED]>
  
  > I've been looking for a way to tag my pictures - jbrout looks nice!
  thanks ...
  
  > However, I note that once I've added a tag with jbrout, exiv2 no
  > longer recognizes that file as a valid .jpeg image.
  > Is jbrout writing
  > an invalid file?  Or is exiv2 too particular about its input file?
  
  jbrout use a python lib to put "iptc keywords" in a jpeg (iptcinfo)
  (it's a port of the famous iptc perl lib)
  i've contacted the author of the python lib about this problem ... and
  he thinks it's a bug from exiv2 ... i trust him, because it seems he
  know very well the problem
  
  A lot of programs (in win32/nux) understand the iptc tags of jbrout,
  without any trouble .. so i consider it's an exiv2 trouble too.
  
The (unofficial) jbrout package is available here:

deb http://jbrout.free.fr/download/debian binary/

               - Jim Van Zandt

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages exiv2 depends on:
ii  libc6                         2.3.5-6    GNU C Library: Shared libraries an
ii  libexiv2                      0.7-9      EXIF/IPTC metadata manipulation li
ii  libgcc1                       1:4.0.2-2  GCC support library
ii  libstdc++6                    4.0.2-2    The GNU Standard C++ Library v3

exiv2 recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to