[Tiff] Archive out of date?

2023-09-14 Thread L. E. Segovia via Tiff
Hey all,

I was trying to get a link to a thread for a friend, and in 
https://www.awaresystems.be/imaging/tiff/tml/recentthreads.html the last 
updated date is two months ago (11 July).

Are there any known issues with it?

Best,

amyspark

-- 
amyspark  https://www.amyspark.me


___
Tiff mailing list
Tiff@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/tiff


Re: [Tiff] libtiff 4.6.0 is released

2023-09-14 Thread William Bader
> William – are you (and others) still working with a PS-based workflow?  Why 
> not move to something more modern (aka PDF)?

I have a print publishing system that is a few million lines of code with a 
composition engine with comments that go back to 1982. It does all of the work 
in eps, and then we use ghostscript to convert the final output to pdf. 
Rewriting it to be pdf-based is too much work for too little return.


___
Tiff mailing list
Tiff@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/tiff


Re: [Tiff] libtiff 4.6.0 is released

2023-09-14 Thread miguel medalha
> > I am really unclear on whether there will be fallout from tools removal.


> I have scripts that use tiff2ps. ImageMagick can convert tiffs to ps, but
some versions of ImageMagick shift or scale the image. tiff2ps works.

> I think that with a ps-based workflow, tiff2ps is the best tools to
convert tiffs to eps.


I agree and I would extend the above considerations to tiff2pdf.

 

>> I don't mind building tiff2ps from source, but I'm hoping that if
something breaks, patches to tiff2ps.c will be accepted.

I would say the same, extending it to tiff2pdf again. Instead of killing the
tools, invite people to address their problems and accept the eventual
patches. Meaning, be willing to move the tools from "unsupported" to "tools"
again if support arises.

 

___
Tiff mailing list
Tiff@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/tiff


Re: [Tiff] libtiff 4.6.0 is released

2023-09-14 Thread miguel medalha
 

>> William - are you (and others) still working with a PS-based workflow?
Why not move ot something more modern (aka PDF)?

 

I may even agree with that somewhat, but tiff2pdf was also deprecated. And
don't point me to ImageMagick and such like, it's not the same thing, some
of the functionality or mode of working of tiff2pdf cannot be found
elsewhere that I know of.

___
Tiff mailing list
Tiff@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/tiff


Re: [Tiff] libtiff 4.6.0 is released

2023-09-14 Thread Leonard Rosenthol via Tiff
William – are you (and others) still working with a PS-based workflow?  Why not 
move ot something more modern (aka PDF)?

As evidenced by Apple removing support from their latest OS platforms – the 
technology has not evolve with time and should really be left as a legacy 
solution.  It is not entirely secure and, of course, is proprietary (from my 
company, but still).

I support the deprecation of tiff2ps…

Leonard

From: Tiff  on behalf of William Bader 

Date: Wednesday, September 13, 2023 at 8:25 PM
To: Greg Troxel , Even Rouault 
Cc: tiff@lists.osgeo.org 
Subject: Re: [Tiff] libtiff 4.6.0 is released

EXTERNAL: Use caution when clicking on links or opening attachments.


> I am really unclear on whether there will be fallout from tools removal.

I have scripts that use tiff2ps. ImageMagick can convert tiffs to ps, but some 
versions of ImageMagick shift or scale the image. tiff2ps works.
I think that with a ps-based workflow, tiff2ps is the best tools to convert 
tiffs to eps.
I don't mind building tiff2ps from source, but I'm hoping that if something 
breaks, patches to tiff2ps.c will be accepted.
William


From: Tiff  on behalf of Greg Troxel 

Sent: Wednesday, September 13, 2023 3:26 PM
To: Even Rouault 
Cc: tiff@lists.osgeo.org 
Subject: Re: [Tiff] libtiff 4.6.0 is released

Even Rouault  writes:

> I've promoted rc2 as the final 4.6.0 release.

Thanks for all your efforts on tiff.

> Read about this release at
> https://libtiff.gitlab.io/libtiff/releases/v4.6.0.html
>
> Pay attention to the following warning:
>
> This version removes a big number of utilities that have suffered
> from lack of maintenance over the years and were the source of
> various reported security issues.  See "Removed functionality"
> below for the list of removed utilities.  Starting with libtiff
> v4.6.0, their source code, at this time, will still be available
> in the source distribution, but they will no longer be built by
> default, and issues related to them will no longer be accepted in
> the libtiff bug tracker.  The only remaining supported TIFF tools
> are tiffinfo, tiffdump, tiffcp, tiffset and tiffsplit.

Because of where pkgsrc is on its quarterly release schedule -- going
into freeze in just under 6 days for the next branch -- I have decided
to defer updating until just after the branch.  This is an FYI not a
complaint; release cycles are just like this.

I don't see any urgent security fixes, but please let me know if I read
that wrong.  If so, it may be better to take the pain during the branch.

I am really unclear on whether there will be fallout from tools removal.
Again not a complaint; I just don't like surprises.  My expectation is
very little to maybe none, and that if so it will be run time not
build/install/package time.  So if anyone updates tiff in a packaging
system, and does or doesn't find issues, I would appreciate a note here
from fellow packagers.  I'll post myself after updating.

Thanks,
Greg
___
Tiff mailing list
Tiff@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/tiff
___
Tiff mailing list
Tiff@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/tiff