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

Don't requires entities here

Browse Source 
2004-09-13  Rodney Dawes  <dobey@novell.com>

	* xmldocs.make: Don't requires entities here

	* C/Makefile.am: Add new figures to the list of images
	Generate versioned xml/omf files based on $(BASE_VERSION)
	Fix up CLEANFILES to include the stuff we generate

	* C/POTFILES.in:
	* C/apx-*.xml:
	* C/config-*.xml:
	* C/evolution-1.5-C.omf:
	* C/evolution-1.5.xml:
	* C/legal.xml:
	* C/menuref.xml:
	* C/preface.xml:
	* C/topic.dat:
	* C/usage-*.xml:
	Remove all of these files from CVS

	* C/evolution-C.omf:
	* C/evolution.xml:
	Add these files to replace the removed files above

	* C/figure/*_a.(png|gif): Add new screenshots

svn path=/trunk/; revision=27253
This commit is contained in:
Rodney Dawes
2004-09-13 16:21:48 +00:00
committed by Rodney Dawes
parent a9619acb9d
commit d926df1ed5
41 changed files with 3971 additions and 10689 deletions
Download Patch File Download Diff File Expand all files Collapse all files

55
help/C/Makefile.am
View File

@ -1,4 +1,19 @@
figs = \
figures/contacts_mainwindow_a.png \
figures/evo_account_info_a.png \
figures/evo_cal_callout_a.gif \
figures/evo_contacteditor_a.png \
figures/evo_email_a.png \
figures/evo_identity_a.png \
figures/evo_mail_callout_a.gif \
figures/evo_mail_callout_a.png \
figures/evo_newmess_a.png \
figures/evo_receive_setup2_a.png \
figures/evo_receive_setup_a.png \
figures/evo_rule_a.png \
figures/evo_send_setup_a.png \
figures/evo_timezone_a.png \
figures/mail_mainwindow_a.png \
figures/calendar.png \
figures/config-cal.png \
figures/config-mail.png \
@ -26,27 +41,27 @@ figs = \
figures/summary.png \
figures/vfolder-createrule-fig.png
figdir = figures
docname = evolution-1.5
all: $(docname).xml $(omffile)
doc_in_files = evolution.xml
%-$(BASE_VERSION).xml: $(doc_in_files)
cp -f $< $@
docname = evolution-$(BASE_VERSION)
lang = C
omffile = evolution-1.5-C.omf
entities = \
apx-authors.xml \
apx-bugs.xml \
apx-fdl.xml \
apx-gloss.xml \
apx-gpl.xml \
config-prefs.xml \
config-sync.xml \
legal.xml \
menuref.xml \
preface.xml \
usage-calendar.xml \
usage-contact.xml \
usage-exchange.xml \
usage-mail-org.xml \
usage-mail.xml \
usage-mainwindow.xml \
usage-sync.xml
omf_in_files = evolution-$(lang).omf
%-$(BASE_VERSION)-$(lang).omf: $(omf_in_files)
cp -f $< $@
omffile = evolution-$(BASE_VERSION)-C.omf
include $(top_srcdir)/help/xmldocs.make
dist-hook: app-dist-hook
CLEANFILES += \
$(docname).xml \
omf_timestamp \
$(omffile).out \
$(omffile)

16
help/C/POTFILES.in
View File

@ -1,16 +0,0 @@
apx-authors.sgml
apx-bugs.sgml
apx-gloss.sgml
config-prefs.sgml
config-setupassist.sgml
config-sync.sgml
evolution.sgml
menuref.sgml
preface.sgml
usage-calendar.sgml
usage-contact.sgml
usage-mail.sgml
usage-mainwindow.sgml
usage-notes.sgml
usage-print.sgml
usage-sync.sgml

76
help/C/apx-authors.xml
View File

@ -1,76 +0,0 @@
<appendix id="authors">
<title>Authors</title>
<para>
<application>Evolution</application> was written by the Ximian
Evolution team and numerous other dedicated GNOME programmers.
You can see their names by selecting <menuchoice>
<guimenu>Help</guimenu> <guimenuitem>About</guimenuitem>
</menuchoice> from any Evolution window.
</para>
<para>
The <application>Evolution</application> code owes a great debt
to the <application>GNOME-pim</application> and
<application>GNOME-Calendar</application> applications, and to
<application>KHTMLW</application>. The developers of
<application>Evolution</application> acknowledge the efforts
and contributions of all who worked on those projects.
</para>
<para>
Ximian would like to thank everyone who helped out with the bug
tracking process, particularly Miles Lane, and also the staff of
El Pelon Taqueria, on Peterborough St. in Boston, for
sustenance.
</para>
<para>
For more information please visit the
<application>Evolution</application> <ulink
url="http://www.ximian.com/products/ximian_evolution/"
type="http">Web page</ulink>. Please send all comments,
suggestions, and bug reports to the <ulink
url="http://bugzilla.ximian.com" type="http">Ximian bug tracking
database</ulink>. Instructions for submitting bug reports can be
found on-line at the same location. You can also use the GNOME
bug report tool, <command>bug-buddy</command>, to submit your
defect reports.
</para>
<para>
This manual was written by Aaron Weber
(<email>aaron@ximian.com</email>), Kevin Breit
(<email>mrproper@ximian.com</email>) Duncan Mak
(<email>duncan@ximian.com</email>) and Ettore Perazzoli
(<email>ettore@ximian.com</email>) with the help of the
application programmers and the GNOME Documentation
Project. Special thanks to Baris Cicek for proofreading.
</para>
<para>
Please file comments and suggestions for this manual as bugs in
the Ximian bug tracking system. If you contributed to this
project but do not see your name here, please contact Aaron
Weber (<email>aaron@ximian.com</email>) and he'll list you.
</para>
<para>
Partial list of Documentation Translators (application
translated to 36 additional languages):
<itemizedlist>
<listitem><para>
Daniel Persson for Swedish (.se)
</para></listitem>
<listitem><para>
Hector Garcia Alvarez for Spanish (.es)
</para></listitem>
<listitem><para>
Kjartan Maraas for Norwegian (.no)
</para></listitem>
</itemizedlist>
</para>
</appendix>

30
help/C/apx-bugs.xml
View File

@ -1,30 +0,0 @@
<appendix id="bugs">
<title>Known bugs and limitations</title>
<abstract>
<para>
Ximian Evolution bug tracking is done at the <ulink
url="http://bugzilla.ximian.com">Ximian bug tracking
System</ulink>. You may use that, or the GNOME <application>Bug
Report Tool</application> (known as <command>bug-buddy</command>
at the command line) if you find bugs or would like to request new
features.
</para>
<para>
If you need additional help with Ximian Evolution, please visit
the Ximian support site at <ulink
url="http://support.ximian.com">ximian.com/support</ulink>.
</para>
</abstract>
<para>
A complete list of feature requests and other issues with
Evolution is available online in the Ximian bug tracking system.
You can learn more about the Ximian Evolution development process
at <ulink
url="http://developer.ximian.com">developer.ximian.com</ulink>.
</para>
</appendix>

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

@ -1,667 +0,0 @@
<!--
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>

692
help/C/apx-gloss.xml
View File

@ -1,692 +0,0 @@
<appendix id="outlook-migration">
<title>Outlook to Evolution Migration</title>
<para>If you are using Microsoft Outlook, but not Microsoft Exchange,
this section will help you switch to Evolution.</para>
<sect1 id="outlook-migration-mail">
<title>Migrating Local Outlook Mail Folders</title>
<para>Exchange and IMAP mail is stored on the server, so you do not
need to migrate it to your Linux partition. However, if you have
stored mail on your computer, you may wish to make it accessible to
Evolution.</para>
<para>First, while using Windows, prepare your messages for
import:</para>
<orderedlist>
<listitem><para>Clean up your mail: Delete messages and folders you
do not need, and select <menuchoice>
<guimenu>File</guimenu>
<guisubmenu>Folders</guisubmenu>
<guisubmenu>Properties</guisubmenu>
<guisubmenu>Advanced</guisubmenu>
<guimenuitem>Compact</guimenuitem>
</menuchoice> to erase old, deleted messages from your PST
file.</para></listitem>
<listitem>
<para>If you nest your folders one inside another, you may wish to
rename subfolders so that you can tell which folder they
belong to. You will have to re-nest them after you load them
into Evolution.</para>
</listitem>
<listitem><para>Import the files into Mozilla Mail (or
another mailer, such as Netscape or Eudora, that uses the
standard mbox format). Linux mailers cannot do this task,
because it requires a library available only under
Windows. In Mozilla, import by selecting
<menuchoice><guimenu>Window</guimenu> <guisubmenu>Mail &amp;
Newsgroups</guisubmenu> <guisubmenu>Tools</guisubmenu>
<guimenuitem>Import</guimenuitem> </menuchoice>.</para></listitem>
<listitem>
<para>Mozilla will create a set of files in the directory
<filename>Windows\Application_Data\Mozilla\Profiles\(User
Name)\(Random Letters)\Mail\Local Folders\Outlook
Mail\</filename>. The data files are those that have no
file extension.</para>
<para>If you are using Windows XP or Windows 2000, your
Windows hard drive is probably in the NTFS format,
which some Linux systems will not read without additional
software. You may find it simpler to copy the mail folders to a
different drive or to burn a CD.</para>
</listitem>
</orderedlist>
<para>Now that you have your mail in a format Evolution can
understand, reboot to Linux. Then:</para>
<orderedlist>
<listitem><para>Mount your Windows drive or the
disk where you saved the mail files.</para></listitem>
<listitem><para>Copy all the mail files into your home directory or
another convenient place.</para></listitem>
<listitem><para>Start Evolution.</para></listitem>
<listitem><para>
Press
<keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap>
<keycap>F</keycap></keycombo> or select <menuchoice>
<guimenu>File</guimenu><guisubmenu>New</guisubmenu>
<guimenuitem>Folder</guimenuitem></menuchoice> to create
the folders you want. This is where your previous
organization pays off.
</para></listitem>
</orderedlist>
<para>Now you are ready to import the data files:</para>
<orderedlist>
<listitem>
<para>In Evolution, open the file import assistant by selecting
<menuchoice>
<guimenu>File</guimenu><guimenuitem>Import</guimenuitem></menuchoice>.</para>
</listitem>
<listitem><para>
Click <guilabel>Next</guilabel>, and select
<guilabel>Import a single file</guilabel>.
</para></listitem>
<listitem><para>
Leave the file
type as <guilabel>automatic</guilabel> and click
<guilabel>Browse</guilabel> to select the data
file. Remember, the data files are the files that have no
file extension.
</para></listitem>
<listitem>
<para>Select the folder where you want to put the imported data
file.</para>
</listitem>
<listitem>
<para>Repeat the import steps until you have imported all your
mail.</para>
</listitem>
</orderedlist>
</sect1>
<!--
<sect1 id="outlook-import-contacts">
<title>Importing Contacts from Outlook</title>
<para>
To import contacts, you will again have to use Mozilla as an
intermediary. This time, you will use Outlook to save your data
to a comma separated value (CSV) file, then import it to
Mozilla. From Mozilla, you will save it as an an LDIF file,
which Evolution will import.
</para>
<orderedlist>
<listitem>
<para>
In Windows, export each Outlook address book as .csv. It is
best to select the <guilabel>Export All Fields</guilabel> option,
rather than choose a subset of fields. Be aware that if you
have multiple address books, Outlook will suggest the same
name for each exported file, so be sure to choose a new name
each time you export a new address book.
</para>
</listitem>
<listitem>
<para>
</para>
</listitem>
<listitem>
<para>
</para>
</listitem>
<listitem>
<para>
</para>
</listitem>
<listitem>
<para>
</para>
</listitem>
</orderedlist>
</sect1>
Basically, the .cvs files will contain a top line with column titles
(one per record field), and as many lines as there are contact entries
(records). (Sorry, no idea about "groups" of contacts as subsets of an
address book. Can you help?)
A bit of massaging is useful, because while the Outlook set of columns is very comprehensive, other programs like Mozilla and Evolution have fewer and not entirely consistent, field names.
For example,
* Outlook offers 3 fields for email, Evolution just two, so I move the 3rd Outlook email address to the Notes field.
* Outlook offers First, Middle, Last name fields, the others just First, Last, so I add the Middle Name to the First Name field.
* Outlook offers three lines for the street address, instead of two (although the 3rd is rarely used, since most data end up in the City, State, ZIP/Postcode, Country fields).
2) Switch to Linux. Start OpenOffice.org Calc. Open all the .csv files. A dialog will let you choose the right separators.
3) Copy all records (lines) from all books (if you have multiple books) into the same file, using header lines to separate them. Thus you will massage all books in one shot. Save it.
4.1) For names, add a few columns (by header, to write in the 1st line) FIRSTNAMECALC, FIRSTNAMENEW, SPACE.
4.2) In the 1st record under SPACE insert a space; under FIRSTNAMECALC insert the formula:
=CONCATENATE([cell under FIRSTNAME];[cell under SPACE];[cell under MIDDLE NAME])
4.3) Copy these two cells all the way down to the last record. Check if first and middle names have been merged OK.
4.4) Copy the whole FIRSTNAMECALC column.
4.5) Paste-Special it over the FIRSTNAMENEW column, as "strings" - i.e. just the result, without formula.
4.6) Rename this column to FIRSTANDMIDDLE, delete the FIRSTNAMECALC, FIRTSTNAME, MIDDLENAME, SPACE columns.
If you care about those things (Continental Europe?), you may likewise concatenate more fields, as to have the FIRSTNAME column contain the whole sequence: Title First-Name Middle-Name (perhaps a space and comma) Suffix.
5.1 - 5.6) For the 3rd email: first check if some exist. If they do, repear the procedure like for the names, until the 3rd email addresses are attached to the end of the Notes field.
Likewise, depending on the data you actually have, you may want to plan to enter it into fields that may not be ideal, but at least similar.
6) Seek & delete all empty columns, so at later steps you won't risk importing lots of nothing, and leave out lots of something.
7) Save the file as many times as there are address books you want to have. Specify .csv, but select TAB as field separator and select double quote (") for text marker.
8) Open each file, delete the excess records (lines) but KEEP THE TOP LINE where the column names are, save it as before, and finally once the file is saved, CHANGE THE FILENAME ENDING TO .tab - Mozilla likes them that way. For some reason, it won't recognize a tab-separated file that is not named in .tab, as if Calc did not mark it the file-type properly. This is not exactly Unix-like, but that's how it works. It may be a quirk of my setup, as one can instruct a filemanager to recognize filetypes from the 3-letter subfixes, like in Windows.
9) Start Mozilla, import all the first address book as "single file".
10) Carefully select which destination field (left colum) will suck up which source fields (right column). You do that by moving the destination fields. IMPORTANT: least you go nuts, start from the top and work your way down. Punch OK. Peruse the results. Don't do more imports until satisfied. Field mapping is sticky, so you'll do it only once.
11) Repeat for the other files. (I still have some doubts: sometimes contacts end up in the main Contacts folder istead of the one I select. I still need to investigate. Hints anyone?)
-->
</appendix>
<glossary id="apx-gloss">
<title>Glossary</title>
<glossentry id="assistant">
<glossterm>Assistant:</glossterm>
<glossdef>
<para>
A tool which guides a user through a series of steps,
usually to configure or set up a program. Equivalent to "Wizard"
and "Druid."
</para>
</glossdef>
</glossentry>
<glossentry id="attachment">
<glossterm>Attachment:</glossterm>
<glossdef>
<para>
Any file sent along with an email. Attachments may be embedded in
a message or appended to it.
</para>
</glossdef>
</glossentry>
<glossentry id="automatic-indexing">
<glossterm>Automatic Indexing:</glossterm>
<glossdef>
<para>
Pre-fetching procedure that allows
Evolution to refer to data quickly.
It enables faster searches and decreases memory usage for
data displays.
</para>
</glossdef>
</glossentry>
<glossentry id="bcc">
<glossterm>Bcc (Blind Carbon Copy):</glossterm>
<glossdef>
<para>
A way of addressing a message. Bcc is used to send a group of
people an e-mail, while hiding their names and addresses from each
other.
</para>
</glossdef>
</glossentry>
<glossentry id="cc">
<glossterm>Cc (Carbon Copy):</glossterm>
<glossdef>
<para>
Carbon-copies are used to send a 3rd party a copy of the e-mail,
so they an keep up to date on a conversation, without being in the
To: list.
</para>
</glossdef>
</glossentry>
<glossentry id="conduit">
<glossterm>Conduit:</glossterm>
<glossdef>
<para>
A small application which controls
the transfer of data between a handheld device and a desktop
computer.
</para>
</glossdef>
</glossentry>
<glossentry id="druid">
<glossterm>Druid:</glossterm>
<glossdef>
<para>
See "Assistant."
</para>
</glossdef>
</glossentry>
<glossentry id="evolution">
<glossterm>Evolution:</glossterm>
<glossdef>
<para>
Evolution is the <acronym> GNOME
</acronym> groupware application.
</para>
</glossdef>
</glossentry>
<glossentry id="execute">
<glossterm>Execute:</glossterm>
<glossdef>
<para>
To run a program. Any file that can be run is called an
executable. Evolution can download
executable attachments, but before they can be run, the files must
be marked as executable with a shell or file manager. This
security precaution prevents the automatic or accidental execution
of malicious programs. For more information on executables and file
permissions, see the documentation for your file manager or shell.
</para>
</glossdef>
</glossentry>
<glossentry id="expunge">
<glossterm>Expunge:</glossterm>
<glossdef>
<para>
When messages are marked for deletion, they remain till they are expunged.
When a message is expunged, it is permanently deleted, as long as it was
marked for deletion.
</para>
</glossdef>
</glossentry>
<glossentry id="filetree">
<glossterm>File Tree:</glossterm>
<glossdef>
<para>
A way of describing a group of files on a computer. With the
perversity typical of computer (and especially Unix and Linux)
nomenclature, the top of the tree is called the root directory,
and denoted by <filename>/</filename>.
The rest of the "branches" spread downward from the root. Don't
confuse the root directory with the root
account, or root's home directory, normally
<filename>/root</filename>.
</para>
</glossdef>
</glossentry>
<glossentry id="filter">
<glossterm>Filter:</glossterm>
<glossdef>
<para>
Within Evolution, a filter is a method
of sorting mail automatically when it's downloaded. You can create filters to perform
one or more actions on a message that meets any (or all) of a wide
range of criteria.
</para>
</glossdef>
</glossentry>
<glossentry id="forward">
<glossterm>Forward:</glossterm>
<glossdef>
<para>
If you get a message intended for someone else, you can use
message forwarding to send it on to the right person.
</para>
</glossdef>
</glossentry>
<glossentry id="groupware">
<glossterm>Groupware:</glossterm>
<glossdef>
<para>
Groupware is a term describing an application which helps groups
of people work together. Typically, a groupware application will
have several productivity features built into one program,
including: email, calendar, and address book tools.
</para>
</glossdef>
</glossentry>
<glossentry id="html">
<glossterm>HTML:</glossterm>
<glossdef>
<para>
Hyper-text Markup Language (<acronym>HTML</acronym>) is a language
for describing page layout in electronic documents like web pages,
help files, and email messages. HTML can be used in email and
news posts to insert images and apply text treatments.
</para>
</glossdef>
</glossentry>
<glossentry id="hot-key">
<glossterm>Hot Key:</glossterm>
<glossdef>
<para>
Hot-keys are keyboard combinations used to do actions on a
computer instead of using the mouse.
Hot-keys can speed up computer usage.
</para>
</glossdef>
</glossentry>
<glossentry id="ical">
<glossterm>iCal:</glossterm>
<glossdef>
<para>
<application>iCal</application> is the program which
Evolution uses to manage the calendar
section.
</para>
</glossdef>
</glossentry>
<glossentry id="imap">
<glossterm>IMAP:</glossterm>
<glossdef>
<para>
Depending upon whom you ask, IMAP stands for the Internet Mail
Access Protocol, or the Interim Mail Access Protocol. It allows access to email which is typically (although
not always) stored remotely on a server rather than on a local
hard disk. Often contrasted with <glossterm>POP:</glossterm>.
This will not be on the test.
</para>
</glossdef>
</glossentry>
<glossentry id="inline">
<glossterm>Inline:</glossterm>
<glossdef>
<para>
Displayed as part of a message or other document, rather than
attached as a separate file. Contrast with <glossterm
linkend="attachment">Attachment:</glossterm>.
</para>
</glossdef>
</glossentry>
<glossentry id="ldap">
<glossterm>LDAP:</glossterm>
<glossdef>
<para>
LDAP, the Lightweight Directory Access Protocol, allows a client
to search through a large database of addresses, phone numbers,
and people stored on a server.
</para>
</glossdef>
</glossentry>
<glossentry id="mail-client">
<glossterm>Mail Client:</glossterm>
<glossdef>
<para>
A mail client is the application with which a person reads and
sends e-mail. Its counterparts are the various types of mail
servers, which handle user authentication and direct messages from
sender to recipient.
</para>
</glossdef>
</glossentry>
<glossentry id="minicard">
<glossterm>Minicard:</glossterm>
<glossdef>
<para>
A format for the display of contact data. Similar in appearance
to a small business card.
</para>
</glossdef>
</glossentry>
<glossentry id="nautilus">
<glossterm>Nautilus:</glossterm>
<glossdef>
<para>
<application>Nautilus</application> is the file manager for <acronym>GNOME</acronym>.
</para>
</glossdef>
</glossentry>
<glossentry id="pop">
<glossterm>POP:</glossterm>
<glossdef>
<para>
POP, the Post Office Protocol, is a mechanism for email
transport. In contrast to IMAP, it is used only to get mail from
a server and store it locally on your hard disk.
</para>
</glossdef>
</glossentry>
<glossentry id="protocol">
<glossterm>Protocol:</glossterm>
<glossdef>
<para>
An agreed-upon method of communication, especially one for
sending particular types of information between computer systems.
Examples include POP (Post Office Protocol), for email, and HTTP
(HypterText Transfer Protocol), for web pages.
</para>
</glossdef>
</glossentry>
<glossentry id="postscript">
<glossterm>Postscript:</glossterm>
<glossdef>
<para>
A standard document publishing format. Many printers read raw
Postscript, making Postscript quite versatile.
</para>
</glossdef>
</glossentry>
<glossentry id="public-key-encryption">
<glossterm>Public Key Encryption:</glossterm>
<glossdef>
<para>
A strong encryption method that uses a set of two "keys," one of
which is made public, and one of which is kept private. Data
encrypted using the public key can only be decrypted using the
private key. The longer the keys, the more difficult it is to
break the encryption.
</para>
</glossdef>
</glossentry>
<glossentry id="regular-expression">
<glossterm>Regular Expression:</glossterm>
<glossdef>
<para>
A regular expression, or "regex", is a way of describing a
string of text using metacharacters or wild-card symbols. For
example, the statement <userinput>fly.*so[au]p</userinput> means
"any phrase beginning with 'fly' and ending in 'soup' or
'soap'". If you searched for that expression, you'd find both
"fly in my soup" and "fly in my soap." There's not room here to
go into depth, but if you want, have a look at the documentation
for the <command>grep</command> command by opening a command
line and typing in <command>man grep</command>.
</para>
</glossdef>
</glossentry>
<glossentry id="script">
<glossterm>Script:</glossterm>
<glossdef>
<para>
A program written in an interpreted (rather than compiled)
language. Often used as a synonym for "macro," to denote a series
of pre-recorded commands or actions within an application. Often
times, accomplish repetitive and tedious tasks, to save the
user time.
</para>
</glossdef>
</glossentry>
<glossentry id="search-base">
<glossterm>Search Base:</glossterm>
<glossdef>
<para>
LDAP can break contact lists into many groups. The Search
Base tells LDAP the top group to use. How much of the Search
Base that is searched is set by the <glossterm
linkend="search-scope">Search Scope</glossterm> option.
</para>
</glossdef>
</glossentry>
<glossentry id="search-scope">
<glossterm>Search Scope:</glossterm>
<glossdef>
<para>
Search Scope states how much of the <glossterm
linkend="search-base">Search Base</glossterm> to search.
</para>
</glossdef>
</glossentry>
<glossentry id="sendmail">
<glossterm>Sendmail:</glossterm>
<glossdef>
<para>
As its name implies, <application>sendmail</application> is a
program which sends mail. Evolution
can use it instead of <glossterm>SMTP:</glossterm>; some people
prefer it because it offers more flexibility, but is more
difficult to set up.
</para>
</glossdef>
</glossentry>
<glossentry id="shortcut-bar">
<glossterm>Shortcut Bar:</glossterm>
<glossdef>
<para>
A portion of Evolution which offers
users fast access to the most frequently used portions of the
application.
</para>
</glossdef>
</glossentry>
<glossentry id="signature">
<glossterm>Signature:</glossterm>
<glossdef>
<para>
In email terms, a signature is a piece of text placed at the end
of every email sent, similar to a hand-written signature at the bottom
of a written letter. A signature can be anything from a favorite
quotation to a link to a web page; courtesy dictates that it be
fewer than four lines long.
</para>
</glossdef>
</glossentry>
<glossentry id="smtp">
<glossterm>SMTP:</glossterm>
<glossdef>
<para>
This is the most common way of transporting mail messages from
the client's computer (you) to the server. SMTP stands for
Simple Mail Transfer Protocol.
</para>
</glossdef>
</glossentry>
<glossentry id="tooltip">
<glossterm>Tool-Tip:</glossterm>
<glossdef>
<para>
A small box of explanatory text which appears when the mouse
pointer is held motionless over a button or other interface
element.
</para>
</glossdef>
</glossentry>
<glossentry id="virus">
<glossterm>Virus:</glossterm>
<glossdef>
<para>
A program which inserts itself into other files or programs and
which, when executed, spreads to more programs and other
computers. A virus can cause substantial damage by clogging
networks or disk drives, deleting files, or opening security
holes.
</para>
</glossdef>
</glossentry>
<glossentry id="vcard">
<glossterm>VCard:</glossterm>
<glossdef>
<para>
A file format for the exchange of contact information. When you
get an address card attached to an email, it's probably in VCard
format. Not to be confused with <glossterm
linkend="vfolder">vFolder:</glossterm>.
</para>
</glossdef>
</glossentry>
<glossentry id="vfolder">
<glossterm>vFolder:</glossterm>
<glossdef>
<para>
An email organization tool. vFolders allows you to create a folder
that contains the results of a complex search. vFolder contents are
are updated dynamically.
</para>
</glossdef>
</glossentry>
</glossary>

419
help/C/apx-gpl.xml
View File

@ -1,419 +0,0 @@
<appendix id="apx-gpl">
<title>GNU General Public License</title>
<para>
Copyright (c) 2000 Free Software Foundation, Inc.
<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>.
</para>
<para>
This is version 2
</para>
<para>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
</para>
<sect1 id="preamble">
<title>Preamble</title>
<para>
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change
free software - to make sure the software is free for all its users.
This General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit
to using it. (Some other Free Software Foundation software is covered
by the GNU Library General Public License instead.) You can apply it
to your programs, too.
</para>
<para>
When we speak of free software, we are referring to freedom, not price.
Our General Public Licenses are designed to make sure that you have the
freedom to distribute copies of free software (and charge for this
service if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new free
programs; and that you know you can do these things.
</para>
<para>
To protect your rights, we need to make restrictions that forbid anyone
to deny you these rights or to ask you to surrender the rights. These
restrictions translate to certain responsibilities for you if you distribute
copies of the software, or if you modify it.
</para>
<para>
For example, if you distribute copies of such a program, whether gratis or
for a fee, you must give the recipients all the rights that you have. You
must make sure that they, too, receive or can get the source code. And you
must show them these terms so they know their rights.
</para>
<para>
We protect your rights with two steps:
<orderedlist numeration="arabic">
<listitem>
<para>
copyright the software, and
</para>
</listitem>
<listitem>
<para>
offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
</para>
</listitem>
</orderedlist>
</para>
<para>
Also, for each author's protection and ours, we want to make certain that
everyone understands that there is no warranty for this free software. If
the software is modified by someone else and passed on, we want its
recipients to know that what they have is not the original, so that any
problems introduced by others will not reflect on the original authors'
reputations.
</para>
<para>
Finally, any free program is threatened constantly by software patents.
We wish to avoid the danger that redistributors of a free program will
individually obtain patent licenses, in effect making the program
proprietary. To prevent this, we have made it clear that any patent must be
licensed for everyone's free use or not licensed at all.
</para>
<para>
The precise terms and conditions for copying, distribution and modification
follow.
</para>
</sect1>
<sect1 id="terms">
<title>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</title>
<sect2 id="sect0">
<title>Section 0</title>
<para>
This License applies to any program or other work which contains a notice
placed by the copyright holder saying it may be distributed under the terms
of this General Public License. The "Program", below, refers to any such
program or work, and a <quote>work based on the Program</quote> means either
the Program or any derivative work under copyright law: that is to say, a
work containing the Program or a portion of it, either verbatim or with
modifications and/or translated into another language. (Hereinafter, translation
is included without limitation in the term <quote>modification</quote>.) Each
licensee is addressed as <quote>you</quote>.
</para>
<para>
Activities other than copying, distribution and modification are not covered by
this License; they are outside its scope. The act of running the Program is not
restricted, and the output from the Program is covered only if its contents
constitute a work based on the Program (independent of having been made by running
the Program). Whether that is true depends on what the Program does.
</para>
</sect2>
<sect2 id="sect1">
<title>Section 1</title>
<para>
You may copy and distribute verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and appropriately
publish on each copy an appropriate copyright notice and disclaimer of warranty;
keep intact all the notices that refer to this License and to the absence of any
warranty; and give any other recipients of the Program a copy of this License
along with the Program.
</para>
<para>
You may charge a fee for the physical act of transferring a copy, and you may at
your option offer warranty protection in exchange for a fee.
</para>
</sect2>
<sect2 id="sect2">
<title>Section 2</title>
<para>
You may modify your copy or copies of the Program or any portion of it, thus
forming a work based on the Program, and copy and distribute such modifications
or work under the terms of <link linkend="sect1">Section 1</link> above, provided
that you also meet all of these conditions:
<orderedlist numeration="loweralpha">
<listitem>
<para>
You must cause the modified files to carry prominent notices stating that
you changed the files and the date of any change.
</para>
</listitem>
<listitem>
<para>
You must cause any work that you distribute or publish, that in whole or
in part contains or is derived from the Program or any part thereof, to be
licensed as a whole at no charge to all third parties under the terms of
this License.
</para>
</listitem>
<listitem>
<para>
If the modified program normally reads commands interactively when run, you
must cause it, when started running for such interactive use in the most
ordinary way, to print or display an announcement including an appropriate
copyright notice and a notice that there is no warranty (or else, saying
that you provide a warranty) and that users may redistribute the program
under these conditions, and telling the user how to view a copy of this
License.
<note>
<title>Exception:</title>
<para>
If the Program itself is interactive but does not normally print such an
announcement, your work based on the Program is not required to print an
announcement.)
</para>
</note>
</para>
</listitem>
</orderedlist>
</para>
<para>
These requirements apply to the modified work as a whole. If identifiable sections
of that work are not derived from the Program, and can be reasonably considered
independent and separate works in themselves, then this License, and its terms,
do not apply to those sections when you distribute them as separate works. But when
you distribute the same sections as part of a whole which is a work based on the
Program, the distribution of the whole must be on the terms of this License, whose
permissions for other licensees extend to the entire whole, and thus to each and
every part regardless of who wrote it.
</para>
<para>
Thus, it is not the intent of this section to claim rights or contest your rights
to work written entirely by you; rather, the intent is to exercise the right to control
the distribution of derivative or collective works based on the Program.
</para>
<para>
In addition, mere aggregation of another work not based on the Program with the Program
(or with a work based on the Program) on a volume of a storage or distribution medium
does not bring the other work under the scope of this License.
</para>
</sect2>
<sect2 id="sect3">
<title>Section 3</title>
<para>
You may copy and distribute the Program (or a work based on it, under
<link linkend="sect2">Section 2</link> in object code or executable form under the terms of
<link linkend="sect1">Sections 1</link> and <link linkend="sect2">2</link> above provided that
you also do one of the following:
<orderedlist numeration="loweralpha">
<listitem>
<para>
Accompany it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
</para>
</listitem>
<listitem>
<para>
Accompany it with a written offer, valid for at least three years, to give any
third party, for a charge no more than your cost of physically performing source
distribution, a complete machine-readable copy of the corresponding source code,
to be distributed under the terms of Sections and above on a medium customarily
used for software interchange; or,
</para>
</listitem>
<listitem>
<para>
Accompany it with the information you received as to the offer to distribute
corresponding source code. (This alternative is allowed only for noncommercial
distribution and only if you received the program in object code or executable form
with such an offer, in accord with Subsection b above.)
</para>
</listitem>
</orderedlist>
</para>
<para>
The source code for a work means the preferred form of the work for making modifications
to it. For an executable work, complete source code means all the source code for all modules
it contains, plus any associated interface definition files, plus the scripts used to control
compilation and installation of the executable. However, as a special exception, the source
code distributed need not include anything that is normally distributed (in either source or
binary form) with the major components (compiler, kernel, and so on) of the operating system
on which the executable runs, unless that component itself accompanies the executable.
</para>
<para>
If distribution of executable or object code is made by offering access to copy from a
designated place, then offering equivalent access to copy the source code from the same place
counts as distribution of the source code, even though third parties are not compelled to
copy the source along with the object code.
</para>
</sect2>
<sect2 id="sect4">
<title>Section 4</title>
<para>
You may not copy, modify, sublicense, or distribute the Program except as expressly provided
under this License. Any attempt otherwise to copy, modify, sublicense or distribute the
Program 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>
</sect2>
<sect2 id="sect5">
<title>Section 5</title>
<para>
You are not required to accept this License, since you have not signed it. However, nothing
else grants you permission to modify or distribute the Program or its derivative works.
These actions are prohibited by law if you do not accept this License. Therefore, by modifying
or distributing the Program (or any work based on the Program), you indicate your acceptance
of this License to do so, and all its terms and conditions for copying, distributing or
modifying the Program or works based on it.
</para>
</sect2>
<sect2 id="sect6">
<title>Section 6</title>
<para>
Each time you redistribute the Program (or any work based on the Program), the recipient
automatically receives a license from the original licensor to copy, distribute or modify
the Program subject to these terms and conditions. You may not impose any further restrictions
on the recipients' exercise of the rights granted herein. You are not responsible for enforcing
compliance by third parties to this License.
</para>
</sect2>
<sect2 id="sect7">
<title>Section 7</title>
<para>
If, as a consequence of a court judgment or allegation of patent infringement or for any other
reason (not limited to patent issues), conditions are imposed on you (whether by court order,
agreement or otherwise) that contradict the conditions of this License, they do not excuse you
from the conditions of this License. If you cannot distribute so as to satisfy simultaneously
your obligations under this License and any other pertinent obligations, then as a consequence
you may not distribute the Program at all. For example, if a patent license would not permit
royalty-free redistribution of the Program by all those who receive copies directly or
indirectly through you, then the only way you could satisfy both it and this License would be
to refrain entirely from distribution of the Program.
</para>
<para>
If any portion of this section is held invalid or unenforceable under any particular circumstance,
the balance of the section is intended to apply and the section as a whole is intended to apply
in other circumstances.
</para>
<para>
It is not the purpose of this section to induce you to infringe any patents or other property
right claims or to contest validity of any such claims; this section has the sole purpose of
protecting the integrity of the free software distribution system, which is implemented by public
license practices. Many people have made generous contributions to the wide range of software
distributed through that system in reliance on consistent application of that system; it is up
to the author/donor to decide if he or she is willing to distribute software through any other
system and a licensee cannot impose that choice.
</para>
<para>
This section is intended to make thoroughly clear what is believed to be a consequence of the
rest of this License.
</para>
</sect2>
<sect2 id="sect8">
<title>Section 8</title>
<para>
If the distribution and/or use of the Program is restricted in certain countries either by patents
or by copyrighted interfaces, the original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding those countries, so that
distribution is permitted only in or among countries not thus excluded. In such case, this License
incorporates the limitation as if written in the body of this License.
</para>
</sect2>
<sect2 id="sect9">
<title>Section 9</title>
<para>
The Free Software Foundation may publish revised and/or new versions of the General Public 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.
</para>
<para>
Each version is given a distinguishing version number. If the Program specifies a version number of
this License which applies to it and "any later version", you have the option of following the terms
and conditions either of that version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of this License, you may choose any
version ever published by the Free Software Foundation.
</para>
</sect2>
<sect2 id="sect10">
<title>Section 10</title>
<para>
If you wish to incorporate parts of the Program into other free programs whose distribution
conditions are different, write to the author to ask for permission. For software which is copyrighted
by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions
for this. Our decision will be guided by the two goals of preserving the free status of all
derivatives of our free software and of promoting the sharing and reuse of software generally.
</para>
</sect2>
<sect2 id="sect11">
<title>NO WARRANTY</title>
<subtitle>Section 11</subtitle>
<para>
BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT
PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
</para>
</sect2>
<sect2 id="sect12">
<title>Section 12</title>
<para>
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR
ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH
ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
</para>
</sect2>
</sect1>
</appendix>

1106
help/C/config-prefs.xml
View File

File diff suppressed because it is too large Load Diff

130
help/C/config-sync.xml
View File

@ -1,130 +0,0 @@
<chapter id="config-sync">
<title>Synchronization Settings</title>
<para>
Synchronization presents you with two issues you'll need to
address. First, your computer needs to recognize and access
your handheld. At this time, Novell Evolution only supports
PalmOS devices like the Palm Pilot and the Handspring Visor.
Secondly, you should decide what sort of synchronization
behavior you want.
</para>
<para>
If you haven't used a handheld device with your computer
before, you'll need to run the GNOME Control
Center by selecting
<menuchoice><guimenu>System</guimenu><guimenuitem>Settings</guimenuitem></menuchoice>,
and make sure that <application>Pilot Link</application> is
properly configured. You will need to make sure that you have
read and write permissions on the device, which is normally
/dev/pilot. If that does not work, check /dev/ttyS0 if you have
a serial connection, or /dev/ttyUSB0 for a USB connection. You
can do this by becoming root and running the command:
<userinput>chmod 777 /dev/ttyUSB0</userinput>.
</para>
<para>
Once your computer and your PalmOS device are talking happily
to each other, select the <link
linkend="conduit">conduits</link> you want under the
<guilabel>Pilot Conduits</guilabel> section of the Control
Center. You may use conduits to synchronize data with several
applications; the Novell Evolution
conduits are labeled <guilabel>EAddress</guilabel>, for the
contacts in your address book, <guilabel>ECalendar</guilabel>,
for your calendar, and <guilabel>ETodo</guilabel>, for your
task list.
</para>
<para>
To enable a conduit, click the
<guilabel>Enable</guilabel> to enable it, and click
<guilabel>Settings</guilabel> to change what it will do when
activated. Your options may vary depending on the conduit,
but typically they will be:
<variablelist>
<varlistentry>
<term>Disabled:</term>
<listitem>
<para>
Do nothing.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Synchronize:</term>
<listitem>
<para>
Copy new data from the computer to the handheld, and
from the handheld to the computer. Remove items
that were on both systems but have been deleted on
one.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Copy From Pilot:</term>
<listitem>
<para>
If there is any new data on the the handheld device,
copy it to the computer.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Copy To Pilot:</term>
<listitem>
<para>
Copy new data from the computer to the handheld.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Merge From Pilot:</term>
<listitem>
<para>
Copy new data from the handheld to the computer, and
remove any information from the computer that has
been deleted on the handheld.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Merge To Pilot:</term>
<listitem>
<para>
Copy new data from the computer to the handheld, and
remove any information from the handheld that has
been deleted on the computer.
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
<para>
Select the behavior you want for each conduit you choose to use.
If you're not sure, go ahead and stick with
<guilabel>Synchronize</guilabel>. Then, put your handheld on
its cradle and press the HotSync button.
</para>
<para>
<tip>
<title>Data Loss Prevention</title>
<para>
It's always a good idea to make a backup. To do that,
make a copy of the <filename>evolution</filename>
directory inside your home directory.
</para>
</tip>
</para>
</chapter>

129
help/C/evolution-1.5.xml
View File

@ -1,129 +0,0 @@
<?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 GFDL SYSTEM "apx-fdl.xml">
<!ENTITY LEGAL SYSTEM "legal.xml">
<!ENTITY GPL SYSTEM "apx-gpl.xml">
<!ENTITY PREFACE SYSTEM "preface.xml">
<!ENTITY USAGE-MAINWINDOW SYSTEM "usage-mainwindow.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 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">
<!ENTITY appversion "1.5">
<!ENTITY docversion "1.5">
<!ENTITY pubdate "May, 2004">
]>
<!-- Almost every chapter is an entity. Files, Chapter id's, and
entity names correspond. APX is for appendix. -->
<!-- STYLE RULES:
* Use "guilabel" instead of "guibutton" everywhere.
* "Address Book" is two words, but it's better to use "Contacts", Contact, or Contact List
* The "application" tag is not used around "Evolution."
* Filenames use command tags so they appear in the same font as commands
* There is one bar and it is the Shortcut Bar. The folder bar is dead. -->
<!-- FIXME, TODO: take new screenshots, -->
<book id="index">
<bookinfo>
<title>Evolution 1.5 Manual</title>
<authorgroup>
<author><firstname>Aaron</firstname><surname>Weber</surname></author>
<author><firstname>Kevin</firstname><surname>Breit</surname></author>
<author><firstname>Ettore</firstname><surname>Perazzoli</surname></author>
<author><firstname>Duncan</firstname><surname>Mak</surname></author>
</authorgroup>
<copyright>
<year>2000-2004</year>
<holder>Novell, Inc.</holder>
</copyright>
<releaseinfo>
This is version &docversion; of the Novell Evolution manual. It describes
version &appversion; of the Novell Evolution groupware suite.
</releaseinfo>
<legalnotice id="legalnotice">
<para>
Please note that legal and licensing information is in <xref linkend="preface" /> due to formatting issues with its
previous location.
</para>
</legalnotice>
</bookinfo>
<preface id="preface">
<title>Preface</title>
&LEGAL;
&PREFACE;
</preface>
<part id="usage">
<title>Using Evolution</title>
<partintro>
<para>
Part one of the Novell Evolution manual
describes how to use Novell Evolution for
email, contact management, and appointment and task
scheduling. You'll find as you go along that there's more
than one way to do things, and you can pick whichever method
you like best.
</para>
</partintro>
&USAGE-MAINWINDOW;
&USAGE-MAIL;
&USAGE-MAIL-ORG;
&USAGE-CONTACT;
&USAGE-CALENDAR;
&USAGE-EXCHANGE;
&USAGE-SYNC;
</part>
<part id="config">
<title>Setting Preferences</title>
<partintro>
<para>
Novell Evolution is highly
configurable. Usually, when developers say that, they mean
that they didn't test it out thoroughly and have left it to
other programmers to "configure" themselves a working
system. In the case of Novell
Evolution, "configurable" means that, while you
can expect the program to work perfectly well with the default
settings, it's also easy to alter its behavior in a wide
variety of ways, so that it fits your needs exactly. This
part of the book will describe that process, from the quickest
glimpse of the Setup Assistant to an in-depth guide to obscure
preferences settings.
</para>
</partintro>
&CONFIG-PREFS;
&CONFIG-SYNC;
</part>
&APX-GLOSS;
&MENUREF;
&APX-BUGS;
&APX-AUTHORS;
&GPL;
&GFDL;
</book>

8
help/C/evolution-1.5-C.omf → help/C/evolution-C.omf
View File

@ -2,15 +2,15 @@
<omf>
<resource>
<creator>
Ximian, Inc.
Novell, Inc.
</creator>
<title>
User's Guide to Ximian Evolution 1.4
User's Guide to Evolution 2.0
</title>
<date>2002-2003</date>
<subject category="GNOME|Applications"/>
<description>
A user's guide to Ximian Evolution which explains how to use
A user's guide to Evolution which explains how to use
its mail, calendar, addressbook, and task list features.
</description>
<type>
@ -20,6 +20,6 @@
<identifier url="/"/>
<language code="C"/>
<relation seriesid="83434cc6-71d1-11d7-9b12-ef76b8cf7c8f" />
<rights type="GNU FDL" license.version="1.1" license="http://www.gnu.org/licenses/fdl.html" holder="Ximian, Inc."/>
<rights type="GNU FDL" license.version="1.1" license="http://www.gnu.org/licenses/fdl.html" holder="Novell, Inc."/>
</resource>
</omf>

3901
help/C/evolution.xml Normal file
View File

File diff suppressed because it is too large Load Diff

BIN
help/C/figures/contacts_mainwindow_a.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 62 KiB

BIN
help/C/figures/evo_account_info_a.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 51 KiB

BIN
help/C/figures/evo_cal_callout_a.gif Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 38 KiB

BIN
help/C/figures/evo_contacteditor_a.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 61 KiB

BIN
help/C/figures/evo_email_a.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 86 KiB

BIN
help/C/figures/evo_identity_a.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 45 KiB

BIN
help/C/figures/evo_mail_callout_a.gif Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 50 KiB

BIN
help/C/figures/evo_mail_callout_a.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 88 KiB

BIN
help/C/figures/evo_newmess_a.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 48 KiB

BIN
help/C/figures/evo_receive_setup2_a.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 60 KiB

BIN
help/C/figures/evo_receive_setup_a.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 59 KiB

BIN
help/C/figures/evo_rule_a.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 40 KiB

BIN
help/C/figures/evo_send_setup_a.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 61 KiB

BIN
help/C/figures/evo_timezone_a.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 134 KiB

BIN
help/C/figures/mail_mainwindow_a.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 151 KiB

98
help/C/legal.xml
View File

@ -1,98 +0,0 @@
<sect1 id="legal-info-note">
<title>Legal Information and Licensing</title>
<!-- normally this content belongs in the actual "legalnotice" tag,
but for formatting reasons putting it in a sect1, inside the
Preface, and adding a paragraph to the beginning of it -->
<note id="evo-is-free-software">
<title>Novell Evolution is Free Software</title>
<para>
Novell Evolution is licensed under the terms of the GNU General
Public License (GPL), and its documentation is licensed
separately
under the GNU Free Documentation License (GFDL). You can find a the
complete text of the GPL in <xref linkend="apx-gpl" />, and of the
GFDL in <xref linkend="apx-fdl"/>. The licenses are also available
in the files COPYING and COPYING-DOCS distributed with this
software. The Evolution Connector for Microsoft Exchange is
also licensed under the GPL. Copyright for all three pieces of software and their documentation belongs to
Novell, Inc.
</para>
</note>
<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>
Novell is a registered trademark and Novell Evolution, the
dancing monkey logo and the Ximian capsule logo are
trademarks of Novell, Inc. Other names may be trademarks or
registered trademarks of other companies or
organizations. 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:
</para>
<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>
</sect1>

384
help/C/menuref.xml
View File

@ -1,384 +0,0 @@
<!--
<!DOCTYPE Appendix PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN">
-->
<appendix id="menuref">
<title>Quick Reference</title>
<para>
You might want to copy this section and tape it to the wall
next to your computer: it's a very short summary of most of
the things you'll want to do with
Novell Evolution.
</para>
<sect1 id="quickref-open">
<title>Opening or Creating Anything</title>
<para>
<variablelist>
<varlistentry>
<term>New Item:</term>
<listitem>
<para>
Press <keycombo action="simul"> <keycap>Ctrl</keycap> <keycap>N</keycap></keycombo> to open a new item
for whatever part of Novell
Evolution you're working on. In mail,
that means you'll create a new message. If you're
looking at your address book, <keycombo
action="simul"> <keycap>Ctrl</keycap>
<keycap>N</keycap></keycombo> creates a new contact
card, and in the calendar, a new appointment.
</para>
</listitem>
</varlistentry>
<!--
<varlistentry>
<term>Create a new folder:</term>
<listitem>
<para>
<menuchoice><guimenu>File</guimenu><guisubmenu>New</guisubmenu>
<guimenuitem>Folder</guimenuitem></menuchoice> or
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Shift </keycap>
<keycap>E</keycap>
</keycombo>
</para>
</listitem>
</varlistentry>
-->
<varlistentry>
<term>Create a new email message:</term>
<listitem>
<para>
Use
<menuchoice><guimenu>File</guimenu><guisubmenu>New</guisubmenu><guimenuitem>Mail
Message</guimenuitem> </menuchoice> or
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Shift </keycap>
<keycap>M</keycap>
</keycombo>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Create a new Appointment:</term>
<listitem>
<para>
<menuchoice><guimenu>File</guimenu>
<guisubmenu>New</guisubmenu>
<guimenuitem>Appointment</guimenuitem> </menuchoice> or
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Shift</keycap>
<keycap>A</keycap>
</keycombo>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Enter a new Contact:</term>
<listitem>
<para>
Double-click in any blank space in the contact
manager to create a new address card. You can also
use
<menuchoice><guimenu>File</guimenu>
<guisubmenu>New</guisubmenu>
<guimenuitem>Contact</guimenuitem> </menuchoice> or
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Shift</keycap>
<keycap>C</keycap>
</keycombo>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Create a new Task:</term>
<listitem>
<para>
<menuchoice><guimenu>File</guimenu>
<guisubmenu>New</guisubmenu>
<guimenuitem>Task</guimenuitem> </menuchoice> or
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Shift</keycap>
<keycap>T</keycap>
</keycombo>
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</sect1>
<sect1 id="quickref-mail">
<title>Mail Tasks</title>
<para>
Here are the most frequent email tasks, and shortcuts for
navigating your mailbox with the keyboard instead of the
mouse:
<variablelist>
<varlistentry>
<term>Send and Receive Mail:</term>
<listitem>
<para>
Press <keycap>F9</keycap>, click the
<guilabel>Send/Receive</guilabel> button in the
toolbar, or choose
<menuchoice><guimenu>Actions</guimenu>
<guimenuitem>Send/Receive</guimenuitem></menuchoice>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Navigating the Message List with the Keyboard:</term>
<listitem>
<para>
Press <keycap>]</keycap> or <keycap>.</keycap> to jump to the next unread
message. <keycap>[</keycap> or <keycap>,</keycap> goes to the previous
unread message. Use the arrow keys to move up
and down along the list of all messages.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Move the display up and down in the preview pane:</term>
<listitem>
<para>
Press the space bar to go a page down. Press
<keycap>Backspace</keycap> to go a page up.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Reply to a Message:</term>
<listitem>
<para>
To reply to the sender of the message only:
click <guilabel>Reply</guilabel> in the
toolbar, or press
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>R</keycap>
</keycombo>
</para>
<para>
To reply to the sender and all the other visible
recipients of the message, click <guilabel>Reply to
All</guilabel> or select the message and press
<keycombo action="simul">
<keycap>Shift</keycap>
<keycap>Ctrl</keycap>
<keycap>R</keycap>
</keycombo>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Forward a Message:</term>
<listitem>
<para>
Select the message or messages you want to forward,
and click <guilabel>Forward</guilabel> in the
toolbar, or press
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>F</keycap>
</keycombo>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Open a Message in a New Window:</term>
<listitem>
<para>
Double-click the message you want to view, or select
it and press <keycap>Return</keycap> or
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>O</keycap>
</keycombo>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Create Filters and Virtual Folders:</term>
<listitem>
<para>
Right-click on a message and select
<guimenuitem>Create Rule From
Message</guimenuitem>. You can also create filters and
virtual folders in the <guimenu>Tools</guimenu> menu.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Add Sender to Address Book:</term>
<listitem>
<para>
Right-click on a message and select <guimenuitem>Add
Sender to Address Book</guimenuitem>. You can also
right-click on any email address to add it to your
address book.
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</sect1>
<sect1 id="quickref-cal">
<title>Calendar</title>
<para>
<variablelist>
<varlistentry>
<term>Create a new Appointment:</term>
<listitem>
<para>
<menuchoice><guimenu>File</guimenu>
<guisubmenu>New</guisubmenu>
<guimenuitem>Appointment</guimenuitem> </menuchoice> or
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Shift</keycap>
<keycap>A</keycap>
</keycombo>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Create a new Task:</term>
<listitem>
<para>
<menuchoice><guimenu>File</guimenu>
<guisubmenu>New</guisubmenu>
<guimenuitem>Task</guimenuitem> </menuchoice> or
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Shift</keycap>
<keycap>T</keycap>
</keycombo>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term></term>
<listitem>
<para>
<tip id="new-appt">
<title>New Appointments Fast</title>
<para>
Click on any blank spot in the calendar and start
typing to create a new appointment entry.
</para>
</tip>
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</sect1>
<sect1 id="quickref-contact">
<title>Address Book</title>
<para>
Here are shortcuts for the most frequent address book actions:
<variablelist>
<varlistentry>
<term>Edit a Contact:</term>
<listitem>
<para>
You can edit a contact two ways:
<itemizedlist>
<listitem>
<para>
Click once on the person's address card and you can
edit the person's properties all in the same window.
</para>
</listitem>
<listitem>
<para>
Double-click on the contact's card and alter their details.
</para>
</listitem>
</itemizedlist>
</para>
</listitem>
</varlistentry>
</variablelist>
<variablelist>
<varlistentry>
<term>Deleting a Contact:</term>
<listitem>
<para>
Right click on a contact and click <guilabel>Delete</guilabel>
or select a contact and press the <guilabel>Delete</guilabel>
on the toolbar.
</para>
</listitem>
</varlistentry>
</variablelist>
<variablelist>
<varlistentry>
<term>Email a Contact:</term>
<listitem>
<para>
Right click on a contact and select
<guilabel>Send message to contact</guilabel>.
</para>
</listitem>
</varlistentry>
</variablelist>
<variablelist>
<varlistentry>
<term>Creating a New Contact:</term>
<listitem>
<para>
Double-click in any blank space in the contact
manager to create a new address card, or right-click anywhere
in the address book and select <guilabel>New
Contact</guilabel>. You can also select
use <menuchoice><guimenu>File</guimenu>
<guisubmenu>New</guisubmenu>
<guimenuitem>Contact</guimenuitem> </menuchoice> or press
<keycombo action="simul">
<keycap>Ctrl</keycap>
<keycap>Shift</keycap>
<keycap>C</keycap>
</keycombo>.
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</sect1>
</appendix>

190
help/C/preface.xml
View File

@ -1,190 +0,0 @@
<!-- The actual preface tag is in the evolution.xml file -->
<sect1 id="organization">
<title>Organization</title>
<para>
The first part of this book is a <link linkend="usage">guided
tour</link>, which will explain how to use Evolution. If you
are new to Evolution or to groupware in general, this section is
for you. The second section, covering <link
linkend="config">configuration</link>, is targeted at more
advanced users, but anyone who wants to change the way Evolution
looks or acts can benefit from reading it.
</para>
</sect1>
<sect1 id="other-help">
<title>Additional Help Sources</title>
<para>
You can find additional help in three places. For information
about command-line options, open a terminal window and type
<command>evolution --help</command>. For support,
late-breaking news, and errata, visit the Novell support center at
<ulink url="http://support.novell.com">support.novell.com</ulink>.
</para>
</sect1>
<sect1 id="whats-new-in-one-two">
<title>New in Evolution &appversion;</title>
<para>
Even if you're already familiar with earlier versions,
Evolution &appversion; has a lot of new features to offer.
You can find a complete list of bugs fixed and features added
in the Evolution release notes at the <ulink
url="http://gnome.org/projects/evolution/">Evolution Developer
Website</ulink>. Some of the features include:
</para>
<variablelist>
<varlistentry>
<term>Junk Mail (Spam) Filtering</term>
<listitem>
<para>
Novell Evolution &appversion; includes trainable
Bayesian junk mail filters. When you get mail you
don't want, click the <guilabel>Junk</guilabel> button
in the toolbar. Check your <guilabel>Junk
Mail</guilabel> folder periodically to see if it's
filtered out anything you want to keep, and mark it as
<guilabel>Not Junk.</guilabel> As you correct the
filter, it will become more effective.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>GroupWise Connectivity with no Additional Software</term>
<listitem>
<para>
Now you can access GroupWise servers as well as IMAP
and POP mail servers, with no additional installation
required. Connection to Microsoft Exchange 2000 and
2003 servers is possible with the Evolution Connector,
now available at no charge and under the GPL license.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>User Interface Updates</term>
<listitem>
<para>
The shortcut bar has been replaced with small buttons
at the bottom of the folder bar. The folder bar now
only displays data for the current function, instead
of putting all data together in one tree.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Security: S/MIME and Signatures</term>
<listitem>
<para>
Security with encryption and cryptographic signatures
has never been easier or stronger.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Hiding the "Evolution" Directory</term>
<listitem>
<para>
The <command>~/evolution/</command>
directory has been moved to
<command>~/.evolution</command>, keeping it
out of sight in most cases.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="preface-for-experts">
<title>Tips for Experienced Linux Users</title>
<para>
This section has a few tips for experienced users of Linux or
UNIX systems:
</para>
<variablelist>
<varlistentry>
<term>Backups and File Locations</term>
<listitem>
<para>
To create a backup of your Evolution data, copy the
<command>~/.evolution/</command> directory to
your backup disk. To access data you
have backed up, use the <guilabel>Import</guilabel> tool to
restore individual files as needed.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Default Browsers</term>
<listitem>
<para>
To set the browser used for links from email addresses,
open the GNOME preferences tool
(<menuchoice><guimenu>System</guimenu><guimenuitem>Personal
Settings</guimenuitem></menuchoice>
or <command>gnome-control-center</command>) and click
<guilabel>File Associations</guilabel>. On some systems,
this may be called <guilabel>MIME Types</guilabel> or
<guilabel>Default Applications</guilabel>.
</para>
<para>
In the <guilabel>File Associations</guilabel> tool, go to the
<guilabel>Internet Services</guilabel> section and click
<guilabel>World wide web (http)</guilabel>, then select
the browser of your choice. If you wish to use a
browser other than the ones suggested, you will need to
enter a complete shell command, rather than just the
browser name: <userinput>mybrowser
`%s`</userinput> rather than
<guilabel>My Browser</guilabel>.
Some systems may require you to set the browser used for
https:// links seperately.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Making Evolution Your Default Mail Client</term>
<listitem>
<para>
For GNOME desktops, you can set
Evolution to be the default
mail client, so that it opens when you click a mailto:
link in web pages and help tools. To do that, open the
GNOME preferences tool and start the <guilabel>File
Associations</guilabel> tool. There, look under
<guilabel>Internet Services</guilabel>, select
<guilabel>Electronic mail transmission
(mailto)</guilabel>, and select
<guilabel>Evolution</guilabel> from the drop-down
list.
</para>
<para>
If you are using KDE, you can also set Evolution as the
default through the KDE control center. Go to the
<guilabel>KDE Components</guilabel> section and select
<guilabel>Component Chooser</guilabel>, then
<guilabel>Email Client</guilabel>. Click the
<guilabel>Use a different email client</guilabel> option
and enter <userinput>evolution `%s`</userinput>.
</para>
<para>
For applications such as Mozilla and Netscape, which do
not use the GNOME preference tools, you will need to
find the protocol handler preference tool for that
application and enter <userinput>evolution
`%s`</userinput> as your choice for handling mailto links.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect1>

10
help/C/topic.dat
View File

@ -1,10 +0,0 @@
index.html Table of Contents
introduction.html Introduction
usage-mainwindow.html Getting Started
usage-mail.html Getting and Sending Email
usage-contact.html Using the Contact Manager
usage-calendar.html Managing Your Schedule
usage-exchange.html Connecting to Exchange Servers
config-prefs.html Configuring Evolution
menuref.html Quick Reference
apx-gloss.html Glossary

792
help/C/usage-calendar.xml
View File

@ -1,792 +0,0 @@
<!--
<!DOCTYPE Chapter PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN">
-->
<chapter id="usage-calendar">
<title>Evolution Calendar</title>
<para>
This chapter will show you how to use the Evolution
Calendar to manage your schedule alone or in conjunction with
peers. To learn about importing calendar data, see <xref
linkend="importing-mail" />, which covers the Import tool.
</para>
<sect1 id ="usage-calendar-view">
<title>Ways of Looking at your Calendar</title>
<para>
In Evolution, you can keep multiple calendars and overlay them
one over the next. For example, you might have a schedule of
events for work, one for home, and one for your favorite sports
team. The shortcut bar lists those calendars, and you can check
or uncheck the boxes next to them to show and hide the
appointments in your calendar view. By hiding and showing
different sets of appointments, you can be sure to avoid
conflicts, while keeping a minimum of clutter in your view at
any one time.
</para>
<para>
Appointments for each calendar appear as a different color.
</para>
<para>
The toolbar offers you four different buttons that can show you
different views of your calendar:
<itemizedlist>
<listitem>
<para>
Day
</para>
</listitem>
<listitem>
<para>
Work Week
</para>
</listitem>
<listitem>
<para>
Week
</para>
</listitem>
<listitem>
<para>
Month
</para>
</listitem>
</itemizedlist>
</para>
<para>
You can also select an arbitrary range of days in the small
calendar at the upper right. To do this, click and drag on the
days that you wish to view in your calendar.
</para>
<para>
The <guilabel>Prev</guilabel> and <guilabel>Next</guilabel>
buttons will move you forward and back in your calendar pages.
If you're looking at only one day, you'll see tomorrow's page,
or yesterday's. If you're looking at your calendar by week or
month, you'll move around by just that much.
To come back to today's listing, click the
<guilabel>Today</guilabel> button in the toolbar.
</para>
<para>
To visit calendar entries for a specific date, click
<guilabel>Go To</guilabel> and select the date in the dialog
box that appears.
</para>
</sect1>
<sect1 id="usage-calendar-apts">
<title>Scheduling With the Evolution Calendar</title>
<sect2 id="usage-calendar-apts-basic">
<title>Creating Appointments</title>
<para>
To create a new appointment, select
<menuchoice>
<guimenu>File</guimenu>
<guisubmenu>New</guisubmenu>
<guimenuitem>Appointment</guimenuitem>
</menuchoice>
click the <guilabel>New</guilabel> button on the left end
of the toolbar, or double-click in a blank space in the calendar.
</para>
<para>
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
it. That makes it easy to have appointments that overlap and fit
inside each other. For example, a conference might be an all
day appointment, and the meetings at the conference would be timed
appointments. Of course, appointments with specific starting and ending
times can also overlap. When they do they're displayed as
multiple columns in the day view of the calendar.
</para>
<para>
If you have more than one calendar, be sure to select the
calendar in which you want to save the appointment.
</para>
<para>
Evolution supports the use of
time zones. If you share calendar files with friends or
co-workers, it is quite possible you will need to configure
your tim ezone. To configure your time zone:
<orderedlist numeration="arabic">
<listitem>
<para>
Select
<menuchoice>
<guimenu>Tools</guimenu>
<guimenuitem>Settings</guimenuitem> </menuchoice>, and
click the <guilabel>Calendar And Tasks</guilabel> icon
in the settings dialog.
</para>
</listitem>
<listitem>
<para>
Click the <guilabel>Globe</guilabel> button in the
<guilabel>Time</guilabel> section, located in the
<guilabel>General</guilabel> tab.
</para>
</listitem>
<listitem>
<para>
Each red dot represents a major city. Click a dot and click <guilabel>OK</guilabel> to select your time zone.
</para>
</listitem>
</orderedlist>
</para>
<para>
You can also configure time zone information specific to the
Start and End time in each appointment. To do that, simply
create a new appointment and click on a globe to customize the
time zone that the time exists in. For example, if you live in
New York but have a telephone meeting set for noon with
someone in California, you need to make sure that you're not
calling each other a few hours off. Setting time-zones on a
per-appointment basis helps avoid that potential confusion.
</para>
<note>
<title>Multiple Simultaneous Appointments</title>
<para>
If you create calendar appointments that overlap,
Evolution will display them side
by side in your calendar. However,
Evolution cannot help you do
multiple things at once.
</para>
</note>
<para>
You can have several
<guilabel>Reminders</guilabel>, any time prior to the appointment
you've scheduled. You can have one reminder of each of the following types:
<variablelist>
<varlistentry>
<term><guilabel>Display:</guilabel></term>
<listitem>
<para>
A window will pop up on your screen to remind you of
your appointment.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><guilabel>Audio:</guilabel></term>
<listitem>
<para>
Choose this to have your computer deliver a sound
alarm.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><guilabel>Program:</guilabel></term>
<listitem>
<para>
Select this if you would like to run a program as a
reminder. You can enter its name in the text field,
or find it with the <guilabel>Browse</guilabel>
button.
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
<note id="reminders-when-not-running-evo">
<title>Reminders Without Evolution</title>
<para>
If you have stored reminders in a local calendar, they
will work from the moment you log in. However, for reminders
stored on an Exchange server, you must run Evolution at
least once after logging in. No matter where the reminders
are stored, you can quit Evolution and still be reminded of
an upcoming appointment.
</para>
</note>
<para>
If you are using a a calendar on a GroupWise or
Exchange server, select a <guilabel>Classification</guilabel>
for the appointment, to determine who can view it.
<guilabel>Public</guilabel> is the default category, and a
public appointment can be viewed by anyone on the calendar
sharing network. <guilabel>Private</guilabel> denotes one
level of security, and <guilabel>Confidential</guilabel> an even
higher level. The different levels vary depending on your
server settings; check with your system administrator or adjust
your delegation settings.
</para>
<para>
If you are using a GroupWise or Exchange server, other people
on the server can check your schedule to see if you are
available at any given time. If you have an appointment that
is flexible or that you wish to designate as "Free" rather
than "Busy" time, check the <guilabel>Free</guilabel> box in
the<guilabel>Show Time As</guilabel> section. Normally,
appointments display as "Busy."
</para>
<para>
You can categorize appointments in the same way you can
categorize contacts. Click the <guilabel>Categories</guilabel>
button opens up a checklist. Check the box next to each category
that matches the appointment you are creating.
</para>
<tip>
<title>Adding a New Appointment Category</title>
<para>
You can add a new category to your category list by clicking on
<guilabel>Edit Master Category List</guilabel> and single-clicking
on <guilabel> Click here to add a category</guilabel>.
</para>
</tip>
<para>
Once you've selected your categories, click <guilabel>OK</guilabel> to
assign these categories to the appointment. The categories you selected are now
listed in the text box to the right of the <guilabel>Categories...</guilabel>
button.
</para>
<para>
Appointments with categories will appear
with icons in the calendar display, and you can also search
for appointments by category. To display only the appointments
in a particular category, select <guilabel>Category
Is</guilabel> in the search bar at the top of the calendar, and
select a category.
</para>
<para>
The <guilabel>Recurrence</guilabel> tab lets you describe
repetition in appointments ranging from once every day up to once
every 100 years. You can then choose a time and date when the
appointment will stop recurring, and, under
<guilabel>Exceptions</guilabel>, pick individual days when the
appointment will <emphasis>not</emphasis> recur. Make your
selections from left to right, and you'll form a sentence:
"Every two weeks on Monday and Friday until January 3, 2008"
or "Every month on the first Friday for 12 occurrences."
</para>
<para>
Once you're done with all those settings, click on the disk
icon in the toolbar to save and close the appointment editor window.
If you want, you can alter an appointment
summary in the calendar view by clicking on it and typing. You
can change other settings by right-clicking on the appointment then
choosing <guimenuitem>Open</guimenuitem>, or double-clicking
the appointment.
</para>
</sect2>
<sect2 id="old-meetings">
<title>Deleting Old Events</title>
<para>
Keeping a huge list of everything you did in the past will
eventually slow down your calendar. To delete old events, select
<menuchoice><guimenu>Actions</guimenu><guimenuitem>Purge
</guimenuitem></menuchoice> and enter the number of days of past
events you wish to keep.
</para>
</sect2>
<sect2 id="usage-calendar-rsvp">
<title>Sending a Meeting Invitation</title>
<para>
Evolution can be used to schedule group meetings and help you
manage responses to meeting requests.
</para>
<para>
When you create a meeting or group appointment, you can
specify the attendees in several categories, such as "chair"
or "required." When you save the appointment listing, each
attendee will be sent an email with the appointment
information and gives them the option to respond.
</para>
<note id="meeting-announce">
<title>Simple Announcements</title>
<para>
If you don't need to collect attendance information when
you're scheduling an event, and would rather just announce
it, select
<menuchoice><guimenu>Actions</guimenu><guimenuitem>Forward
as iCalendar</guimenuitem></menuchoice>. That will open a
new email message with the event notification attached as
an announcement. Recipients will be able to add the event
to their calendars with one click, but won't automatically
send you email about whether they'll attend.
</para>
</note>
<para>
To schedule a meeting:
<orderedlist numeration="arabic">
<listitem>
<para>
Select
<menuchoice>
<guimenu>Actions</guimenu> <guimenuitem>Schedule
Meeting</guimenuitem> </menuchoice>. The
<guilabel>Scheduling</guilabel> and
<guilabel>Meeting</guilabel> tabs open.
</para>
</listitem>
<listitem>
<para>
If you have multiple Evolution email accounts, choose the
one you'll use by selecting an item in the
<guilabel>Organizer</guilabel> field.
</para>
</listitem>
<listitem>
<para>
Click the space labeled <guilabel>Click here to add an
attendee</guilabel> to enter the names and email
addresses of people you will invite, or click the
<guilabel>Invite Others</guilabel> to select them from
your contacts.
</para>
</listitem>
<listitem>
<para>
Save the Appointment.
</para>
</listitem>
</orderedlist>
An email is now sent out to all the recipients, inviting them to your event.
</para>
</sect2>
<sect2 id="replying-to-rsvp">
<title>Replying to a Meeting Request</title>
<para>
Meeting requests are sent as iCal attachments. To view or
respond to one, click on the attachment icon and view it
inline in the mail window. All the details are shown about
the event including time and dates. Then you can choose how
to reply to the invitation. Your choices are:
<itemizedlist>
<listitem>
<para>
<guilabel>Accept</guilabel>
</para>
</listitem>
<listitem>
<para>
<guilabel>Tentatively Accept</guilabel>
</para>
</listitem>
<listitem>
<para>
<guilabel>Decline</guilabel>
</para>
</listitem>
</itemizedlist>
Click <guilabel>OK</guilabel> and an email will be sent to
the organizer with your answer. The event will also be added
to your calendar if you accept.
</para>
<para>
Note, however, that if you add a meeting to your calendar,
there are some limitations: only the organizer of a meeting
can add participants in a meeting. Your only options, as a
participant, are to accept the meeting, or decline it.
</para>
<para>
Once you have added the meeting to your calendar, you can make
changes to your copy, but be aware
that if the original organizer sends out another update, your
changes may be overwritten.
</para>
<note id="organizer-only-one">
<title>There Can Be Only One</title>
<para>
A meeting can have only one organizer. You can designate
yourself the organizer of the meeting, but unless you
coordinate that action with the organizer you are replacing,
you could create confusion in the scheduling process. If you
want to invite additional people to a meeting without
changing the organizer, it's best to forward the first
organizer's message to the additional participants.
</para>
</note>
</sect2>
<sect2 id="receiving-rsvp-response">
<title>Getting Responses to Meeting Requests</title>
<para>
Once you get a reply to your meeting invitation, you'll need
to view it inline in the email. Click the attachment and
select <guimenuitem>View Inline</guimenuitem>. At the bottom, you
can click <guilabel>OK</guilabel> to update your attendee
list.
</para>
</sect2>
<!-- ############UNIMPLEMENTED FEATURES ###################
<sect2 id="usage-calendar-apts-group">
<title>Appointments for Groups</title>
<para>
You can use Evolution to mark a
meeting request on another person's calendar. To do it, click
<guilabel>New</guilabel> in the calendar toolbar, or select
<menuchoice> <guimenu>File</guimenu>
<guisubmenu>New</guisubmenu>
<guimenuitem>Appointment</guimenuitem> </menuchoice> to bring
up the <interface>new appointment</interface> window. Then
describe the appointment as you would any other. When you are
ready to send the invitation <guilabel>OK</guilabel>
Evolution will automatically send
email to each person on the request list, notifying of the
time and date of the meeting you have requested with them. In
addition, it will mark the appointment on your calendar and on
theirs as tentative, rather than a confirmed, appointment.
</para>
<para>
To mark a tentative appointment as confirmed, click once on the
appointment in the <interface>calendar view</interface> to select
it, and then choose <guimenuitem>Appointment
Properties</guimenuitem> from the <guimenu>Settings</guimenu>
menu. In the <interface>Appointment Properties</interface> dialog
window, click the "tentative" button to De-select the
appointment.
</para>
<para>
When your meeting attendees get the email inviting them to the
meeting, they'll be able to enter the information into their
calendars and let you know if they'll be able to attend; if
they use Novell Evolution or
another iCal compliant mail client, they can do this with just
one click. When you get a response from them, it will include
an iCal attachment. Opening and accepting this attachment will
change the meeting data in your calendar to indicate that they
have responded to your invitation, and whether they will be in
attendance.
</para>
</sect2>
<sect2 id="usage-calendar-apts-privs">
<title>Scheduling privileges</title>
<para>
There are several levels of scheduling privileges. You
can set whether people can see your calendar, whether they
can request meetings or appointments, and whether they can
create appointments. This section may have to be deleted,
because I don't know if we are going to support privileges
at all.
</para>
</sect2>
########## END UNIMPLEMENTED FEATURESET ############ -->
<sect2 id="usage-calendar-freebusy">
<title>Scheduling Meetings and The Free/Busy View</title>
<para>
In addition to the standard meeting scheduling tools, you can
use the Free/Busy view to check whether people are available
in advance. The Free/Busy feature is normally a function of
dedicated groupware servers such as Exchange and Groupwise.
However, you can also publish Free/Busy information online,
and access Free/Busy information published elsewhere.
If not everyone you collaborate with publishes Free/Busy data,
you can still use iCal event invitations to coordinate
schedules with other
people.
</para>
<para>
To access the free/busy view:
<orderedlist numeration="arabic">
<listitem>
<para>
Open or create an appointment in the
<guilabel>Calendar</guilabel> window.
</para>
</listitem>
<listitem>
<para>
Click
<menuchoice>
<guimenu>Actions</guimenu>
<guimenuitem>Schedule Meeting</guimenuitem>
</menuchoice>
</para>
</listitem>
<listitem>
<para>
Open the <guilabel>Scheduling</guilabel> tab.
</para>
</listitem>
</orderedlist>
</para>
<figure>
<title>Appointment Scheduling Window</title>
<screenshot>
<screeninfo>Appointment Scheduling Window</screeninfo>
<mediaobject><imageobject>
<imagedata format="PNG" fileref="figures/schedule" srccredit="Kevin Breit"/>
</imageobject></mediaobject>
</screenshot>
</figure>
<para>
<inlinemediaobject>
<imageobject>
<imagedata fileref="figures/full-1" format="PNG"/>
</imageobject>
</inlinemediaobject>
<guilabel>Attendee List</guilabel>
</para>
<para>
The <guilabel>Attendee List</guilabel> lists off the people who
have been invited to the respective appointment. It also
shows their RSVP status.
</para>
<para>
<inlinemediaobject>
<imageobject>
<imagedata fileref="figures/full-2" format="PNG"/>
</imageobject>
</inlinemediaobject>
<guilabel>Schedule Grid</guilabel>
</para>
<para>
The <guilabel>Schedule Grid</guilabel> shows the published
Free/Busy information for the people you have invited. This is
where you compare people's schedules to find free time to
schedule the appointment. Individuals will only have visible
scheduling information if they use the same GroupWise or
Exchange server you do (that is, if they are in the same
organization as you), or if they publish free/busy information
at a URL you can reach and you have entered that URL into their
contact card using the contact editor.
</para>
<para>
<inlinemediaobject>
<imageobject>
<imagedata fileref="figures/full-3" format="PNG"/>
</imageobject>
</inlinemediaobject>
<guilabel>Meeting Scheduler</guilabel>
</para>
<para>
The <guilabel>Meeting Scheduler</guilabel> allows you to
schedule the meeting in the <guilabel>Free/Busy</guilabel> window.
</para>
<sect3 id="usage-calendar-freebusy-scheduling">
<title>Scheduling an Appointment</title>
<para>
To schedule an appointment, you'll first need people's
free/busy information. If you're using the Evolution Connector
for Microsoft Exchange, all of the information is already
available to you in the Global Address List. Otherwise, each
person will have to email you their schedule files and you
will have to incorporate them into your calendar.
</para>
<para>
Regardless of how you get the information, Novell Evolution
will display it in the <guilabel>Scheduling</guilabel> tab.
The pending appointment time will appear in white with bold
black borders. Each attendee's free and busy times appear
color-coded next to their names in the attendee list.
</para>
<para>
Adjust the meeting time, either by dragging the meeting
borders or by using the <guilabel>Autopick</guilabel>
buttons to choose a time automatically, then click
<guilabel>Save and Close</guilabel>. Attendees on an
Exchange server will have the appointment updated
automatically; others will receive email notification of any
change in plans.
</para>
<para>
Read <xref linkend="full-advantage"/> to learn about how to
use this feature with the Evolution Connector for Microsoft
Exchange.
</para>
</sect3>
<sect3 id="publishing-freebusy">
<title>Publishing Free/Busy Data Without a Groupware Server</title>
<para>
You can publish Free/Busy information to a WebDAV or other
web server with HTTP PUT support. Check with your system
administrator if you are not sure.
</para>
<para>
To set up Free/Busy publishing, select
<menuchoice>
<guimenu>Tools</guimenu>
<guimenuitem>Settings</guimenuitem>
</menuchoice>, then click the <guilabel>Calendar and
Tasks</guilabel> tool. In the <guilabel>Free/Busy
Publishing</guilabel> tab, click <guilabel>Add</guilabel> and
enter the URL for your upload server. Select the frequency
with which you wish to upload data, the calendars for which
you wish to display data, your username and
password, and then click <guilabel>OK</guilabel>.
</para>
<para>
To have Free/Busy data published immediately, go to the
<guilabel>Calendar</guilabel> tool and select <menuchoice>
<guimenu>Actions</guimenu>
<guimenuitem>Publish Free/Busy</guimenuitem>
</menuchoice>
</para>
</sect3>
<sect3 id="accessing-freebusy-offserver">
<title>Accessing Free/Busy Data Without a Groupware Server</title>
<para>
If someone gives you a URL for Free/Busy data or their web
calendar, you can enter it as part of their contact
information in the <guilabel>Contacts</guilabel> tool. Then,
when you schedule a meeting with them, Evolution will look up
their schedule and display it in the meeting planner.
</para>
</sect3>
</sect2>
</sect1>
<sect1 id="usage-calendar-multiple">
<title>Multiple Calendars and Web Calendars</title>
<para>
To create a new calendar, select
<menuchoice>
<guimenu>File</guimenu> <guisubmenu>New</guisubmenu>
<guimenuitem>Calendar</guimenuitem>
</menuchoice>. If the calendar is one you plan to store locally,
you need only provide a name and color. If it is a remote
calendar, enter the name, color, URL, and a refresh
frequency. The refresh frequency determines how often Evolution
will check to see if the calendar has changed. If you are
working with someone who publishes an online calendar, you may
want to check for updates every thirty minutes. On the other
hand, if you have displayed a sports team schedule in your
calendar, you may not need to refresh it more than once a week,
if at all.
</para>
<para>
The website <ulink
url="http://icalshare.com">icalshare.com</ulink> has an extensive list
of shared online calendars, including national and religious
holidays, phases of the moon, sports, and local and regional events.
</para>
</sect1>
<sect1 id="usage-calendar-todo">
<title>The Task Pad</title>
<para>
The Task Pad, located in the lower right corner of the
calendar, lets you keep a list of tasks separate from your
calendar appointments. You can use the list
in a larger window by choosing the <guilabel>Tasks</guilabel>
button in the shortcut bar or in the folder tree.
</para>
<para>
To record a new task, click the <guilabel>Add</guilabel>
button in the toolbar. Evolution
will pop up a small window with five items in it:
<variablelist>
<varlistentry>
<term> <guilabel>Summary:</guilabel></term>
<listitem>
<para>
The description you enter here will appear in the To Do
list itself.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term> <guilabel>Due Date:</guilabel></term>
<listitem>
<para>
Decide when this item is
due. You can either type in a date and time, or select one from
the <guilabel>Calendar</guilabel> and <guilabel>time</guilabel> drop-down menus.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><guilabel>Start Date:</guilabel></term>
<listitem>
<para>
The date you intend to start working.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term> <guilabel>Description:</guilabel></term>
<listitem>
<para>
If you wish, you can keep a more detailed description of
the item here. For example, you can note that a task is
in progress, and display how close it is to completion.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><guilabel>Classification:</guilabel></term>
<listitem>
<para>
Sets who will see it if your calendar is shared.
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
<para>
There are more options in the <guilabel>Details</guilabel> tab such as priority and progress settings.
</para>
<para>
Once you've added a task to your to-do list, its summary
appears in the <guilabel>Summary</guilabel> section of task
list. To view or edit a detailed description of an item,
double-click on it, or right click on it and select <guilabel>Open</guilabel>. You can delete items by selecting
them and clicking on the <guilabel>Delete</guilabel> button.
</para>
<para>
The list of tasks is sorted in a similar way to the list of
email messages in Novell Evolution
Mail. Click once on the message headers to change
the direction and type of sorting, or right-click to add or
remove columns from the display.
</para>
<sect2 id="task-folders">
<title>Task Groups</title>
<para>
As with calendars, you can create multiple task groups. Task
groups are more easily organized in the dedicated
<guilabel>Tasks</guilabel> tool. Each task group is assigned a
color, and in the <guilabel>Tasks</guilabel> tool shortcut bar
you can hide and show task groups just like calendars. In the
calendar display task pad, tasks from all visible task groups
will appear, color coded by group. To create a new task
group, select <menuchoice><guimenu>New</guimenu>
<guimenuitem>Task Group</guimenuitem></menuchoice>. You will
be prompted for a name, color, and location for the task
group. If the task group is online, you will need to provide
the URL for it.
</para>
</sect2>
</sect1>
</chapter>

494
help/C/usage-contact.xml
View File

@ -1,494 +0,0 @@
<!--
<!DOCTYPE Chapter PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN">
-->
<chapter id="usage-contact">
<title>Evolution Contacts: the Address Book</title>
<para>
This chapter will show you how to use the
Evolution contacts tool to organize
any amount of contact information, share addresses over a
network, and several ways to save time with everyday tasks. To
learn about configuring the contacts tool, see <xref
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>,
or by mailing them to yourself as vCard attachments.
</para>
<para>
Double-click on a card to display all its details.
</para>
<sect1 id="usage-contact-cards">
<title>The Contact Editor</title>
<para>
If you want to add or change cards, you'll use the contact
editor. To change a card that already exists, double click on
it to open the contact editor window. If you want to create a new
card, clicking the <guilabel>New</guilabel> button in the
toolbar will open the same window, with blank entry boxes for
you to fill in.
</para>
<para>
The contact editor window has three tabs,
<guilabel>Contact</guilabel>, for basic contact information,
<guilabel>Personal Information</guilabel>, for a more specific description of
the person, including URLs for their calendar and free/busy information,
and <guilabel>Mailing Address</guilabel>.
In the
<guimenu>Actions</guimenu> menu you will find <guimenuitem>Forward
Contact</guimenuitem>, which opens a new message with the card
already attached, and <guimenuitem>Send Message to
Contact</guimenuitem>, which will open a new message to the
contact's email address.
</para>
<para>
From the contact editor toolbar, you can <guilabel>Save and
Close</guilabel>, <guilabel>Print</guilabel>,
<guilabel>Close</guilabel>, or <guilabel>Delete</guilabel> the contact.
</para>
<figure id="usage-contact-editor-fig">
<title>Evolution Contact Editor</title>
<screenshot>
<screeninfo>Evolution Contact Editor</screeninfo>
<mediaobject><imageobject><imagedata
fileref="figures/contact-editor" format="PNG" srccredit="Aaron
Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>
<tip>
<title>Contact Shortcuts</title>
<para>
You can add cards from within an email message or calendar
appointment. While looking at an email, right-click on
any email address or message, and choose
<guimenuitem>Create Card for this Address</guimenuitem> or
<guimenuitem>Create Card for this Sender</guimenuitem>
from the menu.
</para>
</tip>
<para>
Most of the items in the contact editor simply display the
information you enter, but some of them have additional
features:
</para>
<para>
<variablelist>
<varlistentry>
<term>Full Name</term>
<listitem>
<para>
Enter the name of your contact here. You can enter a
name into the <guilabel>Full Name</guilabel> field, but
you can also click the <guilabel>Full Name</guilabel>
button to bring up a small dialog box with a few text
boxes for first and last names, titles like "Mr." or "Her
Excellency," and suffixes like "Jr."
</para>
<para>
The <guilabel>Full Name</guilabel> field also
interacts with the <guilabel>File Under</guilabel>
box to help you organize your contacts and to handle
multi-word surnames.
</para>
<para>
To see how it works, type a name in the
<guilabel>Full Name</guilabel> field. As an example,
we'll use <userinput>Miguel de Icaza</userinput>. You'll notice that the
<guilabel>File Under</guilabel> field also fills in,
but in reverse: <computeroutput>Icaza, Miguel de
</computeroutput>. If you had entered <userinput>John Q.
Doe</userinput>, the contacts editor would have
correctly guessed that the entry should be filed under
"Doe, John Q." However, Miguel's surname, "de Icaza,"
has two words, and so to get proper sorting you must enter
<userinput>de Icaza, Miguel</userinput> in the
<guilabel>File As</guilabel> entry.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Where</term>
<listitem>
<para>
Select one of your address books as the location for
this contact. You may not be able to write to all
available address books, especially those on a network.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Categories</term>
<listitem>
<para>
Click the <guilabel>Categories</guilabel> button to
select categories for this card. If you assign contact
categories, you can then search for contacts using those
categories. For more information on contact categories,
read <xref linkend="usage-contact-organize"/>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Free/Busy and Calendar URLs</term>
<listitem>
<para>
Click the <guilabel>Personal Information</guilabel> tab
to enter web addresses for the contact. If the contact
publishes Free/Busy or calendar data online, using a
server other than Exchange or GroupWise, you can enter the
address for those servers here. Once you do so, you will
be able to check their schedule when creating appointments
in the calendar.
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</sect1>
<sect1 id="contact-search">
<title>Searching for Contacts</title>
<para>
To search through contacts:
<orderedlist numeration="arabic">
<listitem>
<para>
Select your search type in the search bar.
</para>
</listitem>
<listitem>
<para>
Enter your query.
</para>
</listitem>
<listitem>
<para>
Press return to search.
</para>
</listitem>
</orderedlist>
</para>
<para>
For a more complex search, select
<menuchoice>
<guimenu>Search</guimenu>
<guimenuitem>Advanced</guimenuitem>
</menuchoice> and select criteria that describe your desired contact:
</para>
<orderedlist>
<listitem>
<para>
Name the rule in the <guilabel>Rule Name</guilabel> field.
</para>
</listitem>
<listitem>
<para>
Setup your criteria in the <guilabel>If</guilabel> section.
</para>
</listitem>
<listitem>
<para>
If you want to add more criteria, click the <guilabel>Add
Criterion</guilabel> button.
</para>
</listitem>
<listitem>
<para>
Click <guilabel>Search</guilabel>.
</para>
</listitem>
</orderedlist>
<para>
To show all your contacts, Click <guilabel>Clear</guilabel> in the
search bar, press
<keycombo><keycap>Shift</keycap><keycap>Ctrl</keycap><keycap>B</keycap></keycombo>
or search with an empty query.
</para>
</sect1>
<sect1 id="usage-contact-organize">
<title>Organizing your Contacts</title>
<para>
Just as you can search mail, you can search contacts. You can
also create several individual address books, or contact groups.
Within a given contact group, you can have several
categories of contacts.
</para>
<!-- UNIMPLEMENTED FEATURE
<para>
Another useful Evolution feature is
its ability to recognize when people live or work together. If
several people in your address book share an address, and you
change the address for one of them,
Evolution will ask you if you wish to
change the address for all of them, or just for one.
</para>
-->
<sect2 id="usage-contact-organize-group">
<title>Contacts Groups</title>
<para>
The simplest way to organize contacts is to create
additional groups of contacts. You can create a new one by
selecting <menuchoice><guimenu>New</guimenu>
<guimenuitem>Contacts Group</guimenuitem></menuchoice> For
contacts groups on your computer, you only need to provide a
name. For contacts on the network, you will need to provide
more information about the contacts server you are trying to
access.
</para>
<para>
To move a card from one group to another, just drag it there
from the main display of contacts. Note that you will not be
able to change the contents of most network contact groups.
</para>
<tip id="lists-vs-groups">
<title>Contact Lists and Contact Groups</title>
<para>
Contacts groups are not the same as contact lists. A
contact group is like a folder or address book full of contacts. A
contact list is a single contact which contains other
contacts, and is most often used to email several people at once.
</para>
</tip>
</sect2>
<sect2 id="usage-contact-organize-group-list">
<title>Creating a List of Contacts</title>
<para>
A contact list is a set of contacts with a single nickname
that you create. When you send email to the nickname, it is sent to
every member of the list. This differs from a network
mailing list in that it exists only on your computer as a
convenience to you, rather than as an actual email address
managed by a mailing list application on a server.
</para>
<para>
For example, you could create one card for each family
member, then add
those cards to a contact list called "Family." Then,
instead of entering each person's email address
individually, you could send email to "Family" and the
message would go to all of them.
</para>
<para>
To create a list of contacts:
<orderedlist numeration="arabic">
<listitem>
<para>
Open the list creation dialog box by clicking the
<guilabel>New List</guilabel> button or selecting
<menuchoice>
<guimenu>
File
</guimenu>
<guisubmenu>
New
</guisubmenu>
<guimenuitem>
Contact List
</guimenuitem>
</menuchoice>.
</para>
</listitem>
<listitem>
<para>
Enter a name for the list.
</para>
</listitem>
<listitem>
<para>
Enter names or email addresses of contacts, or just
drag contacts from the main window into the list.
</para>
</listitem>
<listitem>
<para>
Choose whether you would like to hide the email
addresses when you send a message to the list.
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"/>.
</para>
</listitem>
</orderedlist>
</para>
<para>
When you are done, click <guilabel>OK</guilabel>. The
list will appear as a contact card, which you can use as
you would any other. That includes emailing the list to
another person, and, of course, sending email to the list.
</para>
<para>
To mail the list, open a new email and type the name you
chose for the list. Novell Evolution will address the
message to the entire list when you send it. You can also
right-click on the list's address card in the contacts tool
and select <guimenuitem>Send Message to List</guimenuitem>.
</para>
<para>
Evolution cannot store contact lists on Microsoft Exchange
servers.
</para>
</sect2>
<sect2 id="usage-contact-organize-group-category">
<title>Grouping with Categories</title>
<para>
The other way to group cards is to mark them as belonging
to different categories. That means that you
can mark a card as being in several categories or no
category at all. For example, you put a friend's
card in the "Business" category, because he works with you,
the "Friends" category, because he's a friend, and
the "Frequent" category, because you call him often, but can
never remember the number.
</para>
<para>
To mark a card as belonging to a category, click the
<guilabel>Categories</guilabel> button at the lower
right. From the dialog box that appears, you can check as
many or as few categories as you like.
</para>
<para>
If the master list of categories doesn't suit you, you can
add your own. Just enter the new category's name in the
text box, then click <guilabel>Categories</guilabel> and
choose <guilabel>Edit Master Category List</guilabel> in the
window that appears.
</para>
</sect2>
</sect1>
<sect1 id="usage-contact-sharing">
<title>LDAP: Shared Contact Groups on a Network</title>
<para>
The <link linkend="ldap">LDAP</link> protocol was
created to let users share contact information over a network by
sharing access to a central directory. LDAP allows a company
to maintain a shared set of contact information. Many companies
keep a common LDAP address book for all their employees or for
client contacts.
</para>
<para>
To learn how to add a remote directory to your available
contact folders, see <xref linkend="config-prefs-contact"/>.
Remote groups of contacts appear under the <guilabel>On LDAP
Servers</guilabel> item in the shortcut bar. They work
exactly like a local folder of cards, with the following
exceptions:
<itemizedlist>
<listitem>
<para>
Network folders are only available when you are
connected to the network. If you use a laptop or have a
modem connection, you may wish to copy or cache some of the
network directory. You do this by dragging and dropping
your desired contacts into the local contacts list.
</para>
</listitem>
<listitem>
<para>
To prevent excess network traffic,
Evolution will not normally
load data from the LDAP server immediately upon
opening. You must click <guilabel>Display
All</guilabel> before contacts will be loaded
from the network. You can change this behavior in the
<interface>Contact Preferences</interface> window.
</para>
</listitem>
<listitem>
<para>
Depending on your server settings, you may not be able to edit
all the fields in a contact stored on an LDAP server. Some
servers prohibit some or all changes, and others use a smaller
set of fields than Evolution allows. Check with your system
administrator if you need different settings.
</para>
</listitem>
</itemizedlist>
</para>
<sect2 id="usage-contact-sharing-setup">
<title>Configuring Evolution to use LDAP</title>
<para>
For information about setting up
Evolution to use LDAP, please refer
to <xref linkend="config-prefs-contact" />
</para>
</sect2>
</sect1>
<sect1 id="contact-automation-basic">
<title>Send me a Card: Adding New Cards Quickly</title>
<para>
As noted before, when you get information about a person in
the mail or in a calendar entry, you can add it to an address
card. To do so, right click on any email address or email
message, and select <guimenuitem>Add Sender to Contacts</guimenuitem> from the menu that appears.
Evolution can also add cards from a
hand-held device during HotSync operation. For more
information about that, see <xref linkend="usage-sync"/>.
</para>
</sect1>
<!-- Unimplemented features:
<para>
You can also use the contacts tool to print postal addresses
on mailing labels. Future versions of
Evolution will allow you to you
export a group of cards to a spreadsheet, database, or word
processor so you can print address labels or prepare large
mailings.
</para> -->
</chapter>

951
help/C/usage-exchange.xml
View File

@ -1,951 +0,0 @@
<chapter id="usage-exchange">
<title>Connecting to Exchange Servers</title>
<para>The Evolution Connector for Microsoft Exchange allows Novell
Evolution clients to access accounts on Microsoft Exchange 2000
servers. It is available through Novell Red Carpet in its own
channel. Like Novell Evolution, it is free software and licensed under the
GPL.
</para>
<warning id="licensing">
<title>Requirements</title>
<para>
Evolution Connector works only with Exchange 2000 and later, and requires
that Outlook Web Access be enabled. Each user will need a
valid Microsoft Exchange server account, including license.
</para>
</warning>
<sect1 id="new-in-connector">
<title>What's New in Connector &appversion;</title>
<para>
Evolution Connector &appversion; is primarily a bug-fixing
release. New features include password management and password
expiration warnings.
</para>
<para>
Previous versions of Evolution Connector for Microsoft Exchange added
support for the <guilabel>Flag for Followup</guilabel> and
<guilabel>Out of Office</guilabel> feature,
public folders, delegation, direct booking, and more.
</para>
</sect1>
<sect1 id="features">
<title>Connector Features</title>
<para>
Evolution
Connector supports the following basic
<application>Microsoft Exchange</application> features:
<itemizedlist>
<listitem>
<para>
General
</para>
<variablelist>
<varlistentry>
<term>Remote Exchange Information Store</term>
<listitem>
<para>
Allows you to access mail, address book (including
Global Address List folder), and calendars, and task
folders on an Exchange 2000 server from Evolution.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Palm synchronization</term>
<listitem>
<para>
Supported for Contacts and Calendars on Exchange.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Password Management</term>
<listitem>
<para>
To change your password, go to the
<guilabel>Exchange</guilabel> tool and select <menuchoice>
<guimenu>Actions</guimenu> <guimenuitem>Change Exchange
Password</guimenuitem> </menuchoice>. If your
password has expired, Evolution will ask you to
change your password when you start up.
</para>
</listitem>
</varlistentry>
</variablelist>
</listitem>
<listitem>
<para>
Mail
</para>
<variablelist>
<varlistentry>
<term>Viewing Mail in Exchange Folder</term>
<listitem>
<para>Mail stored on the Exchange server is visible in
the <guilabel>Mail</guilabel> and <guilabel>Exchange</guilabel> tools
in Evolution. </para>
</listitem>
</varlistentry>
<varlistentry>
<term>Sending Email via Exchange Protocols</term>
<listitem>
<para>
You may use the Microsoft Exchange mail transport
protocol to send email. Make sure that the address
you have entered as your email address is exactly
the one that the Exchange server has on file. This
may be "yourname@exchange-server.ximian.com" rather
than "yourname@ximian.com."
</para>
</listitem>
</varlistentry>
</variablelist>
</listitem>
<listitem>
<para>
Calendar
</para>
<variablelist>
<varlistentry>
<term>Meeting Request/Proposal</term>
<listitem>
<para>
Allows Evolution users to
schedule meetings and view attendee availability for
other users (Evolution or
Outlook users) on
Exchange.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Adding iCalendar Meeting Requests to Calendar</term>
<listitem>
<para>
If you receive an iCalendar meeting request and add it
to your calendar, it will be saved to your
Exchange calendar.
</para>
</listitem>
</varlistentry>
</variablelist>
</listitem>
<listitem>
<para>
Contacts
</para>
<variablelist>
<varlistentry>
<term>Address Completion</term>
<listitem>
<para>
Supported for your Exchange
Contacts folder. Not yet supported for the Global
Address List.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Adding VCards to Address Book</term>
<listitem>
<para>
If you receive a VCard attachment and click
<guilabel>Save in Address Book</guilabel>, it will
be saved to your Exchange address book.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>New Address Book entries can be created on
Exchange from received email
messages with a single click</term>
<listitem>
<para>
</para>
</listitem>
</varlistentry>
</variablelist>
</listitem>
</itemizedlist>
</para>
<para>
There are, however, some features which are not available:
<itemizedlist>
<listitem>
<para>
Work Offline (disconnected mode).
</para>
</listitem>
<listitem>
<para>
"Recall Message" function.
</para>
</listitem>
</itemizedlist>
</para>
</sect1>
<sect1 id="install">
<title>Installing the Connector</title>
<para>
To install the Evolution Connector, run Red Carpet by
selecting <menuchoice><guimenu>System</guimenu><guimenuitem>Get
Software</guimenuitem></menuchoice>. Subscribe to the Evolution
Connector for Microsoft Exchange channel, select the Evolution
Connector for Microsoft
Exchange2000, and click the
<guilabel>Install</guilabel> button. You can also install
the Connector by downloading the individual packages from
ftp.ximian.com if you wish.
</para>
</sect1>
<sect1 id="exchange-configure">
<title>Adding your Exchange Account in Novell Evolution</title>
<para>
Once you have installed the Connector, you need to set up access
for your Exchange account on both the
Exchange server and within Evolution.
</para>
<sect2 id="config-server">
<title>Exchange Server Settings</title>
<para>
Check with your system administrator to ensure that:
<itemizedlist>
<listitem>
<para>
You have a valid account on the Exchange server.
</para>
</listitem>
<listitem>
<para> You are permitted to access the account with
WebDAV. This is the default setting for the
Exchange server, so unless
your system administrator has specifically turned it
off, no changes should be necessary.
</para>
</listitem>
</itemizedlist>
</para>
<para>
The Novell website knowledge base, at <ulink type="http"
url="http://support.ximian.com">support.ximian.com</ulink>,
has additional information about checking to make sure that
your Exchange server will accept
connections from Novell Evolution.
</para>
</sect2>
<sect2 id="config-client">
<title>Standard Configuration Tool for Evolution Connector</title>
<para>
Once you know that your server is ready for you to connect,
you are ready to add your Exchange account to Evolution Connector.
</para>
<sect3 id="config-easy">
<title>Simple Configuration Tool for Evolution Connector</title>
<para>
Evolution Connector 1.4 comes with a simple account creation tool
for some installations. Other installations will require
the standard account tool described in <xref
linkend="config-client" /> below.
</para>
<para>
If you have no accounts configured,
the simple assistant will start when you start Novell
Evolution. It asks only for the name of your Outlook
Web Access server, and your username and password. Evolution
Connector will determine the remaining information on its own.
</para>
<para>
If the simple account tool does not run automatically, create
an account as described below.
</para>
</sect3>
<sect3 id="config-exchange-new-account">
<title>Creating a New Exchange Account</title>
<para>
If you would like to create a new account for your Exchange
server, select <menuchoice>
<guimenu>Tools</guimenu>
<guimenuitem>Mail Settings</guimenuitem>
</menuchoice>
from any mail view. Then click the <guilabel>Add</guilabel>
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 about any of the information you need, just ask your
system administrator.
</para>
<variablelist>
<varlistentry>
<term>Identity</term>
<listitem>
<para>Enter your name and email address. If you wish,
you may add your organization and the location of your
signature file. Only your name and email address are
required.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Receiving Mail</term>
<listitem>
<para>
In this step, you'll enter information about the way
you check mail:
<orderedlist>
<listitem>
<para>
First, select <guilabel>Microsoft
Exchange</guilabel> as your server type.
</para>
</listitem>
<listitem>
<para>
Enter the name of your Exchange email server, and
the user name you would use to log in to a
Windows workstation in your organization.
</para>
</listitem>
<listitem>
<para>
If you wish, select the box labeled
<guilabel>Use secure connection
(SSL)</guilabel>, to take advantage of a more
secure connection method. This may allow you to
connect to the server from outside your
firewall.
</para>
</listitem>
<listitem>
<para>
Select the kind of authentication your network
uses. You can click the <guilabel>Check for Supported
Types</guilabel> button to see which kinds will work.
</para>
</listitem>
<listitem>
<para>
If you would like Evolution to
remember your password, check the box labeled
<guilabel>Remember this password</guilabel>.
</para>
</listitem>
</orderedlist>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Receiving Mail, Step Two</term>
<listitem>
<para>There are a few additional options in this step:
<orderedlist>
<listitem>
<para>
Checking for New Mail: If you would like to
check for new mail automatically, click the
checkbox and enter an interval in minutes.
</para>
</listitem>
<listitem>
<para>
Global Address List/Active Directory: Enter the
name of your global catalog server (directory
server). This will allow you to use the Global
Address List (GAL). Normally,
Evolution will fetch
a maximum of 500 responses to any query, but you
may increase or decrease this number if you
wish. A lower number decreases load on the
server, and many servers will refuse to return
more than 1000 results, no matter how many you
ask for.
<note id="why-you-need-gal">
<title>The Global Catalog Server</title>
<para>
The Global Catalog server provides you with
access to the Global Address List,
free/busy information, and folder delegation
features. These may not work properly if you do
not have a Global Catalog server.
</para>
</note>
</para>
</listitem>
<listitem>
<para>
Exchange Server: There are two options here:
<itemizedlist>
<listitem>
<para>
Exchange mailbox name: Enter your exchange
mailbox name. The suggested value is
probably correct.
</para>
</listitem>
<listitem>
<para>
Outlook Web Access (OWA) Path: In most cases,
the URL for Outlook Web Access is
"http://server.company.com/exchange." If your
system has a URL that does not end in
"/exchange," enter the custom path here.
</para>
</listitem>
<listitem>
<para>
Public Folder Server: Enter the name of
your public folder server here.
</para>
</listitem>
</itemizedlist>
</para>
</listitem>
<listitem>
<para>
Apply filters to new messages in Inbox on this
server: Check this box to filter messages in
this account.
</para>
</listitem>
</orderedlist>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Sending Mail</term>
<listitem>
<para>Select <guilabel>Microsoft Exchange</guilabel> as
your email sending method. There is nothing else to do
in this step.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Account Management</term>
<listitem>
<para>Enter a name that you will use to remember this
account. "Exchange Account" is a good suggestion. Note
that you cannot have two accounts with the same name.
If you'd like to make this your default account for
sending email, check the <guilabel>Make this my default
account</guilabel> box.</para>
</listitem>
</varlistentry>
</variablelist>
<para>
You're done. Click <guilabel>Finish</guilabel> and
<guilabel>OK</guilabel>, then quit
Evolution and start it again. Now
you're ready to get to work on the Exchange server.
</para>
</sect3>
<sect3 id="config-exchange-existing-account">
<title>Changing an Existing Account to Work with Exchange</title>
<para>
If you have an existing email account, and want to convert it
to use for Exchange, select the account you want to convert
and click the <guilabel>Edit</guilabel> button. You'll want
to change settings in the following tabs of the account
dialog:
</para>
<figure>
<title>Exchange Account Settings: Identity</title>
<screenshot>
<screeninfo>Creating an Exchange Account, Step One: Identity</screeninfo>
<mediaobject><imageobject>
<imagedata format="PNG" fileref="figures/exchange-identity" srccredit="Aaron Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>
<variablelist>
<varlistentry>
<term>Identity</term>
<listitem>
<para>
If your email address will change because you are moving
to a new server, then change it in this tab. Otherwise,
move to the next tab.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Receiving Mail</term>
<listitem>
<para>
Select <guilabel>Microsoft Exchange</guilabel> as your
server type. Enter your name of your server next to
<guilabel>Host</guilabel>, and the user name for your
account next to <guilabel>Username</guilabel>. If your
server supports SSL (Secure Socket Layer) encryption, it
you can check the <guilabel>Use SSL</guilabel> box to
take advantage of more secure data transfers.
<figure>
<title>Exchange Account Settings: Receiving Mail</title>
<screenshot>
<screeninfo>Creating an Exchange Account, Step Two: Receiving Mail</screeninfo>
<mediaobject><imageobject>
<imagedata format="PNG" fileref="figures/exchange-receive" srccredit="Aaron Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Receiving Options</term>
<listitem>
<para>
Here, you'll find some additional settings:
<variablelist>
<varlistentry>
<term>Checking for New Mail</term>
<listitem>
<para>
Select whether you would like to check for
mail automatically, and if so, how often.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Global Address List/Active Directory</term>
<listitem>
<para>
The Global Address List (GAL) is an
address book for everyone represented in
your organization's Exchange deployment. To
use the GAL, click the tab labeled
<guilabel>Receiving Options</guilabel> and
enter the name of your Global Catalog
Server. The GAL is maintained by your
system administrator and you cannot add,
change, or remove items from it using
Novell Evolution. However, you can use it
to invite people to meetings and to look up
addresses and other information.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Exchange Server</term>
<listitem>
<para>
If your Exchange server requires you to use a
different mailbox name from the name you use to
log in, select the second check-box and enter
the mailbox name. Check with your system
administrator to be sure.
</para>
<para>
In most cases, the URL for web access is
"http://server.company.com/exchange." If your
system has a path that is not "exchange," check
the box and enter the custom path here.
</para>
<para>
If your network uses a different server
for Public Folders than for personal
folders, enter its name here.
</para>
</listitem>
</varlistentry>
</variablelist>
<figure>
<title>Exchange Account Settings: Receiving Mail</title>
<screenshot>
<screeninfo>Creating an Exchange Account, Step Three: Mail Options</screeninfo>
<mediaobject><imageobject>
<imagedata format="PNG" fileref="figures/exchange-receive-options" srccredit="Aaron Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Sending Mail</term>
<listitem>
<para>
If you will use your Exchange server to send as well as
receive mail, select <guilabel>Microsoft
Exchange</guilabel> as your server type, and enter the
server name as the <guilabel>Host</guilabel>.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
Once you have made those changes, click the
<guilabel>OK</guilabel> button.
</para>
<para>
Then, quit Evolution and start it
up again. Changes to the Evolution Connector accounts
configuration are not active until you have restarted the
application.
</para>
</sect3>
</sect2>
</sect1>
<sect1 id="access">
<title>Accessing the Exchange Server</title>
<para>
When you have installed the Connector, an
<guilabel>Exchange</guilabel> button is available in the shortcut
bar. The <guilabel>Exchange</guilabel> tool is used only to
access public folders and to perform certain Exchange actions
like delegation and password management. Use the regular
<guilabel>Mail</guilabel> tool for mail, the
<guilabel>Contacts</guilabel> tool for contacts, and the
<guilabel>Calendar</guilabel> tool for your schedule.
</para>
<note id="save-to-local-or-exchange">
<title>Saving Attached Addresses and Appointments</title>
<para>
If you are using both an Exchange account and a local mail
account, you should be aware that whenever you save an email
address or appointment from an email message, it will be
saved in your Exchange contacts list or calendar, rather
than in your local account. The same is true of
synchronization with Palm-OS devices: tasks, appointments,
and addresses from your Palm-OS device will be synchronized
with those in the Exchange folders rather than local
folders.
</para>
</note>
<tip id="gal-empty">
<title>The Global Address List Appears Empty At First</title>
<para>
To avoid unnecessary strain on the server, the GAL will
appear empty until you have searched for something in it.
If you want to display all the cards in the list, click in
the search box and press <keycap>Enter</keycap>. This
enters a blank search: since every card contains a blank in
it, every card will appear.
</para>
</tip>
</sect1>
<sect1 id="exchange-settings">
<title>Special Connector Only Settings</title>
<para>
There are two items in the Evolution preferences window that
are available only with Evolution Connector. The first is
delegation and permissions handling, and the second is the
creation of "Out of Office" messages.
</para>
<sect2 id="exchange-delegate">
<title>Access Delegation</title>
<para>
You can allow other people in your organization's Global
Address List to access your calendar, address
book, and messages, and they can let you manage theirs.
Delegation allows people to do anything from check on each
other's schedules to completely manage their personal
information.
</para>
<sect3 id="exchange-delegate-to-others">
<title>Delegating Access to Others</title>
<para>
To add someone to your list of delegates, click the
<guilabel>Add</guilabel> button and select them from the
Global Address List. When delegating you can grant different
levels of access to different types of data. You may also
decide whether the access you grant applies to items marked
<guilabel>Private</guilabel>, or only to public items.
</para>
<figure>
<title>Exchange Account Delegation</title>
<screenshot>
<screeninfo>Exchange Account Delegation Settings</screeninfo>
<mediaobject><imageobject>
<imagedata format="PNG" fileref="figures/exchange-delegation" srccredit="Aaron Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>
<para>
For each of the four types of folder, you may select one of
the following levels of access:
<variablelist>
<varlistentry>
<term>None</term>
<listitem>
<para>
Do not allow this person to access any folders of
this type.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Reviewer (read-only)</term>
<listitem>
<para>
Allow the person to see items in this type of
folder, but not create new items or edit existing
items.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Author (read, create)</term>
<listitem>
<para>
The delegate may view items in your folders, and may
create new items, but may not change any existing items.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Editor (read, create, edit)</term>
<listitem>
<para>
The delegate may view, create, and change items in
your folders.
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</sect3>
<sect3 id="exchange-delegated-to-you">
<title>Acting as a Delegate for Others</title>
<para>
To see the list of people who have granted you access to
their folders, click the <guilabel>Acting as a
Delegate</guilabel> tab in the Exchange Delegation settings
window. If you plan to send email on behalf of someone,
click the checkbox next to their name, and an email identity
will be created. You can then select that identity in the
<guilabel>From</guilabel> list in your message composer.
</para>
<para>
To access the folders delegated to you, do the following:
<orderedlist>
<listitem>
<para>
Select
<menuchoice>
<guimenu>File</guimenu>
<guimenuitem>Open Other User's Folder</guimenuitem>
</menuchoice>
</para>
</listitem>
<listitem>
<para>
Enter the email address of the user who
has delegated to you or click the
<guilabel>User</guilabel> button to select them from your
address book.
</para>
</listitem>
<listitem>
<para>
Select the folder you wish to open.
</para>
</listitem>
<listitem>
<para>
Click <guilabel>OK</guilabel>.
</para>
</listitem>
</orderedlist>
</para>
<para>
Folders delegated to you appear in your folder list inside a
folder labeled with the name of their owner. For example, if
Martha Thompson delegates folders to you, you will see a
folder called <guilabel>Martha Thompson's Folders</guilabel>
in the folder tree at the same level as your <guilabel>Personal
Folders</guilabel> and <guilabel>Public
Folders</guilabel>.
</para>
<note id="error">
<title>Error Messages</title>
<para>
If the folder fails to open properly, check with the
folder owner that you have been granted the correct access
permissions.
</para>
</note>
</sect3>
</sect2>
<sect2 id="exchange-out-of-office">
<title>Setting an Out of Office Message</title>
<para>
An <guilabel>Out of Office</guilabel> message is
an automatic reply that you can send to emails, explaining why
you aren't going to respond to their message. For example, if
you go on vacation for a week and will be away from email, you
can set an automatic reply so that people who write to you know
that you aren't ignoring them.
</para>
<para>
To create an <guilabel>Out of Office</guilabel> message,
select <menuchoice> <guimenu>Tools</guimenu>
<guimenuitem>Settings</guimenuitem>
</menuchoice> and then click the <guilabel>Out of
Office</guilabel> button.
</para>
<para>
Then, click <guilabel>I am currently
out of the office.</guilabel>. Then, enter a short message in
the text entry box. Click <guilabel>OK</guilabel>.
</para>
<para>
Your message will be sent automatically to
anyone who sends you mail until you return and click
<guilabel>I am currently in the office</guilabel>.
</para>
</sect2>
</sect1>
<sect1 id="full-advantage">
<title>Scheduling Appointments with Free/Busy</title>
<para>
When you schedule a meeting with your calendar on the
Exchange server, you can check when
other local Exchange users are busy according to their
Exchange calendars. To do so:
</para>
<figure>
<title>Scheduling With Free/Busy Information</title>
<screenshot>
<screeninfo>Using the Free/Busy Feature</screeninfo>
<mediaobject><imageobject>
<imagedata format="PNG" fileref="figures/schedule" srccredit="Aaron Weber"/>
</imageobject></mediaobject>
</screenshot>
</figure>
<note id="reminders-in-exchange">
<title>Reminders In Exchange</title>
<para>
Reminders for appointments in your Exchange calendar will
not work until you have run Evolution at least once after
logging in. This is different from locally stored reminders,
which will work from the moment you log in, regardless of
whether you have run Evolution in the session.
</para>
</note>
<orderedlist numeration="arabic">
<listitem>
<para>
Open a new appointment in the calendar.
</para>
</listitem>
<listitem>
<para> Choose <menuchoice> <guimenu>Actions</guimenu>
<guimenuitem>Schedule Meeting</guimenuitem>
</menuchoice> in the meeting editor window.
</para>
</listitem>
<listitem>
<para> Add attendees, either by entering their email
addresses into the list, or by clicking the
<guilabel>Invite Others</guilabel> button. If you choose
to so, it's best to use the Global Address List (GAL).
Choose the GAL from the drop-down list of address sources
at the top of the dialog box.
</para>
</listitem>
<listitem>
<para>
Choose <guilabel>Options</guilabel> and then
<guilabel>Update Free/Busy</guilabel> to check participant
schedules and, if possible, update the meeting in all
participants' calendars.
</para>
</listitem>
</orderedlist>
<tip id="autopick">
<title>Using Autopick to Adjust Meeting Times</title>
<para>
If meeting attendees are not available during the times you
have scheduled a meeting, you can "nudge" the meeting forward
or backward to the nearest available time. To do so, just
click the arrows to the left or right of the
<guilabel>Autopick</guilabel> button. The Autopick tool will
move the meeting to the nearest time during which all
attendees are available. If you aren't satisfied with those
results, you can drag the edges of the meeting time to the
hours that you want to select.
</para>
</tip>
</sect1>
</chapter>

1305
help/C/usage-mail-org.xml
View File

File diff suppressed because it is too large Load Diff

1908
help/C/usage-mail.xml
View File

File diff suppressed because it is too large Load Diff

1220
help/C/usage-mainwindow.xml
View File

File diff suppressed because it is too large Load Diff

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

@ -1,39 +0,0 @@
<chapter id="usage-sync">
<title>Synchronizing 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
Novell Evolution. 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 Novell
Evolution.
</para>
<para>
That's it.
</para>
</sect1>
</chapter>

26
help/ChangeLog
View File

@ -1,3 +1,29 @@
2004-09-13 Rodney Dawes <dobey@novell.com>
* xmldocs.make: Don't requires entities here
* C/Makefile.am: Add new figures to the list of images
Generate versioned xml/omf files based on $(BASE_VERSION)
Fix up CLEANFILES to include the stuff we generate
* C/POTFILES.in:
* C/apx-*.xml:
* C/config-*.xml:
* C/evolution-1.5-C.omf:
* C/evolution-1.5.xml:
* C/legal.xml:
* C/menuref.xml:
* C/preface.xml:
* C/topic.dat:
* C/usage-*.xml:
Remove all of these files from CVS
* C/evolution-C.omf:
* C/evolution.xml:
Add these files to replace the removed files above
* C/figure/*_a.(png|gif): Add new screenshots
2004-01-27 Aaron Weber <aaron@ximian.com>
* C/usage-mail-org.xml: spamfiltering
* C/usage-mail.xml: charsets and input methods.

4
help/es/ChangeLog
View File

@ -1,7 +1,3 @@
2004-09-02 Ismael Olea <ismael@olea.org>
* Merging with main tree for evo 2.0.
2003-12-02 Ismael Olea <ismael@olea.org>
* Updating Spanish translation into v1.4, work financed by

10
help/xmldocs.make
View File

@ -40,7 +40,7 @@
docdir = $(datadir)/gnome/help/$(docname)/$(lang)
# ************** You should not have to edit below this line *******************
xml_files = $(entities) $(docname).xml
xml_files = $(docname).xml
EXTRA_DIST = $(xml_files) $(omffile)
CLEANFILES = omf_timestamp
@ -50,10 +50,10 @@ include $(top_srcdir)/help/omf.make
all: omf
$(docname).xml: $(entities)
-ourdir=`pwd`; \
cd $(srcdir); \
cp $(entities) $$ourdir
#$(docname).xml: $(entities)
# -ourdir=`pwd`; \
# cd $(srcdir); \
# cp $(entities) $$ourdir
app-dist-hook:
if test "$(figdir)"; then \