"miscellaneous update"

git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@1013 9d0c8265-081b-0410-96cb-a4ca84ce46f8

3 files changed, 44 insertions, 32 deletions

diff --git a/jpeg2ktopam.html b/jpeg2ktopam.html
index daefeb41..087becf6 100644
--- a/jpeg2ktopam.html
+++ b/jpeg2ktopam.html
@@ -117,7 +117,7 @@ for general information on JPEG-2000 compression and the
 JPEG-2000 formats.
 
 
-<H2 kd="seealso">SEE ALSO</H2>
+<H2 id="seealso">SEE ALSO</H2>
 
 <B><A HREF="pamtojpeg2k.html">jpctopam</A></B>,
 <B><A HREF="jpegtopnm.html">pnmtopeg</A></B>,
diff --git a/pambayer.html b/pambayer.html
index c997fd17..f66af39b 100644
--- a/pambayer.html
+++ b/pambayer.html
@@ -15,6 +15,7 @@ pambayer - interpret Bayer patterns
 
 <B>pambayer</B>
 <b>-type=</b>{<b>1</b>|<b>2</b>|<b>3</b>|<b>4</b>}
+[<b>-nointerpolate</b>]
 [<I>pamfile</I>]
 
 <P>Minimum unique abbreviation of option is acceptable.  You may use
@@ -38,6 +39,16 @@ The pattern in which they are laid out is the Bayer pattern.  The
 input to <b>pambayer</b> is one sample value for each of those
 sensors, so some samples are red, some are green, and some are blue.
 
+<p><b>pambayer</b> turns that into a regular visual image with one pixel
+per sensor.  For the two components of each pixel that are missing in the
+corresponding Bayer input, <b>pambayer</b> averages the sample values from
+the adjacent pixels that do have that component.
+
+<p>But you can have <b>pambayer</b> fill in black instead (see the
+<b>-noninterpolate</b> option), which gives you a simpler representation of
+what the camera saw, on which you might do further processing.  Such an image
+still looks right, though considerably dimmer, if you stand far enough away
+and let your eyes do the interpolation.
 
 <p>The input image is a pseudo-PNM image (pseudo- because while the structure
 is the same, the sample values have different meanings) or PAM image of
@@ -56,7 +67,7 @@ a standard color image.  You can convert this to PPM with
 
 <DL COMPACT>
 
-<dt><b>type=</b><i>n</i>
+<dt><b>-type=</b><i>n</i>
 
 <dd>This tells which Bayer pattern the input is:
 
@@ -73,6 +84,16 @@ a standard color image.  You can convert this to PPM with
 
 This option is mandatory.
 
+<dt><b>-nointerpolate</b>
+
+<dd>Each output pixel position corresponds to one position in the input
+Bayer pattern, which means only one of the three color components is
+supplied by the input.  For the other two, this option says to user zero.
+Without it, <b>pambayer</b> instead interpolates from the adjacent pixels
+that do have that color component.
+
+<p>This option was new in Netpbm 10.49 (December 2009).
+
 </DL>
 
 
diff --git a/pbmtoascii.html b/pbmtoascii.html
index 2375c53e..0c62da46 100644
--- a/pbmtoascii.html
+++ b/pbmtoascii.html
@@ -6,12 +6,10 @@ Updated: 11 August 2002
 <BR>
 <A HREF="#index">Table Of Contents</A>
 
-<A NAME="lbAB">&nbsp;</A>
 <H2>NAME</H2>
 pbmtoascii - convert a PBM image to ASCII graphics
 
-<A NAME="lbAC">&nbsp;</A>
-<H2>SYNOPSIS</H2>
+<H2 id="synopsis">SYNOPSIS</H2>
 
 <B>pbmtoascii</B>
 
@@ -19,56 +17,49 @@ pbmtoascii - convert a PBM image to ASCII graphics
 
 [<I>pbmfile</I>]
 
-<A NAME="lbAD">&nbsp;</A>
-<H2>DESCRIPTION</H2>
+<H2 id="description">DESCRIPTION</H2>
 
 <p>This program is part of <a href="index.html">Netpbm</a>.
 
-<b>pbmtoascii</b> reads a PBM image as input and produces a somewhat
+<p><b>pbmtoascii</b> reads a PBM image as input and produces a somewhat
 crude ASCII graphic image as output.
 
 <P>To convert back, use <A HREF="asciitopgm.html">asciitopgm</A>.
 
-<A NAME="lbAE">&nbsp;</A>
-<H2>OPTIONS</H2>
+<H2 id="options">OPTIONS</H2>
 
-<p>The <B>-1x2</B> and <B>-2x4</B> options give you two alternate ways for
-the pixels to get mapped to characters.  With <B>1x2</B>, the default,
-each character represents a group of 1 pixel across by 2 pixels down.
-With <B>-2x4</B>, each character represents 2 pixels across by 4
-pixels down.  With the 1x2 mode you can see the individual pixels, so
-it's useful for previewing small images on a non-graphics terminal.
-The 2x4 mode lets you display larger images on a standard 80-column
-display, but it obscures pixel-level details.  2x4 mode is also good
-for displaying PGM images:
+<p>The <B>-1x2</B> and <B>-2x4</B> options give you two alternate ways for the
+pixels to get mapped to characters.  With <B>1x2</B>, the default, each
+character represents a group of 1 pixel across by 2 pixels down.  With
+<B>-2x4</B>, each character represents 2 pixels across by 4 pixels down.  With
+the 1x2 mode you can see the individual pixels, so it's useful for previewing
+small images on a non-graphics terminal.  The 2x4 mode lets you display larger
+images on a small display, but it obscures pixel-level details.  2x4 mode is
+also good for displaying PGM images:
 
 <pre>
-pamscale -width 158 | pnmnorm | pamditherbw -threshold
+pamscale -width 158 | pnmnorm | pamditherbw -threshold | pbmtoascii -2x4
 </pre>
 
 should give good results.
 
-<A NAME="lbAF">&nbsp;</A>
-<H2>SEE ALSO</H2>
+<H2 id="seealso">SEE ALSO</H2>
 
 <A HREF="asciitopgm.html">asciitopgm</A>
 <A HREF="pbm.html">pbm</A>
 
-<A NAME="lbAG">&nbsp;</A>
-<H2>AUTHOR</H2>
+<H2 id="author">AUTHOR</H2>
 
 Copyright (C) 1988, 1992 by Jef Poskanzer.
 
 <HR>
-<A NAME="index">&nbsp;</A>
-<H2>Table Of Contents</H2>
+<H2 id="index">Table Of Contents</H2>
 <UL>
-<LI><A HREF="#lbAB">NAME</A>
-<LI><A HREF="#lbAC">SYNOPSIS</A>
-<LI><A HREF="#lbAD">DESCRIPTION</A>
-<LI><A HREF="#lbAE">OPTIONS</A>
-<LI><A HREF="#lbAF">SEE ALSO</A>
-<LI><A HREF="#lbAG">AUTHOR</A>
+<LI><A HREF="#synopsis">SYNOPSIS</A>
+<LI><A HREF="#description">DESCRIPTION</A>
+<LI><A HREF="#options">OPTIONS</A>
+<LI><A HREF="#seealso">SEE ALSO</A>
+<LI><A HREF="#author">AUTHOR</A>
 </UL>
 </BODY>
 </HTML>