From 1feb4eb4d9783d530653f6e6ac8bc4264732501d Mon Sep 17 00:00:00 2001 From: giraffedata Date: Sat, 25 Dec 2021 19:59:15 +0000 Subject: miscellaneous update git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@4217 9d0c8265-081b-0410-96cb-a4ca84ce46f8 --- pamexec.html | 21 +++++++++++---------- pnmpad.html | 14 ++++++++++---- 2 files changed, 21 insertions(+), 14 deletions(-) diff --git a/pamexec.html b/pamexec.html index 579a018a..95a432c1 100644 --- a/pamexec.html +++ b/pamexec.html @@ -2,7 +2,7 @@ Pamexec User Manual

pamexec

-Updated: 11 August 2011 +Updated: 21 December 2021
Table Of Contents @@ -35,13 +35,13 @@ Input (with a pipe).

netpbmfile is the file name of the input file, or - to indicate Standard Input. The default is Standard Input. -

Many Netpbm programs understand multimage Netpbm streams themselves, -so you don't need to use pamexec to run the program on the images -in the stream. Ideally, all Netpbm programs would have that capability, -but multi-image streams are a relatively recent invention, so older Netpbm -programs just process the first image in the stream and then stop. Even -recently written Netpbm programs work that way, since the authors aren't -aware of the multi-image possibility. +

Many Netpbm programs understand multimage Netpbm streams themselves, so you +don't need to use pamexec to run the program on the images in the +stream. Ideally, all Netpbm programs would have that capability, but +multi-image streams are a relatively recent invention, so older Netpbm +programs just process the first image in the stream and then stop. Even many +recently written Netpbm programs work that way, since the authors aren't aware +of the multi-image possibility.

Another way to process a multi-image stream is to use pamsplit to explode it into multiple files, one image per file. You can then process @@ -81,11 +81,12 @@ To make an animated GIF movie:

pamexec assumes all commands consume all of Standard Input. If yours doesn't (perhaps it just exits when it's seen enough), -you can buffer through a temporary file like this: + you can buffer through a temporary file like this, which copies the + first 3 lines of every image (the PPM header) to Standard Output:

 
-    pamexec "cat >/tmp/x; head -3 x" myvideo.ppm  
+    pamexec "cat >/tmp/x; head --lines=3 x" myvideo.ppm

diff --git a/pnmpad.html b/pnmpad.html index 7847a502..c48b55f5 100644 --- a/pnmpad.html +++ b/pnmpad.html @@ -2,7 +2,7 @@ Pnmpad User Manual

pnmpad

-Updated: 05 October 2019 +Updated: 25 December 2021
Table Of Contents @@ -123,13 +123,19 @@ between the left and right sides of the image to maintain the ratio the other options produce. E.g. if you say -left=10 -right=10 -mwidth=50 with a 100-pixel image, you end up with a 150-pixel image with the extra padding split evenly between left and right for a total of 25 pixels of padding -on the left and 25 on the right. +on the left and 25 on the right. If the other options indicate no +padding, pnmpad adds padding in the ratio specified by -halign +and if -halign is not specified, equally on both sides. + +

Before Netpbm 10.97 (December 2021), pnmpad does not allow +-halign with -mwidth and adds padding only on the right +when -mwidth is specified and the other options indicate no padding. + +

Before Netpbm 10.72 (September 2015), there is no -mwidth.

Before Netpbm 10.23 (July 2004), pnmpad did not allow the -left or -right option together with -width. -

Before Netpbm 10.72 (September 2015), there is no -mwidth. -

-top=pixels

-bottom=pixels

-height=height -- cgit 1.4.1