LibTiff Mailing List
TIFF and LibTiff Mailing List Archive
September 2007
Previous Thread
Next Thread
Previous by Thread
Next by Thread
Previous by Date
Next by Date
Contact
The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems
Thread
2007.09.24 08:01 "Re: G3 fax: EOL needed at the beginning of each strip?", by Andy Cave
Hi Joris, I'm curious - where in the spec does it indicate strips have to start with EOL? I don't remember it saying so, and checking quickly, I can't find a reference to that. Thanks, Andy. ----- Original Message ----- From: "Joris" <joris.at.lebbeke@skynet.be> To: "ComSquare Martin Osieka" <martin.osieka@comsquare.ch>; <tiff@lists.maptools.org> Sent: Monday, September 24, 2007 6:56 AM Subject: Re: [Tiff] G3 fax: EOL needed at the beginning of each strip? > Martin, > ... > The spec clearly indicates strips have to start with EOL. Unfortunately, > I've a reasonable amount (i.e. not just a fluke) of testimages where > garbage data preceeds the G3 block. LibTiff succeeds on these images by > skipping to the first EOL. If we were to change LibTiff to start decoding > right away, more unexpected stuff will happen on these images with > preceeding garbage data that might just be more frequent. > > In AsTiff, what I do if the strip or tile doesn't start with an EOL, is > actually test and see if a line of desired length can successfully be > decoded from the preceeding data, and if that data then is followed by an > EOL. If so, I regard that the first line. If not, the code starts at the > first EOL instead. This works on both the testimages with random > preceeding data, and the testimages that just lack the first EOL. But the > LibTiff fax decoder being as it is, a heap of macro's with embedded > macro's that nobody at this stage can easilly decipher, it may be hard to > make it behave equally intelligent. > ...