Re: [hylafax-users] [hylafax-devel] [Bug 730] New: default Class1JBIGSupport

[Tadeusz Andrzej Kadłubowski <tkadlubo@xxxxxxxxxxxxxxxxx>]

Thus wrote bugzilla-daemon@xxxxxxxxxxx:
> http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=730
> 
>            Summary: default Class1JBIGSupport
>            Product: HylaFAX
>            Version: latest
>           Platform: PC
>         OS/Version: Linux
>             Status: NEW
>           Severity: normal
>           Priority: P2
>          Component: faxrcvd
>         AssignedTo: hylafax-devel@xxxxxxxxxxx
>         ReportedBy: faxguy@xxxxxxxxxxxxxxxx
> 
> 
> Some distributions (like Gentoo) install JBIG-KIT (presumably for the benefit to
> ImageMagick), but haven't yet picked up on the JBIG patch for libtiff.
> 
> Consequently, when HylaFAX is built on those systems Class1JBIGSupport will
> default to true (because JBIG support was found).  And... this poses no
> technical reasons in receiving or sending JBIG faxes because in the case of
> sending, JBIG-KIT libraries are used directly, libtiff is not uniquely involved
> in sending JBIG data.  In the case of receiving there still is no problem,
> because HylaFAX parses the JBIG markers itself and stores correct information in
> the TIFF, and libtiff has had the proper JBIG tags for a long time now.
> 
> The difficulty arises after the fax is received.  I don't know of any TIFF
> utilities that support JBIG other than libtiff after it is patched.  And, so if
> the JBIG fax is received (and stored in TIFF)... well, the receiver won't be
> able to do anything with it when libtiff is not patched for JBIG support.
> 
> It appears that the libtiff development people are slower to accept the JBIG
> contribution into their repository than I had hoped, so it may be a while before
> normal installations are going to have JBIG-enabled libtiffs... unless the
> distributions pick up on the JBIG patch independently.
> 
> I feel that it's important that we enable features like JBIG by default when the
> underlying system supports it.
> 
> So for installations where JBIG-KIT is there, but not the corresponding libtiff
> support, I think that Class1JBIGSupport should be expanded from a boolean to a
> "true/false/send-only" option.
> 
> We'd place a small jbig.tif file somewhere in the repository, and during
> configure, if JBIG libraries are found, we'd test a libtiff utility, such as
> tiffcp, in copying/converting that jbig.tif file.  If it succeeds then the
> default is "true".  If it fails then the default is "send-only".  If JBIG-KIT is
> not on the system then it continues to be "false".
> 
> Any discussion on this?

I use all the elements that You mentioned: gentoo, ImageMagick, vanilla libtiff
and of course HylaFAX.

About two weeeks ago I came across the same problem. With Lee's help I disabled
JBIG support and that's it. However I didn't fill a bugzilla ticket - neither
at gentoo, nor at HylaFAX.

Autotools are magick for me and I do not wish for anyone to hack deep into
them. ;) Anyway the proposed configuration check is likely to do the trick.
-- 
tadeusz

____________________ 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@xxxxxxxxx*