[gnome-db]gnome-db.sgml--freshned
- From: Sean Allen <zeroone worldonline co za>
- To: Gnome DB List <gnome-db-list gnome org>, Rodrigo Moya <rodrigo gnome-db org>
- Subject: [gnome-db]gnome-db.sgml--freshned
- Date: 15 May 2001 02:09:52 +0200
Ok
in learning DocBook and in moving docs over to FDL and GDP.
I endend up getting carried away ;-)
first file is gnome-db.sgml
--changed entity refs, id's etc. to comply with GDP
--Have cleaned up some of the syntax and english
--added markup that was needed, some that was not, but may be if we ever
grow a glossary/index
--moved to FDL, this may seem like overkill (it's longer than the doc,
almost;) but it seems prudent if there are going to be downloads from
website, etc. in pdf/ps
would someone look over this, tell me if it's too much, more needs
doing, suggestions etc.
if there are no complaints I will freshen the rest of the (english)doc
tree before starting on user guide
I will also, if there are no objections enter the GnomeDB docs etc into
the GDP "big-board" maybe we get soem help.
Sean Allen.
--- gnome-db.sgml Tue May 15 01:36:33 2001
+++ gnome-db.sgml.new Tue May 15 01:27:40 2001
@@ -1,12 +1,12 @@
<?xml version='1.0'?>
-<!DOCTYPE book PUBLIC "-//Davenport//DTD DocBook V3.0//EN" [
-<!entity Libgda "<application>libgda</application>">
-<!entity GnomeDB "<application>GNOME-DB</application>">
+<!DOCTYPE book PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN" [
+<!ENTITY LIBGDA "<application>libgda</application>">
+<!ENTITY GNOMEDB "<application>GNOME-DB</application>">
]>
-<book id="gnome-db">
+<book id="index">
<bookinfo>
- <title>GNOME-DB</title>
+ <title>&GNOMEDB; manual</title>
<authorgroup>
<author>
<firstname>Michael</firstname>
@@ -29,36 +29,51 @@
<address><email>malerba linuxave net</email></address>
</affiliation>
</author>
+
+ <author role="clean up">
+ <firstname>Sean</firstname>
+ <surname>Allen</surname>
+ <affiliation>
+ <address><email>zeroone worldonline co za</email></address>
+ </affiliation>
+ <contrib>Additional markup, English syntax, move to FDL.</contrib>
+ </author>
</authorgroup>
<date>1999 February</date>
<copyright>
- <year>1999-2000</year>
+ <year>1999-2001</year>
<holder>The Free Software Foundation</holder>
</copyright>
- <title>&GnomeDB; manual</title>
- <abstract>
+ <abstract>
<para>
- &GnomeDB; is part of the <ulink url="http://www.gnome.org";
- type="http">GNOME project</ulink>. It is a frontend to the
- &Libgda; library, which is an architecture providing
- universal access to different kinds of data sources (databases,
- information servers, plain files, etc).
+ &GNOMEDB; is part of the <ulink url="http://www.gnome.org"; type="http">
+ GNOME project</ulink>. It is a front-end to the &LIBGDA; library, which
+ is an architecture providing universal access to different kinds of
+ data sources (databases, information servers, plain files, etc).
</para>
<para>
- &GnomeDB; is also part of the <ulink
- url="http://www.gnome.org/gnome-office/"; type="http">GNOME
+ &GNOMEDB; is also part of the
+ <ulink url="http://www.gnome.org/gnome-office/"; type="http">GNOME
Office</ulink> project, which is a free suite of GNOME-aware
- applications aimed at desktop productivity. &GnomeDB; provides
+ applications aimed at desktop productivity. &GNOMEDB; provides
the database access part to the suite.
</para>
</abstract>
- <legalnotice>
+ <legalnotice id="legalnotice">
+ <para>
+ Permission is granted to copy, distribute and/or modify this document
+ under the terms of the <link linkend="fdl"><citetitle>GNU
+ Free Documentation License</citetitle></link>, 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. A copy of the
+ license can be found in <xref linkend="fdl">.
+ </para>
<para>
- This document may be distributed subject to the terms and
- conditions set forth in the Open Publication License, v1.0 or
- later (the latest version is presently available at <ulink
- url=" http://www.opencontent.org/openpub/";
- type="http">http://www.opencontent.org/openpub/</ulink> )
+ Many of the names used by companies to distinguish their products and
+ services are claimed as trademarks. Where those names appear in any
+ GNOME documentation, and those trademarks are made aware to the members
+ of the GNOME Documentation Project, the names have been printed in caps
+ or initial caps.
</para>
</legalnotice>
</bookinfo>
@@ -66,321 +81,345 @@
<chapter id="introduction">
<title>Introduction</title>
<para>
- &GnomeDB; can be taken of as an extension of the &Libgda; project.
+ &GNOMEDB; can be taken of as an extension of the &LIBGDA; project.
Its aims are the same: to provide universal data source access for
client applications, as well as development tools and libraries
- for doing so. &GnomeDB; is an extension to &Libgda; because it adds
+ for doing so. &GNOMEDB; is an extension to &LIBGDA; because it adds
support to the architecture for the GNOME project.
</para>
<para>
- Both projects were once together under the &GnomeDB; project, but
- &Libgda; was separated from it due to its great usefulness also
+ Both projects were once together under the &GNOMEDB; project, but
+ &LIBGDA; was separated from it due to its great usefulness also
outside of GNOME environments. All GNOME dependencies were removed
when performing this separation.
</para>
<para>
- But &GnomeDB; is not just a frontend to &Libgda; for the GNOME
+ But &GNOMEDB; is not just a front-end to &LIBGDA; for the GNOME
project. Thus, making use of the different GNOME technologies, such
- as Bonobo, XML, GConf, etc, it extends &Libgda; in a way that allows
- for awesome database-related GNOME applications. Through the use
- of Bonobo, the GNOME component system, a whole range of services and
+ as <systemitem class="resource">Bonobo</systemitem>, <acronym>XML
+ </acronym>, <systemitem class="resource">GConf</systemitem>, etc, it
+ extends &LIBGDA; in a way that allows for awesome database-related GNOME
+ applications. Through the use of <systemitem class="resource">Bonobo
+ </systemitem>, the GNOME component system, a whole range of services and
utilities are provided in the form of components, thus allowing their
- reuse in other Bonobo-aware applications. In fact, this is the way
- the communication is done with the other applications contained
- in the GNOME Office suite.
+ reuse in other <systemitem class="resource">Bonobo</systemitem>-aware
+ applications. In fact, this is the way the communication is done with
+ the other applications contained in the GNOME Office suite.
</para>
<para>
- It provides libraries to be used in developing &GnomeDB; applications,
+ It provides libraries to be used in developing &GNOMEDB; applications,
and lots of tools and utilities to help you in all your database-related
tasks. It also includes a development environment to speed up the
- development of applications based on &GnomeDB;.
+ development of applications based on &GNOMEDB;.
</para>
</chapter>
<chapter id="comlib">
- <title>&GnomeDB; Components Library</title>
+ <title>&GNOMEDB; Components Library</title>
<para>
</para>
</chapter>
<chapter id="widgetlib">
- <title>&GnomeDB; Widget Library</title>
+ <title>&GNOMEDB; Widget Library</title>
<sect1 id="widgetlib-introduction">
<title>Introduction</title>
<para>
This library contains a rich set of GNOME widgets that provide an
- easy way of including the GDA model into your GNOME applications.
+ easy way of including the <acronym>GDA</acronym> model into your GNOME
+ applications.
</para>
<para>
- All the widgets are GTK widgets, which means that you get an
- object-oriented approach to your user interface. This will allow
- you, for example, to write a custom widget for your application
- implementing just the extra fonctionality. The basic behavior
- is already implemented by the GDA widget.
+ All the widgets are <systemitem class="resource">GTK+</systemitem>
+ widgets, which means that you get an object-oriented approach to your
+ user interface. This will allow you, for example, to write a custom
+ widget for your application implementing just the extra functionality.
+ The basic behavior is already implemented by the <acronym>GDA</acronym>
+ widget.
</para>
<para>
This also means that you can attach procedures to the widgets'
- received signals, as you do with GTK/GNOME widgets. In fact, &GnomeDB;
- widgets inform of their behavior by emitting signals that can be
- catched by your application to get information for the event
- signalled.
- </para>
- <para>
- For example, the <classname>GnomeDbBrowser</classname> widget contains lots of child
- widgets, which in turn catch user events, which are then catched
- by the <classname>GnomeDbBrowser</classname> widget itself. The latter propagates some
- of these events by emitting it's own signals. Thus, you can,
- for example, know the interaction the user is doing with the widget
- to update a status bar message, show a dialog box when an error
- occurs, etc.
+ received signals, as you do with <systemitem class="resource">
+ GTK+/GNOME</systemitem> widgets. In fact, &GNOMEDB; widgets inform of
+ their behavior by emitting signals that can be caught by your
+ application to get information for the event signaled.
</para>
<para>
- The widgets provided by the &GnomeDB; library cover almost all you need
+ For example, the <classname>GnomeDbBrowser</classname> widget contains
+ lots of child widgets, which in turn catch user events, which are then
+ caught by the <classname>GnomeDbBrowser</classname> widget itself.
+ The latter propagates some of these events by emitting it's own
+ signals. Thus, you can, for example, know the interaction the user
+ is doing with the widget to update a status bar message, show a dialog
+ box when an error occurs, etc.
+ </para>
+ <para>
+ The widgets provided by the &GNOMEDB; library cover almost all you need
to develop user interfaces for your database-oriented applications.
If your needs are not covered, you have two choices: ask us to do the
- widget you want, or, implement your own by subclassing the most suitable
- &GnomeDB; widget. If you prefer the second method, you should have a look
- at the GTK+ documentation, specially the 'Writing your Own Widgets'
- chapter.
+ widget you want, or, implement your own by sub-classing the most
+ suitable &GNOMEDB; widget. If you prefer the second method, you should
+ have a look at the <systemitem class="resource">GTK+</systemitem>
+ documentation, especially the 'Writing your Own Widgets' chapter.
</para>
<para>
The widgets contained in the library are:
</para>
<itemizedlist mark="bullet">
- <listitem><para>GnomeDbLogin</para></listitem>
- <listitem><para>GnomeDbLoginDlg</para></listitem>
- <listitem><para>GnomeDbDsnConfig</para></listitem>
- <listitem><para>GnomeDbHelpViewer</para></listitem>
- <listitem><para>GnomeDbBrowser</para></listitem>
- <listitem><para>GnomeDbGrid</para></listitem>
- <listitem><para>GnomeDbDataset</para></listitem>
- <listitem><para>GnomeDbCombo</para></listitem>
- <listitem><para>GnomeDbList</para></listitem>
- <listitem><para>GnomeDbIconList</para></listitem>
- <listitem><para>GnomeDbReport</para></listitem>
- <listitem><para>GnomeDbDesigner</para></listitem>
- <listitem><para>GnomeDbHelp</para></listitem>
- <listitem><para>GnomeDbShortcut</para></listitem>
- <listitem><para>GnomeDbWindow</para></listitem>
- <listitem><para>GnomeDbError</para></listitem>
- <listitem><para>GnomeDbErrorDlg</para></listitem>
+ <listitem><para><classname>GnomeDbLogin</classname></para></listitem>
+ <listitem><para><classname>GnomeDbLoginDlg</classname></para></listitem>
+ <listitem><para><classname>GnomeDbDsnConfig</classname></para></listitem>
+ <listitem><para><classname>GnomeDbHelpViewer</classname></para></listitem>
+ <listitem><para><classname>GnomeDbBrowser</classname></para></listitem>
+ <listitem><para><classname>GnomeDbGrid</classname></para></listitem>
+ <listitem><para><classname>GnomeDbDataset</classname></para></listitem>
+ <listitem><para><classname>GnomeDbCombo</classname></para></listitem>
+ <listitem><para><classname>GnomeDbList</classname></para></listitem>
+ <listitem><para><classname>GnomeDbIconList</classname></para></listitem>
+ <listitem><para><classname>GnomeDbReport</classname></para></listitem>
+ <listitem><para><classname>GnomeDbDesigner</classname></para></listitem>
+ <listitem><para><classname>GnomeDbHelp</classname></para></listitem>
+ <listitem><para><classname>GnomeDbShortcut</classname></para></listitem>
+ <listitem><para><classname>GnomeDbWindow</classname></para></listitem>
+ <listitem><para><classname>GnomeDbError</classname></para></listitem>
+ <listitem><para><classname>GnomeDbErrorDlg</classname></para></listitem>
</itemizedlist>
</sect1>
<sect1 id="widgetlib-overview">
- <title>Overview of the &GnomeDB; widgets</title>
+ <title>Overview of the &GNOMEDB; widgets</title>
<para>
This section contains an overview of what can be done with the widgets
- provided by the &GnomeDB; library. It contains short explanations of the
- basic fonctionality and use of each widget.
+ provided by the &GNOMEDB; library. It contains short explanations of
+ the basic functionality and use of each widget.
</para>
<para>
</para>
- <sect2>
+ <sect2 id="gnomedblogin">
<title><classname>GnomeDbLogin</classname> widget</title>
<para>
- The <classname>GnomeDbLogin</classname> widget provides a custom way of visually connecting
- your application to a GDA provider. It can be added to any container
- widget, so that you can create, for example, a dialog box, and then
- add the <classname>GnomeDbLogin</classname> widget to it.
+ The <classname>GnomeDbLogin</classname> widget provides a custom way
+ of visually connecting your application to a <acronym>GDA</acronym>
+ provider. It can be added to any container widget, so that you can
+ create, for example, a dialog box, and then add the <classname>
+ GnomeDbLogin</classname> widget to it.
</para>
<para>
- At initialization, it reads the GDA configuration
- and provides a combo box
- containing all user-configured data sources. The user just have
- to select the data source and provide his/her username and password.
- It also shows a list of the most recently accessed data sources, so
- that you can quickly connect to your "favorite" databases.
+ At initialization, it reads the <acronym>GDA</acronym> configuration
+ and provides a combo box containing all user-configured data sources.
+ The user just has to select the data source and provide his/her
+ username and password. It also shows a list of the most recently
+ accessed data sources, so that you can quickly connect to your
+ "favorite" databases.
</para>
</sect2>
- <sect2>
- <title>GnomeDbLoginDlg widget</title>
+ <sect2 id="gnomedblogindlg">
+ <title><classname>GnomeDbLoginDlg</classname> widget</title>
<para>
- This is a convenience widget which simply contains a GnomeDbLogin
- widget. It is a subclass of GnomeDialog, so you'll expect it to have
- a common look&feel with the rest of your application.
+ This is a convenience widget which simply contains a <classname>
+ GnomeDbLogin</classname> widget. It is a subclass of <classname>
+ GnomeDialog</classname>, so you'll expect it to have a common
+ look&feel with the rest of your application.
</para>
<para>
- This widget not only does it contain the GnomeDbLogin widget, but
- it catches itself the containee's signals, so if you use it, you should
- connect to the GnomeDbLoginDlg signals instead of the GnomeDbLogin
- ones.
+ This widget does not only contain the <classname>GnomeDbLogin
+ </classname> widget, but it catches the containee's signals,
+ so if you use it, you should connect to the <classname>
+ GnomeDbLoginDlg</classname>'s signals instead of the <classname>
+ GnomeDbLogin</classname> ones.
</para>
</sect2>
- <sect2>
- <title>GnomeDbDsnConfig widget</title>
+ <sect2 id="gnomedbdsnconfig">
+ <title><classname>GnomeDbDsnConfig</classname> widget</title>
<para>
- The GnomeDbDsnConfig widget provides a way of letting the user
- visually manage GDA data sources. This widget can easily be
- inserted in a configuration dialog box, for example, and thus
- provide a visual interface to the GDA configuration files.
+ The <classname>GnomeDbDsnConfig</classname> widget provides a way
+ of letting the user visually manage <acronym>GDA</acronym> data
+ sources. This widget can easily be inserted in a configuration dialog
+ box, for example, and thus provides a visual interface to the
+ <acronym>GDA</acronym> configuration files.
</para>
<para>
- This widget is a visual wrapper around the <classname>GdaDsn</classname> management
- functions.
+ This widget is a visual wrapper around the <classname>GdaDsn
+ </classname> management functions.
</para>
</sect2>
- <sect2>
- <title>GnomeDbBrowser widget</title>
+ <sect2 id="gnomedbbrowser">
+ <title><classname>GnomeDbBrowser</classname> widget</title>
<para>
- This is a very complete widget that allows to browse the entire database,
- from tables and views to users and stored procedures. The most simple case
- where you'll want to use this widget is to create a container and
- add the GnomeDbBrowser widget to it. Simply doing this will bring
- a complete database browser to your application.
+ This is a very complete widget that allows to browse the entire
+ database, from tables and views to users and stored procedures. The
+ most simple case where you'll want to use this widget is to create a
+ container and add the <classname>GnomeDbBrowser</classname> widget
+ to it. Simply doing this will bring a complete database browser to
+ your application.
</para>
</sect2>
- <sect2>
- <title>GnomeDbGrid widget</title>
+ <sect2 id="gnomedbgrid">
+ <title><classname>GnomeDbGrid</classname> widget</title>
<para>
This is the most used widget in the library. It provides a way to
- visually inspect a GdaRecordset's contents. The database access part
- responsibility is taken entirely by the widget. You just have to pass
- it valid recordsets to show.
+ visually inspect a <classname>GdaRecordset</classname>'s contents.
+ The database access part responsibility is taken entirely by the
+ widget. You just have to pass it valid recordsets to show.
</para>
<para>
Data is loaded asynchronously, so your program won't block the user
- for accessing other parts of the application. Once the last row has been
- fetched, the GnomeDbGrid emits its "loaded" signal.
+ from accessing other parts of the application. Once the last row has
+ been fetched, the <classname>GnomeDbGrid</classname> emits its
+ "loaded" signal.
</para>
</sect2>
- <sect2>
- <title>GnomeDbDataset widget</title>
+ <sect2 id="gnomedbdataset">
+ <title><classname>GnomeDbDataset</classname> widget</title>
<para>
- The GnomeDbDataset widget allows you to visually navigate recordsets returned
- from the database on a one-by-one basis.
+ The <classname>GnomeDbDataset</classname> widget allows you to
+ visually navigate recordsets returned from the database on a
+ one-by-one basis.
</para>
</sect2>
- <sect2>
- <title>GnomeDbCombo widget</title>
+ <sect2 id="gnomedbcombo">
+ <title><classname>GnomeDbCombo</classname> widget</title>
<para>
This widget is a very useful one. It is mainly used in data input
screens, providing a way by which the user can select a value from
a list of values for a given field.
</para>
<para>
- It works mainly as the GnomeDbGrid widget, since it works based on
- the GdaRecordset's you pass to it, but in this case, you must specify
- which of the columns in the recordset is to be shown.
+ It works mainly as the <classname>GnomeDbGrid</classname> widget,
+ since it works based on the <classname>GdaRecordset</classname>'s
+ you pass to it, but in this case, you must specify which of the
+ columns in the recordset is to be shown.
</para>
</sect2>
- <sect2>
- <title>GnomeDbList widget</title>
+ <sect2 id="gnomedblist">
+ <title><classname>GnomeDbList</classname> widget</title>
<para>
- The GnomeDbList widget lets you show a list of values for a given
- field in a recordset. It also lets you decorate the list with
- icons, resulting in a well looking widget to be included in your
- database access screens.
+ The <classname>GnomeDbList</classname> widget lets you show a list
+ of values for a given field in a recordset. It also lets you
+ decorate the list with icons, resulting in a good looking widget to
+ be included in your database access screens.
</para>
</sect2>
- <sect2>
- <title>GnomeDbReport widget</title>
+ <sect2 id="gnomedbreport">
+ <title><classname>GnomeDbReport</classname> widget</title>
<para>
- The @GnomeDbReport widget provides a way of presenting to the
- user customizable reports based on data coming from a GdaConnection.
- For this, it uses the &Libgda;'s report engine.
+ The <classname>GnomeDbReport</classname> widget provides a way of
+ presenting to the user customizable reports based on data coming
+ from a <classname>GdaConnection</classname>. For this, it uses
+ &LIBGDA;'s report engine.
</para>
<para>
- The report structure is stored in XML format, which makes it possible
- for sharing data with other unrelated applications. This widget just
- reads this XML file, gets the specified data from a given database and
- presents it to the user based on the format instructions specified
- by the report structure.
+ The report structure is stored in <acronym>XML</acronym> format,
+ which makes it possible for sharing data with other unrelated
+ applications. This widget just reads this <acronym>XML</acronym>
+ file, gets the specified data from a given database and presents it
+ to the user based on the format instructions specified by the report
+ structure.
</para>
</sect2>
- <sect2>
- <title>GnomeDbIconList widget</title>
+ <sect2 id="gnomedbiconlist">
+ <title><classname>GnomeDbIconList</classname> widget</title>
<para>
- The @GnomeDbIconList widget works as the @GnomeDbList and
- @GnomeDbCombo widgets. But, in this case, the values present in
+ The <classname>GnomeDbIconList</classname> widget works as the
+ <classname>GnomeDbList</classname> and <classname>GnomeDbCombo
+ </classname> widgets. But, in this case, the values present in
a given field are presented as icons. This offers you - the
developer - another way of presenting data to the user in your
applications.
</para>
</sect2>
- <sect2>
- <title>GnomeDbError widget</title>
+ <sect2 id="gnomedberror">
+ <title><classname>GnomeDbError</classname> widget</title>
<para>
- The GnomeDbError widget provides a way to browse through all the errors
- occured for a given GdaConnection object. You can use it to inform the
- user whenever an error occurs, or as an informational widget.
+ The <classname>GnomeDbError</classname> widget provides a way to
+ browse through all the errors occurred for a given <classname>
+ GdaConnection</classname> object. You can use it to inform the user
+ whenever an error occurs, or as an informational widget.
</para>
</sect2>
- <sect2>
- <title>GnomeDbErrorDlg widget</title>
+ <sect2 id="gnomedberrordlg">
+ <title><classname>GnomeDbErrorDlg</classname> widget</title>
<para>
- As the GnomeDbLoginDlg widget, the GnomeDbErrorDlg widget is just a
- convenience GnomeDialog subclass which just contains a GnomeDbError
- widget.
+ As the <classname>GnomeDbLoginDlg</classname> widget, the
+ <classname>GnomeDbErrorDlg</classname> widget is just a convenience
+ <classname>GnomeDialog</classname> subclass which just contains a
+ <classname>GnomeDbError</classname> widget.
</para>
</sect2>
</sect1>
</chapter>
<chapter id="components">
- <title>Bonobo Components</title>
+ <title><systemitem class="resource">Bonobo</systemitem> Components</title>
<sect1 id="components-introduction">
<title>Introduction</title>
<para>
- &GnomeDB; uses heavily Bonobo, the GNOME components system. As the Bonobo
- API is getting more and more stable, the Bonobo integration in &GnomeDB;
- is bigger. This is a "must" for &GnomeDB;, as it's been included in the
- GNOME Office project, and if we want to have powerful and well-looking
- office applications, the cooperation between these applications is
- crutial.
+ &GNOMEDB; heavily uses <systemitem class="resource">Bonobo</systemitem>
+ , the GNOME components system. As the <systemitem class="resource">
+ Bonobo</systemitem> <acronym>API</acronym> is getting more and more
+ stable, the <systemitem class="resource">Bonobo</systemitem>
+ integration in &GNOMEDB; is growing bigger. This is a "must" for
+ &GNOMEDB;, as it's been included in the GNOME Office project, and if
+ we want to have powerful and good-looking office applications,
+ the cooperation between these applications is crucial.
</para>
<para>
- The applications included with &GnomeDB; are theirselves componentized,
+ The applications included with &GNOMEDB; are theirselves componentized,
so that some parts of them can be embedded in other applications. Apart
from this, a whole set of database-aware components are also included.
</para>
<para>
- In fact, when you execute the &GnomeDB; frontend, you're running just a
- simple container whose unique job is to load &GnomeDB; components into
- itself.
+ In fact, when you execute the &GNOMEDB; front-end, you're just running
+ a simple container whose only job is to load &GNOMEDB; components
+ into itself.
</para>
</sect1>
</chapter>
<chapter id="manager">
- <title>&GnomeDB; Manager</title>
+ <title>&GNOMEDB; Manager</title>
<sect1 id="manager-introduction">
<title>Introduction</title>
<para>
- &GnomeDB; comes with a configuration GUI to perform database
+ &GNOMEDB; comes with a configuration GUI to perform database
administration tasks. This tool is the <filename>gnomedb-mgr</filename>
- application. It's got two purposes, one of which is to let you configure
- all your &GnomeDB; environment, by adding/removing and modifying data sources
- and providers. The other one is to serve as a container for you to load the
- different DBMS configuration components, so that you can administer the
- underlying databases.
+ application. It's got two purposes, one of which is to let you
+ configure all your &GNOMEDB; environment, by adding/removing and
+ modifying data sources and providers. The other one is to serve as a
+ container for you to load the different <acronym>DBMS</acronym>
+ configuration components, so that you can administer the underlying
+ databases.
</para>
</sect1>
<sect1 id="manager-config-components">
<title>Configuration components</title>
<para>
- As stated before, each provider comes with a configuration module,
- in the form of a Bonobo component, which is then loaded by the
- <filename>gnomedb-mgr</filename> application.
+ As stated before, each provider comes with a configuration module, in
+ the form of a <systemitem class="resource">Bonobo</systemitem>
+ component, which is then loaded by the <filename>gnomedb-mgr</filename>
+ application.
</para>
<para>
- The features provided by these Bonobo components are specific to each
- implementation, so there is no assumption on what they do, and the
- <filename>gnomedb-mgr</filename> tool acts just as a container for them.
+ The features provided by these <systemitem class="resource">Bonobo
+ </systemitem> components are specific to each implementation, so there
+ is no assumption on what they do, and the <filename>gnomedb-mgr
+ </filename> tool acts just as a container for them.
</para>
<para>
- The only thing that is assumed about the Bonobo components, is the set
- of properties they export to the outside world. Thus, a client application
- (in this case, <filename>gnomedb-mgr</filename>) can easily affect the
- behavior of the components. The properties currently supported are:
+ The only thing that is assumed about the <systemitem class="resource">
+ Bonobo</systemitem> components, is the set of properties they export to
+ the outside world. Thus, a client application (in this case, <filename>
+ gnomedb-mgr</filename>) can easily affect the behavior of the
+ components. The properties currently supported are:
</para>
<itemizedlist>
<listitem>
<para>
- <emphasis>DSN</emphasis>: specifies the data source string for opening
- a connection to the underlying database. Note that this string is NOT the
- GDA name of the data source, BUT the DSN entry in the &Libgda;
- configuration. The provider, which may be on a different machine, might know nothing
- about the client's &Libgda; local configuration.
+ <emphasis>DSN</emphasis>: specifies the data source string for
+ opening a connection to the underlying database. Note that this
+ string is NOT the <acronym>GDA</acronym> name of the data source,
+ BUT the DSN entry in the &LIBGDA; configuration. The provider,
+ which may be on a different machine, might know nothing about the
+ client's &LIBGDA; local configuration.
</para>
</listitem>
<listitem>
@@ -398,11 +437,11 @@
<title>Introduction</title>
<para>
The front-end application (<filename>gnomedb-fe</filename>) is a nice
- application that provides access to all the &Libgda; model's power
- through a consistent and well-looking user interface. The front-end
- makes use of all the interfaces provided by the &GnomeDB; libraries. This
- consist in a consistent look&feel with the rest of the applications
- contained in the suite.
+ application that provides access to all the &LIBGDA; model's power
+ through a consistent and good-looking user interface. The front-end
+ makes use of all the interfaces provided by the &GNOMEDB; libraries.
+ This results in a consistent look&feel with the rest of the
+ applications contained in the suite.
</para>
<para>
You can use it to query your database, export and import data
@@ -412,5 +451,626 @@
</para>
</sect1>
</chapter>
-
+ <!--
+ The GNU Free Documentation License 1.1 in DocBook
+ Markup by Eric Baudais <baudais okstate edu>
+ Maintained by the GNOME Documentation Project
+ http://developer.gnome.org/projects/gdp
+ Version: 1.0.1
+ Last Modified: Nov 16, 2000
+ -->
+
+ <appendix id="fdl">
+ <docinfo>
+ <releaseinfo>
+ Version 1.1, March 2000
+ </releaseinfo>
+ <copyright>
+ <year>2000</year><holder>Free Software Foundation, Inc.</holder>
+ </copyright>
+ <legalnotice id="fdl-legalnotice">
+ <para>
+ <address>Free Software Foundation, Inc. <street>59 Temple Place,
+ Suite 330</street>, <city>Boston</city>, <state>MA</state>
+ <postcode>02111-1307</postcode> <country>USA</country></address>
+ Everyone is permitted to copy and distribute verbatim copies of this
+ license document, but changing it is not allowed.
+ </para>
+ </legalnotice>
+ </docinfo>
+ <title>GNU Free Documentation License</title>
+
+ <sect1 id="fdl-preamble">
+ <title>0. PREAMBLE</title>
+ <para>
+ The purpose of this License is to make a manual, textbook, or
+ other written document <quote>free</quote> 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.
+ </para>
+
+ <para>
+ This License is a kind of <quote>copyleft</quote>, 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.
+ </para>
+
+ <para>
+ 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.
+ </para>
+ </sect1>
+ <sect1 id="fdl-section1">
+ <title>1. APPLICABILITY AND DEFINITIONS</title>
+ <para id="fdl-document">
+ 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
+ <quote>Document</quote>, below, refers to any such manual or
+ work. Any member of the public is a licensee, and is addressed
+ as <quote>you</quote>.
+ </para>
+
+ <para id="fdl-modified">
+ A <quote>Modified Version</quote> 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.
+ </para>
+
+ <para id="fdl-secondary">
+ A <quote>Secondary Section</quote> is a named appendix or a
+ front-matter section of the <link linkend="fdl-document">Document</link> 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.
+ </para>
+
+ <para id="fdl-invariant">
+ The <quote>Invariant Sections</quote> are certain <link linkend="fdl-secondary"> Secondary Sections</link> whose titles
+ are designated, as being those of Invariant Sections, in the
+ notice that says that the <link linkend="fdl-document">Document</link> is released under this
+ License.
+ </para>
+
+ <para id="fdl-cover-texts">
+ The <quote>Cover Texts</quote> are certain short passages of
+ text that are listed, as Front-Cover Texts or Back-Cover Texts,
+ in the notice that says that the <link linkend="fdl-document">Document</link> is released under this
+ License.
+ </para>
+
+ <para id="fdl-transparent">
+ A <quote>Transparent</quote> copy of the <link linkend="fdl-document"> Document</link> 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 <quote>Transparent</quote> is called
+ <quote>Opaque</quote>.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para id="fdl-title-page">
+ The <quote>Title Page</quote> 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, <quote>Title Page</quote> means the text near the
+ most prominent appearance of the work's title, preceding the
+ beginning of the body of the text.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section2">
+ <title>2. VERBATIM COPYING</title>
+ <para>
+ You may copy and distribute the <link linkend="fdl-document">Document</link> 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 <link linkend="fdl-section3">section 3</link>.
+ </para>
+
+ <para>
+ You may also lend copies, under the same conditions stated
+ above, and you may publicly display copies.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section3">
+ <title>3. COPYING IN QUANTITY</title>
+ <para>
+ If you publish printed copies of the <link linkend="fdl-document">Document</link> numbering more than 100,
+ and the Document's license notice requires <link linkend="fdl-cover-texts">Cover Texts</link>, 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
+ <link linkend="fdl-document">Document</link> and satisfy these
+ conditions, can be treated as verbatim copying in other
+ respects.
+ </para>
+
+ <para>
+ 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.
+ </para>
+
+ <para>
+ If you publish or distribute <link linkend="fdl-transparent">Opaque</link> copies of the <link linkend="fdl-document">Document</link> numbering more than 100,
+ you must either include a machine-readable <link linkend="fdl-transparent">Transparent</link> 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.
+ </para>
+
+ <para>
+ It is requested, but not required, that you contact the authors
+ of the <link linkend="fdl-document">Document</link> well before
+ redistributing any large number of copies, to give them a chance
+ to provide you with an updated version of the Document.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section4">
+ <title>4. MODIFICATIONS</title>
+ <para>
+ You may copy and distribute a <link linkend="fdl-modified">Modified Version</link> of the <link linkend="fdl-document">Document</link> under the conditions of
+ sections <link linkend="fdl-section2">2</link> and <link linkend="fdl-section3">3</link> 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:
+ </para>
+
+ <itemizedlist mark="opencircle">
+ <listitem>
+ <formalpara>
+ <title>A</title>
+ <para>
+ Use in the <link linkend="fdl-title-page">Title
+ Page</link> (and on the covers, if any) a title distinct
+ from that of the <link linkend="fdl-document">Document</link>, 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.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>B</title>
+ <para>
+ List on the <link linkend="fdl-title-page">Title
+ Page</link>, as authors, one or more persons or entities
+ responsible for authorship of the modifications in the
+ <link linkend="fdl-modified">Modified Version</link>,
+ together with at least five of the principal authors of
+ the <link linkend="fdl-document">Document</link> (all of
+ its principal authors, if it has less than five).
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>C</title>
+ <para>
+ State on the <link linkend="fdl-title-page">Title
+ Page</link> the name of the publisher of the <link linkend="fdl-modified">Modified Version</link>, as the
+ publisher.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>D</title>
+ <para>
+ Preserve all the copyright notices of the <link linkend="fdl-document">Document</link>.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>E</title>
+ <para>
+ Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>F</title>
+ <para>
+ Include, immediately after the copyright notices, a
+ license notice giving the public permission to use the
+ <link linkend="fdl-modified">Modified Version</link> under
+ the terms of this License, in the form shown in the
+ Addendum below.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>G</title>
+ <para>
+ Preserve in that license notice the full lists of <link linkend="fdl-invariant"> Invariant Sections</link> and
+ required <link linkend="fdl-cover-texts">Cover
+ Texts</link> given in the <link linkend="fdl-document">Document's</link> license notice.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>H</title>
+ <para>
+ Include an unaltered copy of this License.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>I</title>
+ <para>
+ Preserve the section entitled <quote>History</quote>, and
+ its title, and add to it an item stating at least the
+ title, year, new authors, and publisher of the <link linkend="fdl-modified">Modified Version </link>as given on
+ the <link linkend="fdl-title-page">Title Page</link>. If
+ there is no section entitled <quote>History</quote> in the
+ <link linkend="fdl-document">Document</link>, 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.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>J</title>
+ <para>
+ Preserve the network location, if any, given in the <link linkend="fdl-document">Document</link> for public access
+ to a <link linkend="fdl-transparent">Transparent</link>
+ 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 <quote>History</quote>
+ 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.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>K</title>
+ <para>
+ In any section entitled <quote>Acknowledgements</quote> or
+ <quote>Dedications</quote>, 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.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>L</title>
+ <para>
+ Preserve all the <link linkend="fdl-invariant">Invariant
+ Sections</link> of the <link linkend="fdl-document">Document</link>, unaltered in their
+ text and in their titles. Section numbers or the
+ equivalent are not considered part of the section titles.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>M</title>
+ <para>
+ Delete any section entitled
+ <quote>Endorsements</quote>. Such a section may not be
+ included in the <link linkend="fdl-modified">Modified
+ Version</link>.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>N</title>
+ <para>
+ Do not retitle any existing section as
+ <quote>Endorsements</quote> or to conflict in title with
+ any <link linkend="fdl-invariant">Invariant
+ Section</link>.
+ </para>
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ If the <link linkend="fdl-modified">Modified Version</link>
+ includes new front-matter sections or appendices that qualify as
+ <link linkend="fdl-secondary">Secondary Sections</link> 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 <link linkend="fdl-invariant">Invariant Sections</link> in the
+ Modified Version's license notice. These titles must be
+ distinct from any other section titles.
+ </para>
+
+ <para>
+ You may add a section entitled <quote>Endorsements</quote>,
+ provided it contains nothing but endorsements of your <link linkend="fdl-modified">Modified Version</link> 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.
+ </para>
+
+ <para>
+ You may add a passage of up to five words as a <link linkend="fdl-cover-texts">Front-Cover Text</link>, and a passage
+ of up to 25 words as a <link linkend="fdl-cover-texts">Back-Cover Text</link>, to the end of
+ the list of <link linkend="fdl-cover-texts">Cover Texts</link>
+ in the <link linkend="fdl-modified">Modified Version</link>.
+ 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 <link linkend="fdl-document">Document</link>
+ 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.
+ </para>
+
+ <para>
+ The author(s) and publisher(s) of the <link linkend="fdl-document">Document</link> do not by this License
+ give permission to use their names for publicity for or to
+ assert or imply endorsement of any <link linkend="fdl-modified">Modified Version </link>.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section5">
+ <title>5. COMBINING DOCUMENTS</title>
+ <para>
+ You may combine the <link linkend="fdl-document">Document</link>
+ with other documents released under this License, under the
+ terms defined in <link linkend="fdl-section4">section 4</link>
+ above for modified versions, provided that you include in the
+ combination all of the <link linkend="fdl-invariant">Invariant
+ Sections</link> of all of the original documents, unmodified,
+ and list them all as Invariant Sections of your combined work in
+ its license notice.
+ </para>
+
+ <para>
+ The combined work need only contain one copy of this License,
+ and multiple identical <link linkend="fdl-invariant">Invariant
+ Sections</link> 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.
+ </para>
+
+ <para>
+ In the combination, you must combine any sections entitled
+ <quote>History</quote> in the various original documents,
+ forming one section entitled <quote>History</quote>; likewise
+ combine any sections entitled <quote>Acknowledgements</quote>,
+ and any sections entitled <quote>Dedications</quote>. You must
+ delete all sections entitled <quote>Endorsements.</quote>
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section6">
+ <title>6. COLLECTIONS OF DOCUMENTS</title>
+ <para>
+ You may make a collection consisting of the <link linkend="fdl-document">Document</link> 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.
+ </para>
+
+ <para>
+ You may extract a single document from such a collection, and
+ dispbibute 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.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section7">
+ <title>7. AGGREGATION WITH INDEPENDENT WORKS</title>
+ <para>
+ A compilation of the <link linkend="fdl-document">Document</link> 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 <link linkend="fdl-modified">Modified Version</link>
+ of the Document, provided no compilation copyright is claimed
+ for the compilation. Such a compilation is called an
+ <quote>aggregate</quote>, 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 <link linkend="fdl-cover-texts">Cover Text</link> requirement of <link linkend="fdl-section3">section 3</link> 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.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section8">
+ <title>8. TRANSLATION</title>
+ <para>
+ Translation is considered a kind of modification, so you may
+ distribute translations of the <link linkend="fdl-document">Document</link> under the terms of <link linkend="fdl-section4">section 4</link>. Replacing <link linkend="fdl-invariant"> Invariant Sections</link> 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.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section9">
+ <title>9. TERMINATION</title>
+ <para>
+ You may not copy, modify, sublicense, or distribute the <link linkend="fdl-document">Document</link> 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.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section10">
+ <title>10. FUTURE REVISIONS OF THIS LICENSE</title>
+ <para>
+ The <ulink url="http://www.gnu.org/fsf/fsf.html"; type="http">Free Software
+ Foundation</ulink> 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
+ <ulink url="http://www.gnu.org/copyleft"; type="http">http://www.gnu.org/copyleft/</ulink>.
+ </para>
+
+ <para>
+ Each version of the License is given a distinguishing version
+ number. If the <link linkend="fdl-document">Document</link>
+ specifies that a particular numbered version of this License
+ <quote>or any later version</quote> 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.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-using">
+ <title>Addendum</title>
+ <para>
+ 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:
+ </para>
+
+ <blockquote>
+ <para>
+ Copyright © YEAR YOUR NAME.
+ </para>
+ <para>
+ 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 the <link linkend="fdl-invariant">Invariant Sections</link> being LIST
+ THEIR TITLES, with the <link linkend="fdl-cover-texts">Front-Cover Texts</link> being LIST,
+ and with the <link linkend="fdl-cover-texts">Back-Cover
+ Texts</link> being LIST. A copy of the license is included in
+ the section entitled <quote>GNU Free Documentation
+ License</quote>.
+ </para>
+ </blockquote>
+
+ <para>
+ If you have no <link linkend="fdl-invariant">Invariant
+ Sections</link>, write <quote>with no Invariant Sections</quote>
+ instead of saying which ones are invariant. If you have no
+ <link linkend="fdl-cover-texts">Front-Cover Texts</link>, write
+ <quote>no Front-Cover Texts</quote> instead of
+ <quote>Front-Cover Texts being LIST</quote>; likewise for <link linkend="fdl-cover-texts">Back-Cover Texts</link>.
+ </para>
+
+ <para>
+ 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 <ulink url="http://www.gnu.org/copyleft/gpl.html"; type="http"> GNU General Public
+ License</ulink>, to permit their use in free software.
+ </para>
+ </sect1>
+ </appendix>
</book>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
