Hello community,

here is the log from the commit of package netpbm for openSUSE:Factory checked 
in at 2013-11-28 16:51:47
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/netpbm (Old)
 and      /work/SRC/openSUSE:Factory/.netpbm.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "netpbm"

Changes:
--------
--- /work/SRC/openSUSE:Factory/netpbm/netpbm.changes    2013-10-04 
15:59:11.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.netpbm.new/netpbm.changes       2013-11-28 
16:51:49.000000000 +0100
@@ -1,0 +2,20 @@
+Wed Nov 27 08:36:15 UTC 2013 - [email protected]
+
+- updated to 10.64.04
+  * pnmtops: Fix bug: wrong output with -ascii85.  Introduced in
+    10.63 (June 2013).
+  * pnmtops: Fix bug: wrong output with -rle.  Introduced in
+    10.63 (June 2013).
+  * pnmtops: Fix bug: fails with message about waitpid() failing
+    if invoked with SIGCHLD ignored.  Introduced in 10.56
+    (September 2011).
+  * pnmtops: Fix bug: closes Standard Error.  Introduced in
+    10.64.02 (today).
+  * pnmtops: Fix bug: program hangs if it inherits lots of open
+    files.  Introduced in 10.56 (September 2011).
+  * pngtopam: fix bug: ignores -gamma.  Introduced in 10.48
+  * see HISTORY for details 
+- removed wordaccess-include-be.patch (upstreamed)
+- removed stdbool-after-jasper.patch (workaround not needed yet)
+
+-------------------------------------------------------------------

Old:
----
  netpbm-10.63.1-documentation.tar.bz2
  netpbm-10.63.1-nohpcdtoppm-noppmtompeg.tar.bz2
  netpbm-stdbool-after-jasper.patch
  wordaccess-include-be.patch

New:
----
  netpbm-10.64.4-documentation.tar.bz2
  netpbm-10.64.4-nohpcdtoppm-noppmtompeg.tar.bz2

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ netpbm.spec ++++++
--- /var/tmp/diff_new_pack.wKqxmA/_old  2013-11-28 16:51:49.000000000 +0100
+++ /var/tmp/diff_new_pack.wKqxmA/_new  2013-11-28 16:51:49.000000000 +0100
@@ -17,11 +17,11 @@
 
 
 %define libmaj  11
-%define libmin  63
+%define libmin  64
 %define libver  %{libmaj}.%{libmin}
 
 Name:           netpbm
-Version:        10.63.1
+Version:        10.64.4
 Release:        0
 Summary:        A Powerful Graphics Conversion Package
 License:        BSD-3-Clause and GPL-2.0+ and SUSE-IJG and MIT and 
SUSE-Public-Domain
@@ -40,10 +40,6 @@
 Patch3:         %{name}-tmpfile.patch 
 Patch4:         %{name}-security-code.patch 
 Patch5:         %{name}-security-scripts.patch 
-# workaround to #839584 -- just to meet 13.1 beta1 freeze, it
-# can be removed as soon as jasper enters factory
-Patch6:         %{name}-stdbool-after-jasper.patch
-Patch7:         wordaccess-include-be.patch
 BuildRequires:  flex
 BuildRequires:  libjasper-devel
 BuildRequires:  libjpeg-devel
@@ -114,11 +110,9 @@
 %patch1
 %patch2
 %patch3
-%patch4 -p1
+%patch4
 %patch5 -p1
-%patch6
-%patch7 -p1
-mkdir pnmtopalm # for %doc pnmtopalm
+mkdir pnmtopalm # for %%doc pnmtopalm
 cp -p converter/other/pnmtopalm/{LICENSE,README} pnmtopalm
 
 %build

++++++ netpbm-10.63.1-documentation.tar.bz2 -> 
netpbm-10.64.4-documentation.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/netpbm.sourceforge.net/doc/index.html 
new/netpbm.sourceforge.net/doc/index.html
--- old/netpbm.sourceforge.net/doc/index.html   2013-06-23 23:13:34.000000000 
+0200
+++ new/netpbm.sourceforge.net/doc/index.html   2013-10-20 18:44:30.000000000 
+0200
@@ -824,14 +824,12 @@
 See 
 <B><A 
HREF="ftp://ftp.astron.com/pub/file";>ftp://ftp.astron.com/pub/file</A></B>.
 
-<P>The Utah Raster Toolkit serves a lot of the same purpose as Netpbm,
-but without the emphasis on format conversions.  This package is based
-on the RLE format, which you can convert to and from the Netpbm
-formats.  The website of the <a
-href="http://www.cs.utah.edu/gdc";>Geometric Design And Computation
-group</a> in the Department of Computer Science at University of Utah
-used to (ca. 2002) have information on the Utah Raster Toolkit, but
-now it doesn't.
+<P>The <a href="http://www.cs.utah.edu/gdc/projects/urt";>Utah Raster
+Toolkit</a> from the <a href="http://www.cs.utah.edu/gdc";>Geometric Design And
+Computation group</a> in the Department of Computer Science at University of
+Utah serves a lot of the same purpose as Netpbm, but without the emphasis on
+format conversions.  This package is based on the RLE format, which you can
+convert to and from the Netpbm formats.
 
 <P><B>Ivtools</B> is a suite of free X Window System drawing editors for
 Postscript, Tex, and web graphics production, as well as an embeddable
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/netpbm.sourceforge.net/doc/libnetpbm_image.html 
new/netpbm.sourceforge.net/doc/libnetpbm_image.html
--- old/netpbm.sourceforge.net/doc/libnetpbm_image.html 2013-06-23 
21:59:24.000000000 +0200
+++ new/netpbm.sourceforge.net/doc/libnetpbm_image.html 2013-11-03 
14:46:26.000000000 +0100
@@ -40,8 +40,7 @@
 <p>To use these services, #include <b>pam.h</b>.
 
 
-<a name="types"></a>
-<H2>Types</h2>
+<H2 id="types">Types</h2>
 
 <p>Here are some important types that you use with <b>libnetpbm</b>:
 
@@ -74,47 +73,36 @@
 </dl>
 
 
+<h3 id="pamstruct">struct pam</h3>
 
 <p>The main argument to most of the PAM functions is the address of
 a <b>pam</b> structure, which is defined as follows:
 
-<P>
-<a name="#pamstruct"></a>
-<B>struct pam {</B>
-<BR>
-<B>int </B><I>size</I>
-<BR>
-<B>int </B><I>len</I>
-<BR>
-<B>FILE *</B><I>file   </I>
-<BR>
-<B>int </B><I>format</I>
-<BR>
-<B>int </B><I>plainformat</I>
-<BR>
-<B>int </B><I>height</I>
-<BR>
-<B>int </B><I>width</I>
-<BR>
-<B>int </B><I>depth</I>
-<BR>
-<B>sample </B><I>maxval</I>
-<BR>
-<B>int </B><I>bytes_per_sample</I>
-<BR>
-<B>char </B><I>tuple_type</I><B>[256]</B>
-<BR>
-<B>int </B><I>allocation_depth</I>
-<BR>
-<B>char **</B><I>comment_p</I><B>;</B>
-<B>}</B>
+<pre>
+  <code>
+    <B>struct pam {</B>
+        <B>int </B><I>size</I>
+        <B>int </B><I>len</I>
+        <B>FILE *</B><I>file   </I>
+        <B>int </B><I>format</I>
+        <B>int </B><I>plainformat</I>
+        <B>int </B><I>height</I>
+        <B>int </B><I>width</I>
+        <B>int </B><I>depth</I>
+        <B>sample </B><I>maxval</I>
+        <B>int </B><I>bytes_per_sample</I>
+        <B>char </B><I>tuple_type</I><B>[256]</B>
+        <B>int </B><I>allocation_depth</I>
+        <B>char **</B><I>comment_p</I><B>;</B>
+    <B>}</B>
+    </code>
+  </pre>
 
 <p>See <a href="libnetpbm_ug.html#pamstruct">The Libnetbm User's Guide</a>
 for information on the <b>pam</b> structure.
 
 
-<a name="macros"></a>
-<H2>Macros</h2>
+<H2 id="macros">Macros</h2>
 
 <B>PNM_MAXMAXVAL</B> is the maximum maxval that Netpbm images could
 historically have: 255.  Many programs aren't capable of handling Netpbm
@@ -141,13 +129,11 @@
 
 
 
-<a name="functions"></a>
-<H2>Functions</H2>
+<H2 id="functions">Functions</H2>
 
 <p>These interfaces are declared in <b>pam.h</b>.
 
-<a name="memory"></a>
-<h3>Memory Management</h3>
+<h3 id="memory">Memory Management</h3>
 <h4>Synopsis</h4>
 <P>
 <B>tuple ** pnm_allocpamarray(</B>
@@ -199,8 +185,7 @@
 <b>pnm_freepamrown()</b> is similarly like <b>pnm_freepamrow</b>.
 
 
-<a name="reading"></a>
-<h3>Reading Netpbm Files</h3>
+<h3 id="reading">Reading Netpbm Files</h3>
 <h4>Synopsis</h4>
 
 <P>
@@ -301,8 +286,7 @@
 processed using the system's normal data structures (to wit, a number
 that won't fit in a C 'int').
 
-<a name="writing"></a>
-<h3>Writing Netpbm Files</h3>
+<h3 id="writing">Writing Netpbm Files</h3>
 <h4>Synopsis</h4>
 <P>
 <B>void pnm_writepaminit(</B>
@@ -639,11 +623,13 @@
 
 
 <HR>
-<A NAME="toc">&nbsp;</A>
-<H2>Table Of Contents</H2>
+<H2 id="toc">Table Of Contents</H2>
 
 <ul>
   <li><a href="#types">Types</a>
+    <ul>
+      <li><a href="#pamstruct">struct pam</a>
+      </ul>
   <li><a href="#macros">Macros</a>
   <li><a href="#functions">Functions</a>
   <ul>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pam.html 
new/netpbm.sourceforge.net/doc/pam.html
--- old/netpbm.sourceforge.net/doc/pam.html     2013-02-20 04:30:31.000000000 
+0100
+++ new/netpbm.sourceforge.net/doc/pam.html     2013-11-02 18:49:32.000000000 
+0100
@@ -8,7 +8,7 @@
 <A HREF="#index">Table Of Contents</A>
 
 <H1>pam</H1>
-Updated: 09 October 2005
+Updated: 02 November 2013
 <BR>
 <?makeman .SH NAME ?>
 <?makeman pam - Netpbm common 2-dimensional bitmap format ?>
@@ -274,6 +274,14 @@
 foreground color samples.
 
 
+<h2 id="internetmediatype">Internet Media Type</h2>
+
+<p>No Internet Media Type (aka MIME type, content type) for PBM has been
+registered with IANA, but the unofficial value
+<tt>image/x-portable-arbitrarymap</tt> is assigned by this specification, to
+be consistent with conventional values for the older Netpbm formats.
+
+
 <H2 id="seealso">SEE ALSO</H2>
 
 <B><A HREF="index.html">Netpbm</A></B>,
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pbm.html 
new/netpbm.sourceforge.net/doc/pbm.html
--- old/netpbm.sourceforge.net/doc/pbm.html     2013-05-29 03:36:13.000000000 
+0200
+++ new/netpbm.sourceforge.net/doc/pbm.html     2013-11-02 18:45:58.000000000 
+0100
@@ -6,7 +6,7 @@
 </HEAD>
 <BODY>
 <H1>pbm</H1>
-Updated: 22 September 2006
+Updated: 02 November 2013
 <BR>
 <A HREF="#index">Table Of Contents</A>
 
@@ -39,7 +39,7 @@
 
 <P>Each PBM image consists of the following:
 
-<OL>
+<UL>
 
 <LI>A &quot;magic number&quot; for identifying the file type.
 A pbm image's magic number is the two characters &quot;P4&quot;.
@@ -74,8 +74,16 @@
 have a comment right before the raster, the newline at the end of the
 comment is not sufficient to delimit the raster.
 
-</OL>
+</UL>
+
+<p>All characters referred to herein are encoded in ASCII.
+&quot;newline&quot; refers to the character known in ASCII as Line
+Feed or LF.  A &quot;white space&quot; character is space, CR, LF,
+TAB, VT, or FF (I.e. what the ANSI standard C isspace() function
+calls white space).
+
 
+<h3 id="plainpbm">Plain PBM</h3>
 <P>
 There is actually another version of the PBM format, even more
 simplistic, more lavishly wasteful of space than PBM, called Plain
@@ -94,24 +102,23 @@
 <b>-plain</b> chooses Plain PBM.
 
 <P>The difference is:
-<DL COMPACT>
-<DT>-<DD>
+<ul>
+<li>
 There is exactly one image in a file.
-<DT>-<DD>
+<li>
 The &quot;magic number&quot; is &quot;P1&quot; instead of &quot;P4&quot;.
-<DT>-<DD>
+<li>
 Each pixel in the raster is represented by a byte containing ASCII '1' or '0',
 representing black and white respectively.  There are no fill bits at the
 end of a row.
-<DT>-<DD>
+<li>
 White space in the raster section is ignored.
-<DT>-<DD>
+<li>
 You can put any junk you want after the raster, if it starts with a 
 white space character.
-<DT>-<DD>
+<li>
 No line should be longer than 70 characters.
-</DL>
-<P>
+</ul>
 
 Here is an example of a small image in the plain PBM format.
 <PRE>
@@ -135,11 +142,16 @@
 <P>Programs that read this format should be as lenient as possible,
 accepting anything that looks remotely like a bitmap.
 
-<p>All characters referred to herein are encoded in ASCII.
-&quot;newline&quot; refers to the character known in ASCII as Line
-Feed or LF.  A &quot;white space&quot; character is space, CR, LF,
-TAB, VT, or FF (I.e. what the ANSI standard C isspace() function
-calls white space).
+
+<h3 id="internetmediatype">Internet Media Type</h3>
+
+<p>No Internet Media Type (aka MIME type, content type) for PBM has been
+registered with IANA, but the value <tt>image/x-portable-bitmap</tt>
+is conventional.
+
+<p>Note that the PNM Internet Media Type <tt>image/x-portable-anymap</tt>
+also applies.
+
 
 <H2 id="compatibility">COMPATIBILITY</H2>
 
@@ -160,6 +172,10 @@
 <H2 id="index">Table Of Contents</H2>
 <UL>
 <LI><A HREF="#description">DESCRIPTION</A>
+<ul>
+  <li><A HREF="#plainpbm">Plain PBM</A>
+  <li><A HREF="#internetmediatype">Internet Media Type</A>
+    </ul>
 <LI><A HREF="#compatibility">COMPATIBILITY</A>
 <LI><A HREF="#seealso">SEE ALSO</A>
 </UL>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pgm.html 
new/netpbm.sourceforge.net/doc/pgm.html
--- old/netpbm.sourceforge.net/doc/pgm.html     2013-05-29 03:36:35.000000000 
+0200
+++ new/netpbm.sourceforge.net/doc/pgm.html     2013-11-02 18:45:31.000000000 
+0100
@@ -6,7 +6,7 @@
 </HEAD>
 <BODY>
 <H1>pgm</H1>
-Updated: 03 October 2003
+Updated: 02 November 2013
 <BR>
 <A HREF="#index">Table Of Contents</A>
 
@@ -107,6 +107,14 @@
 format with 1 byte per gray value and the one with 2 bytes per gray
 value.
 
+<p>All characters referred to herein are encoded in ASCII.
+&quot;newline&quot; refers to the character known in ASCII as Line
+Feed or LF.  A &quot;white space&quot; character is space, CR, LF,
+TAB, VT, or FF (I.e. what the ANSI standard C isspace() function
+calls white space).
+
+<h3 id="plainpgm">Plain PGM</h3>
+
 <P>There is actually another version of the PGM format that is fairly
 rare: &quot;plain&quot; PGM format.  The format above, which generally
 considered the normal one, is known as the &quot;raw&quot; PGM format.
@@ -115,24 +123,24 @@
 
 <P>The difference in the plain format is:
 
-<DL COMPACT>
-<DT>-<DD>
+<ul>
+<li>
 There is exactly one image in a file.
-<DT>-<DD>
+<li>
 The magic number is P2 instead of P5.
-<DT>-<DD>
+<li>
 Each pixel in the raster is represented as an ASCII decimal number 
 (of arbitrary size).
-<DT>-<DD>
+<li>
 Each pixel in the raster has white space before and after it.  There must
 be at least one character of white space between any two pixels, but there
 is no maximum.
-<DT>-<DD>
+<li>
 No line should be longer than 70 characters.
-</DL>
-<P>
+</ul>
+
+<p>Here is an example of a small image in the plain PGM format.
 
-Here is an example of a small image in the plain PGM format.
 <PRE>
 P2
 # feep.pgm
@@ -152,11 +160,15 @@
 <p>Programs that read this format should be as lenient as possible,
 accepting anything that looks remotely like a PGM.
 
-<p>All characters referred to herein are encoded in ASCII.
-&quot;newline&quot; refers to the character known in ASCII as Line
-Feed or LF.  A &quot;white space&quot; character is space, CR, LF,
-TAB, VT, or FF (I.e. what the ANSI standard C isspace() function
-calls white space).
+
+<h3 id="internetmediatype">Internet Media Type</h3>
+
+<p>No Internet Media Type (aka MIME type, content type) for PBM has been
+registered with IANA, but the value <tt>image/x-portable-graymap</tt>
+is conventional.
+
+<p>Note that the PNM Internet Media Type <tt>image/x-portable-anymap</tt>
+also applies.
 
 
 <H2 id="compatibility">COMPATIBILITY</H2>
@@ -187,6 +199,10 @@
 <H2 id="index">Table Of Contents</H2>
 <UL>
 <LI><A HREF="#description">DESCRIPTION</A>
+<ul>
+  <li><A HREF="#plainpgm">Plain PGM</A>
+  <li><A HREF="#internetmediatype">Internet Media Type</A>
+    </ul>
 <LI><A HREF="#compatibility">COMPATIBILITY</A>
 <LI><A HREF="#seealso">SEE ALSO</A>
 <LI><A HREF="#author">AUTHOR</A>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pnm.html 
new/netpbm.sourceforge.net/doc/pnm.html
--- old/netpbm.sourceforge.net/doc/pnm.html     2013-02-20 04:30:31.000000000 
+0100
+++ new/netpbm.sourceforge.net/doc/pnm.html     2013-11-02 18:43:09.000000000 
+0100
@@ -7,7 +7,7 @@
 <BODY>
 
 <H1>pnm</H1>
-Updated: 03 October 2003
+Updated: 02 November 2013
 <BR>
 <A HREF="#index">Table Of Contents</A>
 
@@ -43,6 +43,15 @@
 href="libnetpbm.html">Netpbm library routines</a>, some of which aren't even
 related to the PNM format.
 
+<h3 id="internetmediatype">Internet Media Type</h3>
+
+<p>No Internet Media Type (aka MIME type, content type) for PNM has been
+registered with the IANA, but the value <tt>image/x-portable-anymap</tt>
+is conventional.
+
+<p>Note that there are also conventional Internet Media Types for each of the
+PNM subformats.
+
 <H2 id="seealso">SEE ALSO</H2>
 <A HREF="ppm.html">ppm</A>,
 <A HREF="pgm.html">pgm</A>,
@@ -56,6 +65,9 @@
 <H2 id="index">Table Of Contents</H2>
 <UL>
 <LI><A HREF="#description">DESCRIPTION</A>
+<ul>
+  <li><A HREF="#internetmediatype">Internet Media Type</A>
+    </ul>
 <LI><A HREF="#seealso">SEE ALSO</A>
 </UL>
 </BODY>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/netpbm.sourceforge.net/doc/pnmtops.html 
new/netpbm.sourceforge.net/doc/pnmtops.html
--- old/netpbm.sourceforge.net/doc/pnmtops.html 2013-06-28 23:01:40.000000000 
+0200
+++ new/netpbm.sourceforge.net/doc/pnmtops.html 2013-09-04 17:22:45.000000000 
+0200
@@ -8,7 +8,7 @@
 
 <H2>NAME</H2>
 
-pnmtops - convert PNM image to PostScript
+pnmtops - convert PNM image to Postscript
 
 <H2 id="synopsis">SYNOPSIS</H2>
 
@@ -44,11 +44,15 @@
 <p>This program is part of <a href="index.html">Netpbm</a>.
 
 <p><b>pnmtops</b> reads a Netpbm image stream as input and produces
-Encapsulated PostScript (EPSF) as output.
+Encapsulated Postscript (EPSF) as output.
+
+<p>(Note: people usually render the name as &quot;PostScript,&quot; but we use
+standard typography in the Netpbm manual, so capitalize only the first
+letter).
 
 <P>If the input file is in color (PPM), <B>pnmtops</B> generates a
-color PostScript file.  Some PostScript interpreters can't handle
-color PostScript.  If you have one of these you will need to run your
+color Postscript file.  Some Postscript interpreters can't handle
+color Postscript.  If you have one of these you will need to run your
 image through <B>ppmtopgm</B> first.
 
 <P>If you specify no output dimensioning options, the output image is
@@ -243,7 +247,7 @@
 <p>This is
 from <a 
href="http://www.lngpstscrpt.tk/re-postscript-run-length-encoding-again";>a
 forum about Postscript</a>, extracted in October 2010.  Jef added -rle in
-August 1988.  In those days, RS-232 lines (referred to a &quot;serial&quot; in
+August 1988.  In those days, RS-232 lines (referred to as &quot;serial&quot; in
 the quotation) were typically 9600bps.  2400 bps lines were still around.
 What the quotation calls &quot;the network&quot; is probably a 10 Mbps
 Ethernet connection.
@@ -336,6 +340,11 @@
      PostScript files, but can't cope with pictures which are not
      positioned in the lower left corner.
      <P>
+     If you want to position an image on the page arbitrarily, use
+     <b>pamcomp</b> to create an image of the full page with the image in
+     question at the proper place and the rest of the page white, and use
+     <b>pnmtops</b> to convert the composed result to Encapsulated Postscript.
+     <p>
      For backward compatibility, <B>pnmtops</B> accepts the option
      <B>-center</B>, but it has no effect.
 
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/netpbm.sourceforge.net/doc/ppm.html 
new/netpbm.sourceforge.net/doc/ppm.html
--- old/netpbm.sourceforge.net/doc/ppm.html     2013-05-29 03:36:51.000000000 
+0200
+++ new/netpbm.sourceforge.net/doc/ppm.html     2013-11-02 18:44:36.000000000 
+0100
@@ -6,7 +6,7 @@
 </HEAD>
 <BODY>
 <H1>ppm</H1>
-Updated: 03 October 2003
+Updated: 02 November 2013
 <BR>
 <A HREF="#index">Table Of Contents</A>
 
@@ -113,6 +113,14 @@
 <P>Note that you can use <B>pamdepth</B> to convert between a the
 format with 1 byte per sample and the one with 2 bytes per sample.
 
+<p>All characters referred to herein are encoded in ASCII.
+&quot;newline&quot; refers to the character known in ASCII as Line
+Feed or LF.  A &quot;white space&quot; character is space, CR, LF,
+TAB, VT, or FF (I.e. what the ANSI standard C isspace() function
+calls white space).
+
+<h3 id="plainppm">Plain PPM</h3>
+
 <P>There is actually another version of the PPM format that is fairly
 rare: &quot;plain&quot; PPM format.  The format above, which generally
 considered the normal one, is known as the &quot;raw&quot; PPM format.
@@ -121,26 +129,25 @@
 
 <P>The difference in the plain format is:
 
-<DL COMPACT>
-<DT>-<DD>
+<ul>
+<li>
 There is exactly one image in a file.
-<DT>-<DD>
+<li>
 The magic number is P3 instead of P6.
-<DT>-<DD>
+<li>
 Each sample in the raster is represented as an ASCII decimal number
 (of arbitrary size).
-<DT>-<DD>
+<li>
 Each sample in the raster has white space before and after it.  There must
 be at least one character of white space between any two samples, but there
 is no maximum.  There is no particular separation of one pixel from another --
 just the required separation between the blue sample of one pixel from the
 red sample of the next pixel.
-<DT>-<DD>
+<li>
 No line should be longer than 70 characters.
-</DL>
-<P>
+</ul>
 
-Here is an example of a small image in this format.
+<P>Here is an example of a small image in this format.
 <PRE>
 P3
 # feep.ppm
@@ -157,11 +164,15 @@
 <P>Programs that read this format should be as lenient as possible,
 accepting anything that looks remotely like a PPM image.
 
-<p>All characters referred to herein are encoded in ASCII.
-&quot;newline&quot; refers to the character known in ASCII as Line
-Feed or LF.  A &quot;white space&quot; character is space, CR, LF,
-TAB, VT, or FF (I.e. what the ANSI standard C isspace() function
-calls white space).
+
+<h3 id="internetmediatype">Internet Media Type</h3>
+
+<p>No Internet Media Type (aka MIME type, content type) for PBM has been
+registered with IANA, but the value <tt>image/x-portable-pixmap</tt> is
+conventional.
+
+<p>Note that the PNM Internet Media Type <tt>image/x-portable-anymap</tt>
+also applies.
 
 
 <H2 id="compatibility">COMPATIBILITY</H2>
@@ -187,6 +198,10 @@
 <H2 id="index">Table Of Contents</H2>
 <UL>
 <LI><A HREF="#description">DESCRIPTION</A>
+<ul>
+  <li><A HREF="#plainppm">Plain PPM</A>
+  <li><A HREF="#internetmediatype">Internet Media Type</A>
+    </ul>
 <LI><A HREF="#compatibility">COMPATIBILITY</A>
 <LI><A HREF="#seealso">SEE ALSO</A>
 </UL>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/netpbm.sourceforge.net/getting_netpbm.php 
new/netpbm.sourceforge.net/getting_netpbm.php
--- old/netpbm.sourceforge.net/getting_netpbm.php       2013-09-09 
15:38:15.000000000 +0200
+++ new/netpbm.sourceforge.net/getting_netpbm.php       2013-11-27 
08:57:09.000000000 +0100
@@ -341,7 +341,7 @@
 </address>
 
 <p style="font-size:75%">
-This page was generated on 09 Sep 2013.
+This page was generated on 27 Nov 2013.
 
 
 </body> </html>
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' 
'--exclude=.svnignore' old/netpbm.sourceforge.net/history.html 
new/netpbm.sourceforge.net/history.html
--- old/netpbm.sourceforge.net/history.html     2012-03-08 03:45:44.000000000 
+0100
+++ new/netpbm.sourceforge.net/history.html     2013-11-02 19:48:01.000000000 
+0100
@@ -65,13 +65,6 @@
 mentioned below.  Bryan did not know about Anderson's work until March
 2000.
 
-<p>In August 2000, the PAM format appeared.  But it took a long time
-after that for there to be enough programs and library routines to
-make it useful.  It still is barely known and used; PAM is more of a
-direction or philosophy than a practical tool.  Along with PAM came a
-whole new suite of library routines for processing both classic PNM
-and PAM format images.  The new "pam" routines are easier to use.
-
 <p>In parallel, and unknown to Bryan, Jef was working on a new release
 under the original name Pbmplus and claiming again (or maybe still) to
 be maintaining Pbmplus.  He did a limited release of a beta version of
@@ -86,6 +79,20 @@
 Metalab the new home of the source code.  But Metalab had pretty low quality
 too, and in April 2000 Bryan moved the package's home to Sourceforge.
 
+<p>In April 2000, Bryan extended the Netpbm formats to allow an image to have
+2 bytes per sample, for a maximum maxval of 65535, as opposed to the original
+formats that could have only one byte and maximum maxval 255.  This same
+extension had been made previously by others, but some of them defined the two
+bytes to be in the reverse order.  The Sourceforge version of Netpbm
+documented the byte order, ending that ambiguity.
+
+<p>In August 2000, the PAM format appeared.  But it took a long time
+after that for there to be enough programs and library routines to
+make it useful.  It still is barely known and used; PAM is more of a
+direction or philosophy than a practical tool.  Along with PAM came a
+whole new suite of library routines for processing both classic PNM
+and PAM format images.  The new "pam" routines are easier to use.
+
 <p>In June 2002, Bryan reorganized the package.  Before, it was organized to
 reflect the evolution of the package:  first PBM only, then PGM was added,
 then PPM, and then the multi-format PNM programs.  There were four separate
@@ -118,6 +125,6 @@
 <hr>
 <address>
 <font size=1>By Bryan Henderson, San Jose, CA;  [email protected]
-last checked 2007.02.24.</font>
+last checked 2013.11.02.</font>
 </address>
 </body> </html>

++++++ netpbm-10.63.1-nohpcdtoppm-noppmtompeg.tar.bz2 -> 
netpbm-10.64.4-nohpcdtoppm-noppmtompeg.tar.bz2 ++++++
++++ 5153 lines of diff (skipped)

++++++ netpbm-security-code.patch ++++++
++++ 1766 lines (skipped)
++++ between /work/SRC/openSUSE:Factory/netpbm/netpbm-security-code.patch
++++ and /work/SRC/openSUSE:Factory/.netpbm.new/netpbm-security-code.patch

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to