HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] Hylafax 4.1.5 and 2-D MR Wierdness



Lee/Bodo,

Thanks for your help with this. Since I have 3 50ppm Kodak
scanners, I am tied to the Kodak imaging libraries for the
foreseeable future.

I'll try hacking tiff2fax to handle the condition as noted in the bug
report.

Just in case, where would I find the libtiff 3.5.5 libraries?

Thanks!

Mike

----- Original Message ----- 
From: "Lee Howard" <faxguy@howardsilvan.com>
To: "Mike McMullen" <mlm@loanprocessing.net>
Cc: <hylafax-users@hylafax.org>
Sent: Monday, February 17, 2003 7:26 PM
Subject: Re: [hylafax-users] Hylafax 4.1.5 and 2-D MR Wierdness


> On 2003.02.17 17:29 Mike McMullen wrote:
> 
> > ------------------
> > Your facsimile job to 9448422 was rejected because:
> >     docq/doc29.ps.13: Warning, unknown field with tag 32934 (0x80a6)
> > ignored.
> > Unexpected failure converting TIFF document; the command
> > 
> >     /usr/bin/tiffcp -i -c g3:2d -f lsb2msb -r 9999  docq/doc29.ps.13
> > docq/doc29.ps;41
> > 
> > failed with exit status 9.  This conversion was done because:
> > 
> > Document requires reformatting, not in Group 3 format.
> > Document requires reformatting, client is incapable of receiving 2DMR
> > data.
> > ------------------
> 
> Background: TIFF G4 is also known as MMR.  HylaFAX doesn't support MMR 
> in Class 1, and most modems don't support MMR in Class 2.  TIFF G4 is 
> generally a tighter compression than TIFF G3, and so storing image 
> files (particularly 200 dpi monochrome ones) in TIFF G4 is a good 
> idea.  But, when you go to fax these TIFF G4 image files, HylaFAX must 
> convert them to a format which it and/or the modem can use.  So, 
> tiff2fax is called, which is really just a wrapper for tiffcp.  Thus, 
> you see the tiffcp call in your error log.
> 
> The factor that "changed" between your RedHat 7.0 and 7.3 installations 
> is with tiffcp giving an exit status of 9.  This is not a fatal error, 
> but a warning status, and tiff2fax should continue rather than stop.
> 
> http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=341
> 
> http://bugzilla.remotesensing.org/show_bug.cgi?id=14
> 
> http://www.hylafax.org/archive/2002-10/msg00096.php
> 
> SO, you have a number of options.
>    - implement the change to tiff2fax as noted
>    - downgrade libtiff
>    - stop using Windows/Kodak/Wang Imaging functions
> 
> 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@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*




Project hosted by iFAX Solutions