[Gnash-commit] gnash ChangeLog doc/C/bugreport.xml doc/C/userm...

[Benjamin Wolsey]

CVSROOT:        /sources/gnash
Module name:    gnash
Changes by:     Benjamin Wolsey <bwy>   08/03/03 15:18:23

Modified files:
        .              : ChangeLog 
        doc/C          : bugreport.xml 
        doc/C/usermanual: specification.xml 

Log message:
                * doc/C/usermanual/ (various): some typo corrections, small 
additions
                  to usage.xml and removal of obsolete options.
                * doc/C/usermanual/specifications.xml: more corrections.
                * doc/C/bugreport.xml: ditto.
        
        specifications.xml doesn't seem to be included anywhere.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnash/ChangeLog?cvsroot=gnash&r1=1.5782&r2=1.5783
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/bugreport.xml?cvsroot=gnash&r1=1.1&r2=1.2
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/usermanual/specification.xml?cvsroot=gnash&r1=1.5&r2=1.6

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnash/gnash/ChangeLog,v
retrieving revision 1.5782
retrieving revision 1.5783
diff -u -b -r1.5782 -r1.5783
--- ChangeLog   3 Mar 2008 14:59:59 -0000       1.5782
+++ ChangeLog   3 Mar 2008 15:18:20 -0000       1.5783
@@ -1,7 +1,9 @@
 2008-03-03 Benjamin Wolsey <address@hidden>
 
-       * doc/C/usermanual: some typo corrections, small additions to
-         usage.xml and removal of obsolete options.
+       * doc/C/usermanual/ (various): some typo corrections, small additions
+         to usage.xml and removal of obsolete options.
+       * doc/C/usermanual/specifications.xml: more corrections.
+       * doc/C/bugreport.xml: ditto.
 
 2008-03-03 Timo Jyrinki <address@hidden>
 

Index: doc/C/bugreport.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/bugreport.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- doc/C/bugreport.xml 2 Mar 2008 15:53:31 -0000       1.1
+++ doc/C/bugreport.xml 3 Mar 2008 15:18:21 -0000       1.2
@@ -14,7 +14,7 @@
     your bug report is, the easier it will be for the developers to
     address the issue. Bug reports without enough information will
     initially be asked to provide this information anyway. Adding
-    critical details, like the Operating System you are on, it's
+    critical details, like the Operating System you are on, its
     version, and any relevant error messages from Gnash that you get.
   </para>
 

Index: doc/C/usermanual/specification.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/usermanual/specification.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- doc/C/usermanual/specification.xml  20 Feb 2008 05:16:20 -0000      1.5
+++ doc/C/usermanual/specification.xml  3 Mar 2008 15:18:22 -0000       1.6
@@ -257,14 +257,14 @@
       object, and a final purge releases all
       still-<guilabel>UNREACHABLE</guilabel> resources. 
     </para>
-    
+<!--  
     <para>
       This garbage collector has reduced the memory footprint of &app;.
       However, the most current, available test data indicated the following
       runtime memory footprint: 
     </para>
     
-    <!--
+
        <table frame='all'>
        <title>Memory Footprint</title>
        <tgroup cols='4' align='left' colsep='1' rowsep='1'>
@@ -365,22 +365,22 @@
       <title>Local Shared Objects</title>
       
       <para>
-       SWF movies support a form of persistant storage called Local
+       SWF movies support a form of persistent storage called Local
        Shared Objects. These are stored in the subdirectories of one's
        <emphasis>~/.macromedia</emphasis> configuration. These files
-       are comonly called &quot;Flash Cookies&quot;, as they don't get
+       are commonly called &quot;Flash Cookies&quot;, as they don't get
        deleted when the SWF movie that created or writes data to them
        stops executing. These files often store things like game
-       scores. 
+       scores, but can also store a unique identifier for tracking purposes. 
       </para>
       
       <para>
        Till recently, what was contained in these files wasn't widely
        known. There are several LSO file utilities floating around on
-       the Web. Gnash has it's own <emphasis>soldumper</emphasis>
+       the Web. &app; has its own <emphasis>soldumper</emphasis>
        program that lets one find and dump the contents of these
        files. As of yet, I haven't discovered any nasty privacy issues
-       yet, but as Gnash's SharedObject support is new, I may have just
+       yet, but as &app;'s SharedObject support is new, I may have just
        been lucky.
       </para>
       
@@ -389,17 +389,17 @@
        stored in binary, big endian format. While one can look at the
        data in any binary editor or hex dumper, it's easier to use
        soldumper, which knows how to decode all the objects. The data
-       is stored in AMF format, a simple data interhange formats used
+       is stored in AMF format, a simple data interchange format used
        in several other places in SWF.
       </para>
       
       <para>
-       The one security setting Gnash supports is the
+       The one security setting &app; supports is the
        <emphasis>SOLReadOnly</emphasis> setting for your $HOME/.gnashrc
-       file. This makes Gnash never write to a .sol file, it only reads
+       file. This prevents &app; from ever writing to a .sol file, but can 
still read
        them. You can also set <emphasis>SOLSafeDir</emphasis> to a safe
-       subdirectory,or even remove it later, although most people
-       willwant to set this path to the default one created bythe other
+       subdirectory, or even remove it later, although most people
+       will want to set this path to the default one created by the other
        SWF player.
       </para>
       
@@ -411,12 +411,12 @@
       <para>
        SWF movies support a form of data interchange between running
        SWF movies called LocalConnection. This uses a shared memory
-       segment to exchange AMF objects. While the specification claim
+       segment to exchange AMF objects. While the specification claims
        an application has to register as a Listener, it turns out in
        reality this isn't required. Even YouTube violates this
        requirement. While one would think that data written to this
        memory segment would go away when the SWF movies are done
-       playing, but they are persistant, and on some systems, the data
+       playing, they are in fact persistent, and on some systems, the data
        even survives a reboot. Thank you Solaris...
       </para>
       
@@ -424,10 +424,10 @@
        The Gnash utility <emphasis>dumpshm</emphasis> can be used to do
        several things with these shared memory segments. This utility
        can find the shared memory segment left by using other SWF
-       players to see what has been left. it can then dump the contents
+       players to see what has been left. It can then dump the contents
        of the shared mempory segment either by decoding the AMF objects
        and printing the values, or by dumping the raw file to disk
-       where you can analysze it with any other program you wish. If
+       where you can analyze it with any other program you wish. If
        you run dumpshm repeatedly, you can even do a crude packet
        sniffing between two SWF movies playing.
       </para>