[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnash-commit] gnash/doc/C amf.xml appendix.xml bugreport.xml ...
|
From: |
Russ Nelson |
|
Subject: |
[Gnash-commit] gnash/doc/C amf.xml appendix.xml bugreport.xml ... |
|
Date: |
Wed, 05 Mar 2008 21:05:56 +0000 |
CVSROOT: /sources/gnash
Module name: gnash
Changes by: Russ Nelson <nelsonrn> 08/03/05 21:05:55
Modified files:
doc/C : amf.xml appendix.xml bugreport.xml
conformance.xml gnash.man-xml introduction.xml
rtmp.xml security.xml sources.xml
Log message:
Fix typos and unwieldy grammar in doc/C/*.xml and doc/C/userman/*.xml
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/amf.xml?cvsroot=gnash&r1=1.5&r2=1.6
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/appendix.xml?cvsroot=gnash&r1=1.13&r2=1.14
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/bugreport.xml?cvsroot=gnash&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/conformance.xml?cvsroot=gnash&r1=1.3&r2=1.4
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/gnash.man-xml?cvsroot=gnash&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/introduction.xml?cvsroot=gnash&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/rtmp.xml?cvsroot=gnash&r1=1.7&r2=1.8
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/security.xml?cvsroot=gnash&r1=1.2&r2=1.3
http://cvs.savannah.gnu.org/viewcvs/gnash/doc/C/sources.xml?cvsroot=gnash&r1=1.46&r2=1.47
Patches:
Index: amf.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/amf.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- amf.xml 20 Feb 2008 11:13:31 -0000 1.5
+++ amf.xml 5 Mar 2008 21:05:55 -0000 1.6
@@ -9,7 +9,7 @@
</para>
<para>
- Like the RTMP messages, an AMF packet header can be of a variable
+ Like the RTMP messages, an AMF packet header varies in
size. The size is either the same as the initial header of the
RTMP message, or a 1 byte header, which is commonly used for
streaming audio or video data.
Index: appendix.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/appendix.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- appendix.xml 1 Mar 2008 21:14:05 -0000 1.13
+++ appendix.xml 5 Mar 2008 21:05:55 -0000 1.14
@@ -117,7 +117,7 @@
The <emphasis>\brief</emphasis> keyword means that the
text becomes associated
when listing all the classes on the generated web pages. The
- text after the blank link becomes the detailed description which
+ text after the blank line becomes the detailed description which
appears on the generated web page for that class and method.
</para>
</sect2>
Index: bugreport.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/bugreport.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- bugreport.xml 3 Mar 2008 15:18:21 -0000 1.2
+++ bugreport.xml 5 Mar 2008 21:05:55 -0000 1.3
@@ -3,7 +3,7 @@
<para>
The Gnash project relies on the community of Gnash users to test
- the player, feedback is critical to any successful project. Not
+ the player. Feedback is critical to any successful project. Not
only does it let us know that people use Gnash, but it helps us
understand the community's needs. Gnash uses a bug tracker on
<ulink url="http://savannah.gnu.org"; /> to manage these reports.
@@ -13,7 +13,7 @@
When filing a report, please follow the guidelines below. The better
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
+ be asked to provide this information anyway. Adding
critical details, like the Operating System you are on, its
version, and any relevant error messages from Gnash that you get.
</para>
@@ -26,8 +26,8 @@
Gnash build infrastructure allows the automated building of
binary packages. Often the version of Gnash as packaged by a
GNU/Linux or BSD distribution is based on the last official
- release, which could be months out of date. It is helpful if
- this is the case to try a newer packaged build of Gnash.
+ release, which could be months out of date. It helps us, if
+ this is the case, for you to try a newer packaged build of Gnash.
</para>
<para>
Index: conformance.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/conformance.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- conformance.xml 19 Feb 2008 02:08:36 -0000 1.3
+++ conformance.xml 5 Mar 2008 21:05:55 -0000 1.4
@@ -17,16 +17,16 @@
ActionScript 2, many of the same classes work for
both. Support has been added to Gnash's ActionScript library
to support the new ActionScript 3 filters, which get applied
- to every class. Implementing ActionScript clases is often the
+ to every class. Implementing ActionScript classes is often the
easiest way for new Gnash developers to make a contribution
- without a deep internal knpowledge of Gnash.
+ without a deep internal knowledge of Gnash.
</para>
<para>
Gnash has included video support since early 2007, but this is
- an every changing field of reverse engineering. Many of the
+ an ever changing field of reverse engineering. Many of the
popular video sharing sites use SWF v8 or v9, which Gnash
- still has imperfect support for. This is improving all the
+ supports imperfectly. This is improving all the
time, so often builds from a development snapshot will work
when using the older release packaged in your distribution
doesn't. You can find daily snapshots of the latest CVS tree
@@ -35,12 +35,12 @@
</para>
<para>
- Gnash uses ffmpeg for codecs, so any file suppored by Mplayer
+ Gnash uses ffmpeg for codecs, so any file supported by Mplayer
should work with Gnash. Gnash supports the loading of patent
free codecs like Ogg Vorbis or Theora from disk based files,
while work is being done to support these codecs when embedded
in a SWF file. Ffmpeg contains the codecs used by the current
- SWF defintion, FLV, VP6 (ON2), H.263, H.264, and MP3.
+ SWF definition, FLV, VP6 (ON2), H.263, H.264, and MP3.
</para>
<para>
@@ -48,7 +48,7 @@
<para>
This is a quick list of what is currently implemented in Gnash
- as of February, 2008.
+ as of March, 2008.
<informaltable frame="all">
<?dbhtml table-width="75%" ?>
Index: gnash.man-xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/gnash.man-xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- gnash.man-xml 1 Mar 2008 00:53:55 -0000 1.2
+++ gnash.man-xml 5 Mar 2008 21:05:55 -0000 1.3
@@ -387,7 +387,7 @@
</variablelist>
<para>
- Flash is Trademarked by Adobe Corporation.
+Flash is a registered trademark of Adobe Corporation.
</para>
</refsect2>
Index: introduction.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/introduction.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- introduction.xml 3 Mar 2008 15:00:00 -0000 1.2
+++ introduction.xml 5 Mar 2008 21:05:55 -0000 1.3
@@ -66,16 +66,16 @@
ActionScript 2, many of the same classes work for
both. Support has been added to Gnash's ActionScript library
to support the new ActionScript 3 filters, which get applied
- to every class. Implementing ActionScript clases is often the
+ to every class. Implementing ActionScript classes is often the
easiest way for new Gnash developers to make a contribution
- without a deep internal knpowledge of Gnash.
+ without a deep internal knowledge of Gnash.
</para>
<para>
Gnash has included video support since early 2007, but this is
an ever changing field of reverse engineering. Many of the
popular video sharing sites use SWF v8 or v9, which Gnash
- still has imperfect support for. This is improving all the
+ supports imperfectly. This is improving all the
time, so often builds from a development snapshot will work
when using the older release packaged in your distribution
doesn't. You can find daily snapshots of the latest CVS tree
Index: rtmp.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/rtmp.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- rtmp.xml 20 Feb 2008 11:13:31 -0000 1.7
+++ rtmp.xml 5 Mar 2008 21:05:55 -0000 1.8
@@ -48,14 +48,14 @@
<para>
The client starts the RTMP connection by sending a single byte
with a value of 0x3. This byte is followed by a data block of 1536
- bytes. The format if this data block is unknown, but it appears to
+ bytes. The format of this data block is unknown, but it appears to
not be actually used by the protocol except as a handshake.
</para>
<para>
The server receives this packet, stores the 1536 byte data block,
and then send a single byte with the value of 0x3, followed by two
- 1536 data blocks. The second data block is the full contents of
+ 1536 data blocks. The second data block has the full contents of
the original data block as sent by the client.
</para>
@@ -63,7 +63,7 @@
The client receives the 1536 byte data block, and if they match,
the connection is established. After the handshake process is
done, there are three other messages that the client sends to the
- sever to start the data flowing.
+ server to start the data flowing.
</para>
<para>
@@ -108,7 +108,7 @@
ASCII string as the message body. The following AMF packet is the
<emphasis>NetConnection</emphasis> one, which specifies that this is coming
from a Flash application. This also contains the file path the server
- can use to find the file to stream. This is then followed by the
+ can use to find the file to stream. This is followed by the
version number, which I assume is the version of the Flash player,
so the server knows what it is talking to.
</para>
@@ -363,7 +363,7 @@
<term>0x6</term>
<listitem>
<para>
- This specifies the data in the AMF packet is a
+ This specifies the data in the AMF packet is
undefined. This is also used as the return code from
calling Flash functions.
</para>
@@ -437,7 +437,7 @@
<term>0xd</term>
<listitem>
<para>
- This specifies the data in the AMF packet is a an
+ This specifies the data in the AMF packet is an
unsupported feature.
</para>
</listitem>
@@ -457,7 +457,7 @@
<term>0xf</term>
<listitem>
<para>
- This specifies the data in the AMF packet is a AML
+ This specifies the data in the AMF packet is a XML
object. XML objects are then parsed by the
<emphasis>XML</emphasis> ActionScript class.
</para>
Index: security.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/security.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- security.xml 3 Mar 2008 15:35:29 -0000 1.2
+++ security.xml 5 Mar 2008 21:05:55 -0000 1.3
@@ -30,7 +30,7 @@
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 "Flash Cookies", as they don't get
+ are commonly called "Flash Cookies", 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, but can also store a unique identifier for tracking users.
@@ -51,18 +51,18 @@
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 &app; supports is the
<emphasis>SOLReadOnly</emphasis> setting for your $HOME/.gnashrc
- file. This makes &app; never write to a .sol file, it only reads
- them. You can also set <emphasis>SOLSafeDir</emphasis> to a safe
+ file. This makes &app; only read from a .sol file, but never write.
+ You can also set <emphasis>SOLSafeDir</emphasis> to a safe
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.
+ will want to set this path to the same one used by other
+ SWF players.
</para>
</sect2>
@@ -85,8 +85,8 @@
<para>
The &app; 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
+ can find the shared memory segment created by other SWF
+ 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 analyze it with any other program you wish. If
Index: sources.xml
===================================================================
RCS file: /sources/gnash/gnash/doc/C/sources.xml,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -b -r1.46 -r1.47
--- sources.xml 20 Feb 2008 05:16:19 -0000 1.46
+++ sources.xml 5 Mar 2008 21:05:55 -0000 1.47
@@ -28,7 +28,7 @@
optimisation turned off.
</para>
<para>
- At present the Gnash source is about 500 MB to extracted and
+ At present the Gnash source is about 500 MB when extracted and
configured and requires a total of about 25 megabytes to compile
it.
</para>
@@ -771,7 +771,7 @@
<listitem>
<para>
Disable the plugin forking the standalone player, and
- using a thread for the player instead. Currently forking
+ use a thread for the player instead. Currently forking
the standalone player will give you the best results.
</para>
</listitem>
@@ -804,7 +804,7 @@
<listitem>
Simple DirectMedia Layer, a simple and portable GUI.
Its sound facilities are used when --enable-media=ffmpeg|mad
- regoardless of whether it is also in charge of the GUI.
+ regardless of whether it is also in charge of the GUI.
</listitem>
</varlistentry>
<varlistentry>
@@ -820,7 +820,7 @@
<term>FLTK</term>
<listitem>
Fast Light ToolKit, low on resource usage.
- Since all build using fltk are now broken, we declare it
+ Since all builds using fltk are now broken, we declare it
"for developers".
</listitem>
</varlistentry>
@@ -885,7 +885,7 @@
<para>
Select the specified media decoder and sound engine.
FFMPEG uses the SDL sound engine, GST uses its own.
- Using <emphasis>Gstreamer</emphasis> is the default decoder.
+ The default decoder is <emphasis>gst</emphasis>.
</para>
<para>
You should only select one media decoder.
@@ -919,15 +919,15 @@
<term>--enable-renderer=opengl|cairo|agg</term>
<listitem>
<para>
- Enable support for the a graphics backend. Currently
+ Enable support for the graphics backend. Currently
only <emphasis>opengl</emphasis> and
- <emphasis>agg</emphasis> work sufficiently. OpenGL is
+ <emphasis>agg</emphasis> work satisfactorily. OpenGL is
used when you have hardware accelerated graphics. AGG is
used when you don't have hardware accelerated
graphics. Typically most desktop machines have OpenGL
- support, and most embedded systems don't. OpenGL is the
- default when building Gnash, though the quality of AGG's
- rendering is currently superior to OpenGL.
+ support, and most embedded systems don't. AGG is the
+ default when building Gnash. AGG provides higher quality
+ rendering in this release.
</para>
</listitem>
</varlistentry>
@@ -961,7 +961,7 @@
<title>Specifying A Custom Path</title>
<para>
- This set of options typically use a <emphasis>--with-[name]</emphasis>
+ This set of options typically use an <emphasis>--with-[name]</emphasis>
naming convention. A Prefix can often be supplied, which is
the top level directory which can be used to look for the other
sub directories. Most options of this type have two
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Gnash-commit] gnash/doc/C amf.xml appendix.xml bugreport.xml ...,
Russ Nelson <=