diff options
44 files changed, 73 insertions, 73 deletions
diff --git a/index.html b/index.html index 5ebd347f..6f527181 100644 --- a/index.html +++ b/index.html @@ -658,7 +658,7 @@ still GIF, and you can use <B>pamtogif</B> and <B>giftopnm</B> to connect up to all the Netpbm utilities. See <B><A HREF="http://www.lcdf.org/gifsicle">http://www.lcdf.org/gifsicle</A></B>. -<P>To convert an image of text to text (optical character recongition +<P>To convert an image of text to text (optical character recognition - OCR), use <B>gocr</B> (think of it as an inverse of <B>pbmtext</B>). See <B> <a href="http://jocr.sourceforge.net/">http://jocr.sourceforge.net/</a></b>. @@ -689,7 +689,7 @@ transform the image, then compress it back to JPEG format. In that recompression, you lose a little image information because JPEG is a lossy compression. Of course, only a few kinds of lossless transformation are possible. <B>jpegtran</B> comes with the -Independent Jpeg Group's (<A +Independent JPEG Group's (<A HREF="http://www.ijg.org">http://www.ijg.org)</A> JPEG library. <P> Some tools to deal with EXIF files (see also Netpbm's <B><a @@ -851,7 +851,7 @@ understand this format, starting with Windows 7 and Internet Explorer 9, along with many other programs. This format was previously known as Windows Media Photo and HD Photo. -<li>Direct Draw Surface (DDS)is the de factor standard wrapper format for S3 +<li>Direct Draw Surface (DDS)is the de facto standard wrapper format for S3 texture compression, as used in all modern realtime graphics applications. Besides Windows-based tools, there is a <b>Gimp</b> plugin for this format. @@ -929,7 +929,7 @@ for the fact that it is very similar to Netpbm formats and uses the 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 simlar YUV 4:4:4, YUV 4:2:2, +<li>YUV 4:2:0, aka YUV 420, and the similar YUV 4:4:4, YUV 4:2:2, YUV 4:1:1, YUV 4:1:1s, and YUV 4:1:0. Video systems often use this. <li><a href="http://en.wikipedia.org/wiki/MJPEG">MJPEG</a> movie @@ -940,7 +940,7 @@ the Netpbm formats for still images. You use it for manipulating movies, but not for storing or transmitting them. The only known use of the format is with <a href="mjpeg.sourceforge.net"><b>MJPEGTools</b></a>. The programs -<b>pnmtoy4m</b> and <b>y4mtopnm</b> (and predecesors <b>ppmtoy4m</b> +<b>pnmtoy4m</b> and <b>y4mtopnm</b> (and predecessors <b>ppmtoy4m</b> and <b>y4mtoppm</b>) in that package convert between a Netpbm stream and a YUV4MPEG2 stream. As you might guess from the name, YUV4MPEG2 uses a YUV representation of data, which is more convenient than the diff --git a/libnetpbm_draw.html b/libnetpbm_draw.html index 39543dfc..cb7f16cc 100644 --- a/libnetpbm_draw.html +++ b/libnetpbm_draw.html @@ -73,7 +73,7 @@ ends in ".ppmdfont". Ppmdfont file in human readable format. <p>Use the <b>ppmdmkfont</b> program to generate the "standard" -font as a Ppmdfont file. You don't normally need to do this, becuase +font as a Ppmdfont file. You don't normally need to do this, because "standard" is built into <b>libnetpbm</b>. <p>Use the <b>ppmdcfont</b> program to turn a Ppmdfont file into a C diff --git a/libnetpbm_image.html b/libnetpbm_image.html index 858f0706..589bdeea 100644 --- a/libnetpbm_image.html +++ b/libnetpbm_image.html @@ -69,7 +69,7 @@ image's maxval. <dt>tuplen <dd>The same as <b>tuple</b>, except composed of normalized samples -(<b>samplen</b>) intead of regular samples (<b>sample</b>). +(<b>samplen</b>) instead of regular samples (<b>sample</b>). </dl> diff --git a/libnetpbm_ug.html b/libnetpbm_ug.html index aa119589..72be3d61 100644 --- a/libnetpbm_ug.html +++ b/libnetpbm_ug.html @@ -152,13 +152,13 @@ this is the conventional behavior of Netpbm programs. <DD>This is a boolean value (0 = false, 1 = true), meaningful only when writing an image file. It means to write in the plain (text) -version of the format indicated by <b>format</b> as oppposed to the +version of the format indicated by <b>format</b> as opposed to the raw (binary) version. Note that the format code in <b>format</b> would appear to completely specify the format, making <b>plainformat</b> redundant. But see the description of <b>format</b> for why that isn't true. <p> -Until Netpbm 10.32 (Februrary 2006), this was defined a little differently. +Until Netpbm 10.32 (February 2006), this was defined a little differently. The <b>format</b> member did in fact completely identify the format and <b>plainformat</b> was redundant and existed as a separate member only for computational speed. But this was inconsistent with the older diff --git a/pamaddnoise.html b/pamaddnoise.html index 48a8413a..772d18a0 100644 --- a/pamaddnoise.html +++ b/pamaddnoise.html @@ -105,7 +105,7 @@ a plane of colors in a color space. <DT><B>-mgsigma</b> <i>value</i> -<DD>Used for mutliplicative gaussian noise only. The default value is +<DD>Used for multiplicative gaussian noise only. The default value is 0.5. <DT><B>-seed</b> <i>int</i> @@ -138,7 +138,7 @@ type option. The default noise type is <b>gaussian</b>. <ul> <li><b>gaussian</b> -<li><b>mulitiplicative_gaussian</b> +<li><b>multiplicative_gaussian</b> <li><b>impulse</b> <li><b>laplacian</b> <li><b>poisson</b> diff --git a/pamlookup.html b/pamlookup.html index fb938a88..51525db7 100644 --- a/pamlookup.html +++ b/pamlookup.html @@ -178,7 +178,7 @@ option has no effect. <h3>Example: rainfall map</h3> <p>Say you have a set of rainfall data in a single plane PAM image. -The rows and columns of the PAM indicate lattitude and longitude. The +The rows and columns of the PAM indicate latitude and longitude. The sample values are the annual rainfall in (whole) centimeters. The highest rainfall value in the image is 199 centimeters. The image is in the file rainfall.pam. diff --git a/pammasksharpen.html b/pammasksharpen.html index eae11970..45eb097a 100644 --- a/pammasksharpen.html +++ b/pammasksharpen.html @@ -55,7 +55,7 @@ as the input image. <h3>The Unsharp Mask</h3> -<p>You usually create the unsharp mask as a gaussian blur of the +<p>You usually create the unsharp mask as a Gaussian blur of the original image, which you can do using <b>pamgauss</b> and <b>pnmconvol</b> as in the example above. The convolution kernel you use with <b>pnmconvol</b> is normally a square with side length an odd diff --git a/pamscale.html b/pamscale.html index 083e348f..75dae3d9 100644 --- a/pamscale.html +++ b/pamscale.html @@ -2,7 +2,7 @@ <HTML><HEAD><TITLE>Pamscale User Manual</TITLE></HEAD> <BODY> <H1>pamscale</H1> -Updated: 29 Deceber 2009 +Updated: 29 December 2009 <BR> <A HREF="#index">Table Of Contents</A> @@ -586,7 +586,7 @@ original code remains. <LI><A HREF="#methods">Methods Of Scaling</a> <UL> <LI><A HREF="#mixing">Pixel Mixing</a> - <LI><A HREF="#sampling">Discreate Sampling</a> + <LI><A HREF="#sampling">Discrete Sampling</a> <LI><A HREF="#resampling">Resampling</a> </UL> <LI><A HREF="#linear">Linear vs Gamma-adjusted</a> diff --git a/pamsharpness.html b/pamsharpness.html index 9c9100f3..1b6e8958 100644 --- a/pamsharpness.html +++ b/pamsharpness.html @@ -2,7 +2,7 @@ <HTML><HEAD><TITLE>Pamsharpness User Manual</TITLE></HEAD> <BODY> <H1>pamsharpness</H1> -Updated: 07 Februrary 2004 +Updated: 07 February 2004 <BR> <A HREF="#index">Table Of Contents</A> diff --git a/pamsplit.html b/pamsplit.html index ab5dff9b..69471a91 100644 --- a/pamsplit.html +++ b/pamsplit.html @@ -37,7 +37,7 @@ 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 specification of the output file, except that the first -occurence 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. diff --git a/pamstereogram.html b/pamstereogram.html index b035b60c..bf831f16 100644 --- a/pamstereogram.html +++ b/pamstereogram.html @@ -377,7 +377,7 @@ href="http://dx.doi.org/10.1109/2.318576">10.1109/2.318576</a>.</li> <h2><a id="history">HISTORY</a></h2> <p><b>pamstereogram</b> was new in Netpbm 10.22 (April 2004), but probably broken beyond usability until -Netpbm 10.32 (Februrary 2006) and Netpbm 10.26.23 (January 2006).</p> +Netpbm 10.32 (February 2006) and Netpbm 10.26.23 (January 2006).</p> <h2><a id="author">AUTHOR</a></h2> diff --git a/pamtodjvurle.html b/pamtodjvurle.html index e893a824..48428a4f 100644 --- a/pamtodjvurle.html +++ b/pamtodjvurle.html @@ -17,7 +17,7 @@ pamtodjvurle - convert a Netpbm image to DjVu Color RLE format [<b>-transparent</b> <i>color</i>] [<I>netpbmfile</I> [<I>rlefile</I>]] -<p>Mininum unique abbreviation of options in acceptable. +<p>Minimum unique abbreviation of options in acceptable. <H2 id="description">DESCRIPTION</H2> diff --git a/pamtogif.html b/pamtogif.html index 38760834..9c51d2fa 100644 --- a/pamtogif.html +++ b/pamtogif.html @@ -140,7 +140,7 @@ library routine</a>. <p>If the color you specify is not present in the image, <B>pamtogif</B> selects instead the color in the image that is closest to the one you -specify. Closeness is measured as a cartesian distance between colors +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. @@ -317,7 +317,7 @@ function in October 2001: the ability to generate a GIF without using the LZW patent -- an uncompressed GIF. This was very important to many people at the time because the GIF patent was still in force, and this allowed them to make an image that any GIF viewer could display, -royalty-free. Bryan adapted code from the Independent Jpeg Group's +royalty-free. Bryan adapted code from the Independent JPEG Group's <b>djpeg</b> for that. <p>There is no code in <b>pamtogif</b> from Jef's original, but Jef diff --git a/pamtojpeg2k.html b/pamtojpeg2k.html index 52f0a678..c5e07b24 100644 --- a/pamtojpeg2k.html +++ b/pamtojpeg2k.html @@ -60,8 +60,8 @@ specifically, whereas JPC is a more or less arbitrary array of codes. <B>pamtojpeg2k</B> can't produce a JP2, but the JPC image that <b>pamtojpeg2k</b> produces is very similar to a JP2 if the input is a PBM, PGM, or PPM image or equivalent PAM image. One difference is -that that RGB intensity values in a JP2 are SRGB values, while -<b>pamtojpeg2k</b> produces ITU-R Recommedation BT.709 values. Those +that the RGB intensity values in a JP2 are SRGB values, while +<b>pamtojpeg2k</b> produces ITU-R Recommendation BT.709 values. Those are very similar, but not identical. Another difference is that a JP2 can contain extra information about an image that JPC cannot. diff --git a/pamtotiff.html b/pamtotiff.html index a490a90d..f07d2276 100644 --- a/pamtotiff.html +++ b/pamtotiff.html @@ -309,7 +309,7 @@ equal sign) depends upon what kind of value the tag type has: <li>Enumerated (For example, a 'subfiletype' tag takes an enumerated value. Its possible values are REDUCEDIMAGE, PAGE, and MASK.): The name of the value. You can see the possible value names in the TIFF -library's <b>tiff.h</b> foile, where there is a macro defined for each +library's <b>tiff.h</b> file, where there is a macro defined for each consisting of a qualifier plus the value name. E.g. for the REDUCEDIMAGE value of a SUBFILETYPE tag, you see the macro FILETYPE_REDUCEDIMAGE. @@ -381,7 +381,7 @@ or GRAYSCALE (and doesn't distinguish between those two). type RGB except with that number of planes instead of 3. <b>pamtotiff</b> doesn't really understand red, green, and blue, so it has no trouble with a 2-component or 5-component color space. The -TIFF format allows an arbitrary number of color compoonents, so +TIFF format allows an arbitrary number of color components, so <b>pamtotiff</b> simply maps the PAM planes directly to TIFF color components. I don't know if the meanings of 5 components in a TIFF image are standard at all, but the function is there if you want to use it. diff --git a/pbmtext.html b/pbmtext.html index 0ca8dc9e..38dc2c89 100644 --- a/pbmtext.html +++ b/pbmtext.html @@ -259,7 +259,7 @@ use a graphical editor such as ImageMagick). Finally, run it through <h2 id="nonenglish">NON-ENGLISH TEXT</h2> -<p><b>pbmtext</b> does little to accomodate the special needs of non-English +<p><b>pbmtext</b> does little to accommodate the special needs of non-English text. <p><b>pbmtext</b> reads input in byte units. Unicode (utf-7, utf-8, utf-16, @@ -280,7 +280,7 @@ environment variables. <p>If you get garbled output, check whether the font file encoding corresponds to the input text encoding. Also make sure that your input is not in utf-* or -any other mutli-byte format. +any other multi-byte format. <p>To dump characters in a BDF font file run this command: diff --git a/pbmtopgm.html b/pbmtopgm.html index f68dfcad..487c3348 100644 --- a/pbmtopgm.html +++ b/pbmtopgm.html @@ -42,7 +42,7 @@ contain distinct line features. <P>You don't need <B>pbmtopgm</B> just to use a PGM program on a PBM image. Any PGM program (assuming it uses the Netpbm libraries to read the PGM input) takes PBM input as if it were PGM, with only the -mininum and maximum gray levels. So unless your convolution rectangle +minimum and maximum gray levels. So unless your convolution rectangle is bigger than one pixel, you're not gaining anything with a <B>pbmtopgm</B> step. diff --git a/pbmtoppa.html b/pbmtoppa.html index 7e82c95a..f2ccf119 100644 --- a/pbmtoppa.html +++ b/pbmtoppa.html @@ -238,7 +238,7 @@ as small as 1/4 inch without causing the printer to choke with same should work for the 820 and 1000, but it hasn't been tested. Also, use the pbmraw GSDriver if you have it; it's faster. -<P>Here is a tip to intergrate HP720C support in RedHat's printtool: +<P>Here is a tip to integrate HP720C support in RedHat's printtool: <P>Install pbmtoppa. Copy pbmtoppa to /usr/bin. @@ -257,7 +257,7 @@ StartEntry: DeskJet720C It does does not support color printing. \ IMPORTANT! Insert \ "- | pbm2ppa -" \ - in the "Extra GS Otions" field.\ + in the "Extra GS Options" field.\ } Resolution: {600} {600} {} diff --git a/pgm.html b/pgm.html index f42c15fa..d75c9ef3 100644 --- a/pgm.html +++ b/pgm.html @@ -24,7 +24,7 @@ It is designed to be extremely easy to learn and write programs for. because it's easier than reading this specification). <P>A PGM image represents a grayscale graphic image. There are many -psueudo-PGM formats in use where everything is as specified herein except +pseudo-PGM formats in use where everything is as specified herein except for the meaning of individual pixel values. For most purposes, a PGM image can just be thought of an array of arbitrary integers, and all the programs in the world that think they're processing a grayscale image diff --git a/pgmabel.html b/pgmabel.html index 87f64b42..cb53ea52 100644 --- a/pgmabel.html +++ b/pgmabel.html @@ -44,7 +44,7 @@ by the surface area of the calculated ring in square pixels divided by With the <b>-verbose</b> option, <b>pgmabel</b> prints the weighting factors. -<P>Where the caculation generates a negative result, the output is black. +<P>Where the calculation generates a negative result, the output is black. <P>The computation is unstable against periodic structures with size 2 in the vertical direction. diff --git a/pnmdepth.html b/pnmdepth.html index f0ff2048..0ca740e5 100644 --- a/pnmdepth.html +++ b/pnmdepth.html @@ -13,7 +13,7 @@ pnmdepth - change the maxval in a PNM image <p>This program is part of <a href="index.html">Netpbm</a>. -<P>Starting with Netpbm 10.32 (Februrary 2006), <b>pnmdepth</b> is +<P>Starting with Netpbm 10.32 (February 2006), <b>pnmdepth</b> is obsolete. Use <a href="pamdepth.html"><b>pamdepth</b></a> instead. <b>pamdepth</b> is backward compatible with <b>pnmdepth</b>. You can diff --git a/pnmgamma.html b/pnmgamma.html index 003599f3..574d7d9e 100644 --- a/pnmgamma.html +++ b/pnmgamma.html @@ -59,7 +59,7 @@ where the sample values represent intensity in different ways: to radiance (often called "linear intensity"). <p>Another popular variation is to make the samples proportional to -luminance as defined by the Internation Electrotechnical Commission +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. diff --git a/pnmhistmap.html b/pnmhistmap.html index 8b9fa852..b79cecf9 100644 --- a/pnmhistmap.html +++ b/pnmhistmap.html @@ -123,7 +123,7 @@ the dimensions were always what the default is today. <P>The -black and -white options, which can be used separately or together, are useful for images with a large percentage of pixels whose value is zero or 255, which can cause the remaining histogram -data to become unreadbaly small. Note that, for color inputs, these +data to become unreadably small. Note that, for color inputs, these options apply to all colors; if, for example, the input has a large number of bright-red areas, you will probably want to use the -white option. diff --git a/pnmindex.html b/pnmindex.html index 220495c8..b0b1d53a 100644 --- a/pnmindex.html +++ b/pnmindex.html @@ -86,7 +86,7 @@ Default is no title. <DT><B>-quant</B> -<DD>Enables quanization (to the number of colors specified by +<DD>Enables quantization (to the number of colors specified by <B>-colors</B>). Quantization is on by default but you can disable it with <B>-noquant.</B> diff --git a/pnmnorm.html b/pnmnorm.html index 738987bb..8c025984 100644 --- a/pnmnorm.html +++ b/pnmnorm.html @@ -107,15 +107,15 @@ decimal. Zero is valid and is the same as <b>-bvalue=0</b> or <b>-wvalue=</b><i>maxval</i>, respectively. <p>Because there are whole numbers of pixels at each brightness, -<b>pnmnorm</b> obviously can't guarantee the exact per centage, so it -arranges that <em>at least</em> the per centage of pixels you specify +<b>pnmnorm</b> obviously can't guarantee the exact percentage, so it +arranges that <em>at least</em> the percentage of pixels you specify get remapped as promised. <p>It is possible for your <b>-bpercent</b> or <b>-wpercent</b> to overlap your <b>-wvalue</b> or <b>-bvalue</b>, respectively. For example, you say <b>-bpercent=20</b> and <b>-wvalue=100</b> for an -image in which only 10 per cent of the pixels are darker than 100. -In that case, <b>pnmnorm</b> adjusts the per centile value as +image in which only 10 percent of the pixels are darker than 100. +In that case, <b>pnmnorm</b> adjusts the percentile value as required. In the example, it uses 99 as the black value (like <b>-bvalue=99</b>). @@ -144,7 +144,7 @@ intensity by 4 units now differ by 10, and that might be unsightly. <p>So that you can put a limit on the amount of expansion without having to examine the image first, there is the <b>-maxexpand</b> option. It specifies the maximum expansion you will tolerate, as an -additional per centage. In the example above, you could say +additional percentage. In the example above, you could say <b>-maxexpand=50</b> to say you want the range to expand by at most 50%, regardless of your other options. <b>pnmnorm</b> figures out what intensity to stretch to full intensity and what intensity to diff --git a/pnmremap.html b/pnmremap.html index d6dc1284..15ade98a 100644 --- a/pnmremap.html +++ b/pnmremap.html @@ -66,9 +66,9 @@ to something that can handle only certain colors. <p>By default, <b>pnmremap</b> maps an input color that is not in the palette to the closest color that <em>is</em> in the palette. Closest -means with the smallest cartesian distance in the red, green, blue +means with the smallest Cartesian distance in the red, green, blue brightness space (smallest sum of the squares of the differences in -red, green, and blue ITU-R Recommedation BT.709 gamma-adjusted +red, green, and blue ITU-R Recommendation BT.709 gamma-adjusted intensities). <p>You can instead specify a single default color for <b>pnmremap</b> @@ -207,7 +207,7 @@ unmodified quantization has banding or other artifacts, especially when going to a small number of colors such as the above IBM set. However, it does take substantially more CPU time. -<P><B>-fs</B> is a synomym for <B>-floyd</B>. <B>-nofs</B> is a +<P><B>-fs</B> is a synonym for <B>-floyd</B>. <B>-nofs</B> is a synonym for <B>-nofloyd</B>. <P>The default is <B>-nofloyd</B>. diff --git a/pnmrotate.html b/pnmrotate.html index 378edb05..922ec883 100644 --- a/pnmrotate.html +++ b/pnmrotate.html @@ -84,7 +84,7 @@ library routine</a>. <p>By default, if you don't specify this option, <b>pnmrotate</b> selects what appears to it to be the background color of the original image. It -determines this color rather simplisticly, by taking an average of the colors +determines this color rather simplistically, by taking an average of the colors of the two top corners of the image. <p>This option was new in Netpbm 10.15. Before that, <b>pnmrotate</b> diff --git a/pnmshear.html b/pnmshear.html index e72b24a8..f1ee9003 100644 --- a/pnmshear.html +++ b/pnmshear.html @@ -74,7 +74,7 @@ library routine</a>. <p>By default, if you don't specify this option, <b>pnmshear</b> selects what appears to it to be the background color of the original image. It -determines this color rather simplisticly, by taking an average of the colors +determines this color rather simplistically, by taking an average of the colors of the two top corners of the image. <p>This option was new in Netpbm 10.37 (December 2006). Before that, diff --git a/pnmtojpeg.html b/pnmtojpeg.html index 56a475b1..6dd99ef3 100644 --- a/pnmtojpeg.html +++ b/pnmtojpeg.html @@ -473,7 +473,7 @@ not be 0. 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". <P> -In an entry for an AC coeffient, you must specify only one color +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 @@ -482,7 +482,7 @@ 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 coefficent +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 the bits of the DC coefficient, or any of the AC coefficients. diff --git a/pnmtopalm.html b/pnmtopalm.html index 45fdd355..94aa6ffa 100644 --- a/pnmtopalm.html +++ b/pnmtopalm.html @@ -89,7 +89,7 @@ the options you specify. any compression, the version is at least 2. <li>If you specify a custom colormap (<b>-colormap</b> option), the -verison is at least 1. +version is at least 1. <li>If the image has more than one bit per pixel, the version is at least 1. The image has more than one bit per pixel if you specify it with @@ -170,7 +170,7 @@ images. <p>This dummy image header is a special sequence specified in Palm Bitmap specifications. It looks to an older Palm Bitmap interpreter like an invalid -image header, so such an intepreter will stop reading the stream +image header, so such an interpreter will stop reading the stream there. But a new Palm Bitmap interpreter recognizes it for what it is (just something to choke an old interpreter) and skips over it. Presumably, you will add to the stream after this high density images which would diff --git a/pnmtopclxl.html b/pnmtopclxl.html index 1516d508..c14a73b4 100644 --- a/pnmtopclxl.html +++ b/pnmtopclxl.html @@ -82,7 +82,7 @@ determined by <b>-xoffs</b> and <b>-yoffs</b> (or their defaults). <dt><b>-duplex</b> {<b>vertical</b>|<b>horizontal</b>} <dd>This option causes <b>pnmtopclxl</b> to create a printer stream that prints pages -on boths sides of the sheet of paper. <b>vertical</b> means to print +on both sides of the sheet of paper. <b>vertical</b> means to print them so that the left edge of both pages is on the same edge of the sheet, while <b>horizontal</b> means the more usual duplexing where the top of both pages is on the same edge of the sheet. @@ -146,7 +146,7 @@ faster even if the image is grayscale anyway. <dt><b>-jobsetup=</b><i>filename</i> -<dd>This option causes <b>pnmtopclxl</b> to include arbitary job setup +<dd>This option causes <b>pnmtopclxl</b> to include arbitrary job setup PJL commands at the beginning of the output stream. It reads them from the named file. diff --git a/pnmtopng.html b/pnmtopng.html index ce424138..4440a921 100644 --- a/pnmtopng.html +++ b/pnmtopng.html @@ -163,7 +163,7 @@ library routine</a>. E.g. <B>red</B> or <B>rgb:ff/00/0d</B>. If the color you specify is not present in the image, <B>pnmtopng</B> selects instead the color in the image that is -closest to the one you specify. Closeness is measured as a cartesian +closest to the one you specify. Closeness is measured as a Cartesian distance between colors in RGB space. If multiple colors are equidistant, <B>pnmtopng</B> chooses one of them arbitrarily. diff --git a/pnmtops.html b/pnmtops.html index eddafc75..ffd4e772 100644 --- a/pnmtops.html +++ b/pnmtops.html @@ -54,7 +54,7 @@ image through <B>ppmtopgm</B> first. <P>If you specify no output dimensioning options, the output image is dimensioned as if you had specified <B>-scale=1.0</B>, which means -aproximately 72 pixels of the input image generate one inch of output +approximately 72 pixels of the input image generate one inch of output (if that fits the page). <P>Use <B>-imagewidth</B>, <B>-imageheight</B>, <B>-equalpixels</B>, @@ -68,7 +68,7 @@ Postscript stream; someone who knows Postscript should work on this). 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 implmented. The Postscript language level is in the +EPS specification implemented. The Postscript language level is in the "%%LanguageLevel:" comment. <b>pnmtops</b> omits "EPSF-3.0" if you specify <b>-setpage</b>, because it is incorrect to claim EPS compliance if the file uses <b>setpagedevice</b>. @@ -258,7 +258,7 @@ forum about Postscript</a>, extracted in October 2010. Jef added -rle in August 1988. In those days, RS-232 lines (referred to a "serial" in the quotation) were typically 9600bps. 2400 bps lines were still around. What the quotation calls "the network" is probably a 10 Mbps -ethernet connection. +Ethernet connection. <dt><b>-flate</b> diff --git a/ppm3d.html b/ppm3d.html index 8c6b0937..08a5623c 100644 --- a/ppm3d.html +++ b/ppm3d.html @@ -47,7 +47,7 @@ due to the fact that each eye necessarily cannot see the entire spectrum. Red and cyan don't work well, but most other colors -- especially when heavily saturated -- come out quite well. -<p>To view a color analgyph stereogram, you need glasses with a left +<p>To view a color anaglyph stereogram, you need glasses with a left lens that admits only red light and a right lens that admits only blue and green light. (The right lens may be called a cyan lens because that is its pigment in white light; don't be misled into thinking that @@ -59,7 +59,7 @@ if you were looking at the combined light with both eyes. <P>The input PPMs must be the same dimensions. <p>To make a different kind of stereogram, use <b>pamstereogram</b>. -That makes a steregram that you view without special glasses, just by +That makes a stereogram that you view without special glasses, just by letting your eyes unfocus so that each eye sees different parts of the image. diff --git a/ppmchange.html b/ppmchange.html index 38ace9b4..f89b3036 100644 --- a/ppmchange.html +++ b/ppmchange.html @@ -40,7 +40,7 @@ ppmchange - change all pixels of one color to another in a PPM image <p>This program is part of <a href="index.html">Netpbm</a>. <p><b>ppmchange</b> reads a PPM image as input and changes all pixels of -colr <I>oldcolor</I> to color <I>newcolor</I>. +color <I>oldcolor</I> to color <I>newcolor</I>. You may specify up to 256 oldcolor/newcolor pairs on the command line. <B>ppmchange</B> leaves all colors not mentioned unchanged, unless you @@ -83,7 +83,7 @@ option. <DL COMPACT> <DT><B>-closeness </B><I>closeness_percent</I> -<DD><I>closeness</I> is an integer per centage indicating how close +<DD><I>closeness</I> is an integer percentage indicating how close to the color you specified a pixel must be to get replaced. By default, it is 0, which means the pixel must be the exact color you specified. @@ -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/ppmdraw.html b/ppmdraw.html index 14317386..d74770e2 100644 --- a/ppmdraw.html +++ b/ppmdraw.html @@ -184,7 +184,7 @@ are: starting column, starting row, ending column, ending row. <dd>This is like <b>line</b>, except it works in a more relative way. <p>The line starts at the current point. The two arguments are the -rightward and downard displacement from there of the terminal point. +rightward and downward displacement from there to the terminal point. The command moves the current position to the terminal point after drawing. <dt>spline3 diff --git a/ppmtolj.html b/ppmtolj.html index 3d44df18..dc366314 100644 --- a/ppmtolj.html +++ b/ppmtolj.html @@ -54,7 +54,7 @@ ESC&l0E to the output. <DT><B>-noreset</B> <DD> -Don't write the reset sequence to the begining and end of the output. +Don't write the reset sequence to the beginning and end of the output. <DT><B>-resolution</B> diff --git a/ppmtopj.html b/ppmtopj.html index c518a358..c07c1d96 100644 --- a/ppmtopj.html +++ b/ppmtopj.html @@ -81,7 +81,7 @@ Run length encode the image. <DD> Enhance the foreground by indicating if the background is light or -dark compated to the foreground. +dark compared to the foreground. <DT><B>-render</B> <I>alg</I> diff --git a/ppmtoppm.html b/ppmtoppm.html index 99f0979c..01a66623 100644 --- a/ppmtoppm.html +++ b/ppmtoppm.html @@ -4,7 +4,7 @@ <BODY> <H1>ppmtoppm</H1> -Updated: Feburary 2007 +Updated: February 2007 <BR> <A HREF="#index">Table Of Contents</A> diff --git a/ppmtoterm.html b/ppmtoterm.html index 21466ec0..0e4b8361 100644 --- a/ppmtoterm.html +++ b/ppmtoterm.html @@ -26,7 +26,7 @@ name and its value with white space instead of an equals sign. <P>This program tries to produce an accurate representation of a PPM image on an terminal that implements the ANSI ISO 6429 standard. It -aproximates colors, finding the minimum cartesian distance between the +approximates colors, finding the minimum Cartesian distance between the input RGB vectors and the ones in the generated palette. As the available color palette is somewhat restricted, you get the best results when the colors in the original image are few and the RGB @@ -54,7 +54,7 @@ to shift the image up or down, for example to center it, use <b>pnmpad</b> on the input. <P>This program was born with the objective of displaying nice color -images on the linux console, e.g. a proper logo at Linux boot. +images on the Linux console, e.g. a proper logo at Linux boot. <p><b>pbmto4425</b> does a similar thing for black and white images, using line drawing characters, on some terminals. diff --git a/ppmtowinicon.html b/ppmtowinicon.html index e8a5c991..14aa9b11 100644 --- a/ppmtowinicon.html +++ b/ppmtowinicon.html @@ -68,9 +68,9 @@ black in those areas, and in that case the areas are fully transparent -- the background shows through the icon. But in general, a not opaque pixel signifies that the background and foreground should be merged as follows: The intensities of the color components in the -forgeground and background are represented as binary numbers, then +foreground and background are represented as binary numbers, then corresponding bits of the background and foreground intensities are -exlusive-or'ed together. So there is a sort of reverse video effect. +exclusive-or'ed together. So there is a sort of reverse video effect. <p>If you don't want this special effect and instead want straightforward transparency, use the <b>-truetransparent</b> option. diff --git a/pstopnm.html b/pstopnm.html index b7dde802..0b0e8249 100644 --- a/pstopnm.html +++ b/pstopnm.html @@ -204,7 +204,7 @@ case. In this case, <b>pstopnm</b> first chooses an output device resolution that would generate the number of pixels indicated by <b>-xmax</b> and <b>-ymax</b> from the bordered subject image. Then, based on that resolution, it chooses an output image size that is just -large enough to accomodate the subject image (no borders). Remember +large enough to accommodate the subject image (no borders). Remember (above) that <b>pstopnm</b> trims the edges of the bordered subject image to fit the computed output size. diff --git a/rawtopgm.html b/rawtopgm.html index 18e29775..a083b82d 100644 --- a/rawtopgm.html +++ b/rawtopgm.html @@ -124,7 +124,7 @@ resulting image is upside down, which you can correct with <B>pamflip</B>. <P>This option causes <B>rawtopgm</B> to read the entire input stream -into storage at once, which may take a lot of storage. Ordinarly, +into storage at once, which may take a lot of storage. Normally, <B>rawtopgm</B> stores only one row at a time. <P>For backwards compatibility, <B>rawtopgm</B> also accepts <B>-tb diff --git a/sunicontopnm.html b/sunicontopnm.html index af09348c..3e995a73 100644 --- a/sunicontopnm.html +++ b/sunicontopnm.html @@ -35,9 +35,9 @@ convert the PGM output to the proper color Netpbm image. <h2 id="sunicons">ABOUT SUN ICONS</h2> -<p>It seems that this icon format was used in Sunview and were usable in it +<p>It seems that this icon format was used in Sunview and was usable in its successor Openlook/Openwindows in Sun 4.1.1, which offered backward -compatibilty for Sunview, including the icons. Sunview's desktop was +compatibility for Sunview, including the icons. Sunview's desktop was monochrome. OpenWindows had color icons. Sun 4 came with OpenWindows. OpenWindows appears to have been an X-based gui so presumably the icons were mostly XPM files. |