diff options
Diffstat (limited to 'help/C')
| -rw-r--r-- | help/C/apx-authors.sgml | 70 | ||||
| -rw-r--r-- | help/C/apx-bugs.sgml | 19 | ||||
| -rw-r--r-- | help/C/apx-fdl.sgml | 678 | ||||
| -rw-r--r-- | help/C/config-prefs.sgml | 209 | ||||
| -rw-r--r-- | help/C/config-setupassist.sgml | 16 | ||||
| -rw-r--r-- | help/C/config-sync.sgml | 67 | ||||
| -rw-r--r-- | help/C/devel-action.sgml | 18 | ||||
| -rw-r--r-- | help/C/devel-component.sgml | 24 | ||||
| -rw-r--r-- | help/C/devel-script.sgml | 17 | ||||
| -rw-r--r-- | help/C/evo_book_0.1.sgml | 449 | ||||
| -rw-r--r-- | help/C/evolution-guide.sgml | 118 | ||||
| -rw-r--r-- | help/C/preface.sgml | 149 | ||||
| -rw-r--r-- | help/C/usage-calendar.sgml | 140 | ||||
| -rw-r--r-- | help/C/usage-contact.sgml | 283 | ||||
| -rw-r--r-- | help/C/usage-mail.sgml | 644 | ||||
| -rw-r--r-- | help/C/usage-mainwindow.sgml | 214 | ||||
| -rw-r--r-- | help/C/usage-setup.sgml | 46 | ||||
| -rw-r--r-- | help/C/usage-sync.sgml | 19 |
18 files changed, 2731 insertions, 449 deletions
diff --git a/help/C/apx-authors.sgml b/help/C/apx-authors.sgml new file mode 100644 index 0000000000..f68b395c9f --- /dev/null +++ b/help/C/apx-authors.sgml @@ -0,0 +1,70 @@ + + <appendix id="authors"> + <title>Authors</title> + <para> + <application>Evolution</application> was written by: + + Seth Alves: <email>alves@helixcode.com</email> + Anders Carlsson<email>andersca@helixcode.com</email> + Damon Chaplin:<email>damon@helixcode.com</email> + Clifford R. Conover <email>rusty@zootweb.com</email> + Miguel De Icaza: <email>miguel@helixcode.com</email> + Arturo Espinoza <email>arturo@nucleu.unam.mx</email> + Larry Ewing: <email>lewing@helixcode.com</email> + Bertrand Guiheneuf: <email>bertrand@helixcode.com</email> + Tuomas Kuosmanen: <email>tigert@gimp.org</email> + Christopher J. Lahey: <email>clahey@helixcode.com</email> + Matthew Loper: <email>matt@helixcode.com</email> + Dave Mason <email>dcm@redhat.com</email> + Federico Mena: <email>federico@helixcode.com</email> + Eskil Heyn Olsen<email>deity@eski.dk</email> + Nat Friedman: <email>nat@helixcode.com</email> + Ettore Perazzoli:<email>ettore@helixcode.com</email> + Russell Steinthal: <email>rms39@columbia.edu</email> + Peter Teichman: <email>peter@helixcode.com</email> + Chris Toshok: <email>toshok@helixcode.com</email> + Radek Doulik: <email>rodo@helixcode.com</email> + Dan Winship: <email>winship@helixcode.com</email> + Michael Zucchi: <email>notzed@helixcode.com</email> + +and other dedicated GNOME programmers. +</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> + For more information please visit the + <application>Evolution</application> <ulink + url="http://www.helixcode.com/apps/evolution.php3" + type="http">Web page</ulink>. Please send all comments, + suggestions, and bug reports to the <ulink + url="http://bugs.gnome.org" type="http">GNOME bug tracking + database</ulink>. Instructions for submitting bug reports can be + found on-line at <ulink + url="http://bugs.gnome.org/Reporting.html" type="http"> + http://bugs.gnome.org/Reporting.html</ulink>. If you are using + GNOME 1.1 or later, you can also use command + <command>bug-buddy</command> for submitting bug reports. + </para> + <para> + This manual was written by Aaron Weber + (<email>aaron@helixcode.com</email>) with the help of the + application programmers and the GNOME Documentation Project. + Please send all comments and suggestions regarding the manual to + the GNOME Documentation Project at + <email>docs@gnome.org</email>. You can also add your comments + online by using <ulink type="http" + url="http://www.gnome.org/gdp/doctable/">GNOME Documentation + Status Table</ulink>. + </para> + <!-- For translations: uncomment this: <para> Latin translation + was done by ME (<email>MYNAME@MYADDRESS</email>). Please send + all comments and suggestions regarding this translation to + SOMEWHERE. </para> --> + </appendix> diff --git a/help/C/apx-bugs.sgml b/help/C/apx-bugs.sgml new file mode 100644 index 0000000000..eb30901422 --- /dev/null +++ b/help/C/apx-bugs.sgml @@ -0,0 +1,19 @@ + <appendix id="bugs"> + + <title>Known bugs and limitations</title> + <abstract> + <para> + This appendix describes known bugs and limitations of + <application>Evolution</application>. Please contact the + Evolution team (<email>bugs@helixcode.com</email>) or use + <application>bug-buddy</application> if you find one we have not + listed, or if you have a patch to fix one. + </para> + </abstract> + + <para> + The bugs are many, but the application is young, and this is to + be expected. + </para> + </appendix> + diff --git a/help/C/apx-fdl.sgml b/help/C/apx-fdl.sgml new file mode 100644 index 0000000000..7a85c6e4a2 --- /dev/null +++ b/help/C/apx-fdl.sgml @@ -0,0 +1,678 @@ +<appendix id="fdl" label="Appendix - C"> + <title>GNU Free Documentation License</title> + <para> + Version 1.1, March 2000 + </para> + + <para> + Copyright © 2000 + <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> + + <variablelist> + <varlistentry id="fdl-preamble"> + <term>0. PREAMBLE</term> + <listitem> + <para> + The purpose of this License is to make a manual, textbook, or other + written document "free" in the sense of freedom: to assure everyone + the effective freedom to copy and redistribute it, with or without + modifying it, either commercially or noncommercially. Secondarily, + this License preserves for the author and publisher a way to get + credit for their work, while not being considered responsible for + modifications made by others. + </para> + + <para> + This License is a kind of "copyleft", which means that derivative + works of the document must themselves be free in the same sense. It + complements the GNU General Public License, which is a copyleft + license designed for free software. + </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> + </listitem> + </varlistentry> + <varlistentry id="fdl-section1"> + <term>1. APPLICABILITY AND DEFINITIONS</term> + <listitem> + <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 <link + linkend="fdl-document">"Document" </link>, below, refers to any such + manual or work. Any member of the public is a licensee, and is + addressed as "you". + </para> + + <para id="fdl-modified"> + A <link linkend="fdl-modified">"Modified Version"</link> 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 <link linkend="fdl-secondary">"Secondary Section"</link> 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 <link + linkend="fdl-document"> Document</link> to the <link + linkend="fdl-document"> Document's</link> overall subject (or to + related matters) and contains nothing that could fall directly within + that overall subject. (For example, if the <link + linkend="fdl-document">Document</link> is in part a textbook of + mathematics, a <link linkend="fdl-secondary">Secondary Section</link> + 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 <link linkend="fdl-invariant">"Invariant Sections"</link> are + certain <link linkend="fdl-secondary"> Secondary Sections</link> whose + titles are designated, as being those of <link + linkend="fdl-invariant">Invariant Sections</link>, 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 <link linkend="fdl-cover-texts">"Cover Texts"</link> are certain + short passages of text that are listed, as <link + linkend="fdl-cover-texts">Front-Cover Texts</link> or <link + linkend="fdl-cover-texts">Back-Cover Texts</link>, in the notice that + says that the <link linkend="fdl-document">Document</link> is released + under this License. + </para> + + <para id="fdl-transparent"> + A <link linkend="fdl-transparent">"Transparent"</link> 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 <link + linkend="fdl-transparent"> Transparent</link> file format whose markup + has been designed to thwart or discourage subsequent modification by + readers is not <link linkend="fdl-transparent">Transparent</link>. A + copy that is not <link linkend="fdl-transparent">"Transparent"</link> + is called "Opaque". + </para> + + <para> + Examples of suitable formats for <link + linkend="fdl-transparent">Transparent</link> 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 <link linkend="fdl-title-page">"Title Page"</link> 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, <link linkend="fdl-title-page"> "Title Page"</link> + means the text near the most prominent appearance of the work's title, + preceding the beginning of the body of the text. + </para> + </listitem> + </varlistentry> + + <varlistentry id="fdl-section2"> + <term>2. VERBATIM COPYING</term> + <listitem> + <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 <link linkend="fdl-document">Document</link> 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> + </listitem> + </varlistentry> + + <varlistentry id="fdl-section3"> + <term>3. COPYING IN QUANTITY</term> + <listitem> + <para> + If you publish printed copies of the <link + linkend="fdl-document">Document</link> numbering more than 100, and + the <link linkend="fdl-document">Document's</link> 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 <link linkend="fdl-cover-texts">Cover Texts</link>: 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 + <link linkend="fdl-transparent">Opaque</link> copy, or state in or + with each <link linkend="fdl-transparent">Opaque</link> copy a + publicly-accessible computer-network location containing a complete + <link linkend="fdl-transparent"> Transparent</link> copy of the <link + linkend="fdl-document">Document</link>, 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 <link linkend="fdl-transparent">Opaque</link> copies + in quantity, to ensure that this <link + linkend="fdl-transparent">Transparent</link> copy will remain thus + accessible at the stated location until at least one year after the + last time you distribute an <link + linkend="fdl-transparent">Opaque</link> 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 <link + linkend="fdl-document">Document</link>. + </para> + </listitem> + </varlistentry> + + <varlistentry id="fdl-section4"> + <term>4. MODIFICATIONS</term> + <listitem> + <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 <link linkend="fdl-modified">Modified Version</link> under + precisely this License, with the <link linkend="fdl-modified">Modified + Version</link> filling the role of the <link + linkend="fdl-document">Document</link>, thus licensing distribution + and modification of the <link linkend="fdl-modified">Modified + Version</link> to whoever possesses a copy of it. In addition, you + must do these things in the <link linkend="fdl-modified">Modified + Version</link>: + </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 <link + linkend="fdl-document">Document</link>). 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 "History", 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 "History" in the + <link linkend="fdl-document">Document</link>, create one stating + the title, year, authors, and publisher of the <link + linkend="fdl-document">Document</link> as given on its <link + linkend="fdl-title-page">Title Page</link>, then add an item + describing the <link linkend="fdl-modified">Modified + Version</link> 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 + <link linkend="fdl-document">Document</link>, and likewise the + network locations given in the <link + linkend="fdl-document">Document</link> for previous versions it + was based on. These may be placed in the "History" section. You + may omit a network location for a work that was published at + least four years before the <link + linkend="fdl-document">Document</link> 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 "Acknowledgements" or "Dedications", + 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 "Endorsements". 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 "Endorsements" 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 <link linkend="fdl-modified">Modified + Version's</link> license notice. These titles must be distinct from + any other section titles. + </para> + + <para> + You may add a section entitled "Endorsements", 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 + <link linkend="fdl-cover-texts">Front-Cover Text</link> and one of + <link linkend="fdl-cover-texts">Back-Cover Text</link> 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> + </listitem> + </varlistentry> + + <varlistentry id="fdl-section5"> + <term>5. COMBINING DOCUMENTS</term> + <listitem> + <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 <link + linkend="fdl-invariant">Invariant Sections</link> 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 <link linkend="fdl-invariant"> Invariant Sections</link> 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 <link linkend="fdl-invariant">Invariant Sections</link> in the + license notice of the combined work. + </para> + + <para> + In the combination, you must combine any sections entitled "History" + in the various original documents, forming one section entitled + "History"; likewise combine any sections entitled "Acknowledgements", + and any sections entitled "Dedications". You must delete all sections + entitled "Endorsements." + </para> + </listitem> + </varlistentry> + + <varlistentry id="fdl-section6"> + <term>6. COLLECTIONS OF DOCUMENTS</term> + <listitem> + <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 + distribute it individually under this License, provided you insert a + copy of this License into the extracted document, and follow this + License in all other respects regarding verbatim copying of that + document. + </para> + </listitem> + </varlistentry> + + <varlistentry id="fdl-section7"> + <term>7. AGGREGATION WITH INDEPENDENT WORKS</term> + <listitem> + <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 <link linkend="fdl-document"> Document</link>, + provided no compilation copyright is claimed for the compilation. + Such a compilation is called an "aggregate", and this License does not + apply to the other self-contained works thus compiled with the <link + linkend="fdl-document">Document</link> , on account of their being + thus compiled, if they are not themselves derivative works of the + <link linkend="fdl-document">Document</link>. 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 <link linkend="fdl-document">Document</link>, then if the <link + linkend="fdl-document">Document</link> is less than one quarter of the + entire aggregate, the <link linkend="fdl-document">Document's</link> + <link linkend="fdl-cover-texts">Cover Texts</link> may be placed on + covers that surround only the <link + linkend="fdl-document">Document</link> within the aggregate. Otherwise + they must appear on covers around the whole aggregate. + </para> + </listitem> + </varlistentry> + + <varlistentry id="fdl-section8"> + <term>8. TRANSLATION</term> + <listitem> + <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 <link + linkend="fdl-invariant">Invariant Sections</link> in addition to the + original versions of these <link linkend="fdl-invariant">Invariant + Sections</link>. 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> + </listitem> + </varlistentry> + + <varlistentry id="fdl-section9"> + <term>9. TERMINATION</term> + <listitem> + <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 <link linkend="fdl-document">Document</link> 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> + </listitem> + </varlistentry> + + <varlistentry id="fdl-section10"> + <term>10. FUTURE REVISIONS OF THIS LICENSE</term> + <listitem> + <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 "or any later + version" applies to it, you have the option of following the terms and + conditions either of that specified version or of any later version + that has been published (not as a draft) by the Free Software + Foundation. If the <link linkend="fdl-document">Document</link> 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> + </listitem> + </varlistentry> + + <varlistentry id="fdl-using"> + <term>Addendum</term> + <listitem> + <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> + + <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> + + <para> + If you have no <link linkend="fdl-invariant">Invariant + Sections</link>, write "with no Invariant Sections" instead of saying + which ones are invariant. If you have no <link + linkend="fdl-cover-texts">Front-Cover Texts</link>, write "no + Front-Cover Texts" instead of "Front-Cover Texts being LIST"; 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> + </listitem> + </varlistentry> + </variablelist> +</appendix>
\ No newline at end of file diff --git a/help/C/config-prefs.sgml b/help/C/config-prefs.sgml new file mode 100644 index 0000000000..67ca0e7577 --- /dev/null +++ b/help/C/config-prefs.sgml @@ -0,0 +1,209 @@ + + <chapter id="config-prefs"> + <title>Advanced Configuration with the Preferences Window</title> + <para> + If you prefer not to use the setup assistant, select + <guimenuitem>Preferences</guimenuitem> from the + <guimenu>Settings</guimenu> menu, and work your way through + the page tabs it offers you. They are: + <itemizedlist> + <listitem> + <para> + <guilabel>Identity</guilabel>, which allows you to set + your name, email address, and other information. The + default values are the ones found on your system account. + </para> + </listitem> + + <listitem> + <para> + <guilabel>Network</guilabel>, which allows you to + specify your network settings. There are no default + values for this information. + </para> + </listitem> + + <listitem> + <para> + <guilabel>Mail</guilabel>, which allows you to specify + attachment and HTML handling, forwarding behavior, + filters, and other <application>Evolution</application> + behaviors specific to email. The default behaviors are + those approved by Jamie Zawinski. + </para> + </listitem> + + <listitem> + <para> + <guilabel>Contacts</guilabel>, which allows you to + specify behavior that is specific to your contact + manager. + </para> + </listitem> + + <listitem> + <para> + <guilabel>Calendar</guilabel>, which allows you to set + the way that your calendar will behave and appear. The + default view is by week and the default calendar is + Western. Date format is determined by the system clock + and localization, and cannot be set here. + </para> + </listitem> + + <listitem> + <para> + <guilabel>General</guilabel>, which covers everything + else, including the <application>Evolution</application> + startup screen. + </para> + </listitem> + </itemizedlist> + + The <interface>Preferences Dialog</interface> is shown in + <xref linkend="config-prefs-fig">. + </para> + + <!-- ==============Figure===================== --> + <figure id="config-prefs-fig"> + <title>Preferences Dialog</title> + <screenshot> + <screeninfo>Preferences dialog</screeninfo> + <graphic fileref="evolution_config_pic" format="png" srccredit="Aaron Weber"> + </graphic> + </screenshot> + </figure> + <!-- ==============End of Figure================--> + + + <sect1 id="config-prefs-identity"> + <title>Identity Settings</title> + <para> + If you have only one email address, or use automatic + forwarding to funnel multiple addresses into one, then you + will only need to configure one identity. To create a single + user with a single identity, enter the following information: + (INSERT detailed DESCRIPTION HERE) + </para> + + <para> + If you have one email accout for your personal life, and one + for work, you'll want to create multiple identities. You + can do this by: (INSERT DESCRIPTION HERE) + </para> + + <note id="config-prefs-identity-note"> + <title>Multiple Identities and Network Settings</title> + <para> + If you use multiple network connections—if, for + example, you dial up an ISP for your personal mail, and use + a LAN for your work-related tasks— you will also have + to set seperate network settings for each identity. + </para> + </note> + </sect1> + + <sect1 id="config-prefs-network"> + <title>Setting up the Network</title> + <para> + In order to do much of anything with + <application>Evolution</application>, you need to connect to + your network. To do that, you'll need to know your user name + and password, what sort of mail sending and receiving + protocols your network uses, and the names of the servers + you'll be using. If you're switching from another groupware + or email progam, you can almost certainly use the same + settings as you did with that program. Select the + <guibutton>Network</guibutton> tab in the + <interface>Preferences</interface> window to get started. + </para> + + <sect2 id="config-prefs-network-advanced"> + <title>Advanced Network Configuration</title> + <para> + INSERT a little introduction paragraph here. + </para> + <sect3 id="config-prefs-network-advanced-multiconnect"> + <title>Multiple Network Connections</title> + <para> + People with who use multiple ISP's or networks, or who + have multiple email accounts, will need to do a little + more work, but not much. + </para> + <example> + <title>Multiple Identities and Networks</title> + <para> + Nate's laptop goes everywhere with him, and he needs + to be able to use <application>Evolution</application> + from anywhere&mdash a hotel room, an airplane, a + client's office, his office, anywhere at all. (INSERT + HOW EVOLUTION HELPS HIM DO THIS). + </para> + </example> + + <para> + (INSERT DESCRIPTION OF WHAT THESE THINGS ARE AND HOW TO + USE THEM) (I'M THINKING IN TERMS OF THE APPLE LOCATION + MANAGER) (Kill this section if Evolution doesn't support + this for 1.0). + </para> + </sect3> + + <sect3 id="config-prefs-network-advanced-other"> + <title>Other Advanced Network Settings</title> + <para> + I can't think of any at the moment but i'm sure they're + out there. They belong here. + </para> + </sect3> + </sect2> + </sect1> + <sect1 id="config-prefs-mail"> + <title>Modifying the Mail</title> + <para> + This section discusses mail-specific preferences. Click on + the <guibutton>Mail</guibutton> tab in the + <interface>Preferences</interface> window to access these + settings. + </para> + <para> + You can set the following options: <!--insert variable list here--> + </para> + </sect1> + + <sect1 id="config-prefs-contact"> + <title>Managing the Contact Manager</title> + <para> + To set the behavior of your Contact Manager, click on the + <guibutton>Contact Manager</guibutton> tab in the + <interface>Preferences</interface> window. + </para> + <para> + You can set the following options: <!--insert variable list + here--> + </para> + </sect1> + + <sect1 id="config-prefs-cal"> + <title>Configuring the Calendar</title> + <para> + This section discusses calendar-specific preferences. Click + on the <guibutton>Calendar</guibutton> tab in the + <interface>Preferences</interface> window to access these + settings. + </para> + <para> + You can set the following options: <!--insert variable list + here--> + </para> + </sect1> + + + <sect1 id="config-prefs-general"> + <title>General Preferences</title> + <para> + Overall Evolution prefs-- whatever else doesn't fit. + </para> + </sect1> + </chapter> +
\ No newline at end of file diff --git a/help/C/config-setupassist.sgml b/help/C/config-setupassist.sgml new file mode 100644 index 0000000000..03b85ea12c --- /dev/null +++ b/help/C/config-setupassist.sgml @@ -0,0 +1,16 @@ + + <chapter id="config-setupassist"> + <title>Easy Setup with the Setup Assistant</title> + <para> + The setup assistant can gather most of the information + necessary for <application>Evolution</application>'s daily + operation. If you chose not to use it the first time you ran + <application>Evolution</application>, you can run it again by + doing SOMETHING HERE. + </para> + <para> + This paragraph will describe all information required by the + setup assistant. It will include a long itemized list, and a + screenshot or two. + </para> + </chapter> diff --git a/help/C/config-sync.sgml b/help/C/config-sync.sgml new file mode 100644 index 0000000000..ae78a6daaf --- /dev/null +++ b/help/C/config-sync.sgml @@ -0,0 +1,67 @@ + <chapter id="config-sync"> + + <!-- THIS ENTIRE CHAPTER MAY BE DELETED --> + + <title>Setting up your synchronization system</title> + <para> + Synchronization presents you with two issues you'll need to + deal with. The first one is pretty simple: you'll need to get + the data to move among the various devices you're using. If + you've already got <application>Gnome-Pilot</application> + working, then all you have to do is tell it to use Evolution + as a conduit. If you haven't used + <application>Gnome-Pilot</application> before, you'll need to + run the GNOME <application>Control Center</application> and go + through the hand-held device setup assistant. Then you can + create the Evolution conduit and press the hotsync button. + </para> + <para> + If that doesn't work, jump up and down several times and swear + loudly. Then make sure you've got + <application>Gnome-Pilot</application> going to the right + device (for my serial port, it's /dev/ttys0, not the default + /dev/pilot) and that you have read and write permission on + that device. If you don't you'll need to be added to whatever + group has those permissions (for my system, it's tty). + Alternately, if you're the only user of your computer and + don't care too much about security, just use + <command>su</command> to become root, and then use + <command>chmod a+rw /dev/[DEVICENAME]</command> to set + universal read and write permissions on that port— just + don't tell your sysadmin I said you could. (Sysadmins, of + course, would never do such a thing.) + </para> + <para> + Once <application>Evolution</application> knows where to get + the mail, address, and calendar data, it needs to know what to + do with it. When you synchronize your local data with the data on + a server or handheld device, you may run into conflicts: + perhaps you have ended up with two cards with the same name + and different addresses, or old mail that has been deleted + from one device but not the other. What if you want to keep + only the most recent mail on your hand-held or your laptop, + but all the mail on the LDAP server or your desktop machine? + Select the <guibutton>Synchronization</guibutton> tab from the + <interface>Preferences</interface> window to set up the + conflict resolution preferences. + </para> + <para> + You can set <application>Evolution</application>'s + synchronization behavior in the following ways: + <!-- LIST HERE --> + </para> + <para> + <warning> + <title>Data Loss Prevention</title> + <para> + It's always a good idea to make a backup. If you set your + synchronization behaviors wrong, you could end up deleting + the messages and cards you want to keep, and keeping the + ones you want to delete. Before you change these + preferences, make a backup of your + <application>Evolution</application> files. You can do + this by... <!--DESCRIBE HERE --> + </para> + </warning> + </para> + </chapter> diff --git a/help/C/devel-action.sgml b/help/C/devel-action.sgml new file mode 100644 index 0000000000..5d40c78bf7 --- /dev/null +++ b/help/C/devel-action.sgml @@ -0,0 +1,18 @@ + + <chapter id="devel-actions"> + <title>Actions: Making Evolution Behave</title> + <sect1 id="devel-actions-build"> + <title>Build Actions</title> + <para> + How to create an action. + </para> + </sect1> + + <sect1 id="devel-actions-use"> + <title>Using Actions</title> + <para> + How to use an action you or someone else has built. + </para> + </sect1> + </chapter> +
\ No newline at end of file diff --git a/help/C/devel-component.sgml b/help/C/devel-component.sgml new file mode 100644 index 0000000000..db4f93c27d --- /dev/null +++ b/help/C/devel-component.sgml @@ -0,0 +1,24 @@ + + <chapter id="devel-component"> + <title>Evolution Components</title> + <subtitle> Build your own species </subtitle> + <para> + Explain exactly what an Evolution Component is. + </para> + + <sect1 id="devel-component-build"> + <title>Building Evolution Components</title> + <para> + Explain how to build them-- what resources are available, + what interfaces exposed. + </para> + </sect1> + + <sect1 id="devel-component-use"> + <title>Using Additional Evolution Components</title> + <para> + Once you've got one--either you've built it or borrowed it-- + you can use it. Here's how. + </para> + </sect1> + </chapter>
\ No newline at end of file diff --git a/help/C/devel-script.sgml b/help/C/devel-script.sgml new file mode 100644 index 0000000000..74dbf161cd --- /dev/null +++ b/help/C/devel-script.sgml @@ -0,0 +1,17 @@ + + <chapter id="devel-scripts" > + <title>Scripting: Making Evolution Sit up and Beg</title> + <sect1 id="devel-scripts-build"> + <title>Writing Scripts</title> + <para> + How to write scripts for Evolution. + </para> + </sect1> + + <sect1 id="devel-scripts-use"> + <title>Using Scripts</title> + <para> + How to use and install scripts for Evolution. + </para> + </sect1> + </chapter> diff --git a/help/C/evo_book_0.1.sgml b/help/C/evo_book_0.1.sgml deleted file mode 100644 index 357da80224..0000000000 --- a/help/C/evo_book_0.1.sgml +++ /dev/null @@ -1,449 +0,0 @@ -<!DOCTYPE book PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.0//EN"> - -<book> -<bookinfo> - <title>Evolution Users Guide</title> - <author><firstname>Aaron</firstname><surname>Weber</surname></author> - <copyright><year>2000</year><holder>Aaron Weber and Helix Code, inc.</holder></copyright> - - <legalnotice> -PUT THE RIGHT LEGALNOTICE IN HERE - - <para> Windows, Exchange, and Outlook are trademarks of Microsoft Corp.</para> - <para> Lotus and Lotus Notes are trademarks of The Louts Corporation.</para> - <para> Macintosh and Apple are trademarks of Apple Computer, Inc.</para> - <para> All other trademarks are property of their respective owners.</para> - </legalnotice> - - <releaseinfo> - This is version 0.0 of Evolution manual. - </releaseinfo> <!-- this is version of manual, not application --> - -</bookinfo> - -<preface> -<!-- =============Introduction ============================= --> - <title>Introduction</title> - - <section> <title> What is Evolution?</title> - <para> - <application>Evolution</application> is a suite of groupware applications - for mail, contact management, and calendaring. It is - included in the package <filename>Evolution</filename>, which is a - part of the GNOME desktop environment. This document describes - version &version; of <application>Evolution</application> - </para> - - <para> - What that means is that Evolution is your personal secretary. It can keep track of - memos, emails, - and appointments for you and for everyone in your office. - </para> - - <para><application>Evolution</application> can be started by - selecting <guimenuitem>Evolution</guimenuitem> from - <guisubmenu>SUBMENU</guisubmenu> submenu of the <guimenu>Main - Menu</guimenu>, or by running the command - <command>evolution</command> on the commandline. - </para> - - -</preface> - -<part id="usage"> -<title>Using Evolution</title> - - <partintro> - <para> - As was said before, <application>Evolution</application> can be - used to send and recieve email, manage address and other contact information, - and maintain This section describes basic usage of - <application>Evolution</application> in each of those functions. As with most of Linux, - there's more than one way to do things, and you should pick whichever one strikes you as most - appropriate. - </para> - </partintro> - - - <chapter id="basics"> - <title>Basic usage</title> - <para> - When you first start <application>Evolution</application>, you see - the <interface>Main window</interface>, as shown in - <xref linkend="mainshot">the following figure. - From there, you should select which features you wish to - use by clicking on their icons in the left-hand navigational column. - The Mail features can be accessed by clicking on the <guibutton>Mail</guibutton>, - and likewise for other features. -<!-- ==============Figure=================================== --> - <figure id="mainshot"> - <title>Evolution Main Window</title> - <screenshot> - <screeninfo>Evolution Main Window</screeninfo> - <graphic fileref="SCREENSHOT" format="png" - srccredit="Aaron Weber"> - </graphic> - </screenshot> - </figure> -<!-- ==============End of Figure=================================== --> - </para> - - </chapter> - - <chapter id="mailer"> - <title>The Evolution Mailer</title> - <abstract> - <para> - This chapter covers the use of the Evolution Mailer. - Configuration of the mail client is discussed in <xref linkend="customization">. - If you are already accustomed to other email programs, - you can probably skip the mail sending and checking sections. - The more complex functions, such as filtering, organizing, and searching mail, - have some features that are not found in other email programs, and - even power users may wish to review these sections of the guide. - <!--those function descr's should be xrefs to sections of the chapter--> - </para> - </abstract> - - <sect1 id="mailsending"> - <title>Sending and Recieving Mail</title> - <para> - You can start writing a new email message by selecting <guimenuitem>New Mail</guimenuitem> from - the <guimenu>FilMenu</guimenu>, or by pressing <KeyCombo>NEW-MESSAGE-COMBO</KeyCombo>. - When you do so, the <interface>New Message</interface> window will open, as shown in - <xref linkend="evolution-newmsg">. - - -<!-- ==============Figure=================================== --> - <figure id="evolution-newmsg"> - <title>New Message Window</title> - <screenshot> - <screeninfo>Evolution Main Window</screeninfo> - <graphic fileref="evolution_newmsg" format="png" - srccredit="Aaron Weber"> - </graphic> - </screenshot> - </figure> -<!-- ==============End of Figure=================================== --> - - </para> - - <para> - You can pick recipients in several ways: - The <guilabel>TO:</guilabel> field is for the primary recipients of the message your are going to send. - It is considered bad form to have more than a few email addresses in this form. - </para> - <para> - If you want to send a copy of the message to someone, you may also use the <guilabel>Cc:</guilabel> field. - "Cc" stands for "Carbon Copy"-- Those people will recieve a copy of the message. They will see - the rest of the message list, and are noted as secondary recipients of the message. - </para> - - <para> - If you have a large number of recipients, or if you want to send mail to several people without - telling them that it's gone to multiple people, you should use <guilabel>BCC.</guilabel> BCC stands - for "Blind Carbon Copy". Addresses entered into this field will recieve the message - but the message headers will not see the rest of the recipient list. - </para> - - <para> - Enter a subject into the <guilabel>Subject:</guilabel> field. - - Enter the text of your message into the <guilabel>Message:</guilabel> text area. - </para> - - <para> - If you want to attach a document to your email message, you can do so by - <!--describe process here-->. If the people you are sending a message to - can read HTML mail, you can embed an image into the mail. Otherwise, - it's best to attach images, just like other documents. Be aware that a large - attachment will take a long time to download. - </para> - - - <para> - Click <guibutton>Send</guibutton> or press <KeyCombo>SENDCOMBO</KeyCombo> to send the mail. - </para> - <tip> - <title>Send Now, Send Later</title> - <para> - Evolution will send mail immediately unless you set it to do so otherwise. It also checks for - new mail every time you send mail. If you - want, however, you can queue your messages to be sent at a later time, and also set your - preferences to check mail on a regular basis, and alert you whenever it finds new messages. - I like to use "Send Later" because it gives me a chance change my mind about a message - before it goes out, and I have Evolution set to check my mail every ten minutes, and beep - when I get mail that it thinks isn't spam. - Use the <interface>Mail Preferences</interface> to specify message queue and filter behavior. - Preferences are discussed in <xref linkend="customization">. - </para> - </tip> - </sect1> - - <sect1 id="mail-sorting"> - <title>Organizing Your Mail</title> - - <para> - If you only get a few messages a day, you probably don't need to to sort or organize them. When you get several hundred each day, - and when you want to refer to a message you've recieved six weeks ago, you want a real - organizing system. This section will cover the mail sorting and organization: folders, searches, vFolders, and filters. - <!--those last items should be links--> - - <sect2 id="mail_folders"> - <para> - You can create new folders by selecting <guimenuitem>ITEM</guimenuitem> from the <guimenu>MENU</guimenu>, or by - pressing <KeyCombo>SENDCOMBO</KeyCombo>. Move mail to them by selecting <guimenuitem>ITEM</guimenuitem> from the - <guimenu>MENU</guimenu>, or by pressing <KeyCombo>SENDCOMBO</KeyCombo>. An email message can be in only one folder at a time, - just like real mail in real folders. If you forget where an email is, you can search for it. If you find that you want - an email to be in several places at once, you should consider creating a vFolder, or virtual folder. - <para> - </sect2> - - <sect2 id="mail_searching"> - <para> - Because Evolution automatically creates an index of every email you recieve, it can search through your old - messages and present you with the results in short order. - <!--describe the way one creates a search and so forth.--> - </para> - - <para> - If you find yourself performing a search frequently, you can save it as vFolder. - </para> - </sect2> - - <sect2 id="mail_vFolders"> - <para> - Virtual Folders, or vFolders, are one of the more advanced features of <application>Evolution</application>. If they confuse you, - you don't have to use them. However, if you get a lot of mail, and find yourself referring to messages, looking for old email, - or just living in your email client, you'll probably want to use them. - Basically, a vFolder is a saved search, which you can access the same way you would a normmal folder. - There are several important differences between the two, however, which come from the fact that a conventional - folder actually contains a message, but a virtual folder is really a different view of all your email. This means that - while a message can be in several vFolders, it can be in only one conventional folder. Also, - you cannot add or delete a message from a vFolder, and when you delete a message from a conventional folder, - it will disappear from all your vFolders--a search can't find a deleted message. - </para> - </sect2> - - <example><title>Using vFolders</title> - <para> - I have a vFolder set up for all the mail about a project I'm - working on, and another one for all the mail from my friend Bernie. - If Bernie sends me mail about the project, I can see that message both in the "Bernie" folder and in the "Project" folder. - That's because when I open up the "Bernie" folder, I'm really performing a search for all the mail from Bernie, and when you open the - "Project" folder you're really performing a search for all the mail about the project. That particular message - actually resides in some other folder, - maybe just in my Inbox. I can't delete it from the vFolder, because the vFolder is really a different view of my messages. - When I delete it from - the Inbox, I have also removed it from all my vFolders, because no search can find a deleted message. - <!--this could use a cool picture of the Inbox and 2 vFolders with the message in all 3--> - </para> - </example> - - - <sect2 id="mail_filters"> - <para> - Filters sort your email for you, automatically. You can access the Filter functions of - the email client by <!--BLAH BLAH BLAH-->. - </para> - - <para> - Email starts in your Inbox. As it arrives, it is indexed and filtered from ther. Any email - that does not meet filter action criteria remains in the Inbox. To create a filter, - <!--open the menu somehow-->f you have filters enabled, - </para> - </sect2> - </chapter> - - <chapter id="calendar"> - <title>Using the Calendar</title> - <para>To begin using the calendar, select <guibutton>Calendar</guibutton> - from the main navigational frame. This will cause the calendar component of - <application>Evolution</application> to become active. This is illustrated in - the figure below: -<!-- ==============Figure=================================== --> - <figure id="contact_picture"> - <title>Evolution Contact Manager Window</title> - <screenshot> - <screeninfo>Evolution Contact Manager Window</screeninfo> - <graphic fileref="SCREENSHOT" format="png" - srccredit="ME"> - </graphic> - </screenshot> - </figure> -<!-- ==============End of Figure=================================== --> -</para> - - - - </chapter> - <chapter id="addressbook"> - -</chapter> - -<chapter> -<title>Administration and Large-scale setup</title> -</chapter> - -</part><!--end of part two, Administration and Large-Scale Setup--> - - - <appendix> ... </appendix> - <appendix> ... </appendix> -<index> ... </index> -</book> - - -</chapter> - -<chapter> -<title>Administration and Large-scale setup</title> -</chapter> - -</part><!--end of part two, Administration and Large-Scale Setup--> - - - <appendix> ... </appendix> - <appendix> ... </appendix> -<index> ... </index> -</book> - - - - </chapter> - - -</part> <!--end of part one--> - -<part id="configuration"> -<title>Configuring Evolution</title> - -<chapter> -<title>The Preferences Dialog</title> - - <para> - To change default settings, select - <guimenuitem>Preferences</guimenuitem> command in - <guimenu>Settings</guimenu> menu. This launches the - <interface>Preferences dialog</interface>, shown in <xref - linkend="shot2">. - </para> -<!-- ==============Figure=================================== --> - <figure id="shot2"> - <title>Preferences Dialog</title> - <screenshot> - <screeninfo>Preferences dialog</screeninfo> - <graphic fileref="SCREENSHOT" format="png" - srccredit="ME"> - </graphic> - </screenshot> - </figure> -<!-- ==============End of Figure=================================== --> - -<!--obviously there should be more description here.--> - -</chapter> - -<chapter> -<title>Administration and Large-scale setup</title> -</chapter> - -</part><!--end of part two, Administration and Large-Scale Setup--> - - - -<!-- =============APPENDICES============================= --> - <appendix id="bugs"> - - <title>Known bugs and limitations</title> - <abstract> - <para> - This appendix describes known bugs and limitations of - <application>Evolution</application>. Please - contact the appropriate people if you find one we have not listed, - or if you have a patch to fix one. - <para> - </abstract> - - <para> - The program currently does not work. At all. - </para> - </appendix> - - - -<!-- =============Another Appendix============================= --> - - <appendix id="authors"> - <title>Authors</title> - <para> - <application>Evolution</application> was written by: - - Seth Alves: <email>alves@helixcode.com</email> - Anders Carlsson<email>andersca@helixcode.com</email> - Damon Chaplin:<email>damon@helixcode.com</email> - Clifford R. Conover <email>rusty@zootweb.com</email> - Miguel De Icaza: <email>miguel@helixcode.com</email> - Arturo Espinoza <email>arturo@nucleu.unam.mx</email> - Larry Ewing: <email>lewing@helixcode.com</email> - Bertrand Guiheneuf: <email>bertrand@helixcode.com</email> - Tuomas Kuosmanen: <email>tigert@gimp.org</email> - Christopher J. Lahey: <email>clahey@helixcode.com</email> - Matthew Loper: <email>matt@helixcode.com</email> - Dave Mason <email>dcm@redhat.com</email> - Federico Mena: <email>federico@helixcode.com</email> - Eskil Heyn Olsen<email>deity@eski.dk</email> - Nat Friedman: <email>nat@helixcode.com</email> - Ettore Perazzoli:<email>ettore@helixcode.com</email> - Russell Steinthal: <email>rms39@columbia.edu</email> - Peter Teichman: <email>peter@helixcode.com</email> - Chris Toshok: <email>toshok@helixcode.com</email> - Radek Doulik: <email>rodo@helixcode.com</email> - Dan Winship: <email>winship@helixcode.com</email> - Michael Zucchi: <email>notzed@helixcode.com</email> - -and other dedicated GNOME programmers. -</para> - <para> - The<application>Evolution</application> code owes a great debt to - <application>GNOME-pim</application>, <application>KHTMLW</application> - and the developers of <application>Evolution</application> acknowledge the efforts and contributions of its members. - </para> - - <para> - For more information please visit <application>Evolution</application> <ulink - url="http://www.helixcode.com/apps/evolution.php3" type="http">Web page</ulink>. - Please send all comments, suggestions, and bug reports to the - <ulink url="http://bugs.gnome.org" type="http">GNOME bug - tracking database</ulink>. Instructions for submitting bug reports - can be found on-line at <ulink - url="http://bugs.gnome.org/Reporting.html" type="http"> - http://bugs.gnome.org/Reporting.html</ulink>. If you are using GNOME - 1.1 or later, you can also use command - <command>bug-buddy</command> for submitting bug reports. - </para> - <para> - This manual was written by Aaron Weber - (<email>aaron@helixcode.com</email>) with the help of the application programmers. - Please send all comments - and suggestions regarding the manual to the GNOME Documentation - Project at <email>docs@gnome.org</email>. You can also add your - comments online by using <ulink type="http" - url="http://www.gnome.org/gdp/doctable/">GNOME Documentation - Status Table</ulink>. - </para> - <!-- For translations: uncomment this: - <para> Latin translation was done by ME - (<email>MYNAME@MYADDRESS</email>). Please send all comments - and suggestions regarding this translation to SOMEWHERE. - </para> - --> - </appendix> - - - <appendix> ... </appendix> - <appendix> ... </appendix> -<index> ... </index> -</book> - - diff --git a/help/C/evolution-guide.sgml b/help/C/evolution-guide.sgml new file mode 100644 index 0000000000..3e6b374fca --- /dev/null +++ b/help/C/evolution-guide.sgml @@ -0,0 +1,118 @@ +<!DOCTYPE Book PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"[ + +<!ENTITY PREFACE SYSTEM "preface.sgml"> +<!ENTITY USAGE-SETUP SYSTEM "usage-setup.sgml"> +<!ENTITY USAGE-MAINWINDOW SYSTEM "usage-mainwindow.sgml"> +<!ENTITY USAGE-MAIL SYSTEM "usage-mail.sgml"> +<!ENTITY USAGE-CONTACT SYSTEM "usage-contact.sgml"> +<!ENTITY USAGE-CALENDAR SYSTEM "usage-calendar.sgml"> +<!ENTITY USAGE-SYNC SYSTEM "usage-sync.sgml"> +<!ENTITY CONFIG-SETUPASSIST SYSTEM "config-setupassist.sgml"> +<!ENTITY CONFIG-PREFS SYSTEM "config-prefs.sgml"> +<!ENTITY CONFIG-SYNC SYSTEM "config-sync.sgml"> +<!ENTITY DEVEL-ACTION SYSTEM "devel-action.sgml"> +<!ENTITY DEVEL-SCRIPT SYSTEM "devel-script.sgml"> +<!ENTITY DEVEL-COMPONENT SYSTEM "devel-component.sgml"> +<!ENTITY APX-BUGS SYSTEM "apx-bugs.sgml"> +<!ENTITY APX-AUTHORS SYSTEM "apx-authors.sgml"> +<!ENTITY APX-FDL SYSTEM "apx-fdl.sgml"> +]> + + +<!-- Almost every chapter is an entity. Files, Chapter id's, and entity names correspond. APX is for appendix. --> +<book id="index"> + <bookinfo> + <title>A User's Guide to Evolution</title> + <author><firstname>Aaron</firstname><surname>Weber</surname></author> + <copyright><year>2000</year><holder>Helix Code, Inc.</holder></copyright> + + <legalnotice> + <para> + PUT THE RIGHT LEGALNOTICE IN HERE + </para> + </legalnotice> + + <releaseinfo> + This is version 0.4 of the Evolution manual. + </releaseinfo> + <!-- this is version of manual, not application --> + +<!-- ########## TO DO LIST: ########### --> + <!-- +finish content. +standardize capitalization/formatting of titles, interface and +component names. +standardize spelling of buzzwords & techterms like email +add glossterms and glossary +standardize on second person, not 1st pers. plural. +--> + + </bookinfo> + + &PREFACE; + + <part id="usage"> + <title>Using Evolution</title> + <subtitle>A Guide for Everybody</subtitle> + <partintro> + <para> + Part one of the <application>Evolution</application> manual + describes how to use <application>Evolution</application> + for email, contact management, and appointment and task + scheduling. You'll find as you go along that, as with most of + Linux, there's more than one way to do things, and you can + pick whichever method you like best. + </para> + </partintro> + + &USAGE-SETUP; + &USAGE-MAINWINDOW; + &USAGE-MAIL; + &USAGE-CONTACT; + &USAGE-CALENDAR; + &USAGE-SYNC; + + </part> + <part id="config"> + <title>Configuring and Managing Evolution</title> + <subtitle>A guide for Power Users and Administrators</subtitle> + <partintro> + <para> + <application>Evolution</application> is highly configurable. + Usually, when developers say that, they mean that they didn't + test it out thoroughly and have left it to other hackers to + "configure" themselves a working system. When we say + configurable, we mean that although + <application>Evolution</application> will work perfectly well + with minimal setup hassle, you can alter its behavior to fit + your needs with just a little more work. + </para> + </partintro> + + &CONFIG-SETUPASSIST; + &CONFIG-PREFS; + &CONFIG-SYNC; + </part> + <part id="devel"> + <title>Developing for Evolution</title> + <subtitle>An Introduction for the Happy Few</subtitle> + <partintro> + <para> + There are three levels of developing for + <application>Evolution</application>. You can write actions. + You can write scripts. And you can write full-fledged + Evolution components. INSERT CONTENT: paragraph should describe the + differences. + </para> + </partintro> + + &DEVEL-ACTION; + &DEVEL-SCRIPT; + &DEVEL-COMPONENT; + </part> + + &APX-BUGS; + &APX-AUTHORS; + &APX-FDL; + +</book> diff --git a/help/C/preface.sgml b/help/C/preface.sgml new file mode 100644 index 0000000000..05129eb550 --- /dev/null +++ b/help/C/preface.sgml @@ -0,0 +1,149 @@ + + <preface id="introduction"> +<!-- =============Introduction ============================= --> + <title>Introduction</title> + + <section id="what"> + <title> What is Evolution, and What Can It Do for Me?</title> + <para> + The idea of evolution as a process of improvement and + development is a strong influence on the developers at Helix + Code. We named our <glossterm>groupware</glossterm> suite + "Evolution" because we knew that it would be able to survive + in the wilderness of the software marketplace for one reason: + it's better. + </para> + <para> + <application>Evolution</application> is a suite of groupware + applications within the GNOME desktop environment that you can + use to send, receive, and organize email, manage address and + other contact information, and maintain a calendar. It + enables you to do those things on one or several computers, + connected directly or over a network, for one person or for + large groups. <application>Evolution</application> can handle + almost all your communications tasks with the power and + flexibility of the GNOME desktop environment. + </para> + <para> + We built <application>Evolution</application> with three groups of + people in mind: everyday users, system administrators, and + developers. + + <itemizedlist> + <listitem> + <para> + For <emphasis>everyday users</emphasis>, we made + <application>Evolution</application> easy to use without + sacrificing power. We made the interface familiar and + intuitive, but also allowed users to customize it to + their liking. We made the setup and configuration as + easy as possible. For any confusion, we wrote a + comprehensive manual and help system. + </para> + </listitem> + <listitem> + <para> + For <emphasis>administrators</emphasis>, we made sure + <application>Evolution</application> met and and + exceeded the standards set by currently available + groupware products, and we developed support for most + major network protocols so that it can integrate + seamlessly with existing hardware and network + environments. All of our efforts have made + <application>Evolution</application> both easy to use + and easy to support. + </para> + </listitem> + <listitem> + <para> + For <emphasis>developers</emphasis>, we built in + support for open standards and protocols to turn + <application>Evolution</application> into an advanced + development platform. From the simplest scripting to + the most complex network and component programming, + <application>Evolution</application> offers developers + the ideal environment for cutting-edge application + development. + </para> + </listitem> + <listitem> + <para> + For all three groups, we did our best to ensure the + safety of data. + </para> + </listitem> + </itemizedlist> + </para> + <para> + In action, <application>Evolution</application> makes most + daily tasks faster, because we built it to work with you + instead of against you. For example, it takes only one or two + clicks to enter an appointment or an address card sent to you + by email, or to send email to a contact or appointment. + <application>Evolution</application> makes displays faster and + more efficient, so searches are faster and memory usage is + much lower. People who get lots of mail will appreciate + advanced features like <link + linkend="usage-mail-organize-vFolders">vFolders</link>, which + let you save searches as though they were ordinary mail + folders. + </para> + + </section> + + <section id="aboutbook"> + <title>About This Book</title> + + <!-- ************** FOLLOWING PARAGRAPH FOR DRAFT ONLY ************* --> + <para> + This is a DRAFT of the <application>Evolution</application> + User's Guide. Please send comments on it to + <email>aaron@helixcode.com</email>. Items that are known to + need action are indicated as such, often with notation like + (INSERT CONTENT HERE). If you have content to add, please + contact me. This paragraph will be removed in later versions + of the manual. + </para> + <!-- ************* END DRAFT ONLY PARAGRAPH ************** --> + + <para> + This book is divided into three sections. The first section is + a <link linkend="usage">guided tour</link>— it will + explain how to use <application>Evolution</application>. If + you are new to <application>Evolution</application> or to + groupware in general, this is the section for you. The second + section, covering <link linkend="config">configuration</link>, + is targeted at advanced users and administrators. If you are + a network administrator, you may find yourself referring to + this section frequently. The third section is a quick <link + linkend="devel">developer's guide</link>, for power users and + hackers. If you want to add advanced scripting to + <application>Evolution</application>, write your own + embeddable components, or simply want to find out just how + powerful <application>Evolution</application> can be, this is + the section for you. + </para> + <para> + Throughout the book, you'll find examples, tips and warnings + to help you along. Most of them are decent, hardworking + pieces of information, and genuinely try to be helpful. Some + of the tips, entitled <emphasis>Bad Ideas</emphasis>, + are, in fact, out to trick you. Please don't follow their + advice, no matter how appealing it may sound. + </para> + <formalpara> + <title>Typographical conventions</title> + <para> + Some kinds of words are marked off with special typography. + It's listed below: + <simplelist> + <member><application>Applications</application></member> + <member><command>Commands</command></member> + <member><guilabel>Labels</guilabel>for menu items and buttons</member> + <member>Other text treatments</member> + <member>more info here</member> + </simplelist> + </para> + </formalpara> + </section> + </preface>
\ No newline at end of file diff --git a/help/C/usage-calendar.sgml b/help/C/usage-calendar.sgml new file mode 100644 index 0000000000..83e03c80c0 --- /dev/null +++ b/help/C/usage-calendar.sgml @@ -0,0 +1,140 @@ + + <chapter id="usage-calendar"> + <title>The Evolution Calendar: Time-Tamer Extraordinaire</title> + <para> + To begin using the calendar, select + <guibutton>Calendar</guibutton> from the <interface>shortcut + bar</interface>. By default, the calendar starts in week view mode (IS + THIS TRUE? CHANGE TEXT TO FIT FEATURE). The calendar week view is + shown in <xref linkend="usage-calendar-fig">: + + <!-- ============== Figure ============================= --> + <figure id="usage-calendar-fig"> + <title>Evolution Calendar View</title> + <screenshot> + <screeninfo>Evolution Contact Manager Window</screeninfo> + <graphic fileref="cal-pic" format="png" srccredit="Aaron Weber"> + </graphic> + </screenshot> + </figure> + <!-- ============== End of Figure ============================= --> + + </para> + <sect1 id ="usage-calendar-view"> + <title>Ways of Looking at your Calendar</title> + <para> + You can view your calendar by the day, by the week, by the + month, or by the year. To do so, click BUTTONS SOMEWHERE. + </para> + <para> + Describe the less-obvious differences among the views of + time here. + </para> + + <para> + In addition, <application>Evolution</application> supports + Hebrew, Muslim, and other calendar formats. To switch to a + different calendar format, choose + <guimenuitem>GUIMENUITEM</guimenuitem> from the + <guimenu>GUIMENU</guimenu>. + </para> + <para> + Describe the ways that different calendars can work here, + and how the different calendars work together. + </para> + </sect1> + <sect1 id="usage-calendar-apts"> + <title>Scheduling With the Evolution Calendar</title> + <para> + The <application>Evolution</application> calendar allows + you to schedule events for yourself or a group of people. + It can handle events that repeat, event lengths from ten + minutes to multiple days, and events that have a date but + no specific time. You can set overlapping events, although + <application>Evolution</application> will warn you about + trying to do two things at once. You can also set event + reminders so that you don't forget about everything you've + just put into your calendar. Basically, it can handle almost + any schedule you throw at it. + </para> + <sect2 id="usage-calendar-apts-basic"> + <title>Creating events</title> + <para> + While looking at the calendar, select <guimenuitem>New + Appointment</guimenuitem> from the + <guimenu>MENU</guimenu>, or press + <keysym>KEYSYM</keysym>. The <interface>New + Appointment</interface> dialog will appear. (INSERT + DESCRIPTION OF INTERFACE HERE: Date, Time, Recurrence, + Reminders, and Tentative/Confirmed) + </para> + <para> + You can alter those settings later by clicking once on the + event in the <interface>calendar view</interface> to + select it, and then choosing <guimenuitem>Event + Properties</guimenuitem> from the + <guimenu>Settings</guimenu> menu. + </para> + </sect2> + + <sect2 id="usage-calendar-apts-group"> + <title>Appointments for Groups</title> + <para> + If you have your calendar set up to work with other + calendars over a network, you can see when others are + available to meet with you. To browse other people's + calendars over your local network, do this: + </para> + <para> + In addition, you can use + <application>Evolution</application> to mark a meeting + request on another person's calendar. To do so, first + select <guimenuitem>New Appointment</guimenuitem> from the + <guimenu>MENU</guimenu>, or press <keysym>KEYSYM</keysym> + to bring up the <interface>new event</interface> window. + Then describe the event as you would any other. Before + you click <guibutton>OK</guibutton>, (INSERT DESCRIPTION + HERE...). <application>Evolution</application> 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 + event on your calendar and on theirs as tentative, rather than + a confirmed, event. + </para> + <para> + To mark a tentative event as confirmed, click once on the + event in the <interface>calendar view</interface> to + select it, and then choose <guimenuitem>Event + Properties</guimenuitem> from the + <guimenu>Settings</guimenu> menu. In the <interface>Event + Properties</interface> dialog window, click the + "tentative" button to un-mark the event. (NOTE THAT this + feature may not at all exist!) + </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> + </sect1> + + <sect1 id="usage-calendar-organize"> + <title>Organizing your Appointments</title> + <para> + Until I have <application>Evolution</application> running properly, + I have no idea how this sort of organization will actually work. + </para> + <para> + But this section will have at least two paragraphs, and + probably a screenshot. + </para> + </sect1> + </chapter> diff --git a/help/C/usage-contact.sgml b/help/C/usage-contact.sgml new file mode 100644 index 0000000000..f88a3d5791 --- /dev/null +++ b/help/C/usage-contact.sgml @@ -0,0 +1,283 @@ + + <chapter id="usage-contact"> + <title>The Evolution Contact Manager</title> + <para> + The <application>Evolution</application> contact manager can + handle all of the functions of an address book, phone book, + or Rolodex. Of course, <application>Evolution</application> + allows easier updates than an actual paper book, and much + easier synchronization with handheld and remote devices. And + I doubt that you can take your little black book and make it + accessible to the rest of your office over a network. Since + <application>Evolution</application> supports most major + network protocols, including <glossterm>IMAP</glossterm> and + <glossterm>LDAP</glossterm>, it's easy to use over an + existing network. + </para> + <para> + Antother advantage of <application>Evolution</application> + is that the address book is integrated into the rest of + the application. That means that when you look for + someone's address, you can also see a history of + appointments with that person, and when you get an email + with contact information in it, you can create a new address + card very quickly. In addition, searches, folders, and + vFolders all work in the same intuitive way they do in the + other components, so you don't have to learn another system + for similar tasks. + </para> + <para> + This chaper will cover the usage of the + <application>Evolution</application> contact manager, + including organizing large amounts of contact data, sharing + addresses over a network, and the automation + capabilities of the address book. Contact manager + configuration is addressed in <xref + linkend="config-prefs-contact">. + </para> + + <sect1 id="usage-contact-basic"> + <title>Getting Started With the Contact Manager</title> + + <para> + To start managing your contacts, click on + <guibutton>Contacts</guibutton> in the shortcut bar. + </para> + <para> + Describe the interface. Include the fact that the + whole book consists of a set of cards, organized into + folders. + </para> + </sect1> + <sect1 id="usage-contact-cards"> + <title>Creating, Deleting, and Adding Cards</title> + <para> + You can create a new card by pressing the <guibutton>New + Card</guibutton> button, or by pressing + <keysym>KEYSYM</keysym>. The <interface>New Card</interface> + window will appear. It has the following fields: + + <itemizedlist> + <listitem> <para> + <guilabel>Name:</guilabel> Enter the person's name here + </para></listitem> + <listitem> <para> + + </para></listitem> + <listitem> <para> + <guilabel>Address:</guilabel> + </para></listitem> + + <listitem> <para> + Something + </para></listitem> + + <listitem> <para> + Something + </para></listitem> + </itemizedlist> + </para> + <para> + You can choose which fields an address card has, and create + new fields for cards. For example, + <application>Evolution</application> provides for two line + postal addresses by default, but you may have as many or as + few lines to an address as you wish. To change which + fields an address card has, choose DESCRIBE HERE HOW TO DO + THIS + </para> + + <note> + <title>Quick ways to add cards</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 that appears. While looking at a calendar + appointment, right-click any email address, and choose + <guimenuitem>Create Card for this Address</guimenuitem>. + (NOTE that feature may change! unimplemented!) + </para> + </note> + + <para> + You delete a card by pressing the <guibutton>Delete + Card</guibutton> button, or by dragging it into the trash folder. + </para> + + <para> + You can move cards around just as you would with email: + dragging and dropping works, as does right-clicking and + selecting <guimenuitem>Move</guimenuitem> from the menu + that appears. + </para> + </sect1> + + <sect1 id="usage-contact-organize"> + <title>Organizing your Contact Manager</title> + <para> + Organizing your contact manager is a lot like organizing + your mail. You can have folders and searches the same way + you can with mail, but the contact manager does not allow + vFolders. It does, however, allow each card to fall under + several categories, and allow you to create your own + categories. We'll go over categories in a bit. + </para> + <para> + Another useful UNIMPLEMENTED + <application>Evolution</application> feature is its ability + to recognize when people live together. If two people in + your contact manager share an address, and you change the + address for one of them, Evolution will ask you if you wish + to change the address for both of them, or just for one. + </para> + + <sect2 id="usage-contact-organize-group"> + <title>Groups of contacts</title> + <para> + <application>Evolution</application> lets you put cards + into folders, mark them as members of different groups, + and search through them in a variety of ways. This + section will describe how to organize and find contact + information using <application>Evolution</application>. + CHANGE THIS paragraph: it needs a great deal of work. + </para> + + <sect3 id="usage-contact-organize-group-folder"> + <title>Grouping with Folders</title> + <para> + The simplest way to group address cards is to use + folders. By default, cards start in the + <guilabel>Contacts</guilabel> folder. You can create + more folders inside that one, or create other address + book folders as well. Each card must be in one and only + one folder. + </para> + <para> + To create a new folder, do this: + </para> + <para> + To put a card into a folder, do this: + </para> + </sect3> + + <sect3 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. The difference + between folders and categories is that folders contain + cards, but category membership is a property of each + card. That means that you can mark a card as being in + several categories or no category at all. For example, + I put my friend Matthew's card in the "Business" category, + because he works with me, the "Friends" category, because + he's also my friend, and the "Frequent" category, because + I call him all the time and can never remember his phone + number. + </para> + <para> + To mark a card as belonging to a category, do this: + </para> + <para> + Then, you can refer to all the cards in that category + by: + </para> + <para> + If the default categories don't suit you, you can add + your own. Here's how: + </para> + </sect3> + </sect2> + </sect1> + + <sect1 id="usage-contact-sharing"> + <title>Sharing your cards (Or Keeping them to Yourself)</title> + <para> + Cards can be shared over a network. This is the sort of + feature you'll want to use if your company has a list of + vendors and clients that needs constant updating. If you + also share your calendars, people can avoid duplicating + work and keep up to date on developments within their + workgroup or across the entire company. + </para> + + <example id="usage-contact-sharing-ex"> + <title>Sharing Address Cards and Calendar Data</title> + <para> + I want to schedule a meeting with someone at Company + X, but I'm not sure who to talk to there. Our + corporate network has an address card that states our + contacts there, so I know whom to call. Since we also + share the calendars, I know that Deanna has already + scheduled a meeting with them next Thursday, and I can + just ask her to bring up my concerns at the meeting. + </para> + </example> + + <para> + Of course, you don't want to share all of your cards— + why overload the network with a list of babysitters, or + tell everyone on your network you're talking to new job + prospects? <application>Evolution</application> lets you + decide which folders you want to make accessible to others. + </para> + <para> + To begin sharing a folder of address cards, select <!-- + DESCRIBE PROCESS HERE -->. The + <interface>Sharing</interface> will pop up. It contains: + <!--DESCRIBE INTERFACE HERE--> + </para> + </sect1> + + <sect1 id="usage-contact-automate"> + <title>Automating the Contact Manager</title> + <para> + The <application> Evolution</application> contact manager + can perform a wide variety of tasks for you. From speeding + up basic tasks like adding a new address card to managing + mailing lists, you'll find that the contact manager is more + than a mere address book. + </para> + <sect2 id="contact-automation-basic"> + <title>Send me a card: Adding New Cards Quickly</title> + <para> + When you get information 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 Address Card</guimenuitem> from the menu + that appears. Of course, <application> + Evolution</application> adds cards from a hand-held device + during HotSync operation. For more information about + that, see <xref linkend="usage-sync">. + </para> + </sect2> + + <sect2 id="contact-automation-lists"> + <title>Managing a Mailing list</title> + <para> + You already know that when you are writing an email, you + can address it to one or more people, and that + <application>Evolution</application> will fill in + addresses from your contact manager's address cards if + you let it. In addition to that, you can send email to + everyone in a particular group by doing SOMETHING HERE. + Future versions of <application>Evolution</application> + 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 postal mailings. + </para> + </sect2> + <sect2 id="usage-contact-automation-extra"> + <title>Map It! and other extra features</title> + <para> + Need a map or directions? Click + <guibutton>MapIt</guibutton> from within the contact + manager, and <application>Evolution</application> will + map the address for you online. + </para> + </sect2> + </sect1> + </chapter>
\ No newline at end of file diff --git a/help/C/usage-mail.sgml b/help/C/usage-mail.sgml new file mode 100644 index 0000000000..c81c384cfb --- /dev/null +++ b/help/C/usage-mail.sgml @@ -0,0 +1,644 @@ + + <chapter id="usage-mail"> + <title>Evolution Mail: Witty Phrase to Come Later</title> + <abstract> + <title> An Overview of the Evolution Mailer</title> + <para> + Email is an integral part of life these days, and + <application>Evolution</application> mail is here to help + you keep track of it. <application>Evolution</application> + email is like other email programs in all the ways you would + hope: (INSERT GOOD SIMILARITIES). + </para> + <para> + However, <application>Evolution</application> has some + important differences. First, it's built to handle very + large amounts of mail without slowing down or crashing. We + had high mail volumes in mind when we designed our <link + linkend="usage-mail-organize-filters">filtering</link> and + <link linkend="usage-mail-organize-search">searching</link> + functions. There's also the + <application>Evolution</application> <link + linkend="usage-mail-organize-vFolders">vFolder</link>, an + advanced organizational feature not found in other mail + clients. If you get a lot of mail, or if you keep every + message you get in case you need to refer to it later, + you'll find that feature especially useful. + </para> + + <para> + You can start reading email by clicking + <guibutton>Inbox</guibutton> in the shortcut bar. + </para> + </abstract> + + <sect1 id="usage-mail-getnsend"> + <title>Reading, Getting and Sending Mail</title> + <sect2 id="usage-mail-getnsend-read"> + <title>Reading a Message</title> + <para> + The first time you open your + <application>Evolution</application> + <guilabel>Inbox</guilabel>, you will see a window like the + one in <xref linkend="usage-mail-intro-fig">, with a + message from Helix Code in the<interface> message + list</interface>. A preview of the message is displayed + below that, in the <interface>view pane</interface>. If + you find the<interface> view pane</interface> too small, + you can double-click on the message in the + <interface>message list</interface> to have it open in a + new window. As is the case with folders, you can + right-click on messages in the message list and get a + menu of possible actions. + </para> + <para> + Go ahead and right-click on the message, and select + <guimenuitem>Delete Message</guimenuitem> from the menu + that appears. The message will move into the + <guilabel>Trash</guilabel> folder. If you want to keep + it, you can open the <guilabel>Trash</guilabel> folder + and drag the message back to your + <guilabel>Inbox</guilabel>. The trash will be + automatically emptied the next time you quit + <application>Evolution</application>. (FEATURE + UNIMPLEMENTED! Text may change to fit featureset) + + <!-- ==============Figure=================================== --> + <!-- MAKE SURE THIS SCREENSHOT HAS THE WELCOME MESSAGE! --> + <figure id="usage-mail-intro-fig"> + <title>Evolution Mail</title> + <screenshot> + <screeninfo>Evolution Mail</screeninfo> + <graphic fileref="mail-intro-pic" format="png" srccredit="Aaron Weber"> + </graphic> + </screenshot> + </figure> + <!-- ==============End of Figure=================================== --> + </para> + </sect2> + + <sect2 id="usage-mail-getnsend-get"> + <title>Getting Mail</title> + <para> + To check your email, just click <guibutton>Send and + Receive</guibutton> in the toolbar. + <application>Evolution</application> will download your + mail for you and send any mail you've marked ready to + send. New mail will appear in your + <interface>Inbox</interface> and also in the + <interface>Today View</interface>. + </para> + <para> + If you get an error message, you probably need to + change your network preferences. To do that, you can run + the setup assistant again, have a look at <xref + linkend="config-prefs-network">, or ask your system + administrator. + </para> + + <sect3 id="usage-mail-getnsend-get-attach"> + <title>Attachments, HTML Mail, and Live Documents</title> + <para> + If you receive a file attached to an email, + <application>Evolution</application> will ask where you + want to put it. Once you've downloaded it, you can + open, move, copy, or execute those files just like any + others, using <application>Nautilus</application> or + your favorite shell or file manager. + </para> + <para> + <application>Evolution</application> can also display + HTML-formatted mail, complete with graphics. HTML + formatting will display automatically, although you can + turn it off if you prefer. + </para> + <para> + It can also display <glossterm>live + documents</glossterm>, which have scripted or + executable contents— for example, a working + spreadsheet page or a chess game. + </para> + <tip id="badidea-attachment"> + <title>Bad Idea</title> + <para> + When someone you don't know sends you an attached + program, go ahead and run it. Set your preferences to + always run live documents when you recieve them, too. + Everybody knows all that virus stuff is just a Windows + problem. + </para> + </tip> + </sect3> + </sect2> + + <sect2 id="usage-mail-getnsend-send"> + <title>Writing and Sending Mail</title> + <para> + You can start writing a new + email message by selecting <guimenuitem>New + Mail</guimenuitem> from the <guimenu>File Menu</guimenu>, + or by pressing <keysym>Ctrl-N</keysym>. When you do so, + the <interface>New Message</interface> window will open, + as shown in <xref linkend="usage-mail-newmsg-fig">. + </para> + +<!-- ==============Figure=================================== --> + <figure id="usage-mail-newmsg-fig"> + <title>New Message Window</title> + <screenshot> + <screeninfo>Evolution Main Window</screeninfo> + <graphic fileref="newmsg-pic" format="png" srccredit="Aaron Weber"> + </graphic> + </screenshot> + </figure> +<!-- ==============End of Figure=================================== --> + + <para> + Enter an address in the <guilabel>To:</guilabel> field, a + message in the <guilabel>Message:</guilabel> field, and + press <guibutton>Send and Receive</guibutton>. That's + easy. It may even be too easy, which is why I like to + queue my messages up to be sent a few minutes later. + + <tip id="usage-mail-getnsend-send-attach-tip"> + <title>Send Now, Send Later</title> + <para> + Evolution will send mail immediately unless you tell + it to do otherwise by selecting <guimenuitem>Send + Later</guimenuitem> from the <guimenu>MENU</guimenu>. + Then, when you press <guibutton>Send & + Receive</guibutton>, all your unsent messages will go + out at once. I like to use "Send Later" because it + gives me a chance to change my mind about a message + before it goes out. That way, I don't send anything I'll + regret the next day. + </para> + <para> + To learn more about how you can specify message queue + and filter behavior, see <xref linkend="config-prefs-mail">. + </para> + </tip> + </para> + + <para> + There is more to sending mail, though. In the + next few sections, we'll go over additional features, + including mailing lists, attachments, and forwarding. + </para> + + + <sect3 id="usage-mail-getnsend-send-to"> + <title>Choosing Recipients</title> + <para> + If you have created address cards in the contact + manager, you can also enter nicknames or other portions + of address data, and + <application>Evolution</application> will complete the + address for you. (INSERT description of UI for this + feature, once it is decided upon). If you enter a name + or nickname that can go with more than one card, + Evolution will open a dialog box to ask you which person + you meant. (QUESTION: will users be able to drag & drop + address cards to send email?). For more information + about using email together with the contact manager and + the calendar, see <xref + linkend="usage-contact-automate"> and <xref + linkend="usage-calendar-apts-group">. + </para> + <para> + In addition, you can mark recipients in three different + ways. The <guilabel>To:</guilabel> field is for the + primary recipients of the message you are going to send. + However, it is considered bad form to have more than a + few email addresses in this section. + </para> + <para> + If you're writing to one person, but want to keep a + third party up to date, you can use + <guilabel>Cc:</guilabel>. Hearkening back to the dark + ages when people used typewriters and there were no copy + machines, "Cc" stands for "Carbon Copy." Use it + whenever you want to share a message you've written to + someone else. + <example> + <title>Using the Cc: field</title> + <para> + Say, for example, Susan sends an email to a client. + She puts her co-worker, Tim, in the in the + <guilabel>Cc:</guilabel> field, so that he know + what's going on. The client can see that Tim also + recieved the message, and know that they can talk + to Tim about the message as well. + </para> + </example> + </para> + <para> + If you have a large number of recipients, or if you want + to send mail to several people without sharing the + recipient list, you should use + <guilabel>BCc:</guilabel>. "BCc" stands for "Blind + Carbon Copy", and means that addresses in the + <guilabel>BCc:</guilabel> field will receive copies of + the message, but they will not receive the list of the + other recipients' addresses, nor will other recipients + know that they have recieved the message. When I send a + generic message to all my friends and I want them to + think I've written a personalized email to every one of + them, I put them all in the <guilabel>BCc:</guilabel> + list. + </para> + </sect3> + + <sect3 id="usage-mail-getnsend-send-reply"> + <title>Replying to Messages</title> + <para> + In order to reply to a message, click on it once in the + message list to select it. Then press the + <guibutton>Reply</guibutton> button, or use the + <keysym>REPLY COMBO</keysym> hot key. A window like + the <interface>New Message</interface> window will + appear, but the subject will already be present— + typically, your new message will have the same subject + as the message to which you are replying, but with Re: + before it, to mark it as a reply. In addition, the + full text of the previous message may be inserted into + the new message, with the > character before each + line. This indicates quoting. You can intersperse + your message with the quoted material as shown in <xref + linkend="usage-mail-getnsend-reply-fig"> + +<!-- note that this figure should have a reply mail ready to send, with quoted materials and the relevant replies interspersed--> +<!-- ==============Figure=================================== --> + <figure id="usage-mail-getnsend-reply-fig"> + <title>Reply Message Window</title> + <screenshot> + <screeninfo>Evolution Main Window</screeninfo> + <graphic fileref="replymsg-pic" format="png" srccredit="Aaron Weber"> + </graphic> + </screenshot> + </figure> +<!-- ==============End of Figure=================================== --> + + </para> + + <para> + If a message has several recipients, as in the case of + mailing lists or messages that have been carbon copied, + you may wish to select one of the items under the + <guimenuitem>Reply-To</guimenuitem> submenu on the + <guimenu>MENU</guimenu> menu. This will allow you to + choose one or several of the other message recipients in + addition to the person who originally sent you the + message. + <example> + <title>Using the Reply-To feature</title> + <para> + Returning to the previous example, the client can + decide whether to reply just to Susan, just to Tim, + or to both of them by selecting a menu item, rather + than by cutting and pasting the email addresses. If + there are large numbers of people in the Cc: fields, + this can save substantial amounts of time. + </para> + </example> + </para> + </sect3> + + + <sect3 id="usage-mail-getnsend-send-fancy"> + <title>Embellishing that email</title> + <para> + <application>Evolution</application> allows you to + make your email more attractive in a number of ways. You + can send messages formatted with HTML, attach any sort + of file to them, and even include live documents, like + spreadhseets or chess games. This section will tell + you how. + </para> + + + <sect4 id="usage-mail-getnsend-send-html"> + <title>Colors, pictures, and fonts with HTML Mail</title> + <para> + Most email messages are sent as plain text, but they + can also be sent as HTML, which means they can include + color, text style, and other formatting information. + Evolution will read and display HTML properly without + trouble, and also allows you to send outgoing + email messages as HTML. To send an HTML message, just + use the composition toolbar to add formatting; + your message text will appear formatted in the composer + window, and the message will be sent as HTML. + </para> + <note> + <title>A Technical note on HTML Tags</title> + <para> + Any text, including HTML tags, entered into the + message composition window is assumed to be plain + text. If you enter HTML directly into the + composer— say, <markup + role="html"><BR>Bold Text</BR></markup>, + the the composer will assume you meant exactly that, + and not "make this text bold," as a HTML composition + tool would. For the technically inclined, that + means that when the text <markup + role="html"><BR></markup> is sent as HTML, it + will be converted to the string + <literal>&lt;BR&gt;</literal>. + </para> + </note> + <para> + Some people do not have HTML-capable mail clients, or + prefer not to receive HTML-enhanced mail because it + is slower to download and display. Some people refer + to HTML mail as "the root of all evil" and get very + angry if you send them HTML mail, which is why the + default in <application>Evolution</application> is + plain text. If you have an address book entry for + someone who does not wish to receive HTML-enhanced + mail, you can note that preference in their address + card. The mailer will automatically strip the HTML + tags from any messages you send to that address. + </para> + </sect4> + + <sect4 id="usage-mail-getnsend-send-attach"> + <title>Attachments</title> + <para> + If you want to attach a file to your email message, + you can do so by <!--describe process here-->. If + your recipients can read HTML mail, you can put an + image inside the mail by dragging the file into the + composer window, or by selecting (INSERT DESCRIPTION + HERE) (IS THIS CORRECT?). Still, unless you know what + email client the recipient is using, it's best to send + a message or attachment in the simplest manner + possible. + </para> + </sect4> + <sect4 id="usage-mail-getnsend-send-live"> + <title></title> + <para> + Later versions of <application>Evolution</application> + will allow you to enliven your email with almost any + sort of document, and even with entire + applications. At this point, however, I don't know how + that will work. + </para> + </sect4> + </sect3> + + <sect3 id="usage-getnsend-fwd"> + <title>Forwarding Mail</title> + <para> + <guilabel>Forward</guilabel> is useful if you have + received a message and you think someone else would like + to see it, or if you get a message intended for someone + else. You can forward a message as an attachment to a + new message (the default way of forwarding) or you can send it + <glossterm>inline</glossterm> as a quoted portion of the + message you are sending. Attachment forwarding is best + if you want to send the entire message you received, + unaltered. Inline forwarding is best if you want to + send portions of a message, or if you have a large + number of comments on different sections of the message + you are forwarding. Remember to note from whom the + message came, and where, if at all, you have removed or + altered content. + </para> + <para> + To forward a message, first make sure it is selected by + clicking it once in the message list. Then, press + <guibutton>Forward</guibutton> on the toolbar, or select + SOMETHING. To forward a message inline instead of as an + attachment, DO SOMETHING ELSE. Choose an addressee as + you would when sending a new message; the subject will + already be entered, but you can alter it. Enter your + comments on the message in the <interface>composition + frame</interface>, and press <guibutton>Send and + Receive</guibutton>. To forward it + <glossterm>inline</glossterm> instead of attached, + select <guimenuitem>Forward Inline</guimenuitem> from + the <guimenu>Message</guimenu> menu. + </para> + </sect3> + <sect3 id="usage-mail-getnsend-ettiquette"> + <title>Seven Tips for Email Usage</title> + <para> + I started with ten, but four were "Don't send + <glossterm>spam</glossterm>." + <itemizedlist> + <listitem> + <para> + Always begin and close with a salutation. Say + "please" and "thank you", just like you do in real + life. You can keep your pleasantries short, but be pleasant! + </para> + </listitem> + + <listitem> + <para> + ALL CAPS MEANS YOU'RE SHOUTING! + </para> + </listitem> + + <listitem> + <para> + Never write anything in email you wouldn't say in + public. Old messages have a nasty habit of + resurfacing when you least expect them to. + </para> + </listitem> + + <listitem> + <para> + Check your spelling and use complete sentences. + </para> + </listitem> + + <listitem> + <para> + Don't send nasty emails (flames). If you get one, + don't write back. + </para> + </listitem> + + <listitem> + <para> + Don't send spam or forward chain mail. If you + must, verify any rumors, and make sure the + message doesn't have multiple layers of email + quotation symbols (>) indicating multiple + layers of careless inline forwarding. + </para> + </listitem> + + <listitem> + <para> + When you reply or forward, include just enough of + the previous message to provide context. Not too + much, not too little. + </para> + </listitem> + </itemizedlist> + </para> + <para> Happy mailing! </para> + </sect3> + </sect2> + </sect1> + + <sect1 id="usage-mail-organize"> + <title>Organizing Your Mail</title> + <para> + Even if you only get a few email messages a day, you + probably want to sort and organize them. When you get a + hundred a day and you want to refer to a message you + received six weeks ago, you need to sort and organize them, + and <application>Evolution</application> has the tools to + help you do it. + </para> + + <sect2 id="usage-mail-organize-folders"> + <title>Getting Organized with Folders</title> + <para> + You can create new folders by selecting + <guimenuitem>ITEM</guimenuitem> from the + <guimenu>MENU</guimenu>, or by pressing + <keysym>COMBO</keysym>. (Will there be a dialog box to + determine name and location? Must wait for feature to + describe) The new folders will appear in the + <interface>tree view</interface>, and you can drag them + wherever you want to relocate them. You can move messages + into them by dragging, or by selecting them and choosing + <guimenuitem>ITEM</guimenuitem> from the + <guimenu>MENU</guimenu>. An email message can be in only + one folder at a time, just like real mail in real folders. + This is also the case for folders of address cards and calendar + information. + </para> + </sect2> + + <sect2 id="usage-mail-organize-search"> + <title>Searching for Messages</title> + <para> + Because <application>Evolution</application> automatically + creates an index of every email you send or receive, it + can search through your old messages and present you with + results very quickly. You can search for messages by + author, subject, keyword, or headers. (INSERT descriptons + of what those terms mean) + </para> + <para> + (INSERT the way one creates a search and so forth) + </para> + </sect2> + + <sect2 id="usage-mail-organize-vFolders"> + <title>Getting Really Organized with Virtual Folders</title> + <para> + If you find yourself performing a search frequently, you + can save it as a virtual folder. Virtual folders, or + vFolders, are an advanced way of viewing your email + messages within <application>Evolution</application>. If + you get a lot of mail or often forget where you put + messages, vFolders can help you stay on top of things. + </para> + <para> + A vFolder looks and acts a lot like a folder, but it's + actually a saved search that you can access in most of the + same ways you would a regular folder. The one important + differences between them is that a conventional folder + actually contains messages, but a vFolder is a view of + messages that may be in several different folders. This + means that while a message may fall into several vFolders, + it can be in only one conventional folder. Also, it means + that you cannot remove a message from a vFolder unless you + delete it, and you cannot add a message to a vFolder + unless you change the vFolder's search criteria. + </para> + <para> + As messages that meet the vFolder criteria arrive or are + deleted, <application>Evolution</application> will + automatically place them in and and remove them from the + vFolder contents list. When you delete a message, it gets + erased from the folder it actually exists in as well as + any vFolders which include it. + </para> + <para> + That's pretty complicated. But it can be useful. For + example, if I have a folder for all the email from one + person, and another folder for all the email on a given + topic, I feel organized. But when the person sends me + mail about the topic, my whole email filing universe + becomes chaotic. I need vFolders to save the day for me. + </para> + <para> + That sounds silly, but imagine a business trying to keep + track of mail from hundreds of vendors and clients, or a + university with overlapping and changing groups of + faculty, staff, administrators and students. The larger + the system, the less you can afford that sort of + confusion. vFolders make for better organization because + they can accept overlapping groups in a way that regular + folders and filing systems can't. + </para> + + <example id="usage-mail-organize-vFolders-ex"> + <title>Using Folders, Searches, and vFolders</title> + <para> + To organize my mail box, I can set up a vFolder + for emails from my friend Vince, by doing (INSERT + PROCESS HERE). Then, whenever I want to see the + messages Vince has sent me, I open the vFolder, and + every message he's sent me shows up, no matter where + I've actually filed it. If I want, I can also create a + vFolder containing any message from my list of + co-workers which also has the name of the project in + it. That way, when Vince sends me mail about the + project, I can see that message both in the "Vince" + vFolder and in the "Project" vFolder. That's because + when I open up the "Vince" folder, I'm really + performing a search for all the mail from Vince, and + when I open the "Project" folder I'm really performing + a search for all the mail about the project. + + (INSERT SCREENSHOT HERE) + + </para> + </example> + </sect2> + + <sect2 id="usage-mail-organize-filters"> + <title>Staying organized: Mail Filters in Evolution</title> + <para> + Filters sort your email for you as it arrives in your + Inbox, so you don't have to sort them all yourself. + People who subscribe to multiple mailing lists find + filters especially helpful to sort personal from + list-related mail. To create a filter, go to your + <interface>Inbox</interface>. Then select BLAH BLAH BLAH. + This will open the <interface>filters</interface> window. + </para> + + <para> + The <interface>filters</interface> window contains the + following items: <!--DESCRIBE INTERFACE--> + </para> + + <note> + <title>Two Notable Filter Features</title> + <para> + <itemizedlist> + <listitem><para>Any email that does not meet filter + action criteria remains in the Inbox. </para> + </listitem> + + <listitem><para>If you move a folder, your filters + will follow it. </para></listitem> + </itemizedlist> + </para> + </note> + </sect2> + </sect1> + </chapter> +<!-- ================ END OF MAILER CHAPTER ============= --> diff --git a/help/C/usage-mainwindow.sgml b/help/C/usage-mainwindow.sgml new file mode 100644 index 0000000000..8470189977 --- /dev/null +++ b/help/C/usage-mainwindow.sgml @@ -0,0 +1,214 @@ + + <chapter id="usage-mainwindow"> + + <title>The Main Window: Evolution Basics</title> + <para> + After <application>Evolution</application> starts up, you will + see the <interface>main window</interface>, which looks a lot + like in <xref linkend="usage-mainwindow-fig">. On the left of + the <interface>main window</interface> are the + <interface>shortcut bar</interface> and the + <interface>tree-view</interface>. Just underneath the title + bar is a series of menus in the <interface>menu + bar</interface>, and below that, the <interface>tool + bar</interface> with buttons for different functions. The + largest part of the <interface>main window</interface> is + taken up by a welcome message. <!-- para does not end here + but after fig! --> + +<!-- ==============Figure=================================== --> + +<!-- +Make sure that this figure meets its descriptions below: it should +show the shortcut bar, the tree view with some trees expanded, and so +forth. Can these things be labelled with little arrows & stuff? + --> + + <figure id="usage-mainwindow-fig"> + <title>Evolution Main Window</title> + <screenshot> + <screeninfo>Evolution Main Window</screeninfo> + <graphic fileref="mainwindow-pic" format="png" srccredit="Aaron Weber"> + </graphic> + </screenshot> + </figure> +<!-- ==============End of Figure=================================== --> + + + <note> + <title>The Way Evolution Looks</title> + <para> + The appearance of both + <application>Evolution</application> and + <application>GNOME</application> is very easy to + customize, so your screen might not look like this + picture. You might configure + <application>Evolution</application> to start with a + different view, or without the <interface>shortcut + bar</interface> or <interface>tree view</interface>. + </para> + </note> + </para> + + <sect1 id="usage-mainwindow-shortcutbar"> + <title>The Shortcut Bar</title> + <para> + The buttons in the <interface>shortcut bar</interface> give + you quick access to the different functions that + <application>Evolution</application> provides. + </para> + <para> + The buttons in the <interface>shortcut bar</interface> are: + <itemizedlist> + <listitem> + <para> + <guibutton>Today</guibutton>, which will bring up a summary + of any new messages you've recieved, along with the tasks and + appointments you have lined up for today. + </para> + </listitem> + + <listitem> + <para> + <guibutton>Inbox</guibutton>, which will show you all + of your email. Your Inbox is also where you can + access Evolution's tools to filter, sort, organize, + and search your mail. + </para> + </listitem> + + <listitem> + <para> + The <guibutton>Calendar</guibutton>, which can store + appointments for you. Connected to a network, you + can use it to keep a group of people on schedule and + up to date. + </para> + </listitem> + + <listitem> + <para> + The <guibutton>Contacts</guibutton> tool holds your + addresses, phone numbers, and contact information. + Like calendar information, contact data can be + synchronized with hand-held devices and shared over a + network. + </para> + </listitem> + + <listitem> + <para> + The <guibutton>Tasks</guibutton> tool combines a "to + do" list with reminders to help you keep track of + daily events. + </para> + </listitem> + + <listitem> + <para> <guibutton>Notes</guibutton> is your catch-all + notepad: write <glossterm>haiku</glossterm>, take down + messages from phone conversations, or keep small + things organized. + </para> + </listitem> + </itemizedlist> + + + </para> + <para> + If you prefer to use a keyboard shortcut, or <glossterm>hot + key</glossterm>, you can use those instead. They're + shown... (INSERT DESCRIPTION) You can also set your own hot + keys for functions that don't have any; this is covered in + <xref linkend="config">. If you're using the keyboard + shortcuts you may also want to hide the <interface>shortcut + bar</interface> by selecting <guimenuitem>Hide/Show Shortcut + Bar</guimenuitem> from the <guimenu>MENU</guimenu> menu. + </para> + </sect1> + + <sect1 id="usage-mainwindow-treeview"> + <title>The Tree View</title> + <para> + The <interface>tree view</interface> is the most comprehensive way to + get to your information: it can show you everything you've + stored with <application>Evolution</application> + appointments, address cards, emails, and so forth. + + The <interface>tree view</interface> display presents your + data like a <glossterm>file tree</glossterm>— it + starts small at the top, and branches downwards. There are a + few folders you will always see, because they're at the top. + On my computer, they are: (ch. to itemizedlist w/descriptions?) + <simplelist> + <member>Local Mail</member> + <member>Remote Mail</member> + <member>Address Book</member> + <member>Calendar</member> + <member>Trash</member> + </simplelist>. + </para> + + <para> + Right-clicking will bring up a menu for just about anything + in GNOME, and <application>Evolution</application> is no + exception. If you right-click on a folder, you'll have a + menu with the following options: + <itemizedlist> + <listitem><para>Something</para></listitem> + <listitem><para>Something</para></listitem> + <listitem><para>Something</para></listitem> + </itemizedlist>. + </para> + + <tip> + <title>Context-Sensitive Help</title> + <para> + You can almost always get help on an item by + right-clicking it. If you're not sure what something is, + or don't know what you can do with it, right-clicking and + choosing <guimenuitem>Help</guimenuitem> is a good way to + find out. + </para> + </tip> + + <para> + If a folder has other folders in it, there will be a plus + sign next to it. Click on the plus sign, and you will see + the other folders inside. This may change in the future to + something more attractive, like triangles that drop down as + you click on them to display the rest of the tree. + </para> + + <para> + Any time new information arrives in a folder, that folder + will be highlighted, or its label displayed as bold + text. You can learn more about customizing + <application>Evolution</application> alerts and appearance + in <xref linkend="config">. + </para> + + <para> + (CHANGE that title! THIS SECTION BELONGS SOMEWHERE ELSE!) + You can drag the folders inside the tree view to change + their order or put one folder inside another. To delete a + folder, you can drag it into the trash folder. The same + goes for individual messages, appointments, and address + cards, whether they're in the <interface>tree + view</interface> or not: drag them where you want them, and + they will go there. (IS THIS TRUE?) + </para> + <para> + You can also use the <guimenu>right-click menu</guimenu> to + move, rename, and delete folders. + <guimenuitem>Delete</guimenuitem> function from the + <guimenu>right-click menu</guimenu>. + </para> + <para> + Once you've familiarized yourself with the <interface>main + window</interface> you can start doing things with it. + We'll start with email: you've got a letter waiting for you + already. + </para> + </sect1> + </chapter>
\ No newline at end of file diff --git a/help/C/usage-setup.sgml b/help/C/usage-setup.sgml new file mode 100644 index 0000000000..1290b000bb --- /dev/null +++ b/help/C/usage-setup.sgml @@ -0,0 +1,46 @@ + <chapter id="usage-setup"> + <title>A Quick Start</title> + <para> + Start <application>Evolution</application> by selecting + <guimenuitem>Evolution</guimenuitem> from the + <guisubmenu>Applications</guisubmenu> of the <guimenu>Main + Panel Menu</guimenu>, or by typing + <command>evolution</command> at the command-line. If this is + the first time you have run + <application>Evolution</application>, you'll be asked if you + want help setting up your email preferences. If you don't + plan to use email, or if you'd rather configure your email + preferences later, select <guibutton>No</guibutton>, and it + will go away. You can configure your email preferences later + by selecting SOMETHING from SOME MENU. + </para> + <para> + If you answer yes, it will guide you through the network + configuration process. It will ask you for the following + information: (FLESH OUT THIS LIST!) + <itemizedlist> + <listitem> <para> + Name— Your full name: eg. William Blake + </para></listitem> + + <listitem><para> + UserName— Your user or account name: eg. wblake + </para></listitem> + <listitem><para> + Type of Server— POP vs. SMTP vs.... + </para></listitem> + + <listitem> + <para> + TERM— DESCRIPTION + </para> + </listitem> + + <listitem> + <para> + TERM— DESCRIPTION + </para> + </listitem> + </itemizedlist> + </para> + </chapter>
\ No newline at end of file diff --git a/help/C/usage-sync.sgml b/help/C/usage-sync.sgml new file mode 100644 index 0000000000..f28ebc10cc --- /dev/null +++ b/help/C/usage-sync.sgml @@ -0,0 +1,19 @@ + + <chapter id="usage-sync"> + <title>Synchronizing with a Hand-held Device</title> + <para> + Once you've set up a synchronization system, it pretty much + takes care of itself. Not only that, it's entirely possible + that your system administrator has set it up for you. All + that this chapter covers is how to use that system once it's + installed and configured. If you need to set it up, consult + <xref linkend="config-sync">. + </para> + + <para> + If you've already got Gnome-pilot set up to use + <application>Evolution</application> all you need to do is put + your hand-held device on the cradle and press the HotSync + button. No, really. That's all there is to it. + </para> + </chapter>
\ No newline at end of file |