diff options
author | giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8> | 2012-12-04 16:28:05 +0000 |
---|---|---|
committer | giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8> | 2012-12-04 16:28:05 +0000 |
commit | 1f57a21b958487ffdea229f114724e10034ca1b3 (patch) | |
tree | dedb61e8e4f19cb65f725fcd38320be8046ebec9 | |
parent | b0a367f8fd947b52fc2ab0d47b62303584d18f05 (diff) | |
download | netpbm-mirror-1f57a21b958487ffdea229f114724e10034ca1b3.tar.gz netpbm-mirror-1f57a21b958487ffdea229f114724e10034ca1b3.tar.xz netpbm-mirror-1f57a21b958487ffdea229f114724e10034ca1b3.zip |
miscellaneous update
git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@1794 9d0c8265-081b-0410-96cb-a4ca84ce46f8
-rw-r--r-- | libnetpbm_ug.html | 13 | ||||
-rw-r--r-- | libpbm.html | 5 | ||||
-rw-r--r-- | libpgm.html | 4 | ||||
-rw-r--r-- | libpnm.html | 5 | ||||
-rw-r--r-- | libppm.html | 4 | ||||
-rw-r--r-- | 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. <h3><b>libnetpbm classes</b></h3> -<p>In this section, we cover only the PAM functions in -<b>libnetpbm</b>. As described in <a href="libnetpbm.html">the +<p>In this section, Guide To Using Libnetpbm, we cover only the PAM functions +in <b>libnetpbm</b>. As described in <a href="libnetpbm.html">the introduction to <b>libnetpbm</b></a>, 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. </ul> + +<h3 id="initialization">Library Initialization</h3> + +<p>Every program that uses the library must initialize the library, i.e. set +up the process to use the library, as described in <a href="libpm.html#initialization">Initialization</a>. That is the purpose of the call to +<b>pm_init()</b> in the example above. + + + <H3 id="pamstruct">THE pam STRUCTURE</H3> <P>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 <B>PBM_BLACK</B>. <H3 id="initialization">INITIALIZATION</H3> -<P><b>pbm_init()</b> is identical to <b>pm_proginit</b>. +<p><b>pbm_init()</b> is obsolete (at least since Netpbm 9.25 (March 2002)). +Use <a href="libpm.html#initialization"><b>pm_proginit()</b></a> instead. -<p><b>pbm_init()</b> is obsolete. Use <b>pm_proginit()</b> instead. +<P><b>pbm_init()</b> is identical to <b>pm_proginit</b>. <H3 id="memorymanagement">MEMORY MANAGEMENT</H3> 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. <H3 id="initialization">INITIALIZATION</H3> +<p><b>pgm_init()</b> is obsolete (at least since Netpbm 9.25 (March 2002). +Use <b>pm_proginit()</b> instead. + <P><b>pgm_init()</b> is identical to <b>pm_proginit</b>. -<p><b>pgm_init()</b> is obsolete. Use <b>pm_proginit()</b> instead. <H3 id="memorymanagement">MEMORY MANAGEMENT</H3> 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 <I>maxval</I> and <H3 id="initialization">INITIALIZATION</H3> -<P><b>pnm_init()</b> is identical to <b>pm_proginit</b>. +<p><b>pnm_init()</b> is obsolete (at least since Netpbm 9.25 (March 2002). +Use <b>pm_proginit()</b> instead. -<p><b>pnm_init()</b> is obsolete. Use <b>pm_proginit()</b> instead. +<P><b>pnm_init()</b> is identical to <b>pm_proginit</b>. <H3 id="memorymanagement">MEMORY MANAGEMENT</H3> 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. <H3 id="initialization">INITIALIZATION</H3> +<p><b>ppm_init()</b> is obsolete (at least since Netpbm 9.25 (March 2002). +Use <b>pm_proginit()</b> instead. + <P><b>ppm_init()</b> is identical to <b>pm_proginit</b>. -<p><b>ppm_init()</b> is obsolete. Use <b>pm_proginit()</b> instead. <H3 id="memorymanagement">MEMORY MANAGEMENT</H3> diff --git a/pnmmontage.html b/pnmmontage.html index f3795dfa..29b3d6ac 100644 --- a/pnmmontage.html +++ b/pnmmontage.html @@ -119,7 +119,7 @@ is <B>-quality=200.</B> <DT><B>-0</b>, <b>-1</b>, ... <b>-9</B> <DD>These options control the quality at a higher level than -<B>-q</B>; <B>-0</B> is the worst quality (literally pick the first +<B>-quality</B>; <B>-0</B> is the worst quality (pick the first solution found), while <B>-9</B> 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 <H2 id="notes">NOTES</H2> -<p>Using <B>-9</B> 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. +<p>Using <B>-9</B> is very slow on all but the smallest image sets. <p>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 |