diff options
| author | giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8> | 2015-06-28 19:39:47 +0000 |
|---|---|---|
| committer | giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8> | 2015-06-28 19:39:47 +0000 |
| commit | 2222b5020909d4867f10cf72720df36e3483c0de (patch) | |
| tree | 7a8b56782d895e753e39e3cce1c0237b18915855 | |
| parent | dab40b54733b6f31bc41106dc126e4f387e8bb37 (diff) | |
| download | netpbm-mirror-2222b5020909d4867f10cf72720df36e3483c0de.tar.gz netpbm-mirror-2222b5020909d4867f10cf72720df36e3483c0de.tar.xz netpbm-mirror-2222b5020909d4867f10cf72720df36e3483c0de.zip | |
Replace character entity references with plain double quotes
git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@2590 9d0c8265-081b-0410-96cb-a4ca84ce46f8
157 files changed, 524 insertions, 524 deletions
diff --git a/411toppm.html b/411toppm.html index 69c985f9..4c146f01 100644 --- a/411toppm.html +++ b/411toppm.html @@ -33,10 +33,10 @@ The originator of this program and decipherer of the .411 format, Steve Allen <<A HREF="mailto:sla@alumni.caltech.edu">sla@alumni.caltech.edu</A>>, has this to say about the -utility of this program: "There's so little image in a 64x48 thumbnail +utility of this program: "There's so little image in a 64x48 thumbnail (especially when you have the full size JPG file) that the only point in doing this was to answer the implicit challenge posed by the manual -stating that only the camera can use these files." +stating that only the camera can use these files." <A NAME="lbAE"> </A> <H2>OPTIONS</H2> diff --git a/asciitopgm.html b/asciitopgm.html index 1730651f..b843b094 100644 --- a/asciitopgm.html +++ b/asciitopgm.html @@ -21,7 +21,7 @@ asciitopgm - convert ASCII graphics into a PGM <p><B>asciitopgm</b> reads ASCII data as input and produces a PGM image with pixel values which are an approximation of the -"brightness" of the ASCII characters, assuming +"brightness" of the ASCII characters, assuming black-on-white printing. In other words, a capital M is very dark, a period is very light, and a space is white. diff --git a/bmptopnm.html b/bmptopnm.html index e16eb3a2..dae10fff 100644 --- a/bmptopnm.html +++ b/bmptopnm.html @@ -28,7 +28,7 @@ If the input is colormapped and contains only black white and gray, the output is PGM. Otherwise, the output is PPM. <P><b>bmptopnm</b> understands BMP files compressed with run length -encoding (RLE4/RLE8), but not if that encoding includes a "delta" +encoding (RLE4/RLE8), but not if that encoding includes a "delta" (which is rare). <b>bmptopnm</b> recognizes the delta and issues an error message. diff --git a/cameratopam.html b/cameratopam.html index d412c779..4a348178 100644 --- a/cameratopam.html +++ b/cameratopam.html @@ -132,7 +132,7 @@ other cameras. <dt><b>-linear</b> <dd>This option causes <b>cameratopam</b> to generate a variation on -PAM that has "linear" color samples. In true PAM, each +PAM that has "linear" color samples. In true PAM, each sample in the image raster is gamma-corrected; i.e. it is essentially proportional to brightness. With the <b>linear</b> option, <b>cameratopam</b> generates an image in which the samples are instead diff --git a/directory.html b/directory.html index 2aad0679..32f8a21e 100644 --- a/directory.html +++ b/directory.html @@ -445,13 +445,13 @@ convert Palm Pilot Image Viewer format to Netpbm formats. <DD>convert PBM images to Postscript using G3 fax compression. <DT><B><a href=psidtopgm.html>psidtopgm</a> </B> -<DD>convert PostScript "image" data to PGM +<DD>convert PostScript "image" data to PGM <DT><B><a href=pbmtoptx.html>pbmtoptx</a> </B> <DD>convert PBM to Printronix graphics <DT><B><a href=ppmtopuzz.html>ppmtopuzz</a> </B> -<DD>convert PPM to X11 "puzzle" file +<DD>convert PPM to X11 "puzzle" file <DT><B><a href=qrttoppm.html>qrttoppm</a> </B> <DD>convert QRT ray-tracer output to PPM @@ -582,10 +582,10 @@ convert Windows icon file to PPM (obsoleted by <b>winicontoapm</b>). <DD>convert Xv "thumbnail" picture to PPM <DT><B><a href=pbmtoybm.html>pbmtoybm</a> </B> -<DD>convert PBM into Bennet Yee "face" file +<DD>convert PBM into Bennet Yee "face" file <DT><B><a href=ybmtopbm.html>ybmtopbm</a> </B> -<DD>convert Bennet Yee "face" file into PBM +<DD>convert Bennet Yee "face" file into PBM <DT><B><a href=ppmtoyuv.html>ppmtoyuv</a> </B> <DD>convert PPM to Abekas YUV format @@ -1060,7 +1060,7 @@ These all work on the Netpbm formats as input. <DD>simulate a multi-lens camera such as the Pop9 <DT><B><a href="ppmdmkfont.html">ppmdmkfont</a> </B> -<DD>create Ppmdfont "standard" +<DD>create Ppmdfont "standard" <DT><B><a href="ppmddumpfont.html">ppmddumpfont</a> </B> <DD>dump a Ppmdfont file diff --git a/faxformat.html b/faxformat.html index b383ec06..cb5d710c 100644 --- a/faxformat.html +++ b/faxformat.html @@ -47,11 +47,11 @@ line, its impact not spread to many lines after it. <p>All Group 3 and Group 4 fax machines must be able to send and receive MH. -<p>MH is sometimes called "G3," but that is a poor name because +<p>MH is sometimes called "G3," but that is a poor name because while the Group 3 standard does specify MH, it has always specified other formats too. -<p>MH is sometimes called "T4" based on the name of the +<p>MH is sometimes called "T4" based on the name of the document that specifies it, ITU T.4. But this is a poor name because T.4 also specifies MR. @@ -73,7 +73,7 @@ Group 4 standard, but then added to an extended Group 3 standard as well. <p>MMR is sometimes called Group 4, but that is a poor name because of the fact that it is also part of the current Group 3 standard. -<p>MMR is sometimes called "T6" based on the name of the document +<p>MMR is sometimes called "T6" based on the name of the document that specifies it, ITU T.6. </dl> diff --git a/fiascotopnm.html b/fiascotopnm.html index 8de3befe..d8e25510 100644 --- a/fiascotopnm.html +++ b/fiascotopnm.html @@ -130,30 +130,30 @@ Print detailed help, then exit. fiascotopnm foo.wfa >foo.ppm </PRE> -<P>Decompress the FIASCO file "foo.wfa" and store it as -"foo.ppm". +<P>Decompress the FIASCO file "foo.wfa" and store it as +"foo.ppm". <PRE> fiascotopnm -o foo1.wfa foo2.wfa </PRE> -<P>Decompress the FIASCO files "foo1.wfa" and -"foo2.wfa" and write the frames to the image files -"foo1.wfa.ppm" and "foo2.wfa.ppm". +<P>Decompress the FIASCO files "foo1.wfa" and +"foo2.wfa" and write the frames to the image files +"foo1.wfa.ppm" and "foo2.wfa.ppm". <PRE> fiascotopnm -oimage foo1.wfa </PRE> -<P>Decompress the FIASCO file "foo1.wfa" and write all 15 -frames to the image files "image.00.ppm", ... , -"image.14.ppm". +<P>Decompress the FIASCO file "foo1.wfa" and write all 15 +frames to the image files "image.00.ppm", ... , +"image.14.ppm". <PRE> fiascotopnm --fast --magnify=-1 --double video.wfa >stream.ppm </PRE> -<P>Decompress the FIASCO file "video.wfa". The +<P>Decompress the FIASCO file "video.wfa". The decompression speed is as fast as possible: the image is decompressed (in 4:2:0 format) at a quarter of its original size; then the image is enlarged again by pixel doubling. @@ -176,11 +176,11 @@ enlarged again by pixel doubling. <DL COMPACT> <DT><B>FIASCO_IMAGES</B> -<DD>Save path for image files. Default is "./". +<DD>Save path for image files. Default is "./". <DT><B>FIASCO_DATA</B> -<DD>Search path for FIASCO files. Default is "./". +<DD>Search path for FIASCO files. Default is "./". </DL> diff --git a/g3topbm.html b/g3topbm.html index e92d0619..3038c83a 100644 --- a/g3topbm.html +++ b/g3topbm.html @@ -69,7 +69,7 @@ sometimes fax files have some junk at the beginning. <DD>Tells <b>g3topbm</b> to interpret bits least-significant first, instead of the default most-significant first. Apparently some fax modems do it one way and others do it the other way. If you get a -whole bunch of "bad code word" messages, try using this +whole bunch of "bad code word" messages, try using this option. <DT><B>-stretch</B> @@ -102,7 +102,7 @@ does not use the height of the paper for anything. <DT><B>-stop_error</B> <DD>This option tells <b>g3topbm</b> to fail when it finds a problem -in the input. "Fail" means it terminates with a nonzero +in the input. "Fail" means it terminates with a nonzero status code with the contents of the output file undefined. <p>If you don't specify this option, <b>g3topbm</b> does its best to diff --git a/hpcdtoppm.html b/hpcdtoppm.html index 9829a360..f28d5556 100644 --- a/hpcdtoppm.html +++ b/hpcdtoppm.html @@ -387,7 +387,7 @@ Please send bugs reports and patches to the author. <H2 id="version">VERSION</H2> -<p>The name <b>hpcdtoppm</b> stands for "Hadmut's pcdtoppm," to +<p>The name <b>hpcdtoppm</b> stands for "Hadmut's pcdtoppm," to make it distinguishable in the event that someone else is building a similar application and naming it <b>pcdtoppm</b>. diff --git a/ilbmtoppm.html b/ilbmtoppm.html index 313c6cec..9f41d174 100644 --- a/ilbmtoppm.html +++ b/ilbmtoppm.html @@ -57,7 +57,7 @@ it doesn't recognize. <DL COMPACT> <dt><b>-transparent </b><i>color</i> -<dd>This is the color that should "show through" in places where +<dd>This is the color that should "show through" in places where the image is transparent. <P><i>color</i> is like the <a href="libppm.html#colorname">argument of diff --git a/index.html b/index.html index 2bc367c2..2b4902a8 100644 --- a/index.html +++ b/index.html @@ -13,8 +13,8 @@ Updated: 31 January 2014 <P><B>Netpbm</B> is a package of graphics programs and a programming library. <P> There are over 220 separate programs in the package, -most of which have "pbm", "pgm", "ppm", -"pam", or "pnm" in their names. For example, +most of which have "pbm", "pgm", "ppm", +"pam", or "pnm" in their names. For example, <B><a href="pamscale.html">pamscale</a></B> and <B><a href="giftopnm.html">giftopnm</a></B>. @@ -178,7 +178,7 @@ ls *.yuv <B>xargs</B> are also useful for simple manipulation of groups of files. <P> -Some shells' "process substitution" facility can help where a +Some shells' "process substitution" facility can help where a non-Netpbm program expects you to identify a disk file for input and you want it to use the result of a Netpbm manipulation. Say the hypothetical program <b>printcmyk</b> @@ -200,7 +200,7 @@ Netpbm tool. <P> All of the programs work with a set of graphics formats called the -"netpbm" formats. Specifically, these formats are +"netpbm" formats. Specifically, these formats are <A HREF="pbm.html">pbm</A>, <A HREF="pgm.html">pgm</A>, <A HREF="ppm.html">ppm</A>, @@ -208,7 +208,7 @@ and <A HREF="pam.html">pam</A>. The first three of these are sometimes known generically as -"pnm". +"pnm". Many of the Netpbm programs convert from a Netpbm format to another format or vice versa. This is so you can use the Netpbm programs to @@ -227,9 +227,9 @@ it can represent matrices of general data including but not limited to black and white, grayscale, and color images. <P> -Programs designed to work with PBM images have "pbm" in their names. +Programs designed to work with PBM images have "pbm" in their names. Programs designed to work with PGM, PPM, and PAM images similarly have -"pgm", "ppm", and "pam" in their names. +"pgm", "ppm", and "pam" in their names. <P> All Netpbm programs designed to read PGM images see PBM images as if @@ -237,8 +237,8 @@ they were PGM too. All Netpbm programs designed to read PPM images see PGM and PBM images as if they were PPM. See <a href="#impconv"> Implied Format Conversion</a>. -<P> Programs that have "pnm" in their names read PBM, PGM, -and PPM but unlike "ppm" programs, they distinguish between +<P> Programs that have "pnm" in their names read PBM, PGM, +and PPM but unlike "ppm" programs, they distinguish between those formats and their function depends on the format. For example, <B><a href="pnmtopng.html">pnmtopng</a></B> creates a black and white PNG output image if its input is PBM or PGM, but a color PNG output image @@ -315,7 +315,7 @@ PBM program to read a PAM image, run it through <b>pamtopnm</b>. <P>In many graphics formats, there's a means of indicating that certain parts of the image are wholly or partially transparent, meaning that -if it were displayed "over" another image, the other image +if it were displayed "over" another image, the other image would show through there. Netpbm formats deliberately omit that capability, since their purpose is to be extremely simple. @@ -416,7 +416,7 @@ to totally describe the pixel. Netpbm does this expansion to make implementing the programs easier -- it uses the same format regardless of the type of image. -<p>Newer programs use the "pam" family of library functions +<p>Newer programs use the "pam" family of library functions internally, which use memory a little differently. These functions are designed to handle generic tuples with a variable numbers of planes, so no fixed size per-tuple storage is possible. A program of this type uses 4 bytes @@ -507,7 +507,7 @@ href="pamditherbw.html"><b>pamditherbw</b></a> (Make a black and white image that approximates a grayscale image). <p>The Netpbm image formats use 16 bit integers. The Netpbm code uses -"unsigned int" size integers to work with them. +"unsigned int" size integers to work with them. <H2 id="netpbmforgimp">Netpbm For Gimp</H2> @@ -640,7 +640,7 @@ are specifically for KDE. <P>If you're writing a program in C to draw and manipulate images, check out <a href="http://www.boutell.com/gd">gd</a>. Netpbm contains a C library for -drawing images (<b>libnetpbm</b>'s "ppmd" routines), but it is +drawing images (<b>libnetpbm</b>'s "ppmd" routines), but it is probably not as capable or documented as <b>gd</b>. You can easily run any Netpbm program from a C program with the <b>pm_system</b> function from the Netpbm programming library, but that is less efficient than <b>gd</b> @@ -736,7 +736,7 @@ available). This can convert from TIFF -> IOCA and back again. <a href="http://www.thethinktanksoftware.com/details.html">Ameri-Imager</a> ($40 Windows only). -<P><B>pnm2ppa</B> converts to HP's "Winprinter" format (for +<P><B>pnm2ppa</B> converts to HP's "Winprinter" format (for HP 710, 720, 820, 1000, etc). It is a superset of Netpbm's <B>pbmtoppa </B> and handles, notably, color. However, it is more of a printer driver than a Netpbm-style primitive graphics building @@ -775,11 +775,11 @@ purposes the quintessential Postscript and PDF tools. <P>Adobe's free Acrobat Reader displays PDF and converts to Postscript. The Acrobat Reader for unix has a program name of -"acroread" and the -toPostScript option (also see the +"acroread" and the -toPostScript option (also see the -level2 option) is useful. <P>Other software from Adobe, available for purchase, interprets and -creates Postscript and PDF files. "Distill" +creates Postscript and PDF files. "Distill" is a program that converts Postscript to PDF. <p><a href="http://www.foolabs.com/xpdf/"><b>xpdf</b></a> also reads @@ -962,7 +962,7 @@ http://www.openexr.com</a>. <li>Xv Visual Schnauzer thumbnail image. This is a rather antiquated format used by the Xv program. In Netpbm circles, it is best known for the fact that it is very similar to Netpbm formats and uses the -same signature ("P7") as PAM because it was developed as +same signature ("P7") as PAM because it was developed as sort of a fork of the Netpbm format specifications. <li>YUV 4:2:0, aka YUV 420, and the similar YUV 4:4:4, YUV 4:2:2, diff --git a/jpegtopnm.html b/jpegtopnm.html index b4148b9b..1d489070 100644 --- a/jpegtopnm.html +++ b/jpegtopnm.html @@ -67,8 +67,8 @@ interpret the input file. See <B><A HREF="http://www.ijg.org">http://www.ijg.org</A> </B> for information on the library. -<P>"JFIF" is the correct name for the image format commonly -known as "JPEG." Strictly speaking, JPEG is a method of +<P>"JFIF" is the correct name for the image format commonly +known as "JPEG." Strictly speaking, JPEG is a method of compression. The image format using JPEG compression that is by far the most common is JFIF. There is also a subformat of TIFF that uses JPEG compression. @@ -132,7 +132,7 @@ Use a faster, lower-quality upsampling routine. <DD>Set limit on the amount of memory <B>jpegtopnm</B> uses in processing large images. Value is in thousands of bytes, or millions -of bytes if "M" is suffixed to the number. For example, +of bytes if "M" is suffixed to the number. For example, <B>-maxmemory 4m</B> selects 4000000 bytes. If <B>jpegtopnm</B> needs more space, it uses temporary files. @@ -325,8 +325,8 @@ overrides any <B>JPEGMEM</B>. <B>wrjpgcom</B> man page, <B>jhead</B> man page -<p>Wallace, Gregory K. "The JPEG Still Picture Compression -Standard", Communications of the ACM, April 1991 (vol. 34, +<p>Wallace, Gregory K. "The JPEG Still Picture Compression +Standard", Communications of the ACM, April 1991 (vol. 34, no. 4), pp. 30-44. <H2 id="author">AUTHOR</H2> diff --git a/liberror.html b/liberror.html index 2bd8ad9b..82cbc7b0 100644 --- a/liberror.html +++ b/liberror.html @@ -15,8 +15,8 @@ functions return error information. There are no return codes to check. If for some reason a function can't do what was asked of it, it doesn't return at all. -<p>Netpbm's response to encountering an error is called "throwing -an error." +<p>Netpbm's response to encountering an error is called "throwing +an error." <p>The typical way a Netpbm function throws an error (for example, when you attempt to open a non-existent file with <b>pm_openr()</b>) @@ -87,11 +87,11 @@ setjmp() first, then tell the Netpbm programming library with pnm_readpam(stdin, &pam, PAM_STRUCT_SIZE(tuple_type)); - printf("pnm_readpam() succeeded!\n"); + printf("pnm_readpam() succeeded!\n"); } else { - printf("pnm_readpam() failed. You should have seen " - "messages to Standard Error telling you why.\n"); + printf("pnm_readpam() failed. You should have seen " + "messages to Standard Error telling you why.\n"); } </code> </pre> @@ -147,8 +147,8 @@ appropriate one of these. <pre> <code> if (argc-1 < 3) - pm_error("You must specify at least 3 arguments. " - "You specified" only %d", argc-1); + pm_error("You must specify at least 3 arguments. " + "You specified" only %d", argc-1); </code> </pre> @@ -171,7 +171,7 @@ simply throws an error. It issues an error message exactly like <pre> <code> if (rc = -1) - pm_errormsg("Could not open file. errno=%d", errno); + pm_errormsg("Could not open file. errno=%d", errno); return -1; </code> </pre> @@ -206,12 +206,12 @@ newlines or tabs in it. static void logfilewrite(const char * const msg) { - fprintf(myerrorlog, "Netpbm error: %s", msg); + fprintf(myerrorlog, "Netpbm error: %s", msg); } pm_setusererrormsgfn(&logfilewrite); - pm_errormsg("Message for the error log"); + pm_errormsg("Message for the error log"); </code> </pre> diff --git a/libmaketmpfile.html b/libmaketmpfile.html index baea66d6..07c01256 100644 --- a/libmaketmpfile.html +++ b/libmaketmpfile.html @@ -24,8 +24,8 @@ pm_make_tmpfile(FILE ** fileP, <h2>EXAMPLE</h2> -<p>This simple example creates a temporary file, writes "hello -world" to it, then writes some search patterns to it, then uses +<p>This simple example creates a temporary file, writes "hello +world" to it, then writes some search patterns to it, then uses it as input to <b>grep</b>: <pre> @@ -36,12 +36,12 @@ const char * myfilename; pm_make_tmpfile(&myfileP, &myfilename); -fprintf(myfile, "^account:\\s.*\n"); -fprintf(myfile, "^name:\\s.*\n"); +fprintf(myfile, "^account:\\s.*\n"); +fprintf(myfile, "^name:\\s.*\n"); fclose(myFileP); -asprintfN(&grepCommand, "grep --file='%s' /tmp/infile >/tmp/outfile"); +asprintfN(&grepCommand, "grep --file='%s' /tmp/infile >/tmp/outfile"); system(grepCommand); diff --git a/libmaketmpfilefd.html b/libmaketmpfilefd.html index baf6be99..587648ad 100644 --- a/libmaketmpfilefd.html +++ b/libmaketmpfilefd.html @@ -24,8 +24,8 @@ pm_make_tmpfile(int * fdP, <h2>EXAMPLE</h2> -<p>This simple example creates a temporary file, writes "hello -world" to it, then writes some search patterns to it, then uses +<p>This simple example creates a temporary file, writes "hello +world" to it, then writes some search patterns to it, then uses it as input to <b>grep</b>: <pre> @@ -36,12 +36,12 @@ const char * myfilename; pm_make_tmpfile_fd(&fdP, &myfilename); -write(fd, "^account:\\s.*\n", 16); -fprintf(fd, "^name:\\s.*\n", 13); +write(fd, "^account:\\s.*\n", 16); +fprintf(fd, "^name:\\s.*\n", 13); close(fd); -asprintfN(&grepCommand, "grep --file='%s' /tmp/infile >/tmp/outfile"); +asprintfN(&grepCommand, "grep --file='%s' /tmp/infile >/tmp/outfile"); system(grepCommand); diff --git a/libnetpbm_draw.html b/libnetpbm_draw.html index cb7f16cc..eec95af0 100644 --- a/libnetpbm_draw.html +++ b/libnetpbm_draw.html @@ -56,30 +56,30 @@ in this facility. <p> The <b>ppmd_text</b> and <b>ppmd_text_box</b> functions use fonts. You control the fonts using functions described in this section. -There is one font that comes with Netpbm, called "standard". +There is one font that comes with Netpbm, called "standard". It is built into the function library and is the default font. You can create additional fonts and use them instead. <p>In a program that uses Netpbm drawing facilities, there is a -"current font." all drawing of text uses the current font. -When the program starts, the current font is "standard"; you +"current font." all drawing of text uses the current font. +When the program starts, the current font is "standard"; you can change it after that by calling the <b>ppmd_set_font</b> function. <p>Other than a built-in font, a font lives in file in a format special to Netpbm called Ppmdfont. The file typically has a name that -ends in ".ppmdfont". +ends in ".ppmdfont". <p>Use the <b>ppmddumpfont</b> program to dump the contents of a Ppmdfont file in human readable format. -<p>Use the <b>ppmdmkfont</b> program to generate the "standard" +<p>Use the <b>ppmdmkfont</b> program to generate the "standard" font as a Ppmdfont file. You don't normally need to do this, because -"standard" is built into <b>libnetpbm</b>. +"standard" is built into <b>libnetpbm</b>. <p>Use the <b>ppmdcfont</b> program to turn a Ppmdfont file into a C source file that you can compile into a program as a built-in font. Though we don't give full instructions here on how to do that, -<b>libnetpbm</b>'s built-in "standard" font is a good +<b>libnetpbm</b>'s built-in "standard" font is a good example. In Netpbm source code, you will find the C source file <b>standardppmdfont.c</b>, which was generated from the file <b>standard.ppmdfont</b> by <b>ppmdcfont</b>. You simply use a @@ -89,7 +89,7 @@ just like one you would get from <b>ppmd_read_font</b>. <h2>Font File Format</h2> -<p>The font file starts with the characters "ppmdfont" (without +<p>The font file starts with the characters "ppmdfont" (without the quotation marks) in ASCII. <p>The rest of the format is not yet documented, but it generally diff --git a/libnetpbm_ug.html b/libnetpbm_ug.html index 51da49de..4ead55c5 100644 --- a/libnetpbm_ug.html +++ b/libnetpbm_ug.html @@ -290,7 +290,7 @@ the type of a tuple to one with more or fewer planes. When reading an image, this contains the comments from the image's PAM header; when writing, the image gets these as comments, right after the magic number line. The individual comments are delimited by -newlines and are in the same order as in the PAM header. The "#" +newlines and are in the same order as in the PAM header. The "#" at the beginning of a PAM header line that indicates the line is a comment is not part of the comment. @@ -308,8 +308,8 @@ does not return comments and does not allocate any storage. ... pam.comment_p = &comments; pnm_readpaminit(fileP, &pam, PAM_STRUCT_SIZE(comment_p)); - printf("The comments are:\n"); - printf("%s", comments) + printf("The comments are:\n"); + printf("%s", comments) free(comments); </code> </pre> @@ -318,7 +318,7 @@ does not return comments and does not allocate any storage. <code> const char * comments; ... - comments = strdup("This is a comment 1\nThis is comment 2\n"); + comments = strdup("This is a comment 1\nThis is comment 2\n"); pam.comment_p = &comments; pnm_writepaminit(&pam); free(comments); diff --git a/libpm.html b/libpm.html index ff122a16..c60f1e91 100644 --- a/libpm.html +++ b/libpm.html @@ -54,7 +54,7 @@ them from the argument list. services, need not invoke <b>pm_proginit</b>. But such a program must invoke <b>pm_init()</b>. -<P>By "Netpbm program," we mean a program that is part of +<P>By "Netpbm program," we mean a program that is part of the Netpbm package or is intended to act like one. <b>pm_proginit()</b> does things that all Netpbm programs do by convention. For example, it scans the argument list for <a href="index.html#commonoptions"> @@ -349,8 +349,8 @@ buffer. The <B>nread</B> argument returns the number of bytes read. <B>pm_writelittleshort()</B>, <B>pm_readlittlelong()</B>, and <B>pm_writelittlelong()</B> are routines to read and write 1-byte, 2-byte, and 4-byte pure binary integers in either big- or -little-endian byte order. Note that a "long int" C type might -be wider than 4 bytes, but the "long" routines still read and +little-endian byte order. Note that a "long int" C type might +be wider than 4 bytes, but the "long" routines still read and write 4 bytes. <p><b>pm_readbiglongu()</b>, etc. (names ending in <b>u</b>) are the same @@ -505,12 +505,12 @@ Example: static void logfilewrite(const char * const msg) { - fprintf(mymsglog, "Netpbm message: %s", msg); + fprintf(mymsglog, "Netpbm message: %s", msg); } pm_setusermessagefn(&logfilewrite); - pm_message("Message for the message log"); + pm_message("Message for the message log"); </code> </pre> diff --git a/libsystem.html b/libsystem.html index ffed547d..a83dd1d6 100644 --- a/libsystem.html +++ b/libsystem.html @@ -198,7 +198,7 @@ it is a name to be looked up in the system's program search path The last argument <em>must</em> be NULL to tell <b>pm_system_lp()</b> where the arguments end. -<p>Note that the first argument ("arg0") to a program is +<p>Note that the first argument ("arg0") to a program is conventionally the first word of the command used to run the program, as if it were being run for a shell command. In other words, typically the name of the program. @@ -207,8 +207,8 @@ program. <pre> <code> - pm_system_lp("pnmtojpeg", NULL, NULL, NULL, NULL, - "pnmtojpeg", "mypicture.jpg", "-quality=50", NULL); + pm_system_lp("pnmtojpeg", NULL, NULL, NULL, NULL, + "pnmtojpeg", "mypicture.jpg", "-quality=50", NULL); </code> </pre> @@ -218,7 +218,7 @@ build a shell command using such arguments, unless you're really careful, you may end up building a shell command that does something very different from what you intended, because the argument could contain characters that mean something to the shell such as -"|". +"|". <p><b>pm_system_lp()</b> can also be considerably faster that <b>pm_system()</b>, since it skips the whole running of the shell. @@ -237,11 +237,11 @@ the array identifies the end of the arguments. <code> const char * argArray[3]; - argArray[0] = "pnmtojpeg"; - argArray[1] = "-quality=50"; + argArray[0] = "pnmtojpeg"; + argArray[1] = "-quality=50"; argArray[2] = NULL; - pm_system_vp("pnmtojpeg", argArray, NULL, NULL, NULL, NULL); + pm_system_vp("pnmtojpeg", argArray, NULL, NULL, NULL, NULL); </code> </pre> diff --git a/libtmpfile.html b/libtmpfile.html index dca1f472..6a7e53d9 100644 --- a/libtmpfile.html +++ b/libtmpfile.html @@ -23,8 +23,8 @@ pm_tmpfile(void); <h2>EXAMPLE</h2> -<p>This simple example creates a temporary file, writes "hello -world" to it, then reads back and prints those contents. +<p>This simple example creates a temporary file, writes "hello +world" to it, then reads back and prints those contents. <pre> #include <netpbm/pm.h> @@ -33,13 +33,13 @@ FILE * myfileP; myfile = pm_tmpfile(); -fprintf(myfile, "hello world\n"); +fprintf(myfile, "hello world\n"); fseek(myfileP, 0, SEEK_SET); fread(buffer, sizeof(buffer), 1, myfileP); -fprintf(STDOUT, "temp file contains '%s'\n", buffer); +fprintf(STDOUT, "temp file contains '%s'\n", buffer); fclose(myfileP); diff --git a/libtmpfilefd.html b/libtmpfilefd.html index 1d3cc040..9019023c 100644 --- a/libtmpfilefd.html +++ b/libtmpfilefd.html @@ -24,8 +24,8 @@ pm_tmpfile_fd(void); <h2>EXAMPLE</h2> -<p>This simple example creates a temporary file, writes "hello -world" to it, then reads back and prints those contents. +<p>This simple example creates a temporary file, writes "hello +world" to it, then reads back and prints those contents. <pre> #include <netpbm/pm.h> @@ -34,13 +34,13 @@ int fd; fd = pm_tmpfile(); -write(fd, "hello world\n", 17); +write(fd, "hello world\n", 17); lseek(fd, 0, SEEK_SET); read(fd, buffer, sizeof(buffer)); -fprintf(STDOUT, "temp file contains '%s'\n", buffer); +fprintf(STDOUT, "temp file contains '%s'\n", buffer); close(fd); diff --git a/macptopbm.html b/macptopbm.html index 18939e4a..91cfcee0 100644 --- a/macptopbm.html +++ b/macptopbm.html @@ -34,7 +34,7 @@ image as output. <DD>This option is to get around a problem with some methods of transferring files from the Mac world to the Unix world. Most of these methods leave the Mac files alone, but a few of them add the -"finderinfo" data onto the front of the Unix file. This +"finderinfo" data onto the front of the Unix file. This means an extra 128 bytes to skip over when reading the file. The symptom to watch for is that the resulting PBM file looks shifted to one side. If you get this, try <B>-extraskip</B> 128, and if that diff --git a/mdatopbm.html b/mdatopbm.html index efef800d..8edf70e4 100644 --- a/mdatopbm.html +++ b/mdatopbm.html @@ -51,7 +51,7 @@ ratio used in MicroDesign files. <DT><B>--</B> -<DD>End of options (use this if the filename starts with "-") +<DD>End of options (use this if the filename starts with "-") </DL> diff --git a/mrf.html b/mrf.html index fe7bdd70..b2ee9afa 100644 --- a/mrf.html +++ b/mrf.html @@ -36,7 +36,7 @@ compression works afterward. Description <DT>0 <DD> -magic number - "MRF1" (in ASCII) +magic number - "MRF1" (in ASCII) <DT>4 <DD> @@ -81,7 +81,7 @@ for the recursive subdivision routine should make things clearer: each in this order: top-left, top-right, bottom-left, bottom-right </PRE> -<P>(Note that the "output a 0 bit" stage is not reached for squares +<P>(Note that the "output a 0 bit" stage is not reached for squares of size 1x1, which is what stops it recursing infinitely. I mention this as it may not be immediately obvious.) diff --git a/pam.html b/pam.html index 928b3204..0751c998 100644 --- a/pam.html +++ b/pam.html @@ -24,8 +24,8 @@ dimensional rectangular array. Actually, from another perspective it can be seen as a format for data arranged as a three dimensional array. -<P>The name "PAM" is an acronym derived from "Portable -Arbitrary Map." This derivation makes more sense if you consider +<P>The name "PAM" is an acronym derived from "Portable +Arbitrary Map." This derivation makes more sense if you consider it in the context of the other Netpbm format names: PBM, PGM, and PPM. <P>This format does not define the meaning of the data at any particular @@ -65,7 +65,7 @@ format and PBM, PGM, PPM, and PNM. Here is a little enlightenment: and PPM formats collectively. It is also the name of a group of library functions that can each handle all three of those formats. -<P>"PAM" is in fact a fourth format. But it is so general +<P>"PAM" is in fact a fourth format. But it is so general that you can represent the same information in a PAM image as you can in a PBM, PGM, or PPM image. And in fact a program that is designed to read PBM, PGM, or PPM and does so with a recent version of the @@ -73,7 +73,7 @@ Netpbm library, will read an equivalent PAM image just fine and the program will never know the difference. <P>To confuse things more, there is a collection of library routines -called the "pam" functions that read and write the PAM +called the "pam" functions that read and write the PAM format, but also read and write the PBM, PGM, and PPM formats. They do this because the latter formats are much older and more popular, so even a new program must work with them. Having the library handle all @@ -105,7 +105,7 @@ ENDHDR </tt> </pre> -<P>The header begins with the ASCII characters "P7" followed +<P>The header begins with the ASCII characters "P7" followed by newline. This is the magic number. <P>Note: <b>xv</b> thumbnail images also start with the "P7" magic number. @@ -116,7 +116,7 @@ of the format makes it easy to distinguish PAM from that format, though). text. Each line ends with and is delimited by a newline character. <P>Each header line consists of zero or more whitespace-delimited -tokens or begins with "#". If it begins with "#" +tokens or begins with "#". If it begins with "#" it is a comment and the rest of this specification does not apply to it. @@ -187,7 +187,7 @@ Each sample consists of an unsigned integer in pure binary format, with the most significant byte first. The number of bytes is the minimum number of bytes required to represent the maxval of the image. -<p>The character referred to as "newline" herein is the +<p>The character referred to as "newline" herein is the character known in ASCII as Line Feed or LF. <H2 id="limitations">LIMITATIONS</H2> @@ -245,7 +245,7 @@ image. The first plane represents red, the second green, and the third blue. <p>Each of the visual image formats mentioned above has a variation that contains transparency information. In that variation, the tuple type -has "_ALPHA" added to it (e.g. "RGB_ALPHA") and one +has "_ALPHA" added to it (e.g. "RGB_ALPHA") and one more plane. The highest numbered plane is the opacity plane (sometimes called an transparency plane or transparency plane). @@ -281,7 +281,7 @@ be consistent with conventional values for the older Netpbm formats. <h2 id="filename">FILE NAME</h2> -<p>The conventional suffix for the name of a PAM file is ".pam". +<p>The conventional suffix for the name of a PAM file is ".pam". But this is not required. diff --git a/pamaddnoise.html b/pamaddnoise.html index 772d18a0..a151675b 100644 --- a/pamaddnoise.html +++ b/pamaddnoise.html @@ -149,11 +149,11 @@ type option. The default noise type is <b>gaussian</b>. <H2 id="references">REFERENCES</H2> <UL> -<LI>"Adaptive Image Restoration in Signal-Dependent Noise" +<LI>"Adaptive Image Restoration in Signal-Dependent Noise" by R. Kasturi Institute for Electronic Science, Texas Tech University, 1982 -<LI>"Digital Image Processing Algorithms" by Ioannis Pitas, +<LI>"Digital Image Processing Algorithms" by Ioannis Pitas, Prentice Hall, 1993 ISBN 0-13-145814-0 </UL> diff --git a/pamarith.html b/pamarith.html index 97e68ea8..e7cbe79a 100644 --- a/pamarith.html +++ b/pamarith.html @@ -42,9 +42,9 @@ input image is the equivalent PAM image of tuple type and if it produces a PBM, PGM, or PPM output, produces the equivalent of the PAM image which is the result of the calculation. -<p>The first <i>pamfile</i> argument identifies the "left" +<p>The first <i>pamfile</i> argument identifies the "left" argument image; the second <i>pamfile</i> argument identifies the -"right" one. +"right" one. <p>If the output is PAM, the tuple type is the same as the tuple type of the left input image. @@ -82,7 +82,7 @@ according to the function you select. one that applies when a PAM image represents a visual image), is that it represents a fraction of some maximum. The maxval of the image corresponds to some maximum value (in the case of a visual image, it -corresponds to "full intensity."), and a sample value +corresponds to "full intensity."), and a sample value divided by the maxval gives the fraction. <p>For <b>pamarith</b>, this interpretation applies to the regular diff --git a/pambackground.html b/pambackground.html index 40ed77fe..9fedda8a 100644 --- a/pambackground.html +++ b/pambackground.html @@ -56,7 +56,7 @@ this case, you might use <b>ppmchange</b> to change all similar colors to a single one first. For example, if the photograph is a building against a blue sky, where nothing remotely sky-blue appears in the building, you could use <b>ppmchange</b> to change all pixels within -20% of "SkyBlue" to SkyBlue, then run <b>pambackground</b> +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 @@ -67,7 +67,7 @@ of <b>ppmchange</b> like this: <pre> <kbd> - $ echo "#(fred)/#(fgreen)/#(fblue)" >/tmp/bodyskl + $ echo "#(fred)/#(fgreen)/#(fblue)" >/tmp/bodyskl $ color=$(pamcut 0 0 1 1 myimage.ppm | ppmtoarbtxt /tmp/bodyskl) </kbd> </pre> diff --git a/pambayer.html b/pambayer.html index f66af39b..f96c071f 100644 --- a/pambayer.html +++ b/pambayer.html @@ -55,7 +55,7 @@ is the same, the sample values have different meanings) or PAM image of arbitrary tuple type. <b>pambayer</b> looks at only the first plane of the input. -<p>The output image is a PAM image of tuple type "RGB", i.e. +<p>The output image is a PAM image of tuple type "RGB", i.e. a standard color image. You can convert this to PPM with <a href="pamtopnm.html"><b>pamtopnm</b></a>. diff --git a/pamcomp.html b/pamcomp.html index 9c8d0e0a..6616680b 100644 --- a/pamcomp.html +++ b/pamcomp.html @@ -91,7 +91,7 @@ image. <B>pamcomp</B> uses only parts of the overlay image that fit within the underlying image. <p>The output image is a PAM image. Its tuples are color, grayscale, or black -and white, whichever is the "highest" format between the two input +and white, whichever is the "highest" format between the two input images. The maxval of the output is the least common multiple of the maxvals of the input, up to the maximum possible PAM maxval, 65535. diff --git a/pamcrater.html b/pamcrater.html index 79946e2c..16189d06 100644 --- a/pamcrater.html +++ b/pamcrater.html @@ -52,7 +52,7 @@ Rucker. <p>A terrain map is a two dimensional map of terrain elevations. the PAM image that <b>pamcrater</b> produces is therefore not a visual image but a -depth-one image of tuple type "elevation", with the sample value +depth-one image of tuple type "elevation", with the sample value being proportional to an elevation. <p>You can visualize the terrain map by generating a shaded relief image of it @@ -170,7 +170,7 @@ Suisse/Schweiz/Svizzera/Svizra/Switzerland <P>Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, without any conditions or restrictions. This software is provided -"as is" without express or implied warranty. +"as is" without express or implied warranty. <H2 id="history">HISTORY</H2> @@ -192,12 +192,12 @@ code, happened in between). <h3>PLUGWARE!</h3> -<p>If you like this kind of stuff, you may also enjoy "James Gleick's -Chaos--The Software" for MS-DOS, available for $59.95 from your +<p>If you like this kind of stuff, you may also enjoy "James Gleick's +Chaos--The Software" for MS-DOS, available for $59.95 from your local software store or directly from Autodesk, Inc., Attn: Science Series, 2320 Marinship Way, Sausalito, CA 94965, USA. Telephone: (800) 688-2344 toll-free or, outside the U.S. (415) 332-2344 Ext -4886. Fax: (415) 289-4718. "Chaos--The Software" includes a more +4886. Fax: (415) 289-4718. "Chaos--The Software" includes a more comprehensive fractal forgery generator which creates three-dimensional landscapes as well as clouds and planets, plus five more modules which explore other aspects of Chaos. The user guide of diff --git a/pamditherbw.html b/pamditherbw.html index 6277517d..c1f0bacf 100644 --- a/pamditherbw.html +++ b/pamditherbw.html @@ -142,11 +142,11 @@ invocations. <H2 id="references">REFERENCES</H2> -<p>The only reference you need for this stuff is "Digital -Halftoning" by Robert Ulichney, MIT Press, ISBN 0-262-21009-6. +<p>The only reference you need for this stuff is "Digital +Halftoning" by Robert Ulichney, MIT Press, ISBN 0-262-21009-6. -<P>The Hilbert curve space filling method is taken from "Digital -Halftoning with Space Filling Curves" by Luiz Velho, Computer +<P>The Hilbert curve space filling method is taken from "Digital +Halftoning with Space Filling Curves" by Luiz Velho, Computer Graphics Volume 25, Number 4, proceedings of SIGRAPH '91, page 81. ISBN 0-89791-436-8 diff --git a/pamedge.html b/pamedge.html index 18675a9a..f508425c 100644 --- a/pamedge.html +++ b/pamedge.html @@ -30,7 +30,7 @@ with the threshold value to get a PBM (bilevel image) of the edges. The edge detection technique used is to take the Pythagorean sum of two Sobel gradient operators at 90 degrees to each other. For more -details see "Digital Image Processing" by Gonzalez and +details see "Digital Image Processing" by Gonzalez and Wintz, chapter 7. <P>The maxval of the output is the same as the maxval of the input, except at diff --git a/pamexec.html b/pamexec.html index c663a72a..a5f9b3af 100644 --- a/pamexec.html +++ b/pamexec.html @@ -14,7 +14,7 @@ pamexec - Execute a shell command on each image in a Netpbm image stream <B>pamexec</B> -["<i>command</i>"] +["<i>command</i>"] [<I>netpbmfile</I>] @@ -81,7 +81,7 @@ you can buffer through a temporary file like this: <pre> <kbd> - pamexec "cat >/tmp/x; head -3 x" myvideo.ppm + pamexec "cat >/tmp/x; head -3 x" myvideo.ppm </kbd> </pre> diff --git a/pamflip.html b/pamflip.html index e95035bc..05f07d58 100644 --- a/pamflip.html +++ b/pamflip.html @@ -174,12 +174,12 @@ slightly more slowly because of extra overhead in manipulating temporary files. Also, if your environment isn't set up to make temporary files possible, <b>pamflip</b> will fail. -<p>Doing the entire transformation "in memory" doesn't speed +<p>Doing the entire transformation "in memory" doesn't speed things up as much as you might think, because even with the temporary files, the data is just as likely to be in memory. Virtual memory gets paged to disk and disk files get cached in memory. In fact, the pixels fit much more compactly into memory when stored in a temporary -file than when stored "in memory" because <b>pamflip</b> +file than when stored "in memory" because <b>pamflip</b> uses a more efficient format. So you're likely to have <em>less</em> disk I/O when you allow <b>pamflip</b> less memory. diff --git a/pamfunc.html b/pamfunc.html index a7516a7e..34408618 100644 --- a/pamfunc.html +++ b/pamfunc.html @@ -67,7 +67,7 @@ the sample value, and the maxval indicates the width of the bit string. <b>-min</b>, and <b>-max</b>. <p>As an example, consider an image with maxval 100 and a sample value of 10 -and a function of "multiply by 5." The argument to the function is +and a function of "multiply by 5." The argument to the function is 10/100 (0.1) and the result is 5 * 0.1 = 0.5. In the simplest case, the maxval of the output is also 100, so the output sample value is 0.5 * 100 = 50. As you can see, we could just talk about the sample values themselves @@ -95,7 +95,7 @@ The maxval must be a full binary count (a power of two minus one, such as 0xff) and the number of ones in it is the width of the bit string. <p>As an example, consider an image with maxval 15 and a sample value of 5 -and a function of "and with 0100". The argument to the function is +and a function of "and with 0100". The argument to the function is 0101 and the result is 0100. <p>In this example, it doesn't make any practical difference what we consider @@ -153,8 +153,8 @@ greater than the width indicated by the maxval. <i>integer</i>/<i>maxval</i>. If the result is greater than one, it is clipped to one. If it is less than zero, it is clipped to zero. - <p>Note that in mathematics, this entity is called an "addend," - and an "adder" is a snake. We use "adder" because + <p>Note that in mathematics, this entity is called an "addend," + and an "adder" is a snake. We use "adder" because it makes more sense. <DT><B>-subtractor=<i>integer</i></B> @@ -165,8 +165,8 @@ greater than the width indicated by the maxval. clipped to one. If it is less than zero, it is clipped to zero. <p>Note that in mathematics, this entity is called a - "subtrahend" rather than a "subtractor." We use - "subtractor" because it makes more sense. + "subtrahend" rather than a "subtractor." We use + "subtractor" because it makes more sense. <P>This is the same function as you would get with <b>-adder</b>, specifying the negative of <i>integer</i>. diff --git a/pammasksharpen.html b/pammasksharpen.html index 70b17bb6..d10a0805 100644 --- a/pammasksharpen.html +++ b/pammasksharpen.html @@ -40,7 +40,7 @@ via an unsharp mask, which you supply as another Netpbm image. <p>An unsharp mask is generally a blurred version of the original image. The sharpening computation is this: Calculate the -"edgeness" of a sample in the input image as the signed +"edgeness" of a sample in the input image as the signed difference between the sample value and the corresponding sample in the unsharp mask. This tells how different the pixel is from its neighbors. Add a multiple of the edgeness to the original sample to @@ -64,7 +64,7 @@ number of pixels. <p>When you create an unsharp mask like this, you will have to choose the side length of the convolution kernel. That length implements the parameter of unsharp mask sharpening usually known as -"radius." In particular, a radius of R pixels corresponds to a +"radius." In particular, a radius of R pixels corresponds to a convolution kernel 2R+1 pixels on a side. <p>Radius is a very important parameter; you can ruin an image with a @@ -89,7 +89,7 @@ of edgeness that gets added to each sample as described above. <p><i>realnum</i> is a nonnegative real decimal number. Zero means no sharpening at all. -<p>This parameter is known as "amount" in ImageMagick. +<p>This parameter is known as "amount" in ImageMagick. <p>The default is 1.0. diff --git a/pammosaicknit.html b/pammosaicknit.html index d258b1c0..6907c3e2 100644 --- a/pammosaicknit.html +++ b/pammosaicknit.html @@ -32,15 +32,15 @@ knitting patterns</a>. The program inputs a black-and-white Netpbm image that describes a mosaic knitting pattern and outputs a color Netpbm image of the same pattern but with invalid runs shown in red.</p> -<p>A valid knitting pattern starts with a "black" row on the -bottom and alternates "white" and "black" -rows. A "black" row can contain any arrangement of black pixels -but no more than three consecutive white pixels. A "white" row +<p>A valid knitting pattern starts with a "black" row on the +bottom and alternates "white" and "black" +rows. A "black" row can contain any arrangement of black pixels +but no more than three consecutive white pixels. A "white" row can contain any arrangement of white pixels but no more than three -consecutive black pixels. Columns wrap horizontally, so a "white" +consecutive black pixels. Columns wrap horizontally, so a "white" row that both begins and ends with two black pixels is deemed to contain four consecutive black pixels. Because this is an invalid -number for a "white" row, those four pixels will be recolored red +number for a "white" row, those four pixels will be recolored red in the output image.</p> <p>For clarity, there are two shades of red in the output image. Dark diff --git a/pamoil.html b/pamoil.html index 8bae9fa1..5ce61f31 100644 --- a/pamoil.html +++ b/pamoil.html @@ -25,10 +25,10 @@ pamoil - turn a PAM image into an oil painting <p>This program is part of <a href="index.html">Netpbm</a>. -<p><b>pamoil</b> reads a Netpbm image as input and does an "oil -transfer", and writes the same type of Netpbm image as output. +<p><b>pamoil</b> reads a Netpbm image as input and does an "oil +transfer", and writes the same type of Netpbm image as output. -<P>The oil transfer is described in "Beyond Photography" by +<P>The oil transfer is described in "Beyond Photography" by Holzmann, chapter 4, photo 7. It's a sort of localized smearing. <P>The smearing works like this: First, assume a grayscale image. For diff --git a/pampaintspill.html b/pampaintspill.html index 75641534..c71db552 100644 --- a/pampaintspill.html +++ b/pampaintspill.html @@ -32,8 +32,8 @@ from its value. <p>This program is part of <a href="index.html">Netpbm</a>.</p> <p><b>pampaintspill</b> produces a smooth color gradient from all of the -non-background-colored pixels in an input image, effectively "spilling -paint" onto the background. <b>pampaintspill</b> is similar to +non-background-colored pixels in an input image, effectively "spilling +paint" onto the background. <b>pampaintspill</b> is similar to <b>pamgradient</b> but differs in the following characteristics:</p> <ul> diff --git a/pamperspective.html b/pamperspective.html index 618a6c6f..9f5e9f01 100644 --- a/pamperspective.html +++ b/pamperspective.html @@ -215,8 +215,8 @@ number, <b>pamperspective</b> does not allow this format. By default <b>pamperspective</b> outputs exactly the above parallelogram, sheared to a rectangle. With the following options, it is possible to make <b>pamperspective</b> output a larger or smaller -portion, which we call the "visible part." We refer to the -default rectangle as the "frame." The visible part is always +portion, which we call the "visible part." We refer to the +default rectangle as the "frame." The visible part is always a rectangle the axes of which are parallel to those of the frame. <p>The frame options are additive. All the parts of the image diff --git a/pamrecolor.html b/pamrecolor.html index d6aea98e..c69c3b9e 100644 --- a/pamrecolor.html +++ b/pamrecolor.html @@ -111,7 +111,7 @@ the format that uses sRGB. <dd>Wide-gamut RGB with a D50 reference white</dd> </dl> -<p>The default is "ntsc" because this is the color space that the +<p>The default is "ntsc" because this is the color space that the Netpbm format of Netpbm and many other graphics utilities. As a counterexample, <a href="http://www.gimp.org/">GIMP</a> uses sRGB as its native color @@ -131,7 +131,7 @@ contribution of each color channel to the overall luminance as red, green, and blue multipliers. These three options must be used together, and the three <i>fraction</i> values must sum to 1.0. For example, you can specify the ProPhoto (ROMM) RGB color space with -"<b>--rmult</b>=0.2880402 <b>--gmult</b>=0.7118741 <b>--bmult</b>=0.0000857".</dd> +"<b>--rmult</b>=0.2880402 <b>--gmult</b>=0.7118741 <b>--bmult</b>=0.0000857".</dd> <dt><b>--targetcolor</b>=<i>color</i></dt> <dd>Designate <i>color</i> as the target color for the @@ -139,7 +139,7 @@ image. <b>pamrecolor</b> will make each pixel as close as possible to <i>color</i> subject to the constraint that the luminance must stay the same as in the original image. Specify <i>color</i> as in the <a href="libppm.html#colorname">argument of the <b>ppm_parsecolor()</b> -library routine</a> (e.g., "hotpink" or "#ff69b4"). +library routine</a> (e.g., "hotpink" or "#ff69b4"). <p>If you specify neither <b>--targetcolor</b> nor <b>--colorfile</b>, <b>pamrecolor</b> will randomly select a target color for @@ -208,7 +208,7 @@ appropriate <b>--colorspace</b> value for your conversion tool.</p> <ul> <li>Specify a color file that is identical to the input image but with -some large, colored text added to it. The text will "magically" +some large, colored text added to it. The text will "magically" vanish when the image is converted to grayscale.</li> <li>Provide a low-contrast grayscale image — perhaps a secret diff --git a/pamrubber.html b/pamrubber.html index 1ebe15ba..30cce228 100644 --- a/pamrubber.html +++ b/pamrubber.html @@ -33,8 +33,8 @@ hyphens instead of single hyphen to denote options.</p> of <a href="http://netpbm.sourceforge.net/doc/index.html">Netpbm</a>.</p> <p>The <b>pamrubber</b> utility converts a pam image into a new image with the -contents moved around. The transformation is often called "rubber -sheeting": you identify control points (CP) on the source image and +contents moved around. The transformation is often called "rubber +sheeting": you identify control points (CP) on the source image and specify new positions for those points in the new image. <b>pamrubber</b> moves all the pixels around, stretching and compressing as necessary, as if the original image were on a sheet of rubber and you pulled on the sheet @@ -43,7 +43,7 @@ to make the control points move to their new locations. <p>The new image has the same dimensions and format as the original. <p>The transformation can happen in two very different ways, called -"quad" and "tri." With the former, you must specify four +"quad" and "tri." With the former, you must specify four control points (for both source and target). These are the corners of two quadrilaterals that will act as the coordinate system for both source and target images. Consider them as non-orthogonal (0,0), (0,1), (1,0) and (1,1) @@ -58,18 +58,18 @@ rectangle. When you specify only one control point, <b>pamrubber</b> uses a rectangle from the top left corner of the image to the single control point.</p> -<p>In "tri" mode, <b>pamrubber</b> conceptually cuts up the source +<p>In "tri" mode, <b>pamrubber</b> conceptually cuts up the source and target image into triangles. It Transforms within each corresponding pair of triangles in a stretching fashion. It's like pulling on the three corners of the triangle. In this mode, each pixel in the source image gets mapped to a position in the target image. No pixels are lost. -<p>When, in "tri" mode, you specify only a single control point in +<p>When, in "tri" mode, you specify only a single control point in the source and target image, <b>pamrubber</b> creates four triangles from this point to the four corners of the image. With two points, the program creates six triangles from the two endpoints of the line connecting the two points, again to the four corners of the image. Three control points is in a way the -core of this utility in "tri" mode. Between the three edges of the +core of this utility in "tri" mode. Between the three edges of the central triangle and the four edges of the image, <b>pamrubber</b> constructs another seven triangles. Four control points define two central connected triangles. In total this results in cutting the source and target image up diff --git a/pamscale.html b/pamscale.html index 75dae3d9..c861fdba 100644 --- a/pamscale.html +++ b/pamscale.html @@ -129,7 +129,7 @@ it down (without <B>-nomix</B>) to discard some information, then scale it back up using <B>pamstretch</B>. <P>Or scale it back up with <B>pamscale</B> and create a -"pixelized" image, which is sort of a computer-age version +"pixelized" image, which is sort of a computer-age version of blurring. diff --git a/pamshadedrelief.html b/pamshadedrelief.html index 7cdfc19f..179313be 100644 --- a/pamshadedrelief.html +++ b/pamshadedrelief.html @@ -105,7 +105,7 @@ Suisse/Schweiz/Svizzera/Svizra/Switzerland <P>Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, without any conditions or restrictions. This software is provided -"as is" without express or implied warranty. +"as is" without express or implied warranty. <H2 id="history">HISTORY</H2> diff --git a/pamsplit.html b/pamsplit.html index f5149358..15972eb9 100644 --- a/pamsplit.html +++ b/pamsplit.html @@ -37,11 +37,11 @@ in the input into a separate file, in the same format. <P><I>output_file_pattern</I> tells how to name the output files. It is the file name of the output file, except that the first -occurrence of "%d" in it is replaced by the image sequence +occurrence of "%d" in it is replaced by the image sequence number in unpadded ASCII decimal, with the sequence starting at 0. If -there is no "%d" in the pattern, <B>pamsplit</B> fails. +there is no "%d" in the pattern, <B>pamsplit</B> fails. -<P>The default output file pattern is "image%d". +<P>The default output file pattern is "image%d". <p>The <b>-padname</b> option specifies to how many characters you want the image sequence number in the output file name padded with diff --git a/pamstack.html b/pamstack.html index 0edce2e5..b0818db7 100644 --- a/pamstack.html +++ b/pamstack.html @@ -31,7 +31,7 @@ produces a PAM image as output, consisting of all the planes (channels) of the inputs, stacked in the order specified. <p>For any one (but not more) of the input files, you may specify -"-" to mean Standard Input. If you specify no arguments at all, +"-" to mean Standard Input. If you specify no arguments at all, the input is one file: Standard Input. <P>The output is the same dimensions as the inputs, except that the diff --git a/pamstereogram.html b/pamstereogram.html index 82318d9d..13903ad0 100644 --- a/pamstereogram.html +++ b/pamstereogram.html @@ -351,7 +351,7 @@ appears repeated multiple times and overlapped with itself, but it is not hidden.</p> <p>You create an MTS with <b>pamstereogram</b> by passing the filename -of a PAM "texture image" with a <b>-texfile</b> option. A +of a PAM "texture image" with a <b>-texfile</b> option. A texture image portrays the same 3-D object as the depth-map image but indicates the colors that the program should apply to the object.</p> diff --git a/pamtilt.html b/pamtilt.html index 0748ba6b..7b51a679 100644 --- a/pamtilt.html +++ b/pamtilt.html @@ -42,7 +42,7 @@ pamtilt - print the tilt angle of a PGM file floating-point number (the angle in degrees) for use as the argument to pnmrotate. -<p>"Document skew" is the name given to what happens when +<p>"Document skew" is the name given to what happens when you feed a page into an image scanner at an angle: the resulting image is tilted. <b>pamtilt</b> aims to help correct that. diff --git a/pamtodjvurle.html b/pamtodjvurle.html index 48428a4f..adeafb3e 100644 --- a/pamtodjvurle.html +++ b/pamtodjvurle.html @@ -38,7 +38,7 @@ considered transparent. href="libppm.html#colorname">argument of the <b>ppm_parsecolor()</b> library routine</a>. -<p>Default is "white". +<p>Default is "white". </DL> <H2 id="seealso">SEE ALSO</H2> diff --git a/pamtofits.html b/pamtofits.html index 0ecc8064..b3bbe30e 100644 --- a/pamtofits.html +++ b/pamtofits.html @@ -31,8 +31,8 @@ consist of a three-plane image (NAXIS = 3, NAXIS3 = 3). <H2 id="options">OPTIONS</H2> -<p><b>-min</b> and <b>-max</b> tell <b>pamtofits</b> what "physical -values" zero and maxval sample values, respectively, in the input +<p><b>-min</b> and <b>-max</b> tell <b>pamtofits</b> what "physical +values" zero and maxval sample values, respectively, in the input image represent. Physical values are a FITS concept. <b>pamtofits</b> sets up the <b>BSCALE</b> and <b>BZERO</b> FITS header cards to indicate this information. diff --git a/pamtogif.html b/pamtogif.html index 61fe6ec7..6e390cc1 100644 --- a/pamtogif.html +++ b/pamtogif.html @@ -112,8 +112,8 @@ the variability. colormap in the GIF file, instead of the colors from <I>netpbmfile</I>. <I>mapfile</I> can be any PPM file; all that matters is the colors in it. If the colors in <I>netpbmfile</I> do not match those in -<I>mapfile</I>, <b>pamtogif</b> matches them to a "best -match." You can obtain a much better result by using <b>pnmremap</b> +<I>mapfile</I>, <b>pamtogif</b> matches them to a "best +match." You can obtain a much better result by using <b>pnmremap</b> to change the colors in the input to those in the map file. <p>The <i>mapfile</i> file is not a palette file, just an image whose @@ -165,14 +165,14 @@ specify. Closeness is measured as a Cartesian distance between colors in RGB space. If multiple colors are equidistant, <B>pamtogif</B> chooses one of them arbitrarily. -<P>However, if you prefix your color specification with "=", +<P>However, if you prefix your color specification with "=", e.g. <B>-transparent==red</B>, only the exact color you specify will be transparent. If that color does not appear in the image, there will be no transparency. <B>pamtogif</B> issues an information message when this is the case. <p>When you specify <b>-transparent</b>, <b>pamtogif</b> ignores -explicit transparency information (the "alpha channel") in +explicit transparency information (the "alpha channel") in the input image. <DT><B>-alpha=</B><I>pgmfile</I> @@ -203,7 +203,7 @@ transparent. <DD>This specifies the foreground color for transparent pixels. A viewer may use the foreground color for a transparent pixel if it -chooses not to have another color "show through.". The +chooses not to have another color "show through.". The default is black. <p>This applies only to pixels that are transparent in the GIF because @@ -311,7 +311,7 @@ users since 1989. <p>The main outward change in the conversion from <b>ppmtogif</b> to <b>pamtogif</b> was that <b>pamtogif</b> was able to use transparency -information ("alpha channel") in PAM input, whereas with +information ("alpha channel") in PAM input, whereas with <b>ppmtogif</b>, one had to supply the transparency mask in a separate pseudo-PGM image (via the <b>-alpha</b> option). diff --git a/pamtojpeg2k.html b/pamtojpeg2k.html index 2dec593e..39db5f98 100644 --- a/pamtojpeg2k.html +++ b/pamtojpeg2k.html @@ -145,7 +145,7 @@ multiplicative inverse of (1 divided by) the compression ratio. <p>Before Netpbm 10.61 (December 2012), the default was a compression ratio of 1, and if <b>pamtojpeg2k</b> could not make the output that small, it just made it as small as it could, with zero quality. You know this is happening -when you see the warning message, "empty layer generated." +when you see the warning message, "empty layer generated." <DT><B>-verbose</b> diff --git a/pamtooctaveimg.html b/pamtooctaveimg.html index 46879573..9cadc135 100644 --- a/pamtooctaveimg.html +++ b/pamtooctaveimg.html @@ -28,7 +28,7 @@ <p><b>pamtooctaveimg</b> reads a Netpbm image as input and produces a <a href="http://www.octave.org/">GNU Octave</a> image file as output. -<p>An Octave image file (called "Octave's image format" in +<p>An Octave image file (called "Octave's image format" in Octave documentation) is a particular kind of Octave data file. It describes two matrices: diff --git a/pamtopnm.html b/pamtopnm.html index 24971df7..60ed9f03 100644 --- a/pamtopnm.html +++ b/pamtopnm.html @@ -32,7 +32,7 @@ appropriate, as output. <P><B>pamtopnm</B> assumes the PAM image represents the information required for a PBM, PGM, or PPM image if its tuple type is -"BLACKANDWHITE", "GRAYSCALE", or "RGB" +"BLACKANDWHITE", "GRAYSCALE", or "RGB" and its depth and maxval are appropriate. If this is not the case, <B>pamtopnm</B> fails. diff --git a/pamtosvg.html b/pamtosvg.html index b799511e..cbb1b42d 100644 --- a/pamtosvg.html +++ b/pamtosvg.html @@ -60,8 +60,8 @@ CorelTrace, and Autotrace do. It is in fact derived from Autotrace. <p>SVG is a gigantic format, capable of amazing things. <b>pamtosvg</b> exploits only a morsel of it. The SVG image produced by <b>pamtosvg</b> -consists of a single <svg> element, which has a "width" -attribute and a "height" attribute. The value of that element +consists of a single <svg> element, which has a "width" +attribute and a "height" attribute. The value of that element is composed of <path> elements. That's it. <p>In the SVG output, distances are unitless, with one unit corresponding @@ -144,7 +144,7 @@ as a straight line. <dd>Create a log of the curve tracing process (suitable for debugging). Put it in the file named <i>inputfile</i><b>.log</b> in the current directory, where <i>inputfile</i> is the root of the input -file name, or "pamtosvg" if the input is from Standard Input +file name, or "pamtosvg" if the input is from Standard Input or a file with a weird name. <dt><b>-preserve-width</b> @@ -175,7 +175,7 @@ when computing the tangent at that point. Default is 3. <H2 id="applicationnotes">Application Notes</H2> <p>A convenient way to view an SVG document is with a web browser. Many -understand a file whose name ends in ".svg" to be an SVG +understand a file whose name ends in ".svg" to be an SVG image and can render it. diff --git a/pamtotga.html b/pamtotga.html index 74deeca9..6653850c 100644 --- a/pamtotga.html +++ b/pamtotga.html @@ -107,10 +107,10 @@ 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 a transparency channel in a PAM. It recognized -tuple type "RGBA". But when this kind of PAM image was later +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> -changed to recognize "RGB_ALPHA" instead of "RGBA". +"RGB_ALPHA". So in Netpbm 10-26 (January 2005), <b>pamtotga</b> +changed to recognize "RGB_ALPHA" instead of "RGBA". <H2 id="author">AUTHOR</H2> diff --git a/pamtotiff.html b/pamtotiff.html index 0b482e0a..274c8239 100644 --- a/pamtotiff.html +++ b/pamtotiff.html @@ -64,7 +64,7 @@ as output. <p>Actually, it handles multi-image Netpbm streams, producing multi-image TIFF streams (i.e. a TIFF stream with multiple -"directories"). But before Netpbm 10.27 (March 2005), it +"directories"). But before Netpbm 10.27 (March 2005), it ignored all but the first Netpbm image in the input stream. <h3 id="output">The Output File</h3> @@ -191,9 +191,9 @@ Actually, with very old TIFF libraries, <b>-lzw</b> works because no distributors of the TIFF library were sensitive yet to the patent issue. -<p><b>-flate</b> chooses "flate" compression, which is the +<p><b>-flate</b> chooses "flate" compression, which is the patent-free compression common in the Unix world implemented by the -"Z" library. It is what the PNG format uses. +"Z" library. It is what the PNG format uses. <H4 id="faxcompression">Fax Compression</H4> @@ -268,16 +268,16 @@ before Netpbm 9.21 (December 2001). has no effect. <P>The <B>-minisblack</B> and <B>-miniswhite</B> options force the -output image to have a "minimum is black" or "minimum -is white" photometric, respectively. If you don't specify +output image to have a "minimum is black" or "minimum +is white" photometric, respectively. If you don't specify either, <B>pamtotiff</b> uses minimum is black except when using Group 3 or Group 4 compression, in which case <B>pamtotiff</B> follows CCITT -fax standards and uses "minimum is white." This usually +fax standards and uses "minimum is white." This usually results in better compression and is generally preferred for bilevel coding. <P>Before February 2001, <B>pamtotiff</B> always produced -"minimum is black," because of a bug. In either case, +"minimum is black," because of a bug. In either case, <B>pamtotiff</B> sets the photometric interpretation tag in the TIFF output according to which photometric is actually used. @@ -329,7 +329,7 @@ Each tag specification is a name and a value separated by an equal sign. The name is the name of the tag type, except in arbitrary upper/lower case. One place to see the names of TIFF tag types is in the TIFF library's <b>tiff.h</b> file, where there is a macro defined -for each consisting of "TIFF_" plus the name. E.g. for +for each consisting of "TIFF_" plus the name. E.g. for the SUBFILETYPE tag type, there is a macro TIFF_SUBFILETYPE. <p>The format of the value specification for a tag (stuff after the diff --git a/pamtouil.html b/pamtouil.html index ace512e3..9e59393b 100644 --- a/pamtouil.html +++ b/pamtouil.html @@ -50,7 +50,7 @@ in the RGB database. resulting UIL output. If not specified, will default to the filename (without extension) of the ppmfile argument. If <B>-name</B> is not specified and no ppmfile is specified (i.e. piped input), the - prefix string will default to the string "noname". + prefix string will default to the string "noname". </DL> diff --git a/pamtowinicon.html b/pamtowinicon.html index 7e6340d0..dbcd9d7c 100644 --- a/pamtowinicon.html +++ b/pamtowinicon.html @@ -97,7 +97,7 @@ mask</TD></TR> <H3 id="andmask">AND Mask</H3> -The so-called ‘AND mask’ is a special feature of Microsoft +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 transparency channel, but it is also used for e.g. shading the icon while dragging. See diff --git a/pamtoxvmini.html b/pamtoxvmini.html index 74625da6..ae975bad 100644 --- a/pamtoxvmini.html +++ b/pamtoxvmini.html @@ -8,7 +8,7 @@ Updated: 02 April 2006 <H2>NAME</H2> -pamtoxvmini - convert Netpbm image to an XV "thumbnail" picture +pamtoxvmini - convert Netpbm image to an XV "thumbnail" picture <H2 id="synopsis">SYNOPSIS</H2> @@ -21,8 +21,8 @@ pamtoxvmini - convert Netpbm image to an XV "thumbnail" picture <p>This program is part of <a href="index.html">Netpbm</a>. <p><b>pamtoxvmini</b> reads a Netpbm image (PAM or PNM) and produces -an XV "thumbnail" picture (a miniature picture normally -generated by the "VisualSchnauzer" browser) as output. +an XV "thumbnail" picture (a miniature picture normally +generated by the "VisualSchnauzer" browser) as output. <H2 id="seealso">SEE ALSO</H2> diff --git a/pamundice.html b/pamundice.html index 67c15082..549d37fe 100644 --- a/pamundice.html +++ b/pamundice.html @@ -119,10 +119,10 @@ specifiers are: <dl> <dt><b>d</b> -<dd>"down": The rank (row) number, starting with 0. +<dd>"down": The rank (row) number, starting with 0. <dt><b>a</b> -<dd>"across": The file (column) number, starting with 0. +<dd>"across": The file (column) number, starting with 0. <dt><b>%</b> <dd>The per cent character (%). @@ -139,11 +139,11 @@ the file that contains the tile at Rank 0, File 5, you: <ul> -<li>replace the "%2d" with the rank number, as a 2 digit -decimal number: "00" +<li>replace the "%2d" with the rank number, as a 2 digit +decimal number: "00" -<li>Replace the "%2a" with the file number, as a 2 digit -decimal number: "05" +<li>Replace the "%2a" with the file number, as a 2 digit +decimal number: "05" </ul> <p>Note that this pattern describes file names that <b>pamdice</b> diff --git a/pamx.html b/pamx.html index 18a5c832..5c9c9984 100644 --- a/pamx.html +++ b/pamx.html @@ -163,7 +163,7 @@ image. <dt><b>-title=</b><i>text</i> <dd>Set the title bar title of the window. Default is the file name of -the input file, or "stdin" if the image is from Standard Input. +the input file, or "stdin" if the image is from Standard Input. </dl> diff --git a/pbm.html b/pbm.html index 1c10daaf..9cd77aba 100644 --- a/pbm.html +++ b/pbm.html @@ -43,8 +43,8 @@ no data, delimiters, or padding before, after, or between images. <UL> -<LI>A "magic number" for identifying the file type. -A pbm image's magic number is the two characters "P4". +<LI>A "magic number" for identifying the file type. +A pbm image's magic number is the two characters "P4". <LI>Whitespace (blanks, TABs, CRs, LFs). @@ -69,7 +69,7 @@ the file toward the end of the file. in the image are square and contiguous. <li>Before the whitespace character that delimits the raster, any -characters from a "#" through the next carriage return or +characters from a "#" through the next carriage return or newline character, is a comment and is ignored. Note that this is rather unconventional, because a comment can actually be in the middle of what you might consider a token. Note also that this means if you @@ -79,8 +79,8 @@ comment is not sufficient to delimit the raster. </UL> <p>All characters referred to herein are encoded in ASCII. -"newline" refers to the character known in ASCII as Line -Feed or LF. A "white space" character is space, CR, LF, +"newline" refers to the character known in ASCII as Line +Feed or LF. A "white space" character is space, CR, LF, TAB, VT, or FF (I.e. what the ANSI standard C isspace() function calls white space). @@ -108,7 +108,7 @@ default, but the <a href="index.html#commonoptions">common option</a> <li> There is exactly one image in a file. <li> -The "magic number" is "P1" instead of "P4". +The "magic number" is "P1" instead of "P4". <li> Each pixel in the raster is represented by a byte containing ASCII '1' or '0', representing black and white respectively. There are no fill bits at the @@ -158,7 +158,7 @@ also applies. <h2 id="filename">FILE NAME</h2> <p>There are no requirements on the name of a PBM file, but the convention is -to use the suffix ".pbm". "pnm" is also conventional, for +to use the suffix ".pbm". "pnm" is also conventional, for cases where distinguishing between the particular subformats of PNM is not convenient. diff --git a/pbmclean.html b/pbmclean.html index 35efa4e3..af370172 100644 --- a/pbmclean.html +++ b/pbmclean.html @@ -31,10 +31,10 @@ from its value with white space instead of an equals sign. PBM image as input and outputs a PBM that is the same as the input except with isolated pixels inverted. -<P>You can use <B>pbmclean </B> to clean up "snow" on bitmap +<P>You can use <B>pbmclean </B> to clean up "snow" on bitmap images. -<p>There are two ways <b>pbmclean</b> can define "isolated" pixels: +<p>There are two ways <b>pbmclean</b> can define "isolated" pixels: simple and extended. When you specify <b>-extended</b>, <b>pbmclean</b> uses extended; otherwise it uses basic. @@ -136,7 +136,7 @@ Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting -documentation. This software is provided "as is" without express or +documentation. This software is provided "as is" without express or implied warranty. <HR> diff --git a/pbmmask.html b/pbmmask.html index 716a1ee0..a8337104 100644 --- a/pbmmask.html +++ b/pbmmask.html @@ -26,7 +26,7 @@ pbmmask - create a mask bitmap from a regular bitmap <p><b>pbmmask</b> reads a PBM image as input and Generates a corresponding mask of the foreground areas as another PBM image. -<P>The color to be interpreted as "background" is +<P>The color to be interpreted as "background" is determined automatically. Regardless of which color is background, the mask will be white where the background is and black where the figure is. diff --git a/pbmpage.html b/pbmpage.html index c9f2d6b3..5e4e2918 100644 --- a/pbmpage.html +++ b/pbmpage.html @@ -56,14 +56,14 @@ is at the very edges of the paper. <DT><B>2</B> <DD> -A vertical line segment, one pixel wide, extending 1/2" up from the +A vertical line segment, one pixel wide, extending 1/2" up from the exact center of the page. <DT><B>3</B> <DD> Two diagonal line segments, one starting at the upper left corner of the page, the other starting from the lower left corner of the page. Both -extend 1/2" toward the center of the page at 45 degrees. +extend 1/2" toward the center of the page at 45 degrees. </DL> <H2 id="options">OPTIONS</H2> @@ -72,8 +72,8 @@ extend 1/2" toward the center of the page at 45 degrees. <DT><B>-a4</B> <DD>Generate an image for A4 (European) paper. Without this option, -<B>pbmpage</B> generates an image for US standard paper (8 1/2" -wide x 11" high). +<B>pbmpage</B> generates an image for US standard paper (8 1/2" +wide x 11" high). </DL> diff --git a/pbmpscale.html b/pbmpscale.html index d216156c..128071ff 100644 --- a/pbmpscale.html +++ b/pbmpscale.html @@ -44,7 +44,7 @@ Copyright (C) 1989 by Jef Poskanzer. documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting -documentation. This software is provided "as is" without express or +documentation. This software is provided "as is" without express or implied warranty. <H2 id="notes">NOTES</H2> diff --git a/pbmreduce.html b/pbmreduce.html index 2de25a78..fcfdffe5 100644 --- a/pbmreduce.html +++ b/pbmreduce.html @@ -30,7 +30,7 @@ factor of <I>N</I>, producing a PBM image as output. <b>pamditherbw</b>; you could do something like <tt>pamscale | pamditherbw</tt>, but <b>pbmreduce</b> is a lot faster. -<P>You can use <B>pbmreduce</B> to "re-halftone" an image. +<P>You can use <B>pbmreduce</B> to "re-halftone" an image. Let's say you have a scanner that only produces black&white, not grayscale, and it does a terrible job of halftoning (most b&w scanners fit this description). One way to fix the halftoning is to diff --git a/pbmtext.html b/pbmtext.html index 39f5a8a0..fc446100 100644 --- a/pbmtext.html +++ b/pbmtext.html @@ -56,7 +56,7 @@ one line of text, whereas <b>pbmtext</b> can create multiple lines. <p><b>pbmtext</b> is meant for small quantities of simple text. If you're working with a <em>document</em>, you would be better off using a document -formatting program to "print" to a Postscript file, then +formatting program to "print" to a Postscript file, then feeding that Postscript to <b>pstopnm</b>. <H2 id="options">OPTIONS</H2> @@ -74,12 +74,12 @@ feeding that Postscript to <b>pstopnm</b>. Window System <a href="http://xfree86.org/current/bdf.pdf">BDF (Bitmap Distribution Format)</a> file or as a PBM file in a special form. -<p>The default is the built in font "bdf." +<p>The default is the built in font "bdf." -<p>"bdf" is Times-Roman 15 pixels high. (That's about 14 +<p>"bdf" is Times-Roman 15 pixels high. (That's about 14 point type printed at 75 dpi). -<p>"fixed" is a built in fixed width font. +<p>"fixed" is a built in fixed width font. <p>For information about other fonts, and how to make one of your own, see <a href="#fonts">Fonts</a> below. @@ -211,9 +211,9 @@ e.g. in an X11 window. <PRE> - M ",/^_[`jpqy| M + M ",/^_[`jpqy| M - / !"#$%&'()*+ / + / !"#$%&'()*+ / < ,-./01234567 < > 89:;<=>?@ABC > @ DEFGHIJKLMNO @ @@ -222,7 +222,7 @@ e.g. in an X11 window. } hijklmnopqrs } ~ tuvwxyz{|}~ ~ - M ",/^_[`jpqy| M + M ",/^_[`jpqy| M </PRE> @@ -245,8 +245,8 @@ message telling you that the number of lines in the font isn't divisible by 11, or it can't find the blank band around the inner rectangle. Sometimes the symptom is that one of the characters displays with a piece of the character that is next to it in the -matrix. For example, "l" might display with a little piece -of the "m" attached on its right. +matrix. For example, "l" might display with a little piece +of the "m" attached on its right. <p>Do a screen grab or window dump of that text, using for instance <B>xwd</B>, <B>xgrabsc</B>, or <B>screendump</B>. Convert the result @@ -287,7 +287,7 @@ any other multi-byte format. <pre> <tt> $ awk 'BEGIN { for (i=0x01; i<=0xFF; i++) - { printf("%c%s",i,i%16==15 ? "\n":""); } }' |\ + { printf("%c%s",i,i%16==15 ? "\n":""); } }' |\ pbmtext -f font.bdf > dump.pbm </tt> </pre> @@ -306,24 +306,24 @@ line and the next line, which should be CHARSET_ENCODING: <pre> <tt> $ grep -A1 CHARSET_REGISTRY font-a.bdf - CHARSET_REGISTRY "ISO8859" - CHARSET_ENCODING "1" + CHARSET_REGISTRY "ISO8859" + CHARSET_ENCODING "1" $ grep -A1 CHARSET_REGISTRY font-b.bdf - CHARSET_REGISTRY "ISO10646" - CHARSET_ENCODING "1" + CHARSET_REGISTRY "ISO10646" + CHARSET_ENCODING "1" </tt> </pre> <p>The latter is Unicode. BDF files coded in ISO 16046-1 usually work for Western European languages, because ISO 16046-1 expands ISO 8859-1 (also -called "Latin-1") while maintaining the first 256 code points. ISO +called "Latin-1") while maintaining the first 256 code points. ISO 8859-1 itself is a superset of ASCII. Run the above command and verify the necessary glyphs are present. <p>It may sound strange that <b>pbmtext</b> accepts font files encoded in Unicode but not input text in Unicode. This is because Unicode provides -several "numbering schemes". +several "numbering schemes". <p>When rendering text in character sets other than ISO 8859-1, one often has to produce a BDF file in the given encoding from a master BDF file encoded in @@ -340,7 +340,7 @@ don't, you can download <b>ucs2any.pl</b> from <a href="http://www.cl.cam.ac.uk/~mgk25/ucs-fonts.html">Unicode fonts and tools for X11</a>. This website has much useful information on fonts. -<p>Another converter is <b>trbdf</b>, included in the "trscripts" +<p>Another converter is <b>trbdf</b>, included in the "trscripts" package, available in some GNU/Linux distributions. <p>BDF files encoded in ISO 8859-2, ISO 8859-7, koi8-r, etc. are available diff --git a/pbmtoepson.html b/pbmtoepson.html index f823c419..6895d334 100644 --- a/pbmtoepson.html +++ b/pbmtoepson.html @@ -76,8 +76,8 @@ print density for you consistent with your other options. <dt><b>-adjacent</b> <dt><b>-nonadjacent</b> -<dd>These options determine whether the output uses "adjacent dot -printing" or not, whatever that is. +<dd>These options determine whether the output uses "adjacent dot +printing" or not, whatever that is. <p>If you don't specify this, <b>pbmtoepson</b> selects adjacent dot printing unless that is incompatible with your other options. diff --git a/pbmtolj.html b/pbmtolj.html index 95b2959c..4fa85595 100644 --- a/pbmtolj.html +++ b/pbmtolj.html @@ -84,7 +84,7 @@ and end of the output file. <DT><B>-copies</B> <DD>Specifies the number of copies. The default is 1. This option -controls the "number of copies" printer control; +controls the "number of copies" printer control; <B>pbmtolj</B> generates only one copy of the image. </DL> diff --git a/pbmtoln03.html b/pbmtoln03.html index 99f0ff61..d5e07d4b 100644 --- a/pbmtoln03.html +++ b/pbmtoln03.html @@ -31,23 +31,23 @@ LN03+ Sixel output file. <DL COMPACT> <DT><B>-l nn</B> -<DD>Use "nn" as value for left margin (default 0). +<DD>Use "nn" as value for left margin (default 0). <DT><B>-r nn</B> -<DD>Use "nn" as value for right margin (default 2400). +<DD>Use "nn" as value for right margin (default 2400). <DT><B>-t nn</B> -<DD>Use "nn" as value for top margin (default 0). +<DD>Use "nn" as value for top margin (default 0). <DT><B>-b nn</B> -<DD>Use "nn" as value for bottom margin (default 3400). +<DD>Use "nn" as value for bottom margin (default 3400). <DT><B>-f nn</B> -<DD>Use "nn" as value for form length (default 3400). +<DD>Use "nn" as value for form length (default 3400). </DL> diff --git a/pbmtomacp.html b/pbmtomacp.html index 386d5f2d..a685fde8 100644 --- a/pbmtomacp.html +++ b/pbmtomacp.html @@ -93,9 +93,9 @@ more flexibly by processing the input through <b>pamcut</b>. <p><b>pbmtomacp</b> was added to Netpbm in 1988, written by Douwe van der Schaaf (...!mcvax!uvapsy!vdschaaf). -<p>In 2015, Akira Urushibata ("Douso") replaced the program with +<p>In 2015, Akira Urushibata ("Douso") replaced the program with the current version, using different logic and none of the original code. -The new version used the "packed PBM" facilities of the Netpbm +The new version used the "packed PBM" facilities of the Netpbm library and the shhopt method of command line parsing. <HR> diff --git a/pbmtomda.html b/pbmtomda.html index f016bdec..0b2c6c51 100644 --- a/pbmtomda.html +++ b/pbmtomda.html @@ -48,7 +48,7 @@ Invert the colors used. <DT><B>--</B> <DD> -End of options (use this if the filename starts with "-") +End of options (use this if the filename starts with "-") </DL> <A NAME="lbAF"> </A> diff --git a/pbmtopgm.html b/pbmtopgm.html index 487c3348..d499ea9e 100644 --- a/pbmtopgm.html +++ b/pbmtopgm.html @@ -67,7 +67,7 @@ dithering. See <b>pamditherbw</b>. its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in -supporting documentation. This software is provided "as is" +supporting documentation. This software is provided "as is" without express or implied warranty. <HR> diff --git a/pbmtopk.html b/pbmtopk.html index 744ffd1c..ccd3e9da 100644 --- a/pbmtopk.html +++ b/pbmtopk.html @@ -41,7 +41,7 @@ pbmtopk - convert a PBM image into a packed (PK) format font <p><b>pbmtopk</b> reads PBM images as input and produces a packed (PK) font file and a TFM (TeX font metric) file as output. The resolution parameter indicates the resolution of the font, in dots per inch. If -the filename "-" is used for any of the filenames, +the filename "-" is used for any of the filenames, <b>pbmtopk</b> uses Standard Input or Standard Output. <A NAME="lbAE"> </A> @@ -82,12 +82,12 @@ Sets the font family comment in the TFM file. <P>The PBM files specified by the filename parameters are inserted consecutively in the font with the specified attributes. If any of the -attributes are omitted, or replaced with "*", a default +attributes are omitted, or replaced with "*", a default value will be calculated from the size of the bitmap. The settings of the -W, -H, -D, -I, -h, -v, -x, and -y options do not affected characters created in this way. The character number can be changed -by including a line starting with "=", followed by the new -number. Lines beginning with "%" or "#" are +by including a line starting with "=", followed by the new +number. Lines beginning with "%" or "#" are ignored. <DT><B>-c</B> <I>num</I> diff --git a/pbmtoppa.html b/pbmtoppa.html index 69f9b40c..c4ec7d92 100644 --- a/pbmtoppa.html +++ b/pbmtoppa.html @@ -21,7 +21,7 @@ pbmtoppa - convert PBM image to HP Printer Performance Architecture (PPA) <B>pbmtoppa</B> converts page images in PBM format to Hewlett Packard's PPA (Printer Performance Architecture) format, which is the -data stream format expected by some HP "Windows-only" +data stream format expected by some HP "Windows-only" printers including the HP Deskjet 820C series, the HP DeskJet 720 series, and the HP DeskJet 1000 series. @@ -60,8 +60,8 @@ calibration </a> below. <p>The PPA printer language is a far lower level language than most. When you use a PPA printer, most of the processing that a conventional printer does is done instead on the computer end of the wire. In -particular, <b>pbmtoppa</b> has to do "swath cutting," and -"sweep formatting," which other printers do themselves. +particular, <b>pbmtoppa</b> has to do "swath cutting," and +"sweep formatting," which other printers do themselves. There is very little intelligence inside a PPA printer; <b>pbmtoppa</b> generates direct controls for the printer's hardware. @@ -235,7 +235,7 @@ Also, use the pbmraw GSDriver if you have it; it's faster. <P>Install pbmtoppa. Copy pbmtoppa to /usr/bin. -<P>Edit "printerdb" (in my system it is found in +<P>Edit "printerdb" (in my system it is found in /usr/lib/rhs/rhs-printfilters ) and append the following lines: <PRE> @@ -251,8 +251,8 @@ StartEntry: DeskJet720C inkjet printer. \ It does not support color printing. \ IMPORTANT! Insert \ - "- | pbm2ppa -" \ - in the "Extra GS Options " field.\ + "- | pbm2ppa -" \ + in the "Extra GS Options " field.\ } Resolution: {600} {600} {} diff --git a/pbmtoybm.html b/pbmtoybm.html index 7857a020..1d906a57 100644 --- a/pbmtoybm.html +++ b/pbmtoybm.html @@ -9,7 +9,7 @@ Updated: 06 March 1990 <A NAME="lbAB"> </A> <H2>NAME</H2> -pgmtoybm - convert a PBM image into a Bennet Yee "face" file +pgmtoybm - convert a PBM image into a Bennet Yee "face" file <A NAME="lbAC"> </A> <H2>SYNOPSIS</H2> diff --git a/pbmupc.html b/pbmupc.html index 0f7f571d..41801ca3 100644 --- a/pbmupc.html +++ b/pbmupc.html @@ -23,7 +23,7 @@ pbmupc - create a Universal Product Code PBM image <p><b>pbmupc</b> generates an image of a Universal Product Code symbol. The three arguments are: a one digit product type, a five digit manufacturer code, and a five digit product code. -For example, "0 72890 00011" is the code for Heineken. +For example, "0 72890 00011" is the code for Heineken. <P><b>pbmupc</b> produces an image 230 bits wide and 175 bits high. If you want a different size run the output through <B>pamscale</B>. diff --git a/pcxtoppm.html b/pcxtoppm.html index 4b629151..de6e4474 100644 --- a/pcxtoppm.html +++ b/pcxtoppm.html @@ -32,10 +32,10 @@ as output. <UL COMPACT> <LI>Colormapped files with 2-16 colors. -<P>"Packed pixel" format (1, 2 or 4 bits/pixel, 1 plane) or +<P>"Packed pixel" format (1, 2 or 4 bits/pixel, 1 plane) or bitplane format (1 bit/pixel, 1-4 planes). The program uses a predefined standard palette if the image does not provide one. -"Does not provide one" means the palette in the PCX header is +"Does not provide one" means the palette in the PCX header is completely black. <LI>Colormapped files with 256 colors. diff --git a/pfm.html b/pfm.html index 9f3cd8ae..e95dc414 100644 --- a/pfm.html +++ b/pfm.html @@ -20,7 +20,7 @@ the Netpbm converters <a href="pamtopfm.html"><b>pamtopfm</b></a> and <p>There are multiple similar formats known as PFM in the world, none of them authoritatively documented. The format described here is one that Bryan Henderson deduced from a program he found somewhere that -dealt with a "PFM" format. +dealt with a "PFM" format. <p>The PFM format is inspired by the Netpbm formats, and you will see lots of similarity. It is not, however, an official Netpbm format. @@ -35,17 +35,17 @@ described. <h3>PFM header</h3> -<p>The PFM header is 3 consecutive "lines" of ASCII text. +<p>The PFM header is 3 consecutive "lines" of ASCII text. After each line is a white space character. That character is -typically a newline character, hence the term "line," but +typically a newline character, hence the term "line," but doesn't have to be. <p><b>pamtopfm</b> uses a newline in the PFM it generates. <h4>Identifier Line</h4> -<p>The identifier line contains the characters "PF" or -"Pf". PF means it's a color PFM. Pf means it's a grayscale +<p>The identifier line contains the characters "PF" or +"Pf". PF means it's a color PFM. Pf means it's a grayscale PFM. <h4>Dimensions Line</h4> diff --git a/pfmtopam.html b/pfmtopam.html index e8dc53f1..5c6f09fc 100644 --- a/pfmtopam.html +++ b/pfmtopam.html @@ -32,8 +32,8 @@ PFM. <p>If you want one of the older, more portable Netpbm formats, run the output through <b>pamtopnm</b>. -<b>pamtopfm</b> creates a PAM with tuple type "RGB" or -"GRAYSCALE" depending on whether or not the PFM is in the color +<b>pamtopfm</b> creates a PAM with tuple type "RGB" or +"GRAYSCALE" depending on whether or not the PFM is in the color subformat. <p>Use <a href="pamtopfm.html"><b>pamtopfm</b></a> to convert a PFM diff --git a/pgm.html b/pgm.html index 81ecb9fe..fb016389 100644 --- a/pgm.html +++ b/pgm.html @@ -49,8 +49,8 @@ no data, delimiters, or padding before, after, or between images. <OL> -<LI>A "magic number" for identifying the file type. -A pgm image's magic number is the two characters "P5". +<LI>A "magic number" for identifying the file type. +A pgm image's magic number is the two characters "P5". <LI>Whitespace (blanks, TABs, CRs, LFs). @@ -86,7 +86,7 @@ most intense value in the image and any other image to which the image might be compared. <p>Note that a common variation on the PGM format is to have the -gray value be "linear," i.e. as specified above except +gray value be "linear," i.e. as specified above except without the gamma adjustment. <B>pnmgamma</B> takes such a PGM variant as input and produces a true PGM as output. @@ -95,14 +95,14 @@ opaqueness. It is proportional to the fraction of intensity of a pixel that would show in place of an underlying pixel. So what normally means white represents total opaqueness and what normally means black represents total transparency. In between, you would -compute the intensity of a composite pixel of an "under" and -"over" pixel as under * (1-(alpha/alpha_maxval)) + over * +compute the intensity of a composite pixel of an "under" and +"over" pixel as under * (1-(alpha/alpha_maxval)) + over * (alpha/alpha_maxval). Note that there is no gamma transfer function in the transparency mask. </OL> -<p>Strings starting with "#" may be comments, the same as +<p>Strings starting with "#" may be comments, the same as with <a href="pbm.html">PBM</a>. <P>Note that you can use <B>pamdepth</B> to convert between a the @@ -110,16 +110,16 @@ format with 1 byte per gray value and the one with 2 bytes per gray value. <p>All characters referred to herein are encoded in ASCII. -"newline" refers to the character known in ASCII as Line -Feed or LF. A "white space" character is space, CR, LF, +"newline" refers to the character known in ASCII as Line +Feed or LF. A "white space" character is space, CR, LF, TAB, VT, or FF (I.e. what the ANSI standard C isspace() function calls white space). <h3 id="plainpgm">Plain PGM</h3> <P>There is actually another version of the PGM format that is fairly -rare: "plain" PGM format. The format above, which generally -considered the normal one, is known as the "raw" PGM format. +rare: "plain" PGM format. The format above, which generally +considered the normal one, is known as the "raw" PGM format. See <B><A HREF="pbm.html">pbm</A></B> for some commentary on how plain and raw formats relate to one another and how to use them. @@ -176,7 +176,7 @@ also applies. <h2 id="filename">FILE NAME</h2> <p>There are no requirements on the name of a PGM file, but the convention is -to use the suffix ".pgm". "pnm" is also conventional, for +to use the suffix ".pgm". "pnm" is also conventional, for cases where distinguishing between the particular subformats of PNM is not convenient. diff --git a/pgmbentley.html b/pgmbentley.html index e3d64e8e..c4d35df8 100644 --- a/pgmbentley.html +++ b/pgmbentley.html @@ -21,7 +21,7 @@ pgmbentley - Bentleyize a PGM image <p><b>pgmbentley</b> reads a PGM image as input and performs the Bentley Effect, and writes a PGM image as output. -<p>The Bentley Effect is described in "Beyond Photography" +<p>The Bentley Effect is described in "Beyond Photography" by Holzmann, chapter 4, photo 4. It's a vertical smearing based on brightness. diff --git a/pgmdeshadow.html b/pgmdeshadow.html index a6dafe01..acde9010 100644 --- a/pgmdeshadow.html +++ b/pgmdeshadow.html @@ -31,7 +31,7 @@ image. The program uses a simple image reconstruction algorithm to determine the local shadow gray level, then divides each pixel's gray level by the local shadow gray level. -<p>The algorithm is the "fast hybrid grayscale reruction" +<p>The algorithm is the "fast hybrid grayscale reruction" algorithm from Luc Vincent, "Morphological Grayscale Reruction in Image Analysis: Applications and Efficient Algorithms. @@ -44,8 +44,8 @@ Image Analysis: Applications and Efficient Algorithms. <ul> -<li>Luc Vincent, "Morphological Grayscale Reconstruction in Image -Analysis: Applications and Efficient Algorithms," IEEE +<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 --git a/pgmenhance.html b/pgmenhance.html index 3d9eb98e..d1d4a278 100644 --- a/pgmenhance.html +++ b/pgmenhance.html @@ -29,8 +29,8 @@ pgmenhance - edge-enhance a PGM image and writes a PGM image as output. <P>The edge enhancing technique is taken from Philip R. Thompson's -"xim" program, which in turn took it from section 6 of -"Digital Halftones by Dot Diffusion", D. E. Knuth, ACM +"xim" program, which in turn took it from section 6 of +"Digital Halftones by Dot Diffusion", D. E. Knuth, ACM Transaction on Graphics Vol. 6, No. 4, October 1987, which in turn got it from two 1976 papers by J. F. Jarvis et. al. diff --git a/pgmmedian.html b/pgmmedian.html index bbdf9d49..9e38c112 100644 --- a/pgmmedian.html +++ b/pgmmedian.html @@ -92,14 +92,14 @@ under the <b>-cutoff</b> option. <ul> -<li>"Collected Algorithms from ACM" Volume II, Algorithm 489 +<li>"Collected Algorithms from ACM" Volume II, Algorithm 489 by Robert W. Floyd -<li>"A Fast Two-Dimensional Median Filtering Algorithm" in -"IEEE Transactions on Acoustics, Speech, and Signal -Processing" Vol. ASSP-27, No. 1, February 1979 +<li>"A Fast Two-Dimensional Median Filtering Algorithm" in +"IEEE Transactions on Acoustics, Speech, and Signal +Processing" Vol. ASSP-27, No. 1, February 1979 -<li>"Digital Image Processing Algorithms" by Ioannis +<li>"Digital Image Processing Algorithms" by Ioannis Pitas, Prentice Hall, 1993 ISBN 0-13-145814-0 </ul> diff --git a/pgmtoppm.html b/pgmtoppm.html index 40c64ec5..01925ad3 100644 --- a/pgmtoppm.html +++ b/pgmtoppm.html @@ -61,7 +61,7 @@ file that explicitly associates a color with each possible gray level. <H2 id="maxval">NOTE - MAXVAL</H2> -<P>When you don't use <b>-map</b>, the "maxval," or depth, +<P>When you don't use <b>-map</b>, the "maxval," or depth, of the output image is the same as that of the input image. The maxval affects the color resolution, which may cause quantization errors you don't anticipate in your output. For example, you have a diff --git a/pgmtosbig.html b/pgmtosbig.html index 651f9962..faed1494 100644 --- a/pgmtosbig.html +++ b/pgmtosbig.html @@ -27,7 +27,7 @@ Santa Barbara Instrument Group SBIG Type 3 image as output. <ul> <li>The image is uncompressed -<li>The image says it is from a "ST-6" camera +<li>The image says it is from a "ST-6" camera <li>The image header has these lines: <ul> <li>camera type diff --git a/pgmtost4.html b/pgmtost4.html index ee2f33be..538b3be6 100644 --- a/pgmtost4.html +++ b/pgmtost4.html @@ -28,7 +28,7 @@ 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 says it is from a "ST-6" camera <li>The image header has these lines: <ul> <li>camera type diff --git a/picttoppm.html b/picttoppm.html index de38f7c0..380e9fa7 100644 --- a/picttoppm.html +++ b/picttoppm.html @@ -38,7 +38,7 @@ image. <p>PICT is an image format that was developed by Apple Computer in 1984 as the native format for Macintosh graphics. A PICT image is encoded in QuickDraw commands. The PICT format is a meta-format that can be used for both bitmap -images and vector images. PICT is also known as "Macintosh Picture" +images and vector images. PICT is also known as "Macintosh Picture" format, or the QuickDraw Picture format. <p>PICT files are primarily used to exchange graphics between various diff --git a/pktopbm.html b/pktopbm.html index 709e27af..b7be08f2 100644 --- a/pktopbm.html +++ b/pktopbm.html @@ -22,7 +22,7 @@ pktopbm pkfile[.pk] [ -x width ] [ -y height ] [-c num] pbmfile ... <p>This program is part of <a href="index.html">Netpbm</a>. <p><b>pktopbm</b> reads a packed (PK) font file as input, and produces -PBM images as output. If the filename "-" is used for any of +PBM images as output. If the filename "-" is used for any of the filenames, the standard input stream (or standard output where appropriate) will be used. If either the width or height is specified, this value will be used for all bitmaps produced. Also if one or both diff --git a/pngtopam.html b/pngtopam.html index e960f33a..86f85b9d 100644 --- a/pngtopam.html +++ b/pngtopam.html @@ -155,7 +155,7 @@ not the actual image gamma; it is much more likely to be .45. <p>Because the gammas of uncompensated monitors are around 2.6, which results in an image-gamma of 0.45, some typical situations are: when the image-gamma is 0.45 (use -verbose to check) and the picture is too -light, your system is gamma-corrected, so convert with "-gamma 1.0". +light, your system is gamma-corrected, so convert with "-gamma 1.0". When no gAMA chunk is present or the image-gamma is 1.0, use 2.2 to make the picture lighter and 0.45 to make the picture darker. diff --git a/pnm.html b/pnm.html index 8c263c4f..90952b2e 100644 --- a/pnm.html +++ b/pnm.html @@ -18,14 +18,14 @@ pnm - Netpbm superformat <H2 id="description">DESCRIPTION</H2> <P>The PNM format is just an abstraction of the PBM, PGM, and PPM -formats. I.e. the name "PNM" refers collectively to +formats. I.e. the name "PNM" refers collectively to PBM, PGM, and PPM. -<P>The name "PNM" is an acronym derived from "Portable -Any Map." This derivation makes more sense if you consider +<P>The name "PNM" is an acronym derived from "Portable +Any Map." This derivation makes more sense if you consider it in the context of the other Netpbm format names: PBM, PGM, and PPM. -<P>The more general term "Netpbm format" refers to the PNM +<P>The more general term "Netpbm format" refers to the PNM formats plus PAM. <p>PNM is principally used with <a href="index.html">Netpbm</a>. @@ -39,7 +39,7 @@ respond to each differently whereas a PPM program sees everything as if it were PPM. This is discussed more in <a href="index.html">the description of the netpbm programs</a>. -<P>"pnm" also appears in the names of the most general <a +<P>"pnm" also appears in the names of the most general <a href="libnetpbm.html">Netpbm library routines</a>, some of which aren't even related to the PNM format. @@ -56,8 +56,8 @@ PNM code when it is convenient to do so. <h2 id="filename">FILE NAME</h2> <p>There are no requirements on the name of a PNM file, but the convention is -to use the suffix "pbm", "pgm", or "ppm", -depending on the particular subformat, or "pnm" if it is not +to use the suffix "pbm", "pgm", or "ppm", +depending on the particular subformat, or "pnm" if it is not convenient to distinguish the subformats. diff --git a/pnmalias.html b/pnmalias.html index e8e0528e..7fa9f297 100644 --- a/pnmalias.html +++ b/pnmalias.html @@ -77,7 +77,7 @@ background and foreground pixels. <P><B>-weight</B> <I>w</I> says to use <I>w</I> as the central weight for the aliasing filter. <I>w</I> must be a real number in the range 0 < <I>w</I> < 1. The lower the value of <I>w</I> is, the -"blurrier" the output image is. The default is w = 1/3. +"blurrier" the output image is. The default is w = 1/3. <H2 id="seealso">SEE ALSO</H2> diff --git a/pnmcat.html b/pnmcat.html index d2a3fed2..93819211 100644 --- a/pnmcat.html +++ b/pnmcat.html @@ -38,7 +38,7 @@ either left to right or top to bottom, and produces a single PNM image as output. <p>The arguments are names of input files. Any one of these, but not more -than one, may be "-" to indicate Standard Input. If you have no +than one, may be "-" to indicate Standard Input. If you have no arguments, that means a single input image from Standard Input (and that is pointless - the output is the same as the input). diff --git a/pnmcolormap.html b/pnmcolormap.html index ea44d50e..917a984d 100644 --- a/pnmcolormap.html +++ b/pnmcolormap.html @@ -48,7 +48,7 @@ least one pixel of each color in the set of colors it represents. The ones <b>pnmcolormap</b> generates have exactly one pixel of each color, except where padding is necessary with the <b>-square</b> option. -<P>The quantization method is Heckbert's "median cut". +<P>The quantization method is Heckbert's "median cut". See <a href="#quant">QUANTIZATION METHOD</a>. <P>The output image is of the same format (PBM, PGM, PPM, PAM) as the @@ -127,21 +127,21 @@ href="#quant">QUANTIZATION METHOD</a>. <P>A quantization method is a way to choose which colors, being fewer in number than in the input, you want in the output. -<B>pnmcolormap</B> uses Heckbert's "median cut" quantization +<B>pnmcolormap</B> uses Heckbert's "median cut" quantization method. <P>This method involves separating all the colors into -"boxes," each holding colors that represent about the same +"boxes," each holding colors that represent about the same number of pixels. You start with one box and split boxes in two until the number of boxes is the same as the number of colors you want in the output, and choose one color to represent each box. <P>When you split a box, you do it so that all the colors in one -sub-box are "greater" than all the colors in the other. -"Greater," for a particular box, means it is brighter in the +sub-box are "greater" than all the colors in the other. +"Greater," for a particular box, means it is brighter in the color component (red, green, blue) which has the largest spread in that box. <B>pnmcolormap</B> gives you two ways to define -"largest spread.": 1) largest spread of brightness; 2) +"largest spread.": 1) largest spread of brightness; 2) largest spread of contribution to the luminosity of the color. E.g. red is weighted much more than blue. Select among these with the <B>-spreadbrightness</B> and <B>-spreadluminosity</B> options. The @@ -150,7 +150,7 @@ default is <B>-spreadbrightness</B>. <P><B>pnmcolormap</B> provides three ways of choosing a color to represent a box: 1) the center color - the color halfway between the greatest and least colors in the box, using the above definition of -"greater"; 2) the mean of the colors (each component +"greater"; 2) the mean of the colors (each component averaged separately by brightness) in the box; 3) the mean weighted by the number of pixels of a color in the image. @@ -162,7 +162,7 @@ which do not appear in the input at all. <H2 id="references">REFERENCES</H2> -"Color Image Quantization for Frame Buffer Display" by Paul Heckbert, +"Color Image Quantization for Frame Buffer Display" by Paul Heckbert, SIGGRAPH '82 Proceedings, page 297. <H2 id="seealso">SEE ALSO</H2> diff --git a/pnmconvol.html b/pnmconvol.html index 633bb4b5..6efdc197 100644 --- a/pnmconvol.html +++ b/pnmconvol.html @@ -137,7 +137,7 @@ and is the weight to give to each component of a pixel that corresponds to that matrix location. <p>Note that when you supply this option via a shell, semicolon -(";") probably means something to the shell, so use quotation +(";") probably means something to the shell, so use quotation marks. <p>There is no way with this method to have different weights for different diff --git a/pnmgamma.html b/pnmgamma.html index 4c884f5f..fce97752 100644 --- a/pnmgamma.html +++ b/pnmgamma.html @@ -56,14 +56,14 @@ modified with a linear ramp near black. where the sample values represent intensity in different ways: <p>In one common variation, the sample value is directly proportional -to radiance (often called "linear intensity"). +to radiance (often called "linear intensity"). <p>Another popular variation is to make the samples proportional to luminance as defined by the International Electrotechnical Commission (IEC) SRGB standard. The SRGB gamma transfer function is like the BT.709 one except with different constants in it. -<P>Note that SRGB is often spelled "sRGB". In this +<P>Note that SRGB is often spelled "sRGB". In this document, we use standard English typography, though, which doesn't allow for that kind of capitalization. @@ -204,7 +204,7 @@ function (which is not a standard), the default is 2.2. <p>In the <b>-bt709tosrgb</b> and <b>-srgbtobt709</b> conversions there are <em>two</em> exponents. <b>-gamma</b> affects the -"to" function; the "from" function always uses the +"to" function; the "from" function always uses the standard gamma value. <p>If you specify one of the component-specific options (<b>-rgamma</b>, diff --git a/pnmhisteq.html b/pnmhisteq.html index 2e7ccfd0..463f81b0 100644 --- a/pnmhisteq.html +++ b/pnmhisteq.html @@ -33,7 +33,7 @@ pnmhisteq - histogram equalize a PNM image <p>This program is part of <a href="index.html">Netpbm</a>. <p><B>pnmhisteq</B> increases the contrast of a PGM or PPM image -through the technique of "histogram equalization."[1] +through the technique of "histogram equalization."[1] <p><b>pnmhisteq</b> computes a histogram of the luminosity of the pixels in the image. It then calculates a mapping between each diff --git a/pnmhistmap.html b/pnmhistmap.html index b79cecf9..497870c2 100644 --- a/pnmhistmap.html +++ b/pnmhistmap.html @@ -103,7 +103,7 @@ to the maxval. <p>The default width is one pixel for each plotted intensity value (so it's controlled by the maxval of the image and the <b>-lval</b> and <b>-rval</b> -options). The "count buckets" in the histogram are always +options). The "count buckets" in the histogram are always one pixel wide. If you specify a width less than the number of plotted intensity values, a bucket represents more than one intensity value. If you specify a width greater that the number of plotted intensity values, diff --git a/pnmindex.html b/pnmindex.html index b0b1d53a..ba0c3b6f 100644 --- a/pnmindex.html +++ b/pnmindex.html @@ -39,7 +39,7 @@ with white space instead of an equals sign. <B>pnmindex</B> creates an index image containing thumbnail (small) versions of a bunch of PNM files you supply. (Akin to a photographic -"contact sheet." +"contact sheet." <P><B>pnmindex</B> labels each thumbnail and, optionally, contains a title. diff --git a/pnmnlfilt.html b/pnmnlfilt.html index e0cd124a..e2cf5aee 100644 --- a/pnmnlfilt.html +++ b/pnmnlfilt.html @@ -40,7 +40,7 @@ subject pixel (ie. there will be no filtering effect). A radius value of 1.0 means that the 7 hexagons essentially cover the 3x3 immediate neighbor square. -<p>Your choice of "alpha" parameter selects among the three +<p>Your choice of "alpha" parameter selects among the three modes. <H3 id="alphatrimmedmean"> @@ -51,17 +51,17 @@ the 7 hexagon values, but the 7 values are sorted by size and the top and bottom alpha portion of the 7 are excluded from the mean. This implies that an alpha value of 0.0 gives the same sort of output as a normal convolution (ie. averaging or smoothing filter), where radius -will determine the "strength" of the filter. A good value to +will determine the "strength" of the filter. A good value to start from for subtle filtering is alpha = 0.0, radius = 0.55 For a more blatant effect, try alpha 0.0 and radius 1.0 <P>An alpha value of 0.5 will cause the median value of the 7 hexagons to be used to replace the center pixel value. This sort of filter is -good for eliminating "pop" or single pixel noise from an +good for eliminating "pop" or single pixel noise from an image without spreading the noise out or smudging features on the image. Judicious use of the radius parameter will fine tune the filtering. Intermediate values of alpha give effects somewhere between -smoothing and "pop" noise reduction. For subtle filtering +smoothing and "pop" noise reduction. For subtle filtering try starting with values of alpha = 0.4, radius = 0.6 For a more blatant effect try alpha = 0.5, radius = 1.0 @@ -73,7 +73,7 @@ image. For each pixel the variance of the surrounding hexagon values is calculated, and the amount of smoothing is made inversely proportional to it. The idea is that if the variance is small then it is due to noise in the image, while if the variance is large, it is -because of "wanted" image features. As usual the radius +because of "wanted" image features. As usual the radius parameter controls the effective radius, but it probably advisable to leave the radius between 0.8 and 1.0 for the variance calculation to be meaningful. The alpha parameter sets the noise threshold, over @@ -121,16 +121,16 @@ CG&A May 1990 Page 23 by Mark E. Lee and Richard A. Redner, and has been enhanced to allow continuous alpha adjustment. <P>The optimal estimation filter is taken from an article -"Converting Dithered Images Back to Gray Scale" by Allen +"Converting Dithered Images Back to Gray Scale" by Allen Stenger, Dr Dobb's Journal, November 1992, and this article references -"Digital Image Enhancement and Noise Filtering by Use of Local -Statistics", Jong-Sen Lee, IEEE Transactions on Pattern Analysis +"Digital Image Enhancement and Noise Filtering by Use of Local +Statistics", Jong-Sen Lee, IEEE Transactions on Pattern Analysis and Machine Intelligence, March 1980. <P>The edge enhancement details are from <A HREF="pgmenhance.html">pgmenhance</A>, which is taken from Philip -R. Thompson's "xim" program, which in turn took it from -section 6 of "Digital Halftones by Dot Diffusion", +R. Thompson's "xim" program, which in turn took it from +section 6 of "Digital Halftones by Dot Diffusion", D. E. Knuth, ACM Transaction on Graphics Vol. 6, No. 4, October 1987, which in turn got it from two 1976 papers by J. F. Jarvis et. al. diff --git a/pnmnorm.html b/pnmnorm.html index 4bc2114e..b01b3f17 100644 --- a/pnmnorm.html +++ b/pnmnorm.html @@ -70,7 +70,7 @@ approximate the desired brightness. <li>saturation </ol> -In the case of saturation, "brightness" is pretty much a +In the case of saturation, "brightness" is pretty much a misnomer, but you can use the brightness analogy to see what it does. In the analogy, bright means saturated and dark means unsaturated. @@ -245,7 +245,7 @@ what property of the pixels <b>pnmnorm</b> normalizes. I.e., what kind of brightness. You cannot specify more than one of these. <P>The <B>-luminosity</B> option says to use the luminosity (i.e. the -"Y" in the YUV or YCbCr color space) as the pixel's brightness. The +"Y" in the YUV or YCbCr color space) as the pixel's brightness. The luminosity is a measure of how bright a human eye would find the color, taking into account the fact that the human eye is more sensitive to some RGB components than others. @@ -260,7 +260,7 @@ but its meaning was still the default. <P>Before Netpbm 10.28 (August 2005), there was no <B>-colorvalue</B> option. <P>The <B>-colorvalue</B> option says to use the color value (i.e. the -"V" in the HSV color space) as the pixel's brightness. The +"V" in the HSV color space) as the pixel's brightness. The color value is the gamma-adjusted intensity of the most intense RGB component. @@ -269,13 +269,13 @@ component. <P>Before Netpbm 10.28 (August 2005), there was no <B>-colorvalue</B> option. <p>The <b>-saturation</b> option says to use the saturation (i.e. the -"S" in the HSV color space) as the pixel's brightness. The +"S" in the HSV color space) as the pixel's brightness. The saturation is the ratio of the intensity of the most intense RGB component to the difference between the intensities of the most and least intense RGB component (all intensities gamma-adjusted). -<p>In this case, "brightness" is more of a metaphor than anything. -"bright" means saturated and "dark" means unsaturated. +<p>In this case, "brightness" is more of a metaphor than anything. +"bright" means saturated and "dark" means unsaturated. <p>This option is meaningless on grayscale images. diff --git a/pnmpad.html b/pnmpad.html index d92fa5f8..32575fcc 100644 --- a/pnmpad.html +++ b/pnmpad.html @@ -151,7 +151,7 @@ compatibility, but not documented or supported for future use. its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in -supporting documentation. This software is provided "as is" +supporting documentation. This software is provided "as is" without express or implied warranty. <HR> diff --git a/pnmpaste.html b/pnmpaste.html index 7179dfdc..70d80cc2 100644 --- a/pnmpaste.html +++ b/pnmpaste.html @@ -50,7 +50,7 @@ segment you are interested in, edit it, and then paste it back in. <P>Another useful companion tool is <B>pbmmask</B>. <P><B>pamcomp</B> is a more general tool, except that it lacks the -"or," "and," and "xor" functions. +"or," "and," and "xor" functions. <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 @@ -61,12 +61,12 @@ and the base image. <P>The option specifies the operation to use when doing the paste. The default is <B>-replace</B>, which means to do the obvious paste: -replace pixels of the "into" image with those of the -"from" image. +replace pixels of the "into" image with those of the +"from" image. <p><b>-and</b>, <b>-or</b>, and <b>-xor</b> are allowed only if both -input images are PBM images. They say to combine the "from" and -"into" images by performing boolean operations: Each pixel of +input images are PBM images. They say to combine the "from" and +"into" images by performing boolean operations: Each pixel of the output image is the result of the boolean operation on the corresponding pixels of the two input image, where white is TRUE and black is FALSE. diff --git a/pnmpsnr.html b/pnmpsnr.html index 75be0e8e..077a432d 100644 --- a/pnmpsnr.html +++ b/pnmpsnr.html @@ -57,8 +57,8 @@ PSNR of 20 means the mean square difference of the luminances of the pixels is 100 times less than the maximum possible difference, i.e. 0.01. -<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 +<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. diff --git a/pnmremap.html b/pnmremap.html index b0958ca7..502df7cb 100644 --- a/pnmremap.html +++ b/pnmremap.html @@ -88,7 +88,7 @@ typically a single row with one pixel per color. the palette in addition to whatever is in the palette image. <p>For historical reasons, Netpbm sometimes calls the palette a -"colormap." But it doesn't really map anything. +"colormap." But it doesn't really map anything. <b>pnmremap</b> creates its own map, based on the palette, to map colors from the input image to output colors. @@ -144,7 +144,7 @@ pnmremap -map=palette.ppm testimg.ppm >reduced_testimg.ppm <P>To limit colors to a certain set, a typical example is to create an image for posting on the World Wide Web, where different browsers know different colors. But all browsers are supposed to know the 216 -"web safe" colors which are essentially all the colors you +"web safe" colors which are essentially all the colors you can represent in a PPM image with a maxval of 5. So you can do this: <PRE> diff --git a/pnmrotate.html b/pnmrotate.html index 922ec883..04d9aa6e 100644 --- a/pnmrotate.html +++ b/pnmrotate.html @@ -46,7 +46,7 @@ you first use <I>pamflip</I> to do a 90 degree rotation and then <P>The rotation algorithm is Alan Paeth's three-shear method. Each shear is implemented by looping over the source pixels and distributing fractions to each of the destination pixels. This has an -"anti-aliasing" effect - it avoids jagged edges and similar +"anti-aliasing" effect - it avoids jagged edges and similar artifacts. However, it also means that the original colors or gray levels in the image are modified. If you need to keep precisely the same set of colors, you can use the <B>-noantialias</B> option. @@ -108,7 +108,7 @@ in the input, you also must consider the background color. See the <H2 id="references">REFERENCES</H2> -"A Fast Algorithm for General Raster Rotation" by Alan Paeth, +"A Fast Algorithm for General Raster Rotation" by Alan Paeth, Graphics Interface '86, pp. 77-81. <H2 id="seealso">SEE ALSO</H2> diff --git a/pnmshear.html b/pnmshear.html index cc2977a7..d6a95825 100644 --- a/pnmshear.html +++ b/pnmshear.html @@ -53,7 +53,7 @@ image will be unreasonably wide. <P><b>pnmshear</b> does the shearing by looping over the source pixels and distributing fractions to each of the destination pixels. This -has an "anti-aliasing" effect - it avoids jagged edges and +has an "anti-aliasing" effect - it avoids jagged edges and similar artifacts. However, it also means that the original colors in the image are modified and there are typically more of them than you started with. If you need to keep precisely the same set of colors, diff --git a/pnmtofiasco.html b/pnmtofiasco.html index 9f8c63c1..21f5d0c1 100644 --- a/pnmtofiasco.html +++ b/pnmtofiasco.html @@ -128,8 +128,8 @@ following methods (in the specified order): <DD>Preload compression basis <I>name</I> into FIASCO. The basis <I>name</I> provides the initial compression dictionary. Either use -one of the files "small.fco", "medium.fco", or -"large.fco" that come with <B>pnmtofiasco </B> or create a +one of the files "small.fco", "medium.fco", or +"large.fco" that come with <B>pnmtofiasco </B> or create a new ASCII basis file. <DT><B>-z</B> <I>N</I>, <B>--optimize=</B><I>N</I> @@ -248,7 +248,7 @@ HREF="fiascotopnm.html">fiascotopnm</A> to control the framerate. <DD>Defines the type of inter frame compression which should be applied to individual frames of a video stream. <I>type</I> is a -sequence of characters; default is "IPPPPPPPPP". Element +sequence of characters; default is "IPPPPPPPPP". Element <B>N</B> defines the type of predicting which should be used for frame <B>N</B>; the frame type pattern is periodically extended. Valid characters are: @@ -271,7 +271,7 @@ backward or interpolated prediction). <DT><B>--cross-B-search</B> -<DD>Instead of using exhaustive search the "Cross-B-Search" +<DD>Instead of using exhaustive search the "Cross-B-Search" algorithm is used to find the best interpolated prediction of B-frames. @@ -286,21 +286,21 @@ predict the current frame. <H2 id="examples">EXAMPLES</H2> -<p>Compress the still image "foo.ppm" to the FIASCO file -"foo.wfa" using the default options: +<p>Compress the still image "foo.ppm" to the FIASCO file +"foo.wfa" using the default options: <pre> pnmtofiasco < foo.ppm >foo.wfa </pre> -<P>Compress the video frames "foo0*.ppm" to the FIASCO file -"video.wfa" using half pixel precise motion compensation at +<P>Compress the video frames "foo0*.ppm" to the FIASCO file +"video.wfa" using half pixel precise motion compensation at a frame rate of 15 frames per second. Intra frame 1 is used to predict P-frame 4, frames 1 and 4 are used to predict B-frames 2 and 3, and so on. Frame 10 is again an intra-frame. <pre> - pnmtofiasco -2 -p "IBBPBBPBB" -fps 15 -o video.wfa foo0*.ppm + pnmtofiasco -2 -p "IBBPBBPBB" -fps 15 -o video.wfa foo0*.ppm </pre> <H2 id="files">FILES</H2> @@ -323,11 +323,11 @@ predict P-frame 4, frames 1 and 4 are used to predict B-frames 2 and <DT><B>FIASCO_IMAGES</B> -<DD>Search path for image files. Default is "./". +<DD>Search path for image files. Default is "./". <DT><B>FIASCO_DATA</B> -<DD>Search and save path for FIASCO files. Default is "./". +<DD>Search and save path for FIASCO files. Default is "./". </DL> diff --git a/pnmtojpeg.html b/pnmtojpeg.html index 6dd99ef3..07f61ea7 100644 --- a/pnmtojpeg.html +++ b/pnmtojpeg.html @@ -7,7 +7,7 @@ Updated: 23 April 2007 <A HREF="#index">Table Of Contents</A> <H2>NAME</H2> -pnmtojpeg - convert PNM image to a JFIF ("JPEG") image +pnmtojpeg - convert PNM image to a JFIF ("JPEG") image <H2 id="synopsis">SYNOPSIS</H2> @@ -53,8 +53,8 @@ create the output file. See <B><A HREF="http://www.ijg.org">http://www.ijg.org</A> </B> for information on the library. -<P>"JFIF" is the correct name for the image format commonly -known as "JPEG." Strictly speaking, JPEG is a method of +<P>"JFIF" is the correct name for the image format commonly +known as "JPEG." Strictly speaking, JPEG is a method of compression. The image format using JPEG compression that is by far the most common is JFIF. There is also a subformat of TIFF that uses JPEG compression. @@ -227,8 +227,8 @@ some other JFIF programs may be unable to decode the resulting file. Use <B>-baseline</B> if you need to ensure compatibility at low quality values.) -<P>The <B>-progressive</B> option creates a "progressive -JPEG" file. In this type of JFIF file, the data is stored in +<P>The <B>-progressive</B> option creates a "progressive +JPEG" file. In this type of JFIF file, the data is stored in multiple scans of increasing quality. If the file is being transmitted over a slow communications link, the decoder can use the first scan to display a low-quality image very quickly, and can then @@ -282,9 +282,9 @@ JPEG Group since about 1998 are not capable of arithmetic encoding. <b>pnmtojpeg</b> uses a JPEG library (either bound to it when the <b>pnmtojpeg</b> executable was built or accessed on your system at run time) to do the JPEG encoding. If <b>pnmtojpeg</b> terminates -with the message, "Sorry, there are legal restrictions on -arithmetic coding" or "Sorry, arithmetic coding not -supported," this is the problem. +with the message, "Sorry, there are legal restrictions on +arithmetic coding" or "Sorry, arithmetic coding not +supported," this is the problem. <DT><B>-restart=</B><I>n</I> @@ -370,7 +370,7 @@ about the compression process. </DL> -<P>The "wizard" options are intended for experimentation +<P>The "wizard" options are intended for experimentation with JPEG. If you don't know what you are doing, <strong>don't use them</strong>. These switches are documented further in the file wizard.doc that comes with the Independent JPEG Group's JPEG library. @@ -414,7 +414,7 @@ step. And if you can keep a copy in the original format, so much the better. The <B>-optimize</B> option to <B>pnmtojpeg</B> is worth using when -you are making a "final" version for posting or archiving. +you are making a "final" version for posting or archiving. It's also a win when you are using low quality settings to make very small JFIF files; the percentage improvement is often a lot more than it is on larger files. (At present, <B>-optimize</B> mode is @@ -471,26 +471,26 @@ In an entry for AC coefficients, the first number after the colon must not be 0. <P> In a DC entry, the color components must be in increasing order. -E.g. "0,2,1" before the colon is wrong. So is "0,0,0". +E.g. "0,2,1" before the colon is wrong. So is "0,0,0". <P> In an entry for an AC coefficient, you must specify only one color component. I.e. there can be only one number before the colon. <P> In the first entry for a particular coefficient for a particular color -component, the "Ah" value must be zero, but the Al value can be any +component, the "Ah" value must be zero, but the Al value can be any valid bit number. In subsequent entries, Ah must be the Al value from the previous entry (for that coefficient for that color component), and the Al value must be one less than the Ah value. <P> The script must ultimately specify at least some of the DC coefficient for every color component. Otherwise, you get the error message -"Script does not transmit all the data." You need not specify all of +"Script does not transmit all the data." You need not specify all of the bits of the DC coefficient, or any of the AC coefficients. <P> There is a standard option in building the JPEG library to omit scan script capability. If for some reason your library was built with -this option, you get the message "Requested feature was omitted at -compile time." +this option, you get the message "Requested feature was omitted at +compile time." <H2 id="environment">ENVIRONMENT</H2> @@ -514,8 +514,8 @@ overrides any <B>JPEGMEM</B>. <B>rdjpgcom</B> man page, <B>wrjpgcom</B> man page -<p>Wallace, Gregory K. "The JPEG Still Picture Compression -Standard", Communications of the ACM, April 1991 (vol. 34, +<p>Wallace, Gregory K. "The JPEG Still Picture Compression +Standard", Communications of the ACM, April 1991 (vol. 34, no. 4), pp. 30-44. diff --git a/pnmtopalm.html b/pnmtopalm.html index 0a17538f..fdb82cbe 100644 --- a/pnmtopalm.html +++ b/pnmtopalm.html @@ -83,7 +83,7 @@ the options you specify. <ul> <li>If you specify a density (<b>-density</b> option) higher than -"low," the version is at least 3. +"low," the version is at least 3. <li>If you specify transparency (<b>-transparent</b> option) or any compression, the version is at least 2. @@ -154,7 +154,7 @@ whichever is relevant. <p>The <b>-offset</b> option was new in Netpbm 10.26 (January 2005). Before that, <b>pnmtopalm</b> always set the <b>nextDepthOffset</b> -field to "none." +field to "none." <p>Before Netpbm 10.27 (March 2005), you cannot use <b>-offset</b> if you create a compressed raster (because <b>pnmtopalm</b> isn't smart diff --git a/pnmtopng.html b/pnmtopng.html index 14888577..7f6cba83 100644 --- a/pnmtopng.html +++ b/pnmtopng.html @@ -124,13 +124,13 @@ E.g. The old shell command <pre> <kbd> - pnmtopng -size "800 800 0" input.pnm >output.png + pnmtopng -size "800 800 0" input.pnm >output.png </kbd> </pre> <p>If you're writing a program that needs to work with both new and old <b>pnmtopng</b>, have it first try with the new syntax, and if it fails -with "unrecognized option," fall back to the old syntax. +with "unrecognized option," fall back to the old syntax. <DL COMPACT> <DT><B>-verbose</B> @@ -169,7 +169,7 @@ distance between colors in RGB space. If multiple colors are equidistant, <B>pnmtopng</B> chooses one of them arbitrarily. <P>However, if you prefix your color specification with -"=", e.g. +"=", e.g. <pre> <kbd> @@ -308,14 +308,14 @@ arguments. the option <b>-chroma</b> does the same thing, but with slightly different syntax. -<DT><B>-size="</b><i>x</i> <i>y</i> <i>unit</i><b>"</b> +<DT><B>-size="</b><i>x</i> <i>y</i> <i>unit</i><b>"</b> <DD>This option determines the aspect ratio of the individual pixels of your image as well as the physical resolution of it. <p><i>unit</i> is either <b>0</b> or <i>1</i>. When it is <i>1</i>, the option specifies the physical resolution of the image in pixels -per meter. For example, <b>-size="10000 15000 1"</b> means +per meter. For example, <b>-size="10000 15000 1"</b> means that when someone displays the image, he should make it so that 10,000 pixels horizontally occupy 1 meter and 15,000 pixels vertically occupy one meter. And even if he doesn't take this advice on the overall @@ -354,7 +354,7 @@ more information on what this really means. <p>This option was new in Netpbm 10.71 (June 2015). Before that, <b>pnmtopng</b> never generates an sRGB chunk. -<DT><B>-modtime="</b>[<i>yy</i>]<i>yy-mm-dd hh:mm:ss</i><b>"</b> +<DT><B>-modtime="</b>[<i>yy</i>]<i>yy-mm-dd hh:mm:ss</i><b>"</b> <DD>This option allows you to specify the modification time value to be placed in the PNG output. You can specify the year parameter diff --git a/pnmtops.html b/pnmtops.html index 32250220..31573e82 100644 --- a/pnmtops.html +++ b/pnmtops.html @@ -46,7 +46,7 @@ name and its value with white space instead of an equals sign. <p><b>pnmtops</b> reads a Netpbm image stream as input and produces Encapsulated Postscript (EPSF) as output. -<p>(Note: people usually render the name as "PostScript," but we use +<p>(Note: people usually render the name as "PostScript," but we use standard typography in the Netpbm manual, so capitalize only the first letter). @@ -68,8 +68,8 @@ program in the output. (This may not be the best way to create a multi-page Postscript stream; someone who knows Postscript should work on this). <p>The line at the top of the file produced by <b>pnmtops</b> is -either "%!PS-Adobe-3.0 EPSF-3.0" or just -"%!PS-Adobe-3.0". The numbers do not reflect the Postscript +either "%!PS-Adobe-3.0 EPSF-3.0" or just +"%!PS-Adobe-3.0". The numbers do not reflect the Postscript language level, but the version of the DSC comment specification and EPS specification implemented. The Postscript language level is in the "%%LanguageLevel:" comment. <b>pnmtops</b> omits "EPSF-3.0" if you @@ -248,15 +248,15 @@ comp.sources.misc and expo.lcs.mit.edu sometime in October. - Jef <p>This is from <a href="http://www.lngpstscrpt.tk/re-postscript-run-length-encoding-again">a forum about Postscript</a>, extracted in October 2010. Jef added -rle in -August 1988. In those days, RS-232 lines (referred to as "serial" in +August 1988. In those days, RS-232 lines (referred to as "serial" in the quotation) were typically 9600bps. 2400 bps lines were still around. -What the quotation calls "the network" is probably a 10 Mbps +What the quotation calls "the network" is probably a 10 Mbps Ethernet connection. <dt><b>-flate</b> -<dd>This option tells <b>pnmtops</b> to use "flate" -compression (i.e. compression via the "Z" library -- the +<dd>This option tells <b>pnmtops</b> to use "flate" +compression (i.e. compression via the "Z" library -- the same as PNG). <p>See the <b>-rle</b> option for information about compression in general. @@ -276,14 +276,14 @@ and <b>-flate</b> together. <dt><b>-ascii85</b> -<dd>By default, <b>pnmtops</b> uses "asciihex" encoding of +<dd>By default, <b>pnmtops</b> uses "asciihex" encoding of the image raster. The image raster is a stream of bits, while a Postscript program is text, so there has to be an encoding from bits to text. Asciihex encoding is just the common hexadecimal representation of bits. E.g. 8 -1 bits would be encoded as the two characters "FF". +1 bits would be encoded as the two characters "FF". <p>With the <b>-ascii85</b> option, <b>pnmtops</b> uses -"ascii85" encoding instead. This is an encoding in which 32 +"ascii85" encoding instead. This is an encoding in which 32 bits are encoded into five characters of text. Thus, it produces less text for the same raster than asciihex. But ascii85 is not available in Postscript Level 1, whereas asciihex is. @@ -351,7 +351,7 @@ collection as it exits. <DT><B>-setpage</B> <DD> - This causes <b>pnmtops</b> to include a "setpagedevice" + This causes <b>pnmtops</b> to include a "setpagedevice" directive in the output. This causes the output to violate specifications of EPSF encapsulated Postscript, but if you're not using it in an encapsulated way, may be what you need. The directive tells the @@ -360,13 +360,13 @@ collection as it exits. <b>-width</b> and <b>-height</b> options or defaulted. <p>From January through May 2002, the default was to include - "setpagedevice" and this option did not exist. Before - January 2002, there was no way to include "setpagedevice" + "setpagedevice" and this option did not exist. Before + January 2002, there was no way to include "setpagedevice" and neither the <b>-setpage</b> nor <b>-nosetpage</b> option existed. <DT><B>-nosetpage</B> <DD> - This tells <b>pnmtops</b> not to include a "setpagedevice" + This tells <b>pnmtops</b> not to include a "setpagedevice" directive in the output. This is the default, so the option has no effect. @@ -374,9 +374,9 @@ collection as it exits. <DT><B>-noshowpage</B> <DD> - This tells <b>pnmtops</b> not to include a "showpage" + This tells <b>pnmtops</b> not to include a "showpage" directive in the output. By default, <b>pnmtops</b> includes a - "showpage" at the end of the EPSF program. According to + "showpage" at the end of the EPSF program. According to EPSF specs, this is OK, and the program that includes the EPSF is supposed to redefine showpage so this doesn't cause undesirable behavior. But it's often easier just not to have the showpage. @@ -386,7 +386,7 @@ collection as it exits. <dt><b>-showpage</b> <dd> - This tells <b>pnmtops</b> to include a "showpage" directive + This tells <b>pnmtops</b> to include a "showpage" directive at the end of the EPSF output. This is the default, so the option has no effect. diff --git a/pnmtorle.html b/pnmtorle.html index 5daef6e8..c62147a8 100644 --- a/pnmtorle.html +++ b/pnmtorle.html @@ -47,12 +47,12 @@ done by piping the output of this program into the Utah <b>mcut</b> or <DD> This option will cause <b>pnmtorle</b> to operate in verbose mode. The header -information is written to "stderr". Actually, there is not much header +information is written to "stderr". Actually, there is not much header information stored in a Netpbm file, so this information is minimal. <DT><B>-h</B> <DD> -This option allows the header of the Netpbm image to be dumped to "stderr" +This option allows the header of the Netpbm image to be dumped to "stderr" without converting the file. It is equivalent to using the -v option except that no file conversion takes place. <DT><B>-a</B> diff --git a/pnmtosgi.html b/pnmtosgi.html index 468c59b1..62cda3e8 100644 --- a/pnmtosgi.html +++ b/pnmtosgi.html @@ -46,9 +46,9 @@ Write a compressed (run length encoded) file. <DT><B>-imagename</b> <i>name</i> <DD> -Write the string "name" into the imagename field of the header. +Write the string "name" into the imagename field of the header. The name string is limited to 79 characters. -If no name is given, pnmtosgi writes "no name" into this field. +If no name is given, pnmtosgi writes "no name" into this field. </DL> <A NAME="lbAG"> </A> diff --git a/ppm.html b/ppm.html index 05cfde72..c5cd1a3f 100644 --- a/ppm.html +++ b/ppm.html @@ -35,8 +35,8 @@ every respect except the precise semantics of the sample values. These files are useful because of the way PPM is used as an intermediary format. They are informally called PPM files, but to be absolutely precise, you should indicate the variation from true PPM. -For example, "PPM using the red, green, and blue colors that the -scanner in question uses." +For example, "PPM using the red, green, and blue colors that the +scanner in question uses." <P>The name "PPM" is an acronym derived from "Portable Pixel Map." Images in this format (or a precursor of it) were once also called @@ -54,8 +54,8 @@ no data, delimiters, or padding before, after, or between images. <P>Each PPM image consists of the following: <OL> -<LI>A "magic number" for identifying the file type. -A ppm image's magic number is the two characters "P6". +<LI>A "magic number" for identifying the file type. +A ppm image's magic number is the two characters "P6". <LI> Whitespace (blanks, TABs, CRs, LFs). <LI> @@ -82,7 +82,7 @@ significant byte is first. <P>A row of an image is horizontal. A column is vertical. The pixels in the image are square and contiguous. -<p>In the raster, the sample values are "nonlinear." They are +<p>In the raster, the sample values are "nonlinear." They are proportional to the intensity of the ITU-R Recommendation BT.709 red, green, and blue in the pixel, adjusted by the BT.709 gamma transfer function. (That transfer function specifies a gamma number of 2.2 and @@ -103,29 +103,29 @@ variation on PPM is to substitute this color space for the one specified. <p> Note that a common variation on the PPM format is to have the sample -values be "linear," i.e. as specified above except without +values be "linear," i.e. as specified above except without the gamma adjustment. <B>pnmgamma</B> takes such a PPM variant as input and produces a true PPM as output. </OL> -<p>Strings starting with "#" may be comments, the same as +<p>Strings starting with "#" may be comments, the same as with <a href="pbm.html">PBM</a>. <P>Note that you can use <B>pamdepth</B> to convert between a the format with 1 byte per sample and the one with 2 bytes per sample. <p>All characters referred to herein are encoded in ASCII. -"newline" refers to the character known in ASCII as Line -Feed or LF. A "white space" character is space, CR, LF, +"newline" refers to the character known in ASCII as Line +Feed or LF. A "white space" character is space, CR, LF, TAB, VT, or FF (I.e. what the ANSI standard C isspace() function calls white space). <h3 id="plainppm">Plain PPM</h3> <P>There is actually another version of the PPM format that is fairly -rare: "plain" PPM format. The format above, which generally -considered the normal one, is known as the "raw" PPM format. +rare: "plain" PPM format. The format above, which generally +considered the normal one, is known as the "raw" PPM format. See <B><A HREF="pbm.html">pbm</A></B> for some commentary on how plain and raw formats relate to one another and how to use them. @@ -180,7 +180,7 @@ also applies. <h2 id="filename">FILE NAME</h2> <p>There are no requirements on the name of a PPM file, but the convention is -to use the suffix ".ppm". "pnm" is also conventional, for +to use the suffix ".ppm". "pnm" is also conventional, for cases where distinguishing between the particular subformats of PNM is not convenient. diff --git a/ppmbrighten.html b/ppmbrighten.html index 56188ffc..a9657ac6 100644 --- a/ppmbrighten.html +++ b/ppmbrighten.html @@ -140,7 +140,7 @@ Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting -documentation. This software is provided "as is" without express or +documentation. This software is provided "as is" without express or implied warranty. <HR> diff --git a/ppmchange.html b/ppmchange.html index f89b3036..e8548490 100644 --- a/ppmchange.html +++ b/ppmchange.html @@ -48,7 +48,7 @@ specify the <B>-remainder</B> option, in which case they are all changed to the single specified color. <P>You can specify that colors similar, but not identical, to the ones -you specify get replaced by specifying a "closeness" factor. +you specify get replaced by specifying a "closeness" factor. <P>Specify the colors as described for the <a href="libppm.html#colorname">argument of the <b>ppm_parsecolor()</b> @@ -92,7 +92,7 @@ specified. color you specified is less than or equal to <I>closeness</I> per cent of the maxval. -<P>The "distance" in color is defined as the Cartesian sum of the +<P>The "distance" in color is defined as the Cartesian sum of the individual differences in red, green, and blue intensities between the two pixels, normalized so that the difference between black and white is 100%. diff --git a/ppmcie.html b/ppmcie.html index 4d57b741..9ccc7349 100644 --- a/ppmcie.html +++ b/ppmcie.html @@ -49,7 +49,7 @@ ppmcie - draw a CIE color chart as a PPM image <p>This program is part of <a href="index.html">Netpbm</a>. <B>ppmcie</B> creates a PPM file containing a plot of the CIE -"tongue" color chart -- to the extent possible in a PPM +"tongue" color chart -- to the extent possible in a PPM image. Alternatively, creates a pseudo-PPM image of the color tongue using RGB values from a color system of your choice. @@ -351,7 +351,7 @@ strength blue BT.709 primary illuminants is D65 white. <p>The tongue has a sharp straight edge at the bottom because that's the limit of human vision. There are colors below that line, but they involve infrared and ultraviolet light, so you can't see them. This -line is called the "line of purples." +line is called the "line of purples." diff --git a/ppmdmkfont.html b/ppmdmkfont.html index 28eeaeba..60bac3b1 100644 --- a/ppmdmkfont.html +++ b/ppmdmkfont.html @@ -8,7 +8,7 @@ Updated: September 2005 <H2>NAME</H2> -ppmdmkfont - Create Ppmdfont "standard". +ppmdmkfont - Create Ppmdfont "standard". <H2 id="synopsis">SYNOPSIS</H2> @@ -18,13 +18,13 @@ ppmdmkfont - Create Ppmdfont "standard". <p>This program is part of <a href="index.html">Netpbm</a>. -<p><b>ppmdmkfont</b> creates the "standard" Ppmdfont font as +<p><b>ppmdmkfont</b> creates the "standard" Ppmdfont font as a Ppmdfont file. It has no input; it always generates identical files. <p>(There are no arguments or options) <p>This program is useful mainly as an example for creating other fonts. -<b>libnetpbm</b> has the "standard" font built in. +<b>libnetpbm</b> has the "standard" font built in. <p>See <A HREF="libnetpbm_draw.html">Libnetpbm PPM Drawing Function Manual</A> for details on Ppmdfont files. diff --git a/ppmdraw.html b/ppmdraw.html index 2e2fe4cc..75bf1ebb 100644 --- a/ppmdraw.html +++ b/ppmdraw.html @@ -36,7 +36,7 @@ and its value. <p><B>ppmdraw</B> draws lines, shapes, text, etc. on a PPM image. It is essentially an easy-to-program front end to <b>libnetpbm</b>'s -"ppmd" subroutines. It lets you create a human-friendly +"ppmd" subroutines. It lets you create a human-friendly script to describe the drawing rather than write a C program. <p>You supply drawing instructions with a script, which you supply either @@ -46,19 +46,19 @@ in a file named by a <b>-scriptfile</b> option or as the value of a <pre> <code> setpos 50 50; -text_here 10 30 "hello"; +text_here 10 30 "hello"; setcolor black; -text_here 10 0 "there"; +text_here 10 0 "there"; line_here 5 20; </code> </pre> <p>This example starts at Column 50, Row 50 of the input image and -writes the word "hello" there in 10 pixel high white letters +writes the word "hello" there in 10 pixel high white letters at a 30 degree angle up from horizontal. Then, from where that leaves -off, the script writes "there" in 10 pixel high black +off, the script writes "there" in 10 pixel high black letters horizontally. Finally, it draws a black line to a point 5 -pixels over and 20 pixels down from the end of "there." +pixels over and 20 pixels down from the end of "there." <P>If you don't specify <I>ppmfile</I>, <B>ppmdraw</B> reads its input PPM image from Standard Input. @@ -128,7 +128,7 @@ But any pixels you draw there just get discarded. <dl> <dt>setpos -<dd>Set the "current position" in the image. This affects +<dd>Set the "current position" in the image. This affects where subsequent commands draw things. The 2 arguments are the column and row number. @@ -136,7 +136,7 @@ and row number. <dt>setlinetype -<dd>The 1 argument is "normal" or "nodiag.". This +<dd>The 1 argument is "normal" or "nodiag.". This effects a <b>ppmd_setlinetype()</b> call. Further details are not yet documented. @@ -146,7 +146,7 @@ documented. <dt>setcolor -<dd>This sets the "current color", which determines the color +<dd>This sets the "current color", which determines the color in which subsequent drawing commands draw. Before the first <b>setcolor</b>, the current color is white. @@ -156,17 +156,17 @@ library routine</a>. <dt>setfont -<dd>This sets the "current font", which determines the font +<dd>This sets the "current font", which determines the font in which subsequent text drawing commands draw. Before the first <b>setfont</b>, the current font is a built in font called -"standard." +"standard." <p>The argument of this command is a file name. It is the name of a Netpbm PPMD font file. <p>A Netpbm PPMD font file typically has a name that ends in -".ppmdfont" and its first 8 bytes are the ASCII encoding of -"ppmdfont". +".ppmdfont" and its first 8 bytes are the ASCII encoding of +"ppmdfont". <p>There is only one of these fonts as far as we know. It is distributed with Netpbm as the file <b>standard.ppmdfont</b>, but you don't need to use that diff --git a/ppmfade.html b/ppmfade.html index 2d1c8eb6..29b2b2bf 100644 --- a/ppmfade.html +++ b/ppmfade.html @@ -88,8 +88,8 @@ of the second image and finally faded to the final image. <DT><B>-oil</B> -<DD>The first image is faded to an "oil transfer" version -of the first image. This is then faded to an "oil transfer" +<DD>The first image is faded to an "oil transfer" version +of the first image. This is then faded to an "oil transfer" version of the second image and finally faded to the final image. <DT><B>-edge</B> @@ -101,9 +101,9 @@ finally faded to the final image. <DT><B>-bentley</B> -<DD> The first image is faded to a "Bentley Effect" version -of the first image. This is then faded to a "Bentley -Effect" version of the second image and finally faded to the +<DD> The first image is faded to a "Bentley Effect" version +of the first image. This is then faded to a "Bentley +Effect" version of the second image and finally faded to the final image. <DT><B>-block</B> @@ -127,7 +127,7 @@ This forms part of the output filenames, as described above. <P> Fade from teapot.ppm to pyr.ppm generating fade.0001.ppm to fade.0030.ppm using -the "spread" transition. +the "spread" transition. <P> <B>ppmfade -l teapot.ppm</B> diff --git a/ppmforge.html b/ppmforge.html index 8db4483b..e18c6f0e 100644 --- a/ppmforge.html +++ b/ppmforge.html @@ -170,7 +170,7 @@ geometrically-precise ice cap boundaries. <DT><B>-hour</B> <I>hour</I> <DD>When generating a planet, <b>ppmforge</b> uses <I>hour</I> as the -"hour angle at the central meridian." If you specify <B>-hour +"hour angle at the central meridian." If you specify <B>-hour 12</B>, for example, the planet will be fully illuminated, corresponding to high noon at the longitude at the center of the screen. You can specify any floating point value between 0 and 24 for @@ -188,8 +188,8 @@ crescents. those of the Earth. Smaller values reduce the amount of ice, while larger <B>-ice</B> settings create more prominent ice caps. Sufficiently large values, such as 100 or more, in conjunction with -small settings for <B>-glaciers</B> (try 0.1) create "ice -balls" like Europa. +small settings for <B>-glaciers</B> (try 0.1) create "ice +balls" like Europa. <DT><B>-inclination|-tilt</B> <I>angle</I> @@ -230,7 +230,7 @@ output consists exclusively of stars. <DT><B>-power</B> <I>factor</I> -<DD>Sets the "power factor" used to scale elevations +<DD>Sets the "power factor" used to scale elevations synthesised from the FFT to <I>factor</I>, which can be any floating point number greater than zero. If no factor is specified a default of 1.2 is used if a planet is being generated, or 0.75 if clouds are diff --git a/ppmlabel.html b/ppmlabel.html index 8e38955b..a1494917 100644 --- a/ppmlabel.html +++ b/ppmlabel.html @@ -52,7 +52,7 @@ ppmlabel - add text to a PPM image <p>This program is part of <a href="index.html">Netpbm</a>. <p><B>ppmlabel</B> uses the text drawing facilities of <B>libnetpbm</B>'s -"ppmd" component to add text to a PBM image. You control +"ppmd" component to add text to a PBM image. You control the location, size, baseline angle, color of the text, and background color (if any) with command line arguments. You can specify the text on the command line or supply it in files. diff --git a/ppmntsc.html b/ppmntsc.html index 5095084f..fc269748 100644 --- a/ppmntsc.html +++ b/ppmntsc.html @@ -33,9 +33,9 @@ Often, images generated on the computer are made for use in movies which ultimately end up on a television screen. However, the range of colors (as specified by their RGB values) on a computer does not match the range of colors that can be represented using the NTSC (or PAL) -systems. If an image with "illegal" colors is sent directly +systems. If an image with "illegal" colors is sent directly to an NTSC (or PAL) video system for recording, the -"illegal" colors will be clipped. This may result in an +"illegal" colors will be clipped. This may result in an undesirable looking picture. <P>This utility tests each pixel in an image to see if it falls diff --git a/ppmpat.html b/ppmpat.html index fb2ecba0..0ded8652 100644 --- a/ppmpat.html +++ b/ppmpat.html @@ -99,7 +99,7 @@ invocations. <H2 id="references">REFERENCES</H2> -Some of the patterns are from "Designer's Guide to Color 3" +Some of the patterns are from "Designer's Guide to Color 3" by Jeanne Allen. <H2 id="seealso">SEE ALSO</H2> diff --git a/ppmrainbow.html b/ppmrainbow.html index 9d966177..f93a431d 100644 --- a/ppmrainbow.html +++ b/ppmrainbow.html @@ -97,7 +97,7 @@ and creates all its files within that directory. <DT><B>-verbose</B> -<DD>Print the "commands" (invocations of other Netpbm +<DD>Print the "commands" (invocations of other Netpbm programs) that <B>ppmrainbow</B> uses to create the image. </DL> diff --git a/ppmrelief.html b/ppmrelief.html index 9725f1f1..c9af17b1 100644 --- a/ppmrelief.html +++ b/ppmrelief.html @@ -23,7 +23,7 @@ ppmrelief - compute a relief of a PPM image <p><b>ppmrelief</b> reads a PPM image as input, and writes a relief of that image as a PPM image as output. -<P>The relief process is described in "Beyond Photography" by +<P>The relief process is described in "Beyond Photography" by Holzmann, equation 3.19. It's a sort of edge-detection and is essentially a convolution with this matrix: diff --git a/ppmrough.html b/ppmrough.html index cc524bdd..4e2d3fb9 100644 --- a/ppmrough.html +++ b/ppmrough.html @@ -72,7 +72,7 @@ you don't specify any of the <B>-left</B>, <B>-right</B>, <B>-top</B>, and <B>-bottom</B> options, all pixels are set to foreground color. The defaults are white foreground and black background. -<P>Use the <B>-var</B> option to control the "raggedness" of +<P>Use the <B>-var</B> option to control the "raggedness" of the border. The less its value is the smoother the border is. You can initialize the pseudo-random generator with the <B>-init</B> option. diff --git a/ppmshadow.html b/ppmshadow.html index d3ac3532..8e74d3d3 100644 --- a/ppmshadow.html +++ b/ppmshadow.html @@ -179,7 +179,7 @@ processing it with <B>ppmshadow</B>. <P>Black pixels and pixels with the same color as the image background don't cast a shadow. If this causes unintentional -"holes" in the shadow, fill the offending areas with a color +"holes" in the shadow, fill the offending areas with a color which differs from black or the background by RGB values of 1, which will be imperceptible to the viewer. Since the comparison is exact, the modified areas will now cast shadows. diff --git a/ppmsvgalib.html b/ppmsvgalib.html index afff3983..f868965a 100644 --- a/ppmsvgalib.html +++ b/ppmsvgalib.html @@ -39,8 +39,8 @@ Svgalib has its own device driver, so you need only proper permissions on a device special file to access the console. <P><B>ppmsvgalib</B> is not capable of using color mapped video modes. -These are the old video modes that are usually called "8 -bit" color modes. +These are the old video modes that are usually called "8 +bit" color modes. <P><B>ppmsvgalib</B> is a bare displayer. It won't do any manipulation of the image and is not interactive in any way. If you @@ -48,7 +48,7 @@ want a regular interactive graphics viewer that uses Svgalib, try <B>zgv</B> (not part of Netpbm). <P>To exit <B>ppmsvgalib</B> while it is displaying your image, send -it a SIGINTR signal (normally, this means "hit control C"). +it a SIGINTR signal (normally, this means "hit control C"). <P><B>ppmsvgalib</B> draws a white border around the edges of the screen. It does this to help you isolate problems between the image diff --git a/ppmtoacad.html b/ppmtoacad.html index c8c73de3..7e70dc84 100644 --- a/ppmtoacad.html +++ b/ppmtoacad.html @@ -153,7 +153,7 @@ Suisse/Schweiz/Svizzera/Svizra/Switzerland <P>Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, without any conditions or restrictions. This software is provided -"as is" without express or implied warranty. +"as is" without express or implied warranty. <P>Autocad and Autodesk are registered trademarks of Autodesk, Inc. diff --git a/ppmtoarbtxt.html b/ppmtoarbtxt.html index 3a080f61..0d76ff4e 100644 --- a/ppmtoarbtxt.html +++ b/ppmtoarbtxt.html @@ -78,7 +78,7 @@ 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". +<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 @@ -208,8 +208,8 @@ of the sphere is the color of the pixel. <p>Contents of our head skeleton: <pre> -#include "colors.inc" -#include "textures.inc" +#include "colors.inc" +#include "textures.inc" camera { location <#(width) * 0.6, #(height) * 0.7, 80> look_at <#(width) * 0.5, #(height) * 0.5, 0> diff --git a/ppmtobmp.html b/ppmtobmp.html index 4e25034e..6eadce77 100644 --- a/ppmtobmp.html +++ b/ppmtobmp.html @@ -62,7 +62,7 @@ or <B>ppmdither</B> to reduce the number of colors in the image. <dt><b>-mapfile=</b><i>filename</i> <dd>This identifies a file to use as the BMP palette (aka -"colormap"). In one BMP subformat, the BMP stream contains +"colormap"). In one BMP subformat, the BMP stream contains a palette of up to 256 colors, and represents the image raster as indices into that palette. Normally, <b>ppmtobmp</b> takes care of computing a suitable palette, but if you are going to dissect the BMP diff --git a/ppmtoicr.html b/ppmtoicr.html index c7f924a3..87aa389d 100644 --- a/ppmtoicr.html +++ b/ppmtoicr.html @@ -56,7 +56,7 @@ way. <DT><B>-windowname</B> <I>name</I> <DD>Output will be displayed in <I>name</I> (Default is to use -<I>ppmfile</I> or "untitled" if the input is from Standard +<I>ppmfile</I> or "untitled" if the input is from Standard Input). <DT><B>-expand</B> <I>expand</I> diff --git a/ppmtoilbm.html b/ppmtoilbm.html index e15f1858..132d65f6 100644 --- a/ppmtoilbm.html +++ b/ppmtoilbm.html @@ -69,8 +69,8 @@ colormap files) unofficial DCOL chunk for direct color ILBM. <A NAME="lbAE"> </A> <H2>OPTIONS</H2> -<p>Options marked with (*) can be prefixed with a "no", -e.g. "-nohamif". All options can be abbreviated to their +<p>Options marked with (*) can be prefixed with a "no", +e.g. "-nohamif". All options can be abbreviated to their shortest unique prefix. <DL COMPACT> diff --git a/ppmtomitsu.html b/ppmtomitsu.html index 67b98a9b..4847a22c 100644 --- a/ppmtomitsu.html +++ b/ppmtomitsu.html @@ -70,7 +70,7 @@ PPM input that <b>ppmtomitsu</b> will use properly. <DT><B>-sharpness</B> <I>1-4</I> <DD> -"sharpness" designation. Default is to use the current sharpness. +"sharpness" designation. Default is to use the current sharpness. <DT><B>-enlarge</B> <I>1-3</I> diff --git a/ppmtompeg.html b/ppmtompeg.html index 99efed9d..a1ce767c 100644 --- a/ppmtompeg.html +++ b/ppmtompeg.html @@ -1115,7 +1115,7 @@ options. <P>You can run <b>ppmtompeg</b> on multiple machines at once, encoding the same MPEG stream. When you do, the machines are used as shown in -the following diagram. We call this "parallel mode." +the following diagram. We call this "parallel mode." <p><img src="ppmtompeg-par.gif" alt="ppmtompeg-par.gif"> @@ -1165,8 +1165,8 @@ have easy access to the input files, you must specify the <B>SIZE</B> parameter file statement when you do parallel operation. <p>The machine on which you originally invoke <b>ppmtompeg</b> is the -master machine. It hosts a "combine server,", a -"decode server," and a number of "i/o servers," +master machine. It hosts a "combine server,", a +"decode server," and a number of "i/o servers," all as separate processes. The other machines in the network (listed in the parameter file) are slave machines. Each hosts a single process that continuously requests work from the master and does it. diff --git a/ppmtopcx.html b/ppmtopcx.html index caa8c209..aead0f52 100644 --- a/ppmtopcx.html +++ b/ppmtopcx.html @@ -80,7 +80,7 @@ colors or fewer. <DT><B>-packed</B> -<DD>Use "packed pixel" format for files with 16 colors or +<DD>Use "packed pixel" format for files with 16 colors or fewer: 1, 2, or 4 bits/pixel, 1 plane. <DT><B>-stdpalette</B> diff --git a/ppmtopgm.html b/ppmtopgm.html index b7e59394..10edf780 100644 --- a/ppmtopgm.html +++ b/ppmtopgm.html @@ -24,7 +24,7 @@ ppmtopgm - convert a PPM image to a PGM image <p>This program is part of <a href="index.html">Netpbm</a>. <p><b>ppmtopgm</b> reads a PPM as input and produces a PGM as output. -The output is a "black and white" rendering of the original +The output is a "black and white" rendering of the original image, as in a black and white photograph. The quantization formula <b>ppmtopgm</b> uses is g = .299 r + .587 g + .114 b. diff --git a/ppmtopuzz.html b/ppmtopuzz.html index b777caf9..4d734d49 100644 --- a/ppmtopuzz.html +++ b/ppmtopuzz.html @@ -9,7 +9,7 @@ Updated: 22 August 1990 <A NAME="lbAB"> </A> <H2>NAME</H2> -ppmtopuzz - convert a PPM image to an X11 "puzzle" file +ppmtopuzz - convert a PPM image to an X11 "puzzle" file <A NAME="lbAC"> </A> <H2>SYNOPSIS</H2> @@ -24,7 +24,7 @@ ppmtopuzz - convert a PPM image to an X11 "puzzle" file <p>This program is part of <a href="index.html">Netpbm</a>. <p><b>ppmtopuzz</b> reads a PPM image as input and produces an X11 -"puzzle" file as output. A "puzzle" file is for +"puzzle" file as output. A "puzzle" file is for use with the <b>puzzle</b> program included with the X11 distribution. <b>puzzle</b>'s <B>-picture</B> option lets you specify an image file. diff --git a/ppmtosixel.html b/ppmtosixel.html index e9b6d63a..c7d1d9a7 100644 --- a/ppmtosixel.html +++ b/ppmtosixel.html @@ -46,7 +46,7 @@ image file. <DD>If you specify this, each pixel will be explicitly described in the image file. If <B>-raw</B> is not specified, output will default to compressed format in which identical adjacent pixels are replaced -by "repeat pixel" commands. A raw file is often an order of +by "repeat pixel" commands. A raw file is often an order of magnitude larger than a compressed file and prints much slower. <DT><B>-margin</B> diff --git a/ppmtoxpm.html b/ppmtoxpm.html index 80adbc64..1d863a46 100644 --- a/ppmtoxpm.html +++ b/ppmtoxpm.html @@ -53,7 +53,7 @@ is greater than 15, such as by running it through <B>pamdepth 255</b>. <h3>Color Code Lengths - Image Size</h3> -<p>In the XPM format, there is a palette ("color map") that +<p>In the XPM format, there is a palette ("color map") that assigns each color in the image to a unique sequence of printable characters called a color code, and a raster that identifies the color of each pixel of the image with one of those color codes. The length @@ -71,7 +71,7 @@ codes will be one character. If you have more than 92 but not more than 92 * <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 transparency 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>. @@ -149,7 +149,7 @@ Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting -documentation. This software is provided "as is" without express or +documentation. This software is provided "as is" without express or implied warranty. <P> This tool was developed for Schlumberger Technologies, ATE Division, and diff --git a/psidtopgm.html b/psidtopgm.html index 598bfe24..d6854d05 100644 --- a/psidtopgm.html +++ b/psidtopgm.html @@ -8,7 +8,7 @@ Updated: 02 August 89 <A NAME="lbAB"> </A> <H2>NAME</H2> -psidtopgm - convert PostScript "image" data to a PGM image +psidtopgm - convert PostScript "image" data to a PGM image <A NAME="lbAC"> </A> <H2>SYNOPSIS</H2> @@ -20,7 +20,7 @@ psidtopgm - convert PostScript "image" data to a PGM image <p>This program is part of <a href="index.html">Netpbm</a>. -<p><b>psidtopgm</b> reads the "image" data from a PostScript +<p><b>psidtopgm</b> reads the "image" data from a PostScript file as input and produces a PGM image as output. <P>This program is obsoleted by <B>pstopnm</B>. @@ -32,7 +32,7 @@ so many people have asked for it. To use it you have to <em>manually</em> extract the readhexstring data portion from your PostScript file, and then give the width, height, and bits/sample on the command line. Before you attempt this, you should <em>at -least</em> read the description of the "image" operator in +least</em> read the description of the "image" operator in the PostScript Language Reference Manual. <P>It would probably not be too hard to write a script that uses this diff --git a/pstopnm.html b/pstopnm.html index 99b65565..3fc177b8 100644 --- a/pstopnm.html +++ b/pstopnm.html @@ -70,8 +70,8 @@ render a PostScript file with its PNM device drivers. If you don't have GhostScript installed or the version you have installed was not built with the relevant PNM device drivers, <B>pstopnm</B> will fail. You can see if you have the proper environment by issuing the command -<kbd>gs --help </kbd>. If it responds and lists under "Available -Devices" <B>pbm</B>, <B>pbmraw</B>, <B>pgm</B>, <B>pgmraw</B>, +<kbd>gs --help </kbd>. If it responds and lists under "Available +Devices" <B>pbm</B>, <B>pbmraw</B>, <B>pgm</B>, <B>pgmraw</B>, <B>pnm</B>, <B>pnmraw</B>, <B>ppm</B>, or <B>ppmraw</B>, you're in business. @@ -216,9 +216,9 @@ represents 1/600 inch horizontally, but 1/300 inch vertically. other, <b>pstopnm</b> defaults the other such that the output device resolution is the same in both directions. -<p>The "x" and "y" of <b>-xsize</b> and <b>-ysize</b> +<p>The "x" and "y" of <b>-xsize</b> and <b>-ysize</b> refer to the image being printed on the page, not the page. So if -<b>pstopnm</b> prints it in landscape orientation, "x" would pertain +<b>pstopnm</b> prints it in landscape orientation, "x" would pertain to the vertical direction on the page, i.e. the vertical direction in the output PNM image. diff --git a/sldtoppm.html b/sldtoppm.html index fc91bf9f..1573cd06 100644 --- a/sldtoppm.html +++ b/sldtoppm.html @@ -167,7 +167,7 @@ Suisse/Schweiz/Svizzera/Svizra/Switzerland Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, without any conditions or restrictions. This software is provided -"as is" without express or implied warranty. +"as is" without express or implied warranty. <P>AutoCAD and Autodesk are registered trademarks of Autodesk, Inc. diff --git a/sunicontopnm.html b/sunicontopnm.html index 0290f7b5..a25a77e3 100644 --- a/sunicontopnm.html +++ b/sunicontopnm.html @@ -61,7 +61,7 @@ mostly XPM files. <p>Jef Poskanzer wrote the program under the name <b>icontopbm</b> in 1988. <p>In October 2010, Prophet Of The Way (afu@wta.att.ne.jp) converted it to use -the more recent "packed PBM" library functions, thus speeding it up +the more recent "packed PBM" library functions, thus speeding it up <P>Netpbm 10.53 (December 2010) renamed the program to <b>sunicontopnm</b>. This name reflects the fact that there are lots of kinds of icons in the world @@ -69,7 +69,7 @@ besides the Sun variety, Windows ones being most popular. It also takes into account the new Depth=8 capability (see below). <p>Netpbm 10.53 (December 2010) added the ability to work with Depth=8 -icon input and input with 32 bit "items." Whereas the previous +icon input and input with 32 bit "items." Whereas the previous program always produced PBM output, the new program produced PGM in the Depth=8 case. diff --git a/svgtopam.html b/svgtopam.html index c1fabc85..c098579f 100644 --- a/svgtopam.html +++ b/svgtopam.html @@ -29,7 +29,7 @@ produces a PAM image as output. <p><b>svgtopam</b> is so weak that it is probably not useful in general for converting SVG images. It understands only <path> SVG elements -which use only the "M", "L", and "z" commands. +which use only the "M", "L", and "z" commands. This is sufficient for converting anything that comes out of <b>pamtosvg</b> (not by coincidence - the program was developed for the specific task of testing <b>pamtosvg</b>), but the main reason it is part of diff --git a/tifftopnm.html b/tifftopnm.html index b4f2670f..d906e7e6 100644 --- a/tifftopnm.html +++ b/tifftopnm.html @@ -35,12 +35,12 @@ generates a PGM image; otherwise, the output is PPM. The program tells you which type it is writing. <p>If the TIFF file contains multiple images (multiple -"directories"), <b>tifftopnm</b> generates a multi-image PNM +"directories"), <b>tifftopnm</b> generates a multi-image PNM 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 file that contains the Tiff -image. If you specify "-" or don't specify this +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 @@ -129,7 +129,7 @@ the transparency output file. <DT><B>-respectfillorder</B> -<DD>By default, <B>tifftopnm </B> ignores the "fillorder" +<DD>By default, <B>tifftopnm </B> ignores the "fillorder" tag in the TIFF input, which means it may incorrectly interpret the image. To make it follow the spec, use this option. For a lengthy but engaging discussion of why <B>tifftopnm</B> works this way and how @@ -243,7 +243,7 @@ in debugging TIFF file conversion problems. <P> There is a piece of information in the header of a TIFF image called -"fillorder." The TIFF specification quite clearly states +"fillorder." The TIFF specification quite clearly states that this value tells the order in which bits are arranged in a byte in the description of the image's pixels. There are two options, assuming that the image has a format where more than one pixel can be diff --git a/winicon.html b/winicon.html index 21f9aa76..64816a11 100644 --- a/winicon.html +++ b/winicon.html @@ -17,7 +17,7 @@ resolutions up to 256 by 256 pixels and various bpp values. The images are encoded either as Portable Network Graphics file (PNG), or in a format similar to Microsoft's BMP format. -<P>If encoded as BMP, the image includes an ‘AND mask’, +<P>If encoded as BMP, the image includes an "AND mask", which contains 1-bit transparency data. It may also contain additional 8-bit transparency data together with the color information. @@ -35,9 +35,9 @@ depth. <H3 id="masks">XOR Mask and AND Mask</H3> -<p>BMP encoded images contain two pixel maps: The so-called ‘XOR -mask’ stores the color information for each pixel, and the -‘AND mask’ stores the transparency belonging to it. +<p>BMP encoded images contain two pixel maps: The so-called "XOR +mask" stores the color information for each pixel, and the +"AND mask" stores the transparency belonging to it. <P>The names and the function of these maps are most easily understood by looking at how a 1-bpp icon image is rendered on a diff --git a/winicontopam.html b/winicontopam.html index 989b3045..19f0118f 100644 --- a/winicontopam.html +++ b/winicontopam.html @@ -33,7 +33,7 @@ converts it to one or more RGB_ALPHA Netpbm PAM files. <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’. +transparency channel is constructed from the so-called "AND mask". <P>The output goes to Standard Output. @@ -56,8 +56,8 @@ line options: <p>You may not specify this together with <b>-image</b>. -<p>By default, <b>winicontopam</b> converts only the one ‘best -quality’ image (largest, then most bits per pixel). +<p>By default, <b>winicontopam</b> converts only the one "best +quality" image (largest, then most bits per pixel). <DT><B>-image=</B><I>index</I> @@ -65,7 +65,7 @@ quality’ image (largest, then most bits per pixel). <p>You may not specify this together with <b>-allimages</b>. -<p>By default, <b>winicontopam</b> converts the ‘best quality’ +<p>By default, <b>winicontopam</b> converts the "best quality" image (largest, then most bits per pixel). <DT><B>-andmasks</B> diff --git a/xpmtoppm.html b/xpmtoppm.html index 5e2aa42a..297b76e4 100644 --- a/xpmtoppm.html +++ b/xpmtoppm.html @@ -63,7 +63,7 @@ Netpbm 10.30 (October 2005), the limit was 2K. Version 3; i.e. it rejects as invalid many valid XPM images. <p>The only place a comment block is valid is starting in Column 1 of the -line immediately after "static char ...". +line immediately after "static char ...". <p>In addition, <b>ppmtoxpm</b> properly recognizes any single-line comment that begins in Column 1 in the color table part of the file. diff --git a/xvminitoppm.html b/xvminitoppm.html index fe4eda19..c9cce7ae 100644 --- a/xvminitoppm.html +++ b/xvminitoppm.html @@ -8,7 +8,7 @@ Updated: 02 April 2006 <H2>NAME</H2> -xvminitoppm - convert an XV "thumbnail" picture to PPM +xvminitoppm - convert an XV "thumbnail" picture to PPM <H2 id="synopsis">SYNOPSIS</H2> @@ -20,8 +20,8 @@ xvminitoppm - convert an XV "thumbnail" picture to PPM <p>This program is part of <a href="index.html">Netpbm</a>. -<p><b>xvminittoppm</b> reads an XV "thumbnail" picture (a -miniature picture generated by the "VisualSchnauzer" +<p><b>xvminittoppm</b> reads an XV "thumbnail" picture (a +miniature picture generated by the "VisualSchnauzer" browser) as input and produces a PPM image as output. <H2 id="seealso">SEE ALSO</H2> diff --git a/ybmtopbm.html b/ybmtopbm.html index d55cc08b..a5e2b4f1 100644 --- a/ybmtopbm.html +++ b/ybmtopbm.html @@ -8,7 +8,7 @@ Updated: 06 March 1990 <A NAME="lbAB"> </A> <H2>NAME</H2> -ybmtopbm - convert a Bennet Yee "face" file to PBM +ybmtopbm - convert a Bennet Yee "face" file to PBM <A NAME="lbAC"> </A> <H2>SYNOPSIS</H2> |