AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2011.06.15 09:25 "Re: [Tiff] bug in G4 encoder.", by Erik Thiele
2011.06.14 11:06 "[Tiff] bug in G4 encoder.", by Erik Thiele
2011.06.14 13:11 "Re: [Tiff] bug in G4 encoder.", by Steve Underwood
2011.06.14 13:46 "Re: [Tiff] bug in G4 encoder.", by Erik Thiele
2011.06.15 15:00 "Re: [Tiff] bug in G4 encoder.", by Steve Underwood
2011.06.15 15:49 "Re: [Tiff] bug in G4 encoder.", by Lee Howard
2011.06.15 05:22 "Re: [Tiff] bug in G4 encoder.", by Lee Howard
2011.06.15 14:22 "Re: [Tiff] bug in G4 encoder.", by Bob Friesenhahn
2011.06.15 15:20 "Re: [Tiff] bug in G4 encoder.", by Erik Thiele

2011.06.14 11:06 "[Tiff] bug in G4 encoder.", by Erik Thiele

Hello,

there is a bug in the G4 encoder. attached to this email you find a file "gimpcrop.g3.tiff". it is a correct TIFF file encoded with G3. you can open it with the usual viewers.

now do this:

tiffcp -c g4 gimpcrop.g3.tiff out.tiff

the file gets converted from G3 to G4. the following command shows that the output file is corrupted.

tiffcp out.tiff lala.tiff

Fax4Decode: out.tiff: Bad code word at line 17 of strip 9 (x 0).

Fax4Decode: Warning, out.tiff: Premature EOL at line 17 of strip 9 (got 0, expected 4519).

Fax4Decode: Warning, out.tiff: Line length mismatch at line 44 of strip 9 (got 4520, expected 4519).

Fax4Decode: Warning, out.tiff: Line length mismatch at line 53 of strip 9 (got 4574, expected 4519).

Fax4Decode: Warning, out.tiff: Premature EOL at line 63 of strip 9 (got 72, expected 4519).

bughunt$

you can open lala.tiff in a viewer and get error messages. usually the viewer anyway views the image, but it contains a horizontal black line, which should not be there. in addition it contains more pixel errors.

in case you cannot reproduce the problem, i attached lala.tiff to this email.

tiffcp sais:
LIBTIFF, Version 3.9.4
my debian version of the libtiff4 package is 3.9.4-5+squeeze2

I have recently reported this bug on the debian bug tracking system and am hereby forwarding it to you.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630042

cu & thanks

Erik