Re: [Tiff] www.libtiff.org is restored

[Vincent Torri via Tiff]

On Sun, Feb 4, 2024 at 12:23 AM Leonard Rosenthol via Tiff
 wrote:
>
> There should be no reason for tiff2ps in 2024….but I agree that having a high 
> quality, open source, TIFF->PDF solution benefits everyone.
>
>
>
> Given the advances in PDF since the last time that tool was touched, it would 
> probably be more reasonable to see if we could partner up with some other 
> solution to keep that supported into the future.   Alternatively, maybe this 
> is an opportunity to improve the PDF output in something like GraphicsMagick 
> - Bob??

do you plan to use an external lib for pdf output, like poppler or mupdf ?

Vincent Torri


>
>
> Leonard
>
>
>
> From: Tiff  on behalf of miguel medalha via 
> Tiff 
> Date: Saturday, February 3, 2024 at 11:38 AM
> To: tiff@lists.osgeo.org 
> Subject: Re: [Tiff] www.libtiff.org is restored
>
> EXTERNAL: Use caution when clicking on links or opening attachments.
>
>
> > (...) It would be beneficial for his project (and others) if
> > the deprecated/removed libtiff utilities are restored (with security
> > fixes), if even as a different project from libtiff itself.
>
> I strongly agree, in particular the 'tiff2ps' and 'tiff2pdf' tools. They are
> immensely useful in the post-processing workflows of mass digitization of
> documents. I know no other tools with their exact capabilities.
>
>
> ___
> Tiff mailing list
> Tiff@lists.osgeo.org
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Ftiff=05%7C02%7Clrosenth%40adobe.com%7C09c8485d8bbf42e3fd5608dc24d68ea4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C638425751137804299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=tClsdKM1iJpp5rL3JPnZQ3lnHqNQgwWRcAAAmwDtDKI%3D=0
>
> ___
> 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

Re: [Tiff] www.libtiff.org is restored

[miguel medalha via Tiff]

> There should be no reason for tiff2ps in 2024….but I agree that having a
high quality, open source, TIFF->PDF solution benefits everyone.

I can agree with that and I think that the effort should be on tiff2pdf.

> Given the advances in PDF since the last time that tool was touched, it
would probably be more 
> reasonable to see if we could partner up with some other solution to keep
that supported into the future.   
> Alternatively, maybe this is an opportunity to improve the PDF output in
something like GraphicsMagick - Bob??

As they are now, neither ImageMagick nor GraphicsMagick are a match for the
functionality of tiff2pdf. Having easy control over the image position on
the page (i.e. page size and horizontal and vertical offsets) and
Distiller-like capabilities, such as inclusion of notes, bookmarks, and
metadata in general, on the fly are essential for my kind of work. Speed is
also important when processing thousands of pages.
 

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

Re: [Tiff] www.libtiff.org is restored

[Paul Hemmer via Tiff]

Thank you all for this. I’m a lurker, but have followed this saga all along.
Paul



On Feb 3, 2024, at 6:28 PM, Patrice Fournier via Tiff  
wrote:



Hi Bob,

On 2024-02-03 10:00, Bob Friesenhahn via Tiff wrote:
Lee Howard has managed to acquire the libtiff.org domain (with great effort and 
expense to himself).

That's an excellent news! Thanks Lee!


On 2024-02-03 11:15, Bob Friesenhahn via Tiff wrote:

We should keep in mind that Lee Howard is a maintainer of Hylafax, which is now 
broken given latest libtiff due to many libtiff utilities being removed.  It 
would be beneficial for his project (and others) if the deprecated/removed 
libtiff utilities are restored (with security fixes), if even as a different 
project from libtiff itself.

This would be really helpful indeed! I was already looking at my teams (iFAX 
Solutions (HylaFAX Enterprise and HylaFAX), but also T38Fax which uses these 
tools internally) to spare some time to work on this, but first, we'll need to 
know where to work on this and where to handle the issues. We'd personally 
prefer it be in the libtiff project, either in the main project, master branch 
or at minimum a separate branch from which (security issues) fixed tools are 
merged back into master. This would require all tools bugs to be restored and 
`wontfix-unmaintained` tags changed to `tools` or something like that, from 
which we could identify/label security issues and know which ones to 
concentrate on for this task (and the main libtiff team could exclude in their 
buglist if they so prefer, until we made enough progress).

Working in a separate project under the libtiff group or a separate one (I got 
`libtiff-tools` just in case) would allow giving rights to different people 
from the main project and have the bugs completely separated if that is 
preferred. And if it's a fork of the main project, still makes for easy merge 
requests so the fixes makes it to the main project. Adding that layer would 
complicate things when it's time to report bugs to tools though, especially 
when some tools bugs need to go to the main project and not others.

Is the libtiff team willing to have a group of helpers come on board to work on 
tools issues inside the libtiff project so we can restore these tools and 
willing to restore tools to build automatically inside the main libtiff 
project?  (So at first, restore the issues  that have been closed so we can 
work on this and agree to get tools back inside the main project?) If the goal 
is to not burden the current team with these issues, then we'd need to create a 
tools team to triage these bugs, add labels, close them, etc., so that would 
require at minimum some reporter level users. Might also need some developer to 
merge the fixes unless the main team is willing to accept that role.


P.S. http://libtiff.org/ doesn't redirect like http://www.libtiff.org/ does. It 
shows the main Simple Systems web page.


Regards,

--
Patrice Fournier
iFAX Solutions, Inc.
http://www.ifax.com/


___
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

Re: [Tiff] www.libtiff.org is restored

[Patrice Fournier via Tiff]

Hi Bob,

On 2024-02-03 10:00, Bob Friesenhahn via Tiff wrote:
Lee Howard has managed to acquire the libtiff.org domain (with great 
effort and expense to himself).


That's an excellent news! Thanks Lee!


On 2024-02-03 11:15, Bob Friesenhahn via Tiff wrote:

We should keep in mind that Lee Howard is a maintainer of Hylafax, 
which is now broken given latest libtiff due to many libtiff utilities 
being removed.  It would be beneficial for his project (and others) if 
the deprecated/removed libtiff utilities are restored (with security 
fixes), if even as a different project from libtiff itself.


This would be really helpful indeed! I was already looking at my teams 
(iFAX Solutions (HylaFAX Enterprise and HylaFAX), but also T38Fax which 
uses these tools internally) to spare some time to work on this, but 
first, we'll need to know where to work on this and where to handle the 
issues. We'd personally prefer it be in the libtiff project, either in 
the main project, master branch or at minimum a separate branch from 
which (security issues) fixed tools are merged back into master. This 
would require all tools bugs to be restored and `wontfix-unmaintained` 
tags changed to `tools` or something like that, from which we could 
identify/label security issues and know which ones to concentrate on for 
this task (and the main libtiff team could exclude in their buglist if 
they so prefer, until we made enough progress).


Working in a separate project under the libtiff group or a separate one 
(I got `libtiff-tools` just in case) would allow giving rights to 
different people from the main project and have the bugs completely 
separated if that is preferred. And if it's a fork of the main project, 
still makes for easy merge requests so the fixes makes it to the main 
project. Adding that layer would complicate things when it's time to 
report bugs to tools though, especially when some tools bugs need to go 
to the main project and not others.


Is the libtiff team willing to have a group of helpers come on board to 
work on tools issues inside the libtiff project so we can restore these 
tools and willing to restore tools to build automatically inside the 
main libtiff project?  (So at first, restore the issues  that have been 
closed so we can work on this and agree to get tools back inside the 
main project?) If the goal is to not burden the current team with these 
issues, then we'd need to create a tools team to triage these bugs, add 
labels, close them, etc., so that would require at minimum some reporter 
level users. Might also need some developer to merge the fixes unless 
the main team is willing to accept that role.



P.S. http://libtiff.org/ doesn't redirect like http://www.libtiff.org/ 
does. It shows the main Simple Systems web page.



Regards,

--
Patrice Fournier
iFAX Solutions, Inc.
http://www.ifax.com/
___
Tiff mailing list
Tiff@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/tiff

Re: [Tiff] www.libtiff.org is restored

[Leonard Rosenthol via Tiff]

There should be no reason for tiff2ps in 2024….but I agree that having a high 
quality, open source, TIFF->PDF solution benefits everyone.

Given the advances in PDF since the last time that tool was touched, it would 
probably be more reasonable to see if we could partner up with some other 
solution to keep that supported into the future.   Alternatively, maybe this is 
an opportunity to improve the PDF output in something like GraphicsMagick - 
Bob??

Leonard

From: Tiff  on behalf of miguel medalha via Tiff 

Date: Saturday, February 3, 2024 at 11:38 AM
To: tiff@lists.osgeo.org 
Subject: Re: [Tiff] www.libtiff.org is restored
EXTERNAL: Use caution when clicking on links or opening attachments.


> (...) It would be beneficial for his project (and others) if
> the deprecated/removed libtiff utilities are restored (with security
> fixes), if even as a different project from libtiff itself.

I strongly agree, in particular the 'tiff2ps' and 'tiff2pdf' tools. They are
immensely useful in the post-processing workflows of mass digitization of
documents. I know no other tools with their exact capabilities.


___
Tiff mailing list
Tiff@lists.osgeo.org
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Ftiff=05%7C02%7Clrosenth%40adobe.com%7C09c8485d8bbf42e3fd5608dc24d68ea4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C638425751137804299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=tClsdKM1iJpp5rL3JPnZQ3lnHqNQgwWRcAAAmwDtDKI%3D=0
___
Tiff mailing list
Tiff@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/tiff

Re: [Tiff] www.libtiff.org is restored

[miguel medalha via Tiff]

> (...) It would be beneficial for his project (and others) if 
> the deprecated/removed libtiff utilities are restored (with security 
> fixes), if even as a different project from libtiff itself.

I strongly agree, in particular the 'tiff2ps' and 'tiff2pdf' tools. They are
immensely useful in the post-processing workflows of mass digitization of
documents. I know no other tools with their exact capabilities.


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

Re: [Tiff] www.libtiff.org is restored

[Bob Friesenhahn via Tiff]

On Sat, 3 Feb 2024, Even Rouault wrote:


Hi Bob,

(by the way I had to manually accept your message. You should probably 
(re?)register your email)


Done.  I forgot that I changed my email address when I was away on a 
three week trip and there was a partial network outage.  Now I am 
subscribed twice.


This is excellent news ! Thanks for sharing it! Would it be possible that 
libtiff.org just redirects to https://libtiff.gitlab.io/libtiff/, which will 
probably have better scalability ? But that's nitpicking. Having got control 
back is the main thing. Thanks to Lee!


I have added the redirection for "http://www.libtiff.org/;, but 
retained "http://www.simplesystems.org/libtiff/;, for redundancy 
purposes.  Since Lee Howard is in charge of this domain, he is free to 
make any changes to it later, such as change it to a dedicated server.


We should keep in mind that Lee Howard is a maintainer of Hylafax, 
which is now broken given latest libtiff due to many libtiff utilities 
being removed.  It would be beneficial for his project (and others) if 
the deprecated/removed libtiff utilities are restored (with security 
fixes), if even as a different project from libtiff itself.


Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt
___
Tiff mailing list
Tiff@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/tiff

Re: [Tiff] www.libtiff.org is restored

[Even Rouault via Tiff]

Hi Bob,

(by the way I had to manually accept your message. You should probably 
(re?)register your email)


This is excellent news ! Thanks for sharing it! Would it be possible 
that libtiff.org just redirects to https://libtiff.gitlab.io/libtiff/, 
which will probably have better scalability ? But that's nitpicking. 
Having got control back is the main thing. Thanks to Lee!


Even

Le 03/02/2024 à 16:00, Bob Friesenhahn via Tiff a écrit :
Lee Howard has managed to acquire the libtiff.org domain (with great 
effort and expense to himself).


The libtiff.org domain was hijacked many years ago, and since then it 
has only provided stale pages for an archaic version of libtiff.


Now "http://www.libtiff.org/; leads to the latest libtiff HTML pages, 
and the same server/directory which already provides 
"http://www.simplesystems.org/libtiff/;.


This is still a server with limited bandwidth which runs out of a 
server closet in my residence.  Please treat it kindly!


Bob


--
http://www.spatialys.com
My software is free, but my time generally not.

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

[Tiff] www.libtiff.org is restored

[Bob Friesenhahn via Tiff]

Lee Howard has managed to acquire the libtiff.org domain (with great 
effort and expense to himself).


The libtiff.org domain was hijacked many years ago, and since then it 
has only provided stale pages for an archaic version of libtiff.


Now "http://www.libtiff.org/; leads to the latest libtiff HTML pages, 
and the same server/directory which already provides 
"http://www.simplesystems.org/libtiff/;.


This is still a server with limited bandwidth which runs out of a 
server closet in my residence.  Please treat it kindly!


Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt
___
Tiff mailing list
Tiff@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/tiff