diff options
| -rw-r--r-- | anytopnm.html | 13 | ||||
| -rw-r--r-- | giftopnm.html | 17 | ||||
| -rw-r--r-- | palmtopnm.html | 2 | ||||
| -rw-r--r-- | pam.html | 2 | ||||
| -rw-r--r-- | pamcomp.html | 40 | ||||
| -rw-r--r-- | pamrgbatopng.html | 4 | ||||
| -rw-r--r-- | pamthreshold.html | 16 | ||||
| -rw-r--r-- | pamtogif.html | 31 | ||||
| -rw-r--r-- | pamtotga.html | 10 | ||||
| -rw-r--r-- | pamtouil.html | 12 | ||||
| -rw-r--r-- | pamtowinicon.html | 11 | ||||
| -rw-r--r-- | pbmtext.html | 4 | ||||
| -rw-r--r-- | pngtopam.html | 6 | ||||
| -rw-r--r-- | pngtopnm.html | 2 | ||||
| -rw-r--r-- | pnminterp.html | 2 | ||||
| -rw-r--r-- | pnmpaste.html | 2 | ||||
| -rw-r--r-- | pnmtopng.html | 24 | ||||
| -rw-r--r-- | pnmtorle.html | 10 | ||||
| -rw-r--r-- | ppmcolormask.html | 2 | ||||
| -rw-r--r-- | ppmmix.html | 2 | ||||
| -rw-r--r-- | ppmrainbow.html | 2 | ||||
| -rw-r--r-- | ppmrough.html | 2 | ||||
| -rw-r--r-- | ppmtotga.html | 2 | ||||
| -rw-r--r-- | ppmtowinicon.html | 2 | ||||
| -rw-r--r-- | ppmtoxpm.html | 25 | ||||
| -rw-r--r-- | rlatopam.html | 2 | ||||
| -rw-r--r-- | rletopnm.html | 23 | ||||
| -rw-r--r-- | sgitopnm.html | 2 | ||||
| -rw-r--r-- | tgatoppm.html | 12 | ||||
| -rw-r--r-- | tifftopnm.html | 16 | ||||
| -rw-r--r-- | winicon.html | 10 | ||||
| -rw-r--r-- | winicontopam.html | 6 | ||||
| -rw-r--r-- | ximtoppm.html | 22 | ||||
| -rw-r--r-- | xpmtoppm.html | 8 |
34 files changed, 189 insertions, 157 deletions
diff --git a/anytopnm.html b/anytopnm.html index 33117768..9dec1f35 100644 --- a/anytopnm.html +++ b/anytopnm.html @@ -2,7 +2,7 @@ <HTML><HEAD><TITLE>Anytopnm User Manual</TITLE></HEAD> <BODY> <H1>anytopnm</H1> -Updated: 05 September 2006 +Updated: 15 November 2014 <BR> <A HREF="#index">Table Of Contents</A> @@ -13,6 +13,7 @@ anytopnm - convert an arbitrary type of image file to PBM, PGM, or PPM <B>anytopnm</B> [<I>file</I>] + <H2 id="description">DESCRIPTION</H2> <p>This program is part of <a href="index.html">Netpbm</a>. @@ -53,6 +54,16 @@ decoded result. <P>If <I>file</I> is <B>-</B> or not given, <B>anytopnm</B> takes its input from Standard Input. +<p>Many image formats are capable of representing multiple images. In +most cases, <b>anytopnm</b> converts these to multi-image Netpbm images, +but for some formats, <b>anytopnm</b> converts only the first image and +ignores the rest. + +<p>In the case of a multi-image GIF input, <b>anytopnm</b> converts all the +images starting with Netpbm 10.69 (December 2014), but only the first in +earlier releases. + + <H2 id="seealso">SEE ALSO</H2> <B><A HREF="pamfile.html">pamfile</A></B>, diff --git a/giftopnm.html b/giftopnm.html index 4e41f607..01f18e3a 100644 --- a/giftopnm.html +++ b/giftopnm.html @@ -53,18 +53,19 @@ Netpbm output image has the wrong aspect ratio. In this case, <DT><B>--alphaout=</B><I>alpha-filename</I> <DD><B>giftopnm </B> creates a PBM file containing the transparency -information from the input image. This "alpha image" is the same -dimensions as the input image, and each pixel of the alpha image tells whether -the corresponding pixel of the input image is transparent. Black means -transparent; white means opaque. If you don't specify <B>--alphaout</B>, -<B>giftopnm</B> does not generate an alpha file, and if the input image has an -alpha channel, <B>giftopnm</B> simply discards it. +information from the input image. This transparency image is the same +dimensions as the input image, and each pixel of the transparency image tells +whether the corresponding pixel of the input image is transparent. Black +means transparent; white means opaque. If you don't +specify <B>--alphaout</B>, <B>giftopnm</B> does not generate a transparency +file, and if the input image has a transparency channel, <B>giftopnm</B> simply +discards it. <P>If you specify <B>-</B> as the filename, <B>giftopnm</B> writes the -alpha output to Standard Output and discards the image. +transparency output to Standard Output and discards the image. <P>See <B><A HREF="pamcomp.html">pamcomp</A></B> for one way to use -the alpha output file. +the transparency output file. <DT><B>-verbose</B> diff --git a/palmtopnm.html b/palmtopnm.html index fae3a66f..c8965f73 100644 --- a/palmtopnm.html +++ b/palmtopnm.html @@ -104,7 +104,7 @@ write a histogram of colors in the input file to Standard Error. <H2 id="limitations">LIMITATIONS</H2> -<P>You cannot generate an alpha mask if the Palm Bitmap has a +<P>You cannot generate a transparency mask if the Palm Bitmap has a transparent color. However, you can still do this with <B>ppmcolormask</B> with a Netpbm pipe similar to: diff --git a/pam.html b/pam.html index 1deed886..ebe62dca 100644 --- a/pam.html +++ b/pam.html @@ -249,7 +249,7 @@ the third blue. contains transparency information. In that variation, the tuple type has "_ALPHA" added to it (e.g. "RGB_ALPHA") and one more plane. The highest numbered plane is the opacity plane (sometimes -called an alpha plane or transparency plane). +called an transparency plane or transparency plane). <p>In this kind of image, the color represented by a pixel is actually a combination of an explicitly specified foreground color and a background diff --git a/pamcomp.html b/pamcomp.html index 17029514..9c8d0e0a 100644 --- a/pamcomp.html +++ b/pamcomp.html @@ -51,21 +51,21 @@ file <I>overlay_file</I> on top of the image in the file beneath it. <P>If you add the <B>-alpha</B> option, then <B>pamcomp</B> uses the -image in file <I>alpha-pgmfile</I> as an alpha mask, which means it +image in file <I>alpha-pgmfile</I> as a transparency mask, which means it determines the level of transparency of each point in the overlay -image. The alpha mask must have the same dimensions as the overlay -image. In places where the alpha mask defines the overlay image to be +image. The transparency mask must have the same dimensions as the overlay +image. In places where the transparency mask defines the overlay image to be opaque, the composite output contains only the contents of the overlay image; the underlying image is totally blocked out. In places where -the alpha mask defines the overlay image to be transparent, the +the transparency mask defines the overlay image to be transparent, the composite output contains none of the overlay image; the underlying -image shows through completely. In places where the alpha mask shows +image shows through completely. In places where the transparency mask shows a value in between opaque and transparent (translucence), the composite image contains a mixture of the overlay image and the underlying image and the level of translucence determines how much of each. -<P>The alpha mask is a PGM file in which a white pixel represents +<P>The transparency mask is a PGM file in which a white pixel represents opaqueness and a black pixel transparency. Anything in between is translucent. (Like any Netpbm program, <B>pamcomp</B> will see a PBM file as if it is PGM). @@ -73,17 +73,17 @@ file as if it is PGM). <p>If the overlay image is a PAM image of tuple type RGB_ALPHA or GRAYSCALE_ALPHA, then the overlay image contains transparency information itself and <b>pamcomp</b> uses it the same way as the -alpha mask described above. If you supply both an overlay image that -has transparency information and an alpha mask, <b>pamcomp</b> +transparency mask described above. If you supply both an overlay image that +has transparency information and a transparency mask, <b>pamcomp</b> multiplies the two opacities to get the opacity of the overlay pixel. <p>Before Netpbm 10.25 (October 2004), <b>pamcomp</b> did not recognize the transparency information in a PAM image -- it just ignored it. So people had -to make appropriate alpha masks in order to have a non-opaque overlay. Some +to make appropriate transparency masks in order to have a non-opaque overlay. Some Netpbm programs that convert from image formats that contain transparency information are not able to create RGB_ALPHA or GRAYSCALE_ALPHA PAM output, so you have to use the old method -- extract the transparency information from -the original into a separate alpha mask and use that as input to +the original into a separate transparency mask and use that as input to <b>pamcomp</b>. <P>The output image is always of the same dimensions as the underlying @@ -187,17 +187,17 @@ exclusive with <b>-valign</b> and always measured from the top edge. <DT><B>-alpha=</B><i>alpha-pgmfile</i> <DD> -This option names a file that contains the alpha mask. If you don't -specify this option, there is no alpha mask, which is equivalent to -having an alpha mask specify total opaqueness everywhere. +This option names a file that contains the transparency mask. If you don't +specify this option, there is no transparency mask, which is equivalent to +having a transparency mask specify total opaqueness everywhere. <p> -You can specify <b>-</b> as the value of this option and the alpha +You can specify <b>-</b> as the value of this option and the transparency mask will come from Standard Input. If you do this, don't specify Standard Input as the source of any other input image. <DT><B>-invert</B> <DD> -This option inverts the sense of the values in the alpha mask, which +This option inverts the sense of the values in the transparency mask, which effectively switches the roles of the overlay image and the underlying image in places where the two intersect. @@ -209,8 +209,8 @@ the underlying image. <i>opacity</i> is a floating point number, with 1.0 meaning the overlay image is totally opaque and 0.0 meaning it is totally transparent. The default is 1.0. -<p>If you specify an alpha mask (the <b>-alpha</b> option), -<b>pamcomp</b> uses the product of the opacity indicated by the alpha +<p>If you specify a transparency mask (the <b>-alpha</b> option), +<b>pamcomp</b> uses the product of the opacity indicated by the transparency mask (as modified by the <b>-invert</b> option, as a fraction, and this opacity value. The <b>-invert</b> option does not apply to this opacity value. @@ -261,10 +261,10 @@ underlying image. <dd>This option indicates that the inputs are not true Netpbm images but rather a non-gamma-adjusted variation. This is relevant only when -you mix pixels, using the <b>-opacity</b> option or an alpha mask +you mix pixels, using the <b>-opacity</b> option or a transparency mask (the <b>-alpha</b> option). -<p>The alpha mask and <b>-opacity</b> values indicate a fraction of +<p>The transparency mask and <b>-opacity</b> values indicate a fraction of the light intensity of a pixel. But the PNM and PNM-equivalent PAM image formats represent intensities with gamma-adjusted numbers that are not linearly proportional to intensity. So <b>pamcomp</b>, by @@ -310,7 +310,7 @@ versions of the same tool. <p><B><A HREF="ppmcolormask.html">ppmcolormask</A></B> and <B><A HREF="pbmmask.html">pbmmask</A></B>, and <a href="pambackground.html"><b>pambackground</b></a> can help with -generating an alpha mask. +generating a transparency mask. <p><B><A HREF="pnmcomp.html">pnmcomp</A></B> is an older program that runs faster, but has less function. diff --git a/pamrgbatopng.html b/pamrgbatopng.html index 9d710bc4..b963f264 100644 --- a/pamrgbatopng.html +++ b/pamrgbatopng.html @@ -27,7 +27,7 @@ space in place of the equals sign to separate an option name from its value. tuple type (a color visual image with transparency) and produces an equivalent PNG image as output. -<p>The input image if from the file named by the <i>pamfile</i> argument, +<p>The input image is from the file named by the <i>pamfile</i> argument, or Standard Input if you don't specify <i>pamfile</i>. The output goes to Standard Output. @@ -41,7 +41,7 @@ information, you must supply it in a separate PGM image. That makes it considerably less convenient to use. <p>(But note that <b>pnmtopng</b> takes PAM images, even with RGB_ALPHA -tuple type just fine -- it just ignores the alpha plane). +tuple type just fine -- it just ignores the transparency plane). <p>Netpbm's strategic direction is to add to <b>pnmtopng</b> all the capabilities of <b>pamrgbatopng</b> and retire <b>pamrgbatopng</b>. diff --git a/pamthreshold.html b/pamthreshold.html index f93993ea..30727ea7 100644 --- a/pamthreshold.html +++ b/pamthreshold.html @@ -37,12 +37,12 @@ to a thresholding value. <p>The input should be a PGM image or a PAM image of tuple type GRAYSCALE or GRAYSCALE_ALPHA. However, pamthreshold doesn't check; it just thresholds the first channel as if it were grayscale samples and -if there is a second channel, processes it as if it is an alpha -(transparency) channel. So if you feed it e.g. a PPM image, it will +if there is a second channel, processes it as if it is a transparency +(alpha) channel. So if you feed it e.g. a PPM image, it will work but produce probably useless results. <p>The output is a PAM with tuple type BLACKANDWHITE or -BLACKANDWHITE_ALPHA, depending on whether the input has an alpha +BLACKANDWHITE_ALPHA, depending on whether the input has a transparency channel. You can turn this into a PBM (if you need to use it with an older program that doesn't understand PAM, or you can't afford the 8X amount of space that PAM uses for the image) with @@ -50,14 +50,14 @@ amount of space that PAM uses for the image) with <p>The output is to Standard Output. -<P>When the input has an alpha channel, <b>pamthreshold</b> includes -an alpha channel in the output. Since the output has maxval 1, the -alpha channel can indicate only fully transparent or fully opaque. +<P>When the input has a transparency channel, <b>pamthreshold</b> includes +a transparency channel in the output. Since the output has maxval 1, the +transparency channel can indicate only fully transparent or fully opaque. <b>pamthreshold</b> make it fully transparent where the input is more than half transparent and fully opaque where it isn't. -<p>The alpha function was new in Netpbm 10.43 (June 2008). Before -that, <b>pamthreshold</b> ignores any alpha channel in the input. +<p>The transparency function was new in Netpbm 10.43 (June 2008). Before +that, <b>pamthreshold</b> ignores any transparency channel in the input. <p>Another way to convert a grayscale image to black and white is to dither. Dithering is using clustered black and white pixels such that diff --git a/pamtogif.html b/pamtogif.html index 48f8168e..61fe6ec7 100644 --- a/pamtogif.html +++ b/pamtogif.html @@ -64,7 +64,9 @@ readers conceivably could not recognize GIF89. <p>The GIF format is not capable of representing an image with more than 256 colors in it (it contains a color map with a maximum size of 256). If the image you want to convert has more colors than that (<b>ppmhist</b> -can tell you), you can use <b>pnmquant</b> to reduce it to 256. +can tell you), you can use <b>pnmquant</b> to reduce it to 256. Or +use the more complex but faster method described under the <b>-mapfile</b> +option. <p>If your input image is a PAM with transparency information, <b>ppmtogif</b> uses one entry in the GIF colormap specifically for the transparent pixels, @@ -121,10 +123,29 @@ duplication of colors in the image is irrelevant. <p>The map file's depth must match the number of color components in the input (which is not necessarily the same as the input's depth -- -the input might have an alpha plane in addition). If your map file +the input might have a transparency plane in addition). If your map file does not, or it <em>might</em> not, run your input through <b>pnmremap</b> using the same map file so that it does. +<p>You can use <b>-mapfile</b> to speed up conversion of an image where you +already have a map file because of earlier processing of your image. For +example, it is common to start with an image that has more than 256 colors +and remap its colors to a set of 256 colors so that <b>pamgtogif</b> can +convert it (a GIF can have only 256 colors; <b>pamtogif</b> without +<b>-mapfile</b> fails on any image that has more than that) with +<b>pnmquant</b>. When you do this, <b>pnmquant</b> generates a palette to do +the color quantization, then <b>pamtogif</b> generates an identical palette +from the quantized image. You can save computation by generating the palette +once: + +<pre> +<kbd> + $ pnmcolormap 256 myimage.ppm >/tmp/colormap.ppm + $ pamtogif myimage.ppm -mapfile=/tmp/colormap.ppm >output.gif +</kbd> +</pre> + + <DT><B>-transparent=</B><I>color</I> <DD> @@ -161,9 +182,9 @@ such an option because it was not capable of taking PAM input that contains a transparency (alpha) plane, so one used this option to supply a transparency plane as a separate PGM file. - This option names a PGM file that contains an alpha mask for the + This option names a PGM file that contains a transparency mask for the image. <B>pamtogif</B> creates fully transparent pixels wherever the -alpha mask indicates transparency greater than 50%. The color of +transparency mask indicates transparency greater than 50%. The color of those pixels is that specified by the <B>-alphacolor</B> option, or black by default. @@ -172,7 +193,7 @@ addition to the entries for colors that are actually in the image. It marks that colormap entry as transparent and uses that colormap index in the output image to create a transparent pixel. -<P> The alpha image must be the same dimensions as the input +<P> The transparency image must be the same dimensions as the input image, but may have any maxval. White means opaque and black means transparent. diff --git a/pamtotga.html b/pamtotga.html index e319e006..74deeca9 100644 --- a/pamtotga.html +++ b/pamtotga.html @@ -32,9 +32,9 @@ value. produces a TrueVision Targa file as output. The PAM image may be either a BLACKANDWHITE, GRAYSCALE, RGB, or RGB_ALPHA image. -<p>To create a TGA image with transparency (i.e. with an alpha mask), +<p>To create a TGA image with transparency (i.e. with a transparency mask), use RGB_ALPHA PAM input. Some Netpbm programs that generate images with -alpha masks generate them in that format. For another way to create +transparency masks generate them in that format. For another way to create the proper input stream, see <a href="pamstack.html"><b>pamstack</b></a>. <p>It is unclear that anything except <b>pamtotga</b> knows about TGAs @@ -102,11 +102,11 @@ Standard Input, <b>pamtotga</b> omits the image ID from the TGA header. That was always a misnomer, though, because a PPM class program would not be able to tell the difference between PGM and PPM input (it would all look like PPM), and thus could not choose the output Targa image type based on the type -of the input. Netpbm 10.6 also added the ability to handle an alpha channel, -so it became a PAM class program. +of the input. Netpbm 10.6 also added the ability to handle a transparency +channel, so it became a PAM class program. <p>In Netpbm 10.15 (April 2003), the program became the first in the -Netpbm package to recognize an alpha channel in a PAM. It recognized +Netpbm package to recognize a transparency channel in a PAM. It recognized tuple type "RGBA". But when this kind of PAM image was later added to the PAM specification, it was specified with tuple type "RGB_ALPHA". So in Netpbm 10-26 (January 2005), <b>pamtotga</b> diff --git a/pamtouil.html b/pamtouil.html index 6c2356b2..ace512e3 100644 --- a/pamtouil.html +++ b/pamtouil.html @@ -8,7 +8,7 @@ Updated: 05 May 2002 <A NAME="lbAB"> </A> <H2>NAME</H2> -pamtouil - convert a PNM or PNM/alpha image into a Motif UIL icon file +pamtouil - convert a PNM or PNM/transparency image into a Motif UIL icon file <A NAME="lbAC"> </A> <H2>SYNOPSIS</H2> @@ -25,11 +25,11 @@ separate an option from its value with whitespace instead of <b>=</b>. <p>This program is part of <a href="index.html">Netpbm</a>. -<p><b>pamtouil</b> reads a PNM or PAM image as input and produces a -Motif UIL icon file as output. If the input is PAM, it may be either -a regular grayscale or color image or grayscale+alpha or color+alpha. -Where the alpha channel is present, <b>pamtouil</b> renders pixels -that are more than half transparent as transparent in the output. +<p><b>pamtouil</b> reads a PNM or PAM image as input and produces a Motif UIL +icon file as output. If the input is PAM, it may be either a regular +grayscale or color image or grayscale+transparency or color+transparency. +Where the transparency channel is present, <b>pamtouil</b> renders pixels that +are more than half transparent as transparent in the output. <P>In the UIL's colormap, <b>pamtouil</b> uses the color names from the RGB database -- the same one <b><a href="ppmmake.html">ppmmake</a></b> diff --git a/pamtowinicon.html b/pamtowinicon.html index 1d916a6b..7e6340d0 100644 --- a/pamtowinicon.html +++ b/pamtowinicon.html @@ -85,10 +85,11 @@ the number of channels. <TABLE summary="Image type based on number of channels" border=1 align="center"> <TR><TH>channels</TH><TH>image</TH></TR> <TR><TD>1</TD><TD>fully opaque grayscale image</TD></TR> -<TR><TD>2</TD><TD>grayscale image with alpha channel</TD></TR> +<TR><TD>2</TD><TD>grayscale image with transparency channel</TD></TR> <TR><TD>3</TD><TD>fully opaque color image</TD></TR> -<TR><TD>4</TD><TD>color image with alpha channel</TD></TR> -<TR><TD>5</TD><TD>color image with alpha channel and additional AND mask</TD></TR> +<TR><TD>4</TD><TD>color image with transparency channel</TD></TR> +<TR><TD>5</TD><TD>color image with transparency channel and additional AND +mask</TD></TR> </TABLE> <P>The tuple types of the PAMs are irrelevant. @@ -98,13 +99,13 @@ the number of channels. The so-called ‘AND mask’ is a special feature of Microsoft Windows icons. It is required for all BMP encoded images. At the -first sight, the AND mask is a 1-bit alpha channel, but it is also +first sight, the AND mask is a 1-bit transparency channel, but it is also used for e.g. shading the icon while dragging. See <A HREF="winicon.html">Windows Icons</A> for details. <P>If there is no explicit AND mask, but transparency data in the input image, <B>pamtowinicon</B> sets the AND mask to opaque where the -sample in the alpha channel is below maxval, and to transparent +sample in the transparency channel is below maxval, and to transparent elsewhere. <P>If no transparency data is present in the input image, diff --git a/pbmtext.html b/pbmtext.html index 38dc2c89..39f5a8a0 100644 --- a/pbmtext.html +++ b/pbmtext.html @@ -159,10 +159,10 @@ the text image itself as the mask, as long as you also specify the <P>If you want to overlay colored text instead of black, just use <B>ppmchange</B> to change all black pixels to the color of your choice before overlaying the text image. But still use the original -black and white image for the alpha mask. +black and white image for the transparency mask. <P>If you want the text at an angle, use <B>pnmrotate</B> on the text -image (and alpha mask) before overlaying. +image (and transparency mask) before overlaying. <h2 id="fonts">FONTS</h2> diff --git a/pngtopam.html b/pngtopam.html index 4c64bc60..42ed0c5e 100644 --- a/pngtopam.html +++ b/pngtopam.html @@ -64,7 +64,7 @@ conversion process. <DT><B>-alphapam</B> <DD>Produce a single output image containing the main image (foreground) -and the alpha channel or transparency mask. This image is in the PAM +and the transparency channel or transparency mask. This image is in the PAM format with tuple type of either GRAYSCALE_ALPHA (which has a depth of 2 channels) or RGB_ALPHA (which has a depth of 4 channels). @@ -80,7 +80,7 @@ with <b>-alphapam</b>, but <b>pamrgbatopng</b> will. <DT><B>-alpha</B> -<DD>Output the alpha channel or transparency mask of the image. The +<DD>Output the transparency channel or transparency mask of the image. The result is either a PBM file or a PGM file, depending on whether different levels of transparency appear. @@ -92,7 +92,7 @@ the foreground of the input image and discards transparency information. <DT><B>-mix</B> -<DD>Compose the image with the transparency or alpha mask against a +<DD>Compose the image with the transparency or transparency mask against a background. The background color is determined by the bKGD chunk in the PNG, except that you can override it with <b>-background</b>. If the PNG has no bKGD chunk and you don't specify <b>-background</b>, diff --git a/pngtopnm.html b/pngtopnm.html index 60244c59..42709612 100644 --- a/pngtopnm.html +++ b/pngtopnm.html @@ -35,7 +35,7 @@ space in place of the equals sign to separate an option name from its value. href="pngtopam.html"><b>pngtopam</b></a>, introduced with Netpbm 10.44 (September 2008). <b>pngtopam</b> is backward compatible with <b>pngtopnm</b>, plus adds many additional functions, including the -ability to produce a PAM image that includes an alpha (transparency) +ability to produce a PAM image that includes a transparency (alpha) channel. Starting in Release 10.48, <b>pngtopnm</b> is just an alias for diff --git a/pnminterp.html b/pnminterp.html index 6c21fa30..ddcb4fb0 100644 --- a/pnminterp.html +++ b/pnminterp.html @@ -14,7 +14,7 @@ Updated: December 2001 <b><a href="pamstretch.html">pamstretch</a></b>. <P><B>pamstretch</b> is backward compatible with <b>pnminterp</b>, but -also recognizes PAM input, including that with an alpha channel. +also recognizes PAM input, including that with a transparency channel. </BODY> </HTML> diff --git a/pnmpaste.html b/pnmpaste.html index 0125b0ca..7179dfdc 100644 --- a/pnmpaste.html +++ b/pnmpaste.html @@ -51,7 +51,7 @@ segment you are interested in, edit it, and then paste it back in. <P><B>pamcomp</B> is a more general tool, except that it lacks the "or," "and," and "xor" functions. -<B>pamcomp</B> allows you to specify an alpha mask in order to have +<B>pamcomp</B> allows you to specify a transparency mask in order to have only part of the inserted image get inserted. So the inserted pixels need not be a rectangle. You can also have the inserted image be translucent, so the resulting image is a mixture of the inserted image diff --git a/pnmtopng.html b/pnmtopng.html index dd42117f..3c952948 100644 --- a/pnmtopng.html +++ b/pnmtopng.html @@ -144,12 +144,12 @@ with "unrecognized option," fall back to the old syntax. Creates an interlaced PNG file (Adam7). <DT><B>-alpha=</b><i>filename</i> -<DD> This specifies the transparency (alpha channel) of the image. -You supply the alpha channel as a standard PGM alpha mask (see the <a -href="pgm.html">PGM</a> specification. <b>pnmtopng</b> does not -necessarily represents the transparency information as an alpha channel in -the PNG format. If it can represent the transparency information through -a palette, it will do so in order to make a smaller PNG file. +<DD> This specifies the transparency (alpha) channel of the image. You supply +the transparency channel as a standard PGM transparency mask (see +the <a href="pgm.html">PGM</a> specification. <b>pnmtopng</b> does not +necessarily represents the transparency information as a transparency channel +in the PNG format. If it can represent the transparency information through a +palette, it will do so in order to make a smaller PNG file. <b>pnmtopng</b> even sorts the palette so it can omit the opaque colors from the transparency part of the palette and save space for the palette. @@ -183,7 +183,7 @@ color does not appear in the image, there will be no transparency. <DT><B>-background=</b><i>color</i> <DD> Causes <b>pnmtopng</b> to create a background color chunk in the PNG output -which can be used for subsequent alpha channel or transparent color +which can be used for subsequent transparency channel or transparent color conversions. Specify <i>color</i> the same as for <b>-transparent</b>. <DT><B>-palette=</b><i>palettefile</i> @@ -440,11 +440,11 @@ compression buffer) in bytes. <DT><B>-force</B> <DD> -When you specify this, <b>pnmtopng</b> limits its optimizations. -The resulting PNG output is as similar to the Netpbm input as possible. -For example, the PNG output will not be paletted and the alpha channel -will be represented as a full alpha channel even if the information could -be represented more succinctly with a transparency chunk. +When you specify this, <b>pnmtopng</b> limits its optimizations. The +resulting PNG output is as similar to the Netpbm input as possible. For +example, the PNG output will not be paletted and the transparency channel will +be represented as a full transparency channel even if the information could be +represented more succinctly with a transparency chunk. <DT><B>-libversion</B> diff --git a/pnmtorle.html b/pnmtorle.html index 70751107..5daef6e8 100644 --- a/pnmtorle.html +++ b/pnmtorle.html @@ -27,7 +27,7 @@ pnmtorle - convert a Netpbm image file into an RLE image file. <p>This program is part of <a href="index.html">Netpbm</a>. <p>This program converts Netpbm image files into Utah RLE image files. -You can include an alpha mask. If the input is a multiple image file, +You can include a transparency mask. If the input is a multiple image file, the output consists of several concatenated RLE images. <P>The RLE file will contain either a three channel color image (24 @@ -58,10 +58,10 @@ that no file conversion takes place. <DT><B>-a</B> <DD> -This option causes <b>pnmtorle</b> to include an alpha channel in the output -image. The alpha channel is based on the image: Wherever a pixel -is black, the corresponding alpha value is transparent. Everywhere -else, the alpha value is fully opaque. +This option causes <b>pnmtorle</b> to include an transparency channel in the +output image. The transparency channel is based on the image: Wherever a +pixel is black, the corresponding trasparency value is transparent. +Everywhere else, the transparency value is fully opaque. <DT><B>-o</B> <I>outfile</I> diff --git a/ppmcolormask.html b/ppmcolormask.html index 39acfa87..e4671f33 100644 --- a/ppmcolormask.html +++ b/ppmcolormask.html @@ -43,7 +43,7 @@ the input file and is black in all places where the input file is a color indicated by the <b>-color</b> option, and white everywhere else. -<P>The output of <B>ppmcolormask</B> is useful as an alpha mask input +<P>The output of <B>ppmcolormask</B> is useful as a transparency mask input to <B>pamcomp</B>. Note that you don't need <b>ppmcolormask</b> and <b>pamcomp</b> if you are ultimately converting to PNG with <b>pnmtopng</b> because the <b>-transparent</b> option on <b>pnmtopng</b> does diff --git a/ppmmix.html b/ppmmix.html index 5e9d07ea..5e2b7ee4 100644 --- a/ppmmix.html +++ b/ppmmix.html @@ -40,7 +40,7 @@ original image. <P><B>pamcomp</B> is a more general alternative. It allows you to mix images of different size and to have the fade factor vary throughout -the image (through the use of an alpha mask). It does not have the +the image (through the use of a transparency mask). It does not have the same-maxval and same-type restrictions. It mixes light intensity, not brightness. diff --git a/ppmrainbow.html b/ppmrainbow.html index dc6b8f93..9d966177 100644 --- a/ppmrainbow.html +++ b/ppmrainbow.html @@ -31,7 +31,7 @@ another to another from left to right, like a rainbow. through <B>pnmrotate</B> or <b>pamflip</b>. <P>One use for such a rainbow is to compose it with another image -under an alpha mask in order to add a rainbow area to another image. +under a transparency mask in order to add a rainbow area to another image. In fact, you can make rainbow-colored text by using <B>pbmtext</B>, <B>pamcomp</B>, and <B>ppmrainbow</B>. diff --git a/ppmrough.html b/ppmrough.html index 5639b391..cc524bdd 100644 --- a/ppmrough.html +++ b/ppmrough.html @@ -78,7 +78,7 @@ can initialize the pseudo-random generator with the <B>-init</B> option. <P>You could use <b>ppmrough</b> with <b>ppmtopgm</b> to create a PGM -alpha mask and use it to roughen up the edges of another image. +transparency mask and use it to roughen up the edges of another image. <H2 id="options">OPTIONS</H2> diff --git a/ppmtotga.html b/ppmtotga.html index 25fdab29..3a3a78de 100644 --- a/ppmtotga.html +++ b/ppmtotga.html @@ -14,7 +14,7 @@ ppmtotga - replaced by pamtotga <b><a href="pamtotga.html">pamtotga</a></b>. <P><B>pamtotga</b> is backward compatible with <b>ppmtotga</b>, but -also recognizes PAM input, including that with an alpha channel. +also recognizes PAM input, including that with a transparency channel. </BODY> </HTML> diff --git a/ppmtowinicon.html b/ppmtowinicon.html index 0eab3084..00b66f77 100644 --- a/ppmtowinicon.html +++ b/ppmtowinicon.html @@ -62,7 +62,7 @@ be opaque. Everywhere else, the icon will be transparent. Note that as with any Netpbm program, you can use a PBM image for the transparency mask and <b>ppmtowinicon</b> will treat it like a PGM. -<P>The and mask is like an alpha mask, except for what it signifies in +<P>The and mask is like a transparency mask, except for what it signifies in the "not opaque" areas. In the usual case, the foreground image is black in those areas, and in that case the areas are fully transparent -- the background shows through the icon. But in general, a not diff --git a/ppmtoxpm.html b/ppmtoxpm.html index 1530682b..80adbc64 100644 --- a/ppmtoxpm.html +++ b/ppmtoxpm.html @@ -62,17 +62,16 @@ of the color code affects the size of the image stream. <p>All color codes in an image are the same length, and <b>ppmtoxpm</b> tries to make it as short as possible. That length is, of course, determined by the number of colors in the image. -<b>ppmtoxpm</b> counts the colors in the image, excluding those that -will be transparent in the output because of your alpha mask, and chooses -a color code length accordingly. There are 92 printable characters -that can be used in a color code. Therefore, if you have 92 or fewer -colors, your color codes will be one character. If you have more than -92 but not more than 92 * 92, your color codes will be two characters. -And so on. - -<p>There's one exception to the above: If you specify an alpha mask +<b>ppmtoxpm</b> counts the colors in the image, excluding those that will be +transparent in the output because of your transparency mask, and chooses a +color code length accordingly. There are 92 printable characters that can be +used in a color code. Therefore, if you have 92 or fewer colors, your color +codes will be one character. If you have more than 92 but not more than 92 * +92, your color codes will be two characters. And so on. + +<p>There's one exception to the above: If you specify a transparency mask (the <b>-alpha</b> option, one unique color code represents -"transparent." This is true even if the alpha mask doesn't +"transparent." This is true even if the transparency mask doesn't actually produce any transparent pixels. So subtract one from the number of possible colors if you use <b>-alpha</b>. @@ -114,15 +113,15 @@ to the system color dictionary. If you didn't specify <b>-rgb</b>, <DT><B>-alphamask=</B><I>pgmfile</I> -<DD> This option names a PGM file to use as an alpha (transparency) +<DD> This option names a PGM file to use as a transparency (alpha) mask. The file must contain an image the same dimensions as the input image. <B>ppmtoxpm</B> marks as transparent any pixel whose position -in the alpha mask image is at most half white. +in the transparency mask image is at most half white. <P>If you don't specify <B>-alphamask</B>, <B>ppmtoxpm</B> makes all pixels in the output opaque. -<P><B>ppmcolormask</B> is one way to generate an alpha mask file. You +<P><B>ppmcolormask</B> is one way to generate a transparency mask file. You might also generate it by extracting transparency information from an XPM file with the <B>-alphaout</B> option to <B>xpmtoppm</B>. diff --git a/rlatopam.html b/rlatopam.html index b3467ed9..c7ec030c 100644 --- a/rlatopam.html +++ b/rlatopam.html @@ -22,7 +22,7 @@ to PAM image files. <p><b>rlatopam</b> converts an Alias RLA (run-length encoded type A) or RPF (rich pixel format) image to a PAM image file. The output PAM -file can be grayscale or RGB, with or without an alpha channel. +file can be grayscale or RGB, with or without a transparency channel. <p><i>rlafile</i> is the file name of the input file. If you omit this parameter, <b>rlatopam</b> reads the image from Standard Input. diff --git a/rletopnm.html b/rletopnm.html index f1520cf7..02132311 100644 --- a/rletopnm.html +++ b/rletopnm.html @@ -45,18 +45,18 @@ the input comes from Standard Input. <DD> <B>rletopnm </B> creates a PGM (portable graymap) file containing the -alpha channel values in the input image. If the input image doesn't -contain an alpha channel, the <I>alpha-filename</I> file contains all -zero (transparent) alpha values. If you don't specify -<B>--alphaout</B>, <B>rletopnm</B> does not generate an alpha file, -and if the input image has an alpha channel, <B>rletopnm</B> simply +transparency channel values in the input image. If the input image doesn't +contain an transparency channel, the <I>alpha-filename</I> file contains all +zero (transparent) transparency values. If you don't specify +<B>--alphaout</B>, <B>rletopnm</B> does not generate a transparency file, +and if the input image has a transparency channel, <B>rletopnm</B> simply discards it. <P>If you specify <B>-</B> as the filename, <B>rletopnm</B> writes the -alpha output to Standard Output and discards the image. +transparency output to Standard Output and discards the image. <P>See <B><A HREF="pamcomp.html">pamcomp</A></B> for one way to use -the alpha output file. +the transparency output file. <DT><B>--verbose</B> @@ -93,8 +93,8 @@ store the resulting image as lenna.ppm: </pre> <li>Convert RLE file dart.rle to PPM format as dart.ppm. Store the -alpha channel of dart.rle as dartalpha.pgm (if dart.rle doesn't have -an alpha channel, store a fully transparent alpha mask as +transparency channel of dart.rle as dartalpha.pgm (if dart.rle doesn't have +a transparency channel, store a fully transparent transparency mask as dartalpha.pgm): <pre> @@ -129,12 +129,11 @@ Minnesota Supercomputer Center, Inc. <P>Modifications by Eric Haines to support raw and plain formats. -<P>Modifications by Bryan Henderson to create alpha files and use +<P>Modifications by Bryan Henderson to create transparency files and use mnemonic options. <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> diff --git a/sgitopnm.html b/sgitopnm.html index 95d8e6e8..c153e098 100644 --- a/sgitopnm.html +++ b/sgitopnm.html @@ -57,7 +57,7 @@ be a seekable file, so for example you can't feed it from a pipe. image or, if the input has 1 or 2 channels, extracts the first channel as a PGM image. -<p>A 2-channel image is grayscale plus alpha (transparency), so you can get +<p>A 2-channel image is grayscale plus transparency, so you can get the transparency information with <b>-channel=2</b>. You could then combine them into a PAM image of tuple type GRAYSCALE_ALPHA with <b>pamstack</b>. diff --git a/tgatoppm.html b/tgatoppm.html index 61cfd7d5..abc11784 100644 --- a/tgatoppm.html +++ b/tgatoppm.html @@ -34,18 +34,18 @@ a PPM image as output. <DT><B>--alphaout=</B><I>alpha-filename</I> -<DD><B>tgatoppm </B> creates a PGM image containing the alpha channel +<DD><B>tgatoppm </B> creates a PGM image containing the transparency channel values in the input image. If the input image doesn't contain an -alpha channel, the <I>alpha-filename</I> file contains all zero -(transparent) alpha values. If you don't specify <B>--alphaout</B>, +transparency channel, the <I>alpha-filename</I> file contains all zero +(transparent) transparency values. If you don't specify <B>--alphaout</B>, <B>tgatoppm</B> does not generate an alpha file, and if the input -image has an alpha channel, <B>tgatoppm</B> simply discards it. +image has a transparency channel, <B>tgatoppm</B> simply discards it. <P>If you specify <B>-</B> as the filename, <B>tgatoppm</B> writes the -alpha output to Standard Output and discards the image. +transparency output to Standard Output and discards the image. <P>See <B><A HREF="pamcomp.html">pamcomp</A></B> for one way to use -the alpha output file. +the transparency output file. <DT><B>--headerdump</B> diff --git a/tifftopnm.html b/tifftopnm.html index df1f468d..7d4b2ddb 100644 --- a/tifftopnm.html +++ b/tifftopnm.html @@ -53,7 +53,7 @@ it is able to interpret is determined mostly by that library. <P>This program cannot read every possible TIFF file -- there are myriad variations of the TIFF format. However, it does understand -monochrome and gray scale, RGB, RGBA (red/green/blue with alpha +monochrome and gray scale, RGB, RGBA (red/green/blue with transparency channel), CMYK (Cyan-Magenta-Yellow-Black ink color separation), and color palette TIFF files. An RGB file can have either single plane (interleaved) color or multiple plane format. The program reads 1-8 @@ -109,18 +109,18 @@ its value either by an equals sign or white space. <DT><B>-alphaout=</B><I>alpha-filename</I> <DD><B>tifftopnm </B>creates a PGM file containing the alpha channel -values in the input image. If the input image doesn't contain an -alpha channel, the <I>alpha-filename</I> file contains all zero -(transparent) alpha values. If you don't specify <B>-alphaout</B>, +values in the input image. If the input image doesn't contain a +transparency channel, the <I>alpha-filename</I> file contains all zero +(transparent) transparency values. If you don't specify <B>-alphaout</B>, -<B>tifftopnm</B> does not generate an alpha file, and if the input -image has an alpha channel, <B>tifftopnm</B> simply discards it. +<B>tifftopnm</B> does not generate a transparency file, and if the input +image has an transparency channel, <B>tifftopnm</B> simply discards it. <P>If you specify <B>-</B> as the filename, <B>tifftopnm</B> -writes the alpha output to Standard Output and discards the image. +writes the transparency output to Standard Output and discards the image. <P>See <B><A HREF="pamcomp.html">pamcomp</A></B> for one way to use -the alpha output file. +the transparency output file. <DT><B>-respectfillorder</B> diff --git a/winicon.html b/winicon.html index 35913305..21f9aa76 100644 --- a/winicon.html +++ b/winicon.html @@ -56,13 +56,13 @@ screen is inverted. the image is usually black and sometimes white, but a color other than black and white will hardly give predictable results. -<P>Since Windows XP, there may also be an 8-bit alpha channel in 32-bpp BMP -encoded icon images. The AND mask, however, is still required and used +<P>Since Windows XP, there may also be an 8-bit transparency channel in 32-bpp +BMP encoded icon images. The AND mask, however, is still required and used e.g. for generating shadows. <P>PNG encoded images don't contain AND masks. While rendering a PNG encoded -image, Windows constructs an AND mask on the fly from the alpha channel, if -present. +image, Windows constructs an AND mask on the fly from the transparency +channel, if present. <H3 id="evolution">Evolution of Windows Icons</H3> @@ -76,7 +76,7 @@ invented in the mid-eighties for Windows 1: <LI>Windows 4.0 (a.k.a. Windows95) added support for 32-bpp images and resolutions up to 256 by 256. <LI>NT 5.1 (a.k.a. Windows XP) added support for the 8-bit -alpha channel in the unused bits of 32-bpp images. +transparency channel in the unused bits of 32-bpp images. <LI>NT 6.0 (a.k.a. Windows Vista) added support for PNG encoded images </UL> diff --git a/winicontopam.html b/winicontopam.html index ad9625d4..989b3045 100644 --- a/winicontopam.html +++ b/winicontopam.html @@ -31,9 +31,9 @@ its value. <P><B>winicontopam</B> reads a Microsoft Windows icon file and converts it to one or more RGB_ALPHA Netpbm PAM files. -<P>The alpha channel is copied from the 8-bit transparency data from the icon, -if present. If no 8-bit transparency data is available, the alpha channel is -constructed from the so-called ‘AND mask’. +<P>The transparency channel is copied from the 8-bit transparency data from +the icon, if present. If no 8-bit transparency data is available, the +transparency channel is constructed from the so-called ‘AND mask’. <P>The output goes to Standard Output. diff --git a/ximtoppm.html b/ximtoppm.html index 36985799..3b0605e5 100644 --- a/ximtoppm.html +++ b/ximtoppm.html @@ -36,23 +36,23 @@ the X.V11R4 release. <DL COMPACT> <DT><B>--alphaout=</B><I>alpha-filename</I> -<DD><B>ximtoppm</B> creates a PGM file containing the alpha channel -values in the input image. If the input image doesn't contain an -alpha channel, the <I>alpha-filename</I> file contains all zero -(transparent) alpha values. If you don't specify <B>--alphaout</B>, -<B>ximtoppm</B> does not generate an alpha file, and if the input -image has an alpha channel, <B>ximtoppm</B> simply discards it. +<DD><B>ximtoppm</B> creates a PGM file containing the transparency channel +values in the input image. If the input image doesn't contain a +transparency channel, the <I>alpha-filename</I> file contains all zero +(transparent) transparency values. If you don't specify <B>--alphaout</B>, +<B>ximtoppm</B> does not generate a transparency file, and if the input +image has a transparency channel, <B>ximtoppm</B> simply discards it. <P>If you specify <B>-</B> as the filename, <B>ximtoppm</B> writes the -alpha output to Standard Output and discards the image. +transparency output to Standard Output and discards the image. <P>Actually, an Xim image can contain an arbitrary fourth channel -- -it need not be an Alpha channel. <B>ximtoppm</B> extracts any fourth -channel it finds as described above; it doesn't matter if it is an -alpha channel or not. +it need not be a transparency channel. <B>ximtoppm</B> extracts any fourth +channel it finds as described above; it doesn't matter if it is a +transparency channel or not. <P>See <B><A HREF="pamcomp.html">pamcomp</A></B> for one way to use -the alpha output file. +the transparency output file. </DL> diff --git a/xpmtoppm.html b/xpmtoppm.html index f96b2499..5e2aa42a 100644 --- a/xpmtoppm.html +++ b/xpmtoppm.html @@ -34,16 +34,16 @@ and produces a PPM image as output. <DD><B>xpmtoppm</B> creates a PBM file containing the transparency mask for the image. If the input image doesn't contain transparency information, the <I>alpha-filename</I> file contains all white -(opaque) alpha values. If you don't specify <B>--alphaout</B>, -<B>xpmtoppm</B> does not generate an alpha file, and if the input +(opaque) transparency values. If you don't specify <B>--alphaout</B>, +<B>xpmtoppm</B> does not generate a transparency file, and if the input image has transparency information, <B>xpmtoppm</B> simply discards it. <P>If you specify <B>-</B> as the filename, <B>xpmtoppm</B> writes the -alpha output to Standard Output and discards the image. +transparency output to Standard Output and discards the image. <P>See <B><A HREF="pamcomp.html">pamcomp</A></B> for one way to use -the alpha output file. +the transparency output file. <p><b>xpmtoppm</b> can't handle a line longer than 8K characters in the XPM input. If an input line exceeds this limit, |