Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] Tiff2fax bug?
On 24 Dec 2003, Andrea Nicolini wrote:
> OK I verified that on Hylafax 4.1.8 tiffcheck is on version 1.3,
> while on cvs it is on 1.5. Here's the diff:
>
> diff 4.1.8/tiffcheck.c++ cvs/tiffcheck.c++
> 1c1
> < /* $Id: tiffcheck.c++,v 1.3 2003/02/09 02:22:54 darren Exp $ */
> ---
> > /* $Id: tiffcheck.c++,v 1.5 2003/10/13 23:35:17 lhoward Exp $ */
> 67c67
I'm on vacation right now and not properly able to verify your findings,
but I have no reason to doubt you.
> < while ((c = getopt(argc, argv, "r:l:w:12")) != -1)
> ---
> > while ((c = getopt(argc, argv, "r:l:w:123")) != -1)
> 95a96,101
I've been using strictly CVS since 4.1.5 days, so I don't know why this
change isn't part of 4.1.8, but this change was supposed to be part of
4.1.6. So, I'm not sure if it was or wasn't in the 4.1.6 or 4.1.7
tarball, but it should of been, and it certainly should be in 4.1.8.
Seems like a code release glitch of some kind.
> >
> > /*
> > * Suppress libtiff warning messages from becoming fatal.
> > */
> > TIFFErrorHandler whandler = TIFFSetWarningHandler(NULL);
>
This is supposed to be the only difference in tiffcheck between 4.1.8 and
CVS.
> Is this a bug?
>
Probably.
Lee.
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxxxxx*