summary refs log tree commit diff
diff options
context:
space:
mode:
authorgiraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>2020-03-22 01:54:12 +0000
committergiraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>2020-03-22 01:54:12 +0000
commit895e9c3897d592b7df1c579a9522185c826c3a36 (patch)
tree2dec329e3a6ab73aaac39b52a0acde8ea32e0f64
parentd9bbf089cc1180650c6222cc4ce98c89c9ccb8b9 (diff)
downloadnetpbm-mirror-895e9c3897d592b7df1c579a9522185c826c3a36.tar.gz
netpbm-mirror-895e9c3897d592b7df1c579a9522185c826c3a36.tar.xz
netpbm-mirror-895e9c3897d592b7df1c579a9522185c826c3a36.zip
miscellaneous update
git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@3769 9d0c8265-081b-0410-96cb-a4ca84ce46f8
-rw-r--r--pamcut.html23
-rw-r--r--pamditherbw.html2
-rw-r--r--pnmshear.html8
3 files changed, 17 insertions, 16 deletions
diff --git a/pamcut.html b/pamcut.html
index 9f0666c8..c0016b37 100644
--- a/pamcut.html
+++ b/pamcut.html
@@ -87,18 +87,17 @@ read, more expressive, and allow you to use defaults.
 <P>If you use both options and arguments, the two specifications get
 mixed in an unspecified way.
 
-<P>To use arguments, specify all four of the <I>left</I>,
-<I>top</I>, <I>width</I>, and <I>height</I> arguments.  <I>left</I>
-and <I>top</I> have the same effect as specifying them as the argument
-of a <B>-left</B> or <B>-top</B> option, respectively.  <I>width</I>
-and <I>height</I> have the same effect as specifying them as the
-argument of a <B>-width</B> or <B>-height</B> option, respectively,
-where they are positive.  Where they are not positive, they have the
-same effect as specifying one less than the value as the argument to a
-<B>-right</B> or <B>-bottom</B> option, respectively.  (E.g.
-<I>width</I> = 0 makes the cut go all the way to the right edge).
-Before July 2000, negative numbers were not allowed for <I>width</I>
-and <I>height</I>.
+<P>To use arguments, specify all four of the <I>left</I>, <I>top</I>,
+<I>width</I>, and <I>height</I> arguments.  <I>left</I> and <I>top</I> have
+the same effect as specifying them as the argument of a <B>-left</B> or
+<B>-top</B> option, respectively.  <I>width</I> and <I>height</I> have the
+same effect as specifying them as the argument of a <B>-width</B> or
+<B>-height</B> option, respectively, where they are positive.  Where they are
+not positive, they have the same effect as specifying one less than the value
+as the argument to a <B>-right</B> or <B>-bottom</B> option, respectively.
+(E.g. <I>width</I> = 0 makes the cut go all the way to the right edge).
+Before July 2000, negative numbers were not allowed for <I>width</I> and
+<I>height</I>.
 
 <P>Input is from Standard Input if you don't specify the input file
 <I>pnmfile</I>.
diff --git a/pamditherbw.html b/pamditherbw.html
index c1f0bacf..5491a6f1 100644
--- a/pamditherbw.html
+++ b/pamditherbw.html
@@ -47,7 +47,7 @@ just takes the first channel of whatever you give it and treats it as
 if it represented gray levels).
 
 <p>The output is a PAM with tuple type BLACKANDWHITE.  You can turn
-this into a PBM (if you need to use it with an older program doesn't
+this into a PBM (if you need to use it with an older program that doesn't
 understand PAM) with <b>pamtopnm</b>.
 
 <P>To do the opposite of dithering, you can usually just scale the image
diff --git a/pnmshear.html b/pnmshear.html
index 4ff36304..abdff36f 100644
--- a/pnmshear.html
+++ b/pnmshear.html
@@ -2,7 +2,7 @@
 <HTML><HEAD><TITLE>Pnmshear User Manual</TITLE></HEAD>
 <BODY>
 <H1>pnmshear</H1>
-Updated: 27 November 2006
+Updated: 22 March 2020
 <BR>
 <A HREF="#index">Table Of Contents</A>
 
@@ -48,8 +48,10 @@ If the angle is negative, it shears the other way:
     +-------+  +-------+
 </PRE>
 
-The angle should not get too close to 90 or -90, or the resulting
-image will be unreasonably wide.
+The angle should not get too close to 90 or -90, or the resulting image will
+be unreasonably wide.  In fact, if it gets too close, the width will be so
+large that <b>pnmshear</b> cannot do computations in the word sizes it uses,
+and the program detects this and fails.
 
 <P><b>pnmshear</b> does the shearing by looping over the source pixels
 and distributing fractions to each of the destination pixels.  This