From 1f57a21b958487ffdea229f114724e10034ca1b3 Mon Sep 17 00:00:00 2001 From: giraffedata Date: Tue, 4 Dec 2012 16:28:05 +0000 Subject: miscellaneous update git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@1794 9d0c8265-081b-0410-96cb-a4ca84ce46f8 --- libnetpbm_ug.html | 13 +++++++++++-- libpbm.html | 5 +++-- libpgm.html | 4 +++- libpnm.html | 5 +++-- libppm.html | 4 +++- pnmmontage.html | 7 ++----- 6 files changed, 25 insertions(+), 13 deletions(-) diff --git a/libnetpbm_ug.html b/libnetpbm_ug.html index 72be3d61..eba0dd28 100644 --- a/libnetpbm_ug.html +++ b/libnetpbm_ug.html @@ -59,8 +59,8 @@ Netpbm image input and produce a Netpbm image output.

libnetpbm classes

-

In this section, we cover only the PAM functions in -libnetpbm. As described in the +

In this section, Guide To Using Libnetpbm, we cover only the PAM functions +in libnetpbm. As described in the introduction to libnetpbm, there are four other classes of image processing functions (PBM, PGM, PPM, PNM). They are less important, since you can do everything more easily with the PAM @@ -87,6 +87,15 @@ functions require you to pass up to 5 pieces of image information (height, width, etc.) as separate arguments to every function. + +

Library Initialization

+ +

Every program that uses the library must initialize the library, i.e. set +up the process to use the library, as described in Initialization. That is the purpose of the call to +pm_init() in the example above. + + +

THE pam STRUCTURE

The PAM functions take most of their arguments in the form of a diff --git a/libpbm.html b/libpbm.html index 01c3d904..169668a0 100644 --- a/libpbm.html +++ b/libpbm.html @@ -141,9 +141,10 @@ or PBM_BLACK.

INITIALIZATION

-

pbm_init() is identical to pm_proginit. +

pbm_init() is obsolete (at least since Netpbm 9.25 (March 2002)). +Use pm_proginit() instead. -

pbm_init() is obsolete. Use pm_proginit() instead. +

pbm_init() is identical to pm_proginit.

MEMORY MANAGEMENT

diff --git a/libpgm.html b/libpgm.html index 83f34848..1edb75b8 100644 --- a/libpgm.html +++ b/libpgm.html @@ -162,9 +162,11 @@ code which is its argument.

INITIALIZATION

+

pgm_init() is obsolete (at least since Netpbm 9.25 (March 2002). +Use pm_proginit() instead. +

pgm_init() is identical to pm_proginit. -

pgm_init() is obsolete. Use pm_proginit() instead.

MEMORY MANAGEMENT

diff --git a/libpnm.html b/libpnm.html index 750013e2..3e918e0a 100644 --- a/libpnm.html +++ b/libpnm.html @@ -219,9 +219,10 @@ black xel, respectively, for the given maxval and

INITIALIZATION

-

pnm_init() is identical to pm_proginit. +

pnm_init() is obsolete (at least since Netpbm 9.25 (March 2002). +Use pm_proginit() instead. -

pnm_init() is obsolete. Use pm_proginit() instead. +

pnm_init() is identical to pm_proginit.

MEMORY MANAGEMENT

diff --git a/libppm.html b/libppm.html index e0667981..7bd7df6a 100644 --- a/libppm.html +++ b/libppm.html @@ -216,9 +216,11 @@ just look up the products in the tables.

INITIALIZATION

+

ppm_init() is obsolete (at least since Netpbm 9.25 (March 2002). +Use pm_proginit() instead. +

ppm_init() is identical to pm_proginit. -

ppm_init() is obsolete. Use pm_proginit() instead.

MEMORY MANAGEMENT

diff --git a/pnmmontage.html b/pnmmontage.html index f3795dfa..29b3d6ac 100644 --- a/pnmmontage.html +++ b/pnmmontage.html @@ -119,7 +119,7 @@ is -quality=200.
-0, -1, ... -9
These options control the quality at a higher level than --q; -0 is the worst quality (literally pick the first +-quality; -0 is the worst quality (pick the first solution found), while -9 is the best quality (perform an exhaustive search of problem space for the absolute best packing). The higher the number, the slower the computation. The default is @@ -130,10 +130,7 @@ The higher the number, the slower the computation. The default is

NOTES

-

Using -9 is excessively slow on all but the smallest image -sets. If the input images differ in maxvals, then pnmmontage will pick the -smallest maxval which is evenly divisible by each of the maxvals of -the original images. +

Using -9 is very slow on all but the smallest image sets.

The minimum area arrangement is often not a convenient shape. For example, it might be a tall, thin column of images, when you'd rather -- cgit 1.4.1