From 3f5173528a7f3e0dc237db27544e889b9282ff41 Mon Sep 17 00:00:00 2001 From: giraffedata Date: Tue, 16 Aug 2022 01:22:28 +0000 Subject: miscellaneous update git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@4412 9d0c8265-081b-0410-96cb-a4ca84ce46f8 --- pamcat.html | 72 +++++++++++++++++++++---------------------------------------- pnmcat.html | 66 +++++++------------------------------------------------- 2 files changed, 33 insertions(+), 105 deletions(-) diff --git a/pamcat.html b/pamcat.html index 6522396b..e7b580c0 100644 --- a/pamcat.html +++ b/pamcat.html @@ -16,8 +16,6 @@ pamcat - concatenate Netpbm images {-leftright | -lr | -topbottom | -tb} -[-extendplane] - [-white|-black] [-jtop|-jbottom|-jcenter] @@ -36,11 +34,8 @@ from its value.

This program is part of Netpbm.

pamcat reads one or more Netpbm images as input, concatenates them -either left to right or top to bottom, and produces a single PAM image -as output. - -

As an exception for greater efficiency, pamcat produces raw PBM -output if all of the input images are raw PBM. +either left to right or top to bottom, and produces a single Netpbm image as +output.

Options -leftright and -topbottom determine the direction of the concatenation. @@ -48,18 +43,24 @@ output if all of the input images are raw PBM.

The images do not have to be the same shape: You can concatenate images of different widths top to bottom and of different heights left to right. You can concatenate images of different depths (numbers of planes). You - can concatenate a PBM image with a PPM image. - -

Where the input images are of different depths, the depth of the output is - the maximum of the depths of the inputs. pamcat adds higher numbered - planes to the input images as padding. You can choose whether those higher - planes have all zero (black) sample values or duplicate the highest numbered - plane in the input. Use the -extendplane option for this. The - duplication function is useful when your inputs are visual images, without - transparency planes, because it effectively translates black and white - pixels from a 1-plane black and white input image to black and white pixels - in 3-plane color output and gray pixels from a 1-plane grayscale input image - to the same grays in 3-plane color output. + can concatenate a PBM image with a PPM image. Et cetera. + +

The format of the output image is the highest of the formats of the + input images, in the order PBM, PGM, PPM, PAM. + +

For PAM output, if all of the input images has the same tuple type + (including implied tuple types of PNM images), that is the tuple type of the + output. If the inputs differ, but are all visual tuple types, the + output's tuple type is the most primitive that can represent all the + input. E.g. if inputs are GRAYSCALE and RGB, the output is RGB, and if the + inputs are GRAYSCALE_ALPHA and RGB, the output is RGB_ALPHA. If the inputs + differ and are not all visual, the output tuple type is a null string. + +

When the output is PAM, its depth is the maximum of the depths of the + inputs (including implied depths of PNM images), but at least enough to + represent the tuple type specified above. In the case of nonvisual PAM + output, input images are padded to this output depth with higher numbered + planes of all zeroes.

Where the input images are of different widths and you concatenate top to bottom, pamcat generates output as wide as the widest of the @@ -78,6 +79,11 @@ output if all of the input images are raw PBM. likely background color, with possibly different colored padding for each input image. Control this with the -black and -white options. +

Where the output image contains transparency information (because at least + one of the input images does), the padding is opaque. (That is consistent + with the result for an output image without transparency information, because + such an image is defined to be opaque). +

The arguments are names of input files. Any one of these, but not more than one, may be "-" to indicate Standard Input. If you have no arguments, that means a single input image from Standard Input (and that is @@ -167,28 +173,6 @@ different for each image. -

Depth Extension

- -

This option controls what happens when the input image have different - depths (number of planes), so pamcat adds planes to the shallower - input images. - -
The default is to make the additional planes all zero. - -
-extendplane -: Make the additional planes copies of the highest numbered plane in the - input. -
This is appropriate whenever the input images are visual images without a - transparency plane. PBM, PGM, and PPM images are all examples of visual - images without a transparency plane. PAM images with tuple types - "BLACKANDWHITE", "GRAYSCALE", and "RGB" - are also examples. - -

- -

pnmcat

-Updated: 30 July 2022 +Updated: 13 August 2022

NAME

@@ -12,65 +12,15 @@ pnmcat - replaced by pamcat

This program is part of Netpbm. -

pnmcat was obsoleted by pamcat, -introduced with Netpbm 11.00 (September 2022). pamcat is almost -backward compatible with pnmcat, plus adds many additional functions, -including the ability to process PAM images. - -

These are the ways in which pamcat is not backward compatible with - pnmcat: - -

pamcat produces PAM output, whereas pnmcat produces PNM. - With pamcat, If your inputs are PNM and you want PNM output, you - can run the output through pamtopnm. But most Netpbm programs - that take PNM input can just as well take the PAM input, so this may not - be necessary. - -
pnmcat recognizes PBM, PGM, and PPM input images as visual - images and makes sure the images are the same in the concatenated - outputs even though the output may be a different format. For example, - if you are concatenating PBM image foo.pbm and PPM image bar.ppm, the - resulting image will be PPM and the foo part of it will have the same - black and white pixels as the foo.pbm input. - -
pamcat, on the other hand, work on generic PAM images and does - not really recognize colors. It sees a PBM input as a 1-plane image - and a PPM input as a 3-plane image and produces a 3-plane output - image. By default, in the example above, the foo part of the output - contains the black and white sample values in its first plane, but - zeroes in its second and third planes, which means if you take the - output image to be a PPM-like color visual image, the foo part is - black and red instead of black and white. - -
But this is easy to fix. Use the -extendplane option to say - instead of making those additional planes zero, make them copies of - the first plane. So the three panes in the foo part of the output - image will all contain the same sample values as the single plane of - the PBM input, which means if you use the output image as a color - image, those pixels are black and white. -

- -

For full backward compatibility, pnmcat remains in Netpbm, - implemented as a simple wrapper of pamcat. For the fewest problems - with future releases of Netpbm, you should not use pnmcat in any - new work. - - -

Using pnmcat in old Netpbm

pnmcat was obsoleted by pamcat, introduced with Netpbm 11.00 +(September 2022). pamcat is backward compatible with pnmcat, +plus adds many additional functions, including the ability to process PAM +images.

In Netpbm before 11.00, use the manual for pamcat with -pnmcat, observing the following differences: - -

pnmcat accepts only PNM input (i.e. PBM, PGM, or PPM) - and produces only PNM output. The output is the highest format - (PBM, PGM, PPM) of any of its inputs. - -
Features that the manual says were added to pamcat - in Release 11.00 or later are not there. -

- +pnmcat. Features that are in pamcat but not pnmcat +are indicated by statements that they didn't exist before 11.00. -- cgit 1.4.1

Depth Extension

SEE ALSO

Table Of Contents

pnmcat

NAME

Using pnmcat in old Netpbm