[openvrml-commit] openvrml/doc fdl.texi, NONE, 1.1 openvrml-gtkplug.texi, NONE, 1.1 .cvsignore, 1.4, 1.5 Makefile.am, 1.34, 1.35

[Braden M. <br...@us...>]

Update of /cvsroot/openvrml/openvrml/doc
In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv6988/doc

Modified Files:
	.cvsignore Makefile.am 
Added Files:
	fdl.texi openvrml-gtkplug.texi 
Log Message:
Added info documentation for openvrml-gtkplug.

Index: .cvsignore
===================================================================
RCS file: /cvsroot/openvrml/openvrml/doc/.cvsignore,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** .cvsignore	10 Aug 2006 02:56:17 -0000	1.4
--- .cvsignore	4 Oct 2006 06:26:42 -0000	1.5
***************
*** 1,2 ****
--- 1,7 ----
+ *.info
  Makefile
  Makefile.in
+ mdate-sh
+ stamp-vti
+ texinfo.tex
+ version.texi

--- NEW FILE: openvrml-gtkplug.texi ---
\input texinfo @c -*-texinfo-*-
@c %**start of header
@setfilename openvrml-gtkplug.info
@include version.texi
@settitle openvrml-gtkplug @value{VERSION}
@c %**end of header

@copying
This manual is for openvrml-gtkplug (version @value{VERSION},
@value{UPDATED}), which provides a VRML/X3D browser as a GtkPlug
component that can be used in any GTK+ application.

Copyright @copyright{} 2006 Braden McDaniel

@quotation
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation.  A copy
of the license is included in the section entitled ``GNU Free
Documentation License.''
@end quotation
@end copying

@c Define a new index for options.
@defcodeindex op
@c Combine everything into one index (arbitrarily chosen to be the
@c concept index).
@syncodeindex op cp

@dircategory Miscellaneous
@direntry
* openvrml-gtkplug: A VRML/X3D browser component for GTK+ applications.
@end direntry

@titlepage
@title openvrml-gtkplug
@subtitle for version @value{VERSION}, @value{UPDATED}
@author Braden McDaniel (@email{braden@@endoframe.com})
@page
@vskip 0pt plus 1filll
@insertcopying
@end titlepage

@contents


@ifnottex
@node Top
@top openvrml-gtkplug

This manual is for openvrml-gtkplug (version @value{VERSION}, @value{UPDATED}).
@end ifnottex

@menu
* Overview::                    General purpose and information.
* Invoking openvrml-gtkplug::   How to run @code{openvrml-gtkplug}.
* Servicing Requests::          How to respond to requests from the component.
* Problems::		        Getting help and reporting bugs.
* Copying This Manual::         Copying and sharing this documentation.
* Concept Index::	        Index of concepts.
@end menu


@node Overview
@chapter Overview

@cindex overview

@code{openvrml-gtkplug} provides a VRML/X3D browser as a GtkPlug
component that can be used in any GTK+ application.
@code{openvrml-gtkplug} communicates with the host application via
pipes from its @code{stdout} and to its @code{stdin}.  The host
application is responsible for fetching network resources and sending
these to the component.

@code{openvrml-gtkplug} uses the OpenVRML VRML/X3D runtime.  For the
latest updates and other information, please visit OpenVRML on the
World Wide Web at @url{http://openvrml.org}.

@cindex authors
@cindex McDaniel, Braden
@code{openvrml-gtkplug} was written by Braden McDaniel.


@node Invoking openvrml-gtkplug
@chapter Invoking @code{openvrml-gtkplug}

@cindex invoking
@cindex options
@cindex usage
@cindex help

The format for running the @code{openvrml-gtkplug} program is:

@example
openvrml-gtkplug [@var{options}] @var{gtk-socket-id}
@end example

@var{gtk-socket-id} is the XID of a GtkSocket.

@section Options

@code{openvrml-gtkplug} supports the following options:

@subsection Help Options

@table @option
@item --help
@itemx -?
@opindex --help
@opindex -?
Show help options.

@item --help-all
@opindex --help-all
Show all help options.

@item --help-gtk
@opindex --help-gtk
Show GTK+ options.
@end table

@subsection GTK+ Options

@table @option
@item --class=@var{class}
@opindex --class
Program class as used by the window manager.

@item --name=@var{name}
@opindex --name
Program name as used by the window manager.

@item --screen=@var{screen}
@opindex --screen
X screen to use.

@item --sync
@opindex --sync
Make X calls synchronous.

@item --gtk-module=@var{modules}
@opindex --gtk-module
Load additional GTK+ modules.

@item --g-fatal-warnings
@opindex --g-fatal-warnings
Make all warnings fatal.
@end table

@subsection Application Options

@table @option
@item --version
@opindex --version
Print the version information and exit.

@item --display=@var{display}
@opindex --display
X display to use.
@end table

@section Invoking From Another Program

In general @code{openvrml-gtkplug} is invoked from another program
which establishes pipes to @code{openvrml-gtkplug}'s @code{stdin} and
from its @code{stdout}.  This can be done using the typical
@code{fork}-@code{exec} mechanism.  If you are using GLib, the
function @code{g_spawn_async_with_pipes} nicely encapsulates the
required logic:

@example
gchar * working_directory;
gchar ** argv;
gchar ** envp = 0;
GPid * child_pid = 0;
gint standard_input, standard_output;
gint * standard_error = 0;
GError * error = 0;
gboolean succeeded;

working_directory = g_get_current_dir();
argv = g_malloc(sizeof (gchar *) * 3)
argv[0] = g_strdup("/usr/libexec/openvrml-gtkplug");
argv[1] = g_strdup_printf("%d", gtk_socket_id);
argv[2] = 0;

succeeded = g_spawn_async_with_pipes(working_directory,
                                     argv,
                                     envp,
                                     0,
                                     0,
                                     0,
                                     child_pid,
                                     &standard_input,
                                     &standard_output,
                                     standard_error,
                                     &error);
@end example


@node Servicing Requests
@chapter Servicing Requests

@cindex request
@cindex request channel
@cindex command
@cindex command channel

@section Requests and Commands

@code{openvrml-gtkplug} relies on the host application for fetching
network resources.  @code{openvrml-gtkplug} will send a @dfn{request}
for a network resource via its @code{stdout}.  As such, the pipe from
@code{openvrml-gtkplug}'s @code{stdout} to the host application is
referred to as the @dfn{request channel}.

In general (and as the name implies), requests elicit some response
from the host application.  The pipe to @code{openvrml-gtkplug}'s
@code{stdin} is used for such responses as well other @dfn{commands}.
This pipe is referred to as the @dfn{command channel}.

Requests and commands are terminated by an end-of-line.  They take the
general form:

@example
@var{command-name} [@var{param1} [@var{param2} ... ]]
@end example

@cindex get-url
@section The @code{get-url} Request

@code{openvrml-gtkplug} sends a @code{get-url} request to indicate to
the host application that it needs a particular network resource.
This request takes the following form:

@example
get-url @var{url} [@var{target}]
@end example

@table @var
@item url
The URL being requested.

@item target
The name of a window.
@end table

The @var{url} parameter is the URL being requested.  The optional
@var{target} parameter is the name of a window of the host
application.  If @var{target} is not meaningful to the host
application, it can be ignored.

The @code{get-url} request expects a response in the form of a
@code{get-url-result} command.  @code{openvrml-gtkplug} is unable to
process the availability of the resource until it receives this
command; so it should be issued as soon as possible.

@section Commands

@cindex get-url-result
@subsection @code{get-url-result}

The @code{get-url-result} command should be sent immediately in
response to a @code{get-url} request.  This command should indicate
the basic success or failure of initiating the resource request.
@strong{It is not intended to indicate a response from a server}.
Rather, it should be used to indicate whether the @var{URL} can be
processed at all.  A URL might not be usable if it is syntactically
invalid or its scheme is unsupported.

This command takes the following form:

@example
get-url-result @var{url} @var{result}
@end example

@table @var
@item url
The URL from the @code{get-url} request.
@item result
An integer value.
@end table

The @var{url} parameter should match the URL received in the
corresponding @code{get-url} request.  The @var{result} is an integer
value; 0 indicates success, while nonzero indicates failure.

@cindex new-stream
@subsection @code{new-stream}

The @code{new-stream} command indicates to @code{openvrml-gtkplug}
that the host application intends to begin writing data associated
with a requested resource.  @code{new-stream} should be sent after
@code{get-url-result} has been sent for a stream and before
@code{write} is sent for any of the stream data.

This command takes the following form:

@example
new-stream @var{stream-id} @var{type} @var{url}
@end example

@table @var
@item stream-id
An integer identifier for the stream.
@item type
The MIME media type of the stream.
@item url
The URL associated with the stream.
@end table

The @var{stream-id} is an integer identifier for the stream.  This
identifier will be used subsequently by the @code{write} and
@code{destroy-stream} commands to refer to the stream.

The @var{type} parameter is the MIME media type of the stream.  The
@var{url} parameter should match the @var{url} parameter of a
previously issued @code{get-url-result} command.

@cindex write
@subsection @code{write}

The @code{write} command writes data to a stream for which
@code{new-stream} has already been issued.  This command takes the
following form:

@example
write @var{stream_id} @var{offset} @var{length}
@var{data}
@end example

@table @var
@item stream-id
An integer identifier for the stream.
@item offset
The offset from the beginning of the stream to the beginning of
@var{data}.
@item length
The number of bytes in @var{data}
@item data
The stream data.
@end table

The @var{stream-id} parameter is an integer identifier corresponding
to a stream for which @code{new-stream} has already been called (and
for which @code{destroy-stream} has @emph{not} been called.

@code{write} is unique among commands in that the end-of-line
character does not terminate the command; rather, it marks the
beginning of the @var{data} parameter.  The command ends at the end of
the @var{data} parameter, which is indicated by the @var{length}
parameter.

@code{write} may be called multiple times for the same stream.  The
@var{offset} parameter indicates the offset of the beginning of
@var{data} with respect to the beginning of the stream (in bytes).

@cindex destroy-stream
@subsection @code{destroy-stream}

@code{destroy-stream} should be sent for a @var{stream-id} after no
more @code{write} commands will be issued for it.  This command takes
the following form:

@example
destroy-stream @var{stream-id}
@end example

@table @var
@item stream-id
An integer identifier for a stream.
@end table

@var{stream-id} should identify a stream for which @code{new-stream}
has been sent, but for which @code{destroy-stream} has @emph{not}
already been sent.

@node Problems
@chapter Getting Help and Reporting Bugs

@cindex bug reporting
@cindex problems
@cindex reporting bugs

@section Mailing List

As part of the OpenVRML package, @code{openvrml-gtkplug} is discussed
on the OpenVRML development mailing list,
@email{openvrml-develop@@lists.sourceforge.net}.  Questions about usage
of any part of the OpenVRML package are welcome here.  This mailing
list permits posting only by subscribers in order to curb spam.
Subscription information can be found at
@url{http://lists.sourceforge.net/lists/listinfo/openvrml-develop}.

@section Reporting Bugs

Please report any bugs you encounter using
@url{http://sourceforge.net/tracker/?func=add&group_id=7151&atid=107151,
OpenVRML's SourceForge bug tracker}.

@cindex checklist for bug reports
Please include enough information for the maintainers to reproduce the
problem.  Generally speaking, that means:

@itemize @bullet
@item The version number of openvrml-gtkplug (which you can find by
running @w{@samp{openvrml-gtkplug --version}}) and any other
program(s) or manual(s) involved.
@item Hardware and operating system names and versions.
@item The contents of any input files necessary to reproduce the bug.
@item The expected behavior and/or output.
@item A description of the problem and samples of any erroneous output.
@item Any unusual options you gave to @command{configure}.
@item Anything else that you think would be helpful.
@end itemize

When in doubt whether something is needed or not, include it.  It's
better to include too much than to leave out something important.

@section Submitting Patches

@cindex patches, contributing
Patches are welcome; if possible, please make them with @samp{@w{diff
-u}} (@pxref{Top,, Overview, diff, Comparing and Merging Files}) and
include @file{ChangeLog} entries (@pxref{Change Log,,, emacs, The GNU
Emacs Manual}).  Please follow the existing coding style.

The preferred means of submitting a patch is using @url{OpenVRML's
SourceForge Patch Manager,
http://sourceforge.net/tracker/?func=add&group_id=7151&atid=307151}.


@node Copying This Manual
@appendix Copying This Manual

@menu
* GNU Free Documentation License::  License for copying this manual.
@end menu

@include fdl.texi


@node Concept Index
@unnumbered Concept Index

@printindex cp

@bye

--- NEW FILE: fdl.texi ---

@node GNU Free Documentation License
@appendixsec GNU Free Documentation License

@cindex FDL, GNU Free Documentation License
@center Version 1.2, November 2002

@display
Copyright @copyright{} 2000,2001,2002 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA  02110-1301, USA

Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@end display

@enumerate 0
@item
PREAMBLE

The purpose of this License is to make a manual, textbook, or other
functional and useful document @dfn{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 noncommercially.
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.

@item
APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License.  Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
work under the conditions stated herein.  The ``Document'', below,
refers to any such manual or work.  Any member of the public is a
licensee, and is addressed as ``you''.  You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.

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 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.  (Thus, 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 whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License.  If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant.  The Document may contain zero
Invariant Sections.  If the Document does not identify any Invariant
Sections then there are none.

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 is released under this License.  A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.

A ``Transparent'' copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
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, or absence of markup, has been arranged to thwart
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text.  A copy that is not ``Transparent'' is called ``Opaque''.

Examples of suitable formats for Transparent copies include plain
@sc{ascii} without markup, Texinfo input format, La@TeX{} input
format, @acronym{SGML} or @acronym{XML} using a publicly available
@acronym{DTD}, and standard-conforming simple @acronym{HTML},
PostScript or @acronym{PDF} designed for human modification.  Examples
of transparent image formats include @acronym{PNG}, @acronym{XCF} and
@acronym{JPG}.  Opaque formats include proprietary formats that can be
read and edited only by proprietary word processors, @acronym{SGML} or
@acronym{XML} for which the @acronym{DTD} and/or processing tools are
not generally available, and the machine-generated @acronym{HTML},
PostScript or @acronym{PDF} 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.

A section ``Entitled XYZ'' means a named subunit of the Document whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language.  (Here XYZ stands for a
specific section name mentioned below, such as ``Acknowledgements'',
``Dedications'', ``Endorsements'', or ``History''.)  To ``Preserve the Title''
of such a section when you modify the Document means that it remains a
section ``Entitled XYZ'' according to this definition.

The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document.  These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.

@item
VERBATIM COPYING

You may copy and distribute the 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.

You may also lend copies, under the same conditions stated above, and
you may publicly display copies.

@item
COPYING IN QUANTITY

If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
Document's license notice requires 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 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 copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
public has access to download using public-standard network protocols
a complete Transparent copy of the Document, free of added material.
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 well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.

@item
MODIFICATIONS

You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 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:

@enumerate A
@item
Use in the Title Page (and on the covers, if any) a title distinct
from that of the 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.

@item
List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.

@item
State on the Title page the name of the publisher of the
Modified Version, as the publisher.

@item
Preserve all the copyright notices of the Document.

@item
Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.

@item
Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.

@item
Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document's license notice.

@item
Include an unaltered copy of this License.

@item
Preserve the section Entitled ``History'', Preserve its Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page.  If
there is no section Entitled ``History'' in the 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.

@item
Preserve the network location, if any, given in the Document for
public access to a 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.

@item
For any section Entitled ``Acknowledgements'' or ``Dedications'', Preserve
the Title of the section, and preserve in the section all the
substance and tone of each of the contributor acknowledgements and/or
dedications given therein.

@item
Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles.  Section numbers
or the equivalent are not considered part of the section titles.

@item
Delete any section Entitled ``Endorsements''.  Such a section
may not be included in the Modified Version.

@item
Do not retitle any existing section to be Entitled ``Endorsements'' or
to conflict in title with any Invariant Section.

@item
Preserve any Warranty Disclaimers.
@end enumerate

If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections 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 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 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, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version.  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 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 do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.

@item
COMBINING DOCUMENTS

You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and
multiple identical Invariant Sections 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.''

@item
COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the 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.

@item
AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an ``aggregate'' if the copyright
resulting from the compilation is not used to limit the legal rights
of the compilation's users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
the entire aggregate, the Document's Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.

@item
TRANSLATION

Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections 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, and all the license notices in the
Document, and any Warranty Disclaimers, provided that you also include
the original English version of this License and the original versions
of those notices and disclaimers.  In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.

If a section in the Document is Entitled ``Acknowledgements'',
``Dedications'', or ``History'', the requirement (section 4) to Preserve
its Title (section 1) will typically require changing the actual
title.

@item
TERMINATION

You may not copy, modify, sublicense, or distribute the 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.

@item
FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation 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
@uref{http://www.gnu.org/copyleft/}.

Each version of the License is given a distinguishing version number.
If the 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.
@end enumerate

@page
@appendixsubsec ADDENDUM: How to use this License for your documents

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:

@smallexample
@group
  Copyright (C)  @var{year}  @var{your name}.
  Permission is granted to copy, distribute and/or modify this document
  under the terms of the GNU Free Documentation License, Version 1.2
  or any later version published by the Free Software Foundation;
  with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
  Texts.  A copy of the license is included in the section entitled ``GNU
  Free Documentation License''.
@end group
@end smallexample

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
replace the ``with...Texts.'' line with this:

@smallexample
@group
    with the Invariant Sections being @var{list their titles}, with
    the Front-Cover Texts being @var{list}, and with the Back-Cover Texts
    being @var{list}.
@end group
@end smallexample

If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.

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,
to permit their use in free software.

@c Local Variables:
@c ispell-local-pdict: "ispell-dict"
@c End:


Index: Makefile.am
===================================================================
RCS file: /cvsroot/openvrml/openvrml/doc/Makefile.am,v
retrieving revision 1.34
retrieving revision 1.35
diff -C2 -d -r1.34 -r1.35
*** Makefile.am	10 Aug 2006 06:50:34 -0000	1.34
--- Makefile.am	4 Oct 2006 06:26:42 -0000	1.35
***************
*** 1,2 ****
--- 1,5 ----
+ info_TEXINFOS = openvrml-gtkplug.texi
+ openvrml_gtkplug_TEXINFOS = fdl.texi
+ 
  docdir = $(datadir)/doc/@PACKAGE_TARNAME@-@PACKAGE_VERSION@