[xiph-commits] r17033 - in trunk/ogg: . doc

[xiphmont at svn.xiph.org]

Author: xiphmont
Date: 2010-03-25 13:28:17 -0700 (Thu, 25 Mar 2010)
New Revision: 17033

Modified:
   trunk/ogg/CHANGES
   trunk/ogg/doc/oggstream.html
Log:
Update CHANGES file

Correct one last misleading caption in the stream documentation, pending 
the more complete examples rewrite langing post 1.2.0



Modified: trunk/ogg/CHANGES
===================================================================
--- trunk/ogg/CHANGES	2010-03-25 09:30:18 UTC (rev 17032)
+++ trunk/ogg/CHANGES	2010-03-25 20:28:17 UTC (rev 17033)
@@ -1,3 +1,10 @@
+Version 1.2.0 (2010 March 25)
+
+* Alter default flushing behavior to span less often and use larger page 
+  sizes when packet sizes are large.
+* Build fixes for additional compilers
+* Documentation updates
+
 Version 1.1.4 (2009 June 24)
 
 * New async error reporting mechanism. Calls made after a fatal error are 

Modified: trunk/ogg/doc/oggstream.html
===================================================================
--- trunk/ogg/doc/oggstream.html	2010-03-25 09:30:18 UTC (rev 17032)
+++ trunk/ogg/doc/oggstream.html	2010-03-25 20:28:17 UTC (rev 17033)
@@ -462,7 +462,7 @@
 
 <em>[More to come shortly; this section is currently being revised and expanded]</em>
 
-<p>Below, we present an example of a grouped and chained bitstream:</p>
+<p>Below, we present an example of a multiplexed and chained bitstream:</p>
 
 <p><img src="stream.png" alt="stream"/></p>
 
@@ -471,18 +471,15 @@
 characteristics:</p>
 
 <ol>
-<li>Grouped bitstreams begin together; all of the initial pages
-must appear before any data pages. When concurrently multiplexed
-groups are chained, the new group does not begin until all the
-bitstreams in the previous group have terminated.</li>
+<li>Multiplexed bitstreams in a given link begin together; all of the
+initial pages must appear before any data pages. When concurrently
+multiplexed groups are chained, the new group does not begin until all
+the bitstreams in the previous group have terminated.</li>
 
-<li>The pages of concurrently multiplexed bitstreams need not conform
-to a regular order; the only requirement is that page <tt>n</tt> of a
-logical bitstream follow page <tt>n-1</tt> in the physical bitstream.
-There are no restrictions on intervening pages belonging to other
-logical bitstreams. (Tying page appearance to bitrate demands is one
-logical strategy, ie, the page appears at the chronological point
-where decode requires more information).</li>
+<li>The ordering of pages of concurrently multiplexed bitstreams is
+goverened by timestamp (not shown here); there is no regular
+interleaving order.  Pages within a logical bitstream appear in
+sequence order.</li>
 </ol>
 
 <div id="copyright">