miscellaneous update

git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@3905 9d0c8265-081b-0410-96cb-a4ca84ce46f8
author: giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8> 2020-08-02 18:44:01 +0000
committer: giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8> 2020-08-02 18:44:01 +0000
commit: ad48d09aa16cf2c106ba4d0e232c703a75ab5c49 (patch)
tree: 67fe02ab9d4f8952d6ac8b0aac1674f099f0fd7e /ppmtompeg.html
parent: 56ef5a9528e4eb818db26d7cee8733d46d6cb687 (diff)
download: netpbm-mirror-ad48d09aa16cf2c106ba4d0e232c703a75ab5c49.tar.gz
netpbm-mirror-ad48d09aa16cf2c106ba4d0e232c703a75ab5c49.tar.xz
netpbm-mirror-ad48d09aa16cf2c106ba4d0e232c703a75ab5c49.zip
1 files changed, 321 insertions, 313 deletions
diff --git a/ppmtompeg.html b/ppmtompeg.html
index 3759ad55..af5a8d71 100644
--- a/ppmtompeg.html
+++ b/ppmtompeg.html
@@ -1,28 +1,25 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<HTML>
-<HEAD>
-<TITLE>Ppmtompeg User Manual</TITLE>
-</HEAD>
-<BODY>
-<H1>Ppmtompeg</H1>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.3//EN">
+<html><head><title>Ppmtompeg User Manual</title></head>
+<body>
+<h1>ppmtompeg</h1>
 Updated: 23 July 2006
-<BR>
-<A HREF="#index">Table Of Contents</A>
+<br>
+<a href="#index">Table Of Contents</a>
 
-<H2>NAME</H2>
+<h2>NAME</h2>
 ppmtompeg - encode an MPEG-1 bitstream
 
-<H2 id="synopsis">SYNOPSIS</H2>
+<h2 id="synopsis">SYNOPSIS</h2>
 
-<B>ppmtompeg</B>
-[<I>options</I>]
-<I>parameter-file</I>
+<b>ppmtompeg</b>
+[<i>options</i>]
+<i>parameter-file</i>
 
-<H2 id="description">DESCRIPTION</H2>
+<h2 id="description">DESCRIPTION</h2>
 
 <p>This program is part of <a href="index.html">Netpbm</a>.
 
-<P><B>ppmtompeg</B> produces an MPEG-1 video stream.  MPEG-1 is the
+<p><b>ppmtompeg</b> produces an MPEG-1 video stream.  MPEG-1 is the
 first great video compression method, and is what is used in Video CDs
 (VCD).  <b>ppmtompeg</b> originated in the year 1995.  DVD uses a more
 advanced method, MPEG-2.  There is an even newer method called MPEG-4
@@ -48,21 +45,21 @@ stream.
 input files and other parameters.  The file is described in detail
 below.
 
-<P>To understand this program, you need to understand something about
+<p>To understand this program, you need to understand something about
 the complex MPEG-1 format.  One source of information about this
 standard format is the section Introduction to MPEG in the <a
 href="http://www.faqs.org/faqs/compression-faq">Compression FAQ</a>.
 
-<H2 id="options">OPTIONS</H2>
+<h2 id="options">OPTIONS</h2>
 
 <p>The <b>-gop</b>, <b>-combine_gops</b>, <b>-frames</b>, and
 <b>-combine_frames</b> options are all mutually exclusive.
 
-<DL COMPACT>
-<DT><B>-stat stat_file</B>
+<dl compact>
+<dt><b>-stat stat_file</b>
 
-<DD>This option causes <b>ppmtompeg</b> to append the statistics that
-it write to Standard Output to the file <I>stat_file</I> as well.  The
+<dd>This option causes <b>ppmtompeg</b> to append the statistics that
+it write to Standard Output to the file <i>stat_file</i> as well.  The
 statistics use the following abbreviations: bits per block (bpb), bits
 per frame (bpf), seconds per frame (spf), and bits per second (bps).
 
@@ -70,40 +67,41 @@ per frame (bpf), seconds per frame (spf), and bits per second (bps).
 and information about compression and quality.
 
 
-<DT><B>-quiet</b> <i>num_seconds</i>
+<dt><b>-quiet</b> <i>num_seconds</i>
 
-<DD> causes <b>ppmtompeg</b> not to report remaining time more often
+<dd> causes <b>ppmtompeg</b> not to report remaining time more often
 than every <i>num_seconds</i> seconds (unless the time estimate rises,
 which will happen near the beginning of the run).  A negative value
 tells <b>ppmtompeg</b> not to report at all.  0 is the default
 (reports once after each frame).  Note that the time remaining is an
 estimate and does not take into account time to read in frames.
 
-<DT><B>-realquiet</B> <DD> causes <b>ppmtompeg</b> to run silently,
+<dt><b>-realquiet</b> <dd> causes <b>ppmtompeg</b> to run silently,
 with the only screen output being errors.  Particularly useful when
-reading input from stdin.
+reading input from stdin.  The equivalent of the <b>-quiet</b>
+common option of most other Netpbm programs.
 
-<DT>
-<B>-no_frame_summary</B>
+<dt>
+<b>-no_frame_summary</b>
 
-<DD> This option prevents <b>ppmtompeg</b> from printing a summary
+<dd> This option prevents <b>ppmtompeg</b> from printing a summary
 line for each frame
 
-<DT><B>-float_dct</B>
+<dt><b>-float_dct</b>
 
-<DD> forces <b>ppmtompeg</b> to use a more accurate, yet more
+<dd> forces <b>ppmtompeg</b> to use a more accurate, yet more
 computationally expensive version of the DCT.
 
-<DT><B>-gop</b> <i>gop_num</i>
-<DD>
+<dt><b>-gop</b> <i>gop_num</i>
+<dd>
 causes <b>ppmtompeg</b> to encode only the numbered GOP (first GOP is 0).  The
 parameter file is the same as for normal usage.  The output file will be
 the normal output file with the suffix <b>.gop.</b><i>gop_num</i>.
 <b>ppmtompeg</b> does not output any sequence information.
 
-<DT><B>-combine_gops</B>
+<dt><b>-combine_gops</b>
 
-<DD> causes <b>ppmtompeg</b> simply to combine some GOP files into a
+<dd> causes <b>ppmtompeg</b> simply to combine some GOP files into a
 single MPEG output stream.  <b>ppmtompeg</b> inserts a sequence header
 and trailer.  In this case, the parameter file needs only to contain 
 the SIZE value, an output file, and perhaps a list of input GOP
@@ -126,9 +124,9 @@ GOP files (<b>-gop</b>) and for later turning them into an MPEG stream
 (<b>-combine_gops</b>).
      
 
-<DT><B>-frames <i>first_frame</i> <i>last_frame</i></B>
+<dt><b>-frames <i>first_frame</i> <i>last_frame</i></b>
 
-<DD>This option causes <b>ppmtompeg</b> to encode only the frames numbered
+<dd>This option causes <b>ppmtompeg</b> to encode only the frames numbered
 <i>first_frame</i> to <i>last_frame</i>, inclusive.  The parameter
 file is the same as for normal usage.  The output will be placed in
 separate files, one per frame, with the file names being the normal
@@ -140,9 +138,9 @@ include the GOP_SIZE value)
 an MPEG stream.
 
 
-<DT><B>-combine_frames</B>
+<dt><b>-combine_frames</b>
 
-<DD> This option causes <b>ppmtompeg</b> simply to combine some
+<dd> This option causes <b>ppmtompeg</b> simply to combine some
 individual MPEG frames (such as you might have created with an earlier
 run of <b>ppmtompeg -frames</b>) into a single MPEG stream.  Sequence
 and GOP headers are inserted appropriately.  In this case, the
@@ -158,42 +156,42 @@ output file name with suffix <b>.frame.</b><i>frame_num</i>, with
      
 
 
-<DT><B>-nice</B>
+<dt><b>-nice</b>
 
-<DD>This option causes <b>ppmtompeg</b> to run any remote processes
+<dd>This option causes <b>ppmtompeg</b> to run any remote processes
 "nicely," i.e.  at low priority.  (This is relevant only if you are
 running <b>ppmtompeg</b> in parallel mode.  Otherwise, there are no
 remote processes).  See 'man nice.'
 
-<DT><B>-max_machines <i>num_machines</i></B>
+<dt><b>-max_machines <i>num_machines</i></b>
 
-<DD>This option causes <b>ppmtompeg</b> to use no more than
+<dd>This option causes <b>ppmtompeg</b> to use no more than
 <i>num_machines</i> machines as slaves for use in parallel encoding.
 
-<DT><B>-snr</B> 
+<dt><b>-snr</b> 
 
-<DD>This option causes <b>ppmtompeg</b> to include the signal-to-noise
+<dd>This option causes <b>ppmtompeg</b> to include the signal-to-noise
 ratio in the reported statistics.  Prints SNR (Y U V) and peak SNR (Y
 U V) for each frame.  In summary, prints averages of luminance only
 (Y).  SNR is defined as 10*log(variance of original/variance of
 error).  Peak SNR is defined as 20*log(255/RMSE).  Note that
 <b>ppmtompeg</b> runs a little slower when you use this option.
 
-<DT><B>-mse</B>
+<dt><b>-mse</b>
 
-<DD>This option causes <b>ppmtompeg</b> to report the mean squared
+<dd>This option causes <b>ppmtompeg</b> to report the mean squared
 error per block.  It also automatically reports the quality of the
 images, so there is no need to specify <b>-snr</b> then.
 
-<DT><B>-bit_rate_info</b> <i>rate_file</i>
+<dt><b>-bit_rate_info</b> <i>rate_file</i>
 
-<DD> This option makes <b>ppmtompeg</b> write bit rate information
+<dd> This option makes <b>ppmtompeg</b> write bit rate information
 into the file <i>rate_file</i>.  Bit rate information is bits per frame, and
 also bits per I-frame-to-I-frame.
 
-<DT><B>-mv_histogram</B> 
+<dt><b>-mv_histogram</b> 
 
-<DD> This option causes <b>ppmtompeg</b> to print a histogram of the
+<dd> This option causes <b>ppmtompeg</b> to print a histogram of the
 motion vectors as part of statistics.  There are three histograms --
 one for P frame, one for forward B frame, and one for backward B frame
 motion vectors.
@@ -215,19 +213,19 @@ messages that narrate the progress of the conversion on the various
 machines when you run <b>ppmtompeg</b> in <a href="#parallel">parallel
 mode</a>.
      
-</DL>
+</dl>
 
-<H2 id="parmfile">PARAMETER FILE</H2>
+<h2 id="parmfile">PARAMETER FILE</h2>
 
-<P>The parameter file <strong>must</strong> contain the following
+<p>The parameter file <strong>must</strong> contain the following
 lines (except when using the <b>-combine_gops</b> or <b>-combine_frames</b>
 options):
 
-<DL COMPACT>
+<dl compact>
 
-<DT><B>PATTERN</b> <i>pattern</i>
+<dt><b>PATTERN</b> <i>pattern</i>
 
-<DD>This statement specifies the pattern (sequence) of I frames, P frames,
+<dd>This statement specifies the pattern (sequence) of I frames, P frames,
 and B frames.  <i>pattern</i> is just a sequence of the letters I, P, and
 B with nothing between.  Example:
 
@@ -237,12 +235,12 @@ B with nothing between.  Example:
 
 <p>See <a href="#ipb">I Frames, P Frames, B Frames</a>.
 
-<DT><B>OUTPUT</b> <i>output file</i>
-<DD>This names the file where the output MPEG stream goes.
+<dt><b>OUTPUT</b> <i>output file</i>
+<dd>This names the file where the output MPEG stream goes.
      
-<DT><B>INPUT_DIR</b> <i>directory</i>
+<dt><b>INPUT_DIR</b> <i>directory</i>
 
-<DD>This statement tells where the input images (frames) come from.
+<dd>This statement tells where the input images (frames) come from.
 If each frame is in a separate file, <i>directory</i> is the directory
 where they all are.  You may use <b>.</b> to refer to the current 
 directory.  A null <i>directory</i> refers to the root directory of the
@@ -254,10 +252,10 @@ Input, specify
     INPUT_DIR stdin
 </pre>
 
-<DT><B>INPUT</b>
-<DD>
+<dt><b>INPUT</b>
+<dd>
 This line must be followed by a list of the input files (in display order)
-and then the line <B>END_INPUT</B>.
+and then the line <b>END_INPUT</b>.
 
 <p>There are three types of lines between INPUT and END_INPUT.  First,
 a line may simply be the name of an input file.  Second, the line
@@ -291,13 +289,13 @@ Bourne Shell, like this:
 
 <p>
 If input is from Standard Input (per the <b>INPUT_DIR</b> statement), 
-<b>ppmtompeg</b> ignores the <B>INPUT</b>/<b>END_INPUT</b> block, but
+<b>ppmtompeg</b> ignores the <b>INPUT</b>/<b>END_INPUT</b> block, but
 it still must be present.
      
-<DT><b>BASE_FILE_FORMAT</b> {<b>PPM</b> | <b>PNM</b> | <b>YUV</b> | 
+<dt><b>BASE_FILE_FORMAT</b> {<b>PPM</b> | <b>PNM</b> | <b>YUV</b> | 
      <b>JPEG</b> | <b>JMOVIE</b>}
 
-<DD><B>ppmtompeg</b> must convert all input files to one of the
+<dd><b>ppmtompeg</b> must convert all input files to one of the
 following formats as a first step of processing: PNM, YUV, JPEG(v4),
 or JMOVIE.  (The conversion may be trivial if your input files are
 already in one of these formats).  This line specifies which of the
@@ -305,9 +303,9 @@ four formats.  PPM is actually a subset of PNM.  The separate
 specification is allowed for backward compatibility.  Use PNM instead
 of PPM in new applications.
 
-<DT><b>INPUT_CONVERT</b> <i>conversion_command</i>
+<dt><b>INPUT_CONVERT</b> <i>conversion_command</i>
 
-<DD>You must specify how to convert a file to the base file format.
+<dd>You must specify how to convert a file to the base file format.
 If no conversion is necessary, then you would just say:
 
      <pre>
@@ -315,7 +313,7 @@ If no conversion is necessary, then you would just say:
      </pre>
      
 <p>Otherwise, <i>conversion_command</i> is a shell command that causes
-an image in the format your specified with <B>BASE_FILE_FORMAT</b> to
+an image in the format your specified with <b>BASE_FILE_FORMAT</b> to
 be written to Standard Output.  <b>ppmtompeg</b> executes the command
 once for each line between <b>INPUT</b> and <b>END_INPUT</b> (which is
 normally, but not necessarily, a file name).  In the conversion
@@ -342,7 +340,7 @@ line.
 
 as described above.
      
-<DT><b>SIZE</b> <i>width</i><b>x</b><i>height</i>
+<dt><b>SIZE</b> <i>width</i><b>x</b><i>height</i>
 
 <dd>
 
@@ -360,21 +358,21 @@ processes in the network have access to the image files, so
 <b>SIZE</b> is required and must give the same dimensions as the
 input image files.
 
-<DT><b>YUV_SIZE</b> <i>width</i><b>x</b><i>height</i>
+<dt><b>YUV_SIZE</b> <i>width</i><b>x</b><i>height</i>
 
 <dd>This is an obsolete synonym of <b>SIZE</b>.
 
-<DT><b>YUV_FORMAT</B> {<b>ABEKAS</b> | <b>PHILLIPS</b> | <b>UCB</B> |
+<dt><b>YUV_FORMAT</b> {<b>ABEKAS</b> | <b>PHILLIPS</b> | <b>UCB</b> |
                       <b>EYUV</b> | <i>pattern</i>}
 
-<DD>This is meaningful only when <b>BASE_FILE_FORMAT</b> specifies
+<dd>This is meaningful only when <b>BASE_FILE_FORMAT</b> specifies
 YUV format, and then it is required.  It specifies the sub-format of
 the YUV class.
 
 
-<DT><b>GOP_SIZE</b> <i>n</i>
+<dt><b>GOP_SIZE</b> <i>n</i>
 
-<DD><i>n</i> is the number of frames in a Group of Pictures.  Except that
+<dd><i>n</i> is the number of frames in a Group of Pictures.  Except that
 because a GOP must start with an I frame, <b>ppmtompeg</b> makes a GOP as
 much longer than <i>n</i> as it has to to make the next GOP start with an
 I frame. 
@@ -385,59 +383,59 @@ statement).
 
 <p>See <a href="#gop">Group Of Pictures</a>.
 
-<DT><b>SLICES_PER_FRAME</b> <i>n</i>
+<dt><b>SLICES_PER_FRAME</b> <i>n</i>
 <dd><i>n</i> is roughly the number of slices per frame.  Note, at
 least one MPEG player may complain if slices do not start at the left
 side of an image.  To ensure this does not happen, make sure the
 number of rows is divisible by SLICES_PER_FRAME.
 
-<DT><b>PIXEL</b> {<b>FULL</b> | <b>HALF</b>} 
+<dt><b>PIXEL</b> {<b>FULL</b> | <b>HALF</b>} 
 
 <dd>use half-pixel motion vectors, or just full-pixel ones It is
 usually important that you use half-pixel motion vectors, because it
 results in both better quality and better compression.
      
 
-<DT><b>RANGE</b> <i>n</i>
+<dt><b>RANGE</b> <i>n</i>
 <dd>Use a search range of <i>n</i> pixels in each of the four directions
 from a subject pixel.  (So the search window is a square <i>n</i>*2 pixels
 on a side).
 
-<DT><b>PSEARCH_ALG</b> {<b>EXHAUSTIVE</B> | <b>TWOLEVEL</b> |
+<dt><b>PSEARCH_ALG</b> {<b>EXHAUSTIVE</b> | <b>TWOLEVEL</b> |
      <b>SUBSAMPLE</b> | <b>LOGARITHMIC</b>}
 
 <dd>This statement tells <b>ppmtompeg</b> what kind of search
     technique (algorithm) to use for P frames.  You select the desired
     combination of speed and compression.  <b>EXHAUSTIVE</b> gives the
-    best compression, but <b>LOGARITHMIC</B> is the fastest.
-    <B>TWOLEVEL</B> is an exhaustive full-pixel search, followed by a
+    best compression, but <b>LOGARITHMIC</b> is the fastest.
+    <b>TWOLEVEL</b> is an exhaustive full-pixel search, followed by a
     local half- pixel search around the best full-pixel vector (the
     PIXEL option is ignored for this search technique).
 
-<DT><b>BSEARCH_ALG</b> {<b>SIMPLE</B> | <B>CROSS2</B> | <B>EXHAUSTIVE</B>}
+<dt><b>BSEARCH_ALG</b> {<b>SIMPLE</b> | <b>CROSS2</b> | <b>EXHAUSTIVE</b>}
 
 <dd>This statement tells <b>ppmtompeg</b> what kind of search
-    technique (algorithm) to use for B frames.  <b>SIMPLE</B> means
+    technique (algorithm) to use for B frames.  <b>SIMPLE</b> means
     find best forward and backward vectors, then interpolate.
-    <B>CROSS2</B> means find those two vectors, then see what backward
+    <b>CROSS2</b> means find those two vectors, then see what backward
     vector best matches the best forward vector, and vice versa.
     <b>EXHAUSTIVE</b> does an n-squared search and is
     <em>extremely</em> slow in relation to the others (<b>CROSS2</b>
-    is about half as fast as <b>SIMPLE</B>).
+    is about half as fast as <b>SIMPLE</b>).
 
-<DT><b>IQSCALE</b> <i>n</i>
+<dt><b>IQSCALE</b> <i>n</i>
 <dd>Use <i>n</i> as the qscale for I frames.
      See <a href="#qscale">Qscale</a>.
 
-<DT><b>PQSCALE</b> <i>n</i>
+<dt><b>PQSCALE</b> <i>n</i>
 <dd>Use <i>n</i> as the qscale for P frames.
      See <a href="#qscale">Qscale</a>.
 
-<DT><b>BQSCALE</b> <i>n</i>
+<dt><b>BQSCALE</b> <i>n</i>
 <dd>Use <i>n</i> as the qscale for B frames.
      See <a href="#qscale">Qscale</a>.
 
-<DT><b>REFERENCE_FRAME</b> {<B>ORIGINAL</B> | <b>DECODED</b>} <dd>This
+<dt><b>REFERENCE_FRAME</b> {<b>ORIGINAL</b> | <b>DECODED</b>} <dd>This
 statement determines whether <b>ppmtompeg</b> uses the original images
 or the decoded images when computing motion vectors.  Using decoded
 images is more accurate and should increase the playback quality of
@@ -451,7 +449,7 @@ qscale (see <b>QSCALE</b> if the quality is not good enough.
   <caption>Original or Decoded? (Normalized)</caption>
 <?makeman r c c c c c. ?>
 <?makeman _ ?>
-  <tr align="center" bgcolor="#CCCCCC">
+  <tr style="text-align:center; background-color:#CCCCCC">
     <th>Reference</th>
     <th>Compression</th>
     <th>Speed</th>
@@ -460,20 +458,20 @@ qscale (see <b>QSCALE</b> if the quality is not good enough.
     <th>Quality B</th>
     </tr>
   <tr>
-    <td align="right">Decoded</td>
-    <td align="center">1000</td>
-    <td align="center">1000</td>
-    <td align="center">1000</td>
-    <td align="center">969</td>
-    <td align="center">919</td>
+    <td style="text-align:right">Decoded</td>
+    <td style="text-align:center">1000</td>
+    <td style="text-align:center">1000</td>
+    <td style="text-align:center">1000</td>
+    <td style="text-align:center">969</td>
+    <td style="text-align:center">919</td>
     </tr>
   <tr>
-    <td align="right">Original</td>
-    <td align="center">885</td>
-    <td align="center">1373</td>
-    <td align="center">1000</td>
-    <td align="center">912</td>
-    <td align="center">884</td>
+    <td style="text-align:right">Original</td>
+    <td style="text-align:center">885</td>
+    <td style="text-align:center">1373</td>
+    <td style="text-align:center">1000</td>
+    <td style="text-align:center">912</td>
+    <td style="text-align:center">884</td>
     </tr>
   </table>
 
@@ -483,9 +481,9 @@ qscale (see <b>QSCALE</b> if the quality is not good enough.
      
 <p>The following lines are optional:
 
-<DL>
+<dl>
 
-<DT><B>FORCE_ENCODE_LAST_FRAME</B>
+<dt><b>FORCE_ENCODE_LAST_FRAME</b>
 
 <dd>This statement is obsolete.  It does nothing.
 
@@ -497,7 +495,7 @@ that from happening and get the same function that <b>ppmtompeg</b>
 has today.
 
 
-<DT><b>NIQTABLE</b>
+<dt><b>NIQTABLE</b>
 
 <dd>This statement specifies a custom non-intra quantization table.
 If you don't specify this statement, <b>ppmtompeg</b> uses a default
@@ -508,11 +506,11 @@ The 8 lines immediately following <b>NIQTABLE</b> specify the quantization
 table.  Each line defines a table row and consists of 8 integers,
 whitespace-delimited, which define the table columns.
 
-<DT><B>IQTABLE</b>
+<dt><b>IQTABLE</b>
 
 <dd>This is analogous to NIQTABLE, but for the intra quantization table.
 
-<DT><b>ASPECT_RATIO</b> <i>ratio</i>
+<dt><b>ASPECT_RATIO</b> <i>ratio</i>
 
 <dd>This statement specifies the aspect ratio for <b>ppmtompeg</b> to
 specify in the MPEG output.  I'm not sure what this is used for.
@@ -520,18 +518,18 @@ specify in the MPEG output.  I'm not sure what this is used for.
 <p><i>ratio</i> must be 1.0, 0.6735, 0.7031, 0.7615, 0.8055, 0.8437,
 0.8935, 0.9157, 0.9815, 1.0255, 1.0695, 1.0950, 1.1575, or 1.2015.
 
-<DT><b>FRAME_RATE</b> <i>rate</i>
+<dt><b>FRAME_RATE</b> <i>rate</i>
 <dd>This specifies the frame rate for <b>ppmtompeg</b> to specify in the
 MPEG output.  Some players use this value to determine the playback rate.
 
 <p><i>rate</i> must be 23.976, 24, 25, 29.97, 30, 50, 59.94, or 60.
 
-<DT><b>BIT_RATE</b> <i>rate</i>
-<DD>This specifies the bit rate for Constant Bit Rate (CBR) encoding.
+<dt><b>BIT_RATE</b> <i>rate</i>
+<dd>This specifies the bit rate for Constant Bit Rate (CBR) encoding.
 
 <p><i>rate</i> must be an integer.
 
-<DT><b>BUFFER_SIZE</b> <i>size</i> 
+<dt><b>BUFFER_SIZE</b> <i>size</i> 
 
 <dd>This specifies the value
 <b>ppmtompeg</b> is to specify in the MPEG output for the Video
@@ -545,42 +543,42 @@ the required constant playback speed.
 process in terms of how many bits would be in the VBV as each frame gets
 decoded, assuming a VBV of the size you indicate.  
 
-<P>If you specify the <b>WARN_VBV_UNDERFLOW</b> statement,
+<p>If you specify the <b>WARN_VBV_UNDERFLOW</b> statement,
 <b>ppmtompeg</b> issues a warning each time the simulation underflows
 the buffer, which suggests that an underflow would occur on playback,
 which suggests the buffer is too small.
 
-<P>If you specify the <b>WARN_VBV_OVERFLOW</b> statement,
+<p>If you specify the <b>WARN_VBV_OVERFLOW</b> statement,
 <b>ppmtompeg</b> issues a warning each time the simulation overflows
 the buffer, which suggests that an overflow would occur on playback,
 which suggests the buffer is too small.
 
-<DT><B>WARN_VBV_UNDERFLOW</B>
-<DT><B>WARN_VBV_OVERFLOW</B>
+<dt><b>WARN_VBV_UNDERFLOW</b>
+<dt><b>WARN_VBV_OVERFLOW</b>
 
 <dd>See <b>BUFFER_SIZE</b>.
 
 <p>These options were new in Netpbm 10.26 (January 2005).  Before that,
 <b>ppmtompeg</b> issued the warnings always.
 
-</DL>
+</dl>
 
 
 The following statements apply only to parallel operation:
 
-<DL> 
+<dl> 
 
-<DT><b>PARALLEL</b>
+<dt><b>PARALLEL</b>
 
-<dd>This statement, paired with <b>END PARALLEL</B>, is what causes
+<dd>This statement, paired with <b>END PARALLEL</b>, is what causes
 <b>ppmtompeg</b> to operate in parallel mode.  See <a
 href="#parallel">Parallel Operation</a>.
 
 <dt><b>END PARALLEL</b>
 
-<DD>This goes with <b>PARALLEL</b>.
+<dd>This goes with <b>PARALLEL</b>.
 
-<DT><b>PARALLEL_TEST_FRAMES</b> <i>n</i> 
+<dt><b>PARALLEL_TEST_FRAMES</b> <i>n</i> 
 
 <dd>The master starts off by measuring each slave's speed.  It does
 this by giving each slave <i>n</i> frames to encode and noting how
@@ -598,7 +596,7 @@ the test frames value enough to maintain the alignment.
 number of test frames, <b>ppmtompeg</b> will give some slaves fewer.
 
 
-<DT><b>PARALLEL_TIME_CHUNKS</b> <i>t</i>
+<dt><b>PARALLEL_TIME_CHUNKS</b> <i>t</i>
 
 <dd>When you specify this statement, the master attempts to feed work
 to the slaves in chunks that take <i>t</i> seconds to process.  It uses
@@ -613,9 +611,9 @@ balancing.  The default is 30 seconds.
 <p>You may specify only one of PARALLEL_TIME_CHUNKS, PARALLEL_CHUNK_TAPER,
 and PARALLEL_PERFECT.  PARALLEL_CHUNK_TAPER is usually best.
 
-<DT><b>PARALLEL_CHUNK_TAPER</b>
+<dt><b>PARALLEL_CHUNK_TAPER</b>
 
-<DD>When you specify this statement, the master distributes work like
+<dd>When you specify this statement, the master distributes work like
 with PARALLEL_TIME_CHUNKS, except that the master chooses the number
 of seconds for the chunks.  It starts with a large number and, as it
 gets closer to finishing the job, reduces it.  That way, it reduces
@@ -628,7 +626,7 @@ there's still work to do.
 and PARALLEL_PERFECT.  PARALLEL_CHUNK_TAPER is usually best.
 
 
-<DT><b>PARALLEL_PERFECT</b>
+<dt><b>PARALLEL_PERFECT</b>
 
 <dd>If this statement is present, <b>ppmtompeg</b> schedules on the
 assumption that each machine is about the same speed.  The master will
@@ -647,9 +645,9 @@ the Combine Server and thus can increase the total elapsed time.
 <p>You may specify only one of PARALLEL_TIME_CHUNKS, PARALLEL_CHUNK_TAPER,
 and PARALLEL_PERFECT.  PARALLEL_CHUNK_TAPER is usually best.
 
-<DT><b>RSH</b> <i>remote_shell_command</i>
+<dt><b>RSH</b> <i>remote_shell_command</i>
 
-<DD><b>ppmtompeg</b> executes the shell command
+<dd><b>ppmtompeg</b> executes the shell command
 <i>remote_shell_command</i> to start a process on another machine.
 The default command is <b>rsh</b>, and whatever command you specify
 must have compatible semantics.  <b>ssh</b> is usually compatible.
@@ -662,7 +660,7 @@ where needed.  Otherwise, you'll have to type in passwords.
 <p>On some HP machines, <b>rsh</b> is the restricted shell, and you want
 to specify <b>remsh</b>.
 
-<DT><b>FORCE_I_ALIGN</b>
+<dt><b>FORCE_I_ALIGN</b>
 
 <dd>This statement forces each slave to encode a chunk of frames which
 is a multiple of the pattern length (see <b>PATTERN</b>).  Since the
@@ -675,7 +673,7 @@ would use (and was required to be a multiple of the pattern length).
 But <b>ppmtompeg</b> has apparently always ignored that argument, and
 it does now.
 
-<DT><B>KEEP_TEMP_FILES</B>
+<dt><b>KEEP_TEMP_FILES</b>
 
 <dd>This statement causes <b>ppmtompeg</b> not to delete the temporary
 files it uses to transmit encoded frames to the combine server.  This
@@ -689,12 +687,12 @@ between the servers.
 
 <p>This option was new in Netpbm 10.26 (January 2005).
 
-</DL>
+</dl>
 
 
-<H3>Parameter File Notes</h3>
+<h3 id="parameterfile">Parameter File Notes</h3>
 
-<P> If you use the <b>-combine_gops</b> option, then you need to specify
+<p> If you use the <b>-combine_gops</b> option, then you need to specify
 only the SIZE and OUTPUT values in the parameter file.  In
 addition, the parameter file may specify input GOP files in the same
 manner as normal input files -- except instead of using INPUT_DIR,
@@ -719,27 +717,27 @@ those between INPUT and END_INPUT.  This allows you to use the same
 parameter file for normal usage and for <b>-combine_gops</b> and
 <b>-combine_frames</b>.
 
-<P>The file format is case-sensitive so all keywords should be in
+<p>The file format is case-sensitive so all keywords should be in
 upper case.
 
-<P>The statements may appear in any order, except that the order within
+<p>The statements may appear in any order, except that the order within
 a block statement (such as INPUT ... END INPUT) is significant.
 
-<P><b>ppmtompeg</b> is prepared to handle up to 16 B frames between
+<p><b>ppmtompeg</b> is prepared to handle up to 16 B frames between
 reference frames when encoding with input from stdin.  (To build a
 modified <b>ppmtompeg</b> with a higher limit, change the constant
 B_FRAME_RUN in frame.c and recompile).
 
-<H2 id="general">GENERAL USAGE INFORMATION</H2>
+<h2 id="general">GENERAL USAGE INFORMATION</h2>
 
-<H3 id="qscale">Qscale</h3>
+<h3 id="qscale">Qscale</h3>
 
 <p>The quantization scale values (qscale) give a trade-off between
 quality and compression.  Using different Qscale values has very little
 effect on speed.  The qscale values can be set separately for I, P, and
 B frames.
 
-<p>You select the qscale values with the <B>IQSCALE</b>,
+<p>You select the qscale values with the <b>IQSCALE</b>,
 <b>PQSCALE</b>, and <b>BSCALE</b> parameter file statements.
 
 <p>A qscale value is an integer from 1 to 31.  Larger numbers give
@@ -755,53 +753,53 @@ where MSE is the mean squared error.
   <caption>Qscale vs Quality</caption>
 <?makeman r r r r. ?>
 <?makeman _ ?>
-  <tr align="center">
+  <tr style="text-align:center">
     <th>Qscale</th>
     <th>I Frames</th>
     <th>P Frames</th>
     <th>B Frames</th>
     </tr>
   <tr>
-    <td align="right">1</td>
-    <td align="right">43.2</td>
-    <td align="right">46.3</td>
-    <td align="right">46.5</td>
+    <td style="text-align:right">1</td>
+    <td style="text-align:right">43.2</td>
+    <td style="text-align:right">46.3</td>
+    <td style="text-align:right">46.5</td>
     </tr>
   <tr>
-    <td align="right">6</td>
-    <td align="right">32.6</td>
-    <td align="right">34.6</td>
-    <td align="right">34.3</td>
+    <td style="text-align:right">6</td>
+    <td style="text-align:right">32.6</td>
+    <td style="text-align:right">34.6</td>
+    <td style="text-align:right">34.3</td>
     </tr>
   <tr>
-    <td align="right">11</td>
-    <td align="right">28.6</td>
-    <td align="right">29.5</td>
-    <td align="right">30.0</td>
+    <td style="text-align:right">11</td>
+    <td style="text-align:right">28.6</td>
+    <td style="text-align:right">29.5</td>
+    <td style="text-align:right">30.0</td>
     </tr>
   <tr>
-    <td align="right">16</td>
-    <td align="right">26.3</td>
-    <td align="right">26.8</td>
-    <td align="right">28.6</td>
+    <td style="text-align:right">16</td>
+    <td style="text-align:right">26.3</td>
+    <td style="text-align:right">26.8</td>
+    <td style="text-align:right">28.6</td>
     </tr>
   <tr>
-    <td align="right">21</td>
-    <td align="right">24.7</td>
-    <td align="right">25.0</td>
-    <td align="right">27.9</td>
+    <td style="text-align:right">21</td>
+    <td style="text-align:right">24.7</td>
+    <td style="text-align:right">25.0</td>
+    <td style="text-align:right">27.9</td>
     </tr>
   <tr>
-    <td align="right">26</td>
-    <td align="right">23.5</td>
-    <td align="right">23.9</td>
-    <td align="right">27.5</td>
+    <td style="text-align:right">26</td>
+    <td style="text-align:right">23.5</td>
+    <td style="text-align:right">23.9</td>
+    <td style="text-align:right">27.5</td>
     </tr>
   <tr>
-    <td align="right">31</td>
-    <td align="right">22.6</td>
-    <td align="right">23.0</td>
-    <td align="right">27.3</td>
+    <td style="text-align:right">31</td>
+    <td style="text-align:right">22.6</td>
+    <td style="text-align:right">23.0</td>
+    <td style="text-align:right">27.3</td>
     </tr>
 </table>
 
@@ -809,58 +807,58 @@ where MSE is the mean squared error.
   <caption>Qscale vs Compression</caption>
 <?makeman r r r r. ?>
 <?makeman _ ?>
-  <tr align="center">
+  <tr style="text-align:center">
     <th>Qscale</th>
     <th>I Frames</th>
     <th>P Frames</th>
     <th>B Frames</th>
     </tr>
   <tr>
-    <td align="right">1</td>
-    <td align="right">2</td>
-    <td align="right">2</td>
-    <td align="right">2</td>
+    <td style="text-align:right">1</td>
+    <td style="text-align:right">2</td>
+    <td style="text-align:right">2</td>
+    <td style="text-align:right">2</td>
     </tr>
   <tr>
-    <td align="right">6</td>
-    <td align="right">7</td>
-    <td align="right">10</td>
-    <td align="right">15</td>
+    <td style="text-align:right">6</td>
+    <td style="text-align:right">7</td>
+    <td style="text-align:right">10</td>
+    <td style="text-align:right">15</td>
     </tr>
   <tr>
-    <td align="right">11</td>
-    <td align="right">11</td>
-    <td align="right">18</td>
-    <td align="right">43</td>
+    <td style="text-align:right">11</td>
+    <td style="text-align:right">11</td>
+    <td style="text-align:right">18</td>
+    <td style="text-align:right">43</td>
     </tr>
   <tr>
-    <td align="right">16</td>
-    <td align="right">15</td>
-    <td align="right">29</td>
-    <td align="right">97</td>
+    <td style="text-align:right">16</td>
+    <td style="text-align:right">15</td>
+    <td style="text-align:right">29</td>
+    <td style="text-align:right">97</td>
     </tr>
   <tr>
-    <td align="right">21</td>
-    <td align="right">19</td>
-    <td align="right">41</td>
-    <td align="right">173</td>
+    <td style="text-align:right">21</td>
+    <td style="text-align:right">19</td>
+    <td style="text-align:right">41</td>
+    <td style="text-align:right">173</td>
     </tr>
   <tr>
-    <td align="right">26</td>
-    <td align="right">24</td>
-    <td align="right">56</td>
-    <td align="right">256</td>
+    <td style="text-align:right">26</td>
+    <td style="text-align:right">24</td>
+    <td style="text-align:right">56</td>
+    <td style="text-align:right">256</td>
     </tr>
   <tr>
-    <td align="right">31</td>
-    <td align="right">28</td>
-    <td align="right">73</td>
-    <td align="right">330</td>
+    <td style="text-align:right">31</td>
+    <td style="text-align:right">28</td>
+    <td style="text-align:right">73</td>
+    <td style="text-align:right">330</td>
     </tr>
 </table>
 
 
-<h3>Search Techniques</h3>
+<h3 id="searchtech">Search Techniques</h3>
      
 <p>There are several different motion vector search techniques
 available.  There are different techniques available for P frame
@@ -882,35 +880,35 @@ some numbers comparing the different search methods:
   <caption>P frame Motion Vector Search (Normalized)</caption>
 <?makeman r c c c. ?>
 <?makeman _ ?>
-  <tr align="center">
+  <tr style="text-align:center">
     <th>Technique</th>
     <th>Compression<a href="#smallbetter"><sup>1</sup></a></th>
     <th>Speed      <a href="#largefaster"><sup>2</sup></a></th>
     <th>Quality    <a href="#largebetter"><sup>3</sup></a></th>
     </tr>
   <tr>
-    <td align="right">Exhaustive</td>
-    <td align="center">1000</td>
-    <td align="center">1000</td>
-    <td align="center">1000</td>
+    <td style="text-align:right">Exhaustive</td>
+    <td style="text-align:center">1000</td>
+    <td style="text-align:center">1000</td>
+    <td style="text-align:center">1000</td>
     </tr>
   <tr>
-    <td align="right">SubSample</td>
-    <td align="center">1008</td>
-    <td align="center">2456</td>
-    <td align="center">1000</td>
+    <td style="text-align:right">SubSample</td>
+    <td style="text-align:center">1008</td>
+    <td style="text-align:center">2456</td>
+    <td style="text-align:center">1000</td>
     </tr>
   <tr>
-    <td align="right">TwoLevel</td>
-    <td align="center">1009</td>
-    <td align="center">3237</td>
-    <td align="center">1000</td>
+    <td style="text-align:right">TwoLevel</td>
+    <td style="text-align:center">1009</td>
+    <td style="text-align:center">3237</td>
+    <td style="text-align:center">1000</td>
     </tr>
   <tr>
-    <td align="right">Logarithmic</td>
-    <td align="center">1085</td>
-    <td align="center">8229</td>
-    <td align="center">998</td>
+    <td style="text-align:right">Logarithmic</td>
+    <td style="text-align:center">1085</td>
+    <td style="text-align:center">8229</td>
+    <td style="text-align:center">998</td>
     </tr>
 </table>
 
@@ -918,29 +916,29 @@ some numbers comparing the different search methods:
   <caption>B frame Motion Vector Search (Normalized)</caption>
 <?makeman r c c c. ?>
 <?makeman _ ?>
-  <tr align="center">
+  <tr style="text-align:center">
     <th>Technique</th>
     <th>Compression<a href="#smallbetter"><sup>1</sup></a></th>
     <th>Speed<a href="#largefaster"><sup>2</sup></a></th>
     <th>Quality<a href="#largebetter"><sup>3</sup></a></th>
     </tr>
   <tr>
-    <td align="right">Exhaustive</td>
-    <td align="center">1000</td>
-    <td align="center">1000</td>
-    <td align="center">1000</td>
+    <td style="text-align:right">Exhaustive</td>
+    <td style="text-align:center">1000</td>
+    <td style="text-align:center">1000</td>
+    <td style="text-align:center">1000</td>
     </tr>
   <tr>
-    <td align="right">Cross2</td>
-    <td align="center">975</td>
-    <td align="center">1000</td>
-    <td align="center">996</td>
+    <td style="text-align:right">Cross2</td>
+    <td style="text-align:center">975</td>
+    <td style="text-align:center">1000</td>
+    <td style="text-align:center">996</td>
     </tr>
   <tr>
-    <td align="right">Simple</td>
-    <td align="center">938</td>
-    <td align="center">1765</td>
-    <td align="center">991</td>
+    <td style="text-align:right">Simple</td>
+    <td style="text-align:center">938</td>
+    <td style="text-align:center">1765</td>
+    <td style="text-align:center">991</td>
     </tr>
 </table>
 
@@ -955,12 +953,11 @@ execution.
 <p>For some reason, Simple seems to give better compression, but it
 depends on the image sequence.
 
-<p>Select the search techniques with the <B>PSEARCH_ALG</B> and
-<B>BSEARCH_ALG</b> parameter file statements.
+<p>Select the search techniques with the <b>PSEARCH_ALG</b> and
+<b>BSEARCH_ALG</b> parameter file statements.
 
 
-<a name="gop"></a>
-<h3>Group Of Pictures (GOP)</h3>
+<h3 id="gop">Group Of Pictures (GOP)</h3>
 
 <p>A Group of Pictures (GOP) is a roughly independently decodable
 sequence of frames.  An MPEG video stream is made of one or more
@@ -974,7 +971,7 @@ join the resulting GOP files at any time by running <b>ppmtompeg</b>
 with the <b>-combine_gops</b> command option.
      
      
-<h3>Slices</h3>
+<h3 id="slices">Slices</h3>
 
 <p>A slice is an independently decodable unit in a frame.  It can be
 as small as one macroblock, or it can be as big as the entire frame.
@@ -984,7 +981,7 @@ used for noisy transmission so that errors are more recoverable. Since
 usually errors are not such a problem, we usually just use one slice
 per frame.
      
-<p>Control the slice size with the <B>SLICES_PER_FRAME</B> parameter
+<p>Control the slice size with the <b>SLICES_PER_FRAME</b> parameter
 file statement.
 
 <p>Some MPEG playback systems require that each slice consist of whole
@@ -999,12 +996,12 @@ standard says this doesn't have to be so.
 
 
 
-<h3>Search Window</h3>
+<h3 id="searchwindow">Search Window</h3>
      
 <p>The search window is the window in which <b>ppmtompeg</b> searches
 for motion vectors.  The window is a square.  You can specify the size
 of the square, and whether to allow half-pixel motion vectors or not,
-with the <b>RANGE</b> and <b>PIXEL</B> parameter file statements.
+with the <b>RANGE</b> and <b>PIXEL</b> parameter file statements.
 
 <h3 id="ipb">I Frames, P Frames, B Frames</h3>
 
@@ -1037,29 +1034,29 @@ some of the trade-offs:
   <caption>Comparison of I/P/B Frames (Normalized)</caption>
 <?makeman r c c c. ?>
 <?makeman _ ?>
-  <tr align="center">
+  <tr style="text-align:center">
     <th>Frame Type</th>
     <th>Size</th>
     <th>Speed</th>
     <th>Quality</th>
     </tr>
   <tr>
-    <td align="right">I frames</td>
-    <td align="center">1000</td>
-    <td align="center">1000</td>
-    <td align="center">1000</td>
+    <td style="text-align:right">I frames</td>
+    <td style="text-align:center">1000</td>
+    <td style="text-align:center">1000</td>
+    <td style="text-align:center">1000</td>
     </tr>
   <tr>
-    <td align="right">P frames</td>
-    <td align="center">409</td>
-    <td align="center">609</td>
-    <td align="center">969</td>
+    <td style="text-align:right">P frames</td>
+    <td style="text-align:center">409</td>
+    <td style="text-align:center">609</td>
+    <td style="text-align:center">969</td>
     </tr>
   <tr>
-    <td align="right">B frames</td>
-    <td align="center">72</td>
-    <td align="center">260</td>
-    <td align="center">919</td>
+    <td style="text-align:right">B frames</td>
+    <td style="text-align:center">72</td>
+    <td style="text-align:center">260</td>
+    <td style="text-align:center">919</td>
     </tr>
   </table>
 
@@ -1067,7 +1064,7 @@ some of the trade-offs:
      
 <p>A standard sequence is IBBPBBPBBPBBPBB.
      
-<p>Select the sequence with the <B>PATTERN</B> parameter file statement.
+<p>Select the sequence with the <b>PATTERN</b> parameter file statement.
 
 <p>Since the last MPEG frame cannot be a B frame (see above), if the
 pattern you specify indicates a B frame for the last movie frame of
@@ -1088,17 +1085,17 @@ frames in the MPEG-1 stream are B frames describing movie frames 1 and 2,
 respectively.
 
 
-<h3>Specifying Input and Output Files</h3> 
+<h3 id="iofiles">Specifying Input and Output Files</h3> 
 
-<p>Specify the input frame images with the <B>INPUT_DIR</B>,
-<B>INPUT</B>, <B>END_INPUT</B>, <B>BASE_FILE_FORMAT</B>,
-<B>SIZE</B>, <B>YUV_FORMAT</B> and <b>INPUT_CONVERT</B> parameter
+<p>Specify the input frame images with the <b>INPUT_DIR</b>,
+<b>INPUT</b>, <b>END_INPUT</b>, <b>BASE_FILE_FORMAT</b>,
+<b>SIZE</b>, <b>YUV_FORMAT</b> and <b>INPUT_CONVERT</b> parameter
 file statements.
 
 <p>Specify the output file with the <b>OUTPUT</b> parameter file statement.
 
 
-<h3>Statistics</h3>
+<h3 id="statistics">Statistics</h3>
 
 <p><b>ppmtompeg</b> can generate a variety of statistics about the 
 encoding.  See the <b>-stat</b>, <b>-snr</b>, <b>-mv_histogram</b>,
@@ -1106,9 +1103,9 @@ encoding.  See the <b>-stat</b>, <b>-snr</b>, <b>-mv_histogram</b>,
 options.
      
 
-<H2 id="parallel">PARALLEL OPERATION</H2>
+<h2 id="parallel">PARALLEL OPERATION</h2>
 
-<P>You can run <b>ppmtompeg</b> on multiple machines at once, encoding
+<p>You can run <b>ppmtompeg</b> on multiple machines at once, encoding
 the same MPEG stream.  When you do, the machines are used as shown in
 the following diagram.  We call this "parallel mode."
 
@@ -1133,12 +1130,12 @@ has filesystem access to the input files, then the line is:
 <p>
 <i>machine</i> <i>user</i> <i>executable</i>
 
-<P>The executable is normally <b>ppmtompeg</b> (you may need to give
+<p>The executable is normally <b>ppmtompeg</b> (you may need to give
 the complete path if you've built for different architectures).  If
 the machine does not have filesystem access to the input files, the line
 is:
 
-<P><b>REMOTE</b> <i>machine</i> <i>user</i> <i>executable</i>
+<p><b>REMOTE</b> <i>machine</i> <i>user</i> <i>executable</i>
 <i>parameter file</i>
 
 <p>The <b>-max_machines</b> command option limits the number of
@@ -1155,8 +1152,8 @@ file argument on the original invocation of <b>ppmtompeg</b>.
 using an NFS filesystem, you must make sure it is mounted at the same
 mountpoint on all systems).
 
-<P>Because not all of the processes involved in parallel operation
-have easy access to the input files, you must specify the <B>SIZE</B>
+<p>Because not all of the processes involved in parallel operation
+have easy access to the input files, you must specify the <b>SIZE</b>
 parameter file statement when you do parallel operation.
 
 <p>The machine on which you originally invoke <b>ppmtompeg</b> is the
@@ -1188,8 +1185,7 @@ master divides up work among the slaves.
 long-running CPU load will have minimal impact on other, possibly
 interactive, users of the systems.
 
-<A NAME="speed">&nbsp;</A>
-<H2>SPEED</h2>
+<h2 id="speed">SPEED</h2>
 
 <p>Here is a look at <b>ppmtompeg</b> speed, in single-node (not parallel)
 operation:
@@ -1198,29 +1194,29 @@ operation:
   <caption>Compression Speed</caption>
 <?makeman r c. ?>
 <?makeman _ ?>
-  <tr align="center">
+  <tr style="text-align:center">
     <th>Machine Type</th>
     <th>Macroblocks per second<sup>1</sup></th>
     </tr>
   <tr>
-    <td align="right">HP 9000/755</td>
-    <td align="center">280</td>
+    <td style="text-align:right">HP 9000/755</td>
+    <td style="text-align:center">280</td>
     </tr>
   <tr>
-    <td align="right">DEC 3000/400</td>
-    <td align="center">247</td>
+    <td style="text-align:right">DEC 3000/400</td>
+    <td style="text-align:center">247</td>
     </tr>
   <tr>
-    <td align="right">HP 9000/750</td>
-    <td align="center">191</td>
+    <td style="text-align:right">HP 9000/750</td>
+    <td style="text-align:center">191</td>
     </tr>
   <tr>
-    <td align="right">Sparc 10</td>
-    <td align="center">104</td>
+    <td style="text-align:right">Sparc 10</td>
+    <td style="text-align:center">104</td>
     </tr>
   <tr>
-    <td align="right">DEC 5000</td>
-    <td align="center">68</td>
+    <td style="text-align:right">DEC 5000</td>
+    <td style="text-align:center">68</td>
     </tr>
 </table>
 <sup>1</sup>A macroblock is a 16x16 pixel square
@@ -1245,42 +1241,54 @@ Also, <b>-debug_sockets</b> can help you diagnose communication
 problems.
 
 
-<H2 id="authors">AUTHORS</H2>
-
-<UL>
-
-<LI>Kevin Gong - University of California, Berkeley, <A
-HREF="mailto:keving@cs.berkeley.edu">keving@cs.berkeley.edu</A>
-
-<LI>Ketan Patel - University of California, Berkeley, <A
-HREF="mailto:kpatel@cs.berkeley.edu">kpatel@cs.berkeley.edu</A>
-
-<LI>Dan Wallach - University of California, Berkeley, <A
-HREF="mailto:dwallach@cs.berkeley.edu">dwallach@cs.berkeley.edu</A>
-
-<LI>Darryl Brown - University of California, Berkeley, <A
-HREF="mailto:darryl@cs.berkeley.edu">darryl@cs.berkeley.edu</A>
-
-<LI>Eugene Hung - University of California, Berkeley, <A
-HREF="mailto:eyhung@cs.berkeley.edu">eyhung@cs.berkeley.edu</A>
-
-<LI>Steve Smoot - University of California, Berkeley, <A
-HREF="mailto:smoot@cs.berkeley.edu">smoot@cs.berkeley.edu</A>
-
-</UL>
-
-<HR>
-<A NAME="index">&nbsp;</A>
-<H2>Table Of Contents</H2>
-<UL>
-<LI><A HREF="#synopsis">SYNOPSIS</A></LI>
-<LI><A HREF="#description">DESCRIPTION</A></LI>
-<LI><A HREF="#options">OPTIONS</A></LI>
-<LI><A HREF="#parmfile">PARAMETER FILE</A></LI>
-<LI><A HREF="#general">GENERAL USAGE INFORMATION</A></LI>
-<LI><A HREF="#parallel">PARALLEL OPERATION</A></LI>
-<LI><A HREF="#speed">SPEED</A></LI>
-<LI><A HREF="#authors">AUTHORS</A></LI>
-</UL>
-</BODY>
-</HTML>
+<h2 id="authors">AUTHORS</h2>
+
+<ul>
+
+<li>Kevin Gong - University of California, Berkeley, <a
+href="mailto:keving@cs.berkeley.edu">keving@cs.berkeley.edu</a>
+
+<li>Ketan Patel - University of California, Berkeley, <a
+href="mailto:kpatel@cs.berkeley.edu">kpatel@cs.berkeley.edu</a>
+
+<li>Dan Wallach - University of California, Berkeley, <a
+href="mailto:dwallach@cs.berkeley.edu">dwallach@cs.berkeley.edu</a>
+
+<li>Darryl Brown - University of California, Berkeley, <a
+href="mailto:darryl@cs.berkeley.edu">darryl@cs.berkeley.edu</a>
+
+<li>Eugene Hung - University of California, Berkeley, <a
+href="mailto:eyhung@cs.berkeley.edu">eyhung@cs.berkeley.edu</a>
+
+<li>Steve Smoot - University of California, Berkeley, <a
+href="mailto:smoot@cs.berkeley.edu">smoot@cs.berkeley.edu</a>
+
+</ul>
+
+<hr>
+<h2 id="index">Table Of Contents</h2>
+<ul>
+<li><a href="#synopsis">SYNOPSIS</a>
+<li><a href="#description">DESCRIPTION</a>
+<li><a href="#options">OPTIONS</a>
+<li><a href="#parmfile">PARAMETER FILE</a>
+  <ul>
+  <li><a href="#parameterfile">Parameter File Notes</a>
+  </ul>
+<li><a href="#general">GENERAL USAGE INFORMATION</a>
+  <ul>
+  <li><a href="#qscale">Qscale</a>
+  <li><a href="#searchtech">Search Techniques</a>
+  <li><a href="#gop">Group Of Pictures (GOP)</a>
+  <li><a href="#slices">Slices</a>
+  <li><a href="#searchwindow">Search Window</a>
+  <li><a href="#ipb">I Frames, P Frames, B Frames</a>
+  <li><a href="#iofiles">Specifying Input and Output Files </a>
+  <li><a href="#statistics">Statistics</a>
+  </ul>
+<li><a href="#parallel">PARALLEL OPERATION</a>
+<li><a href="#speed">SPEED</a>
+<li><a href="#authors">AUTHORS</a>
+</ul>
+</body>
+</html>
author	giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>	2020-08-02 18:44:01 +0000
committer	giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8>	2020-08-02 18:44:01 +0000
commit	ad48d09aa16cf2c106ba4d0e232c703a75ab5c49 (patch)
tree	67fe02ab9d4f8952d6ac8b0aac1674f099f0fd7e /ppmtompeg.html
parent	56ef5a9528e4eb818db26d7cee8733d46d6cb687 (diff)
download	netpbm-mirror-ad48d09aa16cf2c106ba4d0e232c703a75ab5c49.tar.gz netpbm-mirror-ad48d09aa16cf2c106ba4d0e232c703a75ab5c49.tar.xz netpbm-mirror-ad48d09aa16cf2c106ba4d0e232c703a75ab5c49.zip