[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnash-commit] gnash/packaging/doc gnash_ref.info.in gnash_use...
|
From: |
Rob Savoye |
|
Subject: |
[Gnash-commit] gnash/packaging/doc gnash_ref.info.in gnash_use... |
|
Date: |
Sat, 01 Mar 2008 15:18:23 +0000 |
CVSROOT: /sources/gnash
Module name: gnash
Changes by: Rob Savoye <rsavoye> 08/03/01 15:18:23
Added files:
packaging/doc : gnash_ref.info.in gnash_user.info.in
gnashuser.html.in gnashuser.ref.in
Log message:
* packaging/gnash_ref.info.in, gnash_user.info.in,
gnashuser.html.in gnashuser.ref.in: Preformatted versions of
the docs.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnash/packaging/doc/gnash_ref.info.in?cvsroot=gnash&rev=1.1
http://cvs.savannah.gnu.org/viewcvs/gnash/packaging/doc/gnash_user.info.in?cvsroot=gnash&rev=1.1
http://cvs.savannah.gnu.org/viewcvs/gnash/packaging/doc/gnashuser.html.in?cvsroot=gnash&rev=1.1
http://cvs.savannah.gnu.org/viewcvs/gnash/packaging/doc/gnashuser.ref.in?cvsroot=gnash&rev=1.1
Patches:
Index: gnash_ref.info.in
===================================================================
RCS file: gnash_ref.info.in
diff -N gnash_ref.info.in
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnash_ref.info.in 1 Mar 2008 15:18:21 -0000 1.1
@@ -0,0 +1,929 @@
+This is gnash_ref.info, produced by makeinfo version 4.8 from
+gnashref.texi.
+
+START-INFO-DIR-ENTRY
+* Gnash Reference Manual: (gnash_ref). [MISSING TEXT]
+END-INFO-DIR-ENTRY
+
+
+File: gnash_ref.info, Node: Top, Next: Introduction, Up: (dir)
+
+Gnash Reference Manual
+**********************
+
+* Menu:
+
+* Introduction::
+* RTMP Protocol::
+* Authors::
+* GNU Free Documentation License::
+
+--- The Detailed Node Listing ---
+
+Introduction
+
+* Audience::
+* What Is Supported ?::
+
+RTMP Protocol
+
+* AMF Format::
+
+GNU Free Documentation License
+
+* 0. PREAMBLE: 0_ PREAMBLE.
+* 1. APPLICABILITY AND DEFINITIONS: 1_ APPLICABILITY AND DEFINITIONS.
+* 2. VERBATIM COPYING: 2_ VERBATIM COPYING.
+* 3. COPYING IN QUANTITY: 3_ COPYING IN QUANTITY.
+* 4. MODIFICATIONS: 4_ MODIFICATIONS.
+* 5. COMBINING DOCUMENTS: 5_ COMBINING DOCUMENTS.
+* 6. COLLECTIONS OF DOCUMENTS: 6_ COLLECTIONS OF DOCUMENTS.
+* 7. AGGREGATION WITH INDEPENDENT WORKS: 7_ AGGREGATION WITH INDEPENDENT WORKS.
+* 8. TRANSLATION: 8_ TRANSLATION.
+* 9. TERMINATION: 9_ TERMINATION.
+* 10. FUTURE REVISIONS OF THIS LICENSE: 10_ FUTURE REVISIONS OF THIS LICENSE.
+* Addendum::
+
+
+File: gnash_ref.info, Node: Introduction, Next: RTMP Protocol, Prev: Top,
Up: Top
+
+1 Introduction
+**************
+
+Gnash is a free SWF movie player. It is available as a stand-alone
+application or as a plugin for several popular web browsers. It
+supports playing media from a disk or streaming over a network
+connection. Some popular video sharing sites like YouTube are supported
+from a wide vaariety of devices from embedded ones to modern desktops.
+
+ Gnash has a better focus on security, allowing the user tight
+control of all network or disk based I/O. Gnash also supports extending
+ActionScript by creating your own. You can write wrappers for any
+development library, and import them into the player much like perl or
+python does.
+
+* Menu:
+
+* Audience::
+* What Is Supported ?::
+
+
+File: gnash_ref.info, Node: Audience, Next: What Is Supported ?, Up:
Introduction
+
+1.1 Audience
+============
+
+This manual is primarily focused on users interested in how to get
+Gnash installed from a package, and basic usage as a web browser
+plugin. For more technical details, please refer to the Gnash Reference
+manual.
+
+
+File: gnash_ref.info, Node: What Is Supported ?, Prev: Audience, Up:
Introduction
+
+1.2 What Is Supported ?
+=======================
+
+Gnash is known to compile for most any POSIX and ANSI C++ conforming
+system if you have all the dependent libraries installed. Systems we
+test on, and which Gnash is know to run on are Ubuntu, Fedora, Debian,
+OpenBSD, NetBSD, FreeBSD, Win32, and Darwin (OSX) primarily.
+Occasionally other platforms are built, primarily by those distribution
+maintainers. This includes BeOS, Haiku, Syllable, OS/2, Solaris,
+Slackware, and Gentoo.
+
+ Gnash is a capable of reading up to SWF v9 files and opcodes, but
+primarily supports SWF v7, with better SWF v8 and v9 support under
+heavy developement. With the 0.8.2 release, Gnash includes initial
+parser support for SWF v8 and v9. Not all ActionScript 2 classes are
+implemented yet, but all of the most heavily used ones are. Many
+ActionScript 2 classes are partially implemented; there is support for
+all of the commonly used methods of each class.
+
+ Gnash has implemented about 80% of ActionScript v. 2.0, and has
+begun implementing ActionScript v. 3.0. Gnash supports the majority of
+Flash opcodes up to SWF version 9, and a wide sampling of ActionScript
+classes for SWF version 8.
+
+ As ActionsScript 3 is a more developed version of 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 easiest way for new Gnash developers to make a contribution
+without a deep internal knpowledge of Gnash.
+
+ Gnash has included video support since early 2007, but this is an
+every 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 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 at: http://www.gnashdev.org/dev_snapshots
+(http://www.gnashdev.org/dev_snapshots/).
+
+ 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.
+
+
+File: gnash_ref.info, Node: RTMP Protocol, Next: Authors, Prev:
Introduction, Up: Top
+
+2 RTMP Protocol
+***************
+
+This document is based mostly on my own reverse engineering of the RTMP
+protocol and AMF format. _tcpdump_ and _ethereal_ are your friend. Some
+additional info that got me started was from the Red5
+(http://www.osflash.org/red5) project. _Red5_ is the only other open
+source Flash server. So some details are still vague, but as the
+implementation appears to work, we'll figure out what they are later.
+
+ The Real Time Messaging Protocol was created by MacroMedia (now
+Adobe) for delivering Flash objects and video over a network
+connection. Currently the only servers which support this format are
+the MacroMedia Media sever, and the Open Source Red5 project.
+
+ This is a simple protocol, optimized for poor bandwidth connections.
+It can support up to 64 concurrent streams over the same network
+connection. Part of each AMF packet header contains the index number of
+the stream. A single RTMP message can contain multiple AMF packets.
+
+ An RTMP connection uses Tcp/ip port 1935. It is also possible to
+tunnel RTMP over an HTTP connection using port 80. Each AMF packet is
+128 bytes long except for streaming audio, which has 64 byte packets.
+
+ The basics of the RTMP protocol are as follows. All communications
+are initiated by the client.
+
+Image of the RTMP protocol.
+
+ 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 not be
+actually used by the protocol except as a handshake.
+
+ 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 the original
+data block as sent by the client.
+
+ 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.
+
+ The first AMF packet sent to the server contains the _connect_
+packet. This doesn't appear to do much but notify the server the client
+is happy with the handshake, and ready to start reading packets.
+
+ The second packet is the _NetConnection_ object from the client.
+This ActionScript class is used by the Flash movie to create the
+network connection to the server.
+
+ The third packet is the _NetStream_ object from the client. This is
+the ActionScript class used to specify the file to be streamed by the
+server.
+
+ The RTMP packet for our example looks like this:
+
+
+ 030000190000c91400000000020007connect00?f0000000000000030003app0200#
+ software/gnash/tests/1153948634.flv0008flashVer02000cLNX 6,0,82,0
0006
+ swfUrl02001dfile:///file|%2Ftmp%2Fout.swfc30005tcUrl\002\0004
+ rtmp://localhost/software/gnash/tests/1153948634.flv\000\000\t
+ \002\000\005userx
+
+We'll take this apart in a bit, but you can see how all three AMF
+packets are in the same message. The message is received in several 128
+byte blocks, with the last one being less than that. The total size of
+the RTMP message is in the header, so the reader can tell if the entire
+message was read or not.
+
+ The RTMP header is first, followed by the connect message as an
+ASCII string as the message body. The following AMF packet is the
+_NetConnection_ 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 version number,
+which I assume is the version of the Flash player, so the server knows
+what it is talking to.
+
+ The third packet is the one from _NetStream_, which specifies the
+URL used for the movie, followed by the user name for a semblance of
+security.
+
+ For the next level of detail, we'll explain the format of AMF. AMF
+is used by the RTMP protocol to transfer data. Each Flash object is
+encapsulated in an AMF packet, including streaming audio or video.
+
+ The first byte of the RTMP header determines two things about the
+rest of the message. The first 2 bits of this byte signify the total
+size of the RTMP header. The RTMP header is of a variable size, so this
+is important.
+
+00
+ This specifies the header contains 12 bytes, including this one.
+
+01
+ This specifies the header contains 8 bytes, including this one.
+
+02
+ This specifies the header contains 4 bytes, including this one.
+
+03
+ This specifies the header contains 1 byte, so this is the complete
+ header.
+
+ The other 6 bits in this byte represent the AMF index. As a single
+RTMP connection can support multiple data streams, this signifies which
+stream this packet is for. Once an AMF object is fully received by the
+client, the AMF index may be reused.
+
+ For messages with headers of at least 4 bytes, the next 3 bytes are
+used by audio and video data packets, but at this time the meaning of
+this field is unknown.
+
+ For messages with a 8 byte or larger header, the next 3 bytes
+determine the size of the RTMP message being transmitted. Messages with
+a 1 byte or 4 byte header use a standard size, 128 bytes for video, and
+64 bytes for audio.
+
+ For messages with an 8 byte or larger header, the next byte is the
+type of the AMF object.
+
+0x3
+ This specifies the content type of the RTMP packet is the number
+ of bytes read. This is used to start the RTMP connection.
+
+0x4
+ This specifies the content type of the RTMP message is a _ping_
+ packet.
+
+0x5
+ This specifies the content type of the RTMP message is server
+ response of some type.
+
+0x6
+ This specifies the content type of the RTMP packet is client
+ request of some type.
+
+0x8
+ This specifies the content type of the RTMP packet is an audio
+ message.
+
+0x9
+ This specifies the content type of the RTMP message is a video
+ packet.
+
+0x12
+ This specifies the content type of the RTMP message is notify.
+
+0x13
+ This specifies the content type of the RTMP message is shared
+ object.
+
+0x14
+ This specifies the content type of the RTMP message is remote
+ procedure call. This invokes the method of a Flash class remotely.
+
+ There are two sets of data types to consider. One set is used by the
+to specify the content type of the AMF object, the other is an
+ActionScript data type tag used to denote which type of object is being
+transferred.
+
+ The values of the initial type byte are:
+
+0x0
+ This specifies the data in the AMF packet is a numeric value. All
+ numeric values in Flash are 64 bit, _big-endian_.
+
+0x1
+ This specifies the data in the AMF packet is a boolean value.
+
+0x2
+ This specifies the data in the AMF packet is an _ASCII_ string.
+
+0x3
+ This specifies the data in the AMF packet is a Flash object. The
+ Flash object data type field further along in the message
+ specifies which type of ActionScript object it is.
+
+0x4
+ This specifies the data in the AMF packet is a Flash movie, ie.
+ another Flash movie.
+
+0x5
+ This specifies the data in the AMF packet is a NULL value. NULL is
+ often used as the return code from calling Flash functions.
+
+0x6
+ This specifies the data in the AMF packet is a undefined. This is
+ also used as the return code from calling Flash functions.
+
+0x7
+ This specifies the data in the AMF packet is a reference.
+
+0x8
+ This specifies the data in the AMF packet is a ECMA array.
+
+0x9
+ This specifies the data in the AMF packet is the end of an object
+ definition. As an object is transmitted with multiple AMF packets,
+ this lets the server know when the end of the object is reached.
+
+0xa
+ This specifies the data in the AMF packet is a Strict array.
+
+0xb
+ This specifies the data in the AMF packet is a date.
+
+0xc
+ This specifies the data in the AMF packet is a multi-byte string.
+ Multi-byte strings are used for international language support to
+ represent non _ASCII_ fonts.
+
+0xd
+ This specifies the data in the AMF packet is a an unsupported
+ feature.
+
+0xe
+ This specifies the data in the AMF packet is a record set.
+
+0xf
+ This specifies the data in the AMF packet is a AML object. XML
+ objects are then parsed by the _XML_ ActionScript class.
+
+0x10
+ This specifies the data in the AMF packet is a typed object.
+
+ For messages with a 12 byte header, the last 4 bytes are the routing
+of the message. If the destination is the server, this value is the
+NetStream object source. If the destination is the client, this is the
+NetStream object for this RTMP message. A value of 0x00000000 appears
+to be reserved for the NetConnection object.
+
+ Multiple AMF streams can be contained in a single RTMP messages, so
+it's important to check the index of each AMF packet.
+
+ An example RTMP header might look like this. (spaces added between
+fields for clarity) All the numbers are in hex.
+
+
+ 03 000019 0000c9 14 000000000
+
+03
+ The first two bits of this byte are the size of the header, which
+ in this example is 00, for a 12 byte header. The next 6 bits is
+ the AMF stream index number, which in this example is 0x3.
+
+000019
+ These 3 bytes currently have an unknown purpose.
+
+000c9
+ Since this example has a 12 byte header, this is the size of the
+ RTMP message, in this case 201 bytes.
+
+14
+ This is the content type of the RTMP message, which in this case
+ is to invoke a remote function call. (which we later see is the
+ connect function).
+
+00000000
+ The source is the NetConnection object used to start this
+ connection.
+
+* Menu:
+
+* AMF Format::
+
+
+File: gnash_ref.info, Node: AMF Format, Up: RTMP Protocol
+
+2.1 AMF Format
+==============
+
+The AMF format is used in the LocalConnection, SharedObject,
+NetConnection, and NetStream ActionScript classes. This is a means of
+binary data interchange between Flash movies, or between a Flash player
+and a Flash server.
+
+ Like the RTMP messages, an AMF packet header can be of a variable
+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.
+
+ The body of an AMF packet may look something like this example. The
+spaces have been added for clarity.
+
+
+ 02 0007 636f6e6e656374
+
+02
+ This is a single byte header. The value of the first 2 bits is
+ 0x3, and the AMF index is also 0x3.
+
+0007
+ This is the length in bytes of the string.
+
+63 6f 6e 6e 65 63 74
+ This is the string. Note that there is no null terminator since
+ the length is specified.
+
+
+File: gnash_ref.info, Node: Authors, Next: GNU Free Documentation License,
Prev: RTMP Protocol, Up: Top
+
+3 Authors
+*********
+
+Gnash is maintained by Rob Savoye. Other active developers are: Sandro
+Santilli, Bastiaan Jacques, Udo Giacomozzi, Chad Musick, Benjamin
+Wolsey, and Zou Lunkai. Please send all comments and suggestions to
+<address@hidden>. Past and sometimes current developers are Tomas
+Groth and Markus Gothe.
+
+ Gnash was initially derived from GameSWF. GameSWF is maintained by
+Thatcher Ulrich <address@hidden>. The following people contributed to
+GameSWF: Mike Shaver, Thierry Berger-Perrin, Ignacio Castan~o, Willem
+Kokke, Vitaly Alexeev, Alexander Streit, and Rob Savoye.
+
+
+File: gnash_ref.info, Node: GNU Free Documentation License, Prev: Authors,
Up: Top
+
+Appendix A GNU Free Documentation License
+*****************************************
+
+* Menu:
+
+* 0. PREAMBLE: 0_ PREAMBLE.
+* 1. APPLICABILITY AND DEFINITIONS: 1_ APPLICABILITY AND DEFINITIONS.
+* 2. VERBATIM COPYING: 2_ VERBATIM COPYING.
+* 3. COPYING IN QUANTITY: 3_ COPYING IN QUANTITY.
+* 4. MODIFICATIONS: 4_ MODIFICATIONS.
+* 5. COMBINING DOCUMENTS: 5_ COMBINING DOCUMENTS.
+* 6. COLLECTIONS OF DOCUMENTS: 6_ COLLECTIONS OF DOCUMENTS.
+* 7. AGGREGATION WITH INDEPENDENT WORKS: 7_ AGGREGATION WITH INDEPENDENT WORKS.
+* 8. TRANSLATION: 8_ TRANSLATION.
+* 9. TERMINATION: 9_ TERMINATION.
+* 10. FUTURE REVISIONS OF THIS LICENSE: 10_ FUTURE REVISIONS OF THIS LICENSE.
+* Addendum::
+
+
+File: gnash_ref.info, Node: 0_ PREAMBLE, Next: 1_ APPLICABILITY AND
DEFINITIONS, Up: GNU Free Documentation License
+
+A.1 0. PREAMBLE
+===============
+
+The purpose of this License is to make a manual, textbook, or other
+written document "free" in the sense of freedom: to assure everyone the
+effective freedom to copy and redistribute it, with or without
+modifying it, either commercially or non-commercially. Secondarily,
+this License preserves for the author and publisher a way to get credit
+for their work, while not being considered responsible for
+modifications made by others.
+
+ This License is a kind of "copyleft", which means that derivative
+works of the document must themselves be free in the same sense. It
+complements the GNU General Public License, which is a copyleft license
+designed for free software.
+
+ We have designed this License in order to use it for manuals for
+free software, because free software needs free documentation: a free
+program should come with manuals providing the same freedoms that the
+software does. But this License is not limited to software manuals; it
+can be used for any textual work, regardless of subject matter or
+whether it is published as a printed book. We recommend this License
+principally for works whose purpose is instruction or reference.
+
+
+File: gnash_ref.info, Node: 1_ APPLICABILITY AND DEFINITIONS, Next: 2_
VERBATIM COPYING, Prev: 0_ PREAMBLE, Up: GNU Free Documentation License
+
+A.2 1. APPLICABILITY AND DEFINITIONS
+====================================
+
+This License applies to any manual or other work that contains a notice
+placed by the copyright holder saying it can be distributed under the
+terms of this License. The "Document", below, refers to any such manual
+or work. Any member of the public is a licensee, and is addressed as
+"you".
+
+ A "Modified Version" of the Document means any work containing the
+Document or a portion of it, either copied verbatim, or with
+modifications and/or translated into another language.
+
+ A "Secondary Section" is a named appendix or a front-matter section
+of the Document (*note fdl-document::) that deals exclusively with the
+relationship of the publishers or authors of the Document to the
+Document's overall subject (or to related matters) and contains nothing
+that could fall directly within that overall subject. (For example, if
+the Document is in part a textbook of mathematics, a Secondary Section
+may not explain any mathematics.) The relationship could be a matter
+of historical connection with the subject or with related matters, or of
+legal, commercial, philosophical, ethical or political position
+regarding them.
+
+ The "Invariant Sections" are certain Secondary Sections (*note
+fdl-secondary::) whose titles are designated, as being those of
+Invariant Sections, in the notice that says that the Document (*note
+fdl-document::) is released under this License.
+
+ The "Cover Texts" are certain short passages of text that are
+listed, as Front-Cover Texts or Back-Cover Texts, in the notice that
+says that the Document (*note fdl-document::) is released under this
+License.
+
+ A "Transparent" copy of the Document (*note fdl-document::) means a
+machine-readable copy, represented in a format whose specification is
+available to the general public, whose contents can be viewed and edited
+directly and straightforwardly with generic text editors or (for images
+composed of pixels) generic paint programs or (for drawings) some
+widely available drawing editor, and that is suitable for input to text
+formatters or for automatic translation to a variety of formats
+suitable for input to text formatters. A copy made in an otherwise
+Transparent file format whose markup has been designed to thwart or
+discourage subsequent modification by readers is not Transparent. A
+copy that is not "Transparent" is called "Opaque".
+
+ Examples of suitable formats for Transparent copies include plain
+ASCII without markup, Texinfo input format, LaTeX input format, SGML or
+XML using a publicly available DTD, and standard-conforming simple HTML
+designed for human modification. Opaque formats include PostScript, PDF,
+proprietary formats that can be read and edited only by proprietary
+word processors, SGML or XML for which the DTD and/or processing tools
+are not generally available, and the machine-generated HTML produced by
+some word processors for output purposes only.
+
+ The "Title Page" means, for a printed book, the title page itself,
+plus such following pages as are needed to hold, legibly, the material
+this License requires to appear in the title page. For works in formats
+which do not have any title page as such, "Title Page" means the text
+near the most prominent appearance of the work's title, preceding the
+beginning of the body of the text.
+
+
+File: gnash_ref.info, Node: 2_ VERBATIM COPYING, Next: 3_ COPYING IN
QUANTITY, Prev: 1_ APPLICABILITY AND DEFINITIONS, Up: GNU Free Documentation
License
+
+A.3 2. VERBATIM COPYING
+=======================
+
+You may copy and distribute the Document (*note fdl-document::) in any
+medium, either commercially or noncommercially, provided that this
+License, the copyright notices, and the license notice saying this
+License applies to the Document are reproduced in all copies, and that
+you add no other conditions whatsoever to those of this License. You
+may not use technical measures to obstruct or control the reading or
+further copying of the copies you make or distribute. However, you may
+accept compensation in exchange for copies. If you distribute a large
+enough number of copies you must also follow the conditions in section
+3 (*note 3_ COPYING IN QUANTITY::).
+
+ You may also lend copies, under the same conditions stated above,
+and you may publicly display copies.
+
+
+File: gnash_ref.info, Node: 3_ COPYING IN QUANTITY, Next: 4_ MODIFICATIONS,
Prev: 2_ VERBATIM COPYING, Up: GNU Free Documentation License
+
+A.4 3. COPYING IN QUANTITY
+==========================
+
+If you publish printed copies of the Document (*note fdl-document::)
+numbering more than 100, and the Document's license notice requires
+Cover Texts (*note fdl-cover-texts::), you must enclose the copies in
+covers that carry, clearly and legibly, all these Cover Texts:
+Front-Cover Texts on the front cover, and Back-Cover Texts on the back
+cover. Both covers must also clearly and legibly identify you as the
+publisher of these copies. The front cover must present the full title
+with all words of the title equally prominent and visible. You may add
+other material on the covers in addition. Copying with changes limited
+to the covers, as long as they preserve the title of the Document
+(*note fdl-document::) and satisfy these conditions, can be treated as
+verbatim copying in other respects.
+
+ If the required texts for either cover are too voluminous to fit
+legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto adjacent
+pages.
+
+ If you publish or distribute Opaque (*note fdl-transparent::) copies
+of the Document (*note fdl-document::) numbering more than 100, you
+must either include a machine-readable Transparent (*note
+fdl-transparent::) copy along with each Opaque copy, or state in or
+with each Opaque copy a publicly-accessible computer-network location
+containing a complete Transparent copy of the Document, free of added
+material, which the general network-using public has access to download
+anonymously at no charge using public-standard network protocols. If
+you use the latter option, you must take reasonably prudent steps, when
+you begin distribution of Opaque copies in quantity, to ensure that
+this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you distribute an
+Opaque copy (directly or through your agents or retailers) of that
+edition to the public.
+
+ It is requested, but not required, that you contact the authors of
+the Document (*note fdl-document::) well before redistributing any
+large number of copies, to give them a chance to provide you with an
+updated version of the Document.
+
+
+File: gnash_ref.info, Node: 4_ MODIFICATIONS, Next: 5_ COMBINING DOCUMENTS,
Prev: 3_ COPYING IN QUANTITY, Up: GNU Free Documentation License
+
+A.5 4. MODIFICATIONS
+====================
+
+You may copy and distribute a Modified Version (*note fdl-modified::)
+of the Document (*note fdl-document::) under the conditions of sections
+2 (*note 2_ VERBATIM COPYING::) and 3 (*note 3_ COPYING IN QUANTITY::)
+above, provided that you release the Modified Version under precisely
+this License, with the Modified Version filling the role of the
+Document, thus licensing distribution and modification of the Modified
+Version to whoever possesses a copy of it. In addition, you must do
+these things in the Modified Version:
+
+ * *A. * Use in the Title Page (*note fdl-title-page::) (and on the
+ covers, if any) a title distinct from that of the Document (*note
+ fdl-document::), and from those of previous versions (which
+ should, if there were any, be listed in the History section of the
+ Document). You may use the same title as a previous version if the
+ original publisher of that version gives permission.
+
+ * *B. * List on the Title Page (*note fdl-title-page::), as authors,
+ one or more persons or entities responsible for authorship of the
+ modifications in the Modified Version (*note fdl-modified::),
+ together with at least five of the principal authors of the
+ Document (*note fdl-document::) (all of its principal authors, if
+ it has less than five).
+
+ * *C. * State on the Title Page (*note fdl-title-page::) the name of
+ the publisher of the Modified Version (*note fdl-modified::), as
+ the publisher.
+
+ * *D. * Preserve all the copyright notices of the Document (*note
+ fdl-document::).
+
+ * *E. * Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.
+
+ * *F. * Include, immediately after the copyright notices, a license
+ notice giving the public permission to use the Modified Version
+ (*note fdl-modified::) under the terms of this License, in the
+ form shown in the Addendum below.
+
+ * *G. * Preserve in that license notice the full lists of Invariant
+ Sections (*note fdl-invariant::) and required Cover Texts (*note
+ fdl-cover-texts::) given in the Document's (*note fdl-document::)
+ license notice.
+
+ * *H. * Include an unaltered copy of this License.
+
+ * *I. * Preserve the section entitled "History", and its title, and
+ add to it an item stating at least the title, year, new authors,
+ and publisher of the Modified Version (*note fdl-modified::)as
+ given on the Title Page (*note fdl-title-page::). If there is no
+ section entitled "History" in the Document (*note fdl-document::),
+ create one stating the title, year, authors, and publisher of the
+ Document as given on its Title Page, then add an item describing
+ the Modified Version as stated in the previous sentence.
+
+ * *J. * Preserve the network location, if any, given in the Document
+ (*note fdl-document::) for public access to a Transparent (*note
+ fdl-transparent::) copy of the Document, and likewise the network
+ locations given in the Document for previous versions it was based
+ on. These may be placed in the "History" section. You may omit a
+ network location for a work that was published at least four years
+ before the Document itself, or if the original publisher of the
+ version it refers to gives permission.
+
+ * *K. * In any section entitled "Acknowledgements" or "Dedications",
+ preserve the section's title, and preserve in the section all the
+ substance and tone of each of the contributor acknowledgements
+ and/or dedications given therein.
+
+ * *L. * Preserve all the Invariant Sections (*note fdl-invariant::)
+ of the Document (*note fdl-document::), unaltered in their text
+ and in their titles. Section numbers or the equivalent are not
+ considered part of the section titles.
+
+ * *M. * Delete any section entitled "Endorsements". Such a section
+ may not be included in the Modified Version (*note fdl-modified::).
+
+ * *N. * Do not retitle any existing section as "Endorsements" or to
+ conflict in title with any Invariant Section (*note
+ fdl-invariant::).
+
+ If the Modified Version (*note fdl-modified::) includes new
+front-matter sections or appendices that qualify as Secondary Sections
+(*note fdl-secondary::) and contain no material copied from the
+Document, you may at your option designate some or all of these
+sections as invariant. To do this, add their titles to the list of
+Invariant Sections (*note fdl-invariant::) in the Modified Version's
+license notice. These titles must be distinct from any other section
+titles.
+
+ You may add a section entitled "Endorsements", provided it contains
+nothing but endorsements of your Modified Version (*note
+fdl-modified::) by various parties-for example, statements of peer
+review or that the text has been approved by an organization as the
+authoritative definition of a standard.
+
+ You may add a passage of up to five words as a Front-Cover Text
+(*note fdl-cover-texts::), and a passage of up to 25 words as a
+Back-Cover Text (*note fdl-cover-texts::), to the end of the list of
+Cover Texts (*note fdl-cover-texts::) in the Modified Version (*note
+fdl-modified::). Only one passage of Front-Cover Text and one of
+Back-Cover Text may be added by (or through arrangements made by) any
+one entity. If the Document (*note fdl-document::) already includes a
+cover text for the same cover, previously added by you or by
+arrangement made by the same entity you are acting on behalf of, you
+may not add another; but you may replace the old one, on explicit
+permission from the previous publisher that added the old one.
+
+ The author(s) and publisher(s) of the Document (*note
+fdl-document::) do not by this License give permission to use their
+names for publicity for or to assert or imply endorsement of any
+Modified Version (*note fdl-modified::).
+
+
+File: gnash_ref.info, Node: 5_ COMBINING DOCUMENTS, Next: 6_ COLLECTIONS OF
DOCUMENTS, Prev: 4_ MODIFICATIONS, Up: GNU Free Documentation License
+
+A.6 5. COMBINING DOCUMENTS
+==========================
+
+You may combine the Document (*note fdl-document::) with other
+documents released under this License, under the terms defined in
+section 4 (*note 4_ MODIFICATIONS::) above for modified versions,
+provided that you include in the combination all of the Invariant
+Sections (*note fdl-invariant::) of all of the original documents,
+unmodified, and list them all as Invariant Sections of your combined
+work in its license notice.
+
+ The combined work need only contain one copy of this License, and
+multiple identical Invariant Sections (*note fdl-invariant::) may be
+replaced with a single copy. If there are multiple Invariant Sections
+with the same name but different contents, make the title of each such
+section unique by adding at the end of it, in parentheses, the name of
+the original author or publisher of that section if known, or else a
+unique number. Make the same adjustment to the section titles in the
+list of Invariant Sections in the license notice of the combined work.
+
+ In the combination, you must combine any sections entitled "History"
+in the various original documents, forming one section entitled
+"History"; likewise combine any sections entitled "Acknowledgements",
+and any sections entitled "Dedications". You must delete all sections
+entitled "Endorsements."
+
+
+File: gnash_ref.info, Node: 6_ COLLECTIONS OF DOCUMENTS, Next: 7_
AGGREGATION WITH INDEPENDENT WORKS, Prev: 5_ COMBINING DOCUMENTS, Up: GNU
Free Documentation License
+
+A.7 6. COLLECTIONS OF DOCUMENTS
+===============================
+
+You may make a collection consisting of the Document (*note
+fdl-document::) and other documents released under this License, and
+replace the individual copies of this License in the various documents
+with a single copy that is included in the collection, provided that
+you follow the rules of this License for verbatim copying of each of the
+documents in all other respects.
+
+ You may extract a single document from such a collection, and
+distribute it individually under this License, provided you insert a
+copy of this License into the extracted document, and follow this
+License in all other respects regarding verbatim copying of that
+document.
+
+
+File: gnash_ref.info, Node: 7_ AGGREGATION WITH INDEPENDENT WORKS, Next: 8_
TRANSLATION, Prev: 6_ COLLECTIONS OF DOCUMENTS, Up: GNU Free Documentation
License
+
+A.8 7. AGGREGATION WITH INDEPENDENT WORKS
+=========================================
+
+A compilation of the Document (*note fdl-document::) or its derivatives
+with other separate and independent documents or works, in or on a
+volume of a storage or distribution medium, does not as a whole count
+as a Modified Version (*note fdl-modified::) of the Document, provided
+no compilation copyright is claimed for the compilation. Such a
+compilation is called an "aggregate", and this License does not apply
+to the other self-contained works thus compiled with the Document , on
+account of their being thus compiled, if they are not themselves
+derivative works of the Document. If the Cover Text (*note
+fdl-cover-texts::) requirement of section 3 (*note 3_ COPYING IN
+QUANTITY::) is applicable to these copies of the Document, then if the
+Document is less than one quarter of the entire aggregate, the
+Document's Cover Texts may be placed on covers that surround only the
+Document within the aggregate. Otherwise they must appear on covers
+around the whole aggregate.
+
+
+File: gnash_ref.info, Node: 8_ TRANSLATION, Next: 9_ TERMINATION, Prev: 7_
AGGREGATION WITH INDEPENDENT WORKS, Up: GNU Free Documentation License
+
+A.9 8. TRANSLATION
+==================
+
+Translation is considered a kind of modification, so you may distribute
+translations of the Document (*note fdl-document::) under the terms of
+section 4 (*note 4_ MODIFICATIONS::). Replacing Invariant Sections
+(*note fdl-invariant::) with translations requires special permission
+from their copyright holders, but you may include translations of some
+or all Invariant Sections in addition to the original versions of these
+Invariant Sections. You may include a translation of this License
+provided that you also include the original English version of this
+License. In case of a disagreement between the translation and the
+original English version of this License, the original English version
+will prevail.
+
+
+File: gnash_ref.info, Node: 9_ TERMINATION, Next: 10_ FUTURE REVISIONS OF
THIS LICENSE, Prev: 8_ TRANSLATION, Up: GNU Free Documentation License
+
+A.10 9. TERMINATION
+===================
+
+You may not copy, modify, sublicense, or distribute the Document (*note
+fdl-document::) except as expressly provided for under this License.
+Any other attempt to copy, modify, sublicense or distribute the
+Document is void, and will automatically terminate your rights under
+this License. However, parties who have received copies, or rights,
+from you under this License will not have their licenses terminated so
+long as such parties remain in full compliance.
+
+
+File: gnash_ref.info, Node: 10_ FUTURE REVISIONS OF THIS LICENSE, Next:
Addendum, Prev: 9_ TERMINATION, Up: GNU Free Documentation License
+
+A.11 10. FUTURE REVISIONS OF THIS LICENSE
+=========================================
+
+The Free Software Foundation (http://www.gnu.org/fsf/fsf.html) may
+publish new, revised versions of the GNU Free Documentation License
+from time to time. Such new versions will be similar in spirit to the
+present version, but may differ in detail to address new problems or
+concerns. See http://www.gnu.org/copyleft/
+(http://www.gnu.org/copyleft).
+
+ Each version of the License is given a distinguishing version
+number. If the Document (*note fdl-document::) specifies that a
+particular numbered version of this License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that specified version or of any later version
+that has been published (not as a draft) by the Free Software
+Foundation. If the Document does not specify a version number of this
+License, you may choose any version ever published (not as a draft) by
+the Free Software Foundation.
+
+
+File: gnash_ref.info, Node: Addendum, Prev: 10_ FUTURE REVISIONS OF THIS
LICENSE, Up: GNU Free Documentation License
+
+A.12 Addendum
+=============
+
+To use this License in a document you have written, include a copy of
+the License in the document and put the following copyright and license
+notices just after the title page:
+
+ Copyright 2008, Free Software Foundation.
+
+ Permission is granted to copy, distribute and/or modify this
+ document under the terms of the GNU Free Documentation License,
+ Version 1.1 or any later version published by the Free Software
+ Foundation; with noInvariant Sections (*note fdl-invariant::),
+ with no Front-Cover Texts (*note fdl-cover-texts::), and with no
+ Back-Cover Texts (*note fdl-cover-texts::). A copy of the license
+ is included in the section entitled "GNU Free Documentation
+ License".
+
+ If your document contains nontrivial examples of program code, we
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License
+(http://www.gnu.org/copyleft/gpl.html), to permit their use in free
+software.
+
+
+
+Tag Table:
+Node: Top175
+Node: Introduction1113
+Node: Audience1907
+Node: What Is Supported ?2235
+Node: RTMP Protocol4767
+Node: AMF Format14538
+Node: Authors15514
+Node: GNU Free Documentation License16215
+Node: 0_ PREAMBLE16978
+Node: 1_ APPLICABILITY AND DEFINITIONS18284
+Ref: fdl-document18509
+Ref: fdl-modified18800
+Ref: fdl-secondary18987
+Ref: fdl-invariant19632
+Ref: fdl-cover-texts19881
+Ref: fdl-transparent20094
+Ref: fdl-title-page21384
+Node: 2_ VERBATIM COPYING21773
+Node: 3_ COPYING IN QUANTITY22753
+Node: 4_ MODIFICATIONS25110
+Node: 5_ COMBINING DOCUMENTS31170
+Node: 6_ COLLECTIONS OF DOCUMENTS32667
+Node: 7_ AGGREGATION WITH INDEPENDENT WORKS33558
+Node: 8_ TRANSLATION34786
+Node: 9_ TERMINATION35689
+Node: 10_ FUTURE REVISIONS OF THIS LICENSE36344
+Node: Addendum37484
+
+End Tag Table
Index: gnash_user.info.in
===================================================================
RCS file: gnash_user.info.in
diff -N gnash_user.info.in
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnash_user.info.in 1 Mar 2008 15:18:22 -0000 1.1
@@ -0,0 +1,1974 @@
+This is gnash_user.info, produced by makeinfo version 4.8 from
+gnashuser.texi.
+
+START-INFO-DIR-ENTRY
+* Gnash User Manual: (gnash_user). [MISSING TEXT]
+END-INFO-DIR-ENTRY
+
+
+File: gnash_user.info, Node: Top, Next: Introduction, Up: (dir)
+
+Gnash User Manual
+*****************
+
+* Menu:
+
+* Introduction::
+* Using Gnash::
+* Installing and Configuring Gnash::
+* Reporting Bugs::
+* Glossary::
+* Authors::
+* GNU Free Documentation License::
+
+--- The Detailed Node Listing ---
+
+Introduction
+
+* Audience::
+* What Is Supported ?::
+
+Using Gnash
+
+* Gnash Command Line Options::
+* Gnash Interactive Control Keys::
+* User Configuration File::
+
+Installing and Configuring Gnash
+
+* Requirements::
+* Downloading Gnash::
+
+Reporting Bugs
+
+* Get a Fresh Binary Package::
+* Determine if the bug was previously reported::
+* Review the bug writing guidelines::
+* Filing a bug report::
+
+GNU Free Documentation License
+
+* 0. PREAMBLE: 0_ PREAMBLE.
+* 1. APPLICABILITY AND DEFINITIONS: 1_ APPLICABILITY AND DEFINITIONS.
+* 2. VERBATIM COPYING: 2_ VERBATIM COPYING.
+* 3. COPYING IN QUANTITY: 3_ COPYING IN QUANTITY.
+* 4. MODIFICATIONS: 4_ MODIFICATIONS.
+* 5. COMBINING DOCUMENTS: 5_ COMBINING DOCUMENTS.
+* 6. COLLECTIONS OF DOCUMENTS: 6_ COLLECTIONS OF DOCUMENTS.
+* 7. AGGREGATION WITH INDEPENDENT WORKS: 7_ AGGREGATION WITH INDEPENDENT WORKS.
+* 8. TRANSLATION: 8_ TRANSLATION.
+* 9. TERMINATION: 9_ TERMINATION.
+* 10. FUTURE REVISIONS OF THIS LICENSE: 10_ FUTURE REVISIONS OF THIS LICENSE.
+* Addendum::
+
+
+File: gnash_user.info, Node: Introduction, Next: Using Gnash, Prev: Top,
Up: Top
+
+1 Introduction
+**************
+
+Gnash is a free SWF movie player. It is available as a stand-alone
+application or as a plugin for several popular web browsers. It
+supports playing media from a disk or streaming over a network
+connection. Some popular video sharing sites like YouTube are supported
+from a wide vaariety of devices from embedded ones to modern desktops.
+
+ Gnash has a better focus on security, allowing the user tight
+control of all network or disk based I/O. Gnash also supports extending
+ActionScript by creating your own. You can write wrappers for any
+development library, and import them into the player much like perl or
+python does.
+
+* Menu:
+
+* Audience::
+* What Is Supported ?::
+
+
+File: gnash_user.info, Node: Audience, Next: What Is Supported ?, Up:
Introduction
+
+1.1 Audience
+============
+
+This manual is primarily focused on users interested in how to get
+Gnash installed from a package, and basic usage as a web browser
+plugin. For more technical details, please refer to the Gnash Reference
+manual.
+
+
+File: gnash_user.info, Node: What Is Supported ?, Prev: Audience, Up:
Introduction
+
+1.2 What Is Supported ?
+=======================
+
+Gnash is known to compile for most any POSIX and ANSI C++ conforming
+system if you have all the dependent libraries installed. Systems we
+test on, and which Gnash is know to run on are Ubuntu, Fedora, Debian,
+OpenBSD, NetBSD, FreeBSD, Win32, and Darwin (OSX) primarily.
+Occasionally other platforms are built, primarily by those distribution
+maintainers. This includes BeOS, Haiku, Syllable, OS/2, Solaris,
+Slackware, and Gentoo.
+
+ Gnash is a capable of reading up to SWF v9 files and opcodes, but
+primarily supports SWF v7, with better SWF v8 and v9 support under
+heavy developement. With the 0.8.2 release, Gnash includes initial
+parser support for SWF v8 and v9. Not all ActionScript 2 classes are
+implemented yet, but all of the most heavily used ones are. Many
+ActionScript 2 classes are partially implemented; there is support for
+all of the commonly used methods of each class.
+
+ Gnash has implemented about 80% of ActionScript v. 2.0, and has
+begun implementing ActionScript v. 3.0. Gnash supports the majority of
+Flash opcodes up to SWF version 9, and a wide sampling of ActionScript
+classes for SWF version 8.
+
+ As ActionsScript 3 is a more developed version of 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 easiest way for new Gnash developers to make a contribution
+without a deep internal knpowledge of Gnash.
+
+ Gnash has included video support since early 2007, but this is an
+every 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 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 at: http://www.gnashdev.org/dev_snapshots
+(http://www.gnashdev.org/dev_snapshots/).
+
+ 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.
+
+
+File: gnash_user.info, Node: Using Gnash, Next: Installing and Configuring
Gnash, Prev: Introduction, Up: Top
+
+2 Using Gnash
+*************
+
+When used as a standalone player, you can play any Flash file from the
+command line by entering a command of the format:
+
+
+ gnash <option> <flashfile.swf>
+
+The only required argument is the name (and location)of the file to be
+played.
+
+ The available options are listed in the following section, or you
+may view them in the terminal window by executing the following at the
+command line:
+
+
+ gnash --help |less
+
+ The source code download of Gnash includes several example .SWF
+files. They are located in the `testsuite/samples/' directory of the
+Gnash source directory. If you have installed Gnash correctly, issuing
+the a command similar to the following plays a short animation of a car
+swerving and crashing:
+
+
+ gnash
+ /home/<username>/gnash/testsuite/car_smash.swf
+
+PNG
+
+
IHDR 6 ÀSh pHYs : Êduh tIMEÕ EöH
IDATxÚì}ydU}ïï,w¿µvWwÏ* à ì*EÑã.F1Ä$ïÅ|address@hidden
Am¥g¦»Ö»õýQÝ=5ÝUÕÕ Qôþ>ý©S·îrÎ=ç{¾¿åü ñYÏ;ÿíÇà yð=6mA Ðü?¹äK.CEÖ öìÙ}ü¶Í«»ÎÃ=pç 7+¥Æø} øè9ç½hzú C©É
øìnáÆF¥±ãÓ$ñ IC±¶íUã(ô=+XóÀ°Kq ^Ê dÍbµË¥R)¬" ~µ+j
+¢c
½,iËÕ8a1 vüb%I2HÈ×/%Ij+*Yd¹Å4I r
ÛÏÒص-& 1¼,<address@hidden:,<ßg\!jì°4,)2
lÎ"×-0&
+LÁcÛñV )Ór9ãER%Rj:3Ó Ra-3B-ÎiR(%8³,SH
6ÏlÛR!-42¤È,ËæBaèiZBJ´¢$£%
$`-9¡¦¤4ÖcbH))ÁJ#ÆT*A
Q¨Rª4Rª%!D+
a$&D)Ý´Va¥Âz¾ZBZk47Ui 4ÿï¾zèÇóçv»îÜõAkèw»ù¢Âé
¢Rw-Tg¡vRPÚSwÉ©aJ©R Ý¢!¥ojN
C
+5×Ôb)kj!(%J#&¦àÜ4
©æÞ¬äe[Bj¤¹F¦à©m»\H E IT`HZ¶Ã¸ X+ R¤¦åpÆ ¥&J$é2Y&
+kÃeYbÛÝnì²,ò\ T
+Äaiäû
K¬S
B1ͦͳÐóiÆ
,%s(Í,
+B
¶[Lı
DñÈ´ I{®ÅÒ"¢f!IÂïeL0õ¸Ó ÂDEøIܪVÇ¢DP$ò³¸Y®Ö¢851ತU,EQbQɵÅÓãã$5ÊÂ=o}Í `f¶Î[Ô]&jãa Àþ¥ºÒ
·Ýò¾ÿ·Ðóιàò±8
+Î:ã$4Oº½4K³[¿ßDöÏ×ßÂ,î|/0Çâötu|¢ÙN}+¤t¦ËcSÍVXrU¦,Ú_ªlh¶ÚåIËãýÅʦf«9V²ÌRÉ~¿²¹Õ¬ÝNJ«ÛÅ
A{¶Rò; Ù1ÝZÔË¥b'Äت$a£T*u"nLÓR× ÅJe!$òYÒð Õ0J<rDÚp ca\JS¦M§0
AÁ3nhÖ´½ñ(êø0D`8å4<ÏI2À:&V1×sLQ!ê±4t 7ɤAÆÈBÛñÒT+° mÇO3f
´!ydÙ~f¶E¸$ZDUȲԶ(address@hidden)2Ã0¹P+ address@hidden
+!AJ2B-)%Xj¬#ÔB»Ð±!¥$w7ÂT)I0V BD+0Öº5´BÍÍõC+=wÐóX¥»Ð3ÁnqávswÇK¥1Ò]$"Ì(Å
5¤Òd¡v 9Ww[fR"ŵ8ç¦AÐ SKpf ÀÀ55WKÀ¦`©iYKB¦äe9ã&Õ
ÉcËò2Y*v!MÇ¢L-BÓ.¦Iì:fÊR1µ
+Y¹rÀ:%¥ëºI&
Äú,鸤Ü$Bc¥ ×+ÄIfJ"W¤-Ç+GqâÙ)[¦
§0
a·«¬ájaÐ.ì(#7-¿RÁ
SUÛpÆã°Y*úA¬ ]
AQNÂÙR©Ú
Sײh¦Xªµ¨àèLû<:P¬LµÚ²Obáîn6ÆËv'3U²ß¯li5fjU¿cÄgâævóÀxµÔ4MÓßÐi «VÚ¤b³$£]¿öº :ö)'n÷<·jÀmwÞkÛ^Ggzi~ëæ;ÇÇkïÿ¿N.xÑKN:å
Ç&_ɸT
+KAixr÷^ÏóôÀ®N¤ ÇiÌãrÐ.Ç6"×ÈR]Zû
+åÙgËûI0í'gê¢;©
ûâÔìl½\0!âýVaC}v¦\rê!Ré,u'RÁ«ñ6²ÆÚÍBÁ¯w8Ñ¡¢å
=ëùÅz;3PÊ ³WntðTºiT·Ýr³ Ù¸ÅuÓ©4Ûkã ¥,iP§Ún·]v"±«íNËuÌNkQ
+íXHi)âGaDzìN,Jr(0,'8δÅ5 Ω4²4 F)Á:å¥!6¼0J bx"âØ
address@hidden f&Ð$Zq¡h%Ó$Z ®ËÀFq
ÌX
address@hidden
+YÆ ÀyªfÓ Lh!Ô$c\0®àRcƹÖÝ¢1.¤F+!¥
+¸PB*!µè~/r¡ÔBj!UÏR )
TBRHÅ¥B
+ ©º'Î5â¼{1Î¥FJI.cL>Tä1®µf-Ô æën¦iJî6Ef£i)3
F¦$SZ2Æ¡¦Ö\(¥1&FrÐ)ÊÒQ+J2T&K#L(I F Ç,ë¾èØ4H!ÈðÃ(2
¦ZñP/
+CÓ4ÃDi+ìFÑB¿Êr¨mZn'Êp¦$n¶ßRÈTØiÔ4íb;,"n²¸a8åV;pmÒIHSmµZ¾gµ"¤²&¶ÇÚ¦ïÙÍPhQ
ÚuÏsÀ*P¤ ´ë_¨·3% £ÎçëØ¢,U^ Ì8~µÞ \K
ÜÍÂN¡6Ûh]ÜN-îw
+fêõJÁªGTÄÓvqóÌÌÁjÙé Íf
oC}v¥\iK,ÈjÖ§Ëåòl[QJÀÐÑé'=3K[·d¬Ûs@(-¥Vfëu)address@hidden
T iÄÁR]ÛÓ
òÄL=(Ø*â^ì÷³õVÉÅíÔæѧ85;Û(ÌFDU|Àò7Ôë³;
Èf©;ÑlÌ^=PX´5ÖiÍ
FGP IRÛ³¾_l´3g
+IXw½R³[D¤ÒÍ¢åíÈ1uÄ-4L§Üê´iØN»ã9´`5SítÚcubмR´ ÇìD
+d¤ Û²X`Jä¤QÇ´ì0b8?V"I§a(Ñ)'<áFQbR0$X©G±Iqâ7c$SZ¤YiSBLiÉYb$© -2X"b$ B¥iÆ4ó.Zq
$x¦e¼Vgq Ä8Φq
À¹RH
ù<ZI)¥B\s©RRJ%¥BJ¥
ÐBuÁKJµªæqM*!ô¡S¤BIBH¥K-e÷ús·RJÕ-¢îÝ
Ds
s¡çLÉ ¹ Á3 ±¹ÊÎ×=Ãe ¤È42³4#§Lk)0³4#¤Ljɤ6²4Å&©oê3NÉáY©$
ÂYÜE+!å¸ûf£(6)2,D
eÐ(address@hidden
+-Ë 2ÑØ£À:¼_YD gÚNã¶ey 1Ì%-Ó.vØ6
æOSnwææ`6©]m·ÛÏlEH³&±«V£àÙÍP#Ñ£´¾ï5Iu¤h9ìÔ}¿Ðh3§ âάëĦ<U~̺~¥Ñ
=KGÜaáAǯÕí¢KÚ©)¢vaª^¯W
+f=¢*9`ùfgÝ6 ¡îÆìj¥8ÓT6=ÙjLW+åÙ3!P´ mÛq%6
º{¸:z½uý×nþôg¯ÿþ]?VJõ ¥>ôçúo_üf¥\ܲibÓÆ×$µÆa,LÌ8xi0S*UÖã%ªÂý¥Jíàl§ìéû29P(OÎÖ[Õi'Îx¥©úl}¬d7BùA»8U©U½ÙP9Kü©Vcv¬â϶¥
°kæL¹\¬·¹Mb+i{¶T*5Úc0¦<õåF;ö,JO¦u·PiµÂ"f)Öp¼J» <¤xÓò*v§è#Ñ4ݱN«U*ØíH]vÁs:¡¢(QF1
Úçv"nb&'¢ãxAÈ-*rdÚ± /2ËЩ0-Ë¢Ä6QÊ©¡1W$q #jyQ;¶eUD
address@hidden,address@hidden SBÍ,åBÆ ¨ S3K¡q abÊQ3®æ11ãi0QJ`
ThΪÕ-J4gfc¥Õ\¤A£®Mj¾ØW º&°EWÐ
+c$¤D °Öc,D×¢µæÁF fSÁÁÀ8Í0¡YÆ)A£neÓ43(I bb±45)M2
kbÉ$5L¤
!±%ÓÄ0Í$t¾©MÃLNbÂP"6,;NI!TØ°8N-%
¨åÆQlÛ4Î ÉX~®c":Õ¦ GëXa,)dúiÔq '¸¹
®:ëuÂÌ¢+G¤mÇõ;aj*¶bmÛ-vȳQÄLÍ[[î´ß¥ABhXnµÝjv3DD5±3Öi5KE§hmWv³Tò aáXârÚ®KÅF;shÆuuê
R¹Ñ}K¦Òçɬ_¬4aÑ
¹*ñJµz£U)Ðvb qõz}¼Ü ÂâÆúìÁ1ÿ` L5CýÍÙµ±âÁ°Q[;address@hidden>I¨ÞhÝsïOºHtÎÙ'~/`ÕÆË[7M>úøî^üJ
îéa¸÷Ó¶£¶\yŶl¸üÒópìi--*z2ëT*v]®HE$«cí
®4d³åêd§Ó/D:Ï*SN«V±CnP9ë7íæä¸×I°©Nq*îÔkc~'¦WË¢ÆXµ&Ò¥1±ª<iV*å0æ¾É-ª¬Y*W¢8+ÚJaO³V¡Tã¤äam¿PMâ¸ì&M"Ûn¡Æa¥`¦RÕqü±4îTKv°
¡åUxNÊÁ" µ2 7eÊ¡ ¾âï{®):
"Ïó箥[HÅ®ëqÎ<+0°Jl×<ó "H-Ç<ó]C(L!5m_ÔsL¡¹aºJd®cJ©M,iÊ ÇJYTj"address@hidden
L±f¦e)--"qÃ4µ¦ ¸aZ ËÄEa¢HRJ(bbMÁh¡`õ\ !cM Ƹ{a
` address@hidden&c¬ç¾ÄzþúhþvceP6àîýEIîÂ#ahi0ÆóµM¢QÄ ÓÒ;U
Ì©aiÅlÛP " address@hidden&¨ÛÔ¶)´ uf;Â1Å:µ GæÚX%:± WòÌs
©Ñ©éø%Ïä(5l_²Ø÷l&ÀÄZ¾äQÁw2¡lʱáén¿bÂ5%¢¡ï²yÖȺ~1MÓ¶°
\¿%QɧLTµ ,IÂjÉ6¡m{ãiÜ®Ý8C ·ÊâVµìGrHL2OZr1
g2dDÚ*WÊa ©¯²F©\¢¤ìñF±R `¬HaÑ('Nk¢bYwo Ûõ©ß±
u»¸1ìÌLÕH»¤møSIpp¢Vm²`Ä®±h¶\*Å©°(7 sjDQôã<ü£û þñO îòbt°P³Ù¦\ýúËw>ú¤V
+õP,ô¦·¼ëõo~ÅbÛÑÛº<m¤!)åÍ·Ý511ùÏ×ßê)®ëvÂÔ5À¥,)UÆZ¤`Ë
+"®JãNXòP" ÕÝbÓî FÄ,`u»8Ñi·ªE§,?v×êuÆã°Q*úX(Æf%
b1¸M"·üB1cJ<¶]¿F©gÓ¶Ê:¶W¢ØwH*MÍ;[£ØwiÂi׬ġïZ1CX
½P¢lX¹®Óµ²õx9dÒÄBa[²Ø²
(±i¹YÆ»Vv-bÃr³Y&æL©é2Ù&aϳ̶h6gew8Ë,²9Ó¯-xfúÝ4¹i¨¬ke'æ\ÔRR¤Æ
address@hidden<gt_deD´Rc5ç¬ìÝ"address@hidden< 5`zÎ_
jávî®Â4`Ða¢Â´Æ »îQI0R½u§HªnÑSJ¬"¦Ì KÀÐ[ì6µ!ë65EJ!CÌ0-Æ
A´CÔ0mƸIÐÝ7ë0Æ,ðCo6ul#åë ËÇ6S2D]Åm¥LSĺ"ìù~¥±#Xd;n2j,É"Ûñ$³MàÚÒ<°b$®M2AASãÐwÍ$Ã-'aPôí0CD
Ô.'Q§XpD#«EíBÁ biLÓÛ
B!c
+|6=¿ D©g)®]5]¿Ú £¢aiÖtýñNÐ)ûfÈ(â
Ûì´ce§"êVaªÓªWüf¦nSw"lÏV+ÅV(m"k,ër9
EP_EOþÚë.è´Ï=ëT)address@hidden
óV«®· þøjããùÂ-®Ø¤Ì"Ba/
R¥$¥òXÒ,« ò )G¦M¯0Ö
¢GajÖtüZ´K¾1xÛòÇÃN«\t
+
§bÁ E!!f)Û
&ÂD
,i{^!JM¥Ä®H;®WÔ1¥X`»Å(N\ 3ej Zn1cϦ
ZF¦]LâÈsÍcaÒ8ô\+auBÌK#DZS¦pL Åí¤LR, ÛÇådL¤ë9J-ËÎ0(HMµH
Ëɳ(hRc¡O#P6ce\R ¶`Ì4)s#Jf
+#ØÔRa¤ J2B
)ÆZéúà¥#X+A!¤8î@ %!X*z® V
+!h×
§4 wðÒ`.v#¤æâ
Ûuô¡" 4 ÑáøÕu("@zñ)z"æ!5WÄZ˹èîѹg/%ÆDI
1RR
+J°Téù"ÅR"¤9"¦Ü DH@ 6¤à¥Bj$`C F©Á¥"address@hidden WTF
±Ì6)©.cmk¤1\%mf\à:"KlÛîíW¶å¤D+dI Y¶¦eÔ¦äåøi:fÊÐ<4bÄm¤L»ÄïÙqDÅÔ.&qPð(ÓT§Ø,dIÇ÷¼(ÊágIà{^p
+
=v\¿Ec*ÈÚ®W£Øs0b-ǯaXtiÂ
Í[? tZ墦åOF¹ä1Ý1ñ0hTJ
v$Ma«õR¹Ü¸E8¢>gN÷¿íõ/ît:µ²iâ: }bo¡X£pã1BÈaGütçµüä_¡_ûõß¹æí¿¥µÞ7½ÑäH¬À§þùdod\QÄõXÒö
(fÚ(dQÓ/¢Ù¦ÈcqÓ+£(qm$´ÍÓëWÂ(*84S¦H?
AÑ·Nk[n5o'
!N9ϵÓy4IÀs» Q¥ãzi& "address@hidden'SHÔ¶
Tñ°ëvmI¬ElX~&¶m2JçûÅÆ!êXŸÂH"l
+Ÿ¤XkdH¦Í¹0(( =E¤4"5LsfX*¢eF [pfD*¤#t¾(ÀØR#P©ÚããçR©y ¿
Êy2¢À.EÅyn¥0FZ£CÌ!
æCP÷hUuÁfQj-±h-¥»ÁX ÁüÝ Ò ÝH1¬ ®UKIL°RzPe
¡óáèð"ÌÑL)!JA·©¥ä´ ^ݦ],S¨ÌcµZ#*EF
KpA)hM¥è¾h>÷f»1z,3M*ÒrË,ò9,sK-Ëà z¾_$Ø<mÛÎ4ÒÈâ,²m7eÜ¢
Á,²l/Ímb¡¨ä¡å¤ÛâéÓ8v]ñ®&QÏ ò³$t]'address@hidden,±0]
Sd CØL8UYËöÇ¢
],ºqìN%ÛÅ¥èÅ,,Ûî4|÷Õ/ÙcÙâ8¬A) ì?0#¥Xttã)address@hidden)rÁ\rÉe¬û¨]y±|×åÜűM;ïtñ'¦r뺲K³6=bcñü36nüþí ôë+
ÀyÈ%\Ö&·ÿÍêÎ ÿëÁ9ï½÷¶"ÎÛ0\ryºHX¹äKX¹äK.9`åK.9`åK.¹äK.¹äV.¹äV.¹äKX¹äK.9`åK.9`åK.¹äK.¹äV.¹äV.¹äKX¹äK.9`åK.9`åK.¹äK.¹ä2м
FøÜ^CÙ@(¡ÃÁÄP2 ¨Ú+Ø+\rÀúE¥¡×¾if ÔÜ! Ì$p ¡ÊL
+ address@hidden@iD0R¦Â ³)<ÖDH¡©
;îOÀp<BHÐé Åsw
b9V¡¤¥´Åhm9MlZ®§{åI¥ë)h2Î
+¶Q¶Àæ!æcé¨ÈÔ¬b
¡æ ªAP4¡fEò×KX?Orx"Zpÿ,úò
åPdxEÛ¶)¥éÁ$bÓ°s0©¹ª´¥µ'% B)¥ À Â5M«Þ ]BlÎßÜ*Óp4BÈÖz !e»_ö
address@hidden £QI¢ò<¯[´gf'address@hidden:H»fs®p ÀRíW¢CÙ¦Ï_GJ
hi)ÕÞùHøø dl*ùH«(¡ @êìÛ¾(Qª¸0 B.1G
address@hidden,0,%J&L:P2¡fCÁÌR.9`YbÓ142x°:address@hidden)¢Á
nc!Dñêí~Ç÷Úö
¯z&>ü5 Ùý¿öÐNMH/}ÍaD
u È4hгÏ9=:b+ ( ¡µPªÙjeiÚh4 h·Z õ®Ý Æ P z !àDíÕRmRó ÏÄÛ
ÂðÍÇèc6T-¨ÙPÌá, °zeo?EÖäS0Ká) S®h
cÝÝöqè|Ùå8J ðÓ@;²êýÞ d
p». 0õÃ{á÷.w {HSç6zás+ÖOêIP(Üõ}ÉvM)ÕF*$J Ũvm³f«s'D mrÁ
le+ ¹üBÖ!|áIszê쪷á)ë
Ss:°2u«Wúú7ùË^Á >ZP}Quþãñâ>%1&´Ô
nÄÐÖj÷âq-ïCJ-A& gÚ)RÐ6GýÊ&½¹¤Um% ¹+;§;`íáÏîEb¿wéy]ø®wáñq à=?H{>ϼåM
õZnWúÖƾéCãPÈf«ÇQÐ ×õ}oçÎGâ8"=¼Ì²R±4¬£Þ1 IDAT7È VR9>|§Ô²¨
,@E{¡Psþ3гjÎð^ÃØ4·ã»©¨DãdZÿT
+ `"GÔ06
+ÐÏØ[H BVÑ! ݯq«µÔÀößPÊ`êQ²OÉûÜäz¡Hkâè~öÛùÍëi%4áïvw?ÂG{§
bÜú=ù?2ª×Tª®Õí
ZK ¥5 D' ¿ïVK Bf³I)å·Ûmq8;3Mc|è˨¥(471¥ Ck! BZk<1_JiÁ2º#¼ .@)
¸ûQH¹P;-A(address@hidden zB*¢¡¢´uÅ×UÐ6º
+â8Æ& d aì#TA#pDkë
"° F`®²UOH
ÎêpVýÔ`Ö1¥;Æ7ËçLÀ3
+ ¤¡rÿfX?¢5|g¿ñ¡Ç/Q
ß×±ùáDpÑ/J5´ªkµO©H«Çì%x7%(I(eR(ËÒ/ÐõÎØt1ZkBH¥R!ض=66
B!dçy
BÁ0 `Û¶mãããõz]÷P¹v» Ç1 `Õ<K Û¶+J÷{J)c¬ÑhdYv"¥ìþ
ZvïRJÍÎÎ*¥´ÖÝ1Ƥ۶m«ÏÎ
+)
Zë(c¶f ÀÁ8NÓtg!<Ïca ! AܹÆÕRRBB µâ\K©
ª¨õT µ¢|©\¥1FJkhj[è6
²
Oa²¼¸¹@&s.8\è4Çvïhx¤c06¤mWS.|Pçõs
RÃgö?ûcë#ÓÖÃZ T Áa¬AÏÜíZRaRk ¤TQ«Õ6ÕjµZmÛ¶m¥R©
¦¦¦°!ÔeFc aBJJ
Ba»_Rªûå¢gF£idý¦5t¿_ø°ôVJ`{rѺ(©¤TZw¿ 0 ;ç|vvöP KY¯×¥
u'²,ët:iî¢i$ÉÂÓv1 c¼ððc¬5Ñ 8×oârR*W©ÒRmD¨ð8Æ'1Y5 êú
NBÆI`¨TwÊ0ýüáãìÃ*© ¾ãx8²í °~vòÃøÄô¦öñ§ ½R$Ñøã¹cµÔqÎ9R
+
ZV.K¥R¥\>ò¨£&'&6nÚÔ
³"e¸ :ÔÕ¼² G½È"ôbY[øÙÒk"´p Ô
Ôy Yô<K¥P(èáæ<address@hidden;KëÙz½K
»¼ï;îã1Ön·ëõz«ÝN &&&Úí6F
1BqN4JB e¥Ç8BêÒ]å´ðÆǺq(Yë0ÙÉ&p.%η¦ÑÇ[gm'¿µ³ÕÏxXÿýhÕ4¿qô[ýðáÿ?ö¼ÎdX,nÚ´©\.W*
6LMMMLLÔjµîÌߥÒÕwú£ÀR"address@hidden/Ð|C
¾®Û{Ú¶mÛÈ]WºHwàÀ
ÚívgfÍfÍÌÌ4$I$éro½N06-«Ëg%ç]h+¤Ùv.Íø© Eè1Òåzó%B ýßOjØtsðþ· ç<¬ÿ>¹¯Iÿ¼È{âà~øã
ÞÏÓ7Ô¦ÆÇÿôà v=ÍË
+®8âP_¶[?µ²;v¥[Ù¥¬ìð&ë%w½0wÄG,:u_ë~BÌÎÌÌÖëIt ÍfóñÇ ?xðàC»wߺ?Ò"Hnz;ãÏòLÇ0vMa¼ É íy ¼ëØóvÞwëOÌÜ$Ö Z*\áí
Þrç-ÛýG~Vñ|ÿ ø_(¤
õ¥$k8-¢WkAAüîçVæëPi¸V» ÷`(¥·lÙ´yó
åtßÞ½?ñÄ®]»öìÙóàÁ_ݹ3fƱ
+Z Pr\È
Bnàâ
JÊqß÷äþ/ ¹ïÜÿ÷7}ðøÉçõÊÍûÉw~×ÞyË6B¿#Ø=ì8ïyÏ{jãã0ÀP:ìPß+^
åÆçacÍdpeÙð´y :T¾Zí £k
[PN6oÙ²yËsÎ9gÊZÍæÃ;w>þøã»wïö§§÷îÝûÆ wÝÿ´mñÞ={nÓOsçKß¼ù³Ï?ë]ü×{ؽÙËÇ{XOÜ´~có7oÙú© G¥øÕwõÕW?ëYÏZBhé
74,V£éh°°/
CL騧¹jvË`
+BýwD
º÷ú«V¥ûÕ¨RyægyæBÝgff ~øáÔëu ø¯
øëÝÓï¶ýGpÏ ¿zí÷|hìûÇò!ÖzËÁ¾3ùçó+{ßó?.ÇF]«wRÊ\tÑyç7 ,VdÒ^"³A
aUy©Eê>zèϹ¤FÝæ:
u´Ã4½¶õ Ë´g÷æoŸ I¬ÕjµZ[<ã3Þÿþ÷ÿÃXéÌvraþÚwn>ñU¯øóo>ñç϶s{ÖÓY~îi þbß'wÙ= üÐÛ jýûÀ÷UO:é¤×¾öµùsÏ?%Ê×ÈÕ½¡
Ë_U{ª
ë,XziËj´¬¾¼¯!f¬~OE>êùÁ2³B'|ò»ßýîÔ4ÏÄT ýé7ÿ=VR: õ9`D>´këWÿÑÿá ¯Ý7
Ç«µZí o{7à{Q1Ȳì à¥guÐF·ê}¶®ûlzO_аAØÈØçIôÏnì"¤>[ Ãß
~rþùç{î¹3cßÉL®ùÉÃví~âWýÅCÌ1+¬µK&á/ÜðwþùýßüÖï¾·ÐGDzÃIÇq~ó7³R®un b§ y
H¶2CóD nK:ä4èëÜ\äd VÖ·:4µ1¬!è¶*à[^£ï½r/© ±gc|ÕUW=Tÿû,~¦§~çÇ+ì9éÍÛeç<+¬5Òð¹½¥¯ú_ÿà® ¾øÕíÄø[ýÓäuì·½ím qk 'ýÇÒÐÊQËj-ú¨5ô¢Ï=náoÀÅêSKHJ¯zÕ衾¦·¡ñ#«¾ACß+÷2Ðîî8ÎoÿöoýW»Fôå¯VjSl½üë{ò59`V4À7÷wdâþ§Ö'yrÝxÆ\ð¼ç>·¿_
3øËA±ZCæ|ýs?;/û=0·"v
° ´jÅ;{ÎáÑ`à ZÚC+û[wìØƨ¥ÕµõÎcÿþùÒ3Oú7rÞOùðÏkUhuÓ4¹cëkxæ1¿úW
+}`^-¾üñÇïرce³úJfûÕx©
ý4T-VgÆѺ6Ù\ê~ý×ÒûPË ^øÂmÛ¶í «¼Ofc_»ûÀýß¾ñç¾ðo ÙÈrÈk¥hµÞxä[N{áK ûã?}ÏLsV«Ø,øG yä;ßùNÃ0ÖâÌBCë _®Z£F?¢.ùsw£<F.K0{±fu/nÃtÁåºÒiÆ´¬ßýÝßT«÷×Æ>ÅÒ0yõ}÷?xÿÅç½ú/address@hidden
zãW_¾ãMw|èsÏLë?ÙôxõÈ#|ï{ß[TÖz^B´ÄzrHY6J ï
F¿ä¦ýYÀQi© ¶¿ï¸¯sÙ*èi¾ìh#»Ö Ö+´rÌ-Ëïz×»:ù7Â]ä¬ncq 餹>¬äÀøæ3®~Í[Þùåëþîí>i"ôO"»arÜ4Ík®¹Æ²¬5vñÅGÚkÂ^[ûºÐUÞ¥è°`t¹XV`SIóèéëÎ"ây!¼cûöíW\qEb[ 6Ñ>%_
¸þ«öÔ3o¼èîÙÜ ÖrIø,Î˯ú{î¼óä/í(B â/}ÆÞð-[¶:V³xð?XóÉõó¿óQ1Ä^pï×æh°©~ÅÐèD¸·>_|ñÅG qÄîñ±?R
ÞÕ
+wßðÍ'=ÿSá³w9ä5Ôtõ·N~Õ»Æà þÈ+dZÿ1])zê©ç>2ö°T3ZPÍú2|B~jeNY [AG[
Zu¸¤õÈa+*]¸ôñæCÛºÒ
è+Ë÷Unl &oyø±Goº¹vÆŹgco«Ö ¹qÚм÷ØcýêÇþúÚF|A°ÛÇ+årùꫯÆ% F
Á^;Ê,Ò,address@hidden<Ô²³>Ð9 5?áS´õ!)X×zë5× øc1«ÔY¼í Ïü×Oà´W}òɲÈ
ð9`-fߨ^ö¢_ò;î8ãß Gx§â[eíر£\.¯³¨ Bë6P6àþñ 3?
[Ø|ÈÐ>ÜÑÙsÍ¥-Ó«¡ÁJÓHeÄúÿ6¥xä;.ð¾N<ñsÎy¤èXe
ôi ÷ýÀæK¿¹ßÊíï9`-î] ß5~Ù~½Õj=þ'v9µ I]rÊ)Ï] V½¢Q1<ÉÁºääAÿ 4xVvëeY'address@hidden
}´Ú_å ù
+Wýê¯K¥ï¿Å¸2³·~wÛ§~Å:ïÞFÌ!¬ ùîl]ø®ñññ/}⺷·# øH
¼ùMoêD|i}*2¢¬Úð´rÒ1ÌÁ7äôeÀÏ£ÕbÕ»ÒhHþÕµ¡¶O¦¼RÅüK] k`ÀZ¤¹webrò¥/}ib×Y¸£Õ$Æç=ôèîÇ ;æì ?Ó8ªÍrXÈ fSø¢wÑ^rù]×_Î
7nÂä?xúoã
ÑÕW_=6>>ÄJÔ¬Z¹[;¥ê56÷5$Í#Ú2:×(*í(y p]´ãáLvpâ®oçaíÙºöói\pÁG yäcòç$h
·| èI|mÚÉà °+øÄÌW¼õw¦§§÷~â/z·æÔuÏ>ûìç?ÿùË°ªî¼q´*3v_µe
i8òCÏàQ:0jxάe address@hidden< «£H}{Q
+ÓÞ·0Ùûa¢ëº;vì}Ê· ¢Ð{î¼óqäô½Q ¿ôõ¯»ÝWüçûßüþFqÐ ig¢666vÕUW
ÙQj¡S¢¾0±Àq5©¬"âq-$hÙ!4 ðªÃAäìd\qÕÊë;Òreת: »}ûÙg ÿI¦õ Ç÷MO|Þç÷óY¿Ôõ´ëÔ·~æYßúÄuoûéÎ"BÿÊÒÛ§&B¿uíµ®ë.ßÅ;2õ/®(3Ì(£§HW]EõÑôµQUÑõRÃ%tîg{t¢ ÑÌw¸PøüòË]×½}¼òEÉ0ÀëRÞ¼ñÆb¹²sâ¶óð÷_VÀIáKö
¿òuwÿûϼþ?ÁtêY
+ào|ã3ñåÇâ ÄE¼iÙ}Ö¢,%J«ÈÖð3JF<ÒéCZi©× ©ºgZ=`u¬hÂè-[.ºè"mY sÍ¥¨
|åc» ¾ëîgü¼OÕò ~ù KiøÄÉ®ù I<öá¼\ ý^©±êi§vÞyçõ·¤ t¨pX8ûRwÏ÷¥Ê ®H®/Y/CRßoM
1$á©© êq\ Á«V¼[ÏÈï!tÑEmݺµ3Vý¿ZDZ?Ó£¿wgèÄ¿°Ï×¹bøËX·
K~³61ù ûw6Ðu<ýÁÔmÛo{ë[çLW£Xe
¬(¤hn2,&`¥X6Ø6µÔ¤Õ;ºø¬¾®¡Âôêsí
q¸¡j)Ãê
XýÎÞ#X-=×}ík_K(ýQúÉÀk¢lß-ßÝ´õÛüç?+¿TÕÌàëö¹gÿ¢û~øÃn¸qá;ûx¹
´~ík_[îÍ ³CîZÍÌ «Z ýT¯:^¾}5
+éGЬ¸m/Q\ò!0d×Å!g {ì±\|qÓ4þMw)¹ òà¾G ÛvÆyÝ åk
I KiøÌôøùo¸6¢þèÃIاä R åÒ 'ð¼`5êCßî>@s]% ¦7 âpCWí62Z8[S
+ªÅÃì\x^6AÕ³¥1zøØ*6v>4ß^ré¥'p®JùKKÈoÒZGÇ]òíýV¿õÅ=¶uñïLmØøÕ?þðÛf?icÃTµZ}÷»ßMY¥e¤oVßøÑ÷gz)ÑXÈÀ7ädìe[vÏ
¬JU!]]ÄÖèõìß
uot=}D'à¢íê¦ Çq®¸â
+Ó²n(û÷Hî"ôÆý³ÜqÇÏ<æ+âÙÓq¿èu×
~ðYW~Îßøëï¸óþgwNMDZ]{íµÅbqejÎrh=ì/}u¢åþ®hg%ÑK÷F]
¥sôª8tûQä©Ë®Zõ.Ük1Áàõ¡K÷Á>¼Ñ>úèóÏ??²¬ë°´>ÐÓpÏ̾}θð3{«yXÖ/2`= ÀWJ/yñ«Þô½ï}ïô¯|ý$DZ}Ô¦À ;¶nÝ:address@hidden
+áÁºµÒý´Î¼ïð³F#´ÖW¢ó®ýÕht
½§vz^vÙe߯ü£Ì4À¡_¿¡X,=8yþ=õ|Qô/(`e>Ý9öÅo~Bèà'?}®Bà/D:address@hidden
ß:ÀÇ"sÛPcè°Ó KõT&Zp¸Þ7öt¤R©tùå#J?Spï¼ð[ö |ø{ß?îÔ3?Y?*Èò~!ëkûÌ®üí±ññoýûç_ñä^ à}¥ZJ²ìíïxmÛKÕHv5V¯vÇc4(²±÷R£[Õ ×µyæ¸F©ºpüQÈÚ «¾»ÖW÷ 8묳;\ú
Õ
NÁôÄïßÕn4§½äßöòí*~Ñ k ?ÚzŶO;pàñ¥/H¦õÅO<ñSNDÈU
+ôi|G©atfªµ0êSK9ßûõà%«V8× £¨C 8U
Jð3µ,Eì× Çyýë_ïûjcà©ØÁÔþnÚ¸é»þ9yXÖ/`}±±áì½Þ4Íï|ê ~u¶E >&³ÖÆÓ,{Ýë^G)]:ZÐ:
r± aõp:=Âèy¨öؽ8põµLõÈÊÆç*°cEÛâ.ËBÛpä²Êe
oÙ²åÊ+¯L(ýjÑÛä8Æ; ~ì»î:þ9/¸îàI õ X·ìô¬7oÞ²õÞ»ï~Ö·oÞð½¦èj.½äEkѪ³}NÝVîDk ö ¾Î¥!òÃSD(g^¯Ùhåh8×XÖ·Äx·«ßW¢MVlÑýý
+cÜWðð£guÖI'Ô*®Ó> ÓgßzG»Ý6OyÉçwçi! +äp³Þ¹\eÙöÑK´~ Õhl¬T*]ñW,address@hidden/F}µR¸G
+ð® ¿ó7oý9u:Ïõ X߶¶½øõãÜòùÏ¿|ïþBàéµ$I®¹æ×uBg¹[ªS
¿ÎZXÌè{!¡àèükEzÖ"é(crHº«µXyFi¢!)ÉFì5Fê Úã5Ö °}ûö³Ï>yÞ_
k=èù?º¿~ðàQg_ô¡'¶äáÓ°fSøÑÄ
'rÚ®]»è¿|þL¤ÄgÊÆø /|ö³½Ô¨kLC²²-¹ÎÂßú0¬¹Ù0wèK3ou9¢÷p)>®-nve¨1Ü
address@hidden/address@hidden; ?ªU×u_ùÊWÎ)}7ÚZvò_ãæ«È¼òìýQi(è¾`7Ô?
+ïÝK-±|¤svº¿ú½V}mÄùcí»qsþ-[Î8ã address@hidden
>ãG õÌïûÛç~ÿîI?ÃÒ'ÆÒ4}ë[ßZê®Âé7buèuxÍöÃ-?EùÀVG¥7þ¶_ö.=Êê¢,Üé ph8Y p÷ÃBü×þäÎ ºñÒlY/ùËàñê××*¼ûƤαç|address@hidden/ ¶6óÎ;ïäOÖKªï øTãÂ[:ÉâÁ\£5¼YVZÁA{L¬º} êï²EBë£2ÏÁ2)ÀNK˾§¦¦.¹ä0Í1q
µÐe<¾ç'=î¸o=ç;address@hidden,Ä[F>Î5=\ËXo¸aV½r¸Kq÷Õ°æíGzÄ¥H«N³.61\%_èÿ/.JW?-R
ð2lDß¹YJi {î-Óy éÏ°nyüù ô#?ÄßÜ
£¯:À}.>ù´3¾ÿ¥ëß²óB_âéjcq _yåÞü|«çW:ÒFWyz¬ë ¿Þïî
address@hidden:ô\i¶A%ì½¼lþu½¬Ãwu¯~8â bý®àùþ«_ýjBé§={¯B/ß?óØn;þĪoÍIÖÏ°ÎMýßØ?õ'68ß«}ìß ¸Áúؽø§ÍeNþÙÊ/}}§ÓI¾~ÃìâCE þQG uÎ9ç:FÜó)Rûîí¾*¥×Ãòµ(\S î]4(°³?.M¿w>9ÊúïüÜÃV£»6[ÞÊTûzÈsó7fÕÊ_ÊL¼QyãMBç¤ß¸/'Y? ÀB ÀEèÔú=«ø¾¨öG§¾óâu÷#6`¹gö=û
ÛÙ~×õ_~å¾±Ö¿$LMrÎßøÆ7.,r i¶ ¼¾^kMú2áQZ}³nõnA¼jånÝQxuÆ
¾qáC6²e<¶¨_lÚa¨úTWvÄ+B !BÈ+^ñ
+¥ÔW+ÅH ÞÜ ¼ïGÛ·oÿ·ð<UÖÏÞ
¿O~`ü ìÓb_eÇ]øò »xÂýâ!ôODòÈÆIJéùçÌ1ÇÀÎr=Ä©>V¬-.]2DsÁÁ¨ p-»Ï¯»Ê¹R-ixÛÁñá1¨«2áûÍ(ÊïÐ+\Z´¢Ô N;í´-[¶Xåò È´>¥ïÞe±ýö¡ G~Ƶ [§«ý·gÉZ/NûG½òw$¹ëøêVp Ïn¯ÚC)}ÙË^¶ü6ÎÃà(а6Å°ø¦ Í«Ï÷ÃQ<
kw-b}ÛvÄ Û¡øåÊÌöÔõê<¡«n´%÷ºêª«RÿU«~M0 xgüçí· {ì±ÿ\ߧù¹ , ¯
ÏÝwX
Ý!ì:æU§~úMÿÉ« zÌGøsÉbAqÕUWU«ÕÇc]b Fßnhxçºk1¥Ä¾ÄdOëer<¦Ó-õxÛ´wá˪1¥g9ºî65bòøµ¾©¥p9ÿáè£Þ¾}»ãû ¶I]«£}Á÷îj6Þé/»~CÉÏ`À&Yg_ÉúQà uæ¯<öØcn¹}3&w vw¹$ÉË.»ìäO^ìÞZ¹N´¼k|E${gþõ
R yÅÑÝg p+}þ^sþhuÆ2= âÅgxìÛ`ÍQ¯ãðû+®¸1LNü=OÀÞ{Ûíÿ½7³eV2æ
IDATë¨îEתÚÓºOênÍóìI-c#`§`cÁ\àq $ address@hidden ` À
&¶Á,K $K²ÔR«Õêy8óÞ»ªÖû£ÎÙ½ÏéÓÔ2-÷þý!³»Î jWýjMµÖ5k¾VØ1\óÉ <9 Ng`Ü
¬àéspd Æ\(
+(ID¶D¨ÙÑ\2Ç2¬+¡
ëÃÁæïÞ¼ù{öç ÏñEÉdmßôö·Oî¹äGSÕ¹¤î4§!8C`ÑÂbæóÏ iIDacÿTûó^ºçûÍÌ00=Ìó4Ð<ÝtþÐéVJûM6íÞ½ûСC_oHÜ÷·sãþ/ »þºkn»ÿo ?ñmËÎpM_A_
âkCÈÆ,3c¶H#CÊ\ÏxÂ#x² àÈ<S²Õ½eº¢lVä/a5å·øã¡Äêûî?×ÛÛñì/address@hidden|ßðÁqæ1HuÝÛ3ÉWÕ'
Û2°Þ¶ÕY_°ÿq^¢Yj/À
9X7ßÖ +_M½ÕK)2÷Jb3n-ÀROU¢ëq"Í«ä9îþûïñÅö¶¿;qê/Yâ¦óÑ?û¶îß¼:ç?4ëúãð¬ÖØ6ißÎ
)OØ ¡ØOÿ~Öýãõ¥JïÜ*vwP,Ú4G , ºp°ñÆ«®¹öÀ7¿ug¾¨ þ46´¶¶ÞpÃ
sµ8÷ª7ý¨nù7UH©Ò¡¦ÙÏ%ξnæf]13
¹çÛºMÎ Ns3$ÃY5|.kbu° M°;¼6uttÜvÛmJ©'»}_¸1Äk ß°ë¦|£~n¿ãøo?I|b¤õüÆ0í9Üa
ñNËùuÕðßÆÛJ?oþ³çù\DVs&,address@hidden<Ýô}ÿ;îH¥Ró[óZåæeºèÑ\gpÏ!/Í5¦ª6F´nì(QÝxѹøìgk¶
RkbçÊ;몸êY9qÆôú¿»îº«¥¥%Jý³ Я?òåmhh|µñú㵿 ÈãOÅ Ô1ÄÛ
çwÆZ ~:öÒ0D¦9VrWÂ`^i½eÓ¶ ¾ñÍ;rEð
ÐÐÐÞÞþ¶·½ÎW|ÐÅL9
+e³n«'°`ÝÎ +V\°¤3kÉh.Bg½ùH²3,Í+"t¸°¹ùð`*zðÁs¹Üétúid¿3=vìØú=·ýõéæðí(;Â?ì74âE¢=ãwMßÿYüÄøRç¬9õã(IÁcCWßý3'Ovüø§+äBÛn»mR¼Ùj3ëîùùF^pAË׬ß̱yÝðÅïvù®Â5H2!§;ÍLó¼Ê¬îKª«5à BðBf*ZïOW]uÕÖ[Y2ñ%òÀÛ
+ûâK¶ãL¬{çÑ5áwÎic `6wO¦¿ÿóø¹|DX³á,C#øyíæ-[=öø»K¾Gô7$(nmm½ñÆ/\ª6À¬âÌ
Nu(
+EE×E À %]ÎÝÊôä
L=·SáôZzä#Bt)ìýÓM-¼6½æ½ï}o±XüiCbH) xGwÏØØØÆm;è´¥ ÅmEg¡ÕA¼ÝOü´)"¬éàõHñLÑûîôÆëné=uªñ± aü9é H7 À;ßùÎ:Ö«¹O¹ÊÇe)DßI¼4Qk¢.Òz1`Zºj¯.6
Ii¡ô ¢v_ê
Ï9rnÝÇzYeÿ)ëè¶mÛÚÚÚb--_ð p/3 8`ÙÎËÎvQÙ~{twæN×mÊúÎËFa × 6f _s Ï
±ýÞõ®wýðÿýÿþc¾Aü+ ±!¿-p. 7O-«E
"ò<¯Ô¼]ärRJ ð<¤R àû¾2f£cc 7q® TÒàFïk¯I¥Ý¥ÖMå2ÍTkk!6¥X#ê]¯Ü4R--û9磯Z7é
+B'â¼$¯ `ÆeYåÙ®q;6YÌmÛä ¥T>WRZ¶
1Ó²æ§Ü]|Ë° S§ë
bL÷N§ ûeÄÄá £ä¦pÖ·ÞúÈ#|#é|ÊSË[ýÒËôw4l»éG^yp½³\Á8 áN811~UkDXõ`#~ÄI<Jü{î8Õ½î©`ü_
{¢£|ÿÝï~wsKËBYI\×%"ß÷¥ú+y¾¯%7?6¦eüȨ> ø® C½BJcãSÊÈdìk\gs1Æ<á@<WàBc´£©
address@hidden
ê`ªVd*> ñêdéEËê; `/+¹¬X¬zØ/y¶m\¯Ë§È_¥TëÄôp±J:
¤h ëÖ HJåû ØÉd,&Ë¥ÖµÐÐÞn$""+k¡¸B1µóÌ´,ÆcÌ4MÆS3;MÆo.ÆÁùÁ¦Ïq!M½â-·ÜòðÃmm_<Ýû_¬ø}®ø§#G6oÝú?\~ÿ³Ö¥º[oLàUV} U¢}ïMË;;Oÿ?ú5WôúcØD:~ûÛß.B(¥<Ïó<O)¥*OäÇÇ
¨8>áWÏU¿T*W×b13>DÉ\ IÅ
+%Ë÷P©T6ñBÑÂFlC¦5Ø42 ,ÀÆÊÐlb|ö'áð /¥4nά3tAõÐË@,×å 8ÉZ%Ä6ÊÕ£ò£U_³_ëÌù¢<) 'ò`T)address@hidden&g
2qlipÏ4KñbÌÅ2L»sé8móDÂpìÀËÏM3ÙÒÈZ3±Æ+ sGÌdÉѹö :õa¦e9/\]&jt^ù.ظL$®¿þúÃ%n}ʧ¸ùOÏÿoßÞ¾e×÷{ÎÞ·öÌØvÆ^(ÂÅ,ÓÜ%zÈ6n~Ç;þý3ÿ÷<Û×ø7n>Of¢§·©Pzô³î¸®ãz\ÊD¡+JùÂo)V(R
5ar6`Cõ²Ä ·e"ÌqÄ8r h#Éz
+ "#æêlË îv `È (Zº O÷ Q
ªÒ¥$æéK3ײ֬ÊÅãïÅmÔ²öxSSçÜqÙs~Ôs`]õZiÅ ²ê¥'¼ÿþûþy³µõKgÏÿ¦»opäñS§v\yõ¾üÄÝ« ÉK
Þ.c<7bHò9F5¤jÃÿ¯ÿöÊþÁÈ<¢Ñ<Ñ hä`äÈô,ñÆ[)d) ¸Ë§ÀsC"¤cG4¹LSjÔ(©qÄÑD<'âÊ2sñ¸0x
0æ8²¥%ÞÒÅ-ÇvíXÌ®°eYVÅrÓÅsÔüzqöSΫ¯¾úرcÿl êÝÜ|øgÏ®ýØGím·üàÌcÀ2a!©E¼EV-JDG¹apä/&
+)'address@hidden)1¥r¦1 sòx6ÏÇ ×¶ãËÚÓ]](ÕÙO´µ!b,³,Ë0
ÇqLÃpb±<ÑæÖD|address@hidden,ûBwï±ã7góGÏßqå5ò
Þô^ba, g
(i§$_ªIg"¬÷Ýs( ÎRð#Ï]ÉÍ
uÓF0 DÚë,§JÉ §£¥|QRhH1Ì$âYÇÎF6ȵµ¥T[«J9-ÍeË[Z|Æ !Æx,Çãñ8c¬ïr¹Ö¬^½{÷î×_ýËIç×<u®ôk¯¼ºçÖw:«¯üÙýÃnöwä
æ5ú|[±°jP$zA¸k9 à¸'IþfQÅЬOü]
n `$£]y:%!#åiçàl< Ç;eI9ÍÍeñööX[[<ÝÇãf³zÀí·ß¾oß¾x[ë?îý¯V|ç+Gä;n¹z×® ½ôÒ{,gÙ
+ ôÝ,_º¡£eÂzÜ(u¢ÑÉX#2 address@hidden Eã¤&
>Ǭm9±ö6§¹Ùikµãñ¸Ö:W¬Xá8a¥â¿Zð7ûò[OüxÛM7:˯ É.ì# æîoÛK÷
kÙúRßÞácìûç #)CaÔ-V <
¯ºÅ»¬Xdºð.¿ÒlrHÁà yýÔQÔQ `<f;vÆ4eÌyûÐèIR=¤¾âo7íß?ôÚßÚ¼ù«Oýü&sÁæôÞ±Íw°G«LXí1X×
ЩÜÞwNÞü]+
+àqÏ]ÍÍ+(¶ ÂRG²É À/ ² Fèç¾;̽¦
ËÏüýÐÈ¿rPrÙBÄ»gH=Þ4ñ[Û[ÂzNÐÄFÙû¸zIøýDwÚ±h°F03·YÎ9¢óJÀrd¿S]À¾ê^T
§tBÊÒ?4~à:/µ´^UFwEððë¸ýtz
ç pR
+ïS±
Ææ¶þÄIüK1÷ßbI hCöif~¶{¿ צB8¯d¯¥¤»²C^Ñ©>ÙH
K^Ï1Â}ô£3h¾Òø+ÜóJþ_úO±T#C{sE'ã óßÕáÝýM,îÞ
++6+I
)yRÊnÛíM¸Ír{|GH
aO%¬pbâ7y ÆH}Û+}ÈN¤12´G0 ÀÝVì/
+k +è þïNòÿYݹõådÚ
D¾/r¹\±XtÚ^Ù?ØXjmR+åfêJÔ
u.ß}Öùï2 À7¼â»íø é"Ì1ÄûøÝüï:I Øaë{zݼy³ò\Ïé³Ç^n¥N[í¸Ë·*-V¼Ë_X4áæHX'NZÿÙO;
_É,Á"D¸PláæanþÄwo5m ðÿ`æ>úxá©RºtkÓèÕ]^«I3
+k7Êß-èè0+ðWz E´GpQá½Vlôû&d äóÿs{ÿ}+½µ)HElu1à¬
+qu$^Epqp?î$ÿÅ-
+ ØÌÌMçS/
G ³p% ¾ê>W",:¿Î´¿ãôL»bO ¶³~Ô1 DXÏøîvÃjc"B
Q o¶ì!¢ )
Ù»ÆSß8yÞ°ÆHýLø¿W", LÀÚóy" ¸YþñÄË#QÇ\ aÀWÝâpâp!¢±Lç
¿ à}2ñè~{Ì:æ"ë¤<JÎ!ÂÂca URçÅoBöL㿼Ä}uÌ
ð©X*ê.b{
ûi¡ëÁ:flïiüÁÉ(°áB ka&£="\2ì6£Rè¸
9ݯƻ³QÇ\aEá¢ÙfÃ|Ö/ YÀ~ò«¼ú&"¬ ®7íçä¤åjã·6þ¸;aE°øÐl'·^£×
õúqk<òF!Â"Äu¦õc1ÉO&àMÙÄÓ½ù8"¬ 1¾¯ÉI!ëZn =aE¬°"DX¸Ó=æO
+Y6âîÄsç"!+"¬ ÅU28ò6f¿pÄ6EG!ÂbÄu¦u0dzwoH>y&²"Âaña#3©*«Õ Ãê=m0+BÅfƵBðÄ ç¢Þ+BÅ]¦µ¯²µPãzÃê>|q0ê°"DXdØÊÍJÕB ñ?Pâéc²8D!¢B q
3UQ4 kéÊDÝV Û
ëYËp3Å^8Ã#KVDX",.läF CUàÆO9çòQ÷D!ÂbØÂØé¯Pã6/ñäI
YaE°¸°½Sk;72§bçrQ÷D!ÂbB;ãçT §àmnâã\FRVDX", t0æùPËL¸<<ÅdE!Ââ
ØÂã²Nr;)þÔQ3J;VWæËõ+xUꩳÑè°"DX4ØÀóJ¨½êW çµ£öh´#:"¬
,ÀÜèâ+ àÖ\òÑ7PEÖ÷°"DX<Zák²~ú¾«5þzât´Y'"¬
! PÓîx~P& 9lú2꧰"DXhb¬P ú_c«zOð"DX °]îµ£û¯EýV
Ä<MKX&àÇ
ùÝ,JU&¬Q5,B_eh&/¬ù\üÌß`X&¬¯0õ *ý,}Ç/ Þ°è+B7-hÕ½"ñí#K}¡QH×®õw]ýînÏu5Kµ¢T¼AÁÕÀ6r£ñhHEpé4#°ñ¾xo.»:µä
ëC úÐ>ð'Oþä'?ééé9øÆ?Ëçã¿Ö-í°
address@hidden B
DcûåìTï~µð_÷H¶T§
|jllܹsçÎ;ï½÷Þb±xæÌÞÞÞÇ üôéÓÇz{:ÞAl*åûW
+u ubFãô!ÂEÏÃ:¾êV"address@hidden<a
ŶlÙ²eË[o½Õó¼îîîCíß¿ÿìÙ³öõ}G$bÜõ:</-äjÀm¶1caF~Çæ¯#5ªT·¯üÃÓ3lw.ÿy;±q øÿý+
߻Q,M!˵
eY+W®\¹råÞ½{
£££}}}ûöí;xðà';GD,ë[R6³ù ¶näÆÆ-ÇêÀ%:§dçH zÕþ
+ý cV¼}õê;n¾9mܸ±·çì?=üo¿u²§Y²ø¹Ø©Lvòùµ6öööööö«®ºJ)566Ö××÷ÒK/ :tèèÑ£§O 0_&Ò.b%w³WKÚl#73#b¯K0ªÔ
%N+qá8ÒbÎ4F¹Q R67·uuuµ´´\qÅ»víZ¹rå²eËÒé4VüÃ7ï}âî÷~P |%ÿüïïr¥§ÎüKÆXKKKKKËÎ;?òLLLô÷÷ <xðàÁG íîîÎ:ö¸eý¹^"_hõJw»¢ñ Ü\ÇhGxk3Ô°g<ªäQTμ³|3æ+%¥lhhX·nÝõ믾úê+®¸¢©©©¡¡!LòilÂ;¯¼òÇïúüc?I
&Wæþ¢»"Ö
iàét:NoÙ²åÁ Ìf³ÃÃï¼òÊ /¼ðÊ+¯={v(ÓþAÞ÷ZòÇ+íêm»
ky3á2Ç©SRô*yÔiÓ Î1,Ü3,³R ÐÕÕµaÙ²µk×nß¾}çÎ]]]ÍÍͱX
çf6aµï½éÜcOl ÛÐ<6a-
y544èä{îÉçóãããG Ý¿ÿáÃO:Õ+Ý:oß÷<3_[*ìt7wrÓl^7\¢>%Ï)yNÉ ã
Þ`Pà<°¥wR*¥»ººººº6oÞ¼}ûöõë×755%ÉX,vÁÞyõÕG
c$ ØÀøs°ä¢H/¹jH$ÄòåËo½õV×u3ÌéÓ§÷ïß¿oß¾'OöɾÃ1çi~¡Xl+¶¹SÒfláF{$yEXèWògÂû9¨nÃEÎ| Ó¦)BÈöööÕ Û¶mÛ´iÓÚµkD< glÁìL6mz®9Æ@;ãÝç9mKm
SmI¶m·µµµµµíÞ½ûüd. >tèо}û 9rìر®ûcÓ´¤ä%wµï])ÔuÀvÖ¼"\zH~%OKÑÄ
ãÇ8º¦!R
², B!,ËZ±bÅ+VZµgÏM6¥ÓéX,Åê®ýüwçÿå¡"¤ ¢ÜRÓI~iÆoÃ0´ÙkÃ
<address@hidden<qìر ÊfXÖ7x±´Þs¯ê&address@hidden&ü³J åì aIV8WJ
á{ßÞظjÕª+VìرC»ðâñx,37{úì¸ûÎ}_yè °RGÇ`{sDX¿
Äãñx<ÞÑѱgÏ ß÷³Ùlÿ£>zìØë¿|xhèuÛúP,®rý»Å hÐÎÈ ÚkØ-Bµ
Õ-ÅkÂï&ù4 Íy27M]ß÷}ß±¬U«VZµjëÖÛ¶mÛ²eKKKã8¶mã/[¹á¦>¿móͯ 7 næö×O³íÍ*"¬_2LÓlnnnnnÞ¶m2;úê«?øÁ}öÙáá¡ ? RZ
JQh; address@hidden Mк´ØÔE!´"³ÅSÈ
address@hidden,1n®B³¾¿¼¥eóæÍ+W®¼òÊ+·mÛ¶råJÛ¶mÛæo×çܼîZÿÕcb+cãÖ"{Cétú¦nºñÆGFF>address@hidden'I
kª,Â&¢O´ñð-ÚÕ$Ø,ùF¯Iÿð)yÁ1¤óEVJ*åºn{[Û
/_ÞÖÖvÛm·Y³& ;óæëwÕ±Ì 8k1[[[?ûÙÏ^sÍ5ôGdF&¯Î«i ¬¢Ì0 '·¡InèçÓ]
°kRi *¨ê:s0Ô,` ø@
á= 0üÚ 6dá«´2æ2j Õªq°FV¥±1ó²MÂ1Nê ðIñ ¨8fm 14 ß÷
ÉdrÓ¦M[·nݽ{÷UW]ÕÙÙiYaxy®k7l8X Å%gñ¸Ì"ÎO<Ëåî»ï¾Ïþó±XlïÞ½>øàÜ]3BL®H¾ïW
ýññb±pr||\
8(Ï
4aI9ÉÈuÝl6kFp!D æ"c5º"2Æ|ßß±cG©T:vìn¯O²apgÖV¨r?n©DDe±\K$¨X
+Ós ¥ú-á"address@hidden|¢ ¶hZDà2£
P3 HUS3l*j#¶àä»îzd7b¿Á0ns3&ò}ß4Í7êÝû7ß|óÚµkMÓ¼|ªëׯÿ&^eXôbÉ(Fµx±iÓ¦W^yeÕªU/¼ðÂÑ£G =ÚÔÔÔÒÒ2ǯ[·nÞxõÄ&¢írê×####ç
?> 2¥T.+
+>úè]wÝ%èîîÞ¹s'cL111Á9'¥tãb©Ífñ'âÖbôåôuóù|©TÒ=Ïs]·±±ñgq §%«!zÎy0¥
jZìF´Úcu[N'5ϱåd ¥ôÿù|>JY¶íy c¬³«ëꫯޱcÇ5×\³cÇËZ©TêÛ ~°hÂ5$Ç°±bxÏ=÷üå_þåý÷ßÿ¹Ï}nttôùç¿ûî»/Ý/>²¦«««Vª_»¶æëºÏ=÷òðáà +W®dh9Kÿzd®0Kª
+H)©Ô+/¿Ü?0ÐÚÒrüøñ¯|å+CCCaI°X,NLLO266V*&E.!FFFÂÊårZº
¤ZìííÍd2MÃlX£OÇ_õ_?cúN
e¦R©?þã?¾ùæÄÔK¼%ÑÑÑaÛvyÁàfoTÒËo²i ýèG zè¡ë¯¿þÙg}øáo¸á¹ Y:(±¥¥¥X,address@hidden(¥
+!ZÉ IDATÌZð tmJ¥L&#¥ÔçB¬]»ö_üâ
Nd×Ý/{®ðï»a-ztvvvvvÞxãû÷ï ùÁ~ð|ä²^]¥ÅbQ±|ùò°éKÓVeZAU á¡ wuêîîïï_@
w.Ç-[6,yèïïÿô§?=22ÒÙÙù©O}êàÁëׯÇ%æfåqP ÙpiI=úe[ðÎ;ïô<ïÞ{ïEÄG y¤§§ç²~
Ùl¶··3nl ª%,Î9cóɯ0Æx¨IgÎY¿aRʲ¬·Æ`%¢ï~÷»ÃÃÃ+V¬øýßÿýS§N½÷½ïÅ¥"+vÕÆû a]hllܺuëöíÛ;::|ßøáÃËrÙä|tlÌÅt¬F Î
+óT
ªôç©låºnooïêÕ«ÒéôÈÈÈ[`°>÷ÜsO<ñDGGÇ wÜqäÈOúÓ¦iÂÒ¯òµ"ërÁm·Ý688xûí·#âÓO?ý_üâò}T*µbÅÌÄD2´m[Û«´28ILµ¬Å¹aÔÈY
+yúôé[·Ú¶],çåH]´ |ôÑGhÅã|ò´m$¨@,É¥õìqæO˲Þó÷<üðÃ---ýýý_úÒ²Ùl*5idµ¶¶Ý|D"LB(Ôsj(i[°¦æK!^uvv
+)ã±X:À~ 2]æ¬Àî ÛµÑ
T§S§Nµ··3ÆÆÆÆn½õÖ·2øõ¯ýøñããÜsÏ=ííí°Tõ}µÀdDXvìØñ /|øà þÜç>wüøñýû÷/_¾<<ʳÙlØ]*´¯*HäóyDÔâIj¶hQÃP5>ñx<Ì ÐÖÖ¦¥!m·,«©©)%¢ÆÆFÇq¼É9/
+étZksýý+V®,óU
¨Âø0a)¥°zn3ÄL&£ÉºP(ìÝ»÷r ¦G 9pàeYøÄ'ÆÇÇ?þñãÞÏTò}`
t|®Ç"ºpÍ5× >|x×®]/¾øâóÏ?¿wïÞ_8çRJ ¡£Äb1Îy< ×Ää8f Ý *b`ÎÂëºa= twwcL
+!òù|ø
+
ïûaÞÅbgÏ ¸ï¾ûcÅR)¸²z¶R¡
R!ñ*l Ä={öèh3gÎLLL$Éx< ~ºt: ¶ý0t9µ»ôù0è±Ç ¸ã;Éä
7ÜH$,[
(©*½biíÎ)Ö÷¾÷½W_}U[:Ѷí+V¬[·®³³S)¥¥X,address@hidden
+ LP*8çù|>¼q1æyïû
RÊx<®És^*òKN*m>³\ §I*JúO¸ê4QÚ¶]CLæðáÃ:address@hidden
ÚaÂBd===÷Þ{ïÓ§-Ë*
+
B¡T*¹®f\.ã×ï]3i]Â"¢àÌ©
+u[[[ðBX,V#~jé2¸®aÍÍÍúTú`ðZö4 ãøñã/¼ðBGGÇûÞ÷¾îîî«®º
+0~ò4Ò¤úo$a% 2þñgFÞ0xHÅR
9·Tôýæövö×[×Þޮ礶tttX¥¿"b[[[" "=MÓÔs,üuá À0¶nÝN§;;; ÇI$
áD2ÐÞÞ^ïwï¸znçWJéxîññqMvzvss³5Ú} ²}1V,uÀ·FSS&¯t:=>>^#
[*¥Þxã
Û¶s¹ ¸[AEh
+È(²Rª « :}útGGÇ#<ÒÐÐ000ô®z
#3u'árÎõö Ì¥KÍ s¦2LX÷</ ¦kJ©À¥«w&iá7ؤ¦ijêB¼þúë
Báºë®ëîîþà?Èv³þþþs: ¿Ä$ ëWù«SV 9¢âR#cgûó p²ÇWj3ET
DYP}Rfú
ï¤RR)]O¡Õ²,˲mÛ¶D"¶njJ&:ü1ÖÕÕe¦6÷Ô¢MÓd¡?Ô}Ûo¿ýgBµ¿
cL u¯mîµ,g
4ïíí=zôh¡PH$Åb¦è§å¯c<address@hidden
1Ó7n4 ãôéÓË/ÿÐ>ÐG& Kóïûúëèè¨Voµ
V(4õXåyçyãär9˲±±±1J!¢ïûaÁ- kîSJqÎc±Xx9
HPsâT ¾õoõ÷÷ëdÄ«W¯njjZÊlEDÇ Ûé î¥)aME1|õ<3Ø
+%A¦ ãg&$ `H)0t h`KêmõÜt{»GD¬aP2ll4m§£« mÆòÎNs
¸¬³Së§DÔÙÙùÏ|address@hidden" address@hidden"ÑÚÚ:wÞ£ÔyâÄ
}ãhÇëÔ©¥Ù0Põ^îpqJD®ëj7þÉØØXOOϲeËÞÿþ÷^ÒM£[=ôÐC~ï{ßäv0o
K§¢jùÁ} sÑ*[kHê²-ÆÏNAQÆIÀ(¹b,ëé/yðÒ
R9Äò h HHÅ6Ü°çÙ¯=ôlådã$ÒÊñln6m 8gR*DLwtTI©¤{1˲Â
+N ÞN>RµÜ¶UÍ BL&Ã9/ííí¯¾ú*Ù
+ª¡*I BÁ
ú¿ÁÆÆFD<þü0ÔT©sóæÍoÂè<xðàSO=å8Î={úûûßÑd Ïó 8ð'øï,address@hidden Ø
Àä À ¬
¶K9 È`Þa6¿8Te$" ¢P§1" tZY¬N #
ÓiR^¨0bªJÉdÑäeÅy!Ô.<ítI§buF Ó²bé4 r0Æm+N+EÚ¤¥Yrlll RHåô*JSX
ì¨j.b©ÔÞÖ¦µÁÁÁËwtjissóÁï»ï¾¥Ê Uø\.÷óÿüñïÿÐ×Mü èù
¹itéÖÛ¸õ;address@hidden)!)"$ < ¿ id)ÄädNtf# 6¢
ÈboúX³ÛkväNm4«¾«ÙZêA¦f+Ä,tP ÊUe8 a"Y¡Q'Êù SrE¶aáyí8,,SU
U4%«µ&&&öìÙÓwî ç<;¶oÔ 7dVcé8P)Uãù5M³Æ¤V5Å7ç%®^½ºµµ5Ë]{íµ«Vâ¤ðÔs´þ¦Å£Ç
³PÔìAÊ\ß÷g®Ö÷ïßÿ£ ýèì3ÙAsdôVÆ?üFÃi¥0ü[¼
/-¡ªF°øëg¶Ú°åÕÝ^6Ô, ( ÆÊ* êWê8)Mg 0d 4"Ú5 :ÍqÀ8¢
k> Vu¢^ñ²VÏãñê~n-|CþÚ÷Ï=»k×®!¥¥Ã¬BDU`
ÄÀÊ f³¶R===<ðÀ¾}ûcJÞÆÿþ ,Äa¥ÜÊàfå
1^mrãoÙ2°!æqÉ'_oÅxUùâDK Qã<ÙÖ
+¡÷è¤Rv"ÆX²µCª´+kXR7|âø»¿û»ï~÷»ÍÍÍö],(address@hidden&`@
üLfll,`:«çAc)e___pªÀÅ©ÃhÂþ_-$B%ÝXÏ¡}Éd2J1Æƽ¡áüàPvx(/´2¾Ò0nbÆrÀÆvØÉôy0¬Ô
éÿg;ö>À_rFw
þÚôÞ85ßwpÈ he¬0ô«ò0t* `B©P(GT:*}È#P nÅæÄTþ¡ b ¥¬æÍ5
Zá!2¢h j_JX5iËãIǸ¿*¹ýýýóT*588¸zõj ª
Øhjl ©ö´º®ÛÒÒgÏR~Ø´o2§7« JÕc½ädçuçã¤üЯFªÓfåIªSßUkë¾aT`.AïýÅBæ ¿tà_N#+
+½5<KR0-·æ2÷<ßJ&çóqë¯.ÇR¡¾IÛ\ËÅ 0Z-°x S{! FæB
°¡zúPhM+ÜÌe¥y â³öyèoJ¹M o 9
+ji*UÍ$íV7ú¹ªY6É×^¢ NwäL%
+D%¥ ÎrI
+e5_=Uõ! address@hidden address@hidden( ±¢
¡S+3: ºjÎ2d¾¯ã¼öîÝÛÛÛ»råÊI¶
D Î.¥|íÕWGF¤LF¿íÚµ«¹¹ù¹çÛ½{7c¬¯¯òù÷Æ/y @:4u§Õ¾gE©ºúK©Ê±y&©³+Ô¨;-OÃÚ±Ëlµ.Oýu·p37:
Ò ,ºí±%GX\¼ØASx&õÎÙOÓ#XµµÎt²ÊÕBÜ
+>@æIi«CO zH *!À*fØ)¢Ð"1Ä"QXUW¸Õ´è Ð\8O
+ = address@hidden<Ð ZyòÉ' ÇÙ¾}{6=~üøjÆDÇ¥°êç#ýÃâQ©±Å
+(address@hidden ïfÆ«£ð+Ë"aÁ<
¬ö4IyÐDkþî/ôö¦øªO«-hÔ [
í#U0
address@hidden"]èSÕѱïÞïe²|ík ÐÑÑ¡c÷'ÙJ° qýúõ5Z!)J¥î¼óN îôÕ¯~5Ó×÷Qf½(} p¼m62µ
Q1جЬ,. ¤,ÀfdS`
+D ªÕv«b£\´P E"µ`C
Ze
address@hidden( IDÀà ·ær´Â#.xÂ]*á¼?0{éý!ÓÓÁ
Ñ_]+ ^ôÙ¦ §©w;u © Ù
æ-<N ÛcX(þúÀØÏþì/¾³ãk×(Æ
address@hidden,Æ8WJ%x<ÍfOì? gÎü+öv|:!³ê æH2D.P9ÈÊ\æÆÆå²SjÇ
D ÊV«Þ>xK h2 í
0 Ó!D 4* Ã87ýÇÊ×Ë4 à)Qýè 9jÊNúÕƪ¯k¢;½)
+l@ qª Ú°*k\ ÑÌ) address@hidden
+¹ ¨?'EpTIFK°pjéÝ"S&Ö#Î\-MÑR/à` ¢Àõ°.mÕAÙÀIÕêó\Ø
+ë ¨º.µ3ÞÎø^Ã.<ÙëV&¿¬x¤
address@hidden p?ÌÆÚSÍ|g u)" $%±ÖY-Í*ê Òlo ò+çT~L Ñy
U¤<VvÕa&1¥ºÀ³
å äÕC$§ºiöuê 'ù{=-§ôç ÏSÇtó¤ïý^ÂúýÒRl(ÖCL=Ád+Ф(ÐÐ,T¡v½%% ce'=Õ(SSHBsMæ)ð"-kTq'¹¨êÇ!¥z´P¢ÎG´U¥±PµÖ8ÈìɮⱠOÍ¢íÆálÆY ¢t¡>wAuZñ9¤>address@hidden
[kgoiS=Û§¿I-åÕ, 4Õ1#¥Ò4kí̦i¨§,yc=Ë*VßcxpÎÎå|CCkÛ?w~{{a
V¡mh˦~)H§X!)-!²Dï[RZ¾Hø~Ú% Em IUR&¨ì)!¦ MÄ$b j]cs30M'address@hidden
¨8 B )©¬
+1¥d6ÌÎ
ËA¨<* ´z>M([QT"t¤YS§9E¦H16¿J #Ú
+ Ë`
&ªgcÐdÓò<×6ÓMª¹ÖòìBVÕj5l;-_Ð,S1ô«¹kêÓ®©3/-TL¢qn6iõi«|address@hidden)ÖØØXoo¯i:ÐY'H1'¨·{¸ .ÀçDtNJ"%¥²
¥òDLISHK®Ôò'dMJ5´´t %Ú¦ ¬·oqfY
gÇfÐ=ëNòÁç}ÏalÙÚµáT¥½q7ø*¤<'DøHçé±´¡¼&ÏJàº2ø)Êå¡â(däû² °Ü$J¯2OÉ´'04¼R&dù
&¢PªÅT©Pý^Ö&µi
+g #³ª'o#ÂäOfd«8FÓHÐ4|:ñ «
MEaén(N;&ç ,v+ÿ ÈÆÆÆ|>ßdãÒ",Äó< «
+ªUÉÜ¡AqB
s>T¢µAÊÊÊÂÒª HÁ´Úå +DFÔ9
À¡¾cÔNú$2 ¡×R
+ÇpÑ\ôÊ-Üeü
èÊÅÝP)åUË}®
+ érÖóÂ4*¥ 'íãË 1y¤|>¬©b\/40esá)2®JMd~SÐjnLªç!çÅ´SzNR
Î8ùi!btæâ9áBXMÓpq¾©²z® þ^}m-Rãããmñ¥Ùݲ®¿2 Ê Tçy:P¨¦A S a
+3
g¤ °vÍÁ
address@hidden ÂI VDò?Sà\Ña»[qÚh¹
+qÓ¿g&Ç)Bå
+ÁÌT 0AêËJ|¹Ñq¾¾¾ÏwÖ
¬2*oÈ 5
+T§s
+ë|Ô4W2Ã# ðZ8£yhöê#Aõ`ó]T¦ù\þO¸óV©3ºx^üR %/lP©vÆjLK8îOu½Æsw,`]{¦&b"¤:fÒÊ©g÷®Ìpoág¡t3òl²¤F2DÏü¡c
&TjttDJi¦¤°.¥p±VPú§ðtQZÐÓÿÆ#ýï(/DÆs {uD0ÔC* °cF}Sô4DX=gqVëXUë
address@hidden;¬Ç,TÏvVçvÊ5 ¡0 address@hidden@ê,Ãs Ï# óL^2
eYË4-K¸îøðp.ÓEµQ#IÍé4ÍéùmIyÞQ¢®HÍ
rl*
ÍãzÊ6"¡øÑ(address@hidden<¬ m®¹%A4N y "M 0QY
«iL¯ÚûA4T,address@hidden(
¾ïsγiÒ °Þ3'ÄtK¼ÁÏy¥¯*_Ï1ÉP`yÞb`° SJ
imHÄ$gíF
+Ô:(s!±j(:3#&\,h%°, Æ ËÁàiEçMN08!¹c2poº]¤ °
>ÔÖÒÆÙ°ÆËR
+ 2HÎAD$¥ó\×
ú.Ò¾¥þäsë ]4ué¢ô2¨ÛD
+dÈæÅ+£ü5L±Ê´Ré
RÊàTáíâxººYõ¢E ض¢¼DTS.7ìÒä2ùtnXK¥Rê2(TÃoª ¶f5«§
address@hidden 2¸a®ëJ)§¶ùHøë̹èøaÖz6ý§â¸
§\%pMýnYSQ|aqc»XZ*áõ¾L½PN
)︢
?fgX1Ñ¡è:1ø GÅ¢sbY².-a/ FôVí7¥XôEÚ
.³ VrOZ"éLX¿0ù¿Æ.Ê»?ø¢1×xéØêf_n/eOõg?Ó·-ã|=Þ\¥h8}Àà¤?Pô:Ày¥´M#bKGX1Ï÷\
+
°ÔÚÔRyØSKç.z,>mò§ÍB|an¼9Ì ú´B1÷°lÏ7
xAqf°6§#º<QD(ÎmJhʵûÞ²hà_¸®ÛâØcRq è^Ä85.®-çy¹\*e8çaè]ÐoÙ'7 %
*Zö/J¥m;}ùüÚAòf¢+&Îà «±±qåÊD¤Ôai¥ëyR*ؽ¬Ý«añ 2]WJEÆ«K
Q*-ËEoRÊÿe¿t·LXù|~th¦ÞfY¶ã8å¼D:MgpÝëzRÊ
æEp×\v=ùbH®°àJÝÖ%þ'·.¡U·L1ÿ©äÿ¯Å~ÊM R g `±qnd9c#ÃÁ
+µqÎ5s !ÅRTÉKCZ.É Å¼tÓÑTâß|0Â¥) P1)eÔí ¦|g)©ÚåÑã 6"¶¢þZ§QUê>ë¤
R(address@hidden@jÔyRã<8Êi3 µò¨?Tvð· ÀBý!ÈÊ týAÓ¶¬i,µéý
RÈ EÛt.%aH¢!D í Ö®F±xG|i5j
+©ÂÔ}ó¬ü7ª¤]c Hs¶)Ô^.æÊWÊ'*
+oèg&/J!
T¤
>8ÄYó~ Çõ Ö Uá£ÉD JÖëAª½! X æ£` H°g¢
>ÃPBäªIUaÏdZ %éºndw¿pÕ¯ IiÏó¶ù'Vl_XEõ3j<oÚÄlr»j¹f_ °3 ¸ ¥«}
>)"¨ëò>WÈQ"H×6LTIåÑSj
>S¸aáDåÂgHYfPs#¼þH)Å ¤JI]>GÃ4M(¹Ñd¸´3MJè1çyaÍLIôfFXÓ4µ¢
+úíX"ðb\
3T
+Ñ¥HªJ}àdUùÕBµÂÈkºd[yþ;M À¬I,¾ªD0ÕH:ï
²êz^yáåÆP~HA<séH ¼Ä çUhò¥¤`5
Sày7 #¦É+W "ÏóD¡À¥R¢T¿¥ðm DÉ%¬B !Ks
Ö-ØNV]_¯&Ñ,õ&f.SCDÉÂ ËmäF½0Y¹Þ|address@hidden"
¦lº®Évö U¼Ìä:´%·¢:
iZe!¢ïyçù¾¯ç¹nBªvE1%¤Bf»¹±q`¥nj`IU%Ë5T¤.0µ~Uº¡r
+RAÙÊ )
)\Ò\¦!(¯DA
+-à«. ¤ M!T*Ê¥C%é¦i
+¦$a á<×aWL8 X>y è2H_¥ý9á6Ó£rh&Vªð= ÕU¤D
+RúRæô>J¥ÒJq6© \ 0(©¨SÈNU¯BÞÅXVÌź4òðì¬[³£k6aMO3Óåpz"
'D è5á=*ý'MÞc.QP $ȸá1 V<¥¤Ñ 1©âDå °L©
öT¨Q)hÄg1dÌàÆ9á ?räµ×^cµ´´%d1ɶý IDATH3¥1ÆÉdxL¦H$jÕ©Ëì¼¼õô
õÜøçIW6¸H !DJ
`&èd>ÔéúqNÅ8"%e%ýguílDnáÇ8gR:xPÿ+þ $år_0¥ZÕµ±<?Ng,© 3Æ Z
Æy3²ï',UV4°C4\»^ ãaFËÐæÉÝB½oKXspµn¶ºStºðÀßòÈ¿m¢- à¡
+Žh
Tà xeÎû àWN{ëßVO,k q£÷¬eÙDÔÛÛn¯
t)%Ñd> 1a:Öqì
+£WoÇq8çA(-ho&s Ðq ɶíX,¾ád2æMÓ4ãñ84%
«ºÆ\X²&aÓ%B>ÙÄ?¥êÖÓ®r½6ý!+ÕOôrt°ÉØÄ+7à<)ý{ÈÌ×5CÐh¶3æ ¶"Ƶ`Å% Hí
VT Û?ªËµÒ|fÐtªÂÚ5m ió%MXs©ãÓ<ÎæôþJ>Á}¶ó_<
¤e³ÙT*ED5ÙÔÂÊííZÎGDÃàa©óÉ}EsÓUΩ
MUrqFQH¦:RgMãJïûáº6ÚÄÄDàͬIq'ªUàHÿ!ÊÌ>address@hidden
«a&"ZÅÉ$çÜqp°1ª³KÃö©¹èÿ3®*q>
ìzú¾ Ð,Ä7
+¡ÙãA^ýqº
+´
Ë%ëNO[Z.ÂIÂê%i)Ùh M;¦{:¶`V
qJ©ËÕRzaÙ{í÷|"
+l
+s=¯Âójb¸ÃDÌö²õ¡2·u0K j
«aoN
Åh£©ðzz×LÔÐj[GUi©:UÈqêÍ rÎjÜÿÚ:;å1kRÍnÆ'Ó÷}ß÷5ê¾ÒÞ+--{2|˲ô½++Ødª¥?Ínº¯,Ë û/
`$B bt1 f4`Ãä$ì`Ì$-cä
address@hidden,à´¥nf¦é¢ÊD表îÍÑté'%W·k¯PK°^h
o.wO®jCÞJØN¸ Ù
+ÆW!oaÌà.ã¡
[ j´é¾úÅÄ]oZ°q!i£££###5sl:hyª_jÅýW˲ôô a6 øHÏg}Ð÷ý|> æµRúÖ
×
address@hidden
êâͬV <¿lÛªy©«ï<address@hidden(e3Q«T]ÈV![¬
Gýú Ù ¯s)
_;¤«sÐHp
+KNzeĦHôåè¢òAd$ªµgm|óíËt dü¬Êó⩼ê /gæU 7
[$3¾ñõÈ:9· ³®?jÐ!àÌ:#´Ú%Çã ®ë)=O¤á_©Pz
§Á\â×kêNå ¯É.ü9ÄFàÆÒÅTù¨FªÑ°9 f½i)Ì;¾/jXO\õ=+D<õÆXñDÑä§æÔÍ 5<î8N|Wo!
+ívÒ½Q#´jGø<b ÂIè
+`h¨òËe¯|¿(Är_ìÈç?ÀÌë
Ó6xfµ´Ö#©%i>¬7Ílº²9¯zõ)µ< K°ÂzJG£ÙÑX;£¤¢¼ ÎþÌÉçs4ñ³c
Wu1s
±IkoçÆ:ÆmÄ$ ]oÉþ=M 6pã+ÿ<×&¥ÿ¿½oä*ïû}çôkfîÌ}ì½wïîJ+VzDB
!L0d¶)WÛ$$))ÊÄå`§âTªr9NA%¡HåR©rl%eãÄ
address@hidden/ôtÏéçô¬Vàìö'4·g¦§ûô9¿óûÞY£NuÃýHnÓ(¢[j,ÏíçéµVqÚC
+étêä4'SUÄÐ<ËLÙVú»=+ kgÉWt
+4Ï©)TÆAæRÛT]Ó;M»Rjww7ÝL¾fÞNýÔ¸~;1£RfjÚæ¤ZëlW 2¾rþü_X
YƤJt=±èM'«1Ti|TnWçদC=jÝcKD\Àµ3ZßØ¿æ«Rá´Þ·ÖûÖ Ç2ÇýHïô¾¯¶Õ¹Ãè±Cµ?
+··Ãµ}Ôâµõ:ËTr6 uò§ ~ÚñÝ=ø·ÑØr ³e¬5$NmpÞè³(¥Q6©I%]ùq|é#eÙI¼ÅGDq§&$ ¤ãåñEQN²ë½`s,ö®1qÓ¤xæ²ÕRòuy¸Yõn. )address@hidden|©±->ÉÖÖRZq³ <d{¤ %§7³b
«ÎR£ã< Ó{ÑÎÆ~-k¡Ú´ó°ü©&?ô¼Vonk^ñ,áõÅzß:½kg¨þè[ûx|address@hidden
¿¸eFk2m+)@Ä2¦ÊÈx<.¬Xmô¹)Dæ|ÿÂèû.×8q \ôÝ¢
+Æ
áC£+´6[|Rß%L Hâ*Rh8åùÏeEÅ üçÌ9[µÖ#¨PÍê²W1© +ðÒÒ¢É2 äx7RJ¹®»à8?¢2y0]lSÄ1r96®õcÖis\çR/&cÚ´è?çV%¼¢²Üïºwit×à3ß:øG~ð Q÷f! y²ÍàX[_
úÞÂ>5èû¾ïû¾eY_ܲj¦¢àÉüã;qAÞA©9NH§gNN9Q²ÞtúS³Ö¹vx9ú#
×ÓI¾ã
jXÄ9êtà1rDÆtð ]¢ú±EÐQðd0¡*v&º®ëºN)ÓjZÜâfÈAäÐФW5Ó¦Õ_d)ÆÅ?3Ð^¯×ï÷sçßl99PÑohîv%Ƨ8g¢ÎUúg¹¯£
+48d(`Ì glxDNãfföE-`]iéØâíw
¶Nuóûoú¶ú!áRÛ%ðÒø!~1 ðÇÞÒÒp8ÜÝÝMxJï&Q+Ò°ç*Y.T*ï NsÄÇ Ê«3µÒ½4ej&rÅ
Í }j¹ÎÃÅ»6+Q̾¹VÍÞWÚ8ílbkÎX Iß÷SºÊÌñ1#Z,address@hidden Ö
à >À6ëCðÖà3ZD¬Iâí!
0 Qú½Ò¾-ëTå2¦EÝk±&Ò÷¨Úêõ Xþtwwûþ;µk×EÉ3Þ`9 ñ_Þ¾È+ËB ÃéF
sPnq¦íÔ«øNZ]¹a©å2àb]«ÈeÃi3VÆ7|Mc_æUô 9;\üyÞ
uüø.ÍðÝ"næ+®$°ªûLÎ) àFáûl¯ðsú
,JM}DÞÁs ( d X?££§Ú, J¤1ø<mÙt¤'mI% i
tl±hQÇ}OÄѾ£PõåïaM)uçæÎm3g¯ë2µõ²ÊÛ^µøþá' ½ 2T#¼ÅrVÃð on9²²°°pxxìØ3¥Î
\#ÆÞnT»Jî(% Ys2rtÃÐ
È)¹BÇe/address@hidden<9$;Ä>ÜYS¨*½¢.s/æ~(V
¹ªëÒ¿¡ðÞn¿:êjFQÎi½ËzSë'´:«Õ.q`Á±h$Y1°
f ¡ÇéYBHê9Nǧ:³gQ¿#tm!]
Á 30=·a?z>È«pOædJørË7÷¾$ðÈüWæjÆïWZöÐâ[X;"Øßß㢨ÂUkB©Ì\9'¨ÌàZc~nÌ\z *0Ó¦ì2WY¿ÚR>=ÖLáÅìOUÃháHIWò\òßÒZäºîküñ¯vâ°aOjñ5ü>address@hidden
ë{"ÞÔû_¾úÃ/ß*jI'D7 ä5>¸uñÛG; ooo?£*¬èP
;2/uf-û)address@hidden&~ª><ïLâ¯
ÃÕÕU×uw>âõû;W¸§Éã²þBþ5Ö§ìWÞпÉ4ùgòÄâ²E=EYÞ8 ÿyb¿<'õ&_SD'7C
÷îÃýû
U1»¦7òç*ºgõ4a}:??tÇàS{;Ç þ´+Móø!ÿµÂÏmm?¶¼Ôívͺ.1 ¶äÄL »ç&¡©'kâÂ7
#QirøâZn¢§S0,address@hidden&T/3OųêóG¢(ZYYéIyß¹ÍBÖ
ÒªÖKµ~<¯Õ¿Ã §ûoZZ]°ÒR·IÊdÃ$iα1Eåyð2þæÁÉØÀ»Á×/ÈÞxôs/È.|G«·¯\õç«}_/¸â{Vé¡û>ráÂû6q¿e7_º'¥ü¨v>paósa
»Ýد©h»ÉC¦±T&ß8Z:²´åb í"Sü¥Tu¡{EÖ+gºÏ§S²éºeL5>òV õÆZÖ3±µË_©ÐsøÂW-Ã0
ú !~ìâî/JÇí°þ(|«íP ¦ ÕÁ[n¸³ÿªMu×T¢"¥`)ø2!OLueA©LÃí´Í Bô îÝ'«ëØã -D y
Ögÿ¯þýÏ ö Õ.®[«=±Ò=G¸u áY$Å3Ç¢7½véÝÿõÂçÅÒjêñɦwÊ
!?éöüùþ3]áx^l´Ä É®àÝH9¥fÚÒ´ÛÔä«B¨¹®÷«(address@hidden:öQÆ·SÔ¢«4ªjS[ûÚÚZW©woï¾Ïv%èIýNà?ìx4ÃûA |ðïÐø·ÉWØeÏÇ$~D6SÙ^@)dqÊcÏ<Ý[m07cSÿìÿøE{Õ÷ßE¡Æp9
?±
k°dÈÎ%¶ÏùO/2³àT©{Ru,Z_«]lôÅRG<Ñqku¹#wó{ú&ï¿<ç¿ßí¦O¢ÉvÜ#ñ7Ýîm÷?G¿yxñ¢ët:¸\e±z8Ååb IMÎr7À\qù¯ }ò¹
v¹e\ZËQWmRqÉOcîkLãÅãf ×ô)&|
D¶3Hu.]Q){ZBÃÊ VñWâCÂtÃ
alpÅõÅ4ÉÚ·t9l\, MOR¨¨M2{1Ä
:«««Þpø··wßãtóÿo¨ð½^w%C]Ë'Ñ6ëçúw¸wmxB¤
CÌo$ 4ªUÝL«Èpö-6µB2
ZüÉPñç>ú½1 ÿY
N,$9¦k°~2P÷míî ;³DHôO{îÓ=¾¥kmSÔ³´+µgA<ò,¬tÅÆ;b±+\ôdý
address@hidden Ñ6éÖzsÈ Ú¢
2\çÕ7um²µcyNtÔ £¹éû§<ÁÏ2×FYq+ñë1¤¦? GºH7jÀñö~ðľS\91Î稨Zhæ'[Þ¦fÔYÏ?#fSÍ:ÞNÒpü8RßÚÝý¥½ÑÛNÄøÏÁÈ#z¿×µË£R2q¡ç´þ°ç yu÷Î%*#³Ï2¼ÌfyAÄÊð(©Çà (þO
address@hidden@«$NXNnÑÀÖC¥`´á(Ð: 6 c`è;Üa :/Ä9H{b¼hG=7úrc
ûîd£v- \aK
+õDµ?»§¾ãÚZ%e
Éð=%¥k)t´?Ö]üÑÐÿ÷Jµ¬ A0 -Ër]·&CÂdX/Ç°õH+\NsÆ Xå¢.õñx\$n) c|ߪ¡EÅ9~ £½öHþticÍnz3É1\VcX¶ÍÌ¡ï¿ä?
ëmsÀüñð Ë~½åÐl=©£ßX
+Öïê íÛ0 ÆDýiì¡,^!®-Tt(0ÉUË`n%
í ò <>úúv÷áð_D¸sZû¬È2 à<ë.p-Vÿ `ÄiYÌjZÐ ,?â]Ö/ÁX© ØdÞö
çÁ¾ ¡%¤ ¥Ü"±¤â=[0îô(Í2³Xª ÃyÛMôãNç-¬_Ôü
}êsÑø
ÑÈq8 $R÷=çG/ÕBF CqA÷¢µ¾¤-:"f ÑZqÓbÍ;ác»V¬}_Þ\ßÎ
ç Xßtÿ!Ë÷ØÝ Ñ.ëù?áx·Ê|:]izö9~Ù þà}K]GdAÈøß4&è±=uRÚ)WL Úeý
FÀ¡ê³O¾¾Ý½þpøë!ß"¬¢[¨ªÐ é7-r Xõ}nJs>
GðHl "Ï$å ÷ý÷B>ð,=à ¡õ|P¸ýÔúG³üGØ
H¼Bw¾ËúÛ*üã
ú,Âgm+î9 GN_;½<¯8y|&ìt_ÚÆ®45©X±ÕZc4zÄÏÛ{¤ «¤ ;Þ-Ò.K[ÎüñptâîNÇfÅÛédf
R¦'jæÄ&#Aj¯J"Ñ<
+ù¹á£ÏFgOý£¿ê[Ý ºã_v¬ \jVF{¯uõæ_çj¿fD
@2MÉ
ª³ÄFN)ÓìÅh À)§,÷!˹
ùÏtô{ }ø,ñöövZ#Ô, tÈZy95å*ËÌ[åy-ÄÝûßî¼Q:î4¤ ²]YÙ7
×ü?ìðÝ)'ÉBOnÒN-ÆôÀÜäHâ
+E.!ÎDG> address@hidden>
Û¤K§àu¢ð´ð¡Pß7åV5mòô!sÏnk£);ò<Efs¿Ñ«»¬äõǪ³ zH8osFGÛÓ?MÀEQê» îÅþ>!öC!ÁûÌ{ZI
¹8>Ëô$Ûm¶òÒ%¦TãñXêõz=!ýýàVgqÂ>Ö êO
þÚ®ç¬TkTÉvÍ
mYiÞªPñ0Ð
ìùzÏçƼ ð®QD
T¡¶Diµ< ½Áßä
B,K¦\. ðÁJ`Q Xµd>²4Ùµg¡ÚL^}9#ZÊòj>fÏ?ÎI!O¸¿¤2}`Äz\bÞb¾Àz;Ô:zÕm ÚMÚ+ÄÅUrZX˲d M P̬=ÃË¢ë}¿*
Ã8¦!eo#±º×rnÙ $:FrÙö(Sis¶ù"W¯*b<
+Þ Óù½Ð¶È³D . u ²1°ïG~8AÐáXBö#½3Â(lÌ´ç³øÒÆÚÒ ID!Ë
+9YÁjà w1nî#yÜrÅìy[z ~\Ewܨ,ÑVõeBG&æðú JTj\+Ib^)W_ת)^®àòôEý ïõ&×
¿¤Àûæ=Ö[¶³÷EÖ!·§&ÂPó¦Ò 8 ¸õà9úÈäæíiÄ>06 Hw@ ¸`À|Iç˳d32õ
{Bù°rí¯rWôÍQ²7Íf#È4:Fg±Haî,æ;"õ É×K÷<*d¯ÄÕBYveS¬²Bø5B~tÜûÇ5Ò¾ `k8,4RHk¡
fbK(3úJÉ(ÉÒc»DJ4cA)address@hidden@´^ n #±*l§$I ¥5 §àï¼F-îMUBª Í*kÆ=ߪ )pÖ¦0FÉfwÜÌcã/Ea
Z", dFién5ò9S%diÑAQÒ¾X'Xés&¼cÕ(õD4f>¯U:address@hidden&J'address@hidden
² Ãev5{ZÑBú`ÌIÆ%Ñ$ýkÄ
uÚvI°ámõtjåäú§-÷ýlëEǶ53ÐSÚf^Ò:×`Z×
x Ô^u3ð àvl]XqÄhWÚT6í9¿LPè³;ô u4XrÑVÃeÜ°%}áêf!5;IUUØÈCUê¢Ì ü11˶¬Ëèå²K4TQ
üñÛx3w1yªf s6JÑM^D1kÂÔp<GÆ µÆØ2bÉ à9
ÀÆßd6(×ðgãNsËi}1ßfða§;address@hidden X"s´áö\£Ì{¶É·Óju]Ij«nëg Í #n
ÊQ/Gµs¢ÒÑd.å8ßÌþÕUï>r62<ûâ\Â,ßfñ¯2´BJ¿bebPºH¡VTü"g+'
"ÝFÙʤw×pvÍ|«8©Ø%Ú
jFܪTÕ+Q¥WEßzÍ~ò?¥àÁc×®>l$(Íãª¨ß ÈLÔ,ûb]{OC¡ãZÅ(dpÕlÚ<©ï~óò |rÛ1,õâ
/Òræ
+hųË~
²xWÀôº!¦Ââ,®RnF»9ãAzµ-TjÙ:7~Ê\VkжV\¸*.{¬ÜàzàçèÔàZƫ˯UUxh®Vºf%ÉdµÐÌ-hæ.]S³¸\ý¬ÞË~¥
address@hidden&ÉóI´t/ë«43U¸ø
õãìCY k#¥³yÑ3&FÞ«\£s°öX®®Ù¬"ÃjbM¨26Í$_¥Û¹#Ñ,m´ V&©¬hlÔXM rvR©
{$WðËÌYe2µJ´I®îRúÀ¥L³·Êù'^ån°ë0WÃA)WÊRx¢f¦ÏÌs¬l¤ØÈFÖྫ) !~ݬ{B©ûó5 Ð,æ×äy&UW>â:¼LyÑ Î¯âË?-gg-×LV[EðâZ,ã2ÒT¥~ÎüL
²ç1©VSÏLÅ<,¹´Zh¦RµMú2Y¬Õ©êzÖT J.(q
L(ÔÄhÕÔ&ó%׿sÑVõÉuQ0§ïTÿHJÍ+sî ̵`JÕìÊøÝlX-psQ«+Pl17e yC JÎÌyÂSª3v¥:
5BÍØky±¾²s] ¶z³eų®mW¨ÞÐð$Uq®íg´Z? ,;h
¸´9_ËYJ@<cI[&Sa÷j`¦Òþ(5vÍÙonÂÅuEiSrÄ{¨ù7U «ÎÆsÕèt
-mjY<« `ÅNÁµäÜK\>¸±íÕ®óé¾ü
+cn`Qipè÷¬ÑC7ë6ÃUd·ã9Çqö^=§É V¯nÉRUÆ).¢l
^;Zê°«äYKS
l5ß¹¹t[¡0reCåæjÓ ¬-5t;address@hidden/éÂñ}¯ño裣CzS%¨4 :÷Pé²z´pÆNPºË0Ï\~eÊBî
ªÐÁP¤Æ(bV6~"Íb1¬ç\C£²ÿ`4C ãæ¬åÇDÜ ë ¸IDATÀÚDëc\xT°a¡éìÑ
&æáå}¦ZnHêÓ×r(V
í/hõ+ì¿rÛú!SÀÚ[7].Haþôé Ëüw3ª! 4{åxV¹Oð2¬(±_MÁmgÌc.ÉaF¹jÇ·{Åjg²ªØ9w/ #Ü
U©úÑ'YPDÍ £,à9 7õèÉÍÊп¢Ü_ïx²+ Ãú
[~ÒRÇÞÔIÍ×'@× y½kBÖ*ÿ j \5'yT
+aSh yW¦`=*ÈNG*g« º"v«µìË S\Èu1"\§åε2g
+¦¥³ÏY5s¦æiddtlN ¹P¯i#ÞJÖ_§D
Óëÿ\èÝ£wÑ°2ew:½õõ]ð%Ʒ⢴A Â0
+/N(½¡yUé
ͧ
|À²7¬öìÒü'u3É ÔùõxÜìyaæĬìí§1¢Tk¹+rFiÙ¢û|
·2T_sRpeæý28k`5°8ϾçÝJ 1UÙiMté
ÿ¶
+¾³¶" 7v·,°rL$ ÏçƤæ<ø|RÈ)
+Ã-IR±Ê8=ô×
°z-E¢5+$ÔlâË ¥Ëè
+iÅèhÎiáÙ¾bæ`¦ên4ÐLਿ;ÆF³f˹ljè5+ݨ #.ûÍ:#÷ìd¹S%Ù¡UÜîVGü*
address@hidden/©FÐ2ãP¶LLvå÷pÊT``*ÉAÅæ"]¾Jʨ°Ó5ªÜ¹áÁx."6öûÒwªÖ¦õr
³ÉQu jñ.ê S þípüÑ¥gq Æw,éª251â°-*:& ý´tÖúÞ#ú
ÇÌ(@åÎyöãùC\ã) Ï BEľ`_p 0b,4EZ&1N °
:)7
ZX¢O¦¬P>¯Æð,nõñ Y Ð<Dy¶uÅ6Mæqhª7Ͳã4a1Ù´P6`Å9yz +çå?#®dá5©Å°¨«r½aqiÐÀEÖ¿¦Ï Y´{½(è(ºq¡eX*aa!0J)®09 {½
øP©½ÙûÀñ \È=ÈhÛöqhôW5Î
address@hidden"@ ¯?æw
"º$ÀË$ú$ã`IU,,íxóF+àÜPT/&.Év&\9{ófwj^"&¥0P½ÆTRFaFV97ÐÙ©
ÏF7nô>³hR
®j"fÙîÁ
çµÞf~J«¬?mËovÜÁà¨mYéº[¶B§m!P¬æqÞBÖ¬µÖdd£0¼{åJ×# d Ôl\IyÎY²`7 3Î À¹1
Fò ðX "f°/
$B}Á c$I"`XDq¹OhuÂõ&TcD'address@hidden
+s)address@hidden:ÞlCWÓ:address@hidden'é:éýÅÀ6ë!
Á¿¦£¯KzÚ±ÏI)address@hidden,: NNL%ÐØ A3 4Î1$!¬QoúO:ƦQYzz( ¢
,IÆddÒ¾Lj `Np 1N¤G4 YXHºªÇÿÝ
¸p¬(k³éEêziãæfÎ67Cr5ÆMólUúÒ1\Ç;c*½MJ бS$`õ%æY_bÞÞeÞe¾
EDtQC!ö¥IiÇ&
)¥ëºñN¿RX_Å×}KÛ-`lXs. ûû{e 9r$ Ø¿æ]ååèMÿ¼¬T
õ¯a; !ãÂ(^E¹à»af1~fÈà¾V$Æã/M address@hidden&¬yÄ w`íYE ý ið ²Ò
~ÈV Mî·FÂ1lh& ``õÖ&,d¯è¦ +9FÕØOr-ÅKÄ»0sÖ Hĺ<
&hfvµÞkÂù ¼ÓÇÃ=E¶¶ /1GÌûDÛ1
áØuömYdI)-ËRHiÅ-/s¬ t Û±ívÕ_+jë%1,˲\×[ZZvaö$·Äõ{ G
+»Â©¹qS7ÐPcs4 # :~d¶À
1)F¶Ç¯_a¬2ätË#á+ úi·Arµ#( F¸d1~$XG%MÕ(3ÕÔXèhb\sªç±?1W M]íô
r%l
O$]Þèó"ÀÍöt§râRÿ³_}z]x eF#!çyaF£ÅÅE K2\\,4±²aM^.9ºµaÍmÃJß{=³¦xÏd Ço<µ£y5-&
Ã+cÙ(ô¬¿y¾Óó<dS_.QÕÖ³FÊÄn ÛõÈð¢(î5üåá)nuV PÖô¬ôO¥¢uWµE¦Và²GÈ
ÁÌì ÌlYV©Tôôè7T;\MÒµ 5ÙmÛ ÇÌ EQlºM´Î¢#ãL´2%Ô6«ÄUU<¨|H
æ¡;£ëÚÁlåª%6¢9nU«bÖav» ¢Ô¯YÅÕ¥Ç&GR§Ú
¬R°V Ì ét:é&EÑGÕf+W¬zð( 0±m; 'íh3-é+>§VåºTòÒÑ¢Ó>Àâ6¬âñ
ÞØê\Õ§p/!P½^ïÒ¥ ThFþe{Êë1U ëþ
½ZeêvU Ê ¸R´J¯[£íH¶rÕmæG]'uÄ!µ½ÞÑ$5-kÃ-eúà ´ÒZßÐ ZUX¨ õªwãÃZëWF×uÛM
«PN/D±s0íDdÛNC°]Å0ÅsÆN_\bñ£Ñè¡ëh]e*aÊQçhÍÀ address@hidden
+e¥ðáÒ|õÉ/¬ÑÝË-(,45ÔÃcY"ÿÕGZ·k+W§Üµ¤ä3>¬i¿mÛÅm¨iÍI
+¼y\k}ßâpµÓ>:
¹Ðoï
Ûf \rï*VÅp»1 Ù¶mYVús§
à7EV«»de¶
«Æá Ú¼V®VéÛ¸wq¬ÔD°m[Jér£ryl*[eÙ¿£ð+îR
XÅQI² =~`µ
hhåjW¯Z©`u¤{
`.4UÊ°ë]ÿh«V©± 30ët§
hhå*[lsÈ°Qa®ËebSe nêø6 ¡
+°
+8+VfJ© XÚ1måê¬ElXóÜÁ¤\X~#OkÌ«&_GÚg%(R·¯µEj«¦
E)Ãê¨á;N¶Z¹Êåh2zAå)s¾ýüPe°-ν¥¢ðµÖØR"¥Í¸f§kýرýW®´ØÊU.DxýêX)
+y
address@hidden>òÑL_kOʽ÷ßÖnå×kKe[ût)¥^³ ¬zíÀתMh¬RUx{wô¯î=¼±
¿jåÚ» ã!v°ø2!UY¾Â0|Ûñ6{¤°b\P 3ÑZ+uÞ¹0zE?z˺w'[iåj÷ Ƶù
FaÍCÞ+±«cmrn=`ÝÕ;x×Ú[ÐSûd<|ëR$=¡oêG ïYÑ×/``·#Öʵ(o>~á©ÈÎép¾úËUÅÌöîXj«°Þ~½þ©&.¿Hc¤0á®´rÉó¯?éagTÚmÚìEFMxV¥>address@hidden|ðÎhA T÷4_ðLÀ*E«( Ú/»íx·ÕJ+/Mn àC· ê`Tîl`fFcå
+îëîüÔMm¼è*a+´R*?s³R|ñÓgíÇöÝÈu 'îÑi0,³ÎÙº².&3GQxʾãúáß¹U¯·
Ï-`µÒÊY-ïü³·[~ðøÎÁ ÿý¬·¥;®ëCÔ÷úÔQØCpÌ
îè¬ë·Ð]´¡W-`µÒÊGàxÇ»üÑÏ>ÿâá#ÏÙ/H µ° address@hidden
m«V^v!àhïºßqCà« ÔP<Õ ¡Ð0I#ºeÀ v R-`µÒÊ÷I\
W6ül²ð¤õ¶ÒJ+-`µÒJ+´ÕJ+´ÕJ+´ÒV+´ÒJ X´Òʵ&ÖO<
¸ñu ÚPÛVZiå/ppã Ü¿xÜúêW¿úÈ#<üðÃãßØL+´òS yä×éOèºë® àþûï¿ýöÛÛAi¥VþJ÷±' üâWÞ$íÿ»ö;g Æ IEND®B`
+
+ The above is useful for playing Flash files downloaded to your local
+system. It is also possible to play Flash files directly from the web.
+To do so, use the `-u' option along with the URL of the desired file.
+
+
+ gnash -u http://example.domain.com/flashfile.swf
+
+Note that this will not work with every website; some embedded Flash
+files are difficult to play.
+
+* Menu:
+
+* Gnash Command Line Options::
+* Gnash Interactive Control Keys::
+* User Configuration File::
+
+
+File: gnash_user.info, Node: Gnash Command Line Options, Next: Gnash
Interactive Control Keys, Up: Using Gnash
+
+2.1 Gnash Command Line Options
+==============================
+
+No options are required for Gnash's default behavior. However, there
+are many options that can be used to that behavior.
+
+
+ gnash <options>
+ filename.swf
+
+
+ *Gnash Command Line Options*
+
+Option Function
+`-h' Print usage information.
+`-s factor' Scale the movie up/down by the
+ specified factor.
+`-c' Produce a core file instead of
+ letting SDL trap it. By default,
+ SDL traps all signals, but
+ sometimes a core file is desired to
+ assist with debugging.
+`-d num' Number of milliseconds to delay in
+ main loop. The main loop polls
+ continuously with a delay to adjust
+ how long _Gnash_ sleeps between
+ iterations of the loop. The smaller
+ the number, the higher the CPU load
+ gets, and of course, the more
+ iterations of the main command loop.
+`-p' Run full speed (no sleep) and log
+ frame rate.
+`-a' Enable Actionscript debugging.
+`-v' Be verbose; i.e. print debug
+ messages to stdout.
+`-va' Be verbose about movie Actions.
+`-vp' Be verbose about parsing the
+ movie. Warning: this can generate a
+ lot of text, and can affect the
+ performance of the movie you are
+ playing.
+`-ml bias' Specify the texture LOD bias
+ (float, default is -1) This affects
+ the fuzziness of small objects,
+ especially small text.
+`-w' Write a debug log called
+ gnash-dbg.log. This will record of
+ all the debug messages whether they
+ are printed to the screen or not.
+`-j' Specify the width of the window.
+ This is mostly used only by the
+ plugin.
+`-k' Specify the height of the window.
+ This is mostly used only by the
+ plugin.
+`-1' Play once; exit when/if movie
+ reaches the last frame. This is the
+ default.
+`-r [0|1|2|3]' ? [undisplayable block object]
+`-t sec' Timeout and exit after the
+ specified number of seconds. This
+ is useful for movies which repeat
+ themselves.
+`-g' Start Gnash with a Flash debugger
+ console so one can set break points
+ or watchpoints.
+`-x id' This specifies the X11 window ID
+ to display in; this is mainly used
+ by plugins.
+`-b bits' Bit depth of output window (for
+ example, 16 or 32). Appropriate bit
+ depths depend on the renderer and
+ GUI library used.
+`-u url' Set the _url member of the root
+ movie. This is useful when you
+ download a movie and play it from a
+ different location. See also the -U
+ switch.
+`-U baseurl' Set base URL for this run. URLs
+ are resolved relative to this base.
+ If omitted defaults to the _url
+ member of the top-level movie (see
+ the -u switch).
+`-P entrymeter' Parameters are given in
+ ParamName=Value syntax and are
+ mostly useful to the plugin to
+ honour EMBED tags attributes or
+ explicit OBJECT PARAM tags. A
+ common use for -P is to provide
+ FlashVars (ie: -P
+ "FlashVars=home=http://www.gnu.org";).
+`-F filedescriptor' Use the given filedescriptor to
+ send requests to the host
+ application. This is currently only
+ used for GETURL requests. The
+ protocol is not documented yet, and
+ also needs improvement. Primary
+ use for this switch is for the
+ NPAPI plugin to properly support
+ javascript and target windows in
+ geturl requests.
+
+
+File: gnash_user.info, Node: Gnash Interactive Control Keys, Next: User
Configuration File, Prev: Gnash Command Line Options, Up: Using Gnash
+
+2.2 Gnash Interactive Control Keys
+==================================
+
+While a movie is playing, there are several control keys. These can be
+used to step through frames, pause the playing, and control other
+actions.
+
+
+
+ *Gnash Interactive Control Keys*
+
+Key Combination Function
+`CTRL-Q' Quit/Exit.
+`CTRL-W' Quit/Exit.
+`ESC' Quit/Exit.
+`CTRL-P' Toggle Pause.
+`CTRL-R ' Restart the movie.
+`CTRL-[ or kp-' Step back one frame.
+`CTRL-] or kp+' Step forward one frame.
+`CTRL-L' Force immediate redraw.
+`CTRL-T' Debug. Test the set_variable()
+ function.
+`CTRL-G' Debug. Test the get_variable()
+ function.
+`CTRL-M' Debug. Test the call_method()
+ function.
+`CTRL-B' Toggle the background color.
+
+
+File: gnash_user.info, Node: User Configuration File, Prev: Gnash
Interactive Control Keys, Up: Using Gnash
+
+2.3 User Configuration File
+===========================
+
+Individual user preferences may be set by editing variables with the
+`.gnashrc' file:
+
+
+ ~/.gnashrc
+
+ Each line must begin with an action: either _set_ or, in the case of
+lists, also _append_.
+
+ The values in this configuration file apply only to an individual
+user, and become the default settings of the standalone player and the
+plugin. Note that any command line options take precedence over
+`.gnashrc' settings.
+
+ The variables in the `.gnashrc' file support three types of
+arguments: on/off, numeric values, or in the case of the whitelist and
+blacklist, a list of hostnames as ASCII text.
+
+
+
+ *User Configuration Variables*
+
+Variable Value Function
+localdomain on/off This value can be set
+ to either _on_ or
+ _off_, and controls the
+ loading of external
+ Flash movies over a
+ network. This option
+ tells Gnash to only
+ load Flash movies from
+ the existing domain.
+localhost on/off This value can be set
+ to either _on_ or
+ _off_, and controls the
+ loading of external
+ Flash movies over a
+ network. This is a
+ stricter version of the
+ _localdomain_ setting as
+ this allows the loading
+ of Flash movies to the
+ same host that is
+ running Gnash.
+whitelist hostnames This is a list of
+ hostnames separated by
+ spaces, or _off_ to
+ disable the whitelist.
+ The hostname must be
+ given without a
+ protocol (http://,
+ https://). If this list
+ is populated, Gnash
+ will only load external
+ Flash movies from the
+ specified hosts. The
+ whitelist takes
+ precedence over the
+ blacklist. Because
+ several files can be
+ parsed in succession,
+ each file can override
+ or add to lists in
+ other files. Use _set_
+ to override all other
+ lists or _append_ to
+ add your blacklisted
+ hosts to lists in
+ previously parsed files.
+blacklist hostnames This is a list of
+ hostnames separated by
+ spaces, or _off_ to
+ disable the blacklist.
+ The hostname must be
+ given without a
+ protocol (http://,
+ https://). External
+ flash movies from these
+ domains are never
+ allowed to load. If
+ whitelist is present
+ and not empty,
+ blacklist is not used.
+ Because several files
+ can be parsed in
+ succession, each file
+ can override or add to
+ lists in other files.
+ Use _set_ to override
+ all other lists or
+ _append_ to add your
+ blacklisted hosts to
+ lists in previously
+ parsed files.
+localSandboxPath dirs This is a list of
+ directories separated
+ by spaces. Only
+ resources from these
+ directories and from
+ the directory portion
+ of movie filename (if
+ loaded from filesystem)
+ are allowed to load.
+ Because several files
+ can be parsed in
+ succession, each file
+ can override or add to
+ lists in other files.
+ Use _set_ to override
+ all other lists or
+ _append_ to add new
+ sandboxes. Note that
+ there's currently no
+ way to *drop* the
+ directory of base dir
+ from the list of
+ allowed local sandboxes.
+delay Number Gnash uses a
+ timer-based event
+ mechanism to advance
+ frames at a steady
+ rate. This option
+ overrides the default
+ setting in Gnash to
+ play a movie slower or
+ faster.
+verbosity Number This is a numeric value
+ which defines the
+ default level of
+ verbosity from the
+ player.
+MalformedSWFVerbosity on/off This value can be set
+ to either _on_ or
+ _off_, and controls
+ whether malformed SWF
+ errors should be
+ printed. If set to
+ true, verbosity level
+ is automatically
+ incremented. Set
+ `verbosity' to 0
+ afterwards to hush.
+ASCodingErrorsVerbosity on/off This value can be set
+ to either _on_ or
+ _off_, and controls
+ whether ActionScript
+ coding errors should be
+ printed. If set to
+ true, verbosity level is
+ automatically
+ incremented. Set
+ `verbosity' to 0
+ afterwards to hush.
+debuglog Absolute path This is the full path
+ and name of debug
+ logfile as produced by
+ Gnash. On systems with
+ a UNIX-type shell, a
+ tilde prefix (~) will
+ be expanded as by Posix
+ shell requirements (see
+
http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_06_01).
+writelog on/off This value can be set
+ to either _on_ or
+ _off_, and controls
+ whether a debug log is
+ always written by
+ Gnash, or not at all.
+sound on/off This value can be set
+ to either _on_ or
+ _off_, and controls the
+ sound of the standalone
+ player. By default
+ Gnash enables playing
+ the sound in any Flash
+ movie.
+pluginsound on/off This value can be set
+ to either _on_ or
+ _off_, and controls the
+ sound of the player
+ when running as a
+ browser plugin. By
+ default, sound is
+ enabled when using
+ Gnash as a browser
+ plugin.
+EnableExtensions on/off Set to _on_ to enable
+ extensions. This option
+ is _off_ by default
+StartStopped on/off Set to _on_ to have the
+ GUI start in "stop"
+ mode. This is useful in
+ particular for the
+ plugin, so you have to
+ explicitly start any
+ movie on a webpage.
+ This option is _off_ by
+ default.
+flashVersionString string Set the string returned
+ by $version and
+ System.capabilities.version.
+ Useful to get around
+ some flash version
+ detection movies. Note
+ that the version
+ advertised by the
+ plugin is NOT affected
+ by this setting,
+ instead you need to set
+ the GNASH_FLASH_VERSION
+ environment variable for
+ the latter (which
+ doesn't affect $version
+ and
+ System.capabilities.version).
+flashSystemOS string The string that Gnash
+ should return for
+ System.capabilities.OS
+flashSystemManufacturer string The string that Gnash
+ should return for
+
System.capabilities.manufacturer
+StreamsTimeout double Set the number of
+ seconds after which
+ streams download time
+ out. Note that timeouts
+ only occurs after the
+ given number of seconds
+ passed w/out anything
+ was received.
+insecureSSL on/off If set to _on_, no
+ verification of SSL
+ connections is
+ performed. This means
+ that, although the
+ connection is
+ encrypted, the server
+ certificate could be
+ invalid, may not belong
+ to the host, or both.
+ Equivalent to curl
+ -insecure. By default,
+ this option is _off_ and
+ connections will fail
+ when a host cannot be
+ verified.
+SOLsafedir Absolute path The full path to a
+ directory where Gnash
+ should store Shared
+ Object files ("flash
+ cookies") if they are
+ enabled.
+SOLreadonly on/off If set to _on_, Gnash
+ will not write Shared
+ Object files.
+URLOpenerFormat string Set the format of an
+ url opener command. The
+ %u label would be
+ substituted by the
+ actual url to be opened.
+ Examples: ?
+ [undisplayable block
+ object]
+
+ The following example `.gnashrc' file allows a user to only play
+Flash files saved locally to the machine on which Gnash is running. It
+also specifically forbids content from doubleclick.com and
+mochibot.com. Gnash's error output is set to be fairly verbose, with
+the debug log placed in a location convenient for the user. Finally,
+sound is turned on for both the standalone player and the plugin.
+
+
+
+ #
+ # Gnash client options
+ #
+
+ # Only access remote content from our local domain
+ set localdomain on
+
+ # Only access content from our local host
+ set localhost on
+
+ # These sites are OK
+ # uncommenting the following line will allow load of external
+ # movies *only* from the specified hosts.
+ #set whitelist www.doonesbury.com www.cnn.com www.9news.com
+
+ # Disable whitelists set in any other gnashrc files, because
+ # these could override our blacklist.
+ set whitelist off
+
+ # Don't access content from these sites
+ set blacklist www.doubleclick.com mochibot.com
+
+ # The delay between timer interrupts
+ set delay 50
+
+ # The default verbosity level
+ set verbosity 1
+
+ # Be verbose about malformed SWF
+ set MalformedSWFVerbosity true
+
+ # Be verbose about AS coding errors
+ set ASCodingErrorsVerbosity true
+
+ # The full path to the debug log
+ set debuglog ~/gnash-dbg.log
+
+ # Write a debug log to disk
+ set writelog on
+
+ # Enable or Disable sound for the standalone player
+ set sound on
+
+ # Enable or Disable sound for the standalone player
+ set pluginsound on
+
+ # Make sure SSL connections are always verified
+ set insecureSSL off
+
+ # Use firefox to open urls
+ set urlOpenerFormat firefox -remote 'openurl(%u)'
+
+
+File: gnash_user.info, Node: Installing and Configuring Gnash, Next:
Reporting Bugs, Prev: Using Gnash, Up: Top
+
+3 Installing and Configuring Gnash
+**********************************
+
+There are two ways of installing Gnash: [Cross reference to
+non-existant ID "packagemanager"] or installing from source (*note
+Getting the Source::).
+
+* Menu:
+
+* Requirements::
+* Downloading Gnash::
+
+
+File: gnash_user.info, Node: Requirements, Next: Downloading Gnash, Up:
Installing and Configuring Gnash
+
+3.1 Requirements
+================
+
+Before downloading and installing Gnash, check that your hardware and
+software meet the following requirements.
+
+* Menu:
+
+* Hardware Requirements::
+* Software Requirements::
+
+
+File: gnash_user.info, Node: Hardware Requirements, Next: Software
Requirements, Up: Requirements
+
+3.1.1 Hardware Requirements
+---------------------------
+
+One of the goals of Gnash is to make it portable enough to install on
+small devices. As a result, the hardware requirements are minimal.
+Gnash has even run on an ARM9 at 200 MHz with 32 MB of RAM! (It ran
+without video support in this case.) While firm minimums have not been
+established, Gnash has been shown to run successfully with the
+following:
+
+ * 336 MHz processor
+
+ * 128 MB RAM
+
+ * Video -- Gnash will run on anything from a raw frame buffer up to
+ an OpenGL-supporting graphics card.
+
+ The following table provides a list of the Operating System/CPU
+combinations on which Gnash has been shown to run.
+
+
+
+ *Build Matrix*
+
+Operating System Processor
+OpenBSD, FreeBSD, NetBSD Alpha AXP, AMD64, i386, Itanium,
+ PC-98, PowerPC, SPARC64
+Debian Alpha AXP, AMD64, ARM, hppa, i386,
+ Itanium, MIPS, PowerPC, IBM zSeries
+ (s390), SPARC
+Fedora x86-32, x86-64, Geode GX, Geode LX
+Gentoo AMD64, PowerPC, SPARC, x86
+Maemo 2.1 i385, ARMv5t
+Scratchbox i386, ARMv5t
+Access Linux Platform i386, ARMv5t
+Mandriva i386, MIPS
+Open Embedded, OpenMoko, Poky ARM
+YellowDog Linux 6 PowerPC, PS3
+OpenSuSE 10 i586, x86-64
+Red Hat Enterprise, CentOS x86-32, x86-64
+Ubuntu x86-64, x86-32, PowerPC, UltraSPARC
+Haiku i386
+Syllable i386
+Irix 6.5 MIPS R10K
+Darwin (MacOS X) PowerPC and x86-32
+Windows XP, Windows Vista x86-32
+
+
+File: gnash_user.info, Node: Software Requirements, Prev: Hardware
Requirements, Up: Requirements
+
+3.1.2 Software Requirements
+---------------------------
+
+The 0.8.2 release of Gnash has been designed to run on UNIX/Linux
+variants, and has been run on most of the free ones. However, Gnash
+has successfully run on Windows, Darwin (Mac OS X), Irix, Solaris,
+BeOs, OS/2, and Haiku. Gnash has also run on the following 64-bit
+systems: PowerPC, Itanium, UltraSparc, and AMD64. For now, it is
+important to be sure that the following code, testing, and
+documentation dependencies are met before installing Gnash. If you
+will be downloading Gnash with a package manager, these dependencies
+may be solved by the package manager. Otherwise, you must first verify
+that each of these dependencies are installed on the target system.
+
+
+File: gnash_user.info, Node: Downloading Gnash, Prev: Requirements, Up:
Installing and Configuring Gnash
+
+3.2 Downloading Gnash
+=====================
+
+There are two ways to download Gnash: using a package manager or by
+downloading the source code and building it on your system. If
+possible, it is advisable to use a package manager to download Gnash,
+as it will resolve dependencies for you. However, if you want the very
+latest features, or a Gnash package is not available for your operating
+system, it is better to download the source code and build Gnash
+locally.
+
+* Menu:
+
+* Getting the Source::
+* Getting Codec Support::
+
+
+File: gnash_user.info, Node: Getting the Source, Next: Getting Codec
Support, Up: Downloading Gnash
+
+3.2.1 Getting the Source
+------------------------
+
+Gnash is available as a release tarball (*note Releases::), a
+development checkout (*note Repository::), or a development snapshot
+(*note Snapshot::).
+
+* Menu:
+
+* Releases::
+* Snapshot::
+* Repository::
+
+
+File: gnash_user.info, Node: Releases, Next: Snapshot, Up: Getting the
Source
+
+3.2.1.1 Releases
+................
+
+The source can be acquired from a GNU FTP Mirror
+(http://www.gnu.org/prep/ftp.html). The release version is intended to
+be stable, and is probably your best choice if the release took place
+recently. If you need features or fixes which were introduced after
+the release, consider a CVS checkout (*note Repository::) or the daily
+snapshot (*note Snapshot::).
+
+ To download, select a mirror near you, then choose the `gnash'
+directory.
+
+
+File: gnash_user.info, Node: Snapshot, Next: Repository, Prev: Releases,
Up: Getting the Source
+
+3.2.1.2 Snapshot
+................
+
+The daily development snapshot can be downloaded from
+http://www.gnashdev.org/dev_snapshots/
+(http://www.gnashdev.org/dev_snapshots/). This is the best option if
+you need changes which were introduced after the last release (*note
+Releases::) of Gnash, but are unable to download directly from the
+repository. (*note Repository::)
+
+
+File: gnash_user.info, Node: Repository, Prev: Snapshot, Up: Getting the
Source
+
+3.2.1.3 Repository
+..................
+
+The latest development sources are available via anonymous CVS. This
+is recommended if you need features or bug fixes which were introduced
+after the last release (*note Releases::). Look at the daily snapshot
+(*note Snapshot::) if you experience difficulty accessing the
+repository.
+
+ To download via anonymous CVS, first set the environment variable
+`CVS_RSH' to `ssh', then check out the source code. The example below
+uses the GNU Bourne-Again shell (bash):
+
+
+ export CVS_RSH="ssh"
+ cvs -z3 -d:pserver:address@hidden:/sources/gnash co gnash
+
+ It is also possible to browse the repository
+`http://cvs.savannah.gnu.org/viewcvs/gnash/?root=gnash' on the web.
+
+
+File: gnash_user.info, Node: Getting Codec Support, Prev: Getting the
Source, Up: Downloading Gnash
+
+3.2.2 Getting Codec Support
+---------------------------
+
+Gnash requires codec support to handle audio and video correctly. Some
+platforms like Ubuntu or Fedora under the GNOME desktop will
+automatically notify the user that the proper codecs aren't installed,
+and pop up a dialog box to let the user download the codecs Gnash needs
+to make site like YouTube work correctly. If you have installed Gnash on
+any other platform, and video doesn't work, it's highly likely you need
+to install the proper codecs. For most platforms, this is the
+Gstreamer-ffmpeg plugin, available from your distributions repository.
+
+
+File: gnash_user.info, Node: Reporting Bugs, Next: Glossary, Prev:
Installing and Configuring Gnash, Up: Top
+
+4 Reporting Bugs
+****************
+
+The Gnash project relies on the community of Gnash users to test 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
+`http://savannah.gnu.org' to manage these reports.
+
+ 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 critical details, like
+the Operating System you are on, it's version, and any relevant error
+messages from Gnash that you get.
+
+* Menu:
+
+* Get a Fresh Binary Package::
+* Determine if the bug was previously reported::
+* Review the bug writing guidelines::
+* Filing a bug report::
+
+
+File: gnash_user.info, Node: Get a Fresh Binary Package, Next: Determine if
the bug was previously reported, Up: Reporting Bugs
+
+4.1 Get a Fresh Binary Package
+==============================
+
+For starters, it's a good idea to obtain a copy of the latest snapshot.
+Although Gnash is primarily released as source, the 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.
+
+ You can get a fresh binary package of Gnash, as well as recent
+source packages from http://www.getgnash.org/packages
+(http://www.getgnash.org/packages/).
+
+
+File: gnash_user.info, Node: Determine if the bug was previously reported,
Next: Review the bug writing guidelines, Prev: Get a Fresh Binary Package,
Up: Reporting Bugs
+
+4.2 Determine if the bug was previously reported
+================================================
+
+Search the Gnash bug tracker
+(https://savannah.gnu.org/bugs/?group=gnash) to see if the bug has
+already been identified.
+
+ If the issue has already been reported, you should not file a bug
+report. However, you may add some additional information to the ticket
+if you feel that it will be beneficial to the developers. For
+instance, if someone reported a memory issue on Ubuntu GNU/Linux, and
+you noticed the same problem on OpenBSD, your stacktrace would be
+useful. Conversely, adding a "me too" note to a feature request is not
+helpful.
+
+
+File: gnash_user.info, Node: Review the bug writing guidelines, Next: Filing
a bug report, Prev: Determine if the bug was previously reported, Up:
Reporting Bugs
+
+4.3 Review the bug writing guidelines
+=====================================
+
+A good bug report should be precise, explicit, and discrete. This
+means that there should be just one bug per ticket, and that a ticket
+should contain the following information:
+
+ * An overview of the problem;
+
+ * Instructions on how to replicate the bug;
+
+ * A description of what happened when you performed the steps to
+ replicate the bug, and what you expected to happen;
+
+ * Your system information: operating system name and version, as
+ well as the versions of major development dependencies;
+
+ * The release number or checkout timestamp for the version of Gnash
+ where you observe the problem;
+
+ * The file `config.log', which should be attached as a file;
+
+ * A descriptive title.
+
+ Include any additional information that you feel might be useful to
+the developers.
+
+
+File: gnash_user.info, Node: Filing a bug report, Prev: Review the bug
writing guidelines, Up: Reporting Bugs
+
+4.4 Filing a bug report
+=======================
+
+After following the steps described above, you can file a bug report at
+`https://savannah.gnu.org/bugs/?group=gnash'.
+
+
+File: gnash_user.info, Node: Glossary, Next: Authors, Prev: Reporting Bugs,
Up: Top
+
+5 Glossary
+**********
+
+
+
+A
+=
+
+ActionScript
+ _ActionScript_, or "AS", is the scripting language for _Flash_
+ applications. It is compiled to bytecode, which is a subset of the
+ _SWF_ format.
+
+AGG
+ AGG is the AntiGrain 2D graphics library, which can be used as a
+ renderer in Gnash. It is faster than OpenGL on systems without
+ hardware graphics acceleration. As of Gnash version 0.8.1 it is
+ the more feature complete renderer.
+
+AMF
+ _AMF_ is the object format used by _Flash_ for shared objects and
+ streaming video.
+
+as_environment
+ In Gnash terms, the as_environment, or ActionScript execution
+ environment, contains a stack of objects, characters and values
+ which are in the immediate environment of the current fn_call.
+ Please refer to the Gnash ActionScript manual for more information.
+
+
+C
+=
+
+Cairo
+ Cairo is a 2D graphics library with support for multiple output
+ devices. Can be used as a renderer in Gnash. A useful feature of
+ Cairo is that it will automatically use graphic card acceleration
+ when available. Cairo has an experimental OpenGL backend.
+
+
+D
+=
+
+DejaGNU
+ DejaGNU is a framework for testing software.
+
+DocBook
+ _DocBook_ is a markup language for presentation-neutral
+ documentation, such as manuals.
+
+Doxygen
+ _Doxygen_ is a documentation generator for for multiple languages
+ which uses comments in the source code to create stand-alone
+ documentation.
+
+Drupal
+ Drupal is a CMS/blog system used for the main Gnash website.
+
+
+E
+=
+
+extensions
+ A Gnash _extension_ is a plugin (not a browser plugin) which
+ implements additional functionality beyond what is covered by
+ _Flash_ specification. These are shared libraries which are loaded
+ at runtime.
+
+
+F
+=
+
+ffmpeg
+ ffmpeg is an audio and video decoding library which can be used by
+ Gnash to decode mp3, FLV and other media types.
+
+Flash
+ The term _Flash_ is used to describe both the Adobe IDE for
+ creating _SWF_ files, and the technology itself. Flash is a
+ trademarked term of Adobe's, we prfer to use SWF to refer to the
+ files themselves, as well as the format, instead of flash(tm).
+
+FLV
+ FLV is a proprietary file format used to deliver Flash video. It
+ is used by YouTube, among others.
+
+FLTK
+ FLTK, or the 'Fast Light ToolKit', is a portable GUI library which
+ is intended to replace the SDL GUI. Currently in Gnash, FLTK may
+ be used with the Cairo and AGG renderers. FLTK has an experimental
+ Cairo backend.
+
+FrameBuffer
+ In Gnash, this is a GUI library that outputs directly to the Linux
+ Frame Buffer and so does not need a window system to run. This
+ makes it particularly suitable for use on small devices.
+
+
+G
+=
+
+Gnash
+ Gnash is the GNU Flash movie player.
+
+Gstreamer
+ Gstreamer is a multimedia framework which Gnash can use for
+ decoding audio and video. Gstreamer itself cannot decode anything,
+ so it needs some appropriate decoding-plugins to do the work for
+ it. Remember to install them if you use Gnash with Gstreamer
+ enabled. To get the best out of Gnashs gstreamer-parts, it is
+ recommended to install the gst-plugins-good, gst-plugins-good and
+ gst-ffmpeg plugins packages.
+
+GTK
+ GTK is the GIMP Toolkit GUI library. It is one of the GUI options
+ for Gnash. As of Gnash 0.7.2, this is the more performant and
+ feature-rich choice. GTK uses Cairo internally.
+
+GUI
+ A _GUI_ is a "graphical user interface". In Gnash, the GUI library
+ provides a wrapper for mouse and keyboard events, menus, windowing
+ (where available) and a drawing area. You must choose a GUI
+ library during the configuration stage of building Gnash.
+
+
+K
+=
+
+Klash
+ _Klash_ was the name given to the stand-alone instance of Gnash
+ which used the KDE GUI. It has been replaced with an
+ implementation using Qt. Some documentation may incorrectly refer
+ to the Konqueror plugin as _Klash_. The plugin was renamed
+ _Kpart_.
+
+Kpart
+ _Kpart_ is a plugin for Konqueror which is enabled with the [Cross
+ reference to non-existant ID "features"] _-enable-klash_.
+
+
+L
+=
+
+libmad
+ libmad is a mp3-decoding library, which can be used by Gnash's
+ sound handler to decode mp3-audio.
+
+
+M
+=
+
+Mesa
+ _Mesa_ is the free software OpenGL implementation. Gnash
+ documentation will sometimes use the glossterms 'OpenGL' and
+ 'Mesa' interchangeably.
+
+Ming
+ Ming is a C library for generating SWF ("Flash") format movies,
+ plus a set of wrappers for using the library. It is used by the
+ Gnash project for generating testcases.
+
+
+N
+=
+
+Nellymoser
+ Nellymoser is a proprietary audio codec introduced in the Flash
+ Player in version 6. For more information, please see Wikipedia.
+
+
+O
+=
+
+OpenGL
+ OpenGL (Open Graphics Library) is a standard specification
+ defining a cross-language cross-platform API for writing
+ applications that produce 3D and 2D computer graphics. Accelerated
+ graphic cards usually provide OpenGL at the hardware level. Please
+ refer to Wikipedia for availability of free software OpenGL
+ hardware drivers. A free software implementation of the API is
+ available (Mesa). OpenGL can be used as a renderer in Gnash.
+
+ORM
+ ORM is a system for ensuring the rights of the creator over a
+ piece of digital content. It is more passive than DRM.
+
+
+P
+=
+
+plugin
+ The glossterm _plugin_ is used in Gnash to refer to both any Gnash
+ browser plugin, as well as the Firefox plugin specifically. The
+ Konqueror plugin is called _Kpart_. Sometimes, the term is used in
+ an even more generic sense to refer to _extensions_.
+
+
+Q
+=
+
+Qt
+ Qt is a GUI library which is used by KDE. The plugin version of
+ Gnash using this GUI library is Kpart. The standalone version is
+ enabled with -enable-gui=kde.
+
+
+R
+=
+
+renderer
+ The _renderer_ is the subsystem of Gnash which renders content.
+ Only one renderer may be used; it is selected at configuration
+ time if building from source.
+
+ Available renderers are: AGG, OpenGL, and Cairo. In terms of
+ feature completeness, AGG comes first; followed by OpenGL and then
+ Cairo. In most cases, AGG is preferred for performance, except
+ cases where it is beneficial to have hardware accelerated
+ rendering (for example, when you have a very slow CPU but a very
+ fast graphics card). In this case OpenGL should be used.
+
+RTMP
+ RTMP is the Real Time Messaging Protocol primarily used with to
+ stream audio and video over the internet to the Flash Player
+ client.
+
+RTMPT
+ RTMPT is basically a HTTP wrapper around the RTMP protocol that is
+ sent using POST requests from the client to the server. Because of
+ the non-persistent nature of HTTP connections, RTMPT requires the
+ clients to poll for updates periodically in order to get notified
+ about events that are generated by the server or other clients.
+
+RTMPTS
+ RTMPTS is the same as RTMPT, but instead of being a HTTP wrapper,
+ it is a HTTP SSL wrapper (HTTP secure connection).
+
+
+S
+=
+
+SDL
+ Simple DirectMedia Layer is a cross-platform multimedia free
+ software library that creates an abstraction over various
+ platforms' graphics, sound, and input APIs. Gnash can use it as a
+ GUI and/or as a sound handler. Note that the two usages are
+ independent of each other: you can use it for a task and not for
+ the other if you wish. At time or writing (2007-01-11) the SDL GUI
+ lacks menus and a performant input event architecture; the SDL
+ sound handler is the most feature rich, supporting Video through
+ ffmpeg.
+
+sound handler
+ The _sound handler_ is the part of Gnash which handles both event
+ sounds and streaming sound. Audio from external sources are also
+ handled through the sound handler when SDL is used. The sound
+ handler must be selected during configuration of Gnash when
+ compiling.
+
+ There are currently two sound handlers available in Gnash: SDL and
+ Gstreamer. The SDL sound handler uses ffmpeg or libmad for
+ decoding mp3-audio, although it can be built without mp3-support.
+ The Gstreamer-sound handler uses the available plugins to decode
+ the audio, so it might not work if some important plugins are
+ missing. The SDL sound handler is recommended.
+
+sprite
+ A sprite is an element of an Flash Movie. It's basically a Movie
+ inside another, having its own timeline.
+
+Stage
+ The visible area of a Flash movie. The name derives from a
+ theater analogy. Graphical elements are referred to as characters.
+
+SWF
+ _SWF_ is the file format for _Flash_ movies.
+
+
+T
+=
+
+Tamarin
+ The Tamarin project seeks to create an open source implementation
+ of the ECMAScript 4th edition language specification. The code is
+ used by Adobe as part of the ActionScript Virtual Machine within
+ the Adobe Flash Player. Gnash does not use Tamarin; it already has
+ a working virtual server and most ActionScript classes are
+ implemented.
+
+timeline
+ In Flash technology, a timeline is a sequence of "frames". A
+ single Flash movie can contain multiple timelines, each
+ independently controlled (STOP or PLAY). At regular intervals
+ (FPS) the player advances all timelines in PLAY mode to the next
+ frame, looping back when last frame is reached.
+
+
+X
+=
+
+X.org
+ X.org is the most commonly used X server; it was forked from
+ XFree86.
+
+
+File: gnash_user.info, Node: Authors, Next: GNU Free Documentation License,
Prev: Glossary, Up: Top
+
+6 Authors
+*********
+
+Gnash is maintained by Rob Savoye. Other active developers are: Sandro
+Santilli, Bastiaan Jacques, Udo Giacomozzi, Chad Musick, Benjamin
+Wolsey, and Zou Lunkai. Please send all comments and suggestions to
+<address@hidden>. Past and sometimes current developers are Tomas
+Groth and Markus Gothe.
+
+ Gnash was initially derived from GameSWF. GameSWF is maintained by
+Thatcher Ulrich <address@hidden>. The following people contributed to
+GameSWF: Mike Shaver, Thierry Berger-Perrin, Ignacio Castan~o, Willem
+Kokke, Vitaly Alexeev, Alexander Streit, and Rob Savoye.
+
+
+File: gnash_user.info, Node: GNU Free Documentation License, Prev: Authors,
Up: Top
+
+Appendix A GNU Free Documentation License
+*****************************************
+
+* Menu:
+
+* 0. PREAMBLE: 0_ PREAMBLE.
+* 1. APPLICABILITY AND DEFINITIONS: 1_ APPLICABILITY AND DEFINITIONS.
+* 2. VERBATIM COPYING: 2_ VERBATIM COPYING.
+* 3. COPYING IN QUANTITY: 3_ COPYING IN QUANTITY.
+* 4. MODIFICATIONS: 4_ MODIFICATIONS.
+* 5. COMBINING DOCUMENTS: 5_ COMBINING DOCUMENTS.
+* 6. COLLECTIONS OF DOCUMENTS: 6_ COLLECTIONS OF DOCUMENTS.
+* 7. AGGREGATION WITH INDEPENDENT WORKS: 7_ AGGREGATION WITH INDEPENDENT WORKS.
+* 8. TRANSLATION: 8_ TRANSLATION.
+* 9. TERMINATION: 9_ TERMINATION.
+* 10. FUTURE REVISIONS OF THIS LICENSE: 10_ FUTURE REVISIONS OF THIS LICENSE.
+* Addendum::
+
+
+File: gnash_user.info, Node: 0_ PREAMBLE, Next: 1_ APPLICABILITY AND
DEFINITIONS, Up: GNU Free Documentation License
+
+A.1 0. PREAMBLE
+===============
+
+The purpose of this License is to make a manual, textbook, or other
+written document "free" in the sense of freedom: to assure everyone the
+effective freedom to copy and redistribute it, with or without
+modifying it, either commercially or non-commercially. Secondarily,
+this License preserves for the author and publisher a way to get credit
+for their work, while not being considered responsible for
+modifications made by others.
+
+ This License is a kind of "copyleft", which means that derivative
+works of the document must themselves be free in the same sense. It
+complements the GNU General Public License, which is a copyleft license
+designed for free software.
+
+ We have designed this License in order to use it for manuals for
+free software, because free software needs free documentation: a free
+program should come with manuals providing the same freedoms that the
+software does. But this License is not limited to software manuals; it
+can be used for any textual work, regardless of subject matter or
+whether it is published as a printed book. We recommend this License
+principally for works whose purpose is instruction or reference.
+
+
+File: gnash_user.info, Node: 1_ APPLICABILITY AND DEFINITIONS, Next: 2_
VERBATIM COPYING, Prev: 0_ PREAMBLE, Up: GNU Free Documentation License
+
+A.2 1. APPLICABILITY AND DEFINITIONS
+====================================
+
+This License applies to any manual or other work that contains a notice
+placed by the copyright holder saying it can be distributed under the
+terms of this License. The "Document", below, refers to any such manual
+or work. Any member of the public is a licensee, and is addressed as
+"you".
+
+ A "Modified Version" of the Document means any work containing the
+Document or a portion of it, either copied verbatim, or with
+modifications and/or translated into another language.
+
+ A "Secondary Section" is a named appendix or a front-matter section
+of the Document (*note fdl-document::) that deals exclusively with the
+relationship of the publishers or authors of the Document to the
+Document's overall subject (or to related matters) and contains nothing
+that could fall directly within that overall subject. (For example, if
+the Document is in part a textbook of mathematics, a Secondary Section
+may not explain any mathematics.) The relationship could be a matter
+of historical connection with the subject or with related matters, or of
+legal, commercial, philosophical, ethical or political position
+regarding them.
+
+ The "Invariant Sections" are certain Secondary Sections (*note
+fdl-secondary::) whose titles are designated, as being those of
+Invariant Sections, in the notice that says that the Document (*note
+fdl-document::) is released under this License.
+
+ The "Cover Texts" are certain short passages of text that are
+listed, as Front-Cover Texts or Back-Cover Texts, in the notice that
+says that the Document (*note fdl-document::) is released under this
+License.
+
+ A "Transparent" copy of the Document (*note fdl-document::) means a
+machine-readable copy, represented in a format whose specification is
+available to the general public, whose contents can be viewed and edited
+directly and straightforwardly with generic text editors or (for images
+composed of pixels) generic paint programs or (for drawings) some
+widely available drawing editor, and that is suitable for input to text
+formatters or for automatic translation to a variety of formats
+suitable for input to text formatters. A copy made in an otherwise
+Transparent file format whose markup has been designed to thwart or
+discourage subsequent modification by readers is not Transparent. A
+copy that is not "Transparent" is called "Opaque".
+
+ Examples of suitable formats for Transparent copies include plain
+ASCII without markup, Texinfo input format, LaTeX input format, SGML or
+XML using a publicly available DTD, and standard-conforming simple HTML
+designed for human modification. Opaque formats include PostScript, PDF,
+proprietary formats that can be read and edited only by proprietary
+word processors, SGML or XML for which the DTD and/or processing tools
+are not generally available, and the machine-generated HTML produced by
+some word processors for output purposes only.
+
+ The "Title Page" means, for a printed book, the title page itself,
+plus such following pages as are needed to hold, legibly, the material
+this License requires to appear in the title page. For works in formats
+which do not have any title page as such, "Title Page" means the text
+near the most prominent appearance of the work's title, preceding the
+beginning of the body of the text.
+
+
+File: gnash_user.info, Node: 2_ VERBATIM COPYING, Next: 3_ COPYING IN
QUANTITY, Prev: 1_ APPLICABILITY AND DEFINITIONS, Up: GNU Free Documentation
License
+
+A.3 2. VERBATIM COPYING
+=======================
+
+You may copy and distribute the Document (*note fdl-document::) in any
+medium, either commercially or noncommercially, provided that this
+License, the copyright notices, and the license notice saying this
+License applies to the Document are reproduced in all copies, and that
+you add no other conditions whatsoever to those of this License. You
+may not use technical measures to obstruct or control the reading or
+further copying of the copies you make or distribute. However, you may
+accept compensation in exchange for copies. If you distribute a large
+enough number of copies you must also follow the conditions in section
+3 (*note 3_ COPYING IN QUANTITY::).
+
+ You may also lend copies, under the same conditions stated above,
+and you may publicly display copies.
+
+
+File: gnash_user.info, Node: 3_ COPYING IN QUANTITY, Next: 4_ MODIFICATIONS,
Prev: 2_ VERBATIM COPYING, Up: GNU Free Documentation License
+
+A.4 3. COPYING IN QUANTITY
+==========================
+
+If you publish printed copies of the Document (*note fdl-document::)
+numbering more than 100, and the Document's license notice requires
+Cover Texts (*note fdl-cover-texts::), you must enclose the copies in
+covers that carry, clearly and legibly, all these Cover Texts:
+Front-Cover Texts on the front cover, and Back-Cover Texts on the back
+cover. Both covers must also clearly and legibly identify you as the
+publisher of these copies. The front cover must present the full title
+with all words of the title equally prominent and visible. You may add
+other material on the covers in addition. Copying with changes limited
+to the covers, as long as they preserve the title of the Document
+(*note fdl-document::) and satisfy these conditions, can be treated as
+verbatim copying in other respects.
+
+ If the required texts for either cover are too voluminous to fit
+legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto adjacent
+pages.
+
+ If you publish or distribute Opaque (*note fdl-transparent::) copies
+of the Document (*note fdl-document::) numbering more than 100, you
+must either include a machine-readable Transparent (*note
+fdl-transparent::) copy along with each Opaque copy, or state in or
+with each Opaque copy a publicly-accessible computer-network location
+containing a complete Transparent copy of the Document, free of added
+material, which the general network-using public has access to download
+anonymously at no charge using public-standard network protocols. If
+you use the latter option, you must take reasonably prudent steps, when
+you begin distribution of Opaque copies in quantity, to ensure that
+this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you distribute an
+Opaque copy (directly or through your agents or retailers) of that
+edition to the public.
+
+ It is requested, but not required, that you contact the authors of
+the Document (*note fdl-document::) well before redistributing any
+large number of copies, to give them a chance to provide you with an
+updated version of the Document.
+
+
+File: gnash_user.info, Node: 4_ MODIFICATIONS, Next: 5_ COMBINING DOCUMENTS,
Prev: 3_ COPYING IN QUANTITY, Up: GNU Free Documentation License
+
+A.5 4. MODIFICATIONS
+====================
+
+You may copy and distribute a Modified Version (*note fdl-modified::)
+of the Document (*note fdl-document::) under the conditions of sections
+2 (*note 2_ VERBATIM COPYING::) and 3 (*note 3_ COPYING IN QUANTITY::)
+above, provided that you release the Modified Version under precisely
+this License, with the Modified Version filling the role of the
+Document, thus licensing distribution and modification of the Modified
+Version to whoever possesses a copy of it. In addition, you must do
+these things in the Modified Version:
+
+ * *A. * Use in the Title Page (*note fdl-title-page::) (and on the
+ covers, if any) a title distinct from that of the Document (*note
+ fdl-document::), and from those of previous versions (which
+ should, if there were any, be listed in the History section of the
+ Document). You may use the same title as a previous version if the
+ original publisher of that version gives permission.
+
+ * *B. * List on the Title Page (*note fdl-title-page::), as authors,
+ one or more persons or entities responsible for authorship of the
+ modifications in the Modified Version (*note fdl-modified::),
+ together with at least five of the principal authors of the
+ Document (*note fdl-document::) (all of its principal authors, if
+ it has less than five).
+
+ * *C. * State on the Title Page (*note fdl-title-page::) the name of
+ the publisher of the Modified Version (*note fdl-modified::), as
+ the publisher.
+
+ * *D. * Preserve all the copyright notices of the Document (*note
+ fdl-document::).
+
+ * *E. * Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.
+
+ * *F. * Include, immediately after the copyright notices, a license
+ notice giving the public permission to use the Modified Version
+ (*note fdl-modified::) under the terms of this License, in the
+ form shown in the Addendum below.
+
+ * *G. * Preserve in that license notice the full lists of Invariant
+ Sections (*note fdl-invariant::) and required Cover Texts (*note
+ fdl-cover-texts::) given in the Document's (*note fdl-document::)
+ license notice.
+
+ * *H. * Include an unaltered copy of this License.
+
+ * *I. * Preserve the section entitled "History", and its title, and
+ add to it an item stating at least the title, year, new authors,
+ and publisher of the Modified Version (*note fdl-modified::)as
+ given on the Title Page (*note fdl-title-page::). If there is no
+ section entitled "History" in the Document (*note fdl-document::),
+ create one stating the title, year, authors, and publisher of the
+ Document as given on its Title Page, then add an item describing
+ the Modified Version as stated in the previous sentence.
+
+ * *J. * Preserve the network location, if any, given in the Document
+ (*note fdl-document::) for public access to a Transparent (*note
+ fdl-transparent::) copy of the Document, and likewise the network
+ locations given in the Document for previous versions it was based
+ on. These may be placed in the "History" section. You may omit a
+ network location for a work that was published at least four years
+ before the Document itself, or if the original publisher of the
+ version it refers to gives permission.
+
+ * *K. * In any section entitled "Acknowledgements" or "Dedications",
+ preserve the section's title, and preserve in the section all the
+ substance and tone of each of the contributor acknowledgements
+ and/or dedications given therein.
+
+ * *L. * Preserve all the Invariant Sections (*note fdl-invariant::)
+ of the Document (*note fdl-document::), unaltered in their text
+ and in their titles. Section numbers or the equivalent are not
+ considered part of the section titles.
+
+ * *M. * Delete any section entitled "Endorsements". Such a section
+ may not be included in the Modified Version (*note fdl-modified::).
+
+ * *N. * Do not retitle any existing section as "Endorsements" or to
+ conflict in title with any Invariant Section (*note
+ fdl-invariant::).
+
+ If the Modified Version (*note fdl-modified::) includes new
+front-matter sections or appendices that qualify as Secondary Sections
+(*note fdl-secondary::) and contain no material copied from the
+Document, you may at your option designate some or all of these
+sections as invariant. To do this, add their titles to the list of
+Invariant Sections (*note fdl-invariant::) in the Modified Version's
+license notice. These titles must be distinct from any other section
+titles.
+
+ You may add a section entitled "Endorsements", provided it contains
+nothing but endorsements of your Modified Version (*note
+fdl-modified::) by various parties-for example, statements of peer
+review or that the text has been approved by an organization as the
+authoritative definition of a standard.
+
+ You may add a passage of up to five words as a Front-Cover Text
+(*note fdl-cover-texts::), and a passage of up to 25 words as a
+Back-Cover Text (*note fdl-cover-texts::), to the end of the list of
+Cover Texts (*note fdl-cover-texts::) in the Modified Version (*note
+fdl-modified::). Only one passage of Front-Cover Text and one of
+Back-Cover Text may be added by (or through arrangements made by) any
+one entity. If the Document (*note fdl-document::) already includes a
+cover text for the same cover, previously added by you or by
+arrangement made by the same entity you are acting on behalf of, you
+may not add another; but you may replace the old one, on explicit
+permission from the previous publisher that added the old one.
+
+ The author(s) and publisher(s) of the Document (*note
+fdl-document::) do not by this License give permission to use their
+names for publicity for or to assert or imply endorsement of any
+Modified Version (*note fdl-modified::).
+
+
+File: gnash_user.info, Node: 5_ COMBINING DOCUMENTS, Next: 6_ COLLECTIONS OF
DOCUMENTS, Prev: 4_ MODIFICATIONS, Up: GNU Free Documentation License
+
+A.6 5. COMBINING DOCUMENTS
+==========================
+
+You may combine the Document (*note fdl-document::) with other
+documents released under this License, under the terms defined in
+section 4 (*note 4_ MODIFICATIONS::) above for modified versions,
+provided that you include in the combination all of the Invariant
+Sections (*note fdl-invariant::) of all of the original documents,
+unmodified, and list them all as Invariant Sections of your combined
+work in its license notice.
+
+ The combined work need only contain one copy of this License, and
+multiple identical Invariant Sections (*note fdl-invariant::) may be
+replaced with a single copy. If there are multiple Invariant Sections
+with the same name but different contents, make the title of each such
+section unique by adding at the end of it, in parentheses, the name of
+the original author or publisher of that section if known, or else a
+unique number. Make the same adjustment to the section titles in the
+list of Invariant Sections in the license notice of the combined work.
+
+ In the combination, you must combine any sections entitled "History"
+in the various original documents, forming one section entitled
+"History"; likewise combine any sections entitled "Acknowledgements",
+and any sections entitled "Dedications". You must delete all sections
+entitled "Endorsements."
+
+
+File: gnash_user.info, Node: 6_ COLLECTIONS OF DOCUMENTS, Next: 7_
AGGREGATION WITH INDEPENDENT WORKS, Prev: 5_ COMBINING DOCUMENTS, Up: GNU
Free Documentation License
+
+A.7 6. COLLECTIONS OF DOCUMENTS
+===============================
+
+You may make a collection consisting of the Document (*note
+fdl-document::) and other documents released under this License, and
+replace the individual copies of this License in the various documents
+with a single copy that is included in the collection, provided that
+you follow the rules of this License for verbatim copying of each of the
+documents in all other respects.
+
+ You may extract a single document from such a collection, and
+distribute it individually under this License, provided you insert a
+copy of this License into the extracted document, and follow this
+License in all other respects regarding verbatim copying of that
+document.
+
+
+File: gnash_user.info, Node: 7_ AGGREGATION WITH INDEPENDENT WORKS, Next: 8_
TRANSLATION, Prev: 6_ COLLECTIONS OF DOCUMENTS, Up: GNU Free Documentation
License
+
+A.8 7. AGGREGATION WITH INDEPENDENT WORKS
+=========================================
+
+A compilation of the Document (*note fdl-document::) or its derivatives
+with other separate and independent documents or works, in or on a
+volume of a storage or distribution medium, does not as a whole count
+as a Modified Version (*note fdl-modified::) of the Document, provided
+no compilation copyright is claimed for the compilation. Such a
+compilation is called an "aggregate", and this License does not apply
+to the other self-contained works thus compiled with the Document , on
+account of their being thus compiled, if they are not themselves
+derivative works of the Document. If the Cover Text (*note
+fdl-cover-texts::) requirement of section 3 (*note 3_ COPYING IN
+QUANTITY::) is applicable to these copies of the Document, then if the
+Document is less than one quarter of the entire aggregate, the
+Document's Cover Texts may be placed on covers that surround only the
+Document within the aggregate. Otherwise they must appear on covers
+around the whole aggregate.
+
+
+File: gnash_user.info, Node: 8_ TRANSLATION, Next: 9_ TERMINATION, Prev: 7_
AGGREGATION WITH INDEPENDENT WORKS, Up: GNU Free Documentation License
+
+A.9 8. TRANSLATION
+==================
+
+Translation is considered a kind of modification, so you may distribute
+translations of the Document (*note fdl-document::) under the terms of
+section 4 (*note 4_ MODIFICATIONS::). Replacing Invariant Sections
+(*note fdl-invariant::) with translations requires special permission
+from their copyright holders, but you may include translations of some
+or all Invariant Sections in addition to the original versions of these
+Invariant Sections. You may include a translation of this License
+provided that you also include the original English version of this
+License. In case of a disagreement between the translation and the
+original English version of this License, the original English version
+will prevail.
+
+
+File: gnash_user.info, Node: 9_ TERMINATION, Next: 10_ FUTURE REVISIONS OF
THIS LICENSE, Prev: 8_ TRANSLATION, Up: GNU Free Documentation License
+
+A.10 9. TERMINATION
+===================
+
+You may not copy, modify, sublicense, or distribute the Document (*note
+fdl-document::) except as expressly provided for under this License.
+Any other attempt to copy, modify, sublicense or distribute the
+Document is void, and will automatically terminate your rights under
+this License. However, parties who have received copies, or rights,
+from you under this License will not have their licenses terminated so
+long as such parties remain in full compliance.
+
+
+File: gnash_user.info, Node: 10_ FUTURE REVISIONS OF THIS LICENSE, Next:
Addendum, Prev: 9_ TERMINATION, Up: GNU Free Documentation License
+
+A.11 10. FUTURE REVISIONS OF THIS LICENSE
+=========================================
+
+The Free Software Foundation (http://www.gnu.org/fsf/fsf.html) may
+publish new, revised versions of the GNU Free Documentation License
+from time to time. Such new versions will be similar in spirit to the
+present version, but may differ in detail to address new problems or
+concerns. See http://www.gnu.org/copyleft/
+(http://www.gnu.org/copyleft).
+
+ Each version of the License is given a distinguishing version
+number. If the Document (*note fdl-document::) specifies that a
+particular numbered version of this License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that specified version or of any later version
+that has been published (not as a draft) by the Free Software
+Foundation. If the Document does not specify a version number of this
+License, you may choose any version ever published (not as a draft) by
+the Free Software Foundation.
+
+
+File: gnash_user.info, Node: Addendum, Prev: 10_ FUTURE REVISIONS OF THIS
LICENSE, Up: GNU Free Documentation License
+
+A.12 Addendum
+=============
+
+To use this License in a document you have written, include a copy of
+the License in the document and put the following copyright and license
+notices just after the title page:
+
+ Copyright 2008, Free Software Foundation.
+
+ Permission is granted to copy, distribute and/or modify this
+ document under the terms of the GNU Free Documentation License,
+ Version 1.1 or any later version published by the Free Software
+ Foundation; with noInvariant Sections (*note fdl-invariant::),
+ with no Front-Cover Texts (*note fdl-cover-texts::), and with no
+ Back-Cover Texts (*note fdl-cover-texts::). A copy of the license
+ is included in the section entitled "GNU Free Documentation
+ License".
+
+ If your document contains nontrivial examples of program code, we
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License
+(http://www.gnu.org/copyleft/gpl.html), to permit their use in free
+software.
+
+
+
+Tag Table:
+Node: Top173
+Node: Introduction1479
+Node: Audience2272
+Node: What Is Supported ?2601
+Node: Using Gnash5134
+Node: Gnash Command Line Options51462
+Ref: Gnash Command Line Options <1>51809
+Node: Gnash Interactive Control Keys57659
+Ref: Gnash Interactive Control Keys <1>58026
+Node: User Configuration File58968
+Ref: User Configuration Variables59747
+Node: Installing and Configuring Gnash78609
+Node: Requirements78999
+Node: Hardware Requirements79320
+Ref: Build Matrix80106
+Node: Software Requirements81333
+Node: Downloading Gnash82166
+Node: Getting the Source82801
+Node: Releases83161
+Node: Snapshot83719
+Node: Repository84190
+Node: Getting Codec Support85011
+Node: Reporting Bugs85728
+Node: Get a Fresh Binary Package86728
+Node: Determine if the bug was previously reported87507
+Node: Review the bug writing guidelines88326
+Node: Filing a bug report89378
+Node: Glossary89662
+Ref: A89776
+Ref: C90600
+Ref: D90886
+Ref: E91298
+Ref: F91538
+Ref: G92521
+Ref: K93506
+Ref: L93940
+Ref: M94062
+Ref: N94421
+Ref: O94578
+Ref: P95193
+Ref: Q95480
+Ref: R95664
+Ref: S96905
+Ref: T98501
+Ref: X99209
+Node: Authors99302
+Node: GNU Free Documentation License99999
+Node: 0_ PREAMBLE100763
+Node: 1_ APPLICABILITY AND DEFINITIONS102070
+Ref: fdl-document102296
+Ref: fdl-modified102587
+Ref: fdl-secondary102774
+Ref: fdl-invariant103419
+Ref: fdl-cover-texts103668
+Ref: fdl-transparent103881
+Ref: fdl-title-page105171
+Node: 2_ VERBATIM COPYING105560
+Node: 3_ COPYING IN QUANTITY106541
+Node: 4_ MODIFICATIONS108899
+Node: 5_ COMBINING DOCUMENTS114960
+Node: 6_ COLLECTIONS OF DOCUMENTS116458
+Node: 7_ AGGREGATION WITH INDEPENDENT WORKS117350
+Node: 8_ TRANSLATION118579
+Node: 9_ TERMINATION119483
+Node: 10_ FUTURE REVISIONS OF THIS LICENSE120139
+Node: Addendum121280
+
+End Tag Table
Index: gnashuser.html.in
===================================================================
RCS file: gnashuser.html.in
diff -N gnashuser.html.in
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnashuser.html.in 1 Mar 2008 15:18:22 -0000 1.1
@@ -0,0 +1,1332 @@
+<html><head><meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>Gnash User Manual</title><meta name="generator"
content="DocBook XSL Stylesheets V1.72.0"></head><body bgcolor="white"
text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"
lang="en"><div class="titlepage"><div><div><h1 class="title"><a
name="index"></a>Gnash User Manual</h1></div><div><p class="releaseinfo">
+ This manual describes version 0.8.2 of Gnash.
+ </p></div><div><p class="copyright">Copyright © 2005, 2006, 2007, 2008
Free Software Foundation</p></div><div><div class="legalnotice"><a
name="legalnotice"></a><p>
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the <a href="#fdl" title="Appendix A. GNU Free
Documentation License"><em class="citetitle">GNU
+ Free Documentation License</em></a>, Version 1.1 or any later
+ version published by the Free Software Foundation with no Invariant
+ Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find
+ a copy of the GFDL at this
+ <a href="#fdl" title="Appendix A. GNU Free Documentation License">link</a>
or in the file COPYING-DOCS
+ distributed with this manual.
+ </p></div></div><div><div class="revhistory"><table border="1" width="100%"
summary="Revision history"><tr><th align="left" valign="top"
colspan="2"><b>Revision History</b></th></tr><tr><td align="left">Revision
Gnash User Manual version 0.1</td><td align="left">Feb 2008</td></tr><tr><td
align="left" colspan="2">
+ <p class="author">Rob Savoye
+ <code class="email"><<a
href="mailto:address@hidden";>address@hidden</a>></code>
+ The end user parts of the manual have been pulled out of
+ the original version of the manual, and rewritten.
+ </p>
+
+ <p class="publisher">Open Media Now! Foundation</p>
+ </td></tr></table></div></div></div><hr></div><div class="toc"><p><b>Table
of Contents</b></p><dl><dt><span class="chapter"><a href="#intro">1.
Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#audience">Audience</a></span></dt><dt><span class="sect1"><a
href="#runs-on">What Is Supported ?</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#usage">2. Using <span
class="application">Gnash</span></a></span></dt><dd><dl><dt><span
class="sect1"><a href="#options"><span class="application">Gnash</span> Command
Line Options</a></span></dt><dt><span class="sect1"><a href="#keys"><span
class="application">Gnash</span> Interactive Control
Keys</a></span></dt><dt><span class="sect1"><a href="#gnashrc">User
Configuration File</a></span></dt></dl></dd><dt><span class="chapter"><a
href="#build">3. Installing and Configuring
Gnash</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#requirements">Requirements</a></span></dt><dd><dl><dt><span
class="sect2"><a href="#hardware">Hardware
Requirements</a></span></dt><dt><span class="sect2"><a
href="#software">Software Requirements</a></span></dt></dl></dd><dt><span
class="sect1"><a href="#downloading">Downloading
Gnash</a></span></dt><dd><dl><dt><span class="sect2"><a
href="#gettingsource">Getting the Source</a></span></dt><dt><span
class="sect2"><a href="#getcodecs">Getting Codec
Support</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a
href="#bugreport">4. Reporting Bugs</a></span></dt><dd><dl><dt><span
class="sect1"><a href="#bugstep_package">Get a Fresh Binary
Package</a></span></dt><dt><span class="sect1"><a
href="#bugstep_search">Determine if the bug was previously
reported</a></span></dt><dt><span class="sect1"><a
href="#bugstep_guidelines">Review the bug writing
guidelines</a></span></dt><dt><span class="sect1"><a
href="#bugstep_file">Filing a bug report</a></span></dt></dl></dd><dt><span
class="glossary"><a href="#glossary">Glossary</a></span></dt><dt><span
class="chapter"><a href="#authors">5. Authors</a></span></dt><dt><span
class="appendix"><a href="#fdl">A. GNU Free Documentation
License</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#fdl-preamble">0. PREAMBLE</a></span></dt><dt><span class="sect1"><a
href="#fdl-section1">1. APPLICABILITY AND DEFINITIONS</a></span></dt><dt><span
class="sect1"><a href="#fdl-section2">2. VERBATIM
COPYING</a></span></dt><dt><span class="sect1"><a href="#fdl-section3">3.
COPYING IN QUANTITY</a></span></dt><dt><span class="sect1"><a
href="#fdl-section4">4. MODIFICATIONS</a></span></dt><dt><span class="sect1"><a
href="#fdl-section5">5. COMBINING DOCUMENTS</a></span></dt><dt><span
class="sect1"><a href="#fdl-section6">6. COLLECTIONS OF
DOCUMENTS</a></span></dt><dt><span class="sect1"><a href="#fdl-section7">7.
AGGREGATION WITH INDEPENDENT WORKS</a></span></dt><dt><span class="sect1"><a
href="#fdl-section8">8. TRANSLATION</a></span></dt><dt><span class="sect1"><a
href="#fdl-section9">9. TERMINATION</a></span></dt><dt><span class="sect1"><a
href="#fdl-section10">10. FUTURE REVISIONS OF THIS
LICENSE</a></span></dt><dt><span class="sect1"><a
href="#fdl-using">Addendum</a></span></dt></dl></dd></dl></div><div
class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>2.1. <a
href="#tb-command-line-options">Gnash Command Line Options</a></dt><dt>2.2. <a
href="#tb-control-keys">Gnash Interactive Control Keys</a></dt><dt>2.3. <a
href="#tb-config-variables">User Configuration Variables</a></dt><dt>3.1. <a
href="#tb-os-cpu">Build Matrix</a></dt></dl></div><div class="chapter"
lang="en"><div class="titlepage"><div><div><h2 class="title"><a
name="intro"></a>Chapter 1. Introduction</h2></div></div></div><div
class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a
href="#audience">Audience</a></span></dt><dt><span class="sect1"><a
href="#runs-on">What Is Supported ?</a></span></dt></dl></div><p>
+ <span class="application">Gnash</span> is a free SWF movie player. It is
available as a
+ stand-alone application or as a plugin for several popular
+ web browsers. It supports playing media from a disk or streaming
+ over a network connection. Some popular video sharing sites like
+ YouTube are supported from a wide vaariety of devices from
+ embedded ones to modern desktops.
+ </p><p>
+ <span class="application">Gnash</span> has a better focus on security,
allowing the user tight
+ control of all network or disk based I/O. Gnash also supports
+ extending ActionScript by creating your own. You can write
+ wrappers for any development library, and import them into the
+ player much like perl or python does.
+ </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a
name="audience"></a>Audience</h2></div></div></div><p>
+ This manual is primarily focused on users interested in how to
+ get Gnash installed from a package, and basic usage as a web
+ browser plugin. For more technical details, please refer to the
+ Gnash Reference manual.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="runs-on"></a>What Is Supported ?</h2></div></div></div><p>
+ Gnash is known to compile for most any POSIX and ANSI C++
+ conforming system if you have all the dependent libraries
+ installed. Systems we test on, and which Gnash is know to
+ run on are Ubuntu, Fedora, Debian, OpenBSD, NetBSD, FreeBSD,
+ Win32, and Darwin (OSX) primarily. Occasionally other platforms
+ are built, primarily by those distribution maintainers. This
+ includes BeOS, Haiku, Syllable, OS/2, Solaris, Slackware, and
+ Gentoo.
+ </p><p>
+ Gnash is a capable of reading up to SWF v9 files and opcodes,
+ but primarily supports SWF v7, with better SWF v8 and v9
+ support under heavy developement. With the 0.8.2 release,
+ Gnash includes initial parser support for SWF v8 and v9.
+ Not all ActionScript 2 classes are implemented yet, but all of the
+ most heavily used ones are. Many ActionScript 2 classes are
+ partially implemented; there is support for all of the
+ commonly used methods of each class.
+ </p><p>
+ Gnash has implemented about 80% of ActionScript v. 2.0, and has
+ begun implementing ActionScript v. 3.0. Gnash supports the
+ majority of Flash opcodes up to SWF version 9, and a wide
+ sampling of ActionScript classes for SWF version 8.
+ </p><p>
+ As ActionsScript 3 is a more developed version of
+ 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
+ easiest way for new Gnash developers to make a contribution
+ without a deep internal knpowledge of Gnash.
+ </p><p>
+ Gnash has included video support since early 2007, but this is
+ an every 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
+ 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
+ at: <a href="http://www.gnashdev.org/dev_snapshots/"; target="_top">
+ http://www.gnashdev.org/dev_snapshots</a>.
+ </p><p>
+ 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.
+ </p></div></div><div class="chapter" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="usage"></a>Chapter 2.
Using <span class="application">Gnash</span></h2></div></div></div><div
class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a
href="#options"><span class="application">Gnash</span> Command Line
Options</a></span></dt><dt><span class="sect1"><a href="#keys"><span
class="application">Gnash</span> Interactive Control
Keys</a></span></dt><dt><span class="sect1"><a href="#gnashrc">User
Configuration File</a></span></dt></dl></div><p>
+ When used as a standalone player, you can play any Flash file from
+ the command line by entering a command of the format:
+ </p><pre class="programlisting">
+ gnash <em class="replaceable"><code><option>
<flashfile.swf></code></em>
+ </pre><p>
+ The only required argument is the name (and location)of the file
+ to be played.
+ </p><p>
+ The available options are listed in the following section, or you
+ may view them in the terminal window by executing the following at
+ the command line:
+ </p><pre class="programlisting">
+ gnash --help |less
+ </pre><p>
+ </p><p>
+ The source code download of <span class="application">Gnash</span>
includes several example .SWF
+ files. They are located in the
+ <code class="filename">testsuite/samples/</code> directory of the <span
class="application">Gnash</span>
+ source directory. If you have installed <span
class="application">Gnash</span> correctly, issuing
+ the a command similar to the following plays a short animation of
+ a car swerving and crashing:
+ </p><pre class="programlisting">
+ gnash
+ /home/<em
class="replaceable"><code><username></code></em>/gnash/testsuite/car_smash.swf
+ </pre><p>
+ </p><div class="mediaobject" align="center"><img
src="images/car_crash.png" align="middle"></div><p>
+ </p><p>
+ The above is useful for playing Flash files downloaded to your
+ local system. It is also possible to play Flash files directly
+ from the web. To do so, use the <code class="option">-u</code> option
along
+ with the URL of the desired file.
+ </p><pre class="programlisting">
+ gnash -u http://example.domain.com/flashfile.swf
+ </pre><p>
+ Note that this will not work with every website; some embedded
+ Flash files are difficult to play.
+ </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a name="options"></a><span
class="application">Gnash</span> Command Line Options</h2></div></div></div><p>
+ No options are required for <span class="application">Gnash</span>'s
default behavior. However,
+ there are many options that can be used to that behavior.
+ </p><p>
+ </p><pre class="programlisting">
+ gnash <em class="replaceable"><code><options></code></em>
+ <code class="filename">filename.swf</code>
+ </pre><p>
+ </p><div class="table"><a name="tb-command-line-options"></a><p
class="title"><b>Table 2.1. Gnash Command Line Options</b></p><div
class="table-contents"><table summary="Gnash Command Line Options"
border="1"><colgroup><col align="left"><col
align="left"></colgroup><thead><tr><th align="left">Option</th><th
align="left">Function</th></tr></thead><tbody><tr><td align="left"><code
class="option">-h</code></td><td align="left">
+ Print usage information.
+ </td></tr><tr><td align="left">
+ <code class="option">-s factor</code>
+ </td><td align="left">
+ Scale the movie up/down by the specified factor.
+ </td></tr><tr><td align="left">
+ <code class="option">-c</code>
+ </td><td align="left">
+ Produce a core file instead of letting SDL trap it. By
+ default, SDL traps all signals, but sometimes a core file
+ is desired to assist with debugging.
+ </td></tr><tr><td align="left">
+ <code class="option">-d num</code>
+ </td><td align="left">
+ Number of milliseconds to delay in main loop. The main
+ loop polls continuously with a delay to adjust how long
+ <span class="emphasis"><em><span
class="application">Gnash</span></em></span> sleeps between iterations of the
+ loop. The smaller the number, the higher the CPU load
+ gets, and of course, the more iterations of the main
+ command loop.
+ </td></tr><tr><td align="left">
+ <code class="option">-p</code>
+ </td><td align="left">
+ Run full speed (no sleep) and log frame rate.
+ </td></tr><tr><td align="left">
+ <code class="option">-a</code>
+ </td><td align="left">
+ Enable Actionscript debugging.
+ </td></tr><tr><td align="left">
+ <code class="option">-v</code>
+ </td><td align="left">
+ Be verbose; i.e. print debug messages to stdout.
+ </td></tr><tr><td align="left">
+ <code class="option">-va</code>
+ </td><td align="left">
+ Be verbose about movie Actions.
+ </td></tr><tr><td align="left">
+ <code class="option">-vp</code>
+ </td><td align="left">
+ Be verbose about parsing the movie. Warning: this can
+ generate a lot of text, and can affect the performance of
+ the movie you are playing.
+ </td></tr><tr><td align="left">
+ <code class="option">-ml bias</code>
+ </td><td align="left">
+ Specify the texture LOD bias (float, default is -1) This
+ affects the fuzziness of small objects, especially small
+ text.
+ </td></tr><tr><td align="left">
+ <code class="option">-w</code>
+ </td><td align="left">
+ Write a debug log called gnash-dbg.log. This will
+ record of all the debug messages whether they are printed
+ to the screen or not.
+ </td></tr><tr><td align="left">
+ <code class="option">-j</code>
+ </td><td align="left">
+ Specify the width of the window. This is mostly used
+ only by the plugin.
+ </td></tr><tr><td align="left">
+ <code class="option">-k</code>
+ </td><td align="left">
+ Specify the height of the window. This is mostly used
+ only by the plugin.
+ </td></tr><tr><td align="left">
+ <code class="option">-1</code>
+ </td><td align="left">
+ Play once; exit when/if movie reaches the last
+ frame. This is the default.
+ </td></tr><tr><td align="left">
+ <code class="option">-r [0|1|2|3]</code>
+ </td><td align="left">
+ <div class="itemizedlist"><ul type="disc"><li><p>
+ 0 disables rendering and sound (good for batch tests).
+ </p></li><li><p>
+ 1 enables rendering and disables sound (default setting).
+ </p></li><li><p>
+ 2 enables sound and disables rendering.
+ </p></li><li><p>
+ 3 enables rendering and sound.
+ </p></li></ul></div>
+ </td></tr><tr><td align="left">
+ <code class="option">-t sec</code>
+ </td><td align="left">
+ Timeout and exit after the specified number of
+ seconds. This is useful for movies which repeat
+ themselves.
+ </td></tr><tr><td align="left">
+ <code class="option">-g</code>
+ </td><td align="left">
+ Start <span class="application">Gnash</span> with a Flash
debugger console so one can set
+ break points or watchpoints.
+ </td></tr><tr><td align="left">
+ <code class="option">-x id</code>
+ </td><td align="left">
+ This specifies the X11 window ID to display
+ in; this is mainly used by plugins.
+ </td></tr><tr><td align="left">
+ <code class="option">-b bits</code>
+ </td><td align="left">
+ Bit depth of output window (for example, 16 or 32). Appropriate
+ bit depths depend on the renderer and GUI library used.
+
+ </td></tr><tr><td align="left">
+ <code class="option">-u url</code>
+ </td><td align="left">
+ Set the _url member of the root movie. This is useful
+ when you download a movie and play it from a different
+ location. See also the -U switch.
+ </td></tr><tr><td align="left">
+ <code class="option">-U baseurl</code>
+ </td><td align="left">
+ Set base URL for this run. URLs are resolved relative to
+ this base. If omitted defaults to the _url member of the
+ top-level movie (see the -u switch).
+ </td></tr><tr><td align="left">
+ <code class="option">-P entrymeter</code>
+ </td><td align="left">
+ Parameters are given in ParamName=Value syntax and are mostly
+ useful to the plugin to honour EMBED tags attributes
+ or explicit OBJECT PARAM tags. A common use for -P
+ is to provide FlashVars
+ (ie: -P "FlashVars=home=http://www.gnu.org";).
+ </td></tr><tr><td align="left">
+ <code class="option">-F filedescriptor</code>
+ </td><td align="left">
+ Use the given filedescriptor to send requests to the host
+ application. This is currently only used for GETURL requests.
+ The protocol is not documented yet, and also needs improvement.
+ Primary use for this switch is for the NPAPI plugin to properly
+ support javascript and target windows in geturl requests.
+ </td></tr></tbody></table></div></div><br
class="table-break"></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="keys"></a><span class="application">Gnash</span> Interactive Control
Keys</h2></div></div></div><p>
+ While a movie is playing, there are several control
+ keys. These can be used to step through frames, pause the
+ playing, and control other actions.
+ </p><div class="table"><a name="tb-control-keys"></a><p
class="title"><b>Table 2.2. Gnash Interactive Control Keys</b></p><div
class="table-contents"><table summary="Gnash Interactive Control Keys"
border="1"><colgroup><col align="left"><col
align="left"></colgroup><thead><tr><th align="left">Key Combination</th><th
align="left">Function</th></tr></thead><tbody><tr><td align="left">
+ <code class="option">CTRL-Q</code>
+ </td><td align="left">
+ Quit/Exit.
+ </td></tr><tr><td align="left">
+ <code class="option">CTRL-W</code>
+ </td><td align="left">
+ Quit/Exit.
+ </td></tr><tr><td align="left">
+ <code class="option">ESC</code>
+ </td><td align="left">
+ Quit/Exit.
+ </td></tr><tr><td align="left">
+ <code class="option">CTRL-P</code>
+ </td><td align="left">
+ Toggle Pause.
+ </td></tr><tr><td align="left">
+ <code class="option">CTRL-R </code>
+ </td><td align="left">
+ Restart the movie.
+ </td></tr><tr><td align="left">
+ <code class="option">CTRL-[ or kp-</code>
+ </td><td align="left">
+ Step back one frame.
+ </td></tr><tr><td align="left">
+ <code class="option">CTRL-] or kp+</code>
+ </td><td align="left">
+ Step forward one frame.
+ </td></tr><tr><td align="left">
+ <code class="option">CTRL-L</code>
+ </td><td align="left">
+ Force immediate redraw.
+ </td></tr><tr><td align="left">
+ <code class="option">CTRL-T</code>
+ </td><td align="left">
+ Debug. Test the set_variable() function.
+ </td></tr><tr><td align="left">
+ <code class="option">CTRL-G</code>
+ </td><td align="left">
+ Debug. Test the get_variable() function.
+ </td></tr><tr><td align="left">
+ <code class="option">CTRL-M</code>
+ </td><td align="left">
+ Debug. Test the call_method() function.
+ </td></tr><tr><td align="left">
+ <code class="option">CTRL-B</code>
+ </td><td align="left">
+ Toggle the background color.
+ </td></tr></tbody></table></div></div><br
class="table-break"></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="gnashrc"></a>User Configuration File</h2></div></div></div><p>
+Individual user preferences may be set by editing variables with the <code
class="filename">.gnashrc</code> file:
+</p><pre class="programlisting">
+~/.gnashrc
+</pre><p>
+</p><p>
+Each line must begin with an action: either <span
class="emphasis"><em>set</em></span> or, in the case of lists, also
+<span class="emphasis"><em>append</em></span>.
+</p><p>
+The values in this configuration file apply only to an individual user, and
become the default settings of the standalone player and the plugin. Note that
any command line options take precedence over <code
class="filename">.gnashrc</code> settings.
+</p><p>
+The variables in the <code class="filename">.gnashrc</code> file support three
types of arguments: on/off, numeric values, or in the case of the
+ whitelist and blacklist, a list of hostnames as ASCII text.
+ </p><div class="table"><a name="tb-config-variables"></a><p
class="title"><b>Table 2.3. User Configuration Variables</b></p><div
class="table-contents"><table summary="User Configuration Variables"
border="1"><colgroup><col align="left"><col align="left"><col
align="left"></colgroup><thead><tr><th align="left">Variable</th><th
align="left">Value</th><th
align="left">Function</th></tr></thead><tbody><tr><td
align="left">localdomain</td><td align="left">on/off</td><td align="left">This
value can be set to either <span class="emphasis"><em>on</em></span> or
+ <span class="emphasis"><em>off</em></span>, and controls the
loading of
+ external Flash movies over a network. This option
+ tells Gnash to only load Flash movies from the existing
domain.</td></tr><tr><td align="left">localhost</td><td
align="left">on/off</td><td align="left">This value can be set to either <span
class="emphasis"><em>on</em></span> or
+ <span class="emphasis"><em>off</em></span>, and controls the
loading of
+ external Flash movies over a network. This is a stricter
+ version of the <span class="emphasis"><em>localdomain</em></span>
setting as
+ this allows the loading of Flash movies to the same host
+ that is running <span
class="application">Gnash</span>.</td></tr><tr><td
align="left">whitelist</td><td align="left">hostnames</td><td align="left">This
is a list of hostnames separated by spaces, or <span
class="emphasis"><em>off</em></span>
+ to disable the whitelist. The hostname must be given
+ without a protocol (http://, https://). If this list is populated,
+ <span class="application">Gnash</span> will only load external
Flash movies from the specified hosts. The
+ whitelist takes precedence over the blacklist. Because several
files can
+ be parsed in succession, each file can override or add to
+ lists in other files. Use <span
class="emphasis"><em>set</em></span> to override
+ all other lists or <span class="emphasis"><em>append</em></span> to
add your blacklisted
+ hosts to lists in previously parsed files.</td></tr><tr><td
align="left">blacklist</td><td align="left">hostnames</td><td align="left">This
is a list of hostnames separated by spaces, or <span
class="emphasis"><em>off</em></span>
+ to disable the blacklist. The hostname must be given
+ without a protocol (http://, https://).
+ External flash movies from these
+ domains are never allowed to load. If whitelist is present
+ and not empty, blacklist is not used. Because several files can
+ be parsed in succession, each file can override or add to
+ lists in other files. Use <span
class="emphasis"><em>set</em></span> to override
+ all other lists or <span class="emphasis"><em>append</em></span> to
add your blacklisted
+ hosts to lists in previously parsed files.</td></tr><tr><td
align="left">localSandboxPath</td><td align="left">dirs</td><td
align="left">This is a list of directories separated by spaces.
+ Only resources from these directories and from the directory
+ portion of movie filename (if loaded from filesystem) are allowed
to load.
+ Because several files can be parsed in succession, each file can
override
+ or add to lists in other files. Use <span
class="emphasis"><em>set</em></span> to override
+ all other lists or <span class="emphasis"><em>append</em></span> to
add new sandboxes.
+ Note that there's currently no way to *drop* the directory of base
dir
+ from the list of allowed local sandboxes.
+ </td></tr><tr><td align="left">delay</td><td
align="left">Number</td><td align="left"><span class="application">Gnash</span>
uses a timer-based event mechanism to advance frames
+ at a steady rate. This option overrides the default
+ setting in Gnash to play a movie slower or faster.</td></tr><tr><td
align="left">verbosity</td><td align="left">Number</td><td align="left">This is
a numeric value which defines the default level of
+ verbosity from the player.</td></tr><tr><td
align="left">MalformedSWFVerbosity</td><td align="left">on/off</td><td
align="left">This value can be set to either <span
class="emphasis"><em>on</em></span> or
+ <span class="emphasis"><em>off</em></span>, and controls whether
malformed SWF errors should
+ be printed. If set to true, verbosity level is automatically
incremented.
+ Set <code class="option">verbosity</code> to 0 afterwards to
hush.</td></tr><tr><td align="left">ASCodingErrorsVerbosity</td><td
align="left">on/off</td><td align="left">This value can be set to either <span
class="emphasis"><em>on</em></span> or
+ <span class="emphasis"><em>off</em></span>, and controls whether
ActionScript coding
+ errors should be printed. If set to true, verbosity level is
+ automatically incremented. Set <code
class="option">verbosity</code> to 0 afterwards to hush.</td></tr><tr><td
align="left">debuglog</td><td align="left">Absolute path</td><td
align="left">This is the full path and name of debug logfile as
+ produced by <span class="application">Gnash</span>. On systems with a
UNIX-type shell,
+ a tilde prefix (~) will be expanded as by Posix shell requirements
+ (see
http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_06_01).</td></tr><tr><td
align="left">writelog</td><td align="left">on/off</td><td align="left">This
value can be set to either <span class="emphasis"><em>on</em></span> or
+ <span class="emphasis"><em>off</em></span>, and controls whether a
debug log
+ is always written by <span class="application">Gnash</span>, or not
at all.</td></tr><tr><td align="left">sound</td><td align="left">on/off</td><td
align="left">This value can be set to either <span
class="emphasis"><em>on</em></span> or
+ <span class="emphasis"><em>off</em></span>, and controls the sound
of the
+ standalone player. By default <span
class="application">Gnash</span> enables playing the
+ sound in any Flash movie.</td></tr><tr><td
align="left">pluginsound</td><td align="left">on/off</td><td align="left">This
value can be set to either <span class="emphasis"><em>on</em></span> or
+ <span class="emphasis"><em>off</em></span>, and controls the sound
of the
+ player when running as a browser plugin. By default, sound
+ is enabled when using <span class="application">Gnash</span> as a
browser plugin.</td></tr><tr><td align="left">EnableExtensions</td><td
align="left">on/off</td><td align="left">Set to <span
class="emphasis"><em>on</em></span> to enable extensions. This option is <span
class="emphasis"><em>off</em></span> by default</td></tr><tr><td
align="left">StartStopped</td><td align="left">on/off</td><td align="left">Set
to <span class="emphasis"><em>on</em></span> to have the GUI start in "stop"
mode. This is useful in particular
+ for the plugin, so you have to explicitly start any movie on a
webpage. This option is <span class="emphasis"><em>off</em></span> by default.
+ </td></tr><tr><td align="left">flashVersionString</td><td
align="left">string</td><td align="left">Set the string returned by $version
and System.capabilities.version.
+ Useful to get around some flash version detection movies.
+ Note that the version advertised by the plugin is NOT affected by this
setting,
+ instead you need to set the GNASH_FLASH_VERSION environment variable for
+ the latter (which doesn't affect $version and
System.capabilities.version).</td></tr><tr><td
align="left">flashSystemOS</td><td align="left">string</td><td align="left">The
string that Gnash should return for System.capabilities.OS</td></tr><tr><td
align="left">flashSystemManufacturer</td><td align="left">string</td><td
align="left">The string that Gnash should return for
System.capabilities.manufacturer</td></tr><tr><td
align="left">StreamsTimeout</td><td align="left">double</td><td align="left">
+Set the number of seconds after which streams download time out. Note that
timeouts only occurs after the given number of seconds
+passed w/out anything was received.
+</td></tr><tr><td align="left">insecureSSL</td><td align="left">on/off</td><td
align="left">If set to <span class="emphasis"><em>on</em></span>, no
verification of SSL connections
+is performed. This means that, although the connection is encrypted, the server
+certificate could be invalid, may not belong to the host, or both. Equivalent
+to curl --insecure. By default, this option is <span
class="emphasis"><em>off</em></span> and
+connections will fail when a host cannot be verified.</td></tr><tr><td
align="left">SOLsafedir</td><td align="left">Absolute path</td><td
align="left">The full path to a directory where <span
class="application">Gnash</span> should store Shared Object files ("flash
cookies") if
+they are enabled.</td></tr><tr><td align="left">SOLreadonly</td><td
align="left">on/off</td><td align="left">If set to <span
class="emphasis"><em>on</em></span>, <span class="application">Gnash</span>
will not write Shared Object files.</td></tr><tr><td
align="left">URLOpenerFormat</td><td align="left">string</td><td align="left">
+Set the format of an url opener command. The %u label would be substituted by
the actual url to be opened.
+Examples:
+<pre class="programlisting">
+ set urlOpenerFormat firefox -remote 'openurl(%u)'
+ set urlOpenerFormat xdg-open %u
+ set urlOpenerFormat open %u
+ set urlOpenerFormat kfmclient exec %u
+</pre>
+</td></tr></tbody></table></div></div><br class="table-break"><p>
+The following example <code class="filename">.gnashrc</code> file allows a
user to only play Flash files saved locally to the machine on which <span
class="application">Gnash</span> is running. It also specifically forbids
content from doubleclick.com and mochibot.com. <span
class="application">Gnash</span>'s error output is set to be fairly verbose,
with the debug log placed in a location convenient for the user. Finally,
sound is turned on for both the standalone player and the plugin.
+</p><pre class="programlisting">
+
+ #
+ # Gnash client options
+ #
+
+ # Only access remote content from our local domain
+ set localdomain on
+
+ # Only access content from our local host
+ set localhost on
+
+ # These sites are OK
+ # uncommenting the following line will allow load of external
+ # movies *only* from the specified hosts.
+ #set whitelist www.doonesbury.com www.cnn.com www.9news.com
+
+ # Disable whitelists set in any other gnashrc files, because
+ # these could override our blacklist.
+ set whitelist off
+
+ # Don't access content from these sites
+ set blacklist www.doubleclick.com mochibot.com
+
+ # The delay between timer interrupts
+ set delay 50
+
+ # The default verbosity level
+ set verbosity 1
+
+ # Be verbose about malformed SWF
+ set MalformedSWFVerbosity true
+
+ # Be verbose about AS coding errors
+ set ASCodingErrorsVerbosity true
+
+ # The full path to the debug log
+ set debuglog ~/gnash-dbg.log
+
+ # Write a debug log to disk
+ set writelog on
+
+ # Enable or Disable sound for the standalone player
+ set sound on
+
+ # Enable or Disable sound for the standalone player
+ set pluginsound on
+
+ # Make sure SSL connections are always verified
+ set insecureSSL off
+
+ # Use firefox to open urls
+ set urlOpenerFormat firefox -remote 'openurl(%u)'
+
+ </pre></div></div><div class="chapter" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="build"></a>Chapter 3.
Installing and Configuring Gnash</h2></div></div></div><div
class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a
href="#requirements">Requirements</a></span></dt><dd><dl><dt><span
class="sect2"><a href="#hardware">Hardware
Requirements</a></span></dt><dt><span class="sect2"><a
href="#software">Software Requirements</a></span></dt></dl></dd><dt><span
class="sect1"><a href="#downloading">Downloading
Gnash</a></span></dt><dd><dl><dt><span class="sect2"><a
href="#gettingsource">Getting the Source</a></span></dt><dt><span
class="sect2"><a href="#getcodecs">Getting Codec
Support</a></span></dt></dl></dd></dl></div><p>
+ There are two ways of installing Gnash:
+ <a href="#">using a package manager</a>
+ or <a href="#gettingsource" title="Getting the Source">installing from
source</a>.
+ </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a
name="requirements"></a>Requirements</h2></div></div></div><p>
+ Before downloading and installing Gnash, check that your
+ hardware and software meet the following requirements.
+ </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3
class="title"><a name="hardware"></a>Hardware
Requirements</h3></div></div></div><p>
+ One of the goals of Gnash is to make it portable enough to
+ install on small devices. As a result, the hardware
+ requirements are minimal. Gnash has even run on an ARM9 at 200
+ MHz with 32 MB of RAM! (It ran without video support in this
+ case.) While firm minimums have not been established, Gnash
+ has been shown to run successfully with the following:
+ </p><div class="itemizedlist"><ul type="disc"><li><p>
+ 336 MHz processor
+ </p></li><li><p>
+ 128 MB RAM
+ </p></li><li><p>
+ Video — Gnash will run on anything from a raw frame
+ buffer up to an OpenGL-supporting graphics card.
+ </p></li></ul></div><p>
+ The following table provides a list of the Operating System/CPU
+ combinations on which Gnash has been shown to run.
+ </p><div class="table"><a name="tb-os-cpu"></a><p class="title"><b>Table
3.1. Build Matrix</b></p><div class="table-contents"><table summary="Build
Matrix" border="1"><colgroup><col align="left"><col
align="left"></colgroup><thead><tr><th align="left">Operating System</th><th
align="left">Processor</th></tr></thead><tbody><tr><td align="left">OpenBSD,
FreeBSD, NetBSD</td><td align="left">Alpha AXP, AMD64, i386, Itanium, PC-98,
PowerPC, SPARC64
+ </td></tr><tr><td align="left">Debian</td><td align="left">Alpha
AXP, AMD64, ARM, hppa, i386, Itanium, MIPS,
+ PowerPC, IBM zSeries (s390), SPARC
+ </td></tr><tr><td align="left">Fedora</td><td
align="left">x86-32, x86-64, Geode GX, Geode LX
+ </td></tr><tr><td align="left">Gentoo</td><td align="left">AMD64,
PowerPC, SPARC, x86
+ </td></tr><tr><td align="left">Maemo 2.1</td><td
align="left">i385, ARMv5t</td></tr><tr><td align="left">Scratchbox</td><td
align="left">i386, ARMv5t</td></tr><tr><td align="left">Access Linux Platform
+ </td><td align="left">i386, ARMv5t</td></tr><tr><td
align="left">Mandriva
+ </td><td align="left">i386, MIPS</td></tr><tr><td
align="left">Open Embedded, OpenMoko, Poky
+ </td><td align="left">ARM
+ </td></tr><tr><td align="left">YellowDog Linux 6
+ </td><td align="left">PowerPC, PS3
+ </td></tr><tr><td align="left">OpenSuSE 10
+ </td><td align="left">i586, x86-64
+ </td></tr><tr><td align="left">Red Hat Enterprise, CentOS
+ </td><td align="left">x86-32, x86-64
+ </td></tr><tr><td align="left">Ubuntu
+ </td><td align="left">x86-64, x86-32, PowerPC, UltraSPARC
+ </td></tr><tr><td align="left">Haiku</td><td
align="left">i386</td></tr><tr><td align="left">Syllable</td><td
align="left">i386</td></tr><tr><td align="left">Irix 6.5
+ </td><td align="left">MIPS R10K
+ </td></tr><tr><td align="left">Darwin (MacOS X)
+ </td><td align="left">PowerPC and x86-32
+ </td></tr><tr><td align="left">Windows XP, Windows Vista</td><td
align="left">x86-32</td></tr></tbody></table></div></div><br
class="table-break"></div><div class="sect2" lang="en"><div
class="titlepage"><div><div><h3 class="title"><a name="software"></a>Software
Requirements</h3></div></div></div><p>
+ The 0.8.2 release of Gnash has been designed to run on
+ UNIX/Linux variants, and has been run on most of the free ones.
+ However, Gnash has successfully run on Windows, Darwin (Mac OS X),
+ Irix, Solaris, BeOs, OS/2, and Haiku. Gnash has also run on the
+ following 64-bit systems: PowerPC, Itanium, UltraSparc, and AMD64.
+ For now, it is important to be sure that the following code, testing,
+ and documentation dependencies are met before installing Gnash. If
+ you will be downloading Gnash with a package manager, these
+ dependencies may be solved by the package manager. Otherwise, you
+ must first verify that each of these dependencies are installed on the
+ target system.
+ </p></div></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="downloading"></a>Downloading Gnash</h2></div></div></div><p>
+ There are two ways to download Gnash: using a package manager or by
+ downloading the source code and building it on your system. If
+ possible, it is advisable to use a package manager to download Gnash,
+ as it will resolve dependencies for you. However, if you want the
+ very latest features, or a Gnash package is not available for your
+ operating system, it is better to download the source code and build
+ Gnash locally.
+ </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3
class="title"><a name="gettingsource"></a>Getting the
Source</h3></div></div></div><p>
+ Gnash is available as a <a href="#sourcereleases"
title="Releases">release
+ tarball</a>, a <a href="#sourcerepo" title="Repository">development
+ checkout</a>, or a <a href="#sourcesnapshot"
title="Snapshot">development
+ snapshot</a>.
+ </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4
class="title"><a name="sourcereleases"></a>Releases</h4></div></div></div><p>
+ The source can be acquired from a
+ <a href="http://www.gnu.org/prep/ftp.html"; target="_top">GNU FTP
+ Mirror</a>. The release version is intended to be
+ stable, and is probably your best choice if the release took
+ place recently. If you need features or fixes which were
+ introduced after the release, consider a
+ <a href="#sourcerepo" title="Repository">CVS checkout</a> or the
+ <a href="#sourcesnapshot" title="Snapshot">daily snapshot</a>.
+ </p><p>
+ To download, select a mirror near you, then choose the
+ <code class="filename">gnash</code> directory.
+ </p></div><div class="sect3" lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
name="sourcesnapshot"></a>Snapshot</h4></div></div></div><p>
+ The daily development snapshot can be downloaded from
+ <a href="http://www.gnashdev.org/dev_snapshots/";
target="_top">http://www.gnashdev.org/dev_snapshots/</a>.
+ This is the best option if you need changes which were introduced
+ after the <a href="#sourcereleases" title="Releases">last
release</a> of
+ Gnash, but are unable to <a href="#sourcerepo"
title="Repository">download
+ directly from the repository.</a>
+ </p></div><div class="sect3" lang="en"><div
class="titlepage"><div><div><h4 class="title"><a
name="sourcerepo"></a>Repository</h4></div></div></div><p>
+ The latest development sources are available via
+ anonymous CVS. This is recommended
+ if you need features or bug fixes which were introduced after
+ the <a href="#sourcereleases" title="Releases">last release</a>.
Look at
+ the <a href="#sourcesnapshot" title="Snapshot">daily snapshot</a>
if you
+ experience difficulty accessing the repository.
+ </p><p>
+ To download via anonymous CVS, first set the
+ environment variable <span><strong
class="command">CVS_RSH</strong></span> to
+ <span><strong class="command">ssh</strong></span>, then check out
the source code.
+ The example below uses the GNU Bourne-Again shell (bash):
+ </p><pre class="screen">
+ export CVS_RSH="ssh"
+ cvs -z3 -d:pserver:address@hidden:/sources/gnash co gnash
+ </pre><p>
+ It is also possible to browse the repository
+ <a href="http://cvs.savannah.gnu.org/viewcvs/gnash/?root=gnash";
target="_top">http://cvs.savannah.gnu.org/viewcvs/gnash/?root=gnash</a> on the
web.
+ </p></div></div><div class="sect2" lang="en"><div
class="titlepage"><div><div><h3 class="title"><a name="getcodecs"></a>Getting
Codec Support</h3></div></div></div><p>
+ Gnash requires codec support to handle audio and video
+ correctly. Some platforms like Ubuntu or Fedora under the
+ GNOME desktop will automatically notify the user that the
+ proper codecs aren't installed, and pop up a dialog box to
+ let the user download the codecs Gnash needs to make site
+ like YouTube work correctly. If you have installed Gnash on
+ any other platform, and video doesn't work, it's highly
+ likely you need to install the proper codecs. For most
+ platforms, this is the Gstreamer-ffmpeg plugin, available
+ from your distributions repository.
+ </p></div></div></div><div class="chapter" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="bugreport"></a>Chapter
4. Reporting Bugs</h2></div></div></div><div class="toc"><p><b>Table of
Contents</b></p><dl><dt><span class="sect1"><a href="#bugstep_package">Get a
Fresh Binary Package</a></span></dt><dt><span class="sect1"><a
href="#bugstep_search">Determine if the bug was previously
reported</a></span></dt><dt><span class="sect1"><a
href="#bugstep_guidelines">Review the bug writing
guidelines</a></span></dt><dt><span class="sect1"><a
href="#bugstep_file">Filing a bug report</a></span></dt></dl></div><p>
+ The Gnash project relies on the community of Gnash users to test
+ 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
+ <a href="http://savannah.gnu.org";
target="_top">http://savannah.gnu.org</a> to manage these reports.
+ </p><p>
+ 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
+ critical details, like the Operating System you are on, it's
+ version, and any relevant error messages from Gnash that you get.
+ </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a name="bugstep_package"></a>Get a Fresh
Binary Package</h2></div></div></div><p>
+ For starters, it's a good idea to obtain a copy of the latest
+ snapshot. Although Gnash is primarily released as source, the
+ 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.
+ </p><p>
+ You can get a fresh binary package of Gnash, as well as recent
+ source packages from
+ <a href="http://www.getgnash.org/packages/"; target="_top">
+ http://www.getgnash.org/packages
+ </a>.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="bugstep_search"></a>Determine if the bug was previously
reported</h2></div></div></div><p>
+ Search the <a href="https://savannah.gnu.org/bugs/?group=gnash";
target="_top">Gnash
+ bug tracker</a> to see if the bug has already been identified.
+ </p><p>
+ If the issue has already been reported, you should not file
+ a bug report. However, you may add some additional information
+ to the ticket if you feel that it will be beneficial to the
+ developers. For instance, if someone reported a memory issue
+ on Ubuntu GNU/Linux, and you noticed the same problem on OpenBSD,
+ your stacktrace would be useful. Conversely, adding a "me too"
+ note to a feature request is not helpful.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="bugstep_guidelines"></a>Review the bug writing
guidelines</h2></div></div></div><p>
+ A good bug report should be precise, explicit, and discrete.
+ This means that there should be just one bug per ticket, and
+ that a ticket should contain the following information:
+ </p><div class="itemizedlist"><ul type="opencircle"><li
style="list-style-type: circle"><p>
+ An overview of the problem;
+ </p></li><li style="list-style-type: circle"><p>
+ Instructions on how to replicate the bug;
+ </p></li><li style="list-style-type: circle"><p>
+ A description of what happened when you performed the steps
+ to replicate the bug, and what you expected to happen;
+ </p></li><li style="list-style-type: circle"><p>
+ Your system information: operating system name and version, as
+ well as the versions of major development dependencies;
+ </p></li><li style="list-style-type: circle"><p>
+ The release number or checkout timestamp for the version of Gnash
+ where you observe the problem;
+ </p></li><li style="list-style-type: circle"><p>
+ The file <code class="filename">config.log</code>, which should be
+ attached as a file;
+ </p></li><li style="list-style-type: circle"><p>
+ A descriptive title.
+ </p></li></ul></div><p>
+ Include any additional information that you feel might be useful
+ to the developers.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="bugstep_file"></a>Filing a bug report</h2></div></div></div><p>
+ After following the steps described above, you can file a bug report at
+ <a href="https://savannah.gnu.org/bugs/?group=gnash";
target="_top">https://savannah.gnu.org/bugs/?group=gnash</a>.
+ </p></div></div><div class="glossary"><div class="titlepage"><div><div><h2
class="title"><a name="glossary"></a>Glossary</h2></div></div></div><div
class="glossdiv"><h3 class="title">A</h3><dl><dt>
+ ActionScript
+ </dt><dd><p>
+ <span class="emphasis"><em>ActionScript</em></span>, or "AS", is the
scripting
+ language for <span class="emphasis"><em>Flash</em></span>
+ applications. It is compiled to bytecode, which is a subset of
+ the <span class="emphasis"><em>SWF</em></span> format.
+ </p></dd><dt>
+ AGG
+ </dt><dd><p>
+ AGG is the AntiGrain 2D graphics library, which can be used
+ as a renderer in Gnash. It is faster than OpenGL on systems
+ without hardware graphics acceleration. As of Gnash version
+ 0.8.1 it is the more feature complete renderer.
+ </p></dd><dt>
+ AMF
+ </dt><dd><p>
+ <span class="emphasis"><em>AMF</em></span>
+ is the object format used by <span
class="emphasis"><em>Flash</em></span>
+ for shared objects and streaming video.
+ </p></dd><dt>
+ as_environment
+ </dt><dd><p>
+ In Gnash terms, the as_environment, or ActionScript
+ execution environment, contains a stack of objects,
+ characters and values which are in the immediate environment
+ of the current fn_call. Please refer to the Gnash
+ ActionScript manual for more information.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">C</h3><dl><dt>
+ Cairo
+ </dt><dd><p>
+ Cairo is a 2D graphics library with support for multiple
+ output devices. Can be used as a renderer in Gnash. A useful
+ feature of Cairo is that it will automatically use graphic
+ card acceleration when available. Cairo has an experimental
+ OpenGL backend.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">D</h3><dl><dt>
+ DejaGNU
+ </dt><dd><p>
+ DejaGNU is a framework for testing software.
+ </p></dd><dt>
+ DocBook
+ </dt><dd><p>
+ <span class="emphasis"><em>DocBook</em></span>
+ is a markup language for presentation-neutral
+ documentation, such as manuals.
+ </p></dd><dt>
+ Doxygen
+ </dt><dd><p>
+ <span class="emphasis"><em>Doxygen</em></span>
+ is a documentation generator for for multiple languages
+ which uses comments in the source code to create stand-alone
+ documentation.
+ </p></dd><dt>
+ Drupal
+ </dt><dd><p>
+ Drupal is a CMS/blog system used for the main Gnash website.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">E</h3><dl><dt>
+ extensions
+ </dt><dd><p>
+ A <span class="application">Gnash</span> <span
class="emphasis"><em>extension</em></span> is a plugin (not a
+ browser plugin) which implements additional functionality
+ beyond what is covered by <span class="emphasis"><em>Flash</em></span>
+ specification. These are shared libraries which are loaded
+ at runtime.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">F</h3><dl><dt>
+ ffmpeg
+ </dt><dd><p>
+ ffmpeg is an audio and video decoding library which can be
+ used by Gnash to decode mp3, FLV and other media types.
+ </p></dd><dt>
+ Flash
+ </dt><dd><p>
+ The term <span class="emphasis"><em>Flash</em></span> is used to
describe both the
+ Adobe IDE for creating <span class="emphasis"><em>SWF</em></span>
+ files, and the technology itself. Flash is a trademarked
+ term of Adobe's, we prfer to use SWF to refer to the files
+ themselves, as well as the format, instead of flash(tm).
+ </p></dd><dt>
+ FLV
+ </dt><dd><p>
+ FLV is a proprietary file format used to deliver Flash
+ video. It is used by YouTube, among others.
+ </p></dd><dt>
+ FLTK
+ </dt><dd><p>
+ FLTK, or the 'Fast Light ToolKit', is a portable GUI library
+ which is intended to replace the SDL GUI. Currently in Gnash,
+ FLTK may be used with the Cairo and AGG renderers. FLTK has an
+ experimental Cairo backend.
+ </p></dd><dt>
+ FrameBuffer
+ </dt><dd><p>
+ In Gnash, this is a GUI library that outputs directly to the
+ Linux Frame Buffer and so does not need a window system to
+ run. This makes it particularly suitable for use on small
+ devices.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">G</h3><dl><dt>
+ Gnash
+ </dt><dd><p>
+ Gnash is the GNU Flash movie player.
+ </p></dd><dt>
+ Gstreamer
+ </dt><dd><p>
+ Gstreamer is a multimedia framework which Gnash can use for
+ decoding audio and video. Gstreamer itself cannot decode
+ anything, so it needs some appropriate decoding-plugins to do
+ the work for it. Remember to install them if you use Gnash
+ with Gstreamer enabled. To get the best out of Gnashs
+ gstreamer-parts, it is recommended to install the
+ gst-plugins-good, gst-plugins-good and gst-ffmpeg plugins
+ packages.
+ </p></dd><dt>
+ GTK
+ </dt><dd><p>
+ GTK is the GIMP Toolkit GUI library. It is one of the GUI
+ options for Gnash. As of Gnash 0.7.2, this is the more
+ performant and feature-rich choice. GTK uses Cairo
+ internally.
+ </p></dd><dt>
+ GUI
+ </dt><dd><p>
+ A <span class="emphasis"><em>GUI</em></span> is a
+ "graphical user interface". In <span class="application">Gnash</span>,
the GUI
+ library provides a wrapper for mouse and keyboard events,
+ menus, windowing (where available) and a drawing area.
+ You must choose a GUI library during the
+ configuration stage of building Gnash.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">K</h3><dl><dt>
+ Klash
+ </dt><dd><p>
+ <span class="emphasis"><em>Klash</em></span> was the name given to
the stand-alone
+ instance of <span class="application">Gnash</span> which used the KDE
GUI. It has been replaced with
+ an implementation using Qt. Some documentation may incorrectly
+ refer to the Konqueror plugin as <span
class="emphasis"><em>Klash</em></span>.
+ The plugin was renamed <span class="emphasis"><em>Kpart</em></span>.
+ </p></dd><dt>
+ Kpart
+ </dt><dd><p>
+ <span class="emphasis"><em>Kpart</em></span> is a plugin for
Konqueror which is
+ enabled with the <a href="#">configuration option</a>
+ <span class="emphasis"><em>--enable-klash</em></span>.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">L</h3><dl><dt>
+ libmad
+ </dt><dd><p>
+ libmad is a mp3-decoding library, which can be used by Gnash's
+ sound handler to decode mp3-audio.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">M</h3><dl><dt>
+ Mesa
+ </dt><dd><p>
+ <span class="emphasis"><em>Mesa</em></span> is the free software
OpenGL
+ implementation. <span class="application">Gnash</span> documentation
will sometimes use the
+ glossterms 'OpenGL' and 'Mesa' interchangeably.
+ </p></dd><dt>
+ Ming
+ </dt><dd><p>
+ Ming is a C library for generating SWF ("Flash") format
+ movies, plus a set of wrappers for using the library. It is
+ used by the Gnash project for generating testcases.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">N</h3><dl><dt>
+ Nellymoser
+ </dt><dd><p>
+ Nellymoser is a proprietary audio codec introduced in the
+ Flash Player in version 6. For more information, please see
+ Wikipedia.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">O</h3><dl><dt>
+ OpenGL
+ </dt><dd><p>
+ OpenGL (Open Graphics Library) is a standard specification
+ defining a cross-language cross-platform API for writing
+ applications that produce 3D and 2D computer
+ graphics. Accelerated graphic cards usually provide OpenGL at
+ the hardware level. Please refer to Wikipedia for availability
+ of free software OpenGL hardware drivers. A free software
+ implementation of the API is available (Mesa). OpenGL can be
+ used as a renderer in Gnash.
+ </p></dd><dt>
+ ORM
+ </dt><dd><p>
+ ORM is a system for ensuring the rights of the creator over a piece
of digital content. It is more passive than DRM.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">P</h3><dl><dt>
+ plugin
+ </dt><dd><p>
+ The glossterm <span class="emphasis"><em>plugin</em></span> is used
in <span class="application">Gnash</span> to
+ refer to both any <span class="application">Gnash</span> browser
plugin, as well as the Firefox
+ plugin specifically. The Konqueror plugin is called
+ <span class="emphasis"><em>Kpart</em></span>. Sometimes, the term is
used in
+ an even more generic sense to refer to
+ <span class="emphasis"><em>extensions</em></span>.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">Q</h3><dl><dt>
+ Qt
+ </dt><dd><p>
+ Qt is a GUI library which is used by KDE. The plugin version
+ of Gnash using this GUI library is Kpart. The standalone
+ version is enabled with --enable-gui=kde.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">R</h3><dl><dt>
+ renderer
+ </dt><dd><p>
+ The <span class="emphasis"><em>renderer</em></span> is the subsystem
of <span class="application">Gnash</span>
+ which renders content. Only one renderer may be used; it is
+ selected at configuration time if building from source.
+ </p><p>
+ Available renderers are: AGG, OpenGL, and Cairo. In terms of
+ feature completeness, AGG comes first; followed by OpenGL and
+ then Cairo. In most cases, AGG is preferred for performance,
+ except cases where it is beneficial to have hardware accelerated
+ rendering (for example, when you have a very slow CPU but a very
+ fast graphics card). In this case OpenGL should be used.
+ </p></dd><dt>
+ RTMP
+ </dt><dd><p>
+ RTMP is the Real Time Messaging Protocol primarily used with
+ to stream audio and video over the internet to the Flash
+ Player client.
+ </p></dd><dt>
+ RTMPT
+ </dt><dd><p>
+ RTMPT is basically a HTTP wrapper around the RTMP protocol
+ that is sent using POST requests from the client to the
+ server. Because of the non-persistent nature of HTTP
+ connections, RTMPT requires the clients to poll for updates
+ periodically in order to get notified about events that are
+ generated by the server or other clients.
+ </p></dd><dt>
+ RTMPTS
+ </dt><dd><p>
+ RTMPTS is the same as RTMPT, but instead of being a HTTP
+ wrapper, it is a HTTP SSL wrapper (HTTP secure connection).
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">S</h3><dl><dt>
+ SDL
+ </dt><dd><p>
+ Simple DirectMedia Layer is a cross-platform multimedia free
+ software library that creates an abstraction over various
+ platforms' graphics, sound, and input APIs. Gnash can use it
+ as a GUI and/or as a sound handler. Note that the two usages
+ are independent of each other: you can use it for a task and
+ not for the other if you wish. At time or writing (2007-01-11)
+ the SDL GUI lacks menus and a performant input event
+ architecture; the SDL sound handler is the most feature rich,
+ supporting Video through ffmpeg.
+ </p></dd><dt>
+ sound handler
+ </dt><dd><p>
+ The <span class="emphasis"><em>sound handler</em></span> is the part
of <span class="application">Gnash</span>
+ which handles both event sounds and streaming sound. Audio
+ from external sources are also handled through the sound handler
+ when SDL is used. The sound handler must be selected during
+ configuration of Gnash when compiling.
+ </p><p>
+ There are currently two sound handlers available in <span
class="application">Gnash</span>:
+ SDL and Gstreamer. The SDL sound handler uses ffmpeg or
+ libmad for decoding mp3-audio, although it can be built without
+ mp3-support. The Gstreamer-sound handler uses the available
+ plugins to decode the audio, so it might not work if some
+ important plugins are missing. The SDL sound handler is
+ recommended.
+ </p></dd><dt>
+ sprite
+ </dt><dd><p>
+ A sprite is an element of an Flash Movie. It's basically a
+ Movie inside another, having its own timeline.
+ </p></dd><dt>
+ Stage
+ </dt><dd><p>
+ The visible area of a Flash movie. The name derives from a
theater analogy. Graphical elements are referred to as
+ characters.
+ </p></dd><dt>
+ SWF
+ </dt><dd><p>
+ <span class="emphasis"><em>SWF</em></span> is the file format for
+ <span class="emphasis"><em>Flash</em></span> movies.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">T</h3><dl><dt>
+ Tamarin
+ </dt><dd><p>
+ The Tamarin project seeks to create an open source
+ implementation of the ECMAScript 4th edition language
+ specification. The code is used by Adobe as part of the
+ ActionScript Virtual Machine within the Adobe Flash
+ Player. Gnash does not use Tamarin; it already has a working
+ virtual server and most ActionScript classes are implemented.
+ </p></dd><dt>
+ timeline
+ </dt><dd><p>
+ In Flash technology, a timeline is a sequence of "frames". A
+ single Flash movie can contain multiple timelines, each
+ independently controlled (STOP or PLAY). At regular intervals
+ (FPS) the player advances all timelines in PLAY mode to the
+ next frame, looping back when last frame is reached.
+ </p></dd></dl></div><div class="glossdiv"><h3
class="title">X</h3><dl><dt>
+ X.org
+ </dt><dd><p>
+ X.org is the most commonly used X server; it was forked from
+ XFree86.
+ </p></dd></dl></div></div><div class="chapter" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="authors"></a>Chapter 5.
Authors</h2></div></div></div><p>
+ <span class="application">Gnash</span> is maintained by Rob Savoye.
Other active developers
+ are: Sandro Santilli, Bastiaan Jacques, Udo Giacomozzi, Chad
+ Musick, Benjamin Wolsey, and Zou Lunkai. Please send all
+ comments and suggestions to <code class="email"><<a
href="mailto:address@hidden";>address@hidden
+ </a>></code>. Past and sometimes current developers are Tomas
+ Groth and Markus Gothe.
+ </p><p>
+ <span class="application">Gnash</span> was initially derived from
<span class="application">GameSWF</span>.
+ <span class="application">GameSWF</span> is maintained by
+ Thatcher Ulrich <code class="email"><<a
href="mailto:address@hidden";>address@hidden</a>></code>. The following
+ people contributed to <span class="application">GameSWF</span>:
+ Mike Shaver, Thierry Berger-Perrin,
+ Ignacio Castaño, Willem Kokke, Vitaly Alexeev, Alexander Streit,
+ and Rob Savoye.
+ </p></div><div class="appendix" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="fdl"></a>Appendix A. GNU
Free Documentation License</h2></div><div><p class="releaseinfo">
+ Version 1.1, March 2000
+ </p></div><div><p class="copyright">Copyright © 2000 Free Software
Foundation, Inc.</p></div><div><div class="legalnotice"><a
name="fdl-legalnotice"></a><p>
+ </p><div class="address"><p>Free Software Foundation, Inc. <span
class="street">59 Temple Place, <br>
+ Suite 330</span>, <span class="city">Boston</span>, <span
class="state">MA</span> <br>
+ <span class="postcode">02111-1307</span> <span
class="country">USA</span></p></div><p>
+ Everyone is permitted to copy and distribute verbatim copies of this
+ license document, but changing it is not allowed.
+ </p></div></div></div></div><div class="toc"><p><b>Table of
Contents</b></p><dl><dt><span class="sect1"><a href="#fdl-preamble">0.
PREAMBLE</a></span></dt><dt><span class="sect1"><a href="#fdl-section1">1.
APPLICABILITY AND DEFINITIONS</a></span></dt><dt><span class="sect1"><a
href="#fdl-section2">2. VERBATIM COPYING</a></span></dt><dt><span
class="sect1"><a href="#fdl-section3">3. COPYING IN
QUANTITY</a></span></dt><dt><span class="sect1"><a href="#fdl-section4">4.
MODIFICATIONS</a></span></dt><dt><span class="sect1"><a href="#fdl-section5">5.
COMBINING DOCUMENTS</a></span></dt><dt><span class="sect1"><a
href="#fdl-section6">6. COLLECTIONS OF DOCUMENTS</a></span></dt><dt><span
class="sect1"><a href="#fdl-section7">7. AGGREGATION WITH INDEPENDENT
WORKS</a></span></dt><dt><span class="sect1"><a href="#fdl-section8">8.
TRANSLATION</a></span></dt><dt><span class="sect1"><a href="#fdl-section9">9.
TERMINATION</a></span></dt><dt><span class="sect1"><a href="#fdl-section10">10.
FUTURE REVISIONS OF THIS LICENSE</a></span></dt><dt><span class="sect1"><a
href="#fdl-using">Addendum</a></span></dt></dl></div><div class="sect1"
lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear:
both"><a name="fdl-preamble"></a>0. PREAMBLE</h2></div></div></div><p>
+ The purpose of this License is to make a manual, textbook, or
+ other written document "free" in the sense of
+ freedom: to assure everyone the effective freedom to copy and
+ redistribute it, with or without modifying it, either
+ commercially or non-commercially. Secondarily, this License
+ preserves for the author and publisher a way to get credit for
+ their work, while not being considered responsible for
+ modifications made by others.
+ </p><p>
+ This License is a kind of "copyleft", which means
+ that derivative works of the document must themselves be free in
+ the same sense. It complements the GNU General Public License,
+ which is a copyleft license designed for free software.
+ </p><p>
+ We have designed this License in order to use it for manuals for
+ free software, because free software needs free documentation: a
+ free program should come with manuals providing the same
+ freedoms that the software does. But this License is not limited
+ to software manuals; it can be used for any textual work,
+ regardless of subject matter or whether it is published as a
+ printed book. We recommend this License principally for works
+ whose purpose is instruction or reference.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section1"></a>1. APPLICABILITY AND
DEFINITIONS</h2></div></div></div><p><a name="fdl-document"></a>
+ This License applies to any manual or other work that contains a
+ notice placed by the copyright holder saying it can be
+ distributed under the terms of this License. The
+ "Document", below, refers to any such manual or
+ work. Any member of the public is a licensee, and is addressed
+ as "you".
+ </p><p><a name="fdl-modified"></a>
+ A "Modified Version" of the Document means any work
+ containing the Document or a portion of it, either copied
+ verbatim, or with modifications and/or translated into another
+ language.
+ </p><p><a name="fdl-secondary"></a>
+ A "Secondary Section" is a named appendix or a
+ front-matter section of the <a href="#fdl-document">Document</a> that
deals exclusively
+ with the relationship of the publishers or authors of the
+ Document to the Document's overall subject (or to related
+ matters) and contains nothing that could fall directly within
+ that overall subject. (For example, if the Document is in part a
+ textbook of mathematics, a Secondary Section may not explain any
+ mathematics.) The relationship could be a matter of historical
+ connection with the subject or with related matters, or of
+ legal, commercial, philosophical, ethical or political position
+ regarding them.
+ </p><p><a name="fdl-invariant"></a>
+ The "Invariant Sections" are certain <a href="#fdl-secondary"> Secondary
Sections</a> whose titles
+ are designated, as being those of Invariant Sections, in the
+ notice that says that the <a href="#fdl-document">Document</a> is
released under this
+ License.
+ </p><p><a name="fdl-cover-texts"></a>
+ The "Cover Texts" are certain short passages of
+ text that are listed, as Front-Cover Texts or Back-Cover Texts,
+ in the notice that says that the <a href="#fdl-document">Document</a> is
released under this
+ License.
+ </p><p><a name="fdl-transparent"></a>
+ A "Transparent" copy of the <a href="#fdl-document"> Document</a> means
a machine-readable
+ copy, represented in a format whose specification is available
+ to the general public, whose contents can be viewed and edited
+ directly and straightforwardly with generic text editors or (for
+ images composed of pixels) generic paint programs or (for
+ drawings) some widely available drawing editor, and that is
+ suitable for input to text formatters or for automatic
+ translation to a variety of formats suitable for input to text
+ formatters. A copy made in an otherwise Transparent file format
+ whose markup has been designed to thwart or discourage
+ subsequent modification by readers is not Transparent. A copy
+ that is not "Transparent" is called "Opaque".
+ </p><p>
+ Examples of suitable formats for Transparent copies include
+ plain ASCII without markup, Texinfo input format, LaTeX input
+ format, SGML or XML using a publicly available DTD, and
+ standard-conforming simple HTML designed for human
+ modification. Opaque formats include PostScript, PDF,
+ proprietary formats that can be read and edited only by
+ proprietary word processors, SGML or XML for which the DTD
+ and/or processing tools are not generally available, and the
+ machine-generated HTML produced by some word processors for
+ output purposes only.
+ </p><p><a name="fdl-title-page"></a>
+ The "Title Page" means, for a printed book, the
+ title page itself, plus such following pages as are needed to
+ hold, legibly, the material this License requires to appear in
+ the title page. For works in formats which do not have any title
+ page as such, "Title Page" means the text near the
+ most prominent appearance of the work's title, preceding the
+ beginning of the body of the text.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section2"></a>2. VERBATIM COPYING</h2></div></div></div><p>
+ You may copy and distribute the <a href="#fdl-document">Document</a> in
any medium, either
+ commercially or noncommercially, provided that this License, the
+ copyright notices, and the license notice saying this License
+ applies to the Document are reproduced in all copies, and that
+ you add no other conditions whatsoever to those of this
+ License. You may not use technical measures to obstruct or
+ control the reading or further copying of the copies you make or
+ distribute. However, you may accept compensation in exchange for
+ copies. If you distribute a large enough number of copies you
+ must also follow the conditions in <a href="#fdl-section3" title="3.
COPYING IN QUANTITY">section 3</a>.
+ </p><p>
+ You may also lend copies, under the same conditions stated
+ above, and you may publicly display copies.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section3"></a>3. COPYING IN QUANTITY</h2></div></div></div><p>
+ If you publish printed copies of the <a
href="#fdl-document">Document</a> numbering more than 100,
+ and the Document's license notice requires <a
href="#fdl-cover-texts">Cover Texts</a>, you must enclose
+ the copies in covers that carry, clearly and legibly, all these
+ Cover Texts: Front-Cover Texts on the front cover, and
+ Back-Cover Texts on the back cover. Both covers must also
+ clearly and legibly identify you as the publisher of these
+ copies. The front cover must present the full title with all
+ words of the title equally prominent and visible. You may add
+ other material on the covers in addition. Copying with changes
+ limited to the covers, as long as they preserve the title of the
+ <a href="#fdl-document">Document</a> and satisfy these
+ conditions, can be treated as verbatim copying in other
+ respects.
+ </p><p>
+ If the required texts for either cover are too voluminous to fit
+ legibly, you should put the first ones listed (as many as fit
+ reasonably) on the actual cover, and continue the rest onto
+ adjacent pages.
+ </p><p>
+ If you publish or distribute <a href="#fdl-transparent">Opaque</a>
copies of the <a href="#fdl-document">Document</a> numbering more than 100,
+ you must either include a machine-readable <a
href="#fdl-transparent">Transparent</a> copy along with
+ each Opaque copy, or state in or with each Opaque copy a
+ publicly-accessible computer-network location containing a
+ complete Transparent copy of the Document, free of added
+ material, which the general network-using public has access to
+ download anonymously at no charge using public-standard network
+ protocols. If you use the latter option, you must take
+ reasonably prudent steps, when you begin distribution of Opaque
+ copies in quantity, to ensure that this Transparent copy will
+ remain thus accessible at the stated location until at least one
+ year after the last time you distribute an Opaque copy (directly
+ or through your agents or retailers) of that edition to the
+ public.
+ </p><p>
+ It is requested, but not required, that you contact the authors
+ of the <a href="#fdl-document">Document</a> well before
+ redistributing any large number of copies, to give them a chance
+ to provide you with an updated version of the Document.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section4"></a>4. MODIFICATIONS</h2></div></div></div><p>
+ You may copy and distribute a <a href="#fdl-modified">Modified
Version</a> of the <a href="#fdl-document">Document</a> under the conditions of
+ sections <a href="#fdl-section2" title="2. VERBATIM COPYING">2</a> and
<a href="#fdl-section3" title="3. COPYING IN QUANTITY">3</a> above, provided
that you release
+ the Modified Version under precisely this License, with the
+ Modified Version filling the role of the Document, thus
+ licensing distribution and modification of the Modified Version
+ to whoever possesses a copy of it. In addition, you must do
+ these things in the Modified Version:
+ </p><div class="itemizedlist"><ul type="opencircle"><li
style="list-style-type: circle"><p><b>A. </b>
+ Use in the <a href="#fdl-title-page">Title
+ Page</a> (and on the covers, if any) a title distinct
+ from that of the <a href="#fdl-document">Document</a>, and from
those of
+ previous versions (which should, if there were any, be
+ listed in the History section of the Document). You may
+ use the same title as a previous version if the original
+ publisher of that version gives permission.
+ </p></li><li style="list-style-type: circle"><p><b>B. </b>
+ List on the <a href="#fdl-title-page">Title
+ Page</a>, as authors, one or more persons or entities
+ responsible for authorship of the modifications in the
+ <a href="#fdl-modified">Modified Version</a>,
+ together with at least five of the principal authors of
+ the <a href="#fdl-document">Document</a> (all of
+ its principal authors, if it has less than five).
+ </p></li><li style="list-style-type: circle"><p><b>C. </b>
+ State on the <a href="#fdl-title-page">Title
+ Page</a> the name of the publisher of the <a
href="#fdl-modified">Modified Version</a>, as the
+ publisher.
+ </p></li><li style="list-style-type: circle"><p><b>D. </b>
+ Preserve all the copyright notices of the <a
href="#fdl-document">Document</a>.
+ </p></li><li style="list-style-type: circle"><p><b>E. </b>
+ Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.
+ </p></li><li style="list-style-type: circle"><p><b>F. </b>
+ Include, immediately after the copyright notices, a
+ license notice giving the public permission to use the
+ <a href="#fdl-modified">Modified Version</a> under
+ the terms of this License, in the form shown in the
+ Addendum below.
+ </p></li><li style="list-style-type: circle"><p><b>G. </b>
+ Preserve in that license notice the full lists of <a
href="#fdl-invariant"> Invariant Sections</a> and
+ required <a href="#fdl-cover-texts">Cover
+ Texts</a> given in the <a href="#fdl-document">Document's</a>
license notice.
+ </p></li><li style="list-style-type: circle"><p><b>H. </b>
+ Include an unaltered copy of this License.
+ </p></li><li style="list-style-type: circle"><p><b>I. </b>
+ Preserve the section entitled "History", and
+ its title, and add to it an item stating at least the
+ title, year, new authors, and publisher of the <a
href="#fdl-modified">Modified Version </a>as given on
+ the <a href="#fdl-title-page">Title Page</a>. If
+ there is no section entitled "History" in the
+ <a href="#fdl-document">Document</a>, create one
+ stating the title, year, authors, and publisher of the
+ Document as given on its Title Page, then add an item
+ describing the Modified Version as stated in the previous
+ sentence.
+ </p></li><li style="list-style-type: circle"><p><b>J. </b>
+ Preserve the network location, if any, given in the <a
href="#fdl-document">Document</a> for public access
+ to a <a href="#fdl-transparent">Transparent</a>
+ copy of the Document, and likewise the network locations
+ given in the Document for previous versions it was based
+ on. These may be placed in the "History"
+ section. You may omit a network location for a work that
+ was published at least four years before the Document
+ itself, or if the original publisher of the version it
+ refers to gives permission.
+ </p></li><li style="list-style-type: circle"><p><b>K. </b>
+ In any section entitled "Acknowledgements" or
+ "Dedications", preserve the section's title,
+ and preserve in the section all the substance and tone of
+ each of the contributor acknowledgements and/or
+ dedications given therein.
+ </p></li><li style="list-style-type: circle"><p><b>L. </b>
+ Preserve all the <a href="#fdl-invariant">Invariant
+ Sections</a> of the <a href="#fdl-document">Document</a>, unaltered
in their
+ text and in their titles. Section numbers or the
+ equivalent are not considered part of the section titles.
+ </p></li><li style="list-style-type: circle"><p><b>M. </b>
+ Delete any section entitled
+ "Endorsements". Such a section may not be
+ included in the <a href="#fdl-modified">Modified
+ Version</a>.
+ </p></li><li style="list-style-type: circle"><p><b>N. </b>
+ Do not retitle any existing section as
+ "Endorsements" or to conflict in title with
+ any <a href="#fdl-invariant">Invariant
+ Section</a>.
+ </p></li></ul></div><p>
+ If the <a href="#fdl-modified">Modified Version</a>
+ includes new front-matter sections or appendices that qualify as
+ <a href="#fdl-secondary">Secondary Sections</a> and
+ contain no material copied from the Document, you may at your
+ option designate some or all of these sections as invariant. To
+ do this, add their titles to the list of <a
href="#fdl-invariant">Invariant Sections</a> in the
+ Modified Version's license notice. These titles must be
+ distinct from any other section titles.
+ </p><p>
+ You may add a section entitled "Endorsements",
+ provided it contains nothing but endorsements of your <a
href="#fdl-modified">Modified Version</a> by various
+ parties--for example, statements of peer review or that the text
+ has been approved by an organization as the authoritative
+ definition of a standard.
+ </p><p>
+ You may add a passage of up to five words as a <a
href="#fdl-cover-texts">Front-Cover Text</a>, and a passage
+ of up to 25 words as a <a href="#fdl-cover-texts">Back-Cover Text</a>,
to the end of
+ the list of <a href="#fdl-cover-texts">Cover Texts</a>
+ in the <a href="#fdl-modified">Modified Version</a>.
+ Only one passage of Front-Cover Text and one of Back-Cover Text
+ may be added by (or through arrangements made by) any one
+ entity. If the <a href="#fdl-document">Document</a>
+ already includes a cover text for the same cover, previously
+ added by you or by arrangement made by the same entity you are
+ acting on behalf of, you may not add another; but you may
+ replace the old one, on explicit permission from the previous
+ publisher that added the old one.
+ </p><p>
+ The author(s) and publisher(s) of the <a
href="#fdl-document">Document</a> do not by this License
+ give permission to use their names for publicity for or to
+ assert or imply endorsement of any <a href="#fdl-modified">Modified
Version </a>.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section5"></a>5. COMBINING DOCUMENTS</h2></div></div></div><p>
+ You may combine the <a href="#fdl-document">Document</a>
+ with other documents released under this License, under the
+ terms defined in <a href="#fdl-section4" title="4.
MODIFICATIONS">section 4</a>
+ above for modified versions, provided that you include in the
+ combination all of the <a href="#fdl-invariant">Invariant
+ Sections</a> of all of the original documents, unmodified,
+ and list them all as Invariant Sections of your combined work in
+ its license notice.
+ </p><p>
+ The combined work need only contain one copy of this License,
+ and multiple identical <a href="#fdl-invariant">Invariant
+ Sections</a> may be replaced with a single copy. If there are
+ multiple Invariant Sections with the same name but different
+ contents, make the title of each such section unique by adding
+ at the end of it, in parentheses, the name of the original
+ author or publisher of that section if known, or else a unique
+ number. Make the same adjustment to the section titles in the
+ list of Invariant Sections in the license notice of the combined
+ work.
+ </p><p>
+ In the combination, you must combine any sections entitled
+ "History" in the various original documents,
+ forming one section entitled "History"; likewise
+ combine any sections entitled "Acknowledgements",
+ and any sections entitled "Dedications". You must
+ delete all sections entitled "Endorsements."
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section6"></a>6. COLLECTIONS OF DOCUMENTS</h2></div></div></div><p>
+ You may make a collection consisting of the <a
href="#fdl-document">Document</a> and other documents
+ released under this License, and replace the individual copies
+ of this License in the various documents with a single copy that
+ is included in the collection, provided that you follow the
+ rules of this License for verbatim copying of each of the
+ documents in all other respects.
+ </p><p>
+ You may extract a single document from such a collection, and
+ distribute it individually under this License, provided you
+ insert a copy of this License into the extracted document, and
+ follow this License in all other respects regarding verbatim
+ copying of that document.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section7"></a>7. AGGREGATION WITH INDEPENDENT
WORKS</h2></div></div></div><p>
+ A compilation of the <a href="#fdl-document">Document</a> or its
derivatives with
+ other separate and independent documents or works, in or on a
+ volume of a storage or distribution medium, does not as a whole
+ count as a <a href="#fdl-modified">Modified Version</a>
+ of the Document, provided no compilation copyright is claimed
+ for the compilation. Such a compilation is called an
+ "aggregate", and this License does not apply to the
+ other self-contained works thus compiled with the Document , on
+ account of their being thus compiled, if they are not themselves
+ derivative works of the Document. If the <a
href="#fdl-cover-texts">Cover Text</a> requirement of <a href="#fdl-section3"
title="3. COPYING IN QUANTITY">section 3</a> is applicable to these
+ copies of the Document, then if the Document is less than one
+ quarter of the entire aggregate, the Document's Cover Texts may
+ be placed on covers that surround only the Document within the
+ aggregate. Otherwise they must appear on covers around the whole
+ aggregate.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section8"></a>8. TRANSLATION</h2></div></div></div><p>
+ Translation is considered a kind of modification, so you may
+ distribute translations of the <a href="#fdl-document">Document</a>
under the terms of <a href="#fdl-section4" title="4. MODIFICATIONS">section
4</a>. Replacing <a href="#fdl-invariant"> Invariant Sections</a> with
+ translations requires special permission from their copyright
+ holders, but you may include translations of some or all
+ Invariant Sections in addition to the original versions of these
+ Invariant Sections. You may include a translation of this
+ License provided that you also include the original English
+ version of this License. In case of a disagreement between the
+ translation and the original English version of this License,
+ the original English version will prevail.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section9"></a>9. TERMINATION</h2></div></div></div><p>
+ You may not copy, modify, sublicense, or distribute the <a
href="#fdl-document">Document</a> except as expressly
+ provided for under this License. Any other attempt to copy,
+ modify, sublicense or distribute the Document is void, and will
+ automatically terminate your rights under this License. However,
+ parties who have received copies, or rights, from you under this
+ License will not have their licenses terminated so long as such
+ parties remain in full compliance.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section10"></a>10. FUTURE REVISIONS OF THIS
LICENSE</h2></div></div></div><p>
+ The <a href="http://www.gnu.org/fsf/fsf.html"; target="_top">Free Software
+ Foundation</a> may publish new, revised versions of the GNU
+ Free Documentation License from time to time. Such new versions
+ will be similar in spirit to the present version, but may differ
+ in detail to address new problems or concerns. See <a
href="http://www.gnu.org/copyleft";
target="_top">http://www.gnu.org/copyleft/</a>.
+ </p><p>
+ Each version of the License is given a distinguishing version
+ number. If the <a href="#fdl-document">Document</a>
+ specifies that a particular numbered version of this License
+ "or any later version" applies to it, you have the
+ option of following the terms and conditions either of that
+ specified version or of any later version that has been
+ published (not as a draft) by the Free Software Foundation. If
+ the Document does not specify a version number of this License,
+ you may choose any version ever published (not as a draft) by
+ the Free Software Foundation.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-using"></a>Addendum</h2></div></div></div><p>
+ To use this License in a document you have written, include a copy of
+ the License in the document and put the following copyright and
+ license notices just after the title page:
+ </p><div class="blockquote"><blockquote class="blockquote"><p>
+ Copyright 2008, Free Software Foundation.
+ </p><p>
+ Permission is granted to copy, distribute and/or modify this
+ document under the terms of the GNU Free Documentation
+ License, Version 1.1 or any later version published by the
+ Free Software Foundation; with no<a href="#fdl-invariant">Invariant
Sections</a>, with no <a href="#fdl-cover-texts">Front-Cover Texts</a>,
+ and with no <a href="#fdl-cover-texts">Back-Cover
+ Texts</a>. A copy of the license is included in
+ the section entitled "GNU Free Documentation License".
+ </p></blockquote></div><p>
+ If your document contains nontrivial examples of program code,
+ we recommend releasing these examples in parallel under your
+ choice of free software license, such as the <a
href="http://www.gnu.org/copyleft/gpl.html"; target="_top"> GNU General Public
+ License</a>, to permit their use in free software.
+ </p></div></div></div></body></html>
Index: gnashuser.ref.in
===================================================================
RCS file: gnashuser.ref.in
diff -N gnashuser.ref.in
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ gnashuser.ref.in 1 Mar 2008 15:18:23 -0000 1.1
@@ -0,0 +1,771 @@
+<html><head><meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1"><title>Gnash Reference Manual</title><meta name="generator"
content="DocBook XSL Stylesheets V1.72.0"></head><body bgcolor="white"
text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"
lang="en"><div class="titlepage"><div><div><h1 class="title"><a
name="index"></a>Gnash Reference Manual</h1></div><div><p class="releaseinfo">
+ This manual describes version 0.8.2 of Gnash.
+ </p></div><div><p class="copyright">Copyright © 2005, 2006, 2007, 2008
Free Software Foundation</p></div><div><div class="legalnotice"><a
name="legalnotice"></a><p>
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the <a href="#fdl" title="Appendix A. GNU Free
Documentation License"><em class="citetitle">GNU
+ Free Documentation License</em></a>, Version 1.1 or any later
+ version published by the Free Software Foundation with no Invariant
+ Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find
+ a copy of the GFDL at this
+ <a href="#fdl" title="Appendix A. GNU Free Documentation License">link</a>
or in the file COPYING-DOCS
+ distributed with this manual.
+ </p></div></div><div><div class="revhistory"><table border="1" width="100%"
summary="Revision history"><tr><th align="left" valign="top"
colspan="2"><b>Revision History</b></th></tr><tr><td align="left">Revision
Gnash User Manual version 0.4</td><td align="left">Feb 2008</td></tr><tr><td
align="left" colspan="2">
+ <p class="author">Rob Savoye
+ <code class="email"><<a
href="mailto:address@hidden";>address@hidden</a>></code>
+ The end user parts of the manual have been pulled out of
+ the original version of the manual, and rewritten. This
+ is now a reference manual only.
+ </p>
+
+ <p class="publisher">Open Media Now! Foundation</p>
+ </td></tr></table></div></div></div><hr></div><div class="toc"><p><b>Table
of Contents</b></p><dl><dt><span class="chapter"><a href="#intro">1.
Introduction</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#audience">Audience</a></span></dt><dt><span class="sect1"><a
href="#runs-on">What Is Supported ?</a></span></dt></dl></dd><dt><span
class="chapter"><a href="#rtmp">2. RTMP
Protocol</a></span></dt><dd><dl><dt><span class="sect1"><a href="#amf">AMF
Format</a></span></dt></dl></dd><dt><span class="chapter"><a href="#authors">3.
Authors</a></span></dt><dt><span class="appendix"><a href="#fdl">A. GNU Free
Documentation License</a></span></dt><dd><dl><dt><span class="sect1"><a
href="#fdl-preamble">0. PREAMBLE</a></span></dt><dt><span class="sect1"><a
href="#fdl-section1">1. APPLICABILITY AND DEFINITIONS</a></span></dt><dt><span
class="sect1"><a href="#fdl-section2">2. VERBATIM
COPYING</a></span></dt><dt><span class="sect1"><a href="#fdl-section3">3.
COPYING IN QUANTITY</a></span></dt><dt><span class="sect1"><a
href="#fdl-section4">4. MODIFICATIONS</a></span></dt><dt><span class="sect1"><a
href="#fdl-section5">5. COMBINING DOCUMENTS</a></span></dt><dt><span
class="sect1"><a href="#fdl-section6">6. COLLECTIONS OF
DOCUMENTS</a></span></dt><dt><span class="sect1"><a href="#fdl-section7">7.
AGGREGATION WITH INDEPENDENT WORKS</a></span></dt><dt><span class="sect1"><a
href="#fdl-section8">8. TRANSLATION</a></span></dt><dt><span class="sect1"><a
href="#fdl-section9">9. TERMINATION</a></span></dt><dt><span class="sect1"><a
href="#fdl-section10">10. FUTURE REVISIONS OF THIS
LICENSE</a></span></dt><dt><span class="sect1"><a
href="#fdl-using">Addendum</a></span></dt></dl></dd></dl></div><div
class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a
name="intro"></a>Chapter 1. Introduction</h2></div></div></div><div
class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a
href="#audience">Audience</a></span></dt><dt><span class="sect1"><a
href="#runs-on">What Is Supported ?</a></span></dt></dl></div><p>
+ <span class="application">Gnash</span> is a free SWF movie player. It is
available as a
+ stand-alone application or as a plugin for several popular
+ web browsers. It supports playing media from a disk or streaming
+ over a network connection. Some popular video sharing sites like
+ YouTube are supported from a wide vaariety of devices from
+ embedded ones to modern desktops.
+ </p><p>
+ <span class="application">Gnash</span> has a better focus on security,
allowing the user tight
+ control of all network or disk based I/O. Gnash also supports
+ extending ActionScript by creating your own. You can write
+ wrappers for any development library, and import them into the
+ player much like perl or python does.
+ </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a
name="audience"></a>Audience</h2></div></div></div><p>
+ This manual is primarily focused on users interested in how to
+ get Gnash installed from a package, and basic usage as a web
+ browser plugin. For more technical details, please refer to the
+ Gnash Reference manual.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="runs-on"></a>What Is Supported ?</h2></div></div></div><p>
+ Gnash is known to compile for most any POSIX and ANSI C++
+ conforming system if you have all the dependent libraries
+ installed. Systems we test on, and which Gnash is know to
+ run on are Ubuntu, Fedora, Debian, OpenBSD, NetBSD, FreeBSD,
+ Win32, and Darwin (OSX) primarily. Occasionally other platforms
+ are built, primarily by those distribution maintainers. This
+ includes BeOS, Haiku, Syllable, OS/2, Solaris, Slackware, and
+ Gentoo.
+ </p><p>
+ Gnash is a capable of reading up to SWF v9 files and opcodes,
+ but primarily supports SWF v7, with better SWF v8 and v9
+ support under heavy developement. With the 0.8.2 release,
+ Gnash includes initial parser support for SWF v8 and v9.
+ Not all ActionScript 2 classes are implemented yet, but all of the
+ most heavily used ones are. Many ActionScript 2 classes are
+ partially implemented; there is support for all of the
+ commonly used methods of each class.
+ </p><p>
+ Gnash has implemented about 80% of ActionScript v. 2.0, and has
+ begun implementing ActionScript v. 3.0. Gnash supports the
+ majority of Flash opcodes up to SWF version 9, and a wide
+ sampling of ActionScript classes for SWF version 8.
+ </p><p>
+ As ActionsScript 3 is a more developed version of
+ 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
+ easiest way for new Gnash developers to make a contribution
+ without a deep internal knpowledge of Gnash.
+ </p><p>
+ Gnash has included video support since early 2007, but this is
+ an every 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
+ 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
+ at: <a href="http://www.gnashdev.org/dev_snapshots/"; target="_top">
+ http://www.gnashdev.org/dev_snapshots</a>.
+ </p><p>
+ 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.
+ </p></div></div><div class="chapter" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="rtmp"></a>Chapter 2.
RTMP Protocol</h2></div></div></div><div class="toc"><p><b>Table of
Contents</b></p><dl><dt><span class="sect1"><a href="#amf">AMF
Format</a></span></dt></dl></div><p>
+ This document is based mostly on my own reverse engineering of the
+ RTMP protocol and AMF format. <span
class="emphasis"><em>tcpdump</em></span> and
+ <span class="emphasis"><em>ethereal</em></span> are your friend. Some
additional info that got
+ me started was from the <a href="http://www.osflash.org/red5";
target="_top">Red5</a>
+ project. <span class="emphasis"><em>Red5</em></span> is the only other
open source Flash
+ server. So some details are still vague, but as the implementation
+ appears to work, we'll figure out what they are later.
+ </p><p>
+ The Real Time Messaging Protocol was created by MacroMedia (now
+ Adobe) for delivering Flash objects and video over a network
+ connection. Currently the only servers which support this format
+ are the MacroMedia Media sever, and the Open Source Red5 project.
+ </p><p>
+ This is a simple protocol, optimized for poor bandwidth
+ connections. It can support up to 64 concurrent streams over the
+ same network connection. Part of each AMF packet header contains
+ the index number of the stream. A single RTMP message can contain
+ multiple AMF packets.
+ </p><p>
+ An RTMP connection uses Tcp/ip port 1935. It is also possible to
+ tunnel RTMP over an HTTP connection using port 80. Each AMF packet
+ is 128 bytes long except for streaming audio, which has 64 byte
+ packets.
+ </p><p>
+ The basics of the RTMP protocol are as follows. All communications
+ are initiated by the client.
+ </p><div class="mediaobject" align="center"><img src="images/rtmp.png"
align="middle"></div><p>
+ </p><p>
+ 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
+ not be actually used by the protocol except as a handshake.
+ </p><p>
+ 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
+ the original data block as sent by the client.
+ </p><p>
+ 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.
+ </p><p>
+ The first AMF packet sent to the server contains the
+ <span class="emphasis"><em>connect</em></span> packet. This doesn't appear
to do
+ much but notify the server the client is happy with the
+ handshake, and ready to start reading packets.
+ </p><p>
+ The second packet is the <span
class="emphasis"><em>NetConnection</em></span> object from
+ the client. This ActionScript class is used by the Flash movie to
+ create the network connection to the server.
+ </p><p>
+ The third packet is the <span class="emphasis"><em>NetStream</em></span>
object from the
+ client. This is the ActionScript class used to specify the file to
+ be streamed by the server.
+ </p><p>
+ The RTMP packet for our example looks like this:
+
+ </p><pre class="programlisting">
+ 030000190000c91400000000020007connect00?f0000000000000030003app0200#
+ software/gnash/tests/1153948634.flv0008flashVer02000cLNX 6,0,82,0 0006
+ swfUrl02001dfile:///file|%2Ftmp%2Fout.swfc30005tcUrl\002\0004
+ rtmp://localhost/software/gnash/tests/1153948634.flv\000\000\t
+ \002\000\005userx
+ </pre><p>
+
+ We'll take this apart in a bit, but you can see how all three AMF
+ packets are in the same message. The message is received in
+ several 128 byte blocks, with the last one being less than
+ that. The total size of the RTMP message is in the header, so the
+ reader can tell if the entire message was read or not.
+ </p><p>
+ The RTMP header is first, followed by the connect message as an
+ ASCII string as the message body. The following AMF packet is the
+ <span class="emphasis"><em>NetConnection</em></span> 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
+ version number, which I assume is the version of the Flash player,
+ so the server knows what it is talking to.
+ </p><p>
+ The third packet is the one from <span
class="emphasis"><em>NetStream</em></span>, which
+ specifies the URL used for the movie, followed by the user name
+ for a semblance of security.
+ </p><p>
+ For the next level of detail, we'll explain the format of AMF. AMF
+ is used by the RTMP protocol to transfer data. Each Flash object
+ is encapsulated in an AMF packet, including streaming audio or
+ video.
+ </p><p>
+ The first byte of the RTMP header determines two things about the
+ rest of the message. The first 2 bits of this byte signify the
+ total size of the RTMP header. The RTMP header is of a variable
+ size, so this is important.
+
+ </p><div class="variablelist"><dl><dt><span
class="term">00</span></dt><dd><p>
+ This specifies the header contains 12 bytes, including
+ this one.
+ </p></dd><dt><span class="term">01</span></dt><dd><p>
+ This specifies the header contains 8 bytes, including this
+ one.
+ </p></dd><dt><span class="term">02</span></dt><dd><p>
+ This specifies the header contains 4 bytes, including this
+ one.
+ </p></dd><dt><span class="term">03</span></dt><dd><p>
+ This specifies the header contains 1 byte, so this is the
+ complete header.
+ </p></dd></dl></div><p>
+ </p><p>
+ The other 6 bits in this byte represent the AMF index. As a single
+ RTMP connection can support multiple data streams, this signifies
+ which stream this packet is for. Once an AMF object is fully
+ received by the client, the AMF index may be reused.
+ </p><p>
+ For messages with headers of at least 4 bytes, the next 3 bytes are
+ used by audio and video data packets, but at this time the meaning
+ of this field is unknown.
+ </p><p>
+ For messages with a 8 byte or larger header, the next 3 bytes
+ determine the size of the RTMP message being transmitted. Messages
+ with a 1 byte or 4 byte header use a standard size, 128 bytes for
+ video, and 64 bytes for audio.
+ </p><p>
+ For messages with an 8 byte or larger header, the next byte is the
+ type of the AMF object.
+
+ </p><div class="variablelist"><dl><dt><span
class="term">0x3</span></dt><dd><p>
+ This specifies the content type of the RTMP packet is the
+ number of bytes read. This is used to start the RTMP
+ connection.
+ </p></dd><dt><span class="term">0x4</span></dt><dd><p>
+ This specifies the content type of the RTMP message is a
+ <span class="emphasis"><em>ping</em></span> packet.
+ </p></dd><dt><span class="term">0x5</span></dt><dd><p>
+ This specifies the content type of the RTMP message is
+ server response of some type.
+ </p></dd><dt><span class="term">0x6</span></dt><dd><p>
+ This specifies the content type of the RTMP packet is
+ client request of some type.
+ </p></dd><dt><span class="term">0x8</span></dt><dd><p>
+ This specifies the content type of the RTMP packet is an
+ audio message.
+ </p></dd><dt><span class="term">0x9</span></dt><dd><p>
+ This specifies the content type of the RTMP message is a
+ video packet.
+ </p></dd><dt><span class="term">0x12</span></dt><dd><p>
+ This specifies the content type of the RTMP message is
+ notify.
+ </p></dd><dt><span class="term">0x13</span></dt><dd><p>
+ This specifies the content type of the RTMP message is
+ shared object.
+ </p></dd><dt><span class="term">0x14</span></dt><dd><p>
+ This specifies the content type of the RTMP message is
+ remote procedure call. This invokes the method of a Flash
+ class remotely.
+ </p></dd></dl></div><p>
+
+ </p><p>
+ There are two sets of data types to consider. One set is used by
+ the to specify the content type of the AMF object, the other is an
+ ActionScript data type tag used to denote which type of object is
+ being transferred.
+ </p><p>
+ The values of the initial type byte are:
+ </p><div class="variablelist"><dl><dt><span
class="term">0x0</span></dt><dd><p>
+ This specifies the data in the AMF packet is a numeric
+ value. All numeric values in Flash are 64 bit,
+ <span class="emphasis"><em>big-endian</em></span>.
+ </p></dd><dt><span class="term">0x1</span></dt><dd><p>
+ This specifies the data in the AMF packet is a boolean
+ value.
+ </p></dd><dt><span class="term">0x2</span></dt><dd><p>
+ This specifies the data in the AMF packet is an
+ <span class="emphasis"><em>ASCII</em></span> string.
+ </p></dd><dt><span class="term">0x3</span></dt><dd><p>
+ This specifies the data in the AMF packet is a Flash
+ object. The Flash object data type field further along in
+ the message specifies which type of ActionScript object it
+ is.
+ </p></dd><dt><span class="term">0x4</span></dt><dd><p>
+ This specifies the data in the AMF packet is a Flash
+ movie, ie. another Flash movie.
+ </p></dd><dt><span class="term">0x5</span></dt><dd><p>
+ This specifies the data in the AMF packet is a NULL
+ value. NULL is often used as the return code from calling
+ Flash functions.
+ </p></dd><dt><span class="term">0x6</span></dt><dd><p>
+ This specifies the data in the AMF packet is a
+ undefined. This is also used as the return code from
+ calling Flash functions.
+ </p></dd><dt><span class="term">0x7</span></dt><dd><p>
+ This specifies the data in the AMF packet is a reference.
+ </p></dd><dt><span class="term">0x8</span></dt><dd><p>
+ This specifies the data in the AMF packet is a ECMA
+ array.
+ </p></dd><dt><span class="term">0x9</span></dt><dd><p>
+ This specifies the data in the AMF packet is the end of an
+ object definition. As an object is transmitted with
+ multiple AMF packets, this lets the server know when the
+ end of the object is reached.
+ </p></dd><dt><span class="term">0xa</span></dt><dd><p>
+ This specifies the data in the AMF packet is a Strict
+ array.
+ </p></dd><dt><span class="term">0xb</span></dt><dd><p>
+ This specifies the data in the AMF packet is a date.
+ </p></dd><dt><span class="term">0xc</span></dt><dd><p>
+ This specifies the data in the AMF packet is a multi-byte
+ string. Multi-byte strings are used for international
+ language support to represent non <span
class="emphasis"><em>ASCII</em></span>
+ fonts.
+ </p></dd><dt><span class="term">0xd</span></dt><dd><p>
+ This specifies the data in the AMF packet is a an
+ unsupported feature.
+ </p></dd><dt><span class="term">0xe</span></dt><dd><p>
+ This specifies the data in the AMF packet is a record
+ set.
+ </p></dd><dt><span class="term">0xf</span></dt><dd><p>
+ This specifies the data in the AMF packet is a AML
+ object. XML objects are then parsed by the
+ <span class="emphasis"><em>XML</em></span> ActionScript class.
+ </p></dd><dt><span class="term">0x10</span></dt><dd><p>
+ This specifies the data in the AMF packet is a typed object.
+ </p></dd></dl></div><p>
+
+ </p><p>
+ For messages with a 12 byte header, the last 4 bytes are the
+ routing of the message. If the destination is the server, this
+ value is the NetStream object source. If the destination is the
+ client, this is the NetStream object for this RTMP message. A
+ value of 0x00000000 appears to be reserved for the NetConnection
+ object.
+ </p><p>
+ Multiple AMF streams can be contained in a single RTMP messages,
+ so it's important to check the index of each AMF packet.
+ </p><p>
+ An example RTMP header might look like this. (spaces added between
+ fields for clarity) All the numbers are in hex.
+
+ </p><pre class="screen">
+ 03 000019 0000c9 14 000000000
+ </pre><p>
+
+ </p><div class="variablelist"><dl><dt><span
class="term">03</span></dt><dd><p>
+ The first two bits of this byte are the size of the
+ header, which in this example is 00, for a 12 byte
+ header. The next 6 bits is the AMF stream index number,
+ which in this example is 0x3.
+ </p></dd><dt><span class="term">000019</span></dt><dd><p>
+ These 3 bytes currently have an unknown purpose.
+ </p></dd><dt><span class="term">000c9</span></dt><dd><p>
+ Since this example has a 12 byte header, this is the size
+ of the RTMP message, in this case 201 bytes.
+ </p></dd><dt><span class="term">14</span></dt><dd><p>
+ This is the content type of the RTMP message, which in
+ this case is to invoke a remote function call. (which we
+ later see is the connect function).
+ </p></dd><dt><span class="term">00000000</span></dt><dd><p>
+ The source is the NetConnection object used to start this
+ connection.
+ </p></dd></dl></div><p>
+
+ </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2
class="title" style="clear: both"><a name="amf"></a>AMF
Format</h2></div></div></div><p>
+ The AMF format is used in the LocalConnection, SharedObject,
+ NetConnection, and NetStream ActionScript classes. This is a means
+ of binary data interchange between Flash movies, or between a
+ Flash player and a Flash server.
+ </p><p>
+ Like the RTMP messages, an AMF packet header can be of a variable
+ 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.
+ </p><p>
+ The body of an AMF packet may look something like this
+ example. The spaces have been added for clarity.
+
+ </p><pre class="screen">
+ 02 0007 636f6e6e656374
+ </pre><p>
+
+ </p><div class="variablelist"><dl><dt><span
class="term">02</span></dt><dd><p>
+ This is a single byte header. The value of the first 2
+ bits is 0x3, and the AMF index is also 0x3.
+ </p></dd><dt><span class="term">0007</span></dt><dd><p>
+ This is the length in bytes of the string.
+ </p></dd><dt><span class="term">63 6f 6e 6e 65 63
74</span></dt><dd><p>
+ This is the string. Note that there is no null terminator
+ since the length is specified.
+ </p></dd></dl></div><p>
+
+ </p></div></div><div class="chapter" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="authors"></a>Chapter 3.
Authors</h2></div></div></div><p>
+ <span class="application">Gnash</span> is maintained by Rob Savoye.
Other active developers
+ are: Sandro Santilli, Bastiaan Jacques, Udo Giacomozzi, Chad
+ Musick, Benjamin Wolsey, and Zou Lunkai. Please send all
+ comments and suggestions to <code class="email"><<a
href="mailto:address@hidden";>address@hidden
+ </a>></code>. Past and sometimes current developers are Tomas
+ Groth and Markus Gothe.
+ </p><p>
+ <span class="application">Gnash</span> was initially derived from
<span class="application">GameSWF</span>.
+ <span class="application">GameSWF</span> is maintained by
+ Thatcher Ulrich <code class="email"><<a
href="mailto:address@hidden";>address@hidden</a>></code>. The following
+ people contributed to <span class="application">GameSWF</span>:
+ Mike Shaver, Thierry Berger-Perrin,
+ Ignacio Castaño, Willem Kokke, Vitaly Alexeev, Alexander Streit,
+ and Rob Savoye.
+ </p></div><div class="appendix" lang="en"><div
class="titlepage"><div><div><h2 class="title"><a name="fdl"></a>Appendix A. GNU
Free Documentation License</h2></div><div><p class="releaseinfo">
+ Version 1.1, March 2000
+ </p></div><div><p class="copyright">Copyright © 2000 Free Software
Foundation, Inc.</p></div><div><div class="legalnotice"><a
name="fdl-legalnotice"></a><p>
+ </p><div class="address"><p>Free Software Foundation, Inc. <span
class="street">59 Temple Place, <br>
+ Suite 330</span>, <span class="city">Boston</span>, <span
class="state">MA</span> <br>
+ <span class="postcode">02111-1307</span> <span
class="country">USA</span></p></div><p>
+ Everyone is permitted to copy and distribute verbatim copies of this
+ license document, but changing it is not allowed.
+ </p></div></div></div></div><div class="toc"><p><b>Table of
Contents</b></p><dl><dt><span class="sect1"><a href="#fdl-preamble">0.
PREAMBLE</a></span></dt><dt><span class="sect1"><a href="#fdl-section1">1.
APPLICABILITY AND DEFINITIONS</a></span></dt><dt><span class="sect1"><a
href="#fdl-section2">2. VERBATIM COPYING</a></span></dt><dt><span
class="sect1"><a href="#fdl-section3">3. COPYING IN
QUANTITY</a></span></dt><dt><span class="sect1"><a href="#fdl-section4">4.
MODIFICATIONS</a></span></dt><dt><span class="sect1"><a href="#fdl-section5">5.
COMBINING DOCUMENTS</a></span></dt><dt><span class="sect1"><a
href="#fdl-section6">6. COLLECTIONS OF DOCUMENTS</a></span></dt><dt><span
class="sect1"><a href="#fdl-section7">7. AGGREGATION WITH INDEPENDENT
WORKS</a></span></dt><dt><span class="sect1"><a href="#fdl-section8">8.
TRANSLATION</a></span></dt><dt><span class="sect1"><a href="#fdl-section9">9.
TERMINATION</a></span></dt><dt><span class="sect1"><a href="#fdl-section10">10.
FUTURE REVISIONS OF THIS LICENSE</a></span></dt><dt><span class="sect1"><a
href="#fdl-using">Addendum</a></span></dt></dl></div><div class="sect1"
lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear:
both"><a name="fdl-preamble"></a>0. PREAMBLE</h2></div></div></div><p>
+ The purpose of this License is to make a manual, textbook, or
+ other written document "free" in the sense of
+ freedom: to assure everyone the effective freedom to copy and
+ redistribute it, with or without modifying it, either
+ commercially or non-commercially. Secondarily, this License
+ preserves for the author and publisher a way to get credit for
+ their work, while not being considered responsible for
+ modifications made by others.
+ </p><p>
+ This License is a kind of "copyleft", which means
+ that derivative works of the document must themselves be free in
+ the same sense. It complements the GNU General Public License,
+ which is a copyleft license designed for free software.
+ </p><p>
+ We have designed this License in order to use it for manuals for
+ free software, because free software needs free documentation: a
+ free program should come with manuals providing the same
+ freedoms that the software does. But this License is not limited
+ to software manuals; it can be used for any textual work,
+ regardless of subject matter or whether it is published as a
+ printed book. We recommend this License principally for works
+ whose purpose is instruction or reference.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section1"></a>1. APPLICABILITY AND
DEFINITIONS</h2></div></div></div><p><a name="fdl-document"></a>
+ This License applies to any manual or other work that contains a
+ notice placed by the copyright holder saying it can be
+ distributed under the terms of this License. The
+ "Document", below, refers to any such manual or
+ work. Any member of the public is a licensee, and is addressed
+ as "you".
+ </p><p><a name="fdl-modified"></a>
+ A "Modified Version" of the Document means any work
+ containing the Document or a portion of it, either copied
+ verbatim, or with modifications and/or translated into another
+ language.
+ </p><p><a name="fdl-secondary"></a>
+ A "Secondary Section" is a named appendix or a
+ front-matter section of the <a href="#fdl-document">Document</a> that
deals exclusively
+ with the relationship of the publishers or authors of the
+ Document to the Document's overall subject (or to related
+ matters) and contains nothing that could fall directly within
+ that overall subject. (For example, if the Document is in part a
+ textbook of mathematics, a Secondary Section may not explain any
+ mathematics.) The relationship could be a matter of historical
+ connection with the subject or with related matters, or of
+ legal, commercial, philosophical, ethical or political position
+ regarding them.
+ </p><p><a name="fdl-invariant"></a>
+ The "Invariant Sections" are certain <a href="#fdl-secondary"> Secondary
Sections</a> whose titles
+ are designated, as being those of Invariant Sections, in the
+ notice that says that the <a href="#fdl-document">Document</a> is
released under this
+ License.
+ </p><p><a name="fdl-cover-texts"></a>
+ The "Cover Texts" are certain short passages of
+ text that are listed, as Front-Cover Texts or Back-Cover Texts,
+ in the notice that says that the <a href="#fdl-document">Document</a> is
released under this
+ License.
+ </p><p><a name="fdl-transparent"></a>
+ A "Transparent" copy of the <a href="#fdl-document"> Document</a> means
a machine-readable
+ copy, represented in a format whose specification is available
+ to the general public, whose contents can be viewed and edited
+ directly and straightforwardly with generic text editors or (for
+ images composed of pixels) generic paint programs or (for
+ drawings) some widely available drawing editor, and that is
+ suitable for input to text formatters or for automatic
+ translation to a variety of formats suitable for input to text
+ formatters. A copy made in an otherwise Transparent file format
+ whose markup has been designed to thwart or discourage
+ subsequent modification by readers is not Transparent. A copy
+ that is not "Transparent" is called "Opaque".
+ </p><p>
+ Examples of suitable formats for Transparent copies include
+ plain ASCII without markup, Texinfo input format, LaTeX input
+ format, SGML or XML using a publicly available DTD, and
+ standard-conforming simple HTML designed for human
+ modification. Opaque formats include PostScript, PDF,
+ proprietary formats that can be read and edited only by
+ proprietary word processors, SGML or XML for which the DTD
+ and/or processing tools are not generally available, and the
+ machine-generated HTML produced by some word processors for
+ output purposes only.
+ </p><p><a name="fdl-title-page"></a>
+ The "Title Page" means, for a printed book, the
+ title page itself, plus such following pages as are needed to
+ hold, legibly, the material this License requires to appear in
+ the title page. For works in formats which do not have any title
+ page as such, "Title Page" means the text near the
+ most prominent appearance of the work's title, preceding the
+ beginning of the body of the text.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section2"></a>2. VERBATIM COPYING</h2></div></div></div><p>
+ You may copy and distribute the <a href="#fdl-document">Document</a> in
any medium, either
+ commercially or noncommercially, provided that this License, the
+ copyright notices, and the license notice saying this License
+ applies to the Document are reproduced in all copies, and that
+ you add no other conditions whatsoever to those of this
+ License. You may not use technical measures to obstruct or
+ control the reading or further copying of the copies you make or
+ distribute. However, you may accept compensation in exchange for
+ copies. If you distribute a large enough number of copies you
+ must also follow the conditions in <a href="#fdl-section3" title="3.
COPYING IN QUANTITY">section 3</a>.
+ </p><p>
+ You may also lend copies, under the same conditions stated
+ above, and you may publicly display copies.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section3"></a>3. COPYING IN QUANTITY</h2></div></div></div><p>
+ If you publish printed copies of the <a
href="#fdl-document">Document</a> numbering more than 100,
+ and the Document's license notice requires <a
href="#fdl-cover-texts">Cover Texts</a>, you must enclose
+ the copies in covers that carry, clearly and legibly, all these
+ Cover Texts: Front-Cover Texts on the front cover, and
+ Back-Cover Texts on the back cover. Both covers must also
+ clearly and legibly identify you as the publisher of these
+ copies. The front cover must present the full title with all
+ words of the title equally prominent and visible. You may add
+ other material on the covers in addition. Copying with changes
+ limited to the covers, as long as they preserve the title of the
+ <a href="#fdl-document">Document</a> and satisfy these
+ conditions, can be treated as verbatim copying in other
+ respects.
+ </p><p>
+ If the required texts for either cover are too voluminous to fit
+ legibly, you should put the first ones listed (as many as fit
+ reasonably) on the actual cover, and continue the rest onto
+ adjacent pages.
+ </p><p>
+ If you publish or distribute <a href="#fdl-transparent">Opaque</a>
copies of the <a href="#fdl-document">Document</a> numbering more than 100,
+ you must either include a machine-readable <a
href="#fdl-transparent">Transparent</a> copy along with
+ each Opaque copy, or state in or with each Opaque copy a
+ publicly-accessible computer-network location containing a
+ complete Transparent copy of the Document, free of added
+ material, which the general network-using public has access to
+ download anonymously at no charge using public-standard network
+ protocols. If you use the latter option, you must take
+ reasonably prudent steps, when you begin distribution of Opaque
+ copies in quantity, to ensure that this Transparent copy will
+ remain thus accessible at the stated location until at least one
+ year after the last time you distribute an Opaque copy (directly
+ or through your agents or retailers) of that edition to the
+ public.
+ </p><p>
+ It is requested, but not required, that you contact the authors
+ of the <a href="#fdl-document">Document</a> well before
+ redistributing any large number of copies, to give them a chance
+ to provide you with an updated version of the Document.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section4"></a>4. MODIFICATIONS</h2></div></div></div><p>
+ You may copy and distribute a <a href="#fdl-modified">Modified
Version</a> of the <a href="#fdl-document">Document</a> under the conditions of
+ sections <a href="#fdl-section2" title="2. VERBATIM COPYING">2</a> and
<a href="#fdl-section3" title="3. COPYING IN QUANTITY">3</a> above, provided
that you release
+ the Modified Version under precisely this License, with the
+ Modified Version filling the role of the Document, thus
+ licensing distribution and modification of the Modified Version
+ to whoever possesses a copy of it. In addition, you must do
+ these things in the Modified Version:
+ </p><div class="itemizedlist"><ul type="opencircle"><li
style="list-style-type: circle"><p><b>A. </b>
+ Use in the <a href="#fdl-title-page">Title
+ Page</a> (and on the covers, if any) a title distinct
+ from that of the <a href="#fdl-document">Document</a>, and from
those of
+ previous versions (which should, if there were any, be
+ listed in the History section of the Document). You may
+ use the same title as a previous version if the original
+ publisher of that version gives permission.
+ </p></li><li style="list-style-type: circle"><p><b>B. </b>
+ List on the <a href="#fdl-title-page">Title
+ Page</a>, as authors, one or more persons or entities
+ responsible for authorship of the modifications in the
+ <a href="#fdl-modified">Modified Version</a>,
+ together with at least five of the principal authors of
+ the <a href="#fdl-document">Document</a> (all of
+ its principal authors, if it has less than five).
+ </p></li><li style="list-style-type: circle"><p><b>C. </b>
+ State on the <a href="#fdl-title-page">Title
+ Page</a> the name of the publisher of the <a
href="#fdl-modified">Modified Version</a>, as the
+ publisher.
+ </p></li><li style="list-style-type: circle"><p><b>D. </b>
+ Preserve all the copyright notices of the <a
href="#fdl-document">Document</a>.
+ </p></li><li style="list-style-type: circle"><p><b>E. </b>
+ Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.
+ </p></li><li style="list-style-type: circle"><p><b>F. </b>
+ Include, immediately after the copyright notices, a
+ license notice giving the public permission to use the
+ <a href="#fdl-modified">Modified Version</a> under
+ the terms of this License, in the form shown in the
+ Addendum below.
+ </p></li><li style="list-style-type: circle"><p><b>G. </b>
+ Preserve in that license notice the full lists of <a
href="#fdl-invariant"> Invariant Sections</a> and
+ required <a href="#fdl-cover-texts">Cover
+ Texts</a> given in the <a href="#fdl-document">Document's</a>
license notice.
+ </p></li><li style="list-style-type: circle"><p><b>H. </b>
+ Include an unaltered copy of this License.
+ </p></li><li style="list-style-type: circle"><p><b>I. </b>
+ Preserve the section entitled "History", and
+ its title, and add to it an item stating at least the
+ title, year, new authors, and publisher of the <a
href="#fdl-modified">Modified Version </a>as given on
+ the <a href="#fdl-title-page">Title Page</a>. If
+ there is no section entitled "History" in the
+ <a href="#fdl-document">Document</a>, create one
+ stating the title, year, authors, and publisher of the
+ Document as given on its Title Page, then add an item
+ describing the Modified Version as stated in the previous
+ sentence.
+ </p></li><li style="list-style-type: circle"><p><b>J. </b>
+ Preserve the network location, if any, given in the <a
href="#fdl-document">Document</a> for public access
+ to a <a href="#fdl-transparent">Transparent</a>
+ copy of the Document, and likewise the network locations
+ given in the Document for previous versions it was based
+ on. These may be placed in the "History"
+ section. You may omit a network location for a work that
+ was published at least four years before the Document
+ itself, or if the original publisher of the version it
+ refers to gives permission.
+ </p></li><li style="list-style-type: circle"><p><b>K. </b>
+ In any section entitled "Acknowledgements" or
+ "Dedications", preserve the section's title,
+ and preserve in the section all the substance and tone of
+ each of the contributor acknowledgements and/or
+ dedications given therein.
+ </p></li><li style="list-style-type: circle"><p><b>L. </b>
+ Preserve all the <a href="#fdl-invariant">Invariant
+ Sections</a> of the <a href="#fdl-document">Document</a>, unaltered
in their
+ text and in their titles. Section numbers or the
+ equivalent are not considered part of the section titles.
+ </p></li><li style="list-style-type: circle"><p><b>M. </b>
+ Delete any section entitled
+ "Endorsements". Such a section may not be
+ included in the <a href="#fdl-modified">Modified
+ Version</a>.
+ </p></li><li style="list-style-type: circle"><p><b>N. </b>
+ Do not retitle any existing section as
+ "Endorsements" or to conflict in title with
+ any <a href="#fdl-invariant">Invariant
+ Section</a>.
+ </p></li></ul></div><p>
+ If the <a href="#fdl-modified">Modified Version</a>
+ includes new front-matter sections or appendices that qualify as
+ <a href="#fdl-secondary">Secondary Sections</a> and
+ contain no material copied from the Document, you may at your
+ option designate some or all of these sections as invariant. To
+ do this, add their titles to the list of <a
href="#fdl-invariant">Invariant Sections</a> in the
+ Modified Version's license notice. These titles must be
+ distinct from any other section titles.
+ </p><p>
+ You may add a section entitled "Endorsements",
+ provided it contains nothing but endorsements of your <a
href="#fdl-modified">Modified Version</a> by various
+ parties--for example, statements of peer review or that the text
+ has been approved by an organization as the authoritative
+ definition of a standard.
+ </p><p>
+ You may add a passage of up to five words as a <a
href="#fdl-cover-texts">Front-Cover Text</a>, and a passage
+ of up to 25 words as a <a href="#fdl-cover-texts">Back-Cover Text</a>,
to the end of
+ the list of <a href="#fdl-cover-texts">Cover Texts</a>
+ in the <a href="#fdl-modified">Modified Version</a>.
+ Only one passage of Front-Cover Text and one of Back-Cover Text
+ may be added by (or through arrangements made by) any one
+ entity. If the <a href="#fdl-document">Document</a>
+ already includes a cover text for the same cover, previously
+ added by you or by arrangement made by the same entity you are
+ acting on behalf of, you may not add another; but you may
+ replace the old one, on explicit permission from the previous
+ publisher that added the old one.
+ </p><p>
+ The author(s) and publisher(s) of the <a
href="#fdl-document">Document</a> do not by this License
+ give permission to use their names for publicity for or to
+ assert or imply endorsement of any <a href="#fdl-modified">Modified
Version </a>.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section5"></a>5. COMBINING DOCUMENTS</h2></div></div></div><p>
+ You may combine the <a href="#fdl-document">Document</a>
+ with other documents released under this License, under the
+ terms defined in <a href="#fdl-section4" title="4.
MODIFICATIONS">section 4</a>
+ above for modified versions, provided that you include in the
+ combination all of the <a href="#fdl-invariant">Invariant
+ Sections</a> of all of the original documents, unmodified,
+ and list them all as Invariant Sections of your combined work in
+ its license notice.
+ </p><p>
+ The combined work need only contain one copy of this License,
+ and multiple identical <a href="#fdl-invariant">Invariant
+ Sections</a> may be replaced with a single copy. If there are
+ multiple Invariant Sections with the same name but different
+ contents, make the title of each such section unique by adding
+ at the end of it, in parentheses, the name of the original
+ author or publisher of that section if known, or else a unique
+ number. Make the same adjustment to the section titles in the
+ list of Invariant Sections in the license notice of the combined
+ work.
+ </p><p>
+ In the combination, you must combine any sections entitled
+ "History" in the various original documents,
+ forming one section entitled "History"; likewise
+ combine any sections entitled "Acknowledgements",
+ and any sections entitled "Dedications". You must
+ delete all sections entitled "Endorsements."
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section6"></a>6. COLLECTIONS OF DOCUMENTS</h2></div></div></div><p>
+ You may make a collection consisting of the <a
href="#fdl-document">Document</a> and other documents
+ released under this License, and replace the individual copies
+ of this License in the various documents with a single copy that
+ is included in the collection, provided that you follow the
+ rules of this License for verbatim copying of each of the
+ documents in all other respects.
+ </p><p>
+ You may extract a single document from such a collection, and
+ distribute it individually under this License, provided you
+ insert a copy of this License into the extracted document, and
+ follow this License in all other respects regarding verbatim
+ copying of that document.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section7"></a>7. AGGREGATION WITH INDEPENDENT
WORKS</h2></div></div></div><p>
+ A compilation of the <a href="#fdl-document">Document</a> or its
derivatives with
+ other separate and independent documents or works, in or on a
+ volume of a storage or distribution medium, does not as a whole
+ count as a <a href="#fdl-modified">Modified Version</a>
+ of the Document, provided no compilation copyright is claimed
+ for the compilation. Such a compilation is called an
+ "aggregate", and this License does not apply to the
+ other self-contained works thus compiled with the Document , on
+ account of their being thus compiled, if they are not themselves
+ derivative works of the Document. If the <a
href="#fdl-cover-texts">Cover Text</a> requirement of <a href="#fdl-section3"
title="3. COPYING IN QUANTITY">section 3</a> is applicable to these
+ copies of the Document, then if the Document is less than one
+ quarter of the entire aggregate, the Document's Cover Texts may
+ be placed on covers that surround only the Document within the
+ aggregate. Otherwise they must appear on covers around the whole
+ aggregate.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section8"></a>8. TRANSLATION</h2></div></div></div><p>
+ Translation is considered a kind of modification, so you may
+ distribute translations of the <a href="#fdl-document">Document</a>
under the terms of <a href="#fdl-section4" title="4. MODIFICATIONS">section
4</a>. Replacing <a href="#fdl-invariant"> Invariant Sections</a> with
+ translations requires special permission from their copyright
+ holders, but you may include translations of some or all
+ Invariant Sections in addition to the original versions of these
+ Invariant Sections. You may include a translation of this
+ License provided that you also include the original English
+ version of this License. In case of a disagreement between the
+ translation and the original English version of this License,
+ the original English version will prevail.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section9"></a>9. TERMINATION</h2></div></div></div><p>
+ You may not copy, modify, sublicense, or distribute the <a
href="#fdl-document">Document</a> except as expressly
+ provided for under this License. Any other attempt to copy,
+ modify, sublicense or distribute the Document is void, and will
+ automatically terminate your rights under this License. However,
+ parties who have received copies, or rights, from you under this
+ License will not have their licenses terminated so long as such
+ parties remain in full compliance.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-section10"></a>10. FUTURE REVISIONS OF THIS
LICENSE</h2></div></div></div><p>
+ The <a href="http://www.gnu.org/fsf/fsf.html"; target="_top">Free Software
+ Foundation</a> may publish new, revised versions of the GNU
+ Free Documentation License from time to time. Such new versions
+ will be similar in spirit to the present version, but may differ
+ in detail to address new problems or concerns. See <a
href="http://www.gnu.org/copyleft";
target="_top">http://www.gnu.org/copyleft/</a>.
+ </p><p>
+ Each version of the License is given a distinguishing version
+ number. If the <a href="#fdl-document">Document</a>
+ specifies that a particular numbered version of this License
+ "or any later version" applies to it, you have the
+ option of following the terms and conditions either of that
+ specified version or of any later version that has been
+ published (not as a draft) by the Free Software Foundation. If
+ the Document does not specify a version number of this License,
+ you may choose any version ever published (not as a draft) by
+ the Free Software Foundation.
+ </p></div><div class="sect1" lang="en"><div
class="titlepage"><div><div><h2 class="title" style="clear: both"><a
name="fdl-using"></a>Addendum</h2></div></div></div><p>
+ To use this License in a document you have written, include a copy of
+ the License in the document and put the following copyright and
+ license notices just after the title page:
+ </p><div class="blockquote"><blockquote class="blockquote"><p>
+ Copyright 2008, Free Software Foundation.
+ </p><p>
+ Permission is granted to copy, distribute and/or modify this
+ document under the terms of the GNU Free Documentation
+ License, Version 1.1 or any later version published by the
+ Free Software Foundation; with no<a href="#fdl-invariant">Invariant
Sections</a>, with no <a href="#fdl-cover-texts">Front-Cover Texts</a>,
+ and with no <a href="#fdl-cover-texts">Back-Cover
+ Texts</a>. A copy of the license is included in
+ the section entitled "GNU Free Documentation License".
+ </p></blockquote></div><p>
+ If your document contains nontrivial examples of program code,
+ we recommend releasing these examples in parallel under your
+ choice of free software license, such as the <a
href="http://www.gnu.org/copyleft/gpl.html"; target="_top"> GNU General Public
+ License</a>, to permit their use in free software.
+ </p></div></div></div></body></html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Gnash-commit] gnash/packaging/doc gnash_ref.info.in gnash_use...,
Rob Savoye <=