Index: brlcad/doc/docbook/system/man5/en/CMakeLists.txt
===================================================================
--- brlcad/doc/docbook/system/man5/en/CMakeLists.txt	(revision 53940)
+++ brlcad/doc/docbook/system/man5/en/CMakeLists.txt	(working copy)
@@ -1,6 +1,8 @@
 set(docbook_man5_EN
   dsp.xml
   gattributes.xml
+  png.xml
+  rle.xml
   )
 
 DOCBOOK_TO_HTML(man5 docbook_man5_EN html/man5/en "")
Index: brlcad/doc/docbook/system/man5/en/png.xml
===================================================================
--- brlcad/doc/docbook/system/man5/en/png.xml	(revision 0)
+++ brlcad/doc/docbook/system/man5/en/png.xml	(working copy)
@@ -0,0 +1,92 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!-- lifted from troff+man by doclifter -->
+<refentry xmlns='http://docbook.org/ns/docbook' version='5.0' xml:lang='en' xml:id='png5'>
+<refmeta>
+<refentrytitle>PNG</refentrytitle>
+<manvolnum>5</manvolnum>
+<refmiscinfo class='source'>July 11, 2012</refmiscinfo>
+</refmeta>
+<refnamediv>
+<refname>png</refname>
+<refpurpose>Portable Network Graphics (PNG) format</refpurpose>
+</refnamediv>
+<!-- body begins here -->
+
+<refsect1 xml:id='description'><title>DESCRIPTION</title>
+<para>PNG (Portable Network Graphics) is an extensible file format for the
+lossless, portable, well-compressed storage of raster images. PNG provides
+a patent-free replacement for GIF and can also replace many
+common uses of TIFF. Indexed-color, grayscale, and truecolor images are
+supported, plus an optional alpha channel. Sample depths range from
+1 to 16 bits.</para>
+
+
+<para>PNG is designed to work well in online viewing applications, such as the
+World Wide Web, so it is fully streamable with a progressive display
+option. PNG is robust, providing both full file integrity checking and
+fast, simple detection of common transmission errors. Also, PNG can store
+gamma and chromaticity data for improved color matching on heterogeneous
+platforms.</para>
+
+</refsect1>
+
+<refsect1 xml:id='see_also'><title>SEE ALSO</title>
+<para><citerefentry><refentrytitle>libpng</refentrytitle><manvolnum>3</manvolnum></citerefentry>,<emphasis remap='B'> libpngpf</emphasis>(3),<emphasis remap='B'> zlib</emphasis>(3),<emphasis remap='B'> deflate</emphasis>(5),and<emphasis remap='B'> zlib</emphasis>(5)</para>
+
+<para>PNG specification (second edition), November 2003:</para>
+
+
+<para>  &lt;http://www.w3.org/TR/2003/REC-PNG-20031110/
+PNG 1.2 specification, July 1999:</para>
+
+
+<para>http://www.libpng.org/pub/png</para>
+
+<para>PNG 1.0 specification, October 1996:</para>
+
+
+<para>RFC 2083</para>
+
+
+<para>ftp://ds.internic.net/rfc/rfc2083.txt</para>
+
+<para>or (as a W3C Recommendation) at</para>
+
+<para>http://www.w3.org/TR/REC-png.html</para>
+</refsect1>
+
+<refsect1 xml:id='authors'><title>AUTHORS</title>
+<para>This man page: Glenn Randers-Pehrson</para>
+
+<para>Portable Network Graphics (PNG) Specification (Second Edition)
+Information technology - Computer graphics and image processing -
+Portable Network Graphics (PNG): Functional specification.
+ISO/IEC 15948:2003 (E) (November 10, 2003): David Duce and others.</para>
+
+<para>Portable Network Graphics (PNG) Specification Version 1.2 (July 8, 1999):
+Glenn Randers-Pehrson and others (png-list).</para>
+
+<para>Portable Network Graphics (PNG) Specification Version 1.0 (October 1, 1996):
+Thomas Boutell and others (png-list).</para>
+
+
+
+</refsect1>
+
+<refsect1 xml:id='copyright_notice'><title>COPYRIGHT NOTICE</title>
+<para>This man page is Copyright (c) 1998-2006 Glenn Randers-Pehrson.  See png.h
+for conditions of use and distribution.</para>
+
+<para>The PNG Specification (Second Edition) is
+Copyright (c) 2003 W3C. (MIT, ERCIM, Keio), All Rights Reserved.</para>
+
+<para>The PNG-1.2 specification is copyright (c) 1999 Glenn Randers-Pehrson.
+See the specification for conditions of use and distribution.</para>
+
+<para>The PNG-1.0 specification is copyright (c) 1996 Massachusetts Institute of
+Technology.  See the specification for conditions of use and distribution.</para>
+
+<!--  end of man page -->
+</refsect1>
+</refentry>
+

Property changes on: brlcad/doc/docbook/system/man5/en/png.xml
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+text/xml
\ No newline at end of property
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Index: brlcad/doc/docbook/system/man5/en/rle.xml
===================================================================
--- brlcad/doc/docbook/system/man5/en/rle.xml	(revision 0)
+++ brlcad/doc/docbook/system/man5/en/rle.xml	(working copy)
@@ -0,0 +1,223 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!-- lifted from troff+man by doclifter -->
+<refentry xmlns='http://docbook.org/ns/docbook' version='5.0' xml:lang='en' xml:id='rle5'>
+<!--  Copyright (c) 1986, University of Utah -->
+<refentryinfo><date>9/14/82</date></refentryinfo>
+<refmeta>
+<refentrytitle>RLE</refentrytitle>
+<manvolnum>5</manvolnum>
+<refmiscinfo class='date'>9/14/82</refmiscinfo>
+<refmiscinfo class='source'>5</refmiscinfo>
+</refmeta>
+<refnamediv>
+<refname>rle</refname>
+<refpurpose>Run length encoded file format produced by the rle library</refpurpose>
+</refnamediv>
+<!-- body begins here -->
+
+<refsect1 xml:id='description'><title>DESCRIPTION</title>
+<para>The output file format is (note: all words are 16 bits, and in PDP-11 byte
+order):</para>
+<variablelist remap='TP'>
+  <varlistentry>
+  <term><emphasis remap='B'>Word 0</emphasis></term>
+  <listitem>
+<para>A "magic" number 0xcc52.  (Byte order 0x52, 0xcc.)</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='B'>Words 1-4</emphasis></term>
+  <listitem>
+<para>The structure (chars saved in PDP-11 order)</para>
+
+<literallayout remap='.nf'>
+{
+    short   xpos,                       /* Lower left corner
+            ypos,
+            xsize,                      /* Size of saved box
+            ysize;
+}
+</literallayout> <!-- .fi -->
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='B'>Byte 10</emphasis></term>
+  <listitem>
+<para><emphasis remap='I'>(flags)</emphasis>
+The following flags are defined:</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='I'>H_CLEARFIRST</emphasis></term>
+  <listitem>
+<para>(0x1) If set, clear the frame buffer to background color before restoring.</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='I'>H_NO_BACKGROUND</emphasis></term>
+  <listitem>
+<para>(0x2) If set, no background color is supplied.  If
+<emphasis remap='I'>H_CLEARFIRST</emphasis>
+is also set, it should be ignored (or alternatively, a clear-to-black
+operation could be performed).</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='I'>H_ALPHA</emphasis></term>
+  <listitem>
+<para>(0x4) If set, an alpha channel is saved as color channel -1.  The alpha
+channel does not contribute to the count of colors in
+<emphasis remap='I'>ncolors</emphasis>.</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='I'>H_COMMENT</emphasis></term>
+  <listitem>
+<para>(0x8) If set, comments will follow the color map in the header.</para>
+  </listitem>
+  </varlistentry>
+</variablelist>
+<variablelist remap='TP'>
+  <varlistentry>
+  <term><emphasis remap='B'>Byte 11</emphasis></term>
+  <listitem>
+<para><emphasis remap='I'>(ncolors)</emphasis>
+Number of color channels present.  0 means load only the color map (if
+present), 1 means a B&amp;W image, 3 means a normal color image.</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='B'>Byte 12</emphasis></term>
+  <listitem>
+<para><emphasis remap='I'>(pixelbits)</emphasis>
+Number of bits per pixel, per color channel.  Values greater than 8
+currently will not work.</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='B'>Byte 13</emphasis></term>
+  <listitem>
+<para><emphasis remap='I'>(ncmap)</emphasis>
+Number of color map channels present.  Need not be identical to
+<emphasis remap='I'>ncolors</emphasis>.
+If this is non-zero, the color map follows immediately after the background
+colors.</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='B'>Byte 14</emphasis></term>
+  <listitem>
+<para><emphasis remap='I'>(cmaplen)</emphasis>
+Log base 2 of the number of entries in the color map for each color channel.
+I.e., would be 8 for a color map with 256 entries.</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='B'>Bytes 15-...</emphasis></term>
+  <listitem>
+<para>The background color.  There are
+<emphasis remap='I'>ncolors</emphasis>
+bytes of background color.  If
+<emphasis remap='I'>ncolors</emphasis>
+is even, an extra padding byte is inserted to end on a 16 bit boundary.
+The background color is only present if
+<emphasis remap='I'>H_NO_BACKGROUND</emphasis>
+is not set in
+<emphasis remap='I'>flags</emphasis>.
+IF
+<emphasis remap='I'>H_NO BACKGROUND</emphasis>
+is set, there is a single filler byte.  Background color is ignored, but
+present, if
+<emphasis remap='I'>H_CLEARFIRST</emphasis>
+is not set in
+<emphasis remap='I'>flags</emphasis>.</para>
+
+<para>If
+<emphasis remap='I'>ncmap</emphasis>
+is non-zero, then the color map will follow as
+<emphasis remap='I'>ncmap</emphasis>*2^<emphasis remap='I'>cmaplen</emphasis>
+16 bit words.  The color map data is left justified in each word.</para>
+
+<para>If the
+<emphasis remap='I'>H_COMMENT</emphasis>
+flag is set, a set of comments will follow.  The first 16 bit word
+gives the length of the comments in bytes.  If this is odd, a filler
+byte will be appended to the comments.  The comments are interpreted
+as a sequence of null terminated strings which should be, by
+convention, of the form
+<emphasis remap='I'>name</emphasis>=<emphasis remap='I'>value</emphasis>,
+or just
+<emphasis remap='I'>name</emphasis>.</para>
+
+<para>Following the setup information is the Run Length Encoded image.  Each
+instruction consists of an opcode, a datum and possibly one or
+more following words (all words are 16 bits).  The opcode is encoded in the
+first byte of the instruction word.  Instructions come in either a short or
+long form.  In the short form, the datum is in the second byte of the
+instruction word; in the long form, the datum is a 16 bit value in the word
+following the instruction word.  Long form instructions are distinguished by
+having the 0x40 bit set in the opcode byte.
+The instruction opcodes are:</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='B'>SkipLines (1)</emphasis></term>
+  <listitem>
+<para>The datum is an unsigned number to be added to the current Y position.</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='B'>SetColor (2)</emphasis></term>
+  <listitem>
+<para>The datum indicates which color is to be loaded with the data described by the
+following ByteData and RunData instructions.  Typically,
+0->red, 1->green, 2->blue.  The
+operation also resets the X position to the initial X (i.e. a carriage return
+operation is performed).</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='B'>SkipPixels (3)</emphasis></term>
+  <listitem>
+<para>The datum is an unsigned number to be added to the current X
+position.</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='B'>ByteData (5)</emphasis></term>
+  <listitem>
+<para>The datum is one less than the number of bytes of color data following.  If the
+number of bytes is odd, a filler byte will be appended to the end of the byte
+string to make an integral number of 16-bit words.  The X position is
+incremented to follow the last byte of data.</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='B'>RunData (6)</emphasis></term>
+  <listitem>
+<para>The datum is one less than the run length.  The following word contains (in its
+lower 8 bits) the color of the run.  The X position is incremented to follow
+the last byte in the run.</para>
+  </listitem>
+  </varlistentry>
+  <varlistentry>
+  <term><emphasis remap='B'>EOF (7)</emphasis></term>
+  <listitem>
+<para>This opcode indicates the logical end of image data.  A physical
+end-of-file will also serve as well.  The
+<emphasis remap='B'>EOF</emphasis>
+opcode may be used to concatenate several images in a single file.</para>
+  </listitem>
+  </varlistentry>
+</variablelist>
+</refsect1>
+
+<refsect1 xml:id='see_also'><title>SEE ALSO</title>
+<para><emphasis remap='I'><citerefentry><refentrytitle>librle</refentrytitle><manvolnum>3</manvolnum></citerefentry></emphasis></para>
+</refsect1>
+
+<refsect1 xml:id='author'><title>AUTHOR</title>
+<para>Spencer W. Thomas, Todd Fuqua</para>
+</refsect1>
+</refentry>
+

Property changes on: brlcad/doc/docbook/system/man5/en/rle.xml
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+text/xml
\ No newline at end of property
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
