Commit e8e0c05a authored by John Fleck's avatar John Fleck

John Fleck <jfleck@inkstain.net>


John Fleck <jfleck@inkstain.net>

removing:
	* xmldocs.make
	* sgmldocs.make
	* omf-install/Makefile.am
	* gnome-session/help/Makefile.am
	* gnome-session/help/C/Makefile.am
	* gnome-session/help/C/session-C.omf
	* gnome-session/help/C/session.sgml
	* gnome-session/help/C/figures/*.png
	* gnome-session/help/ja/Makefile.am
	* gnome-session/help/ja/session-C.omf
	* gnome-session/help/ja/session.sgml
	* gnome-session/help/ja/figures/*.png
	removing old docs cruft, fixes bug #113567
parent 72f30e6d
2003-07-09 John Fleck <jfleck@inkstain.net>
removing:
* xmldocs.make
* sgmldocs.make
* omf-install/Makefile.am
* gnome-session/help/Makefile.am
* gnome-session/help/C/Makefile.am
* gnome-session/help/C/session-C.omf
* gnome-session/help/C/session.sgml
* gnome-session/help/C/figures/*.png
* gnome-session/help/ja/Makefile.am
* gnome-session/help/ja/session-C.omf
* gnome-session/help/ja/session.sgml
* gnome-session/help/ja/figures/*.png
removing old docs cruft, fixes bug #113567
==================== 2.3.3.1 ====================
2003-07-04 Mark McLoughlin <mark@skynet.ie>
......
figs = \
figures/button_remove.png \
figures/session-properties.png \
figures/stock_exec.png \
figures/stock_help.png \
figures/stock_preferences.png \
figures/stock_refresh.png \
figures/stock_save.png \
figures/stock_timer.png \
figures/stock_trash.png
docname = session
lang = C
omffile = session-C.omf
sgml_ents =
include $(top_srcdir)/sgmldocs.make
dist-hook: app-dist-hook
<?xml version="1.0" standalone="no"?>
<omf>
<resource>
<title>
Session Properties Manual
</title>
<subject>
<category>GNOME|Core Desktop</category>
</subject>
<format mime="text/sgml"/>
<identifier url="session.sgml"/>
<language code="C"/>
</resource>
</omf>
<!DOCTYPE article PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"[
]>
<article id="index">
<artheader>
<title>Session Properties Manual</title>
<copyright>
<year>2000</year>
<holder>Eric Baudais</holder>
</copyright>
<!-- translators: uncomment this:
<copyright>
<year>2000</year>
<holder>ME-THE-TRANSLATOR (Latin translation)</holder>
</copyright>
-->
<!-- do not put authorname in the header except in copyright - use
section "authors" below -->
<legalnotice id="legalnotice">
<para>Permission is granted to copy, distribute and/or modify this
document under the terms of the <ulink type="help"
url="gnome-help:fdl"><citetitle>GNU Free Documentation
License</citetitle></ulink>, 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 <ulink type="help"
url="gnome-help:fdl">here</ulink>.</para>
<para>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>
<!-- this is version of manual, not application --> <releaseinfo>
This is version 1.0 of Session Properties manual.
</releaseinfo>
<!-- FIXME: Need to add a longer introduction. -->
</artheader>
<sect1 id="session-properties">
<title>Session Properties</title>
<para>
<systemitem>Session Properties</systemitem> monitors the
state of current GNOME running applications and capplets, as seen in
<link linkend="session-properties-screenshot">Figure 1</link>. <systemitem>
Session Properties</systemitem> displays a list of all the
applications and capplets currently running, what will happen to
the program if you logout, and the state of the application. It allows
you to change the style and priority of each program. You
can shut down applications, if you wish, and those applications
will be removed from your GNOME session. You can also use
<systemitem>Session Properties</systemitem> to kill a GNOME
application and remove it from <systemitem>session management
</systemitem> so it will not be restarted when you log in next
time. Of course, there are other ways to kill an
application, such as using an explicit kill command, but they
would not prevent an application from being restarted if it has
the <link linkend="session-properties-respawn"><guilabel>Respawn
Style</guilabel></link>. The only way to permanently remove such
an application is with the <link linkend="session-properties-remove">
<guibutton>Remove</guibutton></link> button.
</para>
<note>
<title>Note:</title>
<para>
Applications that are not 100 percent GNOME compliant are not managed
by the <systemitem>session manager</systemitem>. To check if
an application is GNOME compliant start <systemitem>Session
Properties</systemitem>. If the application is shown in the
list it is compliant with GNOME and is managed by the
<systemitem>session manager</systemitem>. In order
to restart non-GNOME complaint applications when you log in
<!-- <link linkend="startup-programs-non-session-managed"> -->see
Non-session-managed Startup Programs<!-- </link> -->.
</para>
</note>
<!-- FIXME: Need to add a section over basic usage. -->
<!-- FIXME: Need to add an introduction to customization of the SM. -->
<figure id="session-properties-screenshot">
<title>Session Properties Dialog</title>
<screenshot>
<screeninfo>Screenshot of the session properties manager.</screeninfo>
<graphic Format="png" Fileref="figures/session-properties.png" srccredit="Eric Baudais">
</graphic>
</screenshot>
</figure>
<sect2 id="session-properties-save">
<title>Saving the GNOME Session</title>
<para>
To save your GNOME session select <menuchoice><guimenu>Main Menu</guimenu>
<guisubmenu>Programs</guisubmenu><guisubmenu>Settings</guisubmenu>
<guisubmenu>Session</guisubmenu><guimenuitem>Save Current Session
</guimenuitem></menuchoice>. This causes all the applications to save
their current state: the application's current settings
and work (open files and unsaved data).
</para>
<note>
<title>Note:</title>
<para>
Applications that are not compliant with GNOME will not save the current settings
or work associated with the application. It is recommended that you save your work
periodically in case of a calamity.
</para>
</note>
</sect2>
<sect2 id="session-properties-order">
<title>Priority Order</title>
<para>
The <guilabel>priority order</guilabel> sets the order the applications
will start in the GNOME <link linkend="session-properties-screenshot">
<systemitem>Session Manager</systemitem></link>. This lets applications be started
after other applications or capplets they are dependent upon.
If an application needs to start before the <systemitem>window manager
</systemitem>, like a server, you can change the <guilabel>order</guilabel>
number to be lower than the <systemitem>window manager's</systemitem>
<guilabel>order</guilabel> number. Usually most applications will have
an order number of 50. If the application or capplet is a part of the
<systemitem>window manager</systemitem> or critical system then it
should be assigned a lower <guilabel>order</guilabel> number.
</para>
<important>
<title>Important:</title>
<para>
The <guilabel>priority order</guilabel> is for advanced user only. Unless you are familiar
with the <guilabel>priority order</guilabel> you should not change it.
</para>
</important>
</sect2>
<sect2 id="session-properties-style">
<title>Style Options</title>
<para>
The <guilabel>Style</guilabel> option sets the restart style of
each application running in the GNOME <link linkend="session-properties-screenshot">
<systemitem>Session Manager</systemitem></link>. When an application closes the <guilabel>style
</guilabel> option controls what happens to the program. The style most
applications run with is <guilabel>Normal</guilabel>. There are currently
four styles of applications and capplets.
</para>
<itemizedlist mark="opencircle">
<listitem>
<para id="session-properties-normal">
<guilabel>Normal</guilabel> - This style starts the application
when you log back in, but it allows the application to close
normally given a <command>kill</command> command.
The vast majority of applications you run will have this style
and it is safe to assume this style when in doubt. All you will
see is a blank space in the <guilabel>style</guilabel> row unlike
other styles.
</para>
</listitem>
<listitem>
<para id="session-properties-respawn">
<guiicon>
<inlinegraphic fileref="figures/stock_refresh.png" format="png" srccredit="Tuomas Kuosmanen">
</inlinegraphic>
</guiicon>
<guilabel>Respawn</guilabel> - This style starts the application
or capplet again once it is given the <command>kill</command>
command. It is used primarily for applications or servers that
need to run continuously regardless of user intervention. Two
examples of applications running with the <guilabel>respawn</guilabel>
style is the GNOME <systemitem>Session Manager</systemitem> and
the GNOME <systemitem>Panel</systemitem>.
</para>
</listitem>
<listitem>
<para id="session-properties-trash">
<guiicon>
<inlinegraphic fileref="figures/stock_trash.png" format="png" srccredit="Tuomas Kuosmanen">
</inlinegraphic>
</guiicon>
<guilabel>Trash</guilabel> - This style indicates applications
or capplets that are only temporary. When you logout, the applications
with this style are killed, after saving their data, and do not restart
when you login again.
</para>
</listitem>
<listitem>
<para id="session-properties-settings">
<guiicon>
<inlinegraphic fileref="figures/stock_preferences.png" format="png" srccredit="Tuomas Kuosmanen">
</inlinegraphic>
</guiicon>
<guilabel>Settings</guilabel> - This style indicates applications
or capplets used only for storing and relaying your settings to
GNOME and GNOME compliant applications. These applications and
capplets usually have a lower priority order and handle configurations.
</para>
</listitem>
</itemizedlist>
<important>
<title>Important:</title>
<para>
The <guilabel>Style</guilabel> option is for advanced users only.
Unless you are familiar with the <guilabel>Style</guilabel> settings
you should not change it.
</para>
</important>
</sect2>
<sect2 id="startup-programs-state">
<title>State</title>
<para>
The <guilabel>state</guilabel> of an application tells you what the
application or capplet is doing, at the moment, in the GNOME
<link linkend="session-properties-screenshot"><systemitem>
Session Manager</systemitem></link>. Most of the time you will see
they are either in the <link linkend="session-properties-inactive">
Inactive</link> state or in the <link linkend="session-properties-run">
Running</link> state.
</para>
<itemizedlist mark="opencircle">
<listitem>
<para id="session-properties-inactive">
<guilabel>Inactive</guilabel> - Applications in the <guilabel>inactive
state</guilabel> are either waiting to start or have finished running.
These applications are waiting for you or another user to run them.
Unlike other states the <guilabel>inactive state</guilabel> has no
icon associated with it. All you will see is a blank space in the
<guilabel>state</guilabel> row.
</para>
</listitem>
<listitem>
<para id="session-properties-run">
<guiicon>
<inlinegraphic fileref="figures/stock_exec.png" format="png" srccredit="Tuomas Kuosmanen">
</inlinegraphic>
</guiicon>
<guilabel>Running</guilabel> - Applications in the <guilabel>running
state</guilabel> are running normally in your session. This is the
default state for applications and the most common.
</para>
</listitem>
<listitem>
<para id="session-properties-start">
<guiicon>
<inlinegraphic fileref="figures/stock_timer.png" format="png" srccredit="Tuomas Kuosmanen">
</inlinegraphic>
</guiicon>
<guilabel>Starting</guilabel> - Applications in the <guilabel>starting
state</guilabel> are being given time to get running. Most applications
go to the <guilabel>running state</guilabel> almost instanteously. You
usually won't see this state unless it takes a little bit of time for the
application to start.
</para>
</listitem>
<listitem>
<para id="sessionm-properties-saving">
<guiicon>
<inlinegraphic fileref="figures/stock_save.png" format="png" srccredit="Tuomas Kuosmanen">
</inlinegraphic>
</guiicon>
<guilabel>Saving</guilabel> - Applications in the <guilabel>saving
state</guilabel> are saving their current settings and data. This
state occurs when the GNOME <systemitem>session manager</systemitem>
tells each application to save when you logout or when you
<link linkend="session-properties-save">save the session</link> manually.
</para>
</listitem>
<listitem>
<para id="session-properties-unknown">
<guiicon>
<inlinegraphic fileref="figures/stock_help.png" format="png" srccredit="Tuomas Kuosmanen">
</inlinegraphic>
</guiicon>
<guilabel>Unknown</guilabel> - Applications in the <guilabel>unknown
state</guilabel> do not have any contact with the GNOME <systemitem>
session manager</systemitem>. This usually means the application
has crashed. If this happens highlight the application in <systemitem>
Session Properties</systemitem> and then click the <link linkend="session-properties-remove">
<guibutton>Remove</guibutton></link> button.
</para>
</listitem>
</itemizedlist>
</sect2>
<sect2 id="session-properties-remove">
<title>Remove Button</title>
<para>
<guiicon>
<inlinegraphic fileref="figures/button_remove.png" format="png" srccredit="Eric Baudais">
</inlinegraphic>
</guiicon>
The <guibutton>Remove</guibutton> button removes the application from the GNOME
<link linkend="session-properties-screenshot"><systemitem>session manager</systemitem>
</link> and kills the application. You should
use the <guibutton>Remove</guibutton> button to kill an application after it
crashes or when its <guilabel>state</guilabel> is <link linkend="session-properties-respawn">
<guilabel>Respawn</guilabel></link>.
</para>
</sect2>
</sect1>
<!-- ============= Bugs ================================== -->
<sect1 id="bugs">
<title>Known Bugs and Limitations</title>
<para>
This application has no known bugs.
</para>
</sect1>
<!-- ============= Authors ================================ -->
<sect1 id="authors">
<title>Authors</title>
<para>
<application>Session Management</application> was written by Tom Tromey
(<email>tromey@cygnus.com</email>). It is currently being maintianed
by Jacob Berkman (<email>jacob@helixcode.com</email>). Please send all
comments, suggestions, and bug
reports to the <ulink url="http://bugs.gnome.org/" type="http">GNOME
bug tracking database</ulink>. Instructions for submitting bug
reports can be found on-line at <ulink
url="http://bugs.gnome.org/Reporting.html" type="http">
http://bugs.gnome.org/Reporting.html</ulink>. If you are using
GNOME 1.1 or later, you can also use <application>Bug Report
Tool</application> (<command>bug-buddy</command>), available in the
<guisubmenu>Utilities</guisubmenu> submenu of <guimenu>Main
Menu</guimenu>, for submitting bug reports.
</para>
<para>
This manual was written by Eric Baudais
(<email>baudais@okstate.edu</email>). Please send all comments and
suggestions regarding this manual to the <ulink type="http"
url="http://developer.gnome.org/projects/gdp/">GNOME Documentation Project</ulink>
by sending an email to <email>docs@gnome.org</email>. You can also
add your comments online by using the <ulink type="http"
url="http://developer.gnome.org/projects/gdp/doctable/">GNOME Documentation Status
Table</ulink>.
</para>
<!-- For translations: uncomment this:
<para>
Latin translation was done by ME
(<email>MYNAME@MYADDRESS</email>). Please send all comments and
suggestions regarding this translation to SOMEWHERE.
</para>
-->
</sect1>
<!-- ============= Application License ============================= -->
<sect1 id="license">
<title>License</title>
<para>
This program is free software; you can redistribute it and/or
modify it under the terms of the <ulink type="help"
url="gnome-help:gpl"><citetitle>GNU General Public
License</citetitle></ulink> as published by the Free Software
Foundation; either version 2 of the License, or (at your option)
any later version.
</para>
<para>
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
<ulink type="help" url="gnome-help:gpl"><citetitle>GNU General
Public License</citetitle></ulink> for more details.
</para>
<para>
A copy of the <ulink type="help"
url="gnome-help:gpl"><citetitle>GNU General Public
License</citetitle></ulink> is included with the GNOME documentation.
You may also obtain a copy of the <ulink type="help"
url="gnome-help:gpl"><citetitle>GNU General Public
License</citetitle></ulink> from the Free Software Foundation by
visiting <ulink type="http" url="http://www.fsf.org/">their Web
site</ulink> or by writing to
<address>
The Free Software Foundation, Inc.,
<street>59 Temple Place</street> - Suite 330,
<city>Boston</city>, <state>MA</state> <postcode>02111-1307</postcode>,
<country>USA</country>
</address>
</para>
</sect1>
</article>
figs = \
figures/button_remove.png \
figures/session-properties.png \
figures/stock_exec.png \
figures/stock_help.png \
figures/stock_preferences.png \
figures/stock_refresh.png \
figures/stock_save.png \
figures/stock_timer.png \
figures/stock_trash.png
docname = session
lang = ja
omffile = session-ja.omf
sgml_ents =
include $(top_srcdir)/sgmldocs.make
dist-hook: app-dist-hook
<?xml version="1.0" standalone="no"?>
<omf>
<resource>
<title>
セッションプロパティマニュアル
</title>
<subject>
<category>GNOME|コアデスクトップ</category>
</subject>
<format mime="text/sgml"/>
<identifier url="session.sgml"/>
<language code="ja"/>
</resource>
</omf>
This diff is collapsed.
#
# Modify the definition of $omf_dest_dir, replacing "gdp-example1" with
# the name of your package.
#
# No other modifications should be necessary.
#
# Note that you must configure your package with --localstatedir=/var/lib
# so that the scrollkeeper-update command below will update the database
# in the standard scrollkeeper directory.
#
# If it is impossible to configure with --localstatedir=/var/lib, then
# modify the definition of scrollkeeper_localstate_dir so that
# it points to the correct location. Note that you must still use
# $(localstatedir) in this or when people build RPMs it will update
# the real database on their system instead of the one under RPM_BUILD_ROOT.
omf_dest_dir=$(datadir)/omf/gnome-core
scrollkeeper_localstate_dir = $(localstatedir)/scrollkeeper
install-data-local:
$(mkinstalldirs) $(DESTDIR)$(omf_dest_dir)
-for file in $(srcdir)/*.omf; do \
$(INSTALL_DATA) $(srcdir)/$$file $(DESTDIR)$(omf_dest_dir); \
done
-scrollkeeper-update -p $(scrollkeeper_localstate_dir)
uninstall-local:
-for file in $(srcdir)/*.omf; do \
basefile=`basename $$file`; \
rm -f $(omf_dest_dir)/$$basefile; \
done
-rmdir $(omf_dest_dir)
-scrollkeeper-update -p $(scrollkeeper_localstate_dir)
# To use this template:
# 1) Define: figs, docname, lang, omffile, sgml_ents although figs,
# omffile, and sgml_ents may be empty in your Makefile.am which
# will "include" this one
# 2) Figures must go under figures/ and be in PNG format
# 3) You should only have one document per directory
#
# Note that this makefile forces the directory name under
# $prefix/share/gnome/help/ to be the same as the SGML filename
# of the document. This is required by GNOME. eg:
# $prefix/share/gnome/help/fish_applet/C/fish_applet.sgml
# ^^^^^^^^^^^ ^^^^^^^^^^^
# Definitions:
# figs A list of screenshots which will be included in EXTRA_DIST
# Note that these should reside in figures/ and should be .png
# files, or you will have to make modifications below.
# docname This is the name of the SGML file: <docname>.sgml
# lang This is the document locale
# omffile This is the name of the OMF file. Convention is to name
# it <docname>-<locale>.omf.
# sgml_ents This is a list of SGML entities which must be installed
# with the main SGML file and included in EXTRA_DIST.
# eg:
# figs = \
# figures/fig1.png \
# figures/fig2.png
# docname = scrollkeeper-manual
# lang = C
# omffile=scrollkeeper-manual-C.omf
# sgml_ents = fdl.sgml
# include $(top_srcdir)/help/sgmldocs.make
# dist-hook: app-dist-hook
#
docdir = $(datadir)/gnome/help/$(docname)/$(lang)
doc_DATA = index.html
sgml_files = $(sgml_ents) $(docname).sgml
omf_dir=$(top_srcdir)/omf-install
EXTRA_DIST = $(sgml_files) $(doc_DATA) $(omffile) $(figs)
CLEANFILES = omf_timestamp
all: index.html omf
omf: omf_timestamp
omf_timestamp: $(omffile)
-for file in $(omffile); do \
scrollkeeper-preinstall $(docdir)/$(docname).sgml $$file $(omf_dir)/$$file; \
done
touch omf_timestamp
index.html: $(docname)/index.html
-cp $(docname)/index.html .
$(docname).sgml: $(sgml_ents)
-ourdir=`pwd`; \
cd $(srcdir); \
cp $(sgml_ents) $$ourdir
# The weird srcdir trick is because the db2html from the Cygnus RPMs
# cannot handle relative filenames
$(docname)/index.html: $(srcdir)/$(docname).sgml
-srcdir=`cd $(srcdir) && pwd`; \
if test "$(HAVE_JW)" = 'yes' ; then \
jw -c /etc/sgml/catalog $$srcdir/$(docname).sgml -o $$srcdir/$(docname); \
else \
db2html $$srcdir/$(docname).sgml; \
fi
app-dist-hook: index.html
-$(mkinstalldirs) $(distdir)/$(docname)/stylesheet-images
-$(mkinstalldirs) $(distdir)/figures
-cp $(srcdir)/$(docname)/*.html $(distdir)/$(docname)
-for file in $(srcdir)/$(docname)/*.css; do \
basefile=`echo $$file | sed -e 's,^.*/,,'`; \
cp $$file $(distdir)/$(docname)/$$basefile ; \
done
-for file in $(srcdir)/$(docname)/stylesheet-images/*.gif; do \
basefile=`echo $$file | sed -e 's,^.*/,,'`; \
cp $$file $(distdir)/$(docname)/stylesheet-images/$$basefile ; \
done
-if [ -e topic.dat ]; then \
cp $(srcdir)/topic.dat $(distdir); \
fi
install-data-am: index.html omf
-$(mkinstalldirs) $(DESTDIR)$(docdir)/stylesheet-images
-$(mkinstalldirs) $(DESTDIR)$(docdir)/figures
-cp $(srcdir)/$(sgml_files) $(DESTDIR)$(docdir)
-for file in $(srcdir)/$(docname)/*.html $(srcdir)/$(docname)/*.css; do \
basefile=`echo $$file | sed -e 's,^.*/,,'`; \
$(INSTALL_DATA) $$file $(DESTDIR)$(docdir)/$$basefile; \
done
-for file in $(srcdir)/figures/*.png; do \
basefile=`echo $$file | sed -e 's,^.*/,,'`; \
$(INSTALL_DATA) $$file $(DESTDIR)$(docdir)/figures/$$basefile; \
done
-for file in $(srcdir)/$(docname)/stylesheet-images/*.gif; do \
basefile=`echo $$file | sed -e 's,^.*/,,'`; \
$(INSTALL_DATA) $$file $(DESTDIR)$(docdir)/stylesheet-images/$$basefile; \
done
-if [ -e $(srcdir)/topic.dat ]; then \
$(INSTALL_DATA) $(srcdir)/topic.dat $(DESTDIR)$(docdir); \
fi
$(docname).ps: $(srcdir)/$(docname).sgml
-srcdir=`cd $(srcdir) && pwd`; \
db2ps $$srcdir/$(docname).sgml
$(docname).rtf: $(srcdir)/$(docname).sgml
-srcdir=`cd $(srcdir) && pwd`; \
db2ps $$srcdir/$(docname).sgml
uninstall-local:
-for file in $(srcdir)/$(docname)/stylesheet-images/*.gif; do \
basefile=`echo $$file | sed -e 's,^.*/,,'`; \
rm -f $(docdir)/stylesheet-images/$$basefile; \
done
-for file in $(srcdir)/figures/*.png; do \
basefile=`echo $$file | sed -e 's,^.*/,,'`; \
rm -f $(docdir)/figures/$$basefile; \
done
-for file in $(srcdir)/$(docname)/*.html $(srcdir)/$(docname)/*.css; do \
basefile=`echo $$file | sed -e 's,^.*/,,'`; \
rm -f $(DESTDIR)$(docdir)/$$basefile; \
done
-for file in $(sgml_files); do \
rm -f $(DESTDIR)$(docdir)/$$file; \
done
-rmdir $(DESTDIR)$(docdir)/stylesheet-images
-rmdir $(DESTDIR)$(docdir)/figures
-rmdir $(DESTDIR)$(docdir)
# To use this template:
# 1) Define: figs, docname, lang, omffile, entities although figs,
# omffile, and entities may be empty in your Makefile.am which
# will "include" this one
# 2) Figures must go under figures/ and be in PNG format
# 3) You should only have one document per directory
#
# Note that this makefile forces the directory name under
# $prefix/share/gnome/help/ to be the same as the XML filename
# of the document. This is required by GNOME. eg:
# $prefix/share/gnome/help/fish_applet/C/fish_applet.xml
# ^^^^^^^^^^^ ^^^^^^^^^^^
# Definitions:
# figs A list of screenshots which will be included in EXTRA_DIST
# Note that these should reside in figures/ and should be .png
# files, or you will have to make modifications below.
# docname This is the name of the XML file: <docname>.xml
# lang This is the document locale
# omffile This is the name of the OMF file. Convention is to name
# it <docname>-<locale>.omf.
# entities This is a list of XML entities which must be installed
#