miscellaneous update

git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@4548 9d0c8265-081b-0410-96cb-a4ca84ce46f8
author: giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8> 2023-05-04 00:32:54 +0000
committer: giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8> 2023-05-04 00:32:54 +0000
commit: bd82abed1156636c98b258ade1735dfeb557e674 (patch)
tree: 9dfda56bb337eacc3702e1f4759c3a22fcbf7087
parent: 73b435777acf1b420ba369d8c0de06770d11b738 (diff)
download: netpbm-mirror-bd82abed1156636c98b258ade1735dfeb557e674.tar.gz
netpbm-mirror-bd82abed1156636c98b258ade1735dfeb557e674.tar.xz
netpbm-mirror-bd82abed1156636c98b258ade1735dfeb557e674.zip
18 files changed, 85 insertions, 73 deletions
diff --git a/directory.html b/directory.html
index 10d25a66..1dfe557e 100644
--- a/directory.html
+++ b/directory.html
@@ -1157,7 +1157,7 @@ compatibility wrappers around the replacement program.
 <li><b><a href="pcdindex.html">pcdindex</a></b>
 <li><b><a href="ppmbrighten.html">ppmbrighten</a></b>
 <li><b><a href="ppmcolors.html">ppmcolors</a></b>
-<li><b><a href="pnmcat.html">pnmcat</a></b>
+<li><b><a href="pamcat.html">pamcat</a></b>
 
 </ul>
 
diff --git a/jpegtopnm.html b/jpegtopnm.html
index 9262e033..2504aed6 100644
--- a/jpegtopnm.html
+++ b/jpegtopnm.html
@@ -2,7 +2,7 @@
 <html><head><title>Jpegtopnm User Manual</title></head>
 <body>
 <h1>jpegtopnm</h1>
-Updated: 13 October 2002
+Updated: 20 March 2023
 <br>
 <a href="#index">Table Of Contents</a>
 
@@ -23,6 +23,7 @@ jpegtopnm - convert JPEG/JFIF file to PPM or PGM image
 [<b>-repair</b>]
 [<b>-verbose</b>]
 [<b>-tracelevel</b> <i>N</i>]
+[<b>-traceexif</b>]
 [<i>filename</i>]
 
 <p>Minimum unique abbreviation of option is acceptable.  You may use double
@@ -247,6 +248,13 @@ Print details about the conversion to the Standard Error file.
 file.  A higher value of <i>n</i> gets more trace information.
 <b>-verbose</b> implies a trace level of at least 1.
 
+<dt><b>-traceexif</b>
+
+<dd>
+Print trace information about the processing of EXIF header information.
+
+<p>This option was new in Netpbm 11.02 (March 2023).
+
 </dl>
 
 <h2 id="examples">EXAMPLES</h2>
diff --git a/pamdice.html b/pamdice.html
index d3724d36..1e3dc3b5 100644
--- a/pamdice.html
+++ b/pamdice.html
@@ -59,7 +59,7 @@ output files.
 the output pieces.
 
 <p><b>pamundice</b> can rejoin the images.  For finer control, you can
-also use <p><b>pnmcat</b>.
+also use <p><b>pamcat</b>.
 
 <p>One use for this is to make pieces that take less computer resources
 than the whole image to process.  For example, you might have an image
@@ -139,7 +139,7 @@ in each direction.
 
 <b><a href="pamundice.html">pamundice</a></b>,
 <b><a href="pamcut.html">pamcut</a></b>,
-<b><a href="pnmcat.html">pnmcat</a></b>,
+<b><a href="pamcat.html">pamcat</a></b>,
 <b><a href="pgmslice.html">pgmslice</a></b>,
 <b><a href="ppmglobe.html">ppmglobe</a></b>
 <b><a href="pnm.html">pnm</a></b>
diff --git a/pamlookup.html b/pamlookup.html
index 44aa0254..33cbb95d 100644
--- a/pamlookup.html
+++ b/pamlookup.html
@@ -48,22 +48,22 @@ whole tuple with each possible ordered pair index.  Modifying the example
 above, the index value could be (23, 5) instead of 23.
 
 <p>With whole tuple indexing, the output thus has the same width and height as
-the index image, and tuple depth and type and maxval determined by the lookup
-table.
+the index image, and tuple depth and type and maxval are determined by the
+lookup table.
 
 <p>With whole tuple indexing, if the index image has depth 1, its sample
 values are single whole number indices.  If the index image has depth greater
 than 1, its tuples are ordered pair indices composed of the first and second
 sample in the tuple.
 
-<p>In by plane indexing, the index image contains whole number indices.
-The first sample of each tuple in the index image is the index.  The lookup
-table maps each whole number index to another whole number.
-<b>pamlookup</b> looks up each sample from the index image in the lookup table
-and uses the resulting whole number as the sample value for the same
-row, column, and plane in the output.
+<p>In by-plane indexing, the index image contains whole number indices.  Each
+sample in the index image is an index.  The lookup table maps each whole
+number index to another whole number.  <b>pamlookup</b> looks up the sample at
+each row, column, and plane in the index image in the lookup table and uses
+the resulting whole number as the sample value for the same row, column, and
+plane in the output.
 
-<p>With by plane indexing, the output thus has the same dimensions as the
+<p>With by-plane indexing, the output thus has the same dimensions as the
 index image an the same maxval as the lookup image.
 
 
@@ -105,7 +105,7 @@ rule applies to the height of the index image as to the width.
 lookup table image.  <b>-</b> means Standard Input.  It won't work if both the
 index image file and lookup table file are Standard Input.
 
-<p>You can use <b>ppmmake</b> and <b>pnmcat</b> to create a lookup table file.
+<p>You can use <b>ppmmake</b> and <b>pamcat</b> to create a lookup table file.
 
 
 <h3 id="wholetuple">Example - Whole Tuple Indexing</h3>
@@ -337,9 +337,9 @@ Now, we create a lookup table that we can index with those 4 values:
     ppmmake black 1 1 &gt;black.ppm
     ppmmake red   1 1 &gt;red.ppm
     ppmmake green 1 1 &gt;green.ppm
-    pnmcat -leftright black.ppm red.ppm   &gt;blackred.ppm
-    pnmcat -leftright green.ppm white.ppm &gt;greenwhite.ppm
-    pnmcat -topbottom blackred.ppm greenwhite.ppm &gt;lookup.ppm
+    pamcat -leftright black.ppm red.ppm   &gt;blackred.ppm
+    pamcat -leftright green.ppm white.ppm &gt;greenwhite.ppm
+    pamcat -topbottom blackred.ppm greenwhite.ppm &gt;lookup.ppm
 </kbd>
 </pre>
 
@@ -358,7 +358,7 @@ produce the output:
 <a href="pamunlookup.html">pamunlookup</a>,
 <a href="pnmremap.html">pnmremap</a>,
 <a href="ppmmake.html">ppmmake</a>,
-<a href="pnmcat.html">pnmcat</a>,
+<a href="pamcat.html">pamcat</a>,
 <a href="pamstack.html">pamstack</a>,
 <a href="pnm.html">pnm</a>,
 <a href="pam.html">pam</a>
diff --git a/pamrestack.html b/pamrestack.html
index 9d513cfa..8f3a8913 100644
--- a/pamrestack.html
+++ b/pamrestack.html
@@ -103,7 +103,7 @@ Print information about the processing to Standard Error.
     this problem.
 
   <li><b>pamrestack</b> can be used with <b>pamdice</b>, <b>pamundice</b>,
-    <b>pnmcat</b>, etc. to divide and combine images in the process of
+    <b>pamcat</b>, etc. to divide and combine images in the process of
     interlacing.
   </ul>
 
@@ -124,7 +124,7 @@ pamseq 3 255 | pamrestack -width=4096
 
 <pre>
 <kbd>
-pnmcat -leftright oddrows.ppm evenrows.ppm | pamrestack -width=600
+pamcat -leftright oddrows.ppm evenrows.ppm | pamrestack -width=600
 </kbd>
 </pre>
 
@@ -135,7 +135,7 @@ pnmcat -leftright oddrows.ppm evenrows.ppm | pamrestack -width=600
 <pre>
 <kbd>
   pamflip -leftright evenrows.ppm |
-    pnmcat -leftright oddrows.ppm - |
+    pamcat -leftright oddrows.ppm - |
       pamrestack -width 600
 </kbd>
 </pre>
@@ -151,7 +151,7 @@ pnmcat -leftright oddrows.ppm evenrows.ppm | pamrestack -width=600
 <b><a href="pamdeinterlace.html">pamdeinterlace</a></b>,
 <b><a href="pamdice.html">pamdice</a></b>,
 <b><a href="pamundice.html">pamundice</a></b>,
-<b><a href="pnmcat.html">pnmcat</a></b>,
+<b><a href="pamcat.html">pamcat</a></b>,
 <b><a href="pam.html">pam</a></b>
 
 
diff --git a/pamtopng.html b/pamtopng.html
index acb6d3e2..c9083ea1 100644
--- a/pamtopng.html
+++ b/pamtopng.html
@@ -66,10 +66,10 @@ degree that probably doesn't make any difference in the modern world.
 <p>The main advantage <b>pamtopng</b> has over <b>pnmtopng</b> is that the
 former can use the transparency channel of a PAM image to generate the
 transparency information in the PNG.  In contrast, handling of the alpha
-channel is very cumbersome with <b>pnmotpng</b>.
+channel is very cumbersome with <b>pnmtopng</b>.
 
 <p>One difference that <em>does not</em> exist, that some people might
-incorrectly infer from the names is the possible input formats.  Both programs
+incorrectly infer from the names, is the possible input formats.  Both programs
 can take PBM, PGM, PPM, and PAM input.
 
 <p>Because <b>pnmtopng</b> has been around virtually forever, programs and
@@ -166,7 +166,7 @@ of those 3 primary illuminants and of white (i.e. full strength of
 all three).
 
 <p>The <i>chroma_list</i> value is a blank-separated list of 8 floating
-point decimal numbers.  The CIE-1931 X and Y chromaticities (in that
+point decimal numbers: the CIE-1931 X and Y chromaticities (in that
 order) of each of white, red, green, and blue, in that order.
 
 <p>This information goes into the PNG's cHRM chunk.
diff --git a/pamtosrf.html b/pamtosrf.html
index efc88c95..a2c6330b 100644
--- a/pamtosrf.html
+++ b/pamtosrf.html
@@ -36,7 +36,7 @@ will your SRF output.  For such a file, you should have two image: the first
 for 3D oblique views of the vehicle and the second for overhead views.  Each
 image is a horizontal concatenation of 36 square images, each rotated 10
 degrees from the previous, thereby covering the full 360 degree circle.
-You could create this concatenation with <b>pnmcat -lr</b> and you could
+You could create this concatenation with <b>pamcat -lr</b> and you could
 create the invidual views with <b>pnmrotate</b>.
 
 
@@ -66,7 +66,7 @@ command line option:
 
 <ul>
   <li><a href="srftopam.html">srftopam</a>
-  <li><a href="pnmcat.html">pnmcat</a>
+  <li><a href="pamcat.html">pamcat</a>
   <li><a href="pam.html">pam</a>
   </ul>
 
diff --git a/pamundice.html b/pamundice.html
index a258d72b..bb6716ca 100644
--- a/pamundice.html
+++ b/pamundice.html
@@ -84,7 +84,7 @@ chessboard by computing an image of each square, then using <b>pamundice</b>
 to assemble them into a board.
   
 <p>An alternative to join images in a single direction (i.e. a single
-rank or a single file) is <b>pnmcat</b>.  <b>pnmcat</b> gives you more
+rank or a single file) is <b>pamcat</b>.  <b>pamcat</b> gives you more
 flexibility than <b>pamundice</b> in identifying the input images: you
 can supply them on Standard Input or as a list of arbitrarily named
 files.
@@ -226,13 +226,13 @@ This is an alternative to specifying a file name pattern as an argument.
 <h2 id="history">HISTORY</h2>
 
 <p><b>pamundice</b> was new in Netpbm 10.39 (June 2007).  Before that,
-<b>pnmcat</b> is the best substitute.
+<b>pamcat</b> is the best substitute.
 
 
 <h2 id="seealso">SEE ALSO</h2>
 
 <b><a href="pamdice.html">pamdice</a></b>,
-<b><a href="pnmcat.html">pnmcat</a></b>,
+<b><a href="pamcat.html">pamcat</a></b>,
 <b><a href="pnmindex.html">pnmindex</a></b>,
 <b><a href="pnmtile.html">pnmtile</a></b>,
 <b><a href="pnm.html">pnm</a></b>
diff --git a/pbmtextps.html b/pbmtextps.html
index 5977e2d5..751b12ea 100644
--- a/pbmtextps.html
+++ b/pbmtextps.html
@@ -77,13 +77,13 @@ With <b>-topmargin</b> and <b>-bottommargin</b>, that may not be the case.
      $ pbmtextps -font=Times-Roman -descent=20 \
           &quot;The soup is called&quot; &gt; a1.pbm
      $ pbmtextps -font=Itallic -descent=20 &quot;Goulash.&quot; &gt; a2.pbm
-     $ pnmcat -leftright -jbottom a1.pbm a2.pbm &gt; out.pbm
+     $ pamcat -leftright -jbottom a1.pbm a2.pbm &gt; out.pbm
 </kbd>
 </pre>
 
 <p>If you're using <b>-descent</b> to line up the segments of text you are
-  concatenating horizontally with <b>pnmcat</b>, use the <b>-jbottom</b>
-  (justify to bottom) option on <b>pnmcat</b> as in the example above.  If you
+  concatenating horizontally with <b>pamcat</b>, use the <b>-jbottom</b>
+  (justify to bottom) option on <b>pamcat</b> as in the example above.  If you
   use <b>-ascent</b>, use <b>-jtop</b> instead.
 
 <p>Similarly, if you render two lines of text (in separate invocations of
@@ -148,7 +148,7 @@ as if you specified <b>-leftmargin=</b><i>0.5*fontsize</i>.
 is as if you specified <b>-rightmargin=0</b>.
 
 
-<h3 id="input_text">Input Text</h2>
+<h3 id="input_text">Input Text</h3>
 
 <p>The simplest way to specify the text to render is just to specify it,
   in ASCII, as the sole argument of the command.  For example,
@@ -371,6 +371,7 @@ Copyright (C) 2002 by James McCann
 <li><a href="#description">DESCRIPTION</a>
   <ul>
   <li><a href="#margins">Margins</a>
+  <li><a href="#input_text">Input Text</a>
   </ul>
 <li><a href="#options">OPTIONS</a>
 <li><a href="#usage">USAGE</a>
diff --git a/pnmcolormap.html b/pnmcolormap.html
index 95fe49b9..8790862e 100644
--- a/pnmcolormap.html
+++ b/pnmcolormap.html
@@ -77,7 +77,7 @@ different colors.  Before Netpbm 10.31 (December 2005), <b>pnmcolormap</b>
 ignored any image after the first.
 
 <p>If you want to create a colormap without basing it on the colors in
-an input image, <b>pamseq</b>, <b>ppmmake</b>, and <b>pnmcat</b> can
+an input image, <b>pamseq</b>, <b>ppmmake</b>, and <b>pamcat</b> can
 be useful.
 
 <h2 id="parameters">PARAMETERS</h2>
@@ -192,9 +192,14 @@ 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 default is <b>-spreadbrightness</b>.  Where there are multiple
 colors of the median magnitude, they are distributed arbitrarily among between
-the subboxes.  This arbitrary distribution depends upon what the system's
-<b>qsort</b> function does with multiple equal values, so <b>pnmcolormap</b>
-may produce slightly different results on different systems.
+the subboxes.
+
+This arbitrary distribution is repeatable, though, for a given Netpbm version
+-- every invocation of <b>pnmcolormap</b> generates the same color map.
+Before Netpbm 11.03 (June 2023), the distribution would depend upon what the
+system's <b>qsort</b> function does with multiple equal values, so
+<b>pnmcolormap</b> may produce slightly different results on different
+systems.
 
 <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
@@ -234,7 +239,7 @@ SIGGRAPH '82 Proceedings, page 297.
 <b><a href="ppmdither.html">ppmdither</a></b>,
 <b><a href="pamseq.html">pamseq</a></b>,
 <b><a href="ppmmake.html">ppmmake</a></b>,
-<b><a href="pnmcat.html">pnmcat</a></b>,
+<b><a href="pamcat.html">pamcat</a></b>,
 <b><a href="ppm.html">ppm</a></b>
 
 <h2 id="history">HISTORY</h2>
diff --git a/pnmcrop.html b/pnmcrop.html
index b2f6968a..83237ac4 100644
--- a/pnmcrop.html
+++ b/pnmcrop.html
@@ -94,8 +94,8 @@ all input images but the first.
 <p>If you want to chop a specific amount off the side of an image, use
 <b>pamcut</b>.
 
-<p>If you want to add different borders after removing the existing
-ones, use <b>pnmcat</b> or <b>pamcomp</b>.
+<p>If you want to add different borders after removing the existing ones,
+use <b>pamcat</b> or <b>pamcomp</b>.
 
 
 <h2 id="options">OPTIONS</h2>
diff --git a/pnmhisteq.html b/pnmhisteq.html
index 2cd96a31..2ee38b41 100644
--- a/pnmhisteq.html
+++ b/pnmhisteq.html
@@ -85,11 +85,10 @@ option allows you to save, as a PGM image, the luminosity map it
 computes from an image.  The <b>-rmap</b> option causes <b>pnmisteq</b>
 to use such an image as its luminosity map.
 
-<p>So you can run <b>pnmhisteq</b> with <b>-wmap</b> on a composite
-you created with <b>pnmcat</b> of the images you intend to process.
-Then, you can run <b>pnmisteq</b> with <b>-rmap</b> on each of the
-individual images, using the luminosity map you generated from the
-composite.
+<p>So you can run <b>pnmhisteq</b> with <b>-wmap</b> on a composite you
+created with <b>pamcat</b> of the images you intend to process.  Then, you can
+run <b>pnmisteq</b> with <b>-rmap</b> on each of the individual images, using
+the luminosity map you generated from the composite.
 
 <p>Use <b>pnmhistmap</b> to see the result.  Run a color image through
 <b>ppmtopgm</b> first so that you see a histogram of the luminosity instead of
@@ -190,7 +189,7 @@ identity operation), the only effect of passing the file through
 
 <b><a href="pnmnorm.html">pnmnorm</a></b>,
 
-<b><a href="pnmcat.html">pnmcat</a></b>,
+<b><a href="pamcat.html">pamcat</a></b>,
 
 <b><a href="pamdepth.html">pamdepth</a></b>,
 
diff --git a/pnmmargin.html b/pnmmargin.html
index 4400ed55..12f2c3f2 100644
--- a/pnmmargin.html
+++ b/pnmmargin.html
@@ -56,7 +56,7 @@ version 10.40 (September 2007).
 what is border and what is subject.
 
 <p>For lower level control, including to add different size borders to
-different sides of the image, look at <b>pnmcat</b>.
+different sides of the image, look at <b>pamcat</b>.
 
 <p>If all you're trying to do is get the image up to a certain required
 size, <b>pamcut</b> may be what you want.
@@ -70,7 +70,7 @@ over the individual margins and does only black and white margins.
 <ul>
 <li><a href="pamcut.html">pamcut</a>
 <li><a href="pnmcrop.html">pnmcrop</a>
-<li><a href="pnmcat.html">pnmcat</a>
+<li><a href="pamcat.html">pamcat</a>
 <li><a href="pnmpad.html">pnmpad</a>
 <li><a href="pnm.html">pnm</a>
 </ul>
diff --git a/pnmstitch.html b/pnmstitch.html
index 3caea690..cbc39da4 100644
--- a/pnmstitch.html
+++ b/pnmstitch.html
@@ -53,7 +53,7 @@ You probably want to crop the result with <b>pamcut</b> to make a nice
 rectangular image.
 
 <p>If you're just trying to join (concatenate) two images at their edges, use
-<b>pnmcat</b>.
+<b>pamcat</b>.
 
 <p>The <i>left_filespec</i> and <i>right_filespec</i> arguments are the
 specifications (names) of the PNM files containing the left hand and
@@ -110,7 +110,7 @@ about the stitching process.
 <h2 id="seealso">SEE ALSO</h2>
 
 <b><a href="pamcut.html">pamcut</a></b>,
-<b><a href="pnmcat.html">pnmcat</a></b>,
+<b><a href="pamcat.html">pamcat</a></b>,
 <b><a href="pamflip.html">pamflip</a></b>,
 <b><a href="pnm.html">pnm</a></b>,
 
diff --git a/pnmtile.html b/pnmtile.html
index ae37dee6..7d941aa7 100644
--- a/pnmtile.html
+++ b/pnmtile.html
@@ -27,7 +27,7 @@ format as output.
 <p>You can do pretty much the reverse with <b>pamdice</b>.
 
 <p>You can explicitly concatenate an image to itself (or anything else)
-with <b>pnmcat</b>.
+with <b>pamcat</b>.
 
 <p>If you're trying to tile multiple images into a superimage,
 see <b>pamundice</b> or (for a thumbnail sheet) <b>pnmindex</b>.
@@ -43,7 +43,7 @@ Common Options</a>.)
 <h2 id="seealso">SEE ALSO</h2>
 
 <a href="pamundice.html">pamundice</a>,
-<a href="pnmcat.html">pnmcat</a>,
+<a href="pamcat.html">pamcat</a>,
 <a href="pamdice.html">pamdice</a>,
 <a href="pnmindex.html">pnmindex</a>,
 <a href="pampop9.html">pampop9</a>,
diff --git a/pnmtopng.html b/pnmtopng.html
index 0c605c7f..cb707515 100644
--- a/pnmtopng.html
+++ b/pnmtopng.html
@@ -113,7 +113,7 @@ to come before the non-option program arguments.
 <b>-phys</b>/<b>-size</b> as an example, is that <b>-phys</b> takes
 multiple program arguments as the option argument, whereas <b>-size</b>
 takes a single program argument which is composed of multiple words.
-E.g.  The old shell command
+E.g. the old shell command
 
 <pre>
 <kbd>
@@ -320,7 +320,7 @@ of those 3 primary illuminants and of white (i.e. full strength of
 all three).
 
 <p>The <i>chroma_list</i> value is a blank-separated list of 8 floating
-point decimal numbers.  The CIE-1931 X and Y chromaticities (in that
+point decimal numbers:  the CIE-1931 X and Y chromaticities (in that
 order) of each of white, red, green, and blue, in that order.
 
 <p>This information goes into the PNG's cHRM chunk.
diff --git a/ppmshift.html b/ppmshift.html
index f46fdd92..ce825e04 100644
--- a/ppmshift.html
+++ b/ppmshift.html
@@ -58,7 +58,7 @@ convert it to ppm, and process it e.g. like this, assuming the picture is
          ppmshift 10 &gt;lower.ppm
      
      #and concatenate the two pieces
-     pnmcat -topbottom upper.ppm lower.ppm &gt;newpic.ppm
+     pamcat -topbottom upper.ppm lower.ppm &gt;newpic.ppm
 
 </pre>
 
@@ -71,7 +71,7 @@ surface with slight ripples.
 <a href="pamcut.html">pamcut</a>,
 <a href="pamflip.html">pamflip</a>,
 <a href="ppmdim.html">ppmdim</a>,
-<a href="pnmcat.html">pnmcat</a>
+<a href="pamcat.html">pamcat</a>
 
 
 <h2 id="author">AUTHOR</h2>
diff --git a/ppmtomitsu.html b/ppmtomitsu.html
index e03d14a8..7948aa41 100644
--- a/ppmtomitsu.html
+++ b/ppmtomitsu.html
@@ -36,23 +36,22 @@ ppmtomitsu - convert a PPM image to a Mitsubishi S340-10 file
 format suitable to be printed by a Mitsubishi S340-10 printer, or any
 other Mitsubishi color sublimation printer.
 
-<p>The Mitsubishi S340-10 Color Sublimation printer can print in 24 bit
-color.  Images of the available sizes take so long to transfer that
-there is a fast method, employing a lookuptable, that ppmtomitsu will
-use if there is a maximum of 256 colors in the image.  ppmtomitsu
-will try to position your image to the center of the paper, and will
-rotate your image for you if xsize is larger than ysize.  If your
-image is larger than the media allows, ppmtomitsu will quit with an
-error message. (We decided that the media were too expensive to have
-careless users produce misprints.)  Once data transmission has
-started, the job can't be stopped in a sane way without resetting the
+<p>The Mitsubishi S340-10 Color Sublimation printer can print in 24 bit color.
+Images of the available sizes take so long to transfer that there is a fast
+method, employing a lookup table, that <b>ppmtomitsu</b> uses if there are no
+more than 256 colors in the image.  <b>ppmtomitsu</b> tries to position your
+image at the center of the paper, and will rotate your image for you if
+xs<i>ize</i> is larger than y<i>size</i>.  If your image is larger than the
+media allows, <b>ppmtomitsu</b> fails. (We decided that the media were too
+expensive to have careless users produce misprints).  Once data transmission
+has started, the job can't be stopped in a sane way without resetting the
 printer.  The printer understands putting together images in the
-printers memory; ppmtomitsu doesn't utilize this as pnmcat etc provide
-the same functionality and let you view the result on-screen, too.
-The S340-10 is the lowest common denominator printer; for higher
-resolution printers there's the dpi300 option. The other printers are also
-capable of higher values for enlarge eg, but I don't think that's
-essential enough to warrant a change in the program.
+printer&apos;s memory; <b>ppmtomitsu</b> doesn't use this function because
+<b>pamcat</b> etc provide the same functions and let you view the result
+on-screen, too.  The S340-10 is the lowest common denominator printer; for
+higher resolution printers there is the dpi300 option. The other printers are
+also capable of higher values for <i>enlarge</i>, etc., but I don't think that
+is valuable enough to warrant a change in the program.
 
 <p>For proper results, the input maxval must be 255.  Use <b>pamdepth</b>
 to ensure that it is.
author	giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>	2023-05-04 00:32:54 +0000
committer	giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>	2023-05-04 00:32:54 +0000
commit	bd82abed1156636c98b258ade1735dfeb557e674 (patch)
tree	9dfda56bb337eacc3702e1f4759c3a22fcbf7087
parent	73b435777acf1b420ba369d8c0de06770d11b738 (diff)
download	netpbm-mirror-bd82abed1156636c98b258ade1735dfeb557e674.tar.gz netpbm-mirror-bd82abed1156636c98b258ade1735dfeb557e674.tar.xz netpbm-mirror-bd82abed1156636c98b258ade1735dfeb557e674.zip