summary refs log tree commit diff
diff options
context:
space:
mode:
authorgiraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>2024-02-27 18:16:44 +0000
committergiraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>2024-02-27 18:16:44 +0000
commit230d223185a1d9b07c57097bae2bbfa53964b11f (patch)
treea3ad32100ecc4631bdf87f8262288010f7002777
parent853b554bc27b05f025fcb143c2577658412045db (diff)
downloadnetpbm-mirror-230d223185a1d9b07c57097bae2bbfa53964b11f.tar.gz
netpbm-mirror-230d223185a1d9b07c57097bae2bbfa53964b11f.tar.xz
netpbm-mirror-230d223185a1d9b07c57097bae2bbfa53964b11f.zip
miscellaneous update
git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@4850 9d0c8265-081b-0410-96cb-a4ca84ce46f8
-rw-r--r--pamcut.html15
-rw-r--r--pfm.html26
2 files changed, 26 insertions, 15 deletions
diff --git a/pamcut.html b/pamcut.html
index 13e96c2f..1d375920 100644
--- a/pamcut.html
+++ b/pamcut.html
@@ -2,12 +2,12 @@
 <html><head><title>Pamcut User Manual</title></head>
 <body>
 <h1>pamcut</h1>
-Updated: 04 October 2019
+Updated: 26 February 2024
 <br>
 <a href="#index">Table Of Contents</a>
 
 <h2>NAME</h2>
-pamcut - cut a rectangle out of a PAM, PBM, PGM, or PPM image
+pamcut - select a rectangular region of a PAM, PBM, PGM, or PPM image
 
 <h2 id="synopsis">SYNOPSIS</h2>
 
@@ -70,13 +70,14 @@ leftmost 50 and rightmost 200 columns.
 <b>-top</b>, <b>-bottom</b>, <b>-width</b>, <b>-height</b>, and <b>-pad</b>
 options.
 
-<p>For example, <b>-left=50 -right=200</b> means to keep the 150 columns
+<p>For example, <b>-left=50 -right=200</b> means to keep the 151 columns
 between Columns 50 and 200 inclusive.
 
 <p>You can code any mixture of the options.  What you don't specify defaults.
 Those defaults are in favor of minimal cutting and in favor of cutting the
-right and bottom edges off.  It is an error to overspecify, i.e. to specify
-all three of <b>-left</b>, <b>-right</b>, and <b>-width</b> or <b>-top</b>,
+right and bottom edges off and (with <b>-pad</b>) minimal padding and padding
+on the right and bottom.  It is an error to overspecify, i.e. to specify all
+three of <b>-left</b>, <b>-right</b>, and <b>-width</b> or <b>-top</b>,
 <b>-bottom</b>, and <b>-height</b> or <b>right</b> as well as
 <b>-cropright</b>.
 
@@ -85,8 +86,8 @@ arguments.  Arguments were the only way available before July 2000, but you
 should not use them in new applications.  Options are easier to remember and
 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>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
diff --git a/pfm.html b/pfm.html
index 5f91674d..2ea670b5 100644
--- a/pfm.html
+++ b/pfm.html
@@ -5,7 +5,7 @@
 </head>
 <body>
 <h1>pfm</h1>
-Updated: 19 April 2012
+Updated: 27 February 2024
 <h2>NAME</h2>
 
 PFM - PFM graphic image file format
@@ -17,14 +17,20 @@ This document describes the PFM graphic image file format as understood by
 the Netpbm converters <a href="pamtopfm.html"><b>pamtopfm</b></a> and
 <a href="pfmtopam.html"><b>pfmtopam</b></a>.
 
-<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.
+<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.  This format appears to be the one Gimp calls PFM.
 
-<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.
-Its goal is not consistent with those of Netpbm formats.
+Another important PFM is used by Adobe Photoshop and appears to be identical
+to this except that rows are ordered from top to bottom in the Adobe version.
+If you interchange images between systems that use these two formats, it will
+work except that your image gets flipped upside down.  You can compensate for
+that with <kbd>pamflip -topbottom</kbd>.
+
+<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.  Its goal is not
+consistent with those of Netpbm formats.
 
 <h2>The format</h2>
 
@@ -75,6 +81,10 @@ square meter.
 delimiters of any kind.  They are grouped by row, with the pixels in each
 row ordered left to right and the rows ordered bottom to top.
 
+<em>Note:</em> This is the opposite of Netpbm formats, which order rows
+top to bottom.  It is also the opposite of the format Adobe Photoshop calls
+PFM.  See the introduction for more information on this disparity.
+  
 <p>Each pixel consists of 1 or 3 samples, packed one after another,
 with no delimiters of any kind.  1 sample for a grayscale PFM and 3 for a
 color PFM (see the Identifier Line of the PFM header).