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

Re: Bug#275897: ITP: tiff2png -- TIFF to PNG converter with alpha channel (transparency) support

Steinar H. Gunderson [u] wrote on 10/10/2004 23:41:

On Sun, Oct 10, 2004 at 04:27:21PM -0500, John Goerzen wrote:

This package can convert a TIFF image directly to a PNG image without
the need of any intermediary format.  Unlike the netpbm package,
this program can preserve transparency information during the

What's the gain of this over "convert file.tiff file.png"?

I had the same question in mind ;-)
One thing I can see: It's smaller and therefore probably less error prone. However, a note on the upstream homepage made me think even more:

This can lead to the inadvertent loss of source files, at least on Unix
>>> systems (where the shell would expand ``tiff2png *.tiff'' into a list
>>> of actual filenames, the second of which would be treated by tiff2png
>>> as the output filename).
[Note that the issue of overwriting files is _not_ the problem with upstream 0.91]

What makes me think is the fact that if given numerous filenames on the commandline, the programm takes the second one as the output filename (and probably ignores the rest). IMHO (IANADD), this should be fixed before this program enters the archive. There are two options of how to fix it _if_ it is accepted into the archive:
1) Bail out if more than two filenames are given
2) (which I would prefer) Take all the filenames, loop over them and
   use inputfilename (minus /\.tif+//) plus .png as output filenames

However, if I have the software on a computer to create tiffs with transparency, I see no reason to use tiff2png in favor of ImageMagick/convert, especially as the latter has been around for years and is pretty well tested.


Reply to: