From bd82abed1156636c98b258ade1735dfeb557e674 Mon Sep 17 00:00:00 2001 From: giraffedata Date: Thu, 4 May 2023 00:32:54 +0000 Subject: miscellaneous update git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@4548 9d0c8265-081b-0410-96cb-a4ca84ce46f8 --- directory.html | 2 +- jpegtopnm.html | 10 +++++++++- pamdice.html | 4 ++-- pamlookup.html | 28 ++++++++++++++-------------- pamrestack.html | 8 ++++---- pamtopng.html | 6 +++--- pamtosrf.html | 4 ++-- pamundice.html | 6 +++--- pbmtextps.html | 9 +++++---- pnmcolormap.html | 15 ++++++++++----- pnmcrop.html | 4 ++-- pnmhisteq.html | 11 +++++------ pnmmargin.html | 4 ++-- pnmstitch.html | 4 ++-- pnmtile.html | 4 ++-- pnmtopng.html | 4 ++-- ppmshift.html | 4 ++-- ppmtomitsu.html | 31 +++++++++++++++---------------- 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.
  • pcdindex
  • ppmbrighten
  • ppmcolors -
  • pnmcat +
  • pamcat diff --git a/jpegtopnm.html b/jpegtopnm.html index 9262e033..2504aed6 100644 --- a/jpegtopnm.html +++ b/jpegtopnm.html @@ -2,7 +2,7 @@ Jpegtopnm User Manual

    jpegtopnm

    -Updated: 13 October 2002 +Updated: 20 March 2023
    Table Of Contents @@ -23,6 +23,7 @@ jpegtopnm - convert JPEG/JFIF file to PPM or PGM image [-repair] [-verbose] [-tracelevel N] +[-traceexif] [filename]

    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 n gets more trace information. -verbose implies a trace level of at least 1. +

    -traceexif + +
    +Print trace information about the processing of EXIF header information. + +

    This option was new in Netpbm 11.02 (March 2023). +

    EXAMPLES

    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.

    pamundice can rejoin the images. For finer control, you can -also use

    pnmcat. +also use

    pamcat.

    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. pamundice, pamcut, -pnmcat, +pamcat, pgmslice, ppmglobe pnm 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.

    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.

    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. -

    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. -pamlookup 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. +

    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. pamlookup 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. -

    With by plane indexing, the output thus has the same dimensions as the +

    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. - means Standard Input. It won't work if both the index image file and lookup table file are Standard Input. -

    You can use ppmmake and pnmcat to create a lookup table file. +

    You can use ppmmake and pamcat to create a lookup table file.

    Example - Whole Tuple Indexing

    @@ -337,9 +337,9 @@ Now, we create a lookup table that we can index with those 4 values: ppmmake black 1 1 >black.ppm ppmmake red 1 1 >red.ppm ppmmake green 1 1 >green.ppm - pnmcat -leftright black.ppm red.ppm >blackred.ppm - pnmcat -leftright green.ppm white.ppm >greenwhite.ppm - pnmcat -topbottom blackred.ppm greenwhite.ppm >lookup.ppm + pamcat -leftright black.ppm red.ppm >blackred.ppm + pamcat -leftright green.ppm white.ppm >greenwhite.ppm + pamcat -topbottom blackred.ppm greenwhite.ppm >lookup.ppm @@ -358,7 +358,7 @@ produce the output: pamunlookup, pnmremap, ppmmake, -pnmcat, +pamcat, pamstack, pnm, pam 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.
  • pamrestack can be used with pamdice, pamundice, - pnmcat, etc. to divide and combine images in the process of + pamcat, etc. to divide and combine images in the process of interlacing. @@ -124,7 +124,7 @@ pamseq 3 255 | pamrestack -width=4096
     
    -pnmcat -leftright oddrows.ppm evenrows.ppm | pamrestack -width=600
    +pamcat -leftright oddrows.ppm evenrows.ppm | pamrestack -width=600
     
     
    @@ -135,7 +135,7 @@ pnmcat -leftright oddrows.ppm evenrows.ppm | pamrestack -width=600
     
       pamflip -leftright evenrows.ppm |
    -    pnmcat -leftright oddrows.ppm - |
    +    pamcat -leftright oddrows.ppm - |
           pamrestack -width 600
     
     
    @@ -151,7 +151,7 @@ pnmcat -leftright oddrows.ppm evenrows.ppm | pamrestack -width=600 pamdeinterlace, pamdice, pamundice, -pnmcat, +pamcat, pam 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.

    The main advantage pamtopng has over pnmtopng 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 pnmotpng. +channel is very cumbersome with pnmtopng.

    One difference that does not 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.

    Because pnmtopng 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).

    The chroma_list 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.

    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 pnmcat -lr and you could +You could create this concatenation with pamcat -lr and you could create the invidual views with pnmrotate. @@ -66,7 +66,7 @@ command line option:

    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 pamundice to assemble them into a board.

    An alternative to join images in a single direction (i.e. a single -rank or a single file) is pnmcat. pnmcat gives you more +rank or a single file) is pamcat. pamcat gives you more flexibility than pamundice 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.

    HISTORY

    pamundice was new in Netpbm 10.39 (June 2007). Before that, -pnmcat is the best substitute. +pamcat is the best substitute.

    SEE ALSO

    pamdice, -pnmcat, +pamcat, pnmindex, pnmtile, pnm diff --git a/pbmtextps.html b/pbmtextps.html index 5977e2d5..751b12ea 100644 --- a/pbmtextps.html +++ b/pbmtextps.html @@ -77,13 +77,13 @@ With -topmargin and -bottommargin, that may not be the case. $ pbmtextps -font=Times-Roman -descent=20 \ "The soup is called" > a1.pbm $ pbmtextps -font=Itallic -descent=20 "Goulash." > a2.pbm - $ pnmcat -leftright -jbottom a1.pbm a2.pbm > out.pbm + $ pamcat -leftright -jbottom a1.pbm a2.pbm > out.pbm

    If you're using -descent to line up the segments of text you are - concatenating horizontally with pnmcat, use the -jbottom - (justify to bottom) option on pnmcat as in the example above. If you + concatenating horizontally with pamcat, use the -jbottom + (justify to bottom) option on pamcat as in the example above. If you use -ascent, use -jtop instead.

    Similarly, if you render two lines of text (in separate invocations of @@ -148,7 +148,7 @@ as if you specified -leftmargin=0.5*fontsize. is as if you specified -rightmargin=0. -

    Input Text

    +

    Input Text

    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

  • DESCRIPTION
  • OPTIONS
  • USAGE 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), pnmcolormap ignored any image after the first.

    If you want to create a colormap without basing it on the colors in -an input image, pamseq, ppmmake, and pnmcat can +an input image, pamseq, ppmmake, and pamcat can be useful.

    PARAMETERS

    @@ -192,9 +192,14 @@ luminosity of the color. E.g. red is weighted much more than blue. Select among these with the -spreadbrightness and -spreadluminosity options. The default is -spreadbrightness. 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 -qsort function does with multiple equal values, so pnmcolormap -may produce slightly different results on different systems. +the subboxes. + +This arbitrary distribution is repeatable, though, for a given Netpbm version +-- every invocation of pnmcolormap generates the same color map. +Before Netpbm 11.03 (June 2023), the distribution would depend upon what the +system's qsort function does with multiple equal values, so +pnmcolormap may produce slightly different results on different +systems.

    pnmcolormap 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. ppmdither, pamseq, ppmmake, -pnmcat, +pamcat, ppm

    HISTORY

    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.

    If you want to chop a specific amount off the side of an image, use pamcut. -

    If you want to add different borders after removing the existing -ones, use pnmcat or pamcomp. +

    If you want to add different borders after removing the existing ones, +use pamcat or pamcomp.

    OPTIONS

    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 -rmap option causes pnmisteq to use such an image as its luminosity map. -

    So you can run pnmhisteq with -wmap on a composite -you created with pnmcat of the images you intend to process. -Then, you can run pnmisteq with -rmap on each of the -individual images, using the luminosity map you generated from the -composite. +

    So you can run pnmhisteq with -wmap on a composite you +created with pamcat of the images you intend to process. Then, you can +run pnmisteq with -rmap on each of the individual images, using +the luminosity map you generated from the composite.

    Use pnmhistmap to see the result. Run a color image through ppmtopgm 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 pnmnorm, -pnmcat, +pamcat, pamdepth, 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.

    For lower level control, including to add different size borders to -different sides of the image, look at pnmcat. +different sides of the image, look at pamcat.

    If all you're trying to do is get the image up to a certain required size, pamcut may be what you want. @@ -70,7 +70,7 @@ over the individual margins and does only black and white margins.

    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 pamcut to make a nice rectangular image.

    If you're just trying to join (concatenate) two images at their edges, use -pnmcat. +pamcat.

    The left_filespec and right_filespec arguments are the specifications (names) of the PNM files containing the left hand and @@ -110,7 +110,7 @@ about the stitching process.

    SEE ALSO

    pamcut, -pnmcat, +pamcat, pamflip, pnm, 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.

    You can do pretty much the reverse with pamdice.

    You can explicitly concatenate an image to itself (or anything else) -with pnmcat. +with pamcat.

    If you're trying to tile multiple images into a superimage, see pamundice or (for a thumbnail sheet) pnmindex. @@ -43,7 +43,7 @@ Common Options.)

    SEE ALSO

    pamundice, -pnmcat, +pamcat, pamdice, pnmindex, pampop9, 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. -phys/-size as an example, is that -phys takes multiple program arguments as the option argument, whereas -size takes a single program argument which is composed of multiple words. -E.g. The old shell command +E.g. the old shell command
     
    @@ -320,7 +320,7 @@ of those 3 primary illuminants and of white (i.e. full strength of
     all three).
     
     

    The chroma_list 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.

    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 >lower.ppm #and concatenate the two pieces - pnmcat -topbottom upper.ppm lower.ppm >newpic.ppm + pamcat -topbottom upper.ppm lower.ppm >newpic.ppm

    @@ -71,7 +71,7 @@ surface with slight ripples. pamcut, pamflip, ppmdim, -pnmcat +pamcat

    AUTHOR

    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. -

    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 +

    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 ppmtomitsu uses if there are no +more than 256 colors in the image. ppmtomitsu tries to position your +image at 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 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's memory; ppmtomitsu doesn't use this function because +pamcat 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 enlarge, etc., but I don't think that +is valuable enough to warrant a change in the program.

    For proper results, the input maxval must be 255. Use pamdepth to ensure that it is. -- cgit 1.4.1