Hello community, here is the log from the commit of package netpbm for openSUSE:Factory checked in at 2015-05-20 23:34:44 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/netpbm (Old) and /work/SRC/openSUSE:Factory/.netpbm.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Package is "netpbm" Changes: -------- --- /work/SRC/openSUSE:Factory/netpbm/netpbm.changes 2014-11-24 11:18:28.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.netpbm.new/netpbm.changes 2015-05-20 23:34:46.000000000 +0200 @@ -1,0 +2,33 @@ +Mon May 11 14:46:14 UTC 2015 - pgajdos@suse.com + +- updated to 10.70.4 + * pambackground: fix bug: segfault or incorrect results in most + cases. + * ppmtoarbtxt: Fix some undefined behavior when program limits + are exceeded. + * anytopnm: convert all images in a multi-image GIF instead of + just the first. + * nmnorm: add -bsingle, -wsingle. + * pamtosvg: fix use of unset variable; probably results in a + crash. + * pnmgamma -srgbtobt709, -bt709tosrgb: fix bug; incorrect output + nearly always. + * pamtilt: fix bug: unconditional crash. + * pgmmorphconv: fix bug: always produces PGM Plain format. + * giftopnm: Fix bug: crashes if purported GIF has neither a global + color map nor a local one. + * pgmmorphconv: add -gradient. + * pnmhisteq: add -noblack and -nowhite. + * tifftopnm: allow input file to be nonseekable. + * Add yuy2topam. + * Add pgmtosbig. + * Add st4topgm, pgmtost4. + * ppmtoarbtxt: fix bug: wrong output when high numbers represent + darker. + * ppmtorgb3: Fix buffer overflow with long input file name. + * st4topgm: Fix bug: with no argument, uses file named "'" instead + of Standard Input. + * pnmconvol: Fix bug: wrong output for pixels that convolve to + negative values (should be clipped to zero). + +------------------------------------------------------------------- Old: ---- netpbm-10.68.1-documentation.tar.bz2 netpbm-10.68.1-nohpcdtoppm-noppmtompeg.tar.bz2 New: ---- netpbm-10.70.4-documentation.tar.bz2 netpbm-10.70.4-nohpcdtoppm-noppmtompeg.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ netpbm.spec ++++++ --- /var/tmp/diff_new_pack.YZ1yVH/_old 2015-05-20 23:34:47.000000000 +0200 +++ /var/tmp/diff_new_pack.YZ1yVH/_new 2015-05-20 23:34:47.000000000 +0200 @@ -1,7 +1,7 @@ # # spec file for package netpbm # -# Copyright (c) 2014 SUSE LINUX Products GmbH, Nuernberg, Germany. +# Copyright (c) 2015 SUSE LINUX GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -17,11 +17,11 @@ %define libmaj 11 -%define libmin 68 +%define libmin 70 %define libver %{libmaj}.%{libmin} Name: netpbm -Version: 10.68.1 +Version: 10.70.4 Release: 0 Summary: A Powerful Graphics Conversion Package License: BSD-3-Clause and GPL-2.0+ and IJG and MIT and SUSE-Public-Domain ++++++ netpbm-10.68.1-documentation.tar.bz2 -> netpbm-10.70.4-documentation.tar.bz2 ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/directory.html new/netpbm.sourceforge.net/doc/directory.html --- old/netpbm.sourceforge.net/doc/directory.html 2014-07-29 03:59:32.000000000 +0200 +++ new/netpbm.sourceforge.net/doc/directory.html 2015-03-10 23:26:01.000000000 +0100 @@ -474,6 +474,15 @@ <DT><B><a href=sbigtopgm.html>sbigtopgm</a> </B> <DD>convert Santa Barbara Instrument Group CCD file to PGM +<DT><B><a href=pgmtosbig.html>pgmtosbig</a> </B> +<DD>convert PGM to Santa Barbara Instrument Group CCD file + +<DT><B><a href=st4topgm.html>st4topgm</a> </B> +<DD>convert Santa Barbara Instrument Group ST-4 camera CCD file to PGM + +<DT><B><a href=pgmtost4.html>pgmtost4</a> </B> +<DD>convert PGM to Santa Barbara Instrument Group ST-4 camera CCD file + <DT><B><a href=pnmtosgi.html>pnmtosgi</a></B> <DD>convert from Netpbm formats to SGI format @@ -590,6 +599,9 @@ <DT><B><a href=yuvsplittoppm.html>yuvsplittoppm</a> </B> <DD>merge 3 subsampled raw YUV files to one PPM +<DT><B><a href=yuv2topam.html>yuy2topam</a> </B> +<DD>convert YUY2 format to PAM + <DT><B><a href=zeisstopnm.html>zeisstopnm</a></B> <DD>convert a Zeiss confocal file to Netpbm format @@ -1091,7 +1103,7 @@ <LI><b><a href=pnmfile.html>pnmfile</a></b> <LI><b><a href=pnmarith.html>pnmarith</a></b> <LI><b><a href=pgmedge.html>pgmedge</a></b> -<LI><b><a href=ppmtouil.html>ppmtoouil</a></b> +<LI><b><a href=ppmtouil.html>ppmtouil</a></b> <LI><b><a href=pnmtoplainpnm.html>pnmtoplainpnm</a></b> <LI><b><a href=pnmflip.html>pnmflip</a></b> <LI><b><a href=pnmtofits.html>pnmtofits</a></b> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/libnetpbm_image.html new/netpbm.sourceforge.net/doc/libnetpbm_image.html --- old/netpbm.sourceforge.net/doc/libnetpbm_image.html 2013-12-08 00:53:26.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/libnetpbm_image.html 2015-01-20 04:19:07.000000000 +0100 @@ -127,6 +127,17 @@ format codes then there are format types because there are different format codes for the plain and raw subformats of each format. +<p>Macros for the tuple types that are defined by Netpbm are as follows. +See the <i>tuple_type</i> member of the <b>pam</b> structure</a>. +<UL> +<LI><b>PAM_PBM_TUPLETYPE</b> +<LI><b>PAM_PGM_TUPLETYPE</b> +<LI><b>PAM_PPM_TUPLETYPE</b> +<LI><b>PAM_PBM_ALPHA_TUPLETYPE</b> +<LI><b>PAM_PGM_ALPHA_TUPLETYPE</b> +<LI><b>PAM_PPM_ALPHA_TUPLETYPE</b> +</UL> <H2 id="functions">Functions</H2> @@ -258,10 +269,9 @@ <P><B>pnm_readpam()</B> reads an entire image from a PAM or PNM image file and allocates the space in which to return the raster. It expects to find the file positioned to the first byte of the image and -leaves it positioned just after the image. <P> The function does not -require <B>*</B><I>pamP</I> to have any of its members set and sets -them all. <I>size</I> is the storage size in bytes of the -<B>*</B><I>pamP</I> structure, normally <B>sizeof(struct pam)</B>. +leaves it positioned just after the image. + +<P><B>*</B><I>pamP</I> is the same as for <b>pnm_readpaminit()</b>. <P>The return value is a newly allocated array of the rows of the image, with the top row being Element 0 of the array. Each row is represented diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/libnetpbm_ug.html new/netpbm.sourceforge.net/doc/libnetpbm_ug.html --- old/netpbm.sourceforge.net/doc/libnetpbm_ug.html 2013-02-20 04:30:31.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/libnetpbm_ug.html 2015-01-20 04:01:17.000000000 +0100 @@ -104,11 +104,25 @@ functions depend. So you are free to access or set the elements of the structure however you want. But you will find in most cases it is most convenient to call <B>pnm_readpaminit()</B> or -<B>pnm_writepaminit()</B> to set the fields in the <B>pam</B> +<B>pnm_writepaminit()</B> to set the members in the <B>pam</B> structure before calling any other pam functions, and then just to pass the structure unchanged in all future calls to pam functions. -<P>The fields are: +<p>It depends upon the function to which you pass the structure what members +are inputs, what members are outputs, and what members are irrelevant. + +<p>It is possible for a <b>pam</b> structure <em>not to specify</em> some +members, by operation of its <b>len</b> member. When you supply a <b>pam</b> +structure as an argument to a function, the function has default behavior +defined for unspecified members. All the functions require that you specify +at least up through <b>maxval</b>, and some require more. + +<p>Likewise, a function the returns a <b>pam</b> structure can return only +a subset of the members defined here, according to its setting of the +<b>len</b> member. But this normally happens only because the library is old +and predates the existence of the omitted members. + +<P>The members are: <DL COMPACT> <DT><B>size</B> @@ -129,9 +143,42 @@ <DT><B>format</B> -<DD>The format code of the image. This is <B>PAM_FORMAT</B> -unless the PAM image is really a view of a PBM, PGM, or PPM image. -Then it's <B>PBM_FORMAT</B>, <B>RPBM_FORMAT</B>, etc. +<DD>The format code of the image, which tells which of the various Netpbm +image formats is being processed. The following macros stand for those +format codes: + +<dl> + +<dt><b>PAM_FORMAT</b> + +<dd>PAM + +<dt><b>RPBM_FORMAT</b> + +<dd>raw PBM format + +<dt><b>RPGM_FORMAT</b> + +<dd>raw PGM format + +<dt><b>RPPM_FORMAT</b> + +<dd>raw PPM format + +<dt><b>PBM_FORMAT</b> + +<dd>plain PBM format + +<dt><b>PGM_FORMAT</b> + +<dd>plain PGM format + +<dt><b>PPM_FORMAT</b> + +<dd>plain PPM format + +</dl> + <p> There is an important quirk in the meaning of this member when you use the pam structure to write an image: Only the type portion of it is @@ -175,7 +222,7 @@ difficult to write backward compatible programs. Before Netpbm 10.32, it affected reading as well as writing. <p> -<b>libnetpbm</b> image reading functions set this field to false, for your +<b>libnetpbm</b> image reading functions set this member to false, for your convenience in building an output image pam from an input image pam. <DT><B>height</B> @@ -204,10 +251,26 @@ <DT><B>tuple_type</B> <DD>The tuple type of the image. See definitions in pam</A>. Netpbm does not define any values for this -except the following, which are used for a PAM image which is really a -view of a PBM, PGM, or PPM image: <B>PAM_PBM_TUPLETYPE</B>, -<B>PAM_PGM_TUPLETYPE</B>, <B>PAM_PPM_TUPLETYPE</B>. +HREF="pam.html">pam</A>. Netpbm defines values for the most common +types of visual images, but any value is legal. There are macros for +these values: + +<dl> +<dt><b>PAM_PBM_TUPLETYPE</b> +<dd>black and white image, such as would alternatively be represented by a PBM +image. +<dt><b>PAM_PGM_TUPLETYPE</b> +<dd>grayscale image, such as would alternatively be represented by a PGM +image. +<dt><b>PAM_PPM_TUPLETYPE</b> +<dd>color image, such as would alternatively be represented by a PPM image. +<dt><b>PAM_PBM_ALPHA_TUPLETYPE</b> +<dd>black and white with a transparency (alpha) information. +<dt><b>PAM_PGM_ALPHA_TUPLETYPE</b> +<dd>grayscale with a transparency (alpha) information. +<dt><b>PAM_PPM_ALPHA_TUPLETYPE</b> +<dd>color with a transparency (alpha) information. +</dl> <DT><B>allocation_depth</B> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pam.html new/netpbm.sourceforge.net/doc/pam.html --- old/netpbm.sourceforge.net/doc/pam.html 2014-11-15 04:41:04.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/pam.html 2015-01-20 03:35:44.000000000 +0100 @@ -216,32 +216,30 @@ as are typically represented by images in the older and more concrete PBM, PGM, and PPM formats. -<h4>Black And White (PBM)</h4> +<h4>Black And White</h4> -<P>A black and white image, such as would be represented by a PBM -image, has a tuple type of "BLACKANDWHITE". Such a PAM image -has a depth of 1 and maxval 1 where the one sample in each tuple is 0 -to represent a black pixel and 1 to represent a white one. The -height, width, and raster bear the obvious relationship to those of -the equivalent PBM image. +<P>A black and white image, such as would alternatively be represented by a +PBM image, has a tuple type of "BLACKANDWHITE". Such a PAM image has a depth +of 1 and maxval 1 where the one sample in each tuple is 0 to represent a black +pixel and 1 to represent a white one. The height, width, and raster bear the +obvious relationship to those of the equivalent PBM image. <P>Note that in the PBM format, a zero value means white, but in PAM, zero means black. -<h4>Grayscale (PGM)</h4> +<h4>Grayscale</h4> -<P>A grayscale image, such as would be represented by a PGM image, has -a tuple type of "GRAYSCALE". Such a PAM image has a depth of 1. The -maxval, height, width, and raster bear the obvious relationship to -those of the equivalent PGM image. - -<h4>Color (PPM)</h4> - -<P>A color image, such as would be represented by a PPM image, has a -typle type of "RGB". Such a PAM image has a depth of 3. The maxval, -height, width, and raster bear the obvious relationship to those of -the PPM image. The first plane represents red, the second green, and -the third blue. +<P>A grayscale image, such as would alternativelybe represented by a PGM +image, has a tuple type of "GRAYSCALE". Such a PAM image has a depth of 1. +The maxval, height, width, and raster bear the obvious relationship to those +of the equivalent PGM image. + +<h4>Color</h4> + +<P>A color image, such as would alternatively be represented by a PPM image, +has a typle type of "RGB". Such a PAM image has a depth of 3. The maxval, +height, width, and raster bear the obvious relationship to those of the PPM +image. The first plane represents red, the second green, and the third blue. <h4>Transparent</h4> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pamarith.html new/netpbm.sourceforge.net/doc/pamarith.html --- old/netpbm.sourceforge.net/doc/pamarith.html 2013-12-19 18:01:51.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/pamarith.html 2015-01-03 18:14:53.000000000 +0100 @@ -3,7 +3,7 @@ <HEAD><TITLE>Pamarith User Manual</TITLE></HEAD> <BODY> <H1>pamarith</H1> -Updated: 08 April 2007 +Updated: 03 January 2015 <BR> <A HREF="#index">Table Of Contents</A> @@ -160,7 +160,7 @@ interprets sample values. See <a href="#maxval">Maxval</a>. <P><b>-divide</b> divides a value in the left input image by the value -in the left input image. But like <b>-multiply</b>, it tends to +in the right input image. But like <b>-multiply</b>, it tends to produce nonobvious results. Note that <b>pamarith</b> clipping behavior makes this of little use when the left argument (dividend) is greater than the right argument (divisor) -- the result in that case diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pambackground.html new/netpbm.sourceforge.net/doc/pambackground.html --- old/netpbm.sourceforge.net/doc/pambackground.html 2014-11-09 19:02:50.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/pambackground.html 2014-12-03 10:38:27.000000000 +0100 @@ -2,7 +2,7 @@ <HTML><HEAD><TITLE>Pambackground User Manual</TITLE></HEAD> <BODY> <H1>pambackground</H1> -Updated: 09 November 2014 +Updated: 24 November 2014 <BR> <A HREF="#index">Table Of Contents</A> @@ -59,6 +59,19 @@ 20% of "SkyBlue" to SkyBlue, then run <b>pambackground</b> on it. +<p>You might even extract the argument for <b>ppmchange</b> from the image in +question, using <b>ppmtoarbtxt</b>. In the foregoing example, we knew the +background was approximately SkyBlue, but if we didn't we could just get the +color of the top left pixel, in a form suitable for the color arguments +of <b>ppmchange</b> like this: + +<pre> +<kbd> + $ echo "#(fred)/#(fgreen)/#(fblue)" >/tmp/bodyskl + $ color=$(pamcut 0 0 1 1 myimage.ppm | ppmtoarbtxt /tmp/bodyskl) +</kbd> +</pre> + <p>A more convenient means of dealing with a multi-shade background is to use <b>pnmquant</b> to produce a version of the image with a very small number of colors. The background would likely then be all one color. @@ -114,14 +127,12 @@ <h2 id="examples">EXAMPLES</h2> -<p> <pre> <kbd> $ pambackground test.ppm | pnminvert >/tmp/bgmask.pgm $ pamcomp -alpha=bgmask.pgm test.ppm wallpaper.ppm >output.ppm </kbd> </pre> -<p> <pre> <kbd> $ pnmquant 5 test.pgm | pambackground test.ppm >/tmp/bgmask.pam diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pamcrater.html new/netpbm.sourceforge.net/doc/pamcrater.html --- old/netpbm.sourceforge.net/doc/pamcrater.html 2014-11-03 18:16:11.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/pamcrater.html 2014-12-06 19:40:49.000000000 +0100 @@ -32,6 +32,7 @@ [<b>-randomseed=</b><i>integer</i>] +[<b>-verbose</b>] <H2 id="description">DESCRIPTION</H2> @@ -88,7 +89,7 @@ <DL COMPACT> <DT><B>-number</B> <I>n</I> -<DD>Causes <b>pamcrater</b> to generate <I>n</I> craters. If you do not +<DD>This causes <b>pamcrater</b> to generate <I>n</I> craters. If you do not specify <B>-number</B>, it generates 50000 craters. Don't expect to see them all! For every large crater there are many, many more tiny ones which tend simply to erode the landscape. In general, the more craters you specify, the @@ -98,12 +99,12 @@ <DT><B>-height</B> <I>height</I> -<DD>Sets the height of the generated image to <I>height</I> pixels. +<DD>This sets the height of the generated image to <I>height</I> pixels. The default height is 256 pixels. <DT><B>-width</B> <I>width</I> -<DD>Sets the width of the generated image to <I>width</I> pixels. The +<DD>This sets the width of the generated image to <I>width</I> pixels. The default width is 256 pixels. <dt><b>-randomseed=</b><i>integer</i> @@ -119,6 +120,13 @@ <p>This option was new in Netpbm 10.61 (December 2012). +<dt><b>-verbose</b> + +<dd>This causes <b>pamcrater</b> to issue additional messages about what it +is doing. + +<p>This option was new in Neptbm 10.69 (December 2014). + </DL> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pamfunc.html new/netpbm.sourceforge.net/doc/pamfunc.html --- old/netpbm.sourceforge.net/doc/pamfunc.html 2014-02-14 05:32:10.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/pamfunc.html 2015-01-03 18:19:26.000000000 +0100 @@ -40,7 +40,7 @@ <p>This program is part of <a href="index.html">Netpbm</a>. <P><b>pamfunc</b> reads a Netpbm image as input and produces a Netpbm -image as output, with the same format, maxval, and dimensions as the +image as output, with the same format, and dimensions as the input. <b>pamfunc</b> applies a simple transfer function to each sample in the input to generate the corresponding sample in the output. The options determine what function. diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pgmdeshadow.html new/netpbm.sourceforge.net/doc/pgmdeshadow.html --- old/netpbm.sourceforge.net/doc/pgmdeshadow.html 2013-02-20 04:30:31.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/pgmdeshadow.html 2015-01-16 18:11:22.000000000 +0100 @@ -44,7 +44,7 @@ <ul> -<li>Luc Vincent, "Morphological Grayscale Reruction in Image +<li>Luc Vincent, "Morphological Grayscale Reconstruction in Image Analysis: Applications and Efficient Algorithms," IEEE Transactions on Image Processing, vol. 2, no. 2, April 1993, pp. 176-201. diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pgmmorphconv.html new/netpbm.sourceforge.net/doc/pgmmorphconv.html --- old/netpbm.sourceforge.net/doc/pgmmorphconv.html 2013-02-20 04:30:31.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/pgmmorphconv.html 2015-03-29 03:10:59.000000000 +0200 @@ -3,7 +3,7 @@ <HEAD><TITLE>Pgmmorphconv User Manual</TITLE></HEAD> <BODY> <H1>pgmmorphconv</H1> -Updated: 29 October 2002 +Updated: 29 March 2015 <BR> <A HREF="#index">Table Of Contents</A> @@ -14,7 +14,13 @@ <H2 id="synopsis">SYNOPSIS</H2> <B>pgmmorphconv</B> -[ <b>-erode</b> | <b>-dilate</b> | <b>-open</b> | <b>-close</b> ] +[ + <b>-erode</b> | + <b>-dilate</b> | + <b>-open</b> | + <b>-close</b> | + <b>-gradient</b> +] <I>templatefile</I> [<I>pgmfile</I>] @@ -68,6 +74,11 @@ erode. If you specify none of these options, it is the same as <b>-dilate</b>. +<p>With <b>-gradient</b>, <b>pgmmorphconv</b> produces an image which is the +difference between the eroded image and the dilated image. <b>-gradient</b> +was new in Netpbm 10.70 (March 2015). + + <H2 id="seealso">SEE ALSO</H2> <ul> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pgmtofs.html new/netpbm.sourceforge.net/doc/pgmtofs.html --- old/netpbm.sourceforge.net/doc/pgmtofs.html 2013-02-20 04:30:31.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/pgmtofs.html 2015-01-19 04:27:57.000000000 +0100 @@ -6,20 +6,17 @@ <BR> <A HREF="#index">Table Of Contents</A> -<A NAME="lbAB"> </A> <H2>NAME</H2> pgmtofs - convert PGM image to Usenix FaceSaver(tm) format -<A NAME="lbAC"> </A> -<H2>SYNOPSIS</H2> +<H2 id="synopsis">SYNOPSIS</H2> <B>pgmtofs</B> [<I>pgmfile</I>] -<A NAME="lbAD"> </A> -<H2>DESCRIPTION</H2> +<H2 id="description">DESCRIPTION</H2> <p>This program is part of <a href="index.html">Netpbm</a>. @@ -29,26 +26,22 @@ <P>FaceSaver is a registered trademark of Metron Computerware Ltd. of Oakland, CA. -<A NAME="lbAE"> </A> -<H2>SEE ALSO</H2> +<H2 id="seealso">SEE ALSO</H2> <A HREF="fstopgm.html">fstopgm</A>, <A HREF="pgm.html">pgm</A> -<A NAME="lbAF"> </A> -<H2>AUTHOR</H2> +<H2 id="author">AUTHOR</H2> Copyright (C) 1991 by Jef Poskanzer. <HR> -<A NAME="index"> </A> -<H2>Table Of Contents</H2> +<H2 id="index">Table Of Contents</H2> <UL> -<LI><A HREF="#lbAB">NAME</A> -<LI><A HREF="#lbAC">SYNOPSIS</A> -<LI><A HREF="#lbAD">DESCRIPTION</A> -<LI><A HREF="#lbAE">SEE ALSO</A> -<LI><A HREF="#lbAF">AUTHOR</A> +<LI><A HREF="#synopsis">SYNOPSIS</A> +<LI><A HREF="#description">DESCRIPTION</A> +<LI><A HREF="#seealso">SEE ALSO</A> +<LI><A HREF="#author">AUTHOR</A> </UL> </BODY> </HTML> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pgmtosbig.html new/netpbm.sourceforge.net/doc/pgmtosbig.html --- old/netpbm.sourceforge.net/doc/pgmtosbig.html 1970-01-01 01:00:00.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/pgmtosbig.html 2015-01-20 04:59:03.000000000 +0100 @@ -0,0 +1,60 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML><HEAD><TITLE>Pgmtosbig User Manual</TITLE></HEAD> +<BODY> +<H1>pgmtosbig</H1> +Updated: 18 January 2015 +<BR> +<A HREF="#index">Table Of Contents</A> + +<H2>NAME</H2> + +pgmtosbig - convert PGM image to SBIG format + +<H2 id="synopsis">SYNOPSIS</H2> + +<B>pgmtosbig</B> + +[<I>pgmfile</I>] + +<H2 id="description">DESCRIPTION</H2> + +<p>This program is part of <a href="index.html">Netpbm</a>. + +<p><b>pgmtosbig</b> reads a PGM image as input and produces a +Santa Barbara Instrument Group SBIG Type 3 image as output. + +<p>Note that this format is distinct from the SBIG ST-4 format. + +<ul> +<li>The image is uncompressed +<li>The image says it is from a "ST-6" camera +<li>The image header has these lines: +<ul> +<li>camera type +<li>height +<li>width +<li>saturation level +</ul> +</ul> + + +<H2 id="seealso">SEE ALSO</H2> + +<A HREF="sbigtopgm.html">sbigtopgm</A>, +<A HREF="pgm.html">pgm</A> + +<h2 id="history">HISTORY</h2> + +<p><b>pgmtosbig</b> was new in Netpbm 10.70, and was intended primarily as a +test tool for <b>sbigtopgm</b>. + +<HR> +<H2 id="index">Table Of Contents</H2> +<UL> +<LI><A HREF="#synopsis">SYNOPSIS</A> +<LI><A HREF="#description">DESCRIPTION</A> +<LI><A HREF="#seealso">SEE ALSO</A> +<LI><A HREF="#history">HISTORY</A> +</UL> +</BODY> +</HTML> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pgmtost4.html new/netpbm.sourceforge.net/doc/pgmtost4.html --- old/netpbm.sourceforge.net/doc/pgmtost4.html 1970-01-01 01:00:00.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/pgmtost4.html 2015-01-20 05:54:01.000000000 +0100 @@ -0,0 +1,62 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML><HEAD><TITLE>Pgmtost4 User Manual</TITLE></HEAD> +<BODY> +<H1>pgmtost4</H1> +Updated: 20 January 2015 +<BR> +<A HREF="#index">Table Of Contents</A> + +<H2>NAME</H2> + +pgmtost4 - convert PGM image to SBIG ST-4 format + +<H2 id="synopsis">SYNOPSIS</H2> + +<B>pgmtost4</B> + +[<I>pgmfile</I>] + +<H2 id="description">DESCRIPTION</H2> + +<p>This program is part of <a href="index.html">Netpbm</a>. + +<p><b>pgmtost4</b> reads a PGM image as input and produces a +Santa Barbara Instrument Group SBIG ST-4 camera CCD image as output. + +<p>Note that this format is distinct from the SBIG format used with mos +SBIG cameras. For that, see <b>pgmtosbig</b> + +<ul> +<li>The image is uncompressed +<li>The image says it is from a "ST-6" camera +<li>The image header has these lines: +<ul> +<li>camera type +<li>height +<li>width +<li>saturation level +</ul> +</ul> + + +<H2 id="seealso">SEE ALSO</H2> + +<A HREF="st4topgm.html">st4topgm</A>, +<A HREF="pgm.html">pgm</A> + + +<h2 id="history">HISTORY</h2> + +<p><b>pgmtosbig</b> was new in Netpbm 10.70, and was intended primarily as a +test tool for <b>sbigtopgm</b>. + +<HR> +<H2 id="index">Table Of Contents</H2> +<UL> +<LI><A HREF="#synopsis">SYNOPSIS</A> +<LI><A HREF="#description">DESCRIPTION</A> +<LI><A HREF="#seealso">SEE ALSO</A> +<LI><A HREF="#history">HISTORY</A> +</UL> +</BODY> +</HTML> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pnmhisteq.html new/netpbm.sourceforge.net/doc/pnmhisteq.html --- old/netpbm.sourceforge.net/doc/pnmhisteq.html 2013-12-08 01:01:37.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/pnmhisteq.html 2015-03-22 23:42:50.000000000 +0100 @@ -2,7 +2,7 @@ <HTML><HEAD><TITLE>Pnmhisteq User Manual</TITLE></HEAD> <BODY> <H1>pnmhisteq</H1> -Updated: 02 February 2010 +Updated: 22 March 2015 <BR> <A HREF="#index">Table Of Contents</A> @@ -16,6 +16,9 @@ [<B>-gray</B>] +[<B>-noblack</B>] +[<B>-nowhite</B>] + [<B>-rmap</B> <I>pgmfile</I>] [<B>-wmap</B> <I>pgmfile</I>] @@ -111,6 +114,27 @@ show continent outlines in color are best processed using this option. The option has no effect when the input is a graymap. +<DT><B>-noblack</B> + +<dd>Do not include black pixels in the equalization. The black pixels in the +output are exactly the black pixels in the input and the number of black +pixels does not affect the color of any other pixels. + +<p>Sometimes, black isn't as much a color as a background or annotation for +the real colors, so you want to treat it specially this way. Think of a +picture of stars, which is nearly all black, but with lots of stars of +different brightness. You want to change the brightnesses of the stars to +maximize contrast between them, but if you considered the blackness to be +significant, all the stars would end up close to full white. + +<p>This option was new in Netpbm 10.70 (March 2015). + +<DT><B>-nowhite</B> + +<p>Same as <b>-noblack</b>, but for the white pixels. + +<p>This option was new in Netpbm 10.70 (March 2015). + <DT><B>-rmap</B> <I>mapfile</I> <DD>Process the image using the luminosity map specified by the PGM diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pnmnorm.html new/netpbm.sourceforge.net/doc/pnmnorm.html --- old/netpbm.sourceforge.net/doc/pnmnorm.html 2013-12-08 01:02:10.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/pnmnorm.html 2014-12-19 04:07:10.000000000 +0100 @@ -2,27 +2,27 @@ <HTML><HEAD><TITLE>Pnmnorm User Manual</TITLE></HEAD> <BODY> <H1>pnmnorm</H1> -Updated: 6 January 2006 +Updated: 19 December 2014 <BR> <A HREF="#index">Table Of Contents</A> <H2>NAME</H2> -pnmnorm - normalize the contrast in a Netbpm image +pnmnorm - normalize the contrast in a Netpbm image <H2 id="synopsis">SYNOPSIS</H2> <B>pnmnorm</B> -[<B>-bpercent=</B><I>N</I> | <B>-bvalue=</B><I>N</I>] +[<B>-bpercent=</B><I>percent</I> | <B>-bvalue=</B><I>N</I> | <b>-bsingle</b>] -[<B>-wpercent=</B><I>N</I> | <B>-wvalue=</B><I>N</I>] +[<B>-wpercent=</B><I>percent</I> | <B>-wvalue=</B><I>N</I> | <b>-wsingle</b>] [<b>-midvalue=</b><i>N</i>] [<b>-middle=N</b>] -[<b>-maxexpand</b>] +[<b>-maxexpand=</b><i>percent</i>] [<B>-keephues</B>] @@ -90,7 +90,12 @@ <P>By default, the darkest 2 percent of all pixels are mapped to black, and the brightest 1 percent are mapped to white. You can -override these percentages by using the <B>-bpercent</B> and +override this behavior and specify either a different percentage, or +specific brightness values to map to black and to white, or just have +the single greatest brightness map to white and the least brightness map +to black. + +<p>To specify a percentage, use the <B>-bpercent</B> and <B>-wpercent</B> options, or you can specify the exact pixel values to be mapped by using the <B>-bvalue</B> and <B>-wvalue</B> options. You can get appropriate numbers for the options from @@ -151,6 +156,12 @@ much stretching means two adjacent pixels that used to differ in intensity by 4 units now differ by 10, and that might be unsightly. +<p>To specify that the single least brightness in the image should stretch to +black in the output, specify <b>-bsingle</b>. To specify that the single +greatest brightness in the image should stretch to white in the output, +specify <b>-wsingle</b>. <b>-bsingle</b> and <b>-wsingle</b> were new in +Netpbm 10.69 (December 2014). + <p>So that you can put a limit on the amount of expansion without having to examine the image first, there is the <b>-maxexpand</b> option. It specifies the maximum expansion you will tolerate, as an diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pnmpsnr.html new/netpbm.sourceforge.net/doc/pnmpsnr.html --- old/netpbm.sourceforge.net/doc/pnmpsnr.html 2013-02-20 04:30:31.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/pnmpsnr.html 2015-04-10 04:02:31.000000000 +0200 @@ -2,17 +2,15 @@ <HTML><HEAD><TITLE>Pnmpsnr User Manual</TITLE></HEAD> <BODY> <H1>pnmpsnr</H1> -Updated: 04 March 2001 +Updated: 10 April 2015 <BR> <A HREF="#index">Table Of Contents</A> -<A NAME="lbAB"> </A> <H2>NAME</H2> pnmpsnr - compute the difference between two images (the PSNR) -<A NAME="lbAC"> </A> -<H2>SYNOPSIS</H2> +<H2 id="synopsis">SYNOPSIS</H2> <B>pnmpsnr</B> @@ -20,8 +18,7 @@ [<I>pnmfile2</I>] -<A NAME="lbAD"> </A> -<H2>DESCRIPTION</H2> +<H2 id="description">DESCRIPTION</H2> <p>This program is part of <a href="index.html">Netpbm</a>. @@ -52,19 +49,21 @@ pixels is 100 times less than the maximum possible difference, i.e. 0.01. -<A NAME="lbAE"> </A> -<H2>SEE ALSO</H2> +<p>Note that the word "peak" is a misnomer; there is no maximum +involved; the metric is a mean. But "peak signal to noise ratio" is +for some reason the common term for this measurement. + + +<H2 id="seealso">SEE ALSO</H2> <B><A HREF="pnm.html">pnm</A></B> <HR> -<A NAME="index"> </A> -<H2>Table Of Contents</H2> +<H2 id="index">Table Of Contents</H2> <UL> -<LI><A HREF="#lbAB">NAME</A> -<LI><A HREF="#lbAC">SYNOPSIS</A> -<LI><A HREF="#lbAD">DESCRIPTION</A> -<LI><A HREF="#lbAE">SEE ALSO</A> +<LI><A HREF="#synopsis">SYNOPSIS</A> +<LI><A HREF="#description">DESCRIPTION</A> +<LI><A HREF="#seealso">SEE ALSO</A> </UL> </BODY> </HTML> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/ppmtoarbtxt.html new/netpbm.sourceforge.net/doc/ppmtoarbtxt.html --- old/netpbm.sourceforge.net/doc/ppmtoarbtxt.html 2013-02-20 04:30:31.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/ppmtoarbtxt.html 2014-12-15 17:51:17.000000000 +0100 @@ -3,7 +3,7 @@ <BODY> <H1>ppmtoarbtxt</H1> <BR> -Updated: 27 April 2003 +Updated: 26 November 2014 <BR> <A HREF="#index">Table Of Contents</A> @@ -13,9 +13,9 @@ <H2 id="synopsis">SYNOPSIS</H2> <B>ppmtoarbtxt</B> -<I>bodyskl</I> -[<B>-hd</B> <I>headskl</I>] -[<B>-tl</B> <I>tailskl</I>] +<I>bodytmpl</I> +[<B>-hd</B> <I>headtmpl</I>] +[<B>-tl</B> <I>tailtmpl</I>] [<I>ppmfile</I>] <H2 id="description">DESCRIPTION</H2> @@ -28,17 +28,63 @@ PNM raw format). <b>ppmtoarbtxt</b> reads a PPM image as input. For each pixel in the -image, <b>ppmtoarbtxt</b> writes the contents of the skeleton file -<I>bodyskl</I>, with certain substitutions based on the value of the -pixel, to stdout. The substitutions are as follows: +image, <b>ppmtoarbtxt</b> writes the contents of the template file +<I>bodytmpl</I>, with certain substitutions based on the value of the +pixel, to Standard Output. + +<p>You may also supply a head template file, in which case <b>ppmtoarbtxt</b> +generates text from the template file, based on the image dimensions, and +includes it in the output before anything else. + +<p>Likewise, you may supply a tail template file to cause text to be placed +at the end of the output. + + +<h3 id="templatefiles">Template Files</h3> + +<p>The text that <b>ppmtoarbtxt</b> generates from a template file is the +literal text of the template file, except with substitution specifier replaced +with something else. The program reecognizes a substitution specifier as +text of the form <b>#(</b>...<b>)</b>. + +<P><b>ppmtoarbtxt</b> treats white space in the template files the same as any +other characters, placing it in the output, with one exception: If the +template file ends with a newline character, <b>ppmtoarbtxt</b> ignores it -- +it does not include it in the output. + +<p>Many substitution specifiers use format strings (another form of template) +to specify the substitution. You should make these format strings as minimal +as possible, placing literal text outside the substitution specifier instead +of inside the format string. For example, + +<p>Wrong: <kbd>#(flum %%%2.2f 0 1) </kbd> + +<p>Right: <kbd>%#(flum %2.2f 0 1) </kbd> + +<p>The valid substitution specifiers are as follows. Text that has the +form of a substitution specifier but is not actually valid (e.g. +<b>#(random junk)</b> usually just specifies its literal value, but if it is +close enough to something valid, <b>ppmtoarbtxt</b> assumes you made a mistake +and fails. + +<p>Useful in a body template, to do substitutions based on a particular pixel: <DL COMPACT> <DT><B>#(ired</B><I> format blackref whiteref</I><B>)</B> <DD>generates an integer in the range <I>blackref</I> to -<I>whiteref</I> using <I>format</I> representing the red intensity of -the pixel. A red intensity of 0 becomes <I>blackref</I>; a red -intensity of maxval becomes <I>whiteref</I>. +<I>whiteref</I> in a format specified by <I>format</I> representing the red +intensity of the pixel. A red intensity of 0 becomes <I>blackref</I>; a red +intensity of maxval becomes <I>whiteref</I>, with the rest linearly +interpolated in between. + +<p><i>format</i> is a printf-like format specifier like "%d". +<b>ppmtoarbtxt</b> uses as the entire format string to a <b>fprintf</b> POSIX +library call whose only other argument is the red itensity as an integer data +type. <b>ppmtoarbtxt</b> does not necessarily verify that your format string +makes sense; there are values you could specify that could even crash the +program. To avoid unexpected behavior, keep format strings simple and +hardcoded, and never include a per cent sign or newline. <p><B>#(ired)</B> is equivalent to <B>#(ired %d 0 255)</B>. @@ -60,64 +106,76 @@ <DD>Same as <B>#(ired...</B>, but generates a floating point number instead of an integer. -<p> -<B>#(fred)</B> is equivalent to <B>#(fred %f 0.0 1.0)</B>. +<p>In this case, the second argument to the <b>fprintf</b> that uses +<i>format</i> has a double precision floating point data type. + +<p><B>#(fred)</B> is equivalent to <B>#(fred %f 0.0 1.0)</B>. -<DT><B>#(fgreen</B><I> format blackref whiteref</I><B>)</B> +<DT><B>#(fgreen </B><I>format blackref whiteref</I><B>)</B> <DD>Same as <B>#(fred...</B>, but for green. -<DT><B>#(fblue</B><I> format blackref whiteref</I><B>)</B> +<DT><B>#(fblue </B><I>format blackref whiteref</I><B>)</B> <DD>Same as <B>#(fred...</B>, but for blue. -<DT><B>#(flum</B><I> format blackref whiteref</I><B>)</B> +<DT><B>#(flum </B><I>format blackref whiteref</I><B>)</B> <DD>Same as <B>#(fred...</B>, but representing the luminance value (0.299*red + 0.587*green + 0.114*blue) of the pixel. +<DT><B>#(posx </B><i>format</i><b>)</b> -<DT><B>#(width)</B> +<DD>Generates the horizontal position of the pixel, in pixels from the left +edge of the image. -<DD>Generates the width in pixels of the image. +<p>The second argument to the <b>fprintf</b> that uses <i>format</i> has an +unsigned integer data type. -<DT><B>#(height)</B> +<p><i>format</i> defaults to <b>%u</b> -<DD>Generates the height in pixels of the image. +<DT><B>#(posy </B><i>format</i><b>)</b> +<DD>Same as <b>#(width...</b>, but for the vertical position. -<DT><B>#(posx)</B> +</DL> -<DD>Generates the horizontal position of the pixel, in pixels from the left -edge of the image. +<p>If you use any of the above substitution specifiers in a head or tail +template, the result is undefined. -<DT><B>#(posy)</B> +<p>Useful in a head or tail template, to do substitutions based on whole-image +attributes: -<DD>Generates the vertical position of the pixel, in pixels from the top -edge of the image. +<DL COMPACT> +<DT><B>#(width </B><i>format</i><b>)</b> -</DL> +<DD>Generates the width in pixels of the image. +<p>The second argument to the <b>fprintf</b> that uses <i>format</i> +has an unsigned integer data type. + +<p><i>format</i> defaults to <b>%u</b> + +<DT><B>#(height </B><i>format</i><b>)</b> + +<DD>Same as <b>#(width...</b>, but for the height of the image. + +</dl> -<P>If the skeleton file ends with a LF-character, <b>ppmtoarbtxt</b> -ignores it -- it does not include it in the output. <H2 id="options">OPTIONS</H2> <DL COMPACT> -<DT><B>-hd</B> <I>headskl</I> +<DT><B>-hd</B> <I>headtmpl</I> + +<DD>This option specifies a head template (<i>headtmpl</i> is the name of the +head template file); it causes <b>ppmtoarbtxt</b> to place the contents of the +file named <I>headtmpl</I> at the beginning of the output + +<DT><B>-tl</B> <I>tailtmpl</I> + +<DD>This option specifies a tail template; it is analogous to <b>-hd</b>. -<DD>This option causes <b>ppmtoarbtxt</b> to place the contents of -the file named <I>headskl</I> at the beginning of the output, before -the first pixel. It does the same substitutions as for -<I>bodyskl</I>, except substitutions based on a pixel value are -undefined. - -<DT><B>-tl</B> <I>tailskl</I> - -<DD>This option causes <b>ppmtoarbtxt</b> to place the contents of -the file named <i>tailskl</i> at the end of the output, after the -last pixel. It is analogous to <b>-hd</b>. </DL> <H2 id="examples">EXAMPLES</H2> @@ -127,7 +185,7 @@ <P>Here we generate a PGM plain-format image with gray inversion (like <b>ppmtopgm | pnminvert</b>). -<p>Contents of our head skeleton file: +<p>Contents of our head template file: <pre> P2 @@ -191,11 +249,13 @@ Copyright (C) 1995 by Peter Kirchgessner <HR> -<A NAME="index"> </A> -<H2>Table Of Contents</H2> +<H2 id="index">Table Of Contents</H2> <UL> <LI><A HREF="#synopsis">SYNOPSIS</A> <LI><A HREF="#description">DESCRIPTION</A> +<ul> + <li><A HREF="#templatefiles">Template Files</A> + </ul> <LI><A HREF="#options">OPTIONS</A> <LI><A HREF="#examples">EXAMPLES</A> <LI><A HREF="#seealso">SEE ALSO</A> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/sbigtopgm.html new/netpbm.sourceforge.net/doc/sbigtopgm.html --- old/netpbm.sourceforge.net/doc/sbigtopgm.html 2013-05-29 03:34:18.000000000 +0200 +++ new/netpbm.sourceforge.net/doc/sbigtopgm.html 2015-01-19 04:26:49.000000000 +0100 @@ -2,23 +2,20 @@ <HTML><HEAD><TITLE>Sbigtopgm User Manual</TITLE></HEAD> <BODY> <H1>sbigtopgm</H1> -Updated: 23 January 98 +Updated: 18 January 2015 <BR> <A HREF="#index">Table Of Contents</A> -<A NAME="lbAB"> </A> <H2>NAME</H2> sbigtopgm - convert an SBIG CCDOPS file to PGM -<A NAME="lbAC"> </A> -<H2>SYNOPSIS</H2> +<H2 id="synopsis">SYNOPSIS</H2> <B>sbigtopgm</B> [<I>sbigfile</I>] -<A NAME="lbAD"> </A> -<H2>DESCRIPTION</H2> +<H2 id="description">DESCRIPTION</H2> <p>This program is part of <a href="index.html">Netpbm</a>. @@ -28,27 +25,29 @@ cameras and documentation of the file format is available at the Web site, <A HREF="http://www.sbig.com/">http://www.sbig.com/</A>. -<A NAME="lbAE"> </A> -<H2>SEE ALSO</H2> +<p><b>sbigtopgm</b> recognizes some variation on the documented SBIG Type 3 +format. It allows any capitalization in the header. It ignores all +whitespace in the header except newlines. So a header line can end in +newline, CRLF, or the bizarre LF-CR actually required by the spec. +<H2 id="seealso">SEE ALSO</H2> + +<B><A HREF="pgmtosbig.html">pgmtosbig</A></B> <B><A HREF="pgm.html">pgm</A></B> -<A NAME="lbAF"> </A> -<H2>AUTHOR</H2> +<H2 id="author">AUTHOR</H2> John Walker (<B><A HREF="http://www.fourmilab.ch/">http://www.fourmilab.ch/</A></B>), January 1998. This program is in the public domain. <HR> -<A NAME="index"> </A> -<H2>Table Of Contents</H2> +<H2 id="index">Table Of Contents</H2> <UL> -<LI><A HREF="#lbAB">NAME</A> -<LI><A HREF="#lbAC">SYNOPSIS</A> -<LI><A HREF="#lbAD">DESCRIPTION</A> -<LI><A HREF="#lbAE">SEE ALSO</A> -<LI><A HREF="#lbAF">AUTHOR</A> +<LI><A HREF="#synopsis">SYNOPSIS</A> +<LI><A HREF="#description">DESCRIPTION</A> +<LI><A HREF="#seealso">SEE ALSO</A> +<LI><A HREF="#author">AUTHOR</A> </UL> </BODY> </HTML> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/st4topgm.html new/netpbm.sourceforge.net/doc/st4topgm.html --- old/netpbm.sourceforge.net/doc/st4topgm.html 1970-01-01 01:00:00.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/st4topgm.html 2015-02-03 16:14:06.000000000 +0100 @@ -0,0 +1,64 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML><HEAD><TITLE>St4topgm User Manual</TITLE></HEAD> +<BODY> +<H1>st4topgm</H1> +Updated: 20 January 2015 +<BR> +<A HREF="#index">Table Of Contents</A> +<H2>NAME</H2> + +st4topgm - convert an SBIG ST-4 camera file to PGM + +<H2 id="synopsis">SYNOPSIS</H2> + +<B>st4topgm</B> + +[<I>st4file</I>] + +<H2 id="description">DESCRIPTION</H2> + +<p>This program is part of <a href="index.html">Netpbm</a>. + +<p><b>st4topgm</b> reads an image file in the native format used +by the Santa Barbara Instrument Group (SBIG) ST-4 astronomical CCD cameras, +and produces a PGM image as output. This format is not to be confused with +the format most other SBIG cameras use, for which you can use +<b>sbigtopgm</b>. + +<P>Additional information on SBIG cameras and documentation of the file format +is available at the Web +site, <A HREF="http://www.sbig.com/">http://www.sbig.com/</A>. + + +<H2 id="seealso">SEE ALSO</H2> + +<B><A HREF="pgmtost4.html">pgmtost4</A></B> +<B><A HREF="sbigtopgm.html">sbigtopgm</A></B> +<B><A HREF="pgm.html">pgm</A></B> + +<h2 id="history">HISTORY</h2> + +<p>Bryan Henderson wrote <b>st4topgm</b> for Sourceforge Netpbm in +January 2015. However, there has been another program by the same name for +the same purpose since December 2003, in the Debian version of Netpbm. +It was written by Justin Pryzby <justinpryzby@users.sf.net>. + +<p>Bryan discovered the Debian version when Prophet of the Way did a +comparison of the two Netpbms in January 2015. It was the only program that +the Debian version had that the Netpbm version did not (not counting one that +really didn't belong in any Netpbm), so Bryan decided to add it. Because it +was a small program, Bryan decided to write a replacement in the Netpbm coding +style rather than just copy Pryzby's code, but Bryan endeavoured to keep the +same function. + + +<HR> +<H2 id="index">Table Of Contents</H2> +<UL> +<LI><A HREF="#synopsis">SYNOPSIS</A> +<LI><A HREF="#description">DESCRIPTION</A> +<LI><A HREF="#seealso">SEE ALSO</A> +<LI><A HREF="#history">HISTORY</A> +</UL> +</BODY> +</HTML> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/doc/tifftopnm.html new/netpbm.sourceforge.net/doc/tifftopnm.html --- old/netpbm.sourceforge.net/doc/tifftopnm.html 2014-11-15 04:29:19.000000000 +0100 +++ new/netpbm.sourceforge.net/doc/tifftopnm.html 2015-01-02 18:37:16.000000000 +0100 @@ -2,7 +2,7 @@ <HTML><HEAD><TITLE>Tifftopnm User Manual</TITLE></HEAD> <BODY> <H1>tifftopnm</H1> -Updated: 12 July 2009 +Updated: 02 January 2015 <BR> <A HREF="#index">Table Of Contents</A> @@ -39,11 +39,16 @@ output stream. Before Netpbm 10.27 (March 2005), however, it would just ignore all but the first input image. -<P>The <I>tiff-filename</I> argument names the regular file that -contains the Tiff image. If you specify "-" or don't -specify this argument, <B>tfftopnm</B> uses Standard Input. In either -case, the file must be seekable. That means no pipe, but any regular -file is fine. +<P>The <I>tiff-filename</I> argument names the file that contains the Tiff +image. If you specify "-" or don't specify this +argument, <B>tifftopnm</B> uses Standard Input. + +<p>In either case, before Netpbm 10.70 (March 2015), the file must be +seekable. That means no pipe, but any regular file is fine. In current +Netpbm, the file need not be seekable, but if it isn't, <b>tifftopnm</b> +creates a temporary regular file containing the entire image, so you must have +resources for that (and it may defeat your reason for using a pipe). + <h3 id="library">TIFF Capability</h3> diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/netpbm.sourceforge.net/getting_netpbm.php new/netpbm.sourceforge.net/getting_netpbm.php --- old/netpbm.sourceforge.net/getting_netpbm.php 2014-11-18 17:13:09.000000000 +0100 +++ new/netpbm.sourceforge.net/getting_netpbm.php 2015-05-11 16:40:44.000000000 +0200 @@ -126,7 +126,7 @@ other uses for a Subversion client later. <p>If you don't even know what Subversion</a> is: It's a +href="http://subversion.apache.org">Subversion</a> is: It's a replacement for CVS. If you don't know what CVS is: It's a system designed for tracking changes to code as people develop it. Subversion is primarily intended to be used by developers, but works @@ -212,9 +212,9 @@ bug report</a> and a <a href="https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/270479"> Ubuntu bug report</a> about this. The Debian bug report was opened in 2006; -the last significant motion was that the Ubuntu bug report was changed from +the last significant motion was that the Ubuntu bug report was changed to importance "high" from "undecided" in May 2013. -(The foregoing is so as of December 2013). +(The foregoing is so as of December 2014). <p>The Netpbm source tree contains a program (<b>mkdeb</b>) that creates a Debian install package (.deb file) after you've built Netpbm form source, so @@ -365,7 +365,7 @@ </address> <p style="font-size:75%"> -This page was generated on 18 Nov 2014. +This page was generated on 11 May 2015. </body> </html> ++++++ netpbm-10.68.1-nohpcdtoppm-noppmtompeg.tar.bz2 -> netpbm-10.70.4-nohpcdtoppm-noppmtompeg.tar.bz2 ++++++ ++++ 9570 lines of diff (skipped) ++++++ netpbm-security-code.patch ++++++ ++++ 968 lines (skipped) ++++ between /work/SRC/openSUSE:Factory/netpbm/netpbm-security-code.patch ++++ and /work/SRC/openSUSE:Factory/.netpbm.new/netpbm-security-code.patch