callisto-debian/evolution
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

All sgml files replaced with xml files. XML files validated. Two new XML

Browse Source 
2002-11-04  Aaron Weber  <aaron@ximian.com>

	* C/*.sgml: All sgml files replaced with xml files. XML files
	validated. Two new XML files added: apx-fdl.xml and legal.xml

	* C/evolution-C.omf: Altered to fit the GDP template. This may now
	work with the GNOME 2.0 DTD, although I could be wrong.

	* sgmldocs.make: removed and replaced with xmldocs.make. This will
	break all translations until they are also ported to XML. I will
	probably begin doing that tomorrow, since it's just markup and not
	language stuff.

	* C/Makefile.am: added two files to the list. Does this
	Makefile get included in another, somewhere, or is it just
	detected?

svn path=/trunk/; revision=18538
This commit is contained in:
Aaron Weber
2002-11-04 22:41:05 +00:00
committed by Aaron Weber
parent 877e911cdf
commit fab377c503
24 changed files with 3246 additions and 2503 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
help/C/Makefile.am
View File

@ -29,26 +29,28 @@ figs = \
figures/small_desktop.png \
figures/summary.png \
figures/vfolder-createrule-fig.png
figdir = figures
docname = evolution
lang = C
omffile = evolution-C.omf
sgml_ents = \
apx-authors.sgml \
apx-bugs.sgml \
apx-gloss.sgml \
config-prefs.sgml \
config-sync.sgml \
menuref.sgml \
preface.sgml \
usage-calendar.sgml \
usage-contact.sgml \
usage-exec-summary.sgml \
usage-exchange.sgml \
usage-mail-org.sgml \
usage-mail.sgml \
usage-mainwindow.sgml \
usage-print.sgml \
usage-sync.sgml
include $(top_srcdir)/help/sgmldocs.make
entities = \
apx-authors.xml \
apx-bugs.xml \
apx-gloss.xml \
config-prefs.xml \
config-sync.xml \
menuref.xml \
preface.xml \
usage-calendar.xml \
usage-contact.xml \
usage-exec-summary.xml \
usage-exchange.xml \
usage-mail-org.xml \
usage-mail.xml \
usage-mainwindow.xml \
usage-print.xml \
usage-sync.xml \
legal.xml \
apx-fdl.xml \
include $(top_srcdir)/help/xmldocs.make
dist-hook: app-dist-hook

0
help/C/apx-authors.sgml → help/C/apx-authors.xml
View File

0
help/C/apx-bugs.sgml → help/C/apx-bugs.xml
View File

667
help/C/apx-fdl.xml Normal file
View File

@ -0,0 +1,667 @@
<!--
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="apx-fdl">
<appendixinfo>
<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>
</appendixinfo>
<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 type="http"
url="http://www.gnu.org/fsf/fsf.html">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
type="http"
url="http://www.gnu.org/copyleft">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 type="http"
url="http://www.gnu.org/copyleft/gpl.html"> GNU General Public
License</ulink>, to permit their use in free software.
</para>
</sect1>
</appendix>

2
help/C/apx-gloss.sgml → help/C/apx-gloss.xml
View File

@ -405,7 +405,7 @@
</glossdef>
</glossentry>
<glossentry id="SMTP">
<glossentry id="smtp">
<glossterm>SMTP:</glossterm>
<glossdef>
<para>

18
help/C/config-prefs.sgml → help/C/config-prefs.xml
View File

@ -29,7 +29,7 @@
<title>Changing Mail Settings</title>
<screenshot>
<screeninfo>Changing Mail Settings</screeninfo>
<mediaobject><imageobject><imagedata fileref="figures/config-mail" format="png" srccredit="Aaron Weber">
<mediaobject><imageobject><imagedata fileref="figures/config-mail" format="PNG" srccredit="Aaron Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>
@ -47,7 +47,7 @@
accounts: the servers to which you connect, the way you
download mail, your password authentication mode, and so
forth. This is the most complex item in the list, and is
covered in <xref linkend="config-prefs-mail-identity">.
covered in <xref linkend="config-prefs-mail-identity"/>.
</para>
</listitem>
</varlistentry>
@ -72,7 +72,7 @@
These are overall mail reading preferences: display
settings, notification options, security, and so
forth. These are covered in <xref
linkend="config-prefs-mail-display">.
linkend="config-prefs-mail-display"/>.
</para>
</listitem>
</varlistentry>
@ -86,7 +86,7 @@
feature here is the ability to substitute graphical
smiley-faces for "emoticons" such as :) that many people
use in email. This tool is covered in <xref
linkend="config-prefs-mail-composer">.
linkend="config-prefs-mail-composer"/>.
</para>
</listitem>
</varlistentry>
@ -351,7 +351,7 @@ smtp.omniport.com:143
specific directory where your server stores mail for
you. Typical values are "mail" and "Mail." For more
information about how to use IMAP mail, see <xref
linkend="usage-mail-subscriptions">.</para>
linkend="usage-mail-subscriptions"/>.</para>
</listitem>
<listitem>
@ -410,7 +410,7 @@ smtp.omniport.com:143
this account. Enter your PGP Key ID and decide how
frequently to encrypt and sign your messages. You can
learn more about PGP and encryption in <xref
linkend="encryption">.
linkend="encryption"/>.
</para>
</listitem>
</varlistentry>
@ -432,7 +432,7 @@ smtp.omniport.com:143
<application>Ximian Evolution</application> to handle inline
images in HTML mail that you get. There is a detailed
discussion of the issues surrounding these options in <xref
linkend="usage-mail-getnsend-get-attach-html">.
linkend="usage-mail-getnsend-get-attach-html"/>.
</para>
<para>
To hange the font which <application>Ximian
@ -586,14 +586,14 @@ smtp.omniport.com:143
The calendar configuration tool has two tabs
<guilabel>General</guilabel> and
<guilabel>Display</guilabel>, and is illustrated in <xref
linkend="config-prefs-cal-fig">.
linkend="config-prefs-cal-fig"/>.
<!-- ==============Figure===================== -->
<figure id="config-prefs-cal-fig">
<title>Calendar Preferences Dialog</title>
<screenshot>
<screeninfo>Calendar Configuration</screeninfo>
<mediaobject><imageobject><imagedata fileref="figures/config-cal" format="png" srccredit="Aaron Weber">
<mediaobject><imageobject><imagedata fileref="figures/config-cal" format="PNG" srccredit="Aaron Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>

0
help/C/config-sync.sgml → help/C/config-sync.xml
View File

18
help/C/evolution-C.omf
View File

@ -1,16 +1,24 @@
<?xml version="1.0" standalone="no"?>
<omf>
<resource>
<creator>
Ximian, Inc.
</creator>
<creator>
Ximian, Inc.
</creator>
<title>
Evolution Manual
</title>
<date>2002</date>
<subject category="GNOME|Applications"/>
<format mime="text/html"/>
<identifier url="index.html"/>
<description>
A user's guide to Ximian Evolution which explains how to use
its mail, calendar, addressbook, and task list features.
</description>
<type>
manual
</type>
<format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.1.2//EN"//>
<identifier url="/"/>
<language code="C"/>
<rights type="GNU FDL" license.version="1.1" license="http://www.gnu.org/licenses/fdl.html" holder="Ximian, Inc."/>
</resource>
</omf>

73
help/C/evolution.sgml → help/C/evolution.xml
View File

@ -1,22 +1,26 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN"[
<!ENTITY PREFACE SYSTEM "preface.sgml">
<!ENTITY USAGE-MAINWINDOW SYSTEM "usage-mainwindow.sgml">
<!ENTITY USAGE-EXEC-SUMMARY SYSTEM "usage-exec-summary.sgml">
<!ENTITY USAGE-MAIL SYSTEM "usage-mail.sgml">
<!ENTITY USAGE-MAIL-ORG SYSTEM "usage-mail-org.sgml">
<!ENTITY USAGE-CONTACT SYSTEM "usage-contact.sgml">
<!ENTITY USAGE-CALENDAR SYSTEM "usage-calendar.sgml">
<!ENTITY USAGE-EXCHANGE SYSTEM "usage-exchange.sgml">
<!ENTITY USAGE-SYNC SYSTEM "usage-sync.sgml">
<!ENTITY USAGE-PRINT SYSTEM "usage-print.sgml">
<!ENTITY CONFIG-PREFS SYSTEM "config-prefs.sgml">
<!ENTITY CONFIG-SYNC SYSTEM "config-sync.sgml">
<!ENTITY MENUREF SYSTEM "menuref.sgml">
<!ENTITY APX-GLOSS SYSTEM "apx-gloss.sgml">
<!ENTITY APX-COMMON-TASKS SYSTEM "apx-common-tasks.sgml">
<!ENTITY APX-BUGS SYSTEM "apx-bugs.sgml">
<!ENTITY APX-AUTHORS SYSTEM "apx-authors.sgml">
<?xml version='1.0'?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
<!ENTITY LEGAL SYSTEM "legal.xml">
<!ENTITY GFDL SYSTEM "apx-fdl.xml">
<!ENTITY PREFACE SYSTEM "preface.xml">
<!ENTITY USAGE-MAINWINDOW SYSTEM "usage-mainwindow.xml">
<!ENTITY USAGE-EXEC-SUMMARY SYSTEM "usage-exec-summary.xml">
<!ENTITY USAGE-MAIL SYSTEM "usage-mail.xml">
<!ENTITY USAGE-MAIL-ORG SYSTEM "usage-mail-org.xml">
<!ENTITY USAGE-CONTACT SYSTEM "usage-contact.xml">
<!ENTITY USAGE-CALENDAR SYSTEM "usage-calendar.xml">
<!ENTITY USAGE-EXCHANGE SYSTEM "usage-exchange.xml">
<!ENTITY USAGE-SYNC SYSTEM "usage-sync.xml">
<!ENTITY USAGE-PRINT SYSTEM "usage-print.xml">
<!ENTITY CONFIG-PREFS SYSTEM "config-prefs.xml">
<!ENTITY CONFIG-SYNC SYSTEM "config-sync.xml">
<!ENTITY MENUREF SYSTEM "menuref.xml">
<!ENTITY APX-GLOSS SYSTEM "apx-gloss.xml">
<!ENTITY APX-COMMON-TASKS SYSTEM "apx-common-tasks.xml">
<!ENTITY APX-BUGS SYSTEM "apx-bugs.xml">
<!ENTITY APX-AUTHORS SYSTEM "apx-authors.xml">
]>
@ -38,38 +42,15 @@ entity names correspond. APX is for appendix. -->
<holder>Ximian, Inc.</holder>
</copyright>
<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. You
may obtain a copy of the <citetitle>GNU Free Documentation
License</citetitle> from the Free Software Foundation by
visiting <ulink type="http" url="http://www.fsf.org">their
Web site</ulink> or by writing to: Free Software Foundation,
Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307,
USA.
</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>
<releaseinfo>
This is version 1.2 of the Ximian Evolution manual. It describes
version 1.2 of the Ximian Evolution groupware suite.
This is version 1.4 of the Ximian Evolution manual. It describes
version 1.4 of the Ximian Evolution groupware suite.
</releaseinfo>
</bookinfo>
&LEGAL;
&PREFACE;
<part id="usage">

75
help/C/legal.xml Normal file
View File

@ -0,0 +1,75 @@
<legalnotice id="legalnotice">
<para>
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation
License (GFDL), Version 1.1 or any later version published
by the Free Software Foundation with no Invariant Sections,
no Front-Cover Texts, and no Back-Cover Texts. You can find
a copy of the GFDL in <xref linkend="apx-fdl"/> or in the
file COPYING-DOCS distributed with this manual.
</para>
<para> This manual is part of a collection of GNOME manuals
distributed under the GFDL. If you want to distribute this
manual separately from the collection, you can do so by
adding a copy of the license to the manual, as described in
section 6 of the license.
</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 the members of
the GNOME Documentation Project are made aware of those
trademarks, then the names are in capital letters or initial
capital letters.
</para>
<para>
DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED
UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE
WITH THE FURTHER UNDERSTANDING THAT:
<orderedlist>
<listitem>
<para>DOCUMENT IS PROVIDED ON AN "AS IS" BASIS,
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR
IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES
THAT THE DOCUMENT OR MODIFIED VERSION OF THE
DOCUMENT IS FREE OF DEFECTS MERCHANTABLE, FIT FOR
A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE
RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE
OF THE DOCUMENT OR MODIFIED VERSION OF THE
DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR
MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT,
YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY
CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY
SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER
OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS
LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED
VERSION OF THE DOCUMENT IS AUTHORIZED HEREUNDER
EXCEPT UNDER THIS DISCLAIMER; AND
</para>
</listitem>
<listitem>
<para>UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL
THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE),
CONTRACT, OR OTHERWISE, SHALL THE AUTHOR,
INITIAL WRITER, ANY CONTRIBUTOR, OR ANY
DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION
OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH
PARTIES, BE LIABLE TO ANY PERSON FOR ANY
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR
CONSEQUENTIAL DAMAGES OF ANY CHARACTER
INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS
OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR
MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR
LOSSES ARISING OUT OF OR RELATING TO USE OF THE
DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT,
EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF
THE POSSIBILITY OF SUCH DAMAGES.
</para>
</listitem>
</orderedlist>
</para>
</legalnotice>

0
help/C/menuref.sgml → help/C/menuref.xml
View File

4
help/C/preface.sgml → help/C/preface.xml
View File

@ -37,7 +37,7 @@
in</userinput></member> <member><computeroutput>Text
output from a computer</computeroutput></member>
<member><glossterm linkend="apx-gloss">Words</glossterm>
that are defined in the <xref linkend="apx-gloss">.</member>
that are defined in the <xref linkend="apx-gloss"/>.</member>
</simplelist>
</para>
<para>
@ -116,7 +116,7 @@ Lastly, we'll have warnings, in cases where you should be careful:
</guimenuitem>
</menuchoice>. Detailed help for the preferences
dialogs has been added to <xref
linkend="config-prefs">.
linkend="config-prefs"/>.
</para>
</listitem>
</varlistentry>

20
help/C/usage-calendar.sgml → help/C/usage-calendar.xml
View File

@ -71,7 +71,7 @@
appointments, set alarms, and determine appointment
recurrence. If you have installed the Ximian Connector for
Microsoft Exchange, you can also read <xref
linkend="full-advantage"> to learn about how to take full
linkend="full-advantage"/> to learn about how to take full
advantage of the collaborative group scheduling functions
available on the Microsoft Exchange Server.
</para>
@ -101,8 +101,8 @@
</tip>
<para>
Your appointment must have a starting and ending date &mdash; by
default, today &mdash; but you can choose whether to give it
Your appointment must have a starting and ending date (by
default, today) but you can choose whether to give it
starting and ending times or to mark it as an <guilabel>All
day event</guilabel>. An <guilabel>All day event</guilabel>
appears at the top of a day's appointment list, in the grey header under the date, rather than inside
@ -225,7 +225,7 @@
<application>Evolution</application> can handle free/busy
scheduling Using the Ximian Connector on a Microsoft Exchange
2000 server. For more information about Ximian Connector, see
<xref linkend="usage-exchange">.
<xref linkend="usage-exchange"/>.
</para>
<para>
To set your appointment to be free or busy, simply click the
@ -518,15 +518,15 @@
<screenshot>
<screeninfo>Appointment Scheduling Window</screeninfo>
<mediaobject><imageobject>
<imagedata format="png" fileref="figures/schedule"
srccredit="Kevin Breit">
<imagedata format="PNG" fileref="figures/schedule"
srccredit="Kevin Breit"/>
</imageobject></mediaobject>
</screenshot>
</figure>
<para>
<inlinemediaobject>
<imageobject>
<imagedata fileref="figures/full-1" format="png">
<imagedata fileref="figures/full-1" format="PNG"/>
</imageobject>
</inlinemediaobject>
<guilabel>Invitee List</guilabel>
@ -539,7 +539,7 @@
<para>
<inlinemediaobject>
<imageobject>
<imagedata fileref="figures/full-2" format="png">
<imagedata fileref="figures/full-2" format="PNG"/>
</imageobject>
</inlinemediaobject>
<guilabel>Schedule Grid</guilabel>
@ -553,7 +553,7 @@
<para>
<inlinemediaobject>
<imageobject>
<imagedata fileref="figures/full-3" format="png">
<imagedata fileref="figures/full-3" format="PNG"/>
</imageobject>
</inlinemediaobject>
<guilabel>Meeting Scheduler</guilabel>
@ -590,7 +590,7 @@
</para>
<para>
Read <xref linkend="full-advantage"> to learn about how to
Read <xref linkend="full-advantage"/> to learn about how to
use this feature with the Ximian Connector for Microsoft
Exchange.
</para>

20
help/C/usage-contact.sgml → help/C/usage-contact.xml
View File

@ -10,7 +10,7 @@
any amount of contact information, share addresses over a
network, and several ways to save time with everyday tasks. To
learn about configuring the addressbook, see <xref
linkend="config-prefs-contact">. You can import contacts from
linkend="config-prefs-contact"/>. You can import contacts from
other contact management tools with the Import tool by
selecting
<menuchoice><guimenu>File</guimenu><guimenuitem>Import</guimenuitem></menuchoice>,
@ -89,8 +89,8 @@
<screenshot>
<screeninfo>Evolution Contact Editor</screeninfo>
<mediaobject><imageobject><imagedata
fileref="figures/contact-editor" format="png" srccredit="Aaron
Weber">
fileref="figures/contact-editor" format="PNG" srccredit="Aaron
Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>
@ -204,7 +204,7 @@
The last item in the <guilabel>General</guilabel> tab is the
<guilabel>Categories</guilabel> organization tool; for
information on that, read <xref
linkend="usage-contact-organize">.
linkend="usage-contact-organize"/>.
</para>
<para>
The <guilabel>Details</guilabel> tab is much simpler:
@ -317,7 +317,7 @@
does, however, allow each card to fall under several
categories, and allow you to create your own categories. To
learn about categories, read <xref
linkend="usage-contact-organize-group-category">.
linkend="usage-contact-organize-group-category"/>.
</para>
<!-- UNIMPLEMENTED FEATURE
@ -349,7 +349,7 @@
The simplest way to group address cards is to use folders.
By default, cards start in the
<guilabel>Contacts</guilabel> folder. If you've read <xref
linkend="usage-mainwindow"> then you already know that you
linkend="usage-mainwindow"/> then you already know that you
can create a new folder by selecting
<menuchoice>
<guimenu>File</guimenu>
@ -360,7 +360,7 @@
like with mail, cards must be in a card folder, and no card
can be in two places at once. If you want more
flexibility, try <xref
linkend="usage-contact-organize-group-category">.
linkend="usage-contact-organize-group-category"/>.
</para>
<para>
To put a card into a folder, just drag it there from the
@ -446,7 +446,7 @@
Unless it is a very small list, it is recommended
that you leave the addresses hidden. This is the
same thing as using the "Bcc:" feature discussed in
<xref linkend="usage-mail-getnsend-send-to-types">.
<xref linkend="usage-mail-getnsend-send-to-types"/>.
</para>
</listitem>
@ -488,7 +488,7 @@
<para>
To learn how to add a remote directory to your available
contact folders, see <xref linkend="config-prefs-contact">.
contact folders, see <xref linkend="config-prefs-contact"/>.
Once you have a LDAP connection, the network contacts folder or
folders will appear inside the <guilabel>External
Directories</guilabel> folder in the folder bar. It will work
@ -546,7 +546,7 @@
Card</guimenuitem> from the menu that appears.
<application> Evolution</application> can also add cards from a
hand-held device during HotSync operation. For more
information about that, see <xref linkend="usage-sync">.
information about that, see <xref linkend="usage-sync"/>.
</para>
</sect1>

10
help/C/usage-exchange.sgml → help/C/usage-exchange.xml
View File

@ -335,7 +335,7 @@ There are, however, some features which are not available:
server, click the <guibutton>Add</guibutton> button in the
accounts list. The account creation assistant will guide you
through the process, which is also described in <xref
linkend="usage-mainwindow-starting">. If you're not sure
linkend="usage-mainwindow-starting"/>. If you're not sure
about any of the information you need, just ask your system
administrator.
</para>
@ -474,7 +474,7 @@ There are, however, some features which are not available:
<screenshot>
<screeninfo>Creating an Exchange Account, Step One: Identity</screeninfo>
<mediaobject><imageobject>
<imagedata format="png" fileref="figures/exchange-identity" srccredit="Aaron Weber">
<imagedata format="PNG" fileref="figures/exchange-identity" srccredit="Aaron Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>
@ -484,7 +484,7 @@ There are, however, some features which are not available:
<screenshot>
<screeninfo>Creating an Exchange Account, Step Two: Receiving Mail</screeninfo>
<mediaobject><imageobject>
<imagedata format="png" fileref="figures/exchange-receive" srccredit="Aaron Weber">
<imagedata format="PNG" fileref="figures/exchange-receive" srccredit="Aaron Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>
@ -494,7 +494,7 @@ There are, however, some features which are not available:
<screenshot>
<screeninfo>Creating an Exchange Account, Step Three: Mail Options</screeninfo>
<mediaobject><imageobject>
<imagedata format="png" fileref="figures/exchange-receive-options" srccredit="Aaron Weber">
<imagedata format="PNG" fileref="figures/exchange-receive-options" srccredit="Aaron Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>
@ -684,7 +684,7 @@ There are, however, some features which are not available:
<screenshot>
<screeninfo>Using the Free/Busy Feature</screeninfo>
<mediaobject><imageobject>
<imagedata format="png" fileref="figures/schedule" srccredit="Aaron Weber">
<imagedata format="PNG" fileref="figures/schedule" srccredit="Aaron Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>

0
help/C/usage-exec-summary.sgml → help/C/usage-exec-summary.xml
View File

12
help/C/usage-mail-org.sgml → help/C/usage-mail-org.xml
View File

@ -548,13 +548,13 @@
<listitem><para> Date sent - Filter messages according to the date on
which they were sent: First, choose the conditions you
want a message to meet &mdash; <guilabel>before</guilabel>
want a message to meet -- <guilabel>before</guilabel>
a given time, <guilabel>after</guilabel> it, and so forth.
Then, choose the time. The filter will compare the
message's time-stamp to the system clock when the filter
is run, or to a specific time and date you choose from a
calendar. You can even have it look for messages within a
range of time relative to the filter &mdash; perhaps you're
range of time relative to the filter -- perhaps you're
looking for messages less than two days old.
</para></listitem>
@ -926,7 +926,7 @@
</note>
<example id="usage-mail-organize-vFolders-ex">
<example id="usage-mail-organize-vfolders-ex">
<title>Using Folders, Searches, and vFolders</title>
<para>
To organize his mailbox, Jim sets up a virtual volder for emails from
@ -1008,13 +1008,13 @@
<listitem><para> Date sent - Search messages according to the date on
which they were sent: First, choose the conditions you
want a message to meet &mdash; <guilabel>before</guilabel>
want a message to meet -- <guilabel>before</guilabel>
a given time, <guilabel>after</guilabel> it, and so forth.
Then, choose the time. The vFolder will compare the
message's time-stamp to the system clock when the filter
is run, or to a specific time and date you choose from a
calendar. You can even have it look for messages within a
range of time relative to the filter &mdash; perhaps you're
range of time relative to the filter -- perhaps you're
looking for messages less than two days old.
</para></listitem>
@ -1118,7 +1118,7 @@
<mediaobject>
<imageobject>
<imagedata fileref="figures/vfolder-createrule-fig" format="PNG"
srccredit="Aaron Weber">
srccredit="Aaron Weber"/>
</imageobject>
</mediaobject>
</screenshot>

4418
help/C/usage-mail.sgml → help/C/usage-mail.xml
View File

File diff suppressed because it is too large Load Diff

70
help/C/usage-mainwindow.sgml → help/C/usage-mainwindow.xml
View File

@ -49,7 +49,7 @@
makes displays faster and more efficient, so searches are faster
and memory usage is lower. People who get lots of mail will
appreciate advanced features like <link
linkend="usage-mail-organize-vFolders"><trademark>VFolders</trademark></link>,
linkend="usage-mail-organize-vfolders"><trademark>VFolders</trademark></link>,
which let you save searches as though they were ordinary mail
folders.
</para>
@ -319,7 +319,7 @@
</guimenuitem></menuchoice>, click the <guibutton>Mail
Accounts</guibutton> button. Then, select the account you want
to change and click <guibutton>Edit</guibutton>. See <xref
linkend="config-prefs-mail"> for details.
linkend="config-prefs-mail"/> for details.
</para>
<variablelist>
<varlistentry>
@ -424,7 +424,7 @@
specific directory where your server stores mail for
you. Typical values are "mail" and "Mail." For more
information about how to use IMAP mail, see <xref
linkend="usage-mail-subscriptions">.</para>
linkend="usage-mail-subscriptions"/>.</para>
</listitem>
<listitem>
@ -451,7 +451,7 @@
If you prefer, you can choose to subscribe to
individual mail folders one at a time. For more
information about how to use IMAP mail, see <xref
linkend="usage-mail-subscriptions">.
linkend="usage-mail-subscriptions"/>.
</para>
</note>
@ -796,14 +796,18 @@ the workaround described in the note below.
<title>The Ximian Evolution Main Window</title>
<screenshot>
<screeninfo>Inbox</screeninfo>
<mediaobject><imageobject><imagedata
fileref="figures/mainwindow-pic" format="png" srccredit="Kevin
Breit"> </imageobject></mediaobject>
<mediaobject>
<imageobject>
<imagedata fileref="figures/mainwindow-pic" format="PNG" srccredit="Kevin Breit"/>
</imageobject>
</mediaobject>
</screenshot>
</figure>
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-1" format="png"></imageobject></inlinemediaobject>
<inlinemediaobject>
<imageobject>
<imagedata fileref="figures/full-1" format="PNG"/></imageobject></inlinemediaobject>
<guilabel>Menubar</guilabel>
</para>
@ -813,7 +817,7 @@ the workaround described in the note below.
</para>
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-2" format="png"></imageobject></inlinemediaobject>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-2" format="PNG"/></imageobject></inlinemediaobject>
<guilabel>Toolbar</guilabel>
</para>
@ -823,7 +827,7 @@ the workaround described in the note below.
</para>
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-3" format="png"></imageobject></inlinemediaobject>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-3" format="PNG"/></imageobject></inlinemediaobject>
<guilabel>Shortcut Bar</guilabel>
</para>
@ -833,7 +837,7 @@ the workaround described in the note below.
</para>
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-4" format="png"></imageobject></inlinemediaobject>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-4" format="PNG"/></imageobject></inlinemediaobject>
<guilabel>Status Bar</guilabel>
</para>
@ -845,7 +849,7 @@ the workaround described in the note below.
</para>
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-5" format="png"></imageobject></inlinemediaobject>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-5" format="PNG"/></imageobject></inlinemediaobject>
<guilabel>Search Tool</guilabel>
</para>
@ -953,7 +957,7 @@ the workaround described in the note below.
directories, and <glossterm linkend="imap">IMAP</glossterm> mail
folders to which you subscribe. Lastly, there are
<guilabel>vFolders</guilabel>, or virtual folders, discussed in
<xref linkend="usage-mail-organize-vfolders">,
<xref linkend="usage-mail-organize-vfolders"/>,
</para>
<para>
@ -1220,37 +1224,37 @@ the workaround described in the note below.
<title>The Evolution Summary</title>
<screenshot>
<graphic format="png" fileref="figures/summary" srccredit="Kevin Breit">
<graphic format="PNG" fileref="figures/summary" srccredit="Kevin Breit"/>
</screenshot>
</figure>
</para>
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-1" format="png"></imageobject></inlinemediaobject> <guilabel>Weather Summary</guilabel>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-1" format="PNG"/></imageobject></inlinemediaobject> <guilabel>Weather Summary</guilabel>
</para>
<para>
Shows you the latest weather updates from hundreds of cities around the world.
</para>
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-2" format="png"></imageobject></inlinemediaobject> <guilabel>News Feeds</guilabel>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-2" format="PNG"/></imageobject></inlinemediaobject> <guilabel>News Feeds</guilabel>
</para>
<para>
Displays up to the minute news from your favorite websites.
</para>
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-3" format="png"></imageobject></inlinemediaobject> <guilabel>Mail Summary</guilabel>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-3" format="PNG"/></imageobject></inlinemediaobject> <guilabel>Mail Summary</guilabel>
</para>
<para>
Shows you how many email messages you have in your selected folders, waiting to be read.
</para>
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-4" format="png"></imageobject></inlinemediaobject> <guilabel>Calendar Summary</guilabel>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-4" format="PNG"/></imageobject></inlinemediaobject> <guilabel>Calendar Summary</guilabel>
</para>
<para>
Shows you your calendar.
</para>
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-5" format="png"></imageobject></inlinemediaobject> <guilabel>Tasks</guilabel>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-5" format="PNG"/></imageobject></inlinemediaobject> <guilabel>Tasks</guilabel>
</para>
<para>
Shows your pending tasks
@ -1311,7 +1315,7 @@ Shows your pending tasks
<link linkend="usage-mail-organize-search">searching</link>
functions were built for speed and efficiency on large volumes
of mail. There's also the <application>Ximian Evolution</application>
<link linkend="usage-mail-organize-vFolders">vFolder</link>,
<link linkend="usage-mail-organize-vfolders">vFolder</link>,
an advanced organizational feature not found in mainstream
mail clients. If you get a lot of mail, or if you keep every
message you get in case you need to refer to it later, you'll
@ -1326,7 +1330,7 @@ Shows your pending tasks
<title>Ximian Evolution Mail</title>
<screenshot>
<screeninfo>Inbox</screeninfo>
<mediaobject><imageobject><imagedata fileref="figures/mail-inbox" format="png" srccredit="Kevin Breit">
<mediaobject><imageobject><imagedata fileref="figures/mail-inbox" format="PNG" srccredit="Kevin Breit"/>
</imageobject></mediaobject>
</screenshot>
</figure>
@ -1334,7 +1338,7 @@ Shows your pending tasks
</para>
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-1"
format="png"></imageobject></inlinemediaobject> <guilabel>Email
format="PNG"/></imageobject></inlinemediaobject> <guilabel>Email
Viewer</guilabel>
</para>
@ -1344,7 +1348,7 @@ Shows your pending tasks
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-2"
format="png"></imageobject></inlinemediaobject> <guilabel>Message List</guilabel>
format="PNG"/></imageobject></inlinemediaobject> <guilabel>Message List</guilabel>
</para>
<para>
@ -1383,7 +1387,7 @@ Shows your pending tasks
<para>
For an in-depth guide to the email capabilities of Ximian
Evolution, read <xref linkend="usage-mail">.
Evolution, read <xref linkend="usage-mail"/>.
</para>
</sect2>
<sect2 id="basics-calendar">
@ -1403,7 +1407,7 @@ Shows your pending tasks
<title>Ximian Evolution Calendar View</title>
<screenshot>
<screeninfo>Ximian Evolution Contact Manager Window</screeninfo>
<mediaobject><imageobject><imagedata fileref="figures/calendar" format="png" srccredit="Aaron Weber">
<mediaobject><imageobject><imagedata fileref="figures/calendar" format="PNG" srccredit="Aaron Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>
@ -1413,7 +1417,7 @@ Shows your pending tasks
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-1"
format="png"></imageobject></inlinemediaobject> <guilabel>Appointment
format="PNG"/></imageobject></inlinemediaobject> <guilabel>Appointment
List</guilabel>
</para>
@ -1424,7 +1428,7 @@ Shows your pending tasks
</para>
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-2" format="png"></imageobject></inlinemediaobject>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-2" format="PNG"/></imageobject></inlinemediaobject>
<guilabel>Task List</guilabel>
</para>
@ -1437,7 +1441,7 @@ Shows your pending tasks
</para>
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-3" format="png"></imageobject></inlinemediaobject>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-3" format="PNG"/></imageobject></inlinemediaobject>
<guilabel>Calendar Window</guilabel>
</para>
@ -1449,7 +1453,7 @@ Shows your pending tasks
<para>
For more information about the calendar
read <xref linkend="usage-calendar">.
read <xref linkend="usage-calendar"/>.
</para>
</sect2>
@ -1475,7 +1479,7 @@ Shows your pending tasks
To open your address book, click on
<guibutton>Contacts</guibutton> in the shortcut bar, or select
one of your contacts folders from the folder bar. <xref
linkend="usage-contact-fig"> shows the address book in all its
linkend="usage-contact-fig"/> shows the address book in all its
organizational glory. By default, the address book shows all
your cards in alphabetical order, in a <glossterm
linkend="minicard">minicard</glossterm> view. You can select
@ -1490,14 +1494,14 @@ Shows your pending tasks
<title>Ximian Evolution Contact Interface</title>
<screenshot>
<screeninfo>Ximian Evolution Contact List Window</screeninfo>
<mediaobject><imageobject><imagedata fileref="figures/contact" format="png" srccredit="Kevin Breit">
<mediaobject><imageobject><imagedata fileref="figures/contact" format="PNG" srccredit="Kevin Breit"/>
</imageobject></mediaobject>
</screenshot>
</figure>
</para>
<para>
<inlinemediaobject><imageobject><imagedata fileref="figures/full-1"
format="png"></imageobject></inlinemediaobject> <guilabel>Contact
format="PNG"/></imageobject></inlinemediaobject> <guilabel>Contact
List</guilabel>
</para>
<para>
@ -1505,7 +1509,7 @@ Shows your pending tasks
</para>
<para>
For detailed instructions on how to use the address book,
read <xref linkend="usage-contact">.
read <xref linkend="usage-contact"/>.
</para>
</sect2>
</sect1>

8
help/C/usage-print.sgml → help/C/usage-print.xml
View File

@ -45,7 +45,7 @@
<title>Print Preview</title>
<screenshot>
<screeninfo>Print Preview</screeninfo>
<mediaobject><imageobject><imagedata fileref="figures/print-preview" format="png" srccredit="Aaron Weber">
<mediaobject><imageobject><imagedata fileref="figures/print-preview" format="PNG" srccredit="Aaron Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>
@ -57,8 +57,8 @@
<title>File or Printer?</title>
<para>
The printer selection window, shown in <xref
linkend="print-dest">, lets you choose the format for
printing&mdash; <guilabel>Generic Postscript</guilabel>,
linkend="print-dest"/>, lets you choose the format for
printing-- <guilabel>Generic Postscript</guilabel>,
whether to write to a PDF file, and whether to print to a file
or to an actual printer in Generic Postscript. If you choose a
printer, you'll be asked for the printer command (probably
@ -85,7 +85,7 @@
<title>Choosing a Printer</title>
<screenshot>
<screeninfo>Choosing a Printer</screeninfo>
<mediaobject><imageobject><imagedata fileref="figures/print-dest" format="png" srccredit="Aaron Weber">
<mediaobject><imageobject><imagedata fileref="figures/print-dest" format="PNG" srccredit="Aaron Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>

39
help/C/usage-sync.xml Normal file
View File

@ -0,0 +1,39 @@
<chapter id="usage-sync">
<title>Synchronizing Evolution with Hand-Held Devices</title>
<para>
This chapter is very short. It describes how to synchronize
the data on your Palm-OS device with the data you store in
<application>Ximian Evolution</application>. If you need
information on how to set up handheld synchronization, consult
<xref linkend="config-sync"/>.
</para>
<sect1 id="hotsync">
<title>Using HotSync</title>
<para>
Put your hand-held device in its cradle and press the
HotSync button.
</para>
<tip id="sync-tip">
<title>Palm OS v. 4.0 with Passwords</title>
<para>
If you use Palm OS v. 4.0 and have password protection turned on for
your handheld device, you may encounter trouble synchronizing. If
this happens, try turning off password protection on your handheld,
synchronize it with your desktop computer, and then re-enable password
protection on your handheld.
</para>
</tip>
<para>
If you have followed the set up instructions properly, your
Palm-OS device will synchronize data with <application>Ximian
Evolution</application>.
</para>
<para>
That's it.
</para>
</sect1>
</chapter>

15
help/ChangeLog
View File

@ -1,3 +1,18 @@
2002-11-04 Aaron Weber <aaron@ximian.com>
* C/*.sgml: All sgml files replaced with xml files. XML files
validated. Two new XML files-- apx-fdl.xml and legal.xml
* C/evolution-C.omf: Altered to fit the GDP template. This may now
work with the GNOME 2.0 DTD, although I could be wrong.
* sgmldocs.make: removed and replaced with xmldocs.make. This will
break all translations until they are also ported to XML. I will
probably begin doing that tomorrow, since it's just markup and not
language stuff.
* C/Makefile.am: added two files
2002-10-22 Aaron Weber <aaron@ximian.com>
* C/usage-mail.sgml: Edit-->Undelete, not Actions-->Undelete

144
help/sgmldocs.make
View File

@ -1,144 +0,0 @@
# 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 $(srcdir)/$(omffile); do \
basefile=`echo $$file | sed -e 's,^.*/,,'`; \
scrollkeeper-preinstall $(docdir)/index.html $$file $(omf_dir)/$$basefile; \
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 [ -f topic.dat ]; then \
cp $(srcdir)/topic.dat $(distdir); \
fi
install-data-am: index.html omf
-$(mkinstalldirs) $(DESTDIR)$(docdir)/stylesheet-images
-$(mkinstalldirs) $(DESTDIR)$(docdir)/figures
-$(mkinstalldirs) $(DESTDIR)$(docdir)/sgml
-for file in $(sgml_files); do \
$(INSTALL_DATA) $(srcdir)/$$file $(DESTDIR)$(docdir)/sgml ; \
done
-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 [ -f $(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)

96
help/xmldocs.make Normal file
View File

@ -0,0 +1,96 @@
#
# No modifications of this Makefile should be necessary.
#
# To use this template:
# 1) Define: figdir, docname, lang, omffile, and entities in
# your Makefile.am file for each document directory,
# although figdir, omffile, and entities may be empty
# 2) Make sure the Makefile in (1) also includes
# "include $(top_srcdir)/xmldocs.make" and
# "dist-hook: app-dist-hook".
# 3) Optionally define 'entities' to hold xml entities which
# you would also like installed
# 4) Figures must go under $(figdir)/ and be in PNG format
# 5) You should only have one document per directory
# 6) Note that the figure directory, $(figdir)/, should not have its
# own Makefile since this Makefile installs those figures.
#
# example Makefile.am:
# figdir = figures
# docname = scrollkeeper-manual
# lang = C
# omffile=scrollkeeper-manual-C.omf
# entities = fdl.xml
# include $(top_srcdir)/xmldocs.make
# dist-hook: app-dist-hook
#
# About this file:
# This file was taken from scrollkeeper_example2, a package illustrating
# how to install documentation and OMF files for use with ScrollKeeper
# 0.3.x and 0.4.x. For more information, see:
# http://scrollkeeper.sourceforge.net/
# Version: 0.1.2 (last updated: March 20, 2002)
#
# ************* Begin of section some packagers may need to modify **************
# This variable (docdir) specifies where the documents should be installed.
# This default value should work for most packages.
# docdir = $(datadir)/@PACKAGE@/doc/$(docname)/$(lang)
docdir = $(datadir)/gnome/help/$(docname)/$(lang)
# ************** You should not have to edit below this line *******************
xml_files = $(entities) $(docname).xml
EXTRA_DIST = $(xml_files) $(omffile)
CLEANFILES = omf_timestamp
# If the following file is in a subdir (like help/) you need to add that to the path
include $(top_srcdir)/omf.make
all: omf
$(docname).xml: $(entities)
-ourdir=`pwd`; \
cd $(srcdir); \
cp $(entities) $$ourdir
app-dist-hook:
if test "$(figdir)"; then \
$(mkinstalldirs) $(distdir)/$(figdir); \
for file in $(srcdir)/$(figdir)/*.png; do \
basefile=`echo $$file | sed -e 's,^.*/,,'`; \
$(INSTALL_DATA) $$file $(distdir)/$(figdir)/$$basefile; \
done \
fi
install-data-local: omf
$(mkinstalldirs) $(DESTDIR)$(docdir)
for file in $(xml_files); do \
cp $(srcdir)/$$file $(DESTDIR)$(docdir); \
done
if test "$(figdir)"; then \
$(mkinstalldirs) $(DESTDIR)$(docdir)/$(figdir); \
for file in $(srcdir)/$(figdir)/*.png; do \
basefile=`echo $$file | sed -e 's,^.*/,,'`; \
$(INSTALL_DATA) $$file $(DESTDIR)$(docdir)/$(figdir)/$$basefile; \
done \
fi
install-data-hook: install-data-hook-omf
uninstall-local: uninstall-local-doc uninstall-local-omf
uninstall-local-doc:
-if test "$(figdir)"; then \
for file in $(srcdir)/$(figdir)/*.png; do \
basefile=`echo $$file | sed -e 's,^.*/,,'`; \
rm -f $(docdir)/$(figdir)/$$basefile; \
done; \
rmdir $(DESTDIR)$(docdir)/$(figdir); \
fi
-for file in $(xml_files); do \
rm -f $(DESTDIR)$(docdir)/$$file; \
done
-rmdir $(DESTDIR)$(docdir)