2016.12.13 23:19 "Re: [Tiff] one_little_ill-advised_change_in_v4.0.7_brok e_functionality_for_HylaFAX", by
Od: Lee Howard <email@example.com>
Datum: 13. 12. 2016 19:55:04
It has its own copy of tif_fax3.h (which includes TIFFFaxTabEnt)...
Again, I have no doubt whatsoever that this could all be done cleaner/ better. I'm just saying that it is what it is.
OK, I'll revert that with a prominent warning so that the next one that
touches this code is aware of those tricky aspects that cannot be
anticipated from libtiff code itself.
Thanks. you want to provide a code change for HylaFAX then I'm happy to consider it. If
In my opinion that'd be better, as at this point affected users will need to upgrade *something*. Given that hylafax includes a "fork" of tif_fax3.h, it should also include a fork of tif_fax3sm.c, not import the tables (which are arguably leaked implementation detail) from libtiff.