From c8a180bc595585c7efad6a608e01cd25d68412e0 Mon Sep 17 00:00:00 2001 From: nobody Date: Fri, 2 Mar 2001 01:33:29 +0000 Subject: This commit was manufactured by cvs2svn to create tag 'GIDE_BEFORE_BONOBO'. svn path=/tags/GIDE_BEFORE_BONOBO/; revision=8485 --- doc/.cvsignore | 2 - doc/C/.cvsignore | 9 - doc/C/Makefile.am | 59 - doc/C/apx-authors.sgml | 75 - doc/C/apx-bugs.sgml | 23 - doc/C/apx-gloss.sgml | 459 ------ doc/C/config-prefs.sgml | 646 -------- doc/C/config-setupassist.sgml | 213 --- doc/C/config-sync.sgml | 124 -- doc/C/evolution.sgml | 145 -- doc/C/fig/calendar.png | Bin 30227 -> 0 bytes doc/C/fig/config-cal.png | Bin 6898 -> 0 bytes doc/C/fig/config-mail.png | Bin 8680 -> 0 bytes doc/C/fig/contact-editor.png | Bin 37707 -> 0 bytes doc/C/fig/contact.png | Bin 27020 -> 0 bytes doc/C/fig/filter-assist-fig.png | Bin 6644 -> 0 bytes doc/C/fig/filter-new-fig.png | Bin 7826 -> 0 bytes doc/C/fig/mail-composer.png | Bin 15277 -> 0 bytes doc/C/fig/mail-druid-pic.png | Bin 35959 -> 0 bytes doc/C/fig/mail-inbox.png | Bin 31474 -> 0 bytes doc/C/fig/mainwindow-pic.png | Bin 166348 -> 0 bytes doc/C/fig/print-dest.png | Bin 7219 -> 0 bytes doc/C/fig/print-preview.png | Bin 26643 -> 0 bytes doc/C/fig/vfolder-createrule-fig.png | Bin 7621 -> 0 bytes doc/C/menuref.sgml | 1470 ------------------- doc/C/preface.sgml | 438 ------ doc/C/usage-calendar.sgml | 371 ----- doc/C/usage-contact.sgml | 617 -------- doc/C/usage-exec-summary.sgml | 91 -- doc/C/usage-mail.sgml | 1539 -------------------- doc/C/usage-mainwindow.sgml | 453 ------ doc/C/usage-notes.sgml | 49 - doc/C/usage-print.sgml | 105 -- doc/C/usage-sync.sgml | 20 - doc/COPYING-DOCS | 355 ----- doc/Camel-Classes | 35 - doc/ChangeLog | 694 --------- doc/Design | 201 --- doc/Keybindings | 13 - doc/Makefile.am | 1 - doc/NAMESPACE | 65 - doc/devel/.cvsignore | 4 - doc/devel/ChangeLog | 159 -- doc/devel/Makefile.am | 84 -- doc/devel/calendar/.cvsignore | 2 - doc/devel/calendar/Makefile.am | 7 - doc/devel/calendar/alarm-generation.sgml | 139 -- doc/devel/calendar/architecture.sgml | 162 --- doc/devel/calendar/cal-client/.cvsignore | 3 - doc/devel/calendar/cal-client/Makefile.am | 131 -- .../cal-client/evolution-cal-client-decl.txt | 161 -- .../cal-client/evolution-cal-client-sections.txt | 44 - .../calendar/cal-client/evolution-cal-client.args | 0 .../cal-client/evolution-cal-client.hierarchy | 2 - .../cal-client/evolution-cal-client.signals | 21 - .../calendar/cal-client/evolution-cal-client.types | 4 - doc/devel/calendar/cal-client/tmpl/cal-client.sgml | 303 ---- .../tmpl/evolution-cal-client-unused.sgml | 84 -- doc/devel/calendar/cal-util/.cvsignore | 3 - doc/devel/calendar/cal-util/Makefile.am | 142 -- .../calendar/cal-util/evolution-cal-util-decl.txt | 780 ---------- .../cal-util/evolution-cal-util-sections.txt | 161 -- .../calendar/cal-util/evolution-cal-util.args | 0 .../calendar/cal-util/evolution-cal-util.hierarchy | 2 - .../calendar/cal-util/evolution-cal-util.signals | 0 .../calendar/cal-util/evolution-cal-util.types | 4 - .../calendar/cal-util/tmpl/cal-component.sgml | 991 ------------- doc/devel/calendar/cal-util/tmpl/cal-recur.sgml | 42 - doc/devel/calendar/cal-util/tmpl/cal-util.sgml | 48 - .../cal-util/tmpl/evolution-cal-util-unused.sgml | 228 --- doc/devel/calendar/cal-util/tmpl/timeutil.sgml | 176 --- doc/devel/calendar/evolution-calendar.sgml | 52 - doc/devel/calendar/public-reference.sgml | 24 - doc/devel/evolution-devel-guide.sgml | 97 -- doc/devel/executive-summary/Makefile.am | 125 -- .../executive-summary/evolution-services-decl.txt | 599 -------- .../evolution-services-sections.txt | 95 -- .../executive-summary/evolution-services.args | 0 .../executive-summary/evolution-services.hierarchy | 15 - .../executive-summary/evolution-services.signals | 0 .../executive-summary/evolution-services.types | 10 - doc/devel/executive-summary/private-reference.sgml | 20 - doc/devel/executive-summary/public-reference.sgml | 22 - .../tmpl/evolution-services-unused.sgml | 0 ...executive-summary-component-factory-client.sgml | 53 - .../tmpl/executive-summary-component-factory.sgml | 46 - .../tmpl/executive-summary-component.sgml | 37 - .../tmpl/executive-summary-html-view.sgml | 75 - doc/devel/fdl.sgml | 671 --------- doc/devel/importer/.cvsignore | 3 - doc/devel/importer/Makefile.am | 127 -- .../importer/evolution-shell-importer-sections.txt | 79 - doc/devel/importer/evolution-shell-importer.args | 0 .../importer/evolution-shell-importer.heirarchy | 5 - .../importer/evolution-shell-importer.hierarchy | 14 - doc/devel/importer/evolution-shell-importer.types | 9 - doc/devel/importer/private-reference.sgml | 21 - doc/devel/importer/public-reference.sgml | 20 - .../importer/tmpl/evolution-importer-client.sgml | 83 -- doc/devel/importer/tmpl/evolution-importer.sgml | 86 -- .../tmpl/evolution-shell-importer-unused.sgml | 10 - doc/devel/preface.sgml | 113 -- doc/devel/reference.sgml | 49 - doc/white-papers/calendar/calendar.sgml | 209 --- doc/white-papers/mail/camel.sgml | 339 ----- doc/white-papers/mail/ibex.sgml | 158 -- doc/white-papers/widgets/e-table.sgml | 279 ---- 107 files changed, 15704 deletions(-) delete mode 100644 doc/.cvsignore delete mode 100644 doc/C/.cvsignore delete mode 100644 doc/C/Makefile.am delete mode 100644 doc/C/apx-authors.sgml delete mode 100644 doc/C/apx-bugs.sgml delete mode 100644 doc/C/apx-gloss.sgml delete mode 100644 doc/C/config-prefs.sgml delete mode 100644 doc/C/config-setupassist.sgml delete mode 100644 doc/C/config-sync.sgml delete mode 100644 doc/C/evolution.sgml delete mode 100644 doc/C/fig/calendar.png delete mode 100644 doc/C/fig/config-cal.png delete mode 100644 doc/C/fig/config-mail.png delete mode 100644 doc/C/fig/contact-editor.png delete mode 100644 doc/C/fig/contact.png delete mode 100644 doc/C/fig/filter-assist-fig.png delete mode 100644 doc/C/fig/filter-new-fig.png delete mode 100644 doc/C/fig/mail-composer.png delete mode 100644 doc/C/fig/mail-druid-pic.png delete mode 100644 doc/C/fig/mail-inbox.png delete mode 100644 doc/C/fig/mainwindow-pic.png delete mode 100644 doc/C/fig/print-dest.png delete mode 100644 doc/C/fig/print-preview.png delete mode 100644 doc/C/fig/vfolder-createrule-fig.png delete mode 100644 doc/C/menuref.sgml delete mode 100644 doc/C/preface.sgml delete mode 100644 doc/C/usage-calendar.sgml delete mode 100644 doc/C/usage-contact.sgml delete mode 100644 doc/C/usage-exec-summary.sgml delete mode 100644 doc/C/usage-mail.sgml delete mode 100644 doc/C/usage-mainwindow.sgml delete mode 100644 doc/C/usage-notes.sgml delete mode 100644 doc/C/usage-print.sgml delete mode 100644 doc/C/usage-sync.sgml delete mode 100644 doc/COPYING-DOCS delete mode 100644 doc/Camel-Classes delete mode 100644 doc/ChangeLog delete mode 100644 doc/Design delete mode 100644 doc/Keybindings delete mode 100644 doc/Makefile.am delete mode 100644 doc/NAMESPACE delete mode 100644 doc/devel/.cvsignore delete mode 100644 doc/devel/ChangeLog delete mode 100644 doc/devel/Makefile.am delete mode 100644 doc/devel/calendar/.cvsignore delete mode 100644 doc/devel/calendar/Makefile.am delete mode 100644 doc/devel/calendar/alarm-generation.sgml delete mode 100644 doc/devel/calendar/architecture.sgml delete mode 100644 doc/devel/calendar/cal-client/.cvsignore delete mode 100644 doc/devel/calendar/cal-client/Makefile.am delete mode 100644 doc/devel/calendar/cal-client/evolution-cal-client-decl.txt delete mode 100644 doc/devel/calendar/cal-client/evolution-cal-client-sections.txt delete mode 100644 doc/devel/calendar/cal-client/evolution-cal-client.args delete mode 100644 doc/devel/calendar/cal-client/evolution-cal-client.hierarchy delete mode 100644 doc/devel/calendar/cal-client/evolution-cal-client.signals delete mode 100644 doc/devel/calendar/cal-client/evolution-cal-client.types delete mode 100644 doc/devel/calendar/cal-client/tmpl/cal-client.sgml delete mode 100644 doc/devel/calendar/cal-client/tmpl/evolution-cal-client-unused.sgml delete mode 100644 doc/devel/calendar/cal-util/.cvsignore delete mode 100644 doc/devel/calendar/cal-util/Makefile.am delete mode 100644 doc/devel/calendar/cal-util/evolution-cal-util-decl.txt delete mode 100644 doc/devel/calendar/cal-util/evolution-cal-util-sections.txt delete mode 100644 doc/devel/calendar/cal-util/evolution-cal-util.args delete mode 100644 doc/devel/calendar/cal-util/evolution-cal-util.hierarchy delete mode 100644 doc/devel/calendar/cal-util/evolution-cal-util.signals delete mode 100644 doc/devel/calendar/cal-util/evolution-cal-util.types delete mode 100644 doc/devel/calendar/cal-util/tmpl/cal-component.sgml delete mode 100644 doc/devel/calendar/cal-util/tmpl/cal-recur.sgml delete mode 100644 doc/devel/calendar/cal-util/tmpl/cal-util.sgml delete mode 100644 doc/devel/calendar/cal-util/tmpl/evolution-cal-util-unused.sgml delete mode 100644 doc/devel/calendar/cal-util/tmpl/timeutil.sgml delete mode 100644 doc/devel/calendar/evolution-calendar.sgml delete mode 100644 doc/devel/calendar/public-reference.sgml delete mode 100644 doc/devel/evolution-devel-guide.sgml delete mode 100644 doc/devel/executive-summary/Makefile.am delete mode 100644 doc/devel/executive-summary/evolution-services-decl.txt delete mode 100644 doc/devel/executive-summary/evolution-services-sections.txt delete mode 100644 doc/devel/executive-summary/evolution-services.args delete mode 100644 doc/devel/executive-summary/evolution-services.hierarchy delete mode 100644 doc/devel/executive-summary/evolution-services.signals delete mode 100644 doc/devel/executive-summary/evolution-services.types delete mode 100644 doc/devel/executive-summary/private-reference.sgml delete mode 100644 doc/devel/executive-summary/public-reference.sgml delete mode 100644 doc/devel/executive-summary/tmpl/evolution-services-unused.sgml delete mode 100644 doc/devel/executive-summary/tmpl/executive-summary-component-factory-client.sgml delete mode 100644 doc/devel/executive-summary/tmpl/executive-summary-component-factory.sgml delete mode 100644 doc/devel/executive-summary/tmpl/executive-summary-component.sgml delete mode 100644 doc/devel/executive-summary/tmpl/executive-summary-html-view.sgml delete mode 100644 doc/devel/fdl.sgml delete mode 100644 doc/devel/importer/.cvsignore delete mode 100644 doc/devel/importer/Makefile.am delete mode 100644 doc/devel/importer/evolution-shell-importer-sections.txt delete mode 100644 doc/devel/importer/evolution-shell-importer.args delete mode 100644 doc/devel/importer/evolution-shell-importer.heirarchy delete mode 100644 doc/devel/importer/evolution-shell-importer.hierarchy delete mode 100644 doc/devel/importer/evolution-shell-importer.types delete mode 100644 doc/devel/importer/private-reference.sgml delete mode 100644 doc/devel/importer/public-reference.sgml delete mode 100644 doc/devel/importer/tmpl/evolution-importer-client.sgml delete mode 100644 doc/devel/importer/tmpl/evolution-importer.sgml delete mode 100644 doc/devel/importer/tmpl/evolution-shell-importer-unused.sgml delete mode 100644 doc/devel/preface.sgml delete mode 100644 doc/devel/reference.sgml delete mode 100644 doc/white-papers/calendar/calendar.sgml delete mode 100644 doc/white-papers/mail/camel.sgml delete mode 100644 doc/white-papers/mail/ibex.sgml delete mode 100644 doc/white-papers/widgets/e-table.sgml (limited to 'doc') diff --git a/doc/.cvsignore b/doc/.cvsignore deleted file mode 100644 index 282522db03..0000000000 --- a/doc/.cvsignore +++ /dev/null @@ -1,2 +0,0 @@ -Makefile -Makefile.in diff --git a/doc/C/.cvsignore b/doc/C/.cvsignore deleted file mode 100644 index 2f4c48adbf..0000000000 --- a/doc/C/.cvsignore +++ /dev/null @@ -1,9 +0,0 @@ -Makefile -Makefile.in -evolution-guide -evolution-guide.junk -evolution-guide.log -evolution-guide.ps -evolution-guide.dvi -evolution-guide.tex -fig/*.eps \ No newline at end of file diff --git a/doc/C/Makefile.am b/doc/C/Makefile.am deleted file mode 100644 index 15f1e047b6..0000000000 --- a/doc/C/Makefile.am +++ /dev/null @@ -1,59 +0,0 @@ -evolution_helpdir = $(datadir)/gnome/help/evolution/C - -SGML_FILES = \ - apx-authors.sgml \ - apx-bugs.sgml \ - apx-fdl.sgml \ - apx-gloss.sgml \ - config-prefs.sgml \ - config-setupassist.sgml \ - config-sync.sgml \ - evolution-guide.sgml \ - preface.sgml \ - usage-calendar.sgml \ - usage-contact.sgml \ - usage-mail.sgml \ - usage-mainwindow.sgml \ - usage-sync.sgml - - -EXTRA_DIST = \ - $(SGML_FILES) - -all: evolution-guide - -evolution-guide: $(SGML_FILES) - -db2html evolution-guide.sgml - -dist-hook: - mkdir $(distdir)/evolution-guide - -cp evolution-guide/*.html evolution-guide/*.css $(distdir)/evolution-guide - mkdir $(distdir)/fig - -cp fig/*.png $(distdir)/fig - mkdir $(distdir)/evolution-guide/stylesheet-images - -cp evolution-guide/stylesheet-images/* $(distdir)/evolution-guide/stylesheet-images - -install-data-local: evolution-guide - $(top_srcdir)/mkinstalldirs $(DESTDIR)$(evolution_helpdir) - -for file in $(srcdir)/evolution-guide/*.html $(srcdir)/evolution-guide/*.css; do \ - basefile=`basename $$file`; \ - $(INSTALL_DATA) $$file $(DESTDIR)$(evolution_helpdir)/$$basefile; \ - done - - $(top_srcdir)/mkinstalldirs $(DESTDIR)$(evolution_helpdir)/fig - -for file in $(srcdir)/fig/*.png; do \ - basefile=`basename $$file`; \ - $(INSTALL_DATA) $$file $(DESTDIR)$(evolution_helpdir)/fig/$$basefile; \ - done - - $(top_srcdir)/mkinstalldirs $(DESTDIR)$(evolution_helpdir)/stylesheet-images - -for file in $(srcdir)/evolution-guide/stylesheet-images/*; do \ - basefile=`basename $$file`; \ - $(INSTALL_DATA) $$file $(DESTDIR)$(evolution_helpdir)/stylesheet-images/$$basefile; \ - done - -evolution.ps: evolution.sgml - -db2ps $< - -evolution.rtf: evolution.sgml - -db2rtf $< diff --git a/doc/C/apx-authors.sgml b/doc/C/apx-authors.sgml deleted file mode 100644 index 89f0dd6bc5..0000000000 --- a/doc/C/apx-authors.sgml +++ /dev/null @@ -1,75 +0,0 @@ - - Authors - - Evolution was written by: - - Seth Alves: alves@helixcode.com - Anders Carlsson: andersca@gnu.org - Damon Chaplin: damon@helixcode.com - Clifford R. Conover: rusty@zootweb.com - Miguel De Icaza: miguel@helixcode.com - Radek Doulik: rodo@helixcode.com - Arturo Espinoza: arturo@nucleu.unam.mx - Larry Ewing: lewing@helixcode.com - Bertrand Guiheneuf: bertrand@helixcode.com - Tuomas Kuosmanen: tigert@gimp.org - Christopher J. Lahey: clahey@helixcode.com - Matthew Loper: matt@loper.org - Federico Mena: federico@helixcode.com - Eskil Heyn Olsen: deity@eski.dk - Nat Friedman: nat@helixcode.com - Ettore Perazzoli: ettore@helixcode.com - Jeffrey Stedfast: jeff@helixcode.com - Russell Steinthal: rms39@columbia.edu - Peter Teichman: peter@helixcode.com - Chris Toshok: toshok@helixcode.com - Peter Williams: peter@newton.cx - Dan Winship: danw@helixcode.com - Michael Zucchi: notzed@helixcode.com - -and other dedicated GNOME programmers. - - - The Evolution code owes a great debt - to the GNOME-pim and - GNOME-Calendar applications, and to - KHTMLW. The developers of - Evolution acknowledge the efforts - and contributions of all who worked on those projects. - - - - For more information please visit the - Evolution Web page. Please send all comments, - suggestions, and bug reports to the GNOME bug tracking - database. Instructions for submitting bug reports can be - found on-line at - http://bugs.gnome.org/Reporting.html. You can also use - command bug-buddy for submitting bug reports. - - - This manual was written by Aaron Weber - (aaron@helixcode.com) and Kevin Breit - (battery841@mypad.com) 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 - docs@gnome.org. You can also add your comments - online by using GNOME Documentation - Status Table. - - - - - - - - diff --git a/doc/C/apx-bugs.sgml b/doc/C/apx-bugs.sgml deleted file mode 100644 index e4a96a8155..0000000000 --- a/doc/C/apx-bugs.sgml +++ /dev/null @@ -1,23 +0,0 @@ - - - Known bugs and limitations - - - This appendix describes known bugs and limitations of - Evolution. Please use the GNOME - Bug Report Tool (known as - bug-buddy at the command line) if you find one - we have not listed. - - - - - Evolution is still beta software, so the bug tracking is best - left to the bugzilla system and to the programmers. However, - there are a number of limitations that will not be addressed - before version 1.0. The most notable are: Import of Microsoft - Outlook .pst files, and compatibility with the Microsoft - Exchange protocol. - - - diff --git a/doc/C/apx-gloss.sgml b/doc/C/apx-gloss.sgml deleted file mode 100644 index 129020aa3d..0000000000 --- a/doc/C/apx-gloss.sgml +++ /dev/null @@ -1,459 +0,0 @@ - - - Glossary - - - Attachment - - - Any file sent along with an email. Attachments may be embedded in - a message or appended to it. - - - - - - Automatic Indexing - - - Pre-sorting procedure that allows - Evolution to refer to data quickly. - It enables faster searches and decreases memory usage for - data displays. - - - - - - Bcc (Blind Carbon Copy) - - - A way of addressing a message. Bcc is used to send a group of - people an e-mail, while hiding their names and addresses from each - other. - - - - - - Cc (Carbon Copy) - - - Carbon-copies are used to send a 3rd party a copy of the e-mail, - so they an keep up to date on a conversation, without being in the - To: list. - - - - - - Conduit - - - A synchronization conduit is a small application which controls - the transfer of data between a handheld device and a desktop - computer. - - - - - - - Druid - - - A tool which guides a user through a series of steps, usually to - configure or set up a program. Equivalent to "Assistant" and - "Wizard." - - - - - - Emoticon - - - Also called "smileys," emoticons are the little sideways faces made - of colons and parentheses which people use to convey emotion in email. - Examples: :-) or ;( . - - - - - - Evolution - - - Evolution is the GNOME - groupware application. - - - - - - Execute - - - To run a program. Any file that can be run is called an - executable. Evolution can download - executable attachments, but before they can be run, the files must - be marked as executable with a shell or file manager. This - security precaution prevents the automatic or accidental execution - of malicious programs. For more information on executables and file - permissions, see the documentation for your file manager or shell. - - - - - - - File Tree - - - A way of describing a group of files on a computer. With the - perversity typical of computer (and especially Unix and Linux) - nomenclature, the top of the tree is called the root directory, - and denoted by /. - The rest of the "branches" spread downwards from the root. Don't - confuse the root directory with the root - account, or root's home directory, - /home/root. - - - - - - Filter - - - Within Evolution, a filter is a method - of sorting mail automatically. You can create filters to perform - one or more actions on a message that meets any (or all) of a wide - range of criteria. - - - - - - Forward - - - the user can send a third party a message - which was sent to the user originally. - - - - - - Groupware - - - Groupware is a term describing an application which helps groups - of people work together. Typically, a groupware application will - have several productivity features built into one program. - - - - - - Haiku - - - A traditional Japanese form of poetry. The poems are three lines - long, with first and last lines having five syllables, and the - second line seven syllables. - - - - - - HTML - - - Hyper-text Markup Language(HTML) is a language - for describing page layout in electronic documents like web pages, - help files, and email messages. HTML can be used in email and - news posts to insert images and apply text treatments. - - - - - - Hot Key - - - Hot-keys are keyboard combinations used to do actions on a - computer instead of using the mouse to do the same action. - Hot-keys can speed up computer usage. - - - - - - iCal - - - iCal is the program which - Evolution uses to manage the calendar - section. - - - - - - IMAP - - - Depending upon whom you ask, IMAP stands for the Internet Mail - Access Protocol, or the Interim Mail Access Protocol. Whatever it - stands for, it allows access to email which is typically (although - not always) stored remotely on a server rather than on a local - hard disk. Often contrasted with POP. - This will not be on the test. - - - - - - - Inline - - - Displayed as part of a message or other document, rather than - attached as a separate file. Contrast with Attachment. - - - - - - LDAP - - - LDAP, the Lightweight Directory Access Protocol, allows a client - to search through a large database of addresses, phone numbers, - and people stored on a server. - - - - - - Mail Client - - - A mail client is the application with which a person reads and - sends e-mail. Its counterparts are the various types of mail - servers, which handle user authentication and direct messages from - sender to recipient. - - - - - - - Minicard - - - A format for the display of contact data. Similar in appearance - to a small business card. - - - - - - Nautilus - - - Nautilus is the next generation file - manager for GNOME being written by Eazel. - - - - - - Nickname - - - An alias for an e-mail address. - - - - - - POP - - - POP, the Post Office Protocol, is a mechanism for email - transport. In contrast to IMAP, it is used only to get mail from - a server and store it locally on your hard disk. - - - - - - Protocol - - - An agreed-upon method of communication, especially one for - sending particular types of information between computer systems. - Examples include POP (Post Office Protocol), for email, and HTTP - (HypterText Transfer Protocol), for web pages. - - - - - - - - Regular Expression - - - A regular expression, or "regex", is a way of describing a - string of text using metacharacters or wild-card symbols. For - example, the statement fly.*so[a|u]p means - "any phrase beginning with 'fly' and ending in 'soup' or - 'soap'". If you searched for that expression, you'd find both - "fly in my soup" and "fly in my soap." There's not room here to - go into depth, but if you want, have a look at the documentation - for the grep command. - - - - - - Script - - - A program written in an interpreted (rather than compiled) - language. Often used as a synonym for "macro," to denote a series - of pre-recorded commands or actions within an application. - - - - - - Sendmail - - - As its name implies, sendmail is a - program which sends mail. Evolution - can use it instead of SMTP; some people - prefer it because it offers more flexibility, but is more - difficult to set up. - - - - - - - Shortcut Bar - - - A portion of Evolution which offers - users fast access to the most frequently used portions of the - application. - - - - - - Signature - - - In email terms, a signature is a piece of text placed at the end - of every email sent, like a hand-written signature at the bottom - of a written letter. A signature can be anything from a favorite - quotation to a link to a web page; courtesy dictates that it be - fewer than four lines long. - - - - - - SMTP - - - This is the most common way of transporting mail messages from - the client's computer (you) to the server. SMTP stands for - Simple Mail Transfer Protocol. - - - - - - Spam - - - Useless, unsolicited e-mail. Spam normally comes in forms of - chain letters and advertisements for unscrupulous or clueless - companies. Messages that are merely useless are called "opt-in - newsletters." - - - - - - - Tool-Tip - - - A small box of explanatory text which appears when the mouse - pointer is held motionless over a button or other interface - element. - - - - - - - - - Virus - - - A malicious program which inserts itself into others so that it will be - executed, allowing it to spread to still more programs and other computers. - A virus can cause substantial damage by clogging networks or disk drives, - deleting files, or opening security holes. - - - - - - vCard - - - A file format for the exchange of contact information. When you - get an address card attached to an email, it's probably in vCard - format. Not to be confused with vFolder. - - - - - - vFolder - - - An email organization tool. vFolders allows you to create a folder - that contains the results of a complex search. Folder contents are - are updated dynamically. - - - - - - - - - - - - - - - - - - - diff --git a/doc/C/config-prefs.sgml b/doc/C/config-prefs.sgml deleted file mode 100644 index 157b61e1cc..0000000000 --- a/doc/C/config-prefs.sgml +++ /dev/null @@ -1,646 +0,0 @@ - - - - Advanced Configuration - - Perhaps your mail server has changed names. Perhaps you've - grown tired of a certain layout for your appointments. - Whatever the reason, you want to change your - Evolution settings. This chapter - will tell you how to do just that. - - - - Mail Settings - - To change your mail settings, select - Settings Mail - configuration in the Inbox. This - will open the mail preferences window, - illustrated in . Mail - preferences are separated into several categories: - - - Identities - - - This allows you to create and alter one or more - identities for your email. - - - - - Sources - - - This tab lets you tell - Evolution where to get the - mail sent to you, and how to get it. - - - - - - Mail Transport - - - This tab lets you tell - Evolution how to send mail. - - - - - - News Servers - - - If you would like to use - Evolution to read newsgroups, - you can specify your news server preferences here. - - - - - - Other - - - Miscellaneous mail and news settings, such as HTML - handling preferences, and how long - Evolution should wait before - marking a message read. - - - - - - - - -
- Mail Preferences Dialog - - Setting mail preferences - - - -
- - - - - Identity Settings - - If you have only one email account, or send email from only - one address, you will only need to configure one identity. If - you want, however, you can have multiple identities. This - can be useful if you want to keep personal and professional - email separate, or if you wear several hats at work. - - - - To add a new identity, simply click - Add. To alter an existing identity, - click on it in the Identity tab of the - Preferences window, and then click - Edit. - - - - Evolution will then present you - with a dialog box containing four fields: - - - - Full Name: by default, this is the - same name as the full name described in your user - account on your computer. You can select another if you - wish. - - - - - Email address: Enter your email - address in this space. - - - - - Organization: If you send email as - a representative of a company or other organization, - enter its name here. - - - - - Signature file: You may choose a - small text file to be appended to every message that you - send. Typically, signature files include address or - other contact information, or a favorite quotation. - It's good form to keep it to four lines at the maximum. - - - - - - - - Network Settings - - In order to send mail with - Evolution, 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 program, you can almost certainly use the same - settings as you did with that program. Network-related - settings are in the Mail Sources and - Mail Transport tabs. - - - - Mail Sources - - The Mail Sources tab allows you to - edit, add, or delete methods of retrieving mail from - servers. Clicking on Add or - Edit will bring up a dialog box to - offer you the following options: - - - Mail source type: - - - Select from IMAP or POP servers, or Unix-style - mbox - or mh - files. - - - - - Server: - - - Enter the name of the mail source server in this - field. If you use an may or may not be the same as your - SMTP server. - - - - - Username: - - - Enter the user name for the account you have on the - server-- this should the part of your email address - before the @. If you use - mbox - or mh - files as your mail source, you do not need to enter - a username. - - - - - Authentication: - - - Tell Evolution how to - verify your identity with the server. Your options - vary depending upon the type of server you are - using, and the ways it is configured. Given the - name of a server, - Evolution can detect what - sorts of authentication it offers. - - - - - Test Settings - - - Click this button to have - Evolution check to see if - mail sources are configured correctly. - - - - - - - If you have several mail sources, clicking Get - Mail will refresh any IMAP, - mh, or - mbox - listings and check and download mail from all POP servers. - In other words, Get Mail gets your - mail, no matter how many sources you have, or what types - they are. - - - - - Mail Transports - - The Mail Transports tab lets you set - how you will send mail. Evolution currently supports two - mail transport options: SMTP, which - uses a remote mail server, and - sendmail, which uses the - sendmail program on your local - system. Sendmail is more - difficult to configure, but offers more flexibility than - SMTP. - - - To use SMTP, you'll need to enter the - name of your SMTP server. It may have the same name as - your mail source server. - - - Evolution can attempt to - determine if you have entered a valid server name. To - have it do so, click the Test - Settings button. - - - - - News Servers - - Newsgroups are so much like mailing lists that there's no - reason not to keep them right next to your mail. When you - first select the News Servers tab, - you will see a blank box with the three familiar buttons - on the right: Add, - Edit, and - Delete. - - - Click Add to add a news server; you - will be prompted for its name. Enter the name, click - OK, and you're done. You can have - as many mail servers as you like, of course. News servers - will appear next to your IMAP servers in the - folder bar. - - - - - Other Mail Preferences - - Not everything fits neatly into categories. This tab - contains some miscellaneous configurations that don't have - too much to do with each other. - - - - - Send messages in HTML format - - - If you check this box, you will send - messages as HTML by default. If you leave it unchecked, your - messages will be sent without HTML formatting unless you select - Format HTML - in the message composer. - See - for more information about HTML mail. - - - - - Mark Messages as Seen After - - - When you click on a message, - Evolution will wait a - moment before marking it as seen. You can set the - delay, in milliseconds, here. - - - - - Folder Format - - By default, - Evolution saves its mail - in the - mbox - format. You can switch to the - mh - format if you like. Note that this is an advanced - feature and may cause you to lose some messages, so - you should probably make a backup of your - evolution - directory first. In addition, it will take quite - some time if you have a large mailbox. - - - - - - - - - Configuring the Calendar - - To set your calendar preferences, select - Settings - Calendar - Configuration from the Calendar - view. This will open up the - Preferences window. It contains four - tabs: Time display, - Colors, To Do List - and Alarms. The calendar - preferences window is illustrated in . - - -
- Calendar Preferences Dialog - - If this worked on my job as well as my calendar... - - - -
- - - - - Time Display Settings - - The Time display tab lets you set the - following: - - - Time format - - You may choose between twelve-hour (AM/PM) and - twenty-four hour time formats here by clicking the - appropriate radio button. - - - - - Weeks start on - - You can set weeks to start on Sunday or on Monday. - - - - Day range - - - When does your work day start, and when does it end? - In the day and week views, - Evolution displays all the - hours in the range you select here, even if there are - no appointments for those times. Of course, you can - still schedule an appointment outside of these hours, - and if you do, the display will be extended to show - it. - - - - - - - - Calendar Colors - - The colors tab allows you to decide - what color your calendar will be. The tab consists of a - sample calendar on the right and a list of ten items that can - be colored in different ways. If you click on the color - button to the right of each item, you will bring up a - color-selector window where you can choose to alter that - color. By clicking OK in the color - selection dialog, you can see the results of the color on the - sample calendar. - - The display elements whose color you can set are: - - - - - Outline: The lines between days - and at the top of the display. - - - - - Headings: Text color for day - and month names and other headings. - - - - - Empty days: This is the - background color for any time slots in which you have no appointments. - - - - - - Appointments: This is the - background color for any time slots in which you have appointments. - - - - - Highlighted day: The - background color for a selected time slot. - - - - - - - Day numbers: Text color for date numbers. - - - - - - - Current day's number: Text color for today's date. - - - - - To-Do item that is not yet - due: Text color for To-Do list items that are - not yet due. (Or maybe background color? find out!) - - - - - - To-Do item that is due today: - Text color for today's tasks. - - - - - To-Do item that is overdue: - Text color for overdue tasks. - - - - - - - - - To Do List Settings - - You can choose what information the To Do list displays and the - way it is displayed. The two areas of the To Do - List tab offer several options each: - - - Show on To Do List - - - This box contains three items. If you select the - check boxes next to them, that information will appear - in the To Do list for each task it contains: - - - Due Date - - - Time Until Due - - - Priority - - - - - - - Style Options - - - Select among the following checkboxes to determine - how your To Do list will look: - - - Highlight overdue items - - - Highlight items due today - - - Highlight not yet due items - - - - - - - - - - - Alarms Settings - - The alarms tab enables you to select from three boxes: - - - Beep on display alarms: select - this box to have Evolution beep - at you for any alarms you have set. If you leave this box - unchecked, Evolution will only - alert you to events by opening a dialog box. These beeps - are distinct from full-fledged audio alarms. - - - - Audio alarms timeout after: - Select this button to have your audio alarms stop - automatically after a certain number of seconds. - - - Enable snoozing for: If you - would like to have the option to tell - Evolution to repeat an alarm in - a few minutes, select this button and decide how long - you'd like it to wait. - - - - - - - - - - Managing the Contact Manager - - To set the behavior of your Contact Manager, click on the - Contact Manager tab in the - Preferences window. - - - You can set the following options: - - - - Adding Directory Servers - - To add a new LDAP server to your available contact - folders, select Actions - New Directory Server - . This brings up a small dialog box which - will let you enter the following options: - - - Name — any name you choose for the server. - - - - Description — a longer description of the server. - - - - LDAP Server — the network address of the server. - - - - Port Number — by default, the port number is 389. - - - - Root DN — enter the root DN here. - - - - - - - - - - General Preferences - - Additional configuration options will be covered here, as - they become available. - - - - - - - - - diff --git a/doc/C/config-setupassist.sgml b/doc/C/config-setupassist.sgml deleted file mode 100644 index b9b72b568a..0000000000 --- a/doc/C/config-setupassist.sgml +++ /dev/null @@ -1,213 +0,0 @@ - - Easy Setup with the Setup Assistant - - The first time you try to use email, the mail setup assistant - will ask you for some basic information, so - Evolution can let you use email. If - you prefer more detailed configuration, or if you want to make - changes to an existing email setup, see . - - - - Mail Setup - - The first time you try to send or receive mail with - Evolution, the mail - setup assistant will pop up to help you with your - email preferences. If you don't plan to use email, or if - you'd rather deal with your email preferences later, click - Cancel. - - - - - - The setup assistant (sometimes called a - Druid, by analogy with the "Wizards" - that some other programs use) will guide you through the - network configuration process. It will ask you for some - basic information; your system administrator or ISP should - have the answers you'll need. The mail setup assistant is - pictured in . - - - - -
- Mail Setup Assistant - - Evolution Main Window - - - -
- - - - - The assistant will ask you for the following information: - - - - Name: - Your full name. - - - - Email address: - - Your complete email address. - - - - - Organization: - - - Any organization you represent, or the company where you - work. Leave this blank if you wish, or type "My own bad - self" so people know your opinions are yours alone. - - - - - - Signature File: - - - A text file appended to any email you send. A signature - file typically consists of your name and email address, - or a quotation you like. It's good form to keep your - "sig" on the short side: four lines is plenty. Remember, - this is attached to every email you send. - - - - - - Mail source type: - - - Evolution supports several - mail sources: POP and - IMAP servers, and UNIX-style - mbox and - mh files. - POP servers retrieve your mail and store it on your - local system so you can refer to it even when not - connected to a network; IMAP - servers store the mail on the server so you can access - it from multiple locations; - mbox> - files are used by your computer for internal mail, and - may be useful if you want to switch from another email - client such as Spruce or - Netscape Communicator. Ask - your system administrator which you should use, or keep - guessing until one works. You may use multiple sources - if you wish; see for more - information. - - - If you decide not to have - Evolution use any servers, - the remaining items are not relevant; you only need to - point to the location of the files you wish to access. - - - - - - Server: - - - This should be the name of the server where you get - incoming mail. It may (or may not) be the same as the - server where you send your outgoing mail. - - - - - - Username: - - - Enter the username for your mail server account, if you - have one. In almost all cases, this is the part of your email - address before the @ character, and - Evolution has selected that - value as the default. If you have a different username, - you can enter it here. - - - - - - Authentication: - - - Select the type of authentication you will use. You can - click Detect supported types to - find out which authentication protocols your network - allows. - - - - - - Mail Transport: - - - This is the mail sending protocol you will want to use. - Evolution supports both - SMTP and - sendmail; SMTP is by far the - more common. - - - - - - - To learn how to configure Evolution - in greater detail, or to change preferences once you have set - them, see . - - - - - - - - - - - - - diff --git a/doc/C/config-sync.sgml b/doc/C/config-sync.sgml deleted file mode 100644 index 0445b474c4..0000000000 --- a/doc/C/config-sync.sgml +++ /dev/null @@ -1,124 +0,0 @@ - - Setting up your synchronization system - - Synchronization presents you with two issues you'll need to - deal with. - - - Your computer needs to recognize and access your handheld. - At this time, Evolution only - supports Palm-OS devices like the PalmPilot and the - Handspring Visor. - - - You should decide what sort of synchronization behavior you - want. - - - - - - If you haven't used a handheld device with your computer - before, you'll need to run the GNOME Control - Center and make sure that Pilot - Link is properly configured. Then, select the - Evolution conduits under the - Pilot Conduits section of the Control - Center. - - - Once your computer and your Palm-OS device are talking happily - to each other, you'll have to decide what exactly you want - them to do with the data they exchange. Your options may vary - depending on the conduit, but typically they will be: - - - - Disabled - - - Do nothing. - - - - - - Synchronize - - - Copy new data from the computer to the handheld, and - from the handheld to the computer. Remove items - that were on both systems but have been deleted on - one. - - - - - - Copy From Pilot - - - If there is any new data on the the handheld device, - copy it to the computer. - - - - - - Copy To Pilot - - - Copy new data from the computer to the handheld. - - - - - - Merge From Pilot - - - Copy new data from the handheld to the computer, and - remove any information from the computer that has - been deleted on the handheld. - - - - - - Merge To Pilot - - - Copy new data from the computer to the handheld, and - remove any information from the handheld that has - been deleted on the computer. - - - - - - - - Select a behavior for each conduit available. For the most - part, you'll want to stick with - Synchronize. Then, put your handheld on - its cradle and press the synchronization button. - - - - - - Data Loss Prevention - - It's always a good idea to make a backup. To do that, - make a copy of your - ~/evolution directory. - - - - - - - - - diff --git a/doc/C/evolution.sgml b/doc/C/evolution.sgml deleted file mode 100644 index 114f2e87d9..0000000000 --- a/doc/C/evolution.sgml +++ /dev/null @@ -1,145 +0,0 @@ - - - - - - - - - - - - - - - - -]> - - - - - - - A User's Guide to Evolution - - AaronWeber - KevinBreit - - - 2000 - Ximian, Inc., - Kevin Breit - - - - - - 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 no Invariant - Sections, no Front-Cover Texts, and no Back-Cover Texts. You - may obtain a copy of the GNU Free Documentation - License from the Free Software Foundation by - visiting their - Web site or by writing to: Free Software Foundation, - Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, - USA. - - - Many of the names used by companies to distinguish their - products and services are claimed as trademarks. Where those - names appear in any GNOME documentation, and those trademarks - are made aware to the members of the GNOME Documentation - Project, the names have been printed in caps or initial caps. - - - - - This is version 0.9 of the Evolution manual. - - - - - &PREFACE; - - - Using Evolution - - - Part one of the Evolution manual - describes how to use Evolution for - email, contact management, and appointment and task - scheduling. You'll find as you go along that there's more - than one way to do things, and you can pick whichever method - you like best. - - - - &USAGE-MAINWINDOW; - &USAGE-EXEC-SUMMARY; - &USAGE-MAIL; - &USAGE-CONTACT; - &USAGE-CALENDAR; - - &USAGE-SYNC; - &USAGE-PRINT; - - - Configuring and Managing Evolution - - - Evolution is highly configurable. - Usually, when developers say that, they mean that they didn't - test it out thoroughly and have left it to other programmers - to "configure" themselves a working system. In the case of - Evolution, "configurable" means - what it ought to. It means that, while you can expect the - program to work perfectly well in its default settings, it's - also easy to alter its behavior in a wide variety of ways, so - that it fits your needs exactly. This part of the book will - describe that process, from the quickest glimpse of the Setup - Assistant to an in-depth tour of the preferences dialogs. - - - - &CONFIG-SETUPASSIST; - &CONFIG-PREFS; - &CONFIG-SYNC; - - - - Comprehensive Menu reference - - - The following reference covers all, or nearly all, of the - menus and menu commands that - Evolution has to offer you. - - - &MENUREF; - - - &APX-GLOSS; - &APX-BUGS; - &APX-AUTHORS; - - - - - - - - - - - - diff --git a/doc/C/fig/calendar.png b/doc/C/fig/calendar.png deleted file mode 100644 index c9703f4903..0000000000 Binary files a/doc/C/fig/calendar.png and /dev/null differ diff --git a/doc/C/fig/config-cal.png b/doc/C/fig/config-cal.png deleted file mode 100644 index 25b5b68621..0000000000 Binary files a/doc/C/fig/config-cal.png and /dev/null differ diff --git a/doc/C/fig/config-mail.png b/doc/C/fig/config-mail.png deleted file mode 100644 index cd8543d94e..0000000000 Binary files a/doc/C/fig/config-mail.png and /dev/null differ diff --git a/doc/C/fig/contact-editor.png b/doc/C/fig/contact-editor.png deleted file mode 100644 index 988ad2f918..0000000000 Binary files a/doc/C/fig/contact-editor.png and /dev/null differ diff --git a/doc/C/fig/contact.png b/doc/C/fig/contact.png deleted file mode 100644 index a9ed02251a..0000000000 Binary files a/doc/C/fig/contact.png and /dev/null differ diff --git a/doc/C/fig/filter-assist-fig.png b/doc/C/fig/filter-assist-fig.png deleted file mode 100644 index 5248e0effe..0000000000 Binary files a/doc/C/fig/filter-assist-fig.png and /dev/null differ diff --git a/doc/C/fig/filter-new-fig.png b/doc/C/fig/filter-new-fig.png deleted file mode 100644 index a8b41ca678..0000000000 Binary files a/doc/C/fig/filter-new-fig.png and /dev/null differ diff --git a/doc/C/fig/mail-composer.png b/doc/C/fig/mail-composer.png deleted file mode 100644 index 22c16365b5..0000000000 Binary files a/doc/C/fig/mail-composer.png and /dev/null differ diff --git a/doc/C/fig/mail-druid-pic.png b/doc/C/fig/mail-druid-pic.png deleted file mode 100644 index f29f3e77be..0000000000 Binary files a/doc/C/fig/mail-druid-pic.png and /dev/null differ diff --git a/doc/C/fig/mail-inbox.png b/doc/C/fig/mail-inbox.png deleted file mode 100644 index b4f18640b4..0000000000 Binary files a/doc/C/fig/mail-inbox.png and /dev/null differ diff --git a/doc/C/fig/mainwindow-pic.png b/doc/C/fig/mainwindow-pic.png deleted file mode 100644 index 28bf487bf9..0000000000 Binary files a/doc/C/fig/mainwindow-pic.png and /dev/null differ diff --git a/doc/C/fig/print-dest.png b/doc/C/fig/print-dest.png deleted file mode 100644 index 464705711e..0000000000 Binary files a/doc/C/fig/print-dest.png and /dev/null differ diff --git a/doc/C/fig/print-preview.png b/doc/C/fig/print-preview.png deleted file mode 100644 index 7f9a8d661a..0000000000 Binary files a/doc/C/fig/print-preview.png and /dev/null differ diff --git a/doc/C/fig/vfolder-createrule-fig.png b/doc/C/fig/vfolder-createrule-fig.png deleted file mode 100644 index 162bebf48c..0000000000 Binary files a/doc/C/fig/vfolder-createrule-fig.png and /dev/null differ diff --git a/doc/C/menuref.sgml b/doc/C/menuref.sgml deleted file mode 100644 index d82191cb17..0000000000 --- a/doc/C/menuref.sgml +++ /dev/null @@ -1,1470 +0,0 @@ - - - - Menu Reference - - Evolution's menus may not hold the - secret to happiness, they do hold every ability that - Evolution has. This section will serve - as a reference for all those menus, and the capabilites that they - offer you. - - - In addition, the editor tools for messages, appointments, and - contacts all have menu bars of their own. From left to right, the - menus available to you when you are reading mail are: - File, Edit, - View, Settings, - Message, Folderand - Help. - - - - Menus in Evolution are - context-sensitive, which means that they vary depending on what - you're doing. If you're reading your mail, you'll have - mail-related menus; for your calendar, you'll have - calendar-related menu items. Some menus, of course, like - Help and File don't much, if - at all, because they have more universal functions. But you'd - never mark an address card as "read," or set the recurrence for an - email message you've recieved. depending on whether you're looking - at mail, contacts, or calendar information. - - - - - - Menus that are the same everywhere - - The File and Help menus in - the main Evolution window do not - change, because they refer to universal items. Other menus have - contents that change depending on context. - - - - File Menu - - - - - New... Submenu - - - - Folder — - Create a new folder. See - for more information about folders. - - - Shortcut — - Create a new Shortcut in the Shortcut Bar. - - - Mail Message — - Compose a new mail message. Covered in - . - - - Appointment — - Enter a new appointment in your calendar. See for more information. - - - Task — - Enter a new to-do item in your taskpad. Covered in - . - - - - - - - Go to Folder - - View the items in a particular folder. - - - - - Create New Folder - - This item doesn't belong here any more. - - - - - Print Message - - Print the current message. - - - - - Exit - - Quit using Evolution. - - - - - - - - The Help Menu - - - - Help Index - - Displays the table of contents for this document. - - - - Getting Started - - A quick look around, and a summary of the things - Evolution can do for you. - - - - Using the Mailer - - An in-depth tour of Evolution Mail. - - - - Using the Calendar - - A step-by-step guide to using the Calendar. - - - - Using the Contact Manager - - Find your way around the Contact Manager. - - - - Submit Bug Report - - If you don't report them, they can't fix them. Select this item to let the - developers know what's wrong. - - - - About Evolution - - Displays a window with information about the application and its authors. - This has the same information as . - - - - - - - - - Executive Summary Menus - - We'll leave this section blank until the UI stabilizes a little - more. - - - - - - - Mail Menus - - Evolution Mail has more specialized - menus, and more specialized menu items, than any other part of - the application. - - - - The Edit Menu - - This menu is currently empty. - - - - - The Mail View Menu - - This menu lets you control the way - Evolution displays your information - for you. - - - Show Shortcut Bar - - Toggle the shortcut bar on and off with this item. - - - - - Show Folder Bar - - Toggle the folder bar on and off with this item. - See for - more information about the folder bar. - - - - - Threaded Message List - - This item controls whether your message list is displayed by thread - or by other criteria. The default order is by date; see - for information about the - order of the message list. - - - - - - - - The Mail Settings Menu - - - - Mail Filters - - Edit your mail filters here. - See - for more information about mail filtering. - - - - - Virtual Folder Editor - - Create, edit, and delete Virtual Folders (vFolders) - with this tool. - To learn about using vFolders with mail, see - . - - - - - Mail Configuration - - Tools for setting up all your mail account preferences. - - - - - Manage Subscriptions - - Tools for newsgroup and IMAP folder subscriptions. - - - - - Forget Passwords - - This item will cause Evolution - to forget what your password is. - - - - - - - - - The Mail Folder Menu - - The items in this menu relate to - Evolution mail folders. - - - You can: - - - - Mark all as Read - - Evolution keeps track of which messages - you've seen; to mark everything in a folder as read, choose this item. - You can mark a single message as read by right-clicking it in the message bar. - - - - - Delete All - - This is a favorite item of everyone with too much junk-mail: one click, and it - deletes every message in the current folder. - - - - - - Expunge - - Empties the trash folder, erasing messages permanently. - Once you've done this, they're gone for good. - - - - - Configure Folder - - Use this item to set the file format in which - Evolution stores mail. You - can choose from standard UNIX-style - mbox - files, or the - mh format. - Converting large mailboxes may take a long time, and - it's a good idea to have a backup copy beforehand. - - - - - - - - - The Mail Message Menu - - The items in this menu relate to - Evolution mail messages. Most of - them require you to have a message selected, and are also - available by right-clicking on a message in the message - list. - - - - - - - Open in New Window - - Displays the selected message in a new window. - - - - - Edit Message - - Open the selected message in the message composer. You - can only edit a message you have written: drafts and messages in - the Sent box. - - - - - Print Message - - Displays the Print Preview window, - ready for printing. - - - - - Reply to Sender - - Opens a message composition window addressed to the - author of the message. Covered in detail in - . - - - - - Reply to All - - Opens a message composition window addressed to the - author of the message and all known recipients. - Covered in detail in . - - - - - Forward - - Appends the body of the selected message to a new message. - Covered in detail in . - - - - - Delete Message - - Marks a message for deletion. - - - - - Move Message - - Choose a folder in which to place this message. - - - - - Copy Message - - Copy the selected message to another folder. - - - - - VFolder on Subject - - This item, and the three that follow it, will create vFolders - which you may customize further or save as-is. This one will - create a vFolder which will display all messages that contain the - subject line of the selected message. - - - - - VFolder on Sender - - Creates a vFolder to hold all messages from the sender of - the selected message. - - - - - - VFolder on Recipients - - Creates a VFolder to hold all messages addressed to the - recipient of the selected message. - - - - - Filter on Subject - - This item, and the three that follow it, will create Filters - for which you must select actions. You may keep the criteria as - they are, or alter them as you wish. This one will - create a filter which will affect all messages that contain the - subject line of the selected message. - - - - - Filter on Sender - - Creates a filter which affects all messages from the sender of - the selected message. - - - - - Filter on Recipients - - Creates a filter which will affect all messages addressed to the - recipient of the selected message. - - - - - - - - - The Message Heading Right-Click Menu - - At the top of the message list is the message list heading - bar; you can click on an individual heading — - Subject, for example, to have the - message list sorted by that attribute. However, if you right - click on a heading, you'll get the following menu: - - - - - - - Sort Ascending - - Sort the list, in ascending order, by the attribute you clicked. - - - - - Sort Descending - - Sort the list in descending order. - - - - - Unsort - - Undo any sorting by this attribute, and leave the message list sorted - by the previous one. - - - - - Group by this Field - - Instead of sorting the messages, group them in boxes. - - - - - Group by Box - If you have your messages grouped in - boxes, you can arrange the boxes as well, by choosing - this item. - - - - Remove this column - - Choose this to remove the column from the message list display. - - - - - Field Chooser - - Opens a palette of columns. You can drag the columns - you want from the palette into position in the - message list heading bar; red arrows appear - when you get close enough to a possibile position. - - - Your options are: - - - An Envelope which indicates whether a message has been read (closed for unread, open for read). - - - - An Exclamation Point for priority - - - - A Penguin which indicates something, although I'm not sure what. - - - - A Paper Clip which indicates that there is an attachment to the message. - - - - From, for the From field of a message. - - - Subject, for the Subject field of a message. - - - - Date, for the date and time a message was sent. - - - - Received, for the date and time you got the message. - - - - To, for the To field. - - - - Size, for a message's size. - - - - - - - - - Alignment - Use this item to decide upon the - alignment of the message attributes within their - columns. - - - - Best Fit - - Alters the width of the message list columns to maximize the amount of information displayed. - - - - - Format Columns... - - This item is not yet available. - - - - - - Customize - Views... Opens a - dialog box that lets you choose a complex set of - arrangements for your message list, so you can combine - sorting and grouping in as many ways as you like. - - - - - - - - - - The Message Composer Menus - - The message composition window has its own set of menus: - File, which controls operations on files and - data, Edit, for text editing, - Format, which controls the file format of - messages you send, View, to set how you view - the message, and Insert, which holds tools - for embedding files and other items in messages. Here's what's in them: - - - The Message Composer's File Menu - - - - Open - - Open a text file or a draft mail message. - - - - - Save - - Save a mail message as a text file. - - - - - Save As - - Choose a file name and location for - a message you want to save as a text file. - - - - - Save in Folder - - Save a message as a draft, rather than - as a separate text file. - - - - - Insert Text File - - Open a text file and insert it into - the current message. (FIXME: belongs under "Insert"). - - - - - Send Now - - Sends the message immediately. - - - - - Send Later - - Queue - - - - - Close - - Closes the message composer. If you have not done so, - Evolution - will ask you if you want to save your message. - - - - - - - The Message Composer's Edit Menu - - The Edit menu in the message composer - contains the following items. Keyboard shortcuts are listed - next to the items in the menus themselves. - - - - - Undo - - Undoes the last action you performed. - - - - - Redo - - If you change your mind about Undoing something, - you can always use this item. - - - - - Cut - - Removes the selected text from the text entry window and - retains it in the system "clipboard" memory, ready for pasting. - - - - - Copy - - Copies selected text to the system clipboard without deleting it. - The text can then be inserted elsewhere with the - Paste command. - - - - - Paste - - Inserts the contents of the system clipboard at the - location of the cursor. - - - - - Find - - Enter a phrase and find your match in your message body. - As with Find Regex, - Find Again, and - Replace, Evolution - will offer you the option to search forwards or backwards. - - - - - Find Regex - - If you are familiar with regular expressions, - often called "regexes," you can search for something more complicated, - using wildcards and boolean logic. - - - - - Find Again - - Repeats your last search. - - - - - Replace - - Enter a word or phrase and the word or phrase with which you'd like - to replace it. - - - - - Properties - - This item brings up the Message Composer Properties Capplet, - a portion of the GNOME Control Center that determines the - key bindings for the message composer. Help for this capplet is - available directly from the Control Center. - (FIXME: Write that help doc too) (FIXME: this is in the wrong place!) - - - - - - - - The Message Composer's Format Menu - - The Format menu has only one item: - - - HTML - - Toggles HTML mode for the message composer. When selected, - the message is displayed and sent in HTML. If you have written a - message in HTML and turn HTML off, most formatting will be lost. - Evolution will attempt to preserve spacing - and to remove formatting gracefully, however. - - - - - - - The Message Composer's View Menu - - The View menu controls the way messages are - displayed, and how much of the message, its headers, and - attachments appear. It contains: - - - Show Attachments - - Toggles the display of attachments. When this item is selected, - Evolution will create a separate pane - of the composition window to show what attachments you are appending - to the message. - - - - - - - The Message Composer's Insert Menu - - The Insert menu holds tools that allow you - to include images, horizontal rules, and other objects - in the body of your message. The tools are: - - - - Image - - This tool will prompt you to select an image file to - insert into your HTML message. For text messages, this - is the same as attaching an image file. - - - - - Link - - Opens the link creation window, - which lets you specify the URL and text description - for a link in your message. This only works with HTML - messages. - - - - - Rule - - Opens the horizontal rule creation dialog, which lets you - create an HTML horizontal rule. For more information, - see . - This tool only works with HTML messages. - - - - - Text File - - Open a text file and insert it into the current message. - This tool works with both plain text and HTML messages. - - - - - - - - - The Calendar Menus - - The Main window of the calendar has the same menus as the main - window of the mail client. However, their contents vary in a - number of ways. - - - The Calendar Edit Menu - - The contents of the Edit menu are currently so borked that I - refuse to document them right now. (That means FIXME). They - should be: - - - - Item - - Description - - - - Item - - Description - - - - - Item - - Description - - - - - - - The Calendar View Menu - - The Calendar's View menu contains the following items: - - - - Show Shortcut Bar - - Toggle the Shortcut Bar on and off with this item. - - - - - Show Folder Bar - - Toggle the folder bar on and off with this item. - See for - more information about the folder bar. - - - - - View By Day - - Switch to the day view for your calendar. - - - - - View Five Days - - View five calendar days at once. - - - - - View by Week - - Switch the calendar view to full week mode. - - - - - View By Month - - Look at a month at a time. - - - - - - - - The Calendar Settings Menu - - This menu is empty. - - - - - - - The Appointment Editor Menus - - The appointment editor has its own menus, to help you use its - wide-ranging abilities. - - - - The Appointment Editor's File Menu - - This menu contains several items, including a New submenu - that is identical to that in the - main window's file menu. - Its other contents are: - - - - Send - - Opens a mail message with the appointment attached to it. - - - - - - Save - - Save this appointment in the existing location and name. If you have not yet - chosen a location and name, this is the same as Save As. - - - - - - Save As - - Choose a location and name for this appointment, and save it. - - - - - Delete - - Deletes the appointment. - - - - - Move to Folder - - Chose a folder, and move the appointment into it. - - - - - - Copy to Folder - - Chose a folder, and put a copy of the appointment into it. - - - - - - Page Setup Submenu - - This menu contains two items: - - - Memo Style — - FIXME: What does this do? - - - - Define Print Styles — - FIXME: What does this do? - - - - - - - Print Preview - Shows you what your appointment will look - like if you print it. See - for details on printing and the Print Preview function. - - - - - - Print - - Prints the appointment without preview. - - - - - - Properties - - FIXME: What does this do? - - - - - - Close - - Close the appointment editor window. - - - - - - - - The Appointment Editor's Edit Menu - - FIXME: this menu is copied and pasted entirely from somewhere - else. - - - - - The Appointment Editor's View Menu - - This menu allows you to look at different appointments, and - set the way you look at them, without having to move back to - the Main Window. It contains: - - - - Previous - - The items in this submenu will take you to appointments - prior to the current one. (FIXME: describe). - - - - - Next - - The items in this submenu will take you to appointments - scheduled to occur after the current one. (FIXME: describe). - - - - - Calendar - - FIXME: What does this item do? - - - - - Toolbars - - The Toolbars submenu - allows you to choose which toolbars - are displayed in the - Appointment Editor. They are: - - - Standard — - Toggle the standard toolbar on and off. - - - - Formatting — - Toggle the formatting toolbar on and off. - - - - Customize — - Select the contents of the formatting and standard toolbars. - - - - - - - - - - The Appointment Editor's Insert Menu - - This menu contains: (FIXME: Insert Content Here) - - - File - - Choose a file to append to your appointment or appointment request. - - - - - - Item - - FIXME: ? - - - - - - Object - - FIXME: ? - - - - - - - - The Appointment Editor's Format Menu - - This menu contains two items, neither of which - have any functionality yet: - - - Font - - FIXME: ? - - - - - - Paragraph - - FIXME: ? - - - - - - - - The Appointment Editor's Tools Menu - - This menu contains four items, including the - Forms submenu, which allows you to - alter calendar forms and create your own entries. None of - this works yet, though. - - - - - Spelling - - Checks the spelling of your calendar entry. - - - - - Check Names - Checks the names listed here against - those in your address book. - - - - - - Address Book - - FIXME: ? - - - - - - Forms Submenu - - The Forms submenu lets you alter the - appearance of Calendar Forms. - - - - - - - - - The Appointment Editor's Actions Menu - - This menu contains: - - - - Schedule Meeting - - Brings up the Meeting Invitation window, - described in . - - - - - Cancel Invitation - - Cancels the event, notifying all attendees. You may be prompted - to specify an invitation message. - - - - - Forward as vCalendar - - Opens the message composer with the current event attached. - - - - - Forward as Text - - Opens the message composer with a text description of the current - event included in the message body. - - - - - - - - The Appointment Editor's File Menu - - This menu is empty. - - - - - - - Contact Manager Menus - - The contact manager has six menus: File, - Edit, View, - Settings, Tools, and - Help. - - - - Contact Manager Edit Menu - - This menu is empty. - - - - - - Contact Manager View Menu - - This menu contains the following items: - - - - Show Shortcut Bar - - Toggle the Shortcut Bar on and off with this item. - - - - - Show Folder Bar - - Toggle the folder bar on and off with this item. - See for - more information about the folder bar. - - - - - As Table / As Minicards - - View your contacts as a table. - When in table-view mode, this menu item reads - As Minicards, and changes the view - back to the minicard format. - - - - - - - - Contact Manager Tools Menu - - This menu contains one item: - - - - Search for - Contacts Brings up - the in-depth search window. describes how to use this - feature. - - - - - - - - - Contact Manager Tools Menu - - This menu contains only one item: - - - - New Directory Server Brings up - the in-depth search window. describes how to use this - feature. - - - - - - - - - The Contact Editor Menus - - This window has only one menu: the file menu. - - - - Contact Editor File Menu - - This menu contains five items: - - - - Save - - - - - - - Save As - - Allows you to save the contact as an external - file in the VCard format. - - - - - Print - - Prints the current contact. - - - - - - Delete - - Deletes the current contact. - - - - - - Close - - Closes the Contact Editor without saving. - - - - - - - - - - - - - - - - - diff --git a/doc/C/preface.sgml b/doc/C/preface.sgml deleted file mode 100644 index ddb6a0d2dd..0000000000 --- a/doc/C/preface.sgml +++ /dev/null @@ -1,438 +0,0 @@ - - - - - Introduction - - - What is Evolution, and What Can It Do for Me? - - Information is useless unless it's organized and accessible; - it's hardly even worth the name if you can't look at it and be - informed. - Evolution's goal is to make the - tasks of storing, organizing, and retrieving your personal - information easier, so you can work and communicate with - others. That is, it's a highly evolved groupware program, an integral - part of the Internet-connected desktop. On the inside, it's a - powerful database; on the outside, it's a tool to help you get - your work done. - - - Because it's part of the GNOME project, - Evolution is Free Software. The - program and its source code are released under the terms of - the GNU General - Public License (GPL), and the - documentation falls under the Free Documentation - License (FDL). For more information about - the GPL and the FDL, visit the Free Software Foundation's - website at http://www.fsf.org. - - - - This is a preview release - - Evolution is not complete, and - still has a lot of flaws. Please help improve it by - letting us know about them. You should do this by - submitting bug reports with the GNOME Bug - Report Tool (known as - bug-buddy at the command line). - - - - - - Evolution can help you work in a - group by handling email, address and other contact - information, and one or more calendars. It can do that on one - or several computers, connected directly or over a network, - for one person or for large groups. - - - The Evolution project has four - central goals: - - - - - The application must be both powerful and easy - to use. In other words, it needs a familiar - and intuitive interface that users can customize to their - liking, and users should have access to shortcuts for - complex tasks. - - - - - Evolution must meet and - exceed the standards set by other groupware products. - It must include support for major network protocols so that it can - integrate seamlessly with existing hardware and network - environments. - - - - - The project must support open standards and be open to - expansion, so that it can become a development platform - as well as an application. From the simplest scripting - to the most complex network and component programming, - Evolution must offer - developers an environment for cutting-edge application - development. - - - - - Data must be safe: Evolution - must not lose mail, corrupt mailbox files or other - data, execute arbitrary scripts, - or delete files from your hard disk. - - - - - - Evolution is designed to make most - daily tasks faster. 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. - Evolution makes displays faster and - more efficient, so searches are faster and memory usage is - lower. People who get lots of mail will appreciate advanced - features like Virtual Folders, - which let you save searches as though they were ordinary mail - folders. - - - - - - About This Book - - - This version of the Evolution - User's Guide is a draft. It describes - version 0.6 of the software. It is missing huge - chunks of information, and many of the features it describes - are unimplemented. All the content is subject to change, - especially if you help. Please send comments on the guide to - aaron@ximian.com. If you would like to work - on the guide please contact me or see the GNOME Documentation - project web - site. This paragraph will be removed in later - versions of the manual. - - - - - This book is divided into two parts, with several - appendices. The first part is a guided - tour— it will explain how to use - Evolution. If you are new to - Evolution or to groupware in - general, this section is for you. The second section, covering - configuration, is targeted at - more advanced users, but anyone who wants to change the way - Evolution looks or acts can benefit - from reading it. In addition, there is a comprehensive menu reference which describes nearly - every capability that Evolution has - to offer. - - - Typographical conventions - - Some kinds of words are marked off with special typography: - - Applications - Commands typed at the command line - Labels for interface items - - Menu selections look like this: - - Menu - Submenu - Menu Item - - - Buttons you can - click Anything you type - in Text - output from a computer - Words - that are defined in the . - - - - - - Quick Reference for Common Tasks - - You might want to copy this section and tape it to - the wall next to your computer: it's a very short summary of - most of the things you'll want to do with - Evolution, and pointers to the - sections of the book where you'll find more in-depth - description of those tasks. - - - Opening or Creating Anything - - Here are the keyboard shortcuts and menu items you're most - likely to use: - - - - - Create a new folder - ` - - FileNew - Folder or - - Ctrl - Shift - F - - - - - - - Create a new Shortcut in the Evolution Bar - - - File - New - Evolution Bar Shortcut or - - Ctrl - Shift - S - - - - - - - Create a new email message: - - - Use - FileNewMail - Message or - - Ctrl - Shift - M - - - - - - - Create a new Appointment - - - File - New - Appointment or - - Ctrl - Shift - A - - - - - - - - Enter a new Contact - - - File - New - Contact or - - Ctrl - Shift - C - - - - - - - - Create a new Task - - - File - New - Task or - - Ctrl - Shift - T - - - - - - - - - - Mail Tasks - - Here are the most frequent email tasks, and shortcuts for - navigating your mailbox with the keyboard instead of the - mouse: - - - Check Mail - - - Click Get Mail in the - toolbar. There is no keyboard shortcut for this task, - but you can ask Evolution - to check for new mail periodically. To do so, FIXME. - - - - - - Reply to a Message - - - To reply to the sender of the message only: - click Reply in the - toolbar, or press - - Ctrl - R - - - - To reply to the sender and all the other visible - recipients of the message, click Reply to - All or select the message and press - - Shift - Ctrl - R - - - - - - - Forward a Message - - - Select the message or messages you want to forward, - and click Forward in the - toolbar, or press - - Ctrl - J - - - - - - - Open a Message in a New Window - - - Double-click the message you want to view, or select - it and press - - Ctrl - O - - - - - - - Create Filters and Virtual Folders - - - You can create filters and Virtual Folders based on - specific message attributes from the message's - right-click menu. Alternately, select a message, and - then choose Settings - Mail Filters - or Settings - Virtual Folder Editor - . Filters are discussed in , and Virtual - Folders in . - - - - - - - - - Calendar - - - - - - - - - - - - - - - Contact Manager - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/doc/C/usage-calendar.sgml b/doc/C/usage-calendar.sgml deleted file mode 100644 index a2c14e99a6..0000000000 --- a/doc/C/usage-calendar.sgml +++ /dev/null @@ -1,371 +0,0 @@ - - - - The Evolution Calendar - - To begin using the calendar, select - Calendar from the shortcut - bar. By default, the calendar starts showing today's - schedule on a ruled background. At the upper right, there's a - monthly calendar you can use to switch days. Below that, there's - a TaskPad, where you can keep a list of tasks - seperate from your calendar appointments. The calendar's daily - view is shown in . - - -
- Evolution Calendar View - - Evolution Contact Manager Window - - - -
- - - - - Ways of Looking at your Calendar - - - The toolbar offers you four different views of your calendar: - one day, five days, a week, or a month at once. Press the - calendar-shaped buttons on the right side of the toolbar to - switch between views. You can also select a range of - days— three days, ten days, a fortnight if you want - — in the small calendar at the upper right. - - - The Prev and Next - buttons will move you forward and back in your calendar pages. - If you're looking at only one day, you'll see tomorrow's page, - or yesterday's. If you're looking at your calendar by week, - month, fortnight, or anything else, you'll move around by just - that much. To come back to today's listing, click - Today. - - - To visit a specific date's calendar entries, click - Go To and select the date in the dialog - box that appears. - - - - - - - - Scheduling With the Evolution Calendar - - Of course, you'll want to use the calendar to do more than find - out what day it is. This section will tell you how to schedule - events, set alarms, and determine event recurrence. - - - Creating events - - To create a new calendar event, select - - File - New - Appointment - - or click the New button on the left end - of the toolbar. The New Appointment - dialog will pop up with the usual menu bar, tool bar, and - window full of choices for you. - - - Shortcut - - If you don't need to enter more information than the date - and time of the appointment, you just click in any blank - space in the calendar and start typing. You can enter other - information later with the appointment editor. - - - - - Your event must have a starting and ending date — by - default, today — but you can choose whether to give it - starting and ending times or to mark it as an All - day event. An All day event - appears at the top of a day's event list rather than inside - it. That makes it easy to have events that overlap and fit - inside each other. For example, a conference might be an all - day event, and the meetings at the conference would be timed - events. Of course, events with specific starting and ending - times can also overlap. When they do they're displayed as - multiple columns in the day view of the calendar. - - - Doing Two Things At Once - - If you create calendar events that overlap, - Evolution will display them side - by side in your calendar. However, - Evolution cannot help you do - multiple things at once. - - - - You can have as many as four different - Alarms, any time prior to the event - you've scheduled. You can have one alarm of each type: - - - Display - - - A window will pop up on your screen to remind you of - your event. - - - - - Audio - - - Choose this to have your computer deliver a sound - alarm. - - - - - Program - - - Select this if you would like to run a program as a - reminder. You can enter its name in the text field, - or find it with the Browse - button. - - - - - Mail - - - Evolution will send an - email reminder to the address you enter into the text - field. - - - - - - - - Classification is a little more - complicated, and only applies to calendars on a - network. Public is the default category, - and a public event can be viewed by anyone on the calendar - sharing network. Private denotes one - level of security, and Confidential a - higher level. Exact determinations and - implementations of this feature have yet to be - determined. - - - The Recurrence tab lets you describe - repetition in events ranging from once every day up to once - every 100 years. You can then choose a time and date when the - event will stop recurring, and, under - Exceptions, pick individual days when the - event will not recur. Make your - selections from left to right, and you'll form a sentence: - "Every two weeks on Monday and Friday until January 3, 2003" - or "Every month on the first Friday for 12 occurrences." - - - - Once you're done with all those settings, click on the disk - icon in the toolbar. That will save the event and close the - event editor window. If you want, you can alter an event - summary in the calendar view by clicking on it and typing. You - can change other settings by right-clicking on the event then - choosing Edit this Appointment. - - - - - - - - - The Task Pad - - The Task Pad, located in the lower right corner of the - calendar, lets you keep a list of tasks separate from your - calendar events. Tasks are colored and sorted by priority and - due-date (see for more - information), and are included with calendar data during - synchronization with a hand-held device. You can use the list - in a larger format by choosing the Tasks - button in the shortcut bar or in the folder tree. - - - To record a new task, click the Add - button below the list. Evolution - will pop up a small window with five items in it: - - - - Summary: - - - The description you enter here will appear in the To Do - list itself. - - - - - - Due Date: - - - Decide when this item is - due. You can either type in a date and time, or select one from - the Calendar and time drop-down menus. - - - - - Priority: - - - Select a level of importance from 1 (most important) to 9 - (least important). - - - - - Item Comments: - - - If you wish, you can keep a more detailed description of - the item here. - - - - - - - Once you've added a task to your to-do list, its summary - appears in the Summary section of task - list. To view or edit a detailed description of an item, - double-click on it, or select it and click - Edit. You can delete items by selecting - them and clicking on the Delete button. - - - - - Multiple Calendars - - Evolution permits you to have and - maintain multiple calendars. This is useful if you maintain - schedules for other people, if you are responsible for resource - or room allocation, or if you have multiple personalities. - - - - Keeping Multiple Calendars - - Keelyn, the office manager for a small company, has one - calendar for her own schedule. On the local network, she - maintains one for the conference room, so people know when - they can schedule meetings. Next to that, she maintains a - calendar that reflects when consultants are going to be on - site, and another that keeps track of when the Red Sox are - playing. - - - - To create a new calendar, select - - File New - Calendar - . - You can place the calendar in any calendar folder and access it - from the folder view. Alarms, configuration, and display for - each calendar are separate from each other. - - - - - - - - - - - - - - diff --git a/doc/C/usage-contact.sgml b/doc/C/usage-contact.sgml deleted file mode 100644 index 0c6b976e4d..0000000000 --- a/doc/C/usage-contact.sgml +++ /dev/null @@ -1,617 +0,0 @@ - - - - The Evolution Address Book - - - The Evolution address book can - handle all of the functions of an address book, phone book, or - Rolodex. Of course, it's a lot easier to update - Evolution than it is to change an - actual paper book. Evolution also - allows easy synchronization with hand-held devices. Since - Evolution supports the LDAP directory protocol, you can use - it with almost any type of existing directory server on your - network. - - - Another advantage of the Evolution - address book is its integration with the rest of the - application. When you look for someone's address, you can also - see a history of appointments with that person. Or, you can - create address cards from emails with just a few clicks. In - addition, searches and folders work in the same way they do in - the rest of Evolution. - - - This chapter will show you how to use the - Evolution address book to organize - any amount of contact information, share addresses over a - network, and several ways to save time with everyday tasks. To - learn about configuring the address book, see . - - - - Getting Started With the Address Book - - - To open up your address book, click on - Contacts in the shortcut bar, or select - one of your contacts folders from the folder bar. shows the address book in all - its organizational glory. By default, the address book - shows all your cards in alphabetical order, in a minicard format. You can select - other views from the View menu, and adjust - the width of the columns by clicking and dragging the grey - column dividers. - - - -
- Evolution Address Book - - Evolution Address Book Window - - - -
- - - The toolbar for the address book is quite simple: - - - New creates a new card. - - - - Find brings up an in-depth search window. - - - - Print sends one or more of your cards to the printer. - - - Delete deletes a selected card. - - - View All displays all - the address information in the folder. Use this button to - refresh the display for a network folder, or to switch from - viewing the results of a search and see the whole contents. - - - Stop stops loading - contact data from the network. This button is only - relevant if you are looking at contact information on a - network. - - - - - Your contact information fills the rest of the display. Move - through the cards alphabetically with the buttons and the - scrollbar at the right of the window. Of course, if you have - more than a few people listed, you'll want some way of finding - them more quickly, which is why there's a search feature. - - - - Searching for Contacts - - Between Delete and View - All is a quick search field. To use it, select - from the drop-down list which sort of search you'd like to - perform (the whole card, just the name, or just the email - address), then enter one or more words in the text entry - box, and press Enter. - Evolution will search through - the contents of every displayed card to find one that - matches. You can refine searches by doing several in - succession, or start over by pressing the View - All button. - - - If there are no matches, the card display will be - blank. When you'd like to see all the cards again, press - Show All. - - - Refining a Quick Search - - Tom comes back from lunch and finds a note on his - keyboard: "Curtis in sales called for you, but he didn't - leave a number, and I forgot to write down the name of the - company he works for. He said it was important, though." - Tom is not at all annoyed. - - - He opens his contacts folder, and runs a quick search for - "Curtis." There are eighteen different people with that name - in the file. He then enters "Sales," and - Evolution narrows it down to the - right Curtis. He only becomes annoyed when he discovers that - the call was not actually important. - - - - - If you prefer to perform a more complex search, press - Find or choose - ToolsSearch for - Contact. This will open the - in-depth search window, which lets you use multiple search - criteria in the same way that email filters and virtual folders do.. - - Click Add Criterion to increase the - number of criteria you'd like to use in the search, and - Remove Criterion to remove one from the - bottom of the list. Your criteria may be a search within the - Name or Email - fields; alternately you can choose to search through all the - fields with a regular expression. Then, you can select from - all the familiar requirements like Begins - With and Does Not Contain, - decide whether to match All or - Any of your criteria, and press - Search to set it all off. - - - - - - - Destroy, Create, and Change: The Contact Editor - - To delete a card, click on it once to select it, then press the - Delete button. If you have multiple - cards selected, you'll delete multiple cards. - - - If you want to add or change cards, you'll use the contact - editor. To change a card that already exists, double click on - it to open the contact editor window with all the current - information already filled in. If you want to create a new - one, clicking the New button in the - toolbar will open the same window, with blank entry boxes for - you to fill in. - - - - The contact editor window has two tabs, - General, for basic contact information, - and Details, for a more specific - description of the person. In addition, it contains a - File menu, (see ) and a toolbar with three - items: Save and Close, - Print, and Delete. - - -
- Evolution Contact Editor - - Evolution Contact Editor - - - -
- - The General tab has seven sections, - each with an icon: a face, for name and company; a telephone - for phone numbers; an envelope for email address; a globe for - web page address; a house for postal address; a file folder - for contacts, and a briefcase for categories. - - - - - - Full Name - - - The Full Name field has two - major features: - - - - You can enter a name into the Full - Name field, but you can also click the - Full Name button to bring - up a small dialog box with a few text boxes - - - Title: - - Enter an honorific or select one from the menu. - - - - First: - - Enter the first, or given, name. - - - - Middle: - - Enter the middle name or initial, if any. - - - - Last: - - Enter the last name (surname). - - - - Suffix: - - Enter suffixes such as "Jr." or "III." - - - - - - - - The Full Name field also - interacts with the File As - box to help you organize your contacts. - - - To see how it works, type a name in the - Full Name field: - Rupert T. Monkey. You'll - notice that the File As field - also fills up, but in reverse: - Monkey, Rupert. - You can pick Rupert Monkey - from the drop-down, or type in - your own, such as T. Rupert Monkey - . - - - Filing Suggestion - - - Don't enter something entirely different from - the actual name, since you might forget that - you've filed Rupert's information under "F" for - "Fictitious Ximian Employee." - - - - - - - - - Multiple Values for Fields - - - If you click on the small arrow buttons next to the - Primary Email field, you can also - choose Email 2 and - Email 3. Although the contact - editor will only display one of those at any given - time, Evolution will - store them all. The arrow buttons next to the - telephone and postal address fields work in the same - way. - - - - - - - The last item in the General tab is the - Categories organization tool; for - information on that, read . - - - The Details tab is, fortunately, much more - simple: three sections, all of which are more or less obvious: - the briefcase next to the details about the contact's - professional life; the face next to the details about their - personal life; the globe next to a big blank space you can use - for anything and everything else you'd like to note about them. - If you ever wanted to have that uncanny knack for remembering - obscure details like the date of someone's anniversary (perhaps - your own) this is the way to develop it. - - - - - - - - - - - Organizing your Address Book - - Organizing your address book is a lot like organizing your - mail. You can have folders and searches the same way you can - with mail, but the address book does not allow vFolders. It - does, however, allow each card to fall under several - categories, and allow you to create your own categories. To - learn about categories, read . - - - - - - Groups of contacts - - Evolution offers two ways for you - to organize your cards. The first way is to use folders; - this works the same way that mail folders do. For more - flexibility, you can also mark contacts as members of - different categories. - - - - Grouping with Folders - - The simplest way to group address cards is to use folders. - By default, cards start in the - Contacts folder. If you've read then you already know that you - can create a new folder by selecting - - File - New - Folder - - and that you can put new folders anywhere you like. Just - like with mail, cards must be in a card folder, and no card - can be in two places at once. If you want more - flexibility, try . - - - To put a card into a folder, just drag it there from the - folder view. Remember that contact cards can only go in - contact folders, just like mail can only go in mail folders, - and calendars in calendar folders. - - - - - Grouping with Categories - - 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. - - - To mark a card as belonging to a category, click the - Categories button at the lower - right. From the dialog box that appears, you can check as - many or as few categories as you like. - - - Then, you can refer to all the cards in that category by: - Waiting for Evolution to support the - operation. - - - - - - - - - - Sharing your Cards - - If you keep your cards on a network using an LDAP server, you can share access to - them, browse other address books, or maintain a shared set of - contact information for your company or your department. 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 - share calendars as well as address books, people can avoid - duplicating work and keep up to date on developments within - their work-group or across the entire company. - - - - Sharing Address Cards and Calendar Data - - Ray wants to schedule a meeting with Company X, so he - checks the network for the Company X address card so he - knows whom to call there. Since his company also shares - calendars, he then learns that his co-worker Deanna has - already scheduled a meeting with Company X next Thursday. - He can either go to the meeting himself or ask Deanna to - discuss his concerns for him. Either way, he avoids - scheduling an extra meeting with Company X. - - - - Of course, you don't want to share all of your cards— why - overload the network with a list of babysitters or tell - everyone in the office you're talking to new job prospects? If - you keep cards on your own computer, you can decide which items - you want to make accessible to others. - - - To learn how to add a remote directory to your available - contact folders, see . - Once you have a connection, the network contacts folder or - folders will appear inside the External - Directories folder in the folder bar. It will work - exactly like a local folder of cards, with the following - exceptions: - - - - - Network folders are only available when you are - connected to the network. If you use a laptop or have a - modem connection, you may wish to copy or cache the - network directory and then synchronize your copy with - the networked version periodically. - - - - - - To prevent excess network traffic, - Evolution will not normally - load the contents of LDAP folders immediately upon - opening. You must click Display - All before LDAP folder cards will be loaded - from the network. You can change this behavior in the - Contact Preferences window. - - - - - Your ability to view, change, add, and delete contacts - depends on the settings of the LDAP server. - - - - - - - - Address Book Tools - - The address book works closely with - Evolution's mail and calendar tools. - For example, you can use the address book to help you manage - mailing lists, and send or recieve address cards over email. - More tools are on the way, and when they arrive, - they will be described in this section. - - - - Send me a Card: Adding New Cards Quickly - - As noted before, when you get information about a person in - the mail or in a calendar entry, you can add it to an address - card. To do so, right click on any email address or email - message, and select Add Address - Card from the menu that appears. Of course, - Evolution also adds cards from a - hand-held device during HotSync operation. For more - information about that, see . - - - - - Managing a Mailing list - - You already know that when you are writing an email, you can - address it to one or more people, and that - Evolution will fill in addresses - from your address book's address cards if you let it. In - addition to that, you can send email to everyone in a - particular group if you choose. - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/doc/C/usage-exec-summary.sgml b/doc/C/usage-exec-summary.sgml deleted file mode 100644 index 5ff67029d7..0000000000 --- a/doc/C/usage-exec-summary.sgml +++ /dev/null @@ -1,91 +0,0 @@ - - The Executive Summary - - The Evolution Executive Summary is designed to show you a - summary of important information: the appointments for a given - day, important email, and so forth. To see your executive - summary, click on the Executive Summary - button in the shortcut bar, or select the - executive-summary folder in the folder - bar. - - - - Introducing the Executive Summary - - The first thing you'll want to do with the executive summary - is add a service. Click the Add Service - button in the toolbar, then select one of the available - services. Services may vary depending upon your system, but - most installations will have at least the following options: - - - - - Calendar - - - Pending appointments and other events. - - - - - - Inbox - - - Information about your mail, such as the number of - new messages you have waiting. - - - - - - To Do - - - A short summary of your task pad. - - - - - - RDF Summary - - - News headlines for any valid RDF file. The default - is news about the GNOME project from gnotices. - - - - - - - - - - Each service appears in a small box on the screen; you can - remove the service by clicking the x - button in the upper right, or bring up a settings dialog by - clicking the little wrench icon below that. - - - - Services in Detail - - This section will show you how to use several - Evolution services. - - - - - - - - - - - - - diff --git a/doc/C/usage-mail.sgml b/doc/C/usage-mail.sgml deleted file mode 100644 index 9ec12d9e5b..0000000000 --- a/doc/C/usage-mail.sgml +++ /dev/null @@ -1,1539 +0,0 @@ - - - - Evolution Mail - - An Overview of the Evolution Mailer - - Evolution email is like other email - programs in all the ways you would hope: - - - - It can sort and organize your mail in a wide variety of ways with - folders, searches, and filters. - - - - - It can send and receive mail in HTML or as plain text, and - permits multiple file attachments. - - - - - It supports multiple mail sources, including IMAP, POP3, local - mbox and - mh files, and - even NNTP messages (newsgroups), which aren't technically - email. - - - - - - However, Evolution has some important - differences. First, it's built to handle very large amounts of - mail without slowing down or crashing. Both the filtering and searching functions - were built for speed and efficiency on gargantuan volumes of - mail. There's also the Evolution - Virtual - Folder, 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 this feature especially useful. - - - - - Reading, Getting and Sending Mail - - - Reading Mail - - You can start reading email by clicking - Inbox in the shortcut bar. The first - time you use Evolution, it will - start with the Inbox open and show you a - message from Ximian welcoming you to the application. - - - Your Evolution - Inbox will look something like the one in - . Just below the toolbar - is the message list, showing message - header information like Subject and - Date. The message itself appears below - that, in the view pane. If you find - the view pane too small, you can resize - the pane, enlarge the whole window, or double-click on the - message in the message list to have it - open in a new window. Just like with folders, you can - right-click on messages in the message list and get a menu of - possible actions. - - - - -
- Evolution Mail - - Inbox - - - -
- - - - Most of the mail-related actions you'll want to perform are - listed in the Message menu in the menu - bar. The most frequently used ones, like - Reply and - Forward, also appear as buttons in - the toolbar, and almost all of them are duplicated in the - right-click menu and as keyboard shortcuts, which tend to be - faster once you get the hang of them. You can choose - whichever way you like best; the idea is that the software - should work the way you want, rather than making you work the - way the it does. - - Take a look at the headers - - To look at the entire source of your email message, including - all the header information, select - ViewSource - - - - - - Sorting the message list - - One of the ways Evolution lets - you choose the way you work is the way it lets you sort your - message lists. To sort by sender, subject, or date, click - on the bars with those labels at the top of the message - list. The direction of the arrow next to the label indicates - the direction of the sort, and if you click again, you'll - sort them in reverse order. For example, click once on - Date to sort messages by date from - oldest to newest. Click again, and - Evolution sorts the list from - newest to oldest. You can also right-click on the message - header bars to get a set of sorting options, and add or - remove columns from the message list. You can find detailed - instructions on how to customize your message display - columns in . - - - You can also choose a threaded message view. Select - View - Threaded to turn - the threaded view on or off. When you select this option, - Evolution groups the replies to a - message with the original, so you can follow the thread of a - conversation from one message to the next. - - - - Deleting Mail - - Once you've read your mail, you may want to get rid of - it. To mark a message for deletion, select it in the the - message list by clicking on it once. - Then click on the Delete button in - the tool bar. Or, right-click on a message and choose - Delete from the right-click - menu. The message will appear with a line through it, to - show that you've marked it for deletion. - - - If you change your mind and decide you want to keep it, - select Message - Undelete. If you - really want to get rid of it, choose - Expunge from the - Folder menu. That will delete it - permanently. - - - - - - Checking Mail - - Now that you've had a look around the - Inbox, it's time to check for new mail. - Click Get mail in the toolbar to check - your mail. If it's the first time you've done so, the - mail setup assistant will ask you for - the information it needs to check your mail (see for more information). - - - Then, you need to enter your email - password. Evolution will remember - your password until until you select - Settings Forget - Passwords . - - - Once it's validated the password, - Evolution will check your mail. - New mail will appear in the local Inbox - if you're using a POP account, and in - your IMAP folders if you use IMAP. If - you have chosen to use IMAP, and you have multiple folders on - your IMAP server, you may need to subscribe to them. To learn - how to use the subscription manager, read . - - - - Can't Check Mail? - - If you get an error message instead of mail, you probably need - to change your network settings. To learn how to do that, - have a look at , or - ask your system administrator. - - - - - Using Evolution for News - - Newsgroups are so similar to email that there's no reason not - to read them side by side. If you want to do that, add a - news source to your configuration (see ). The news server will - appear as a remote server, and will look quite similar to an - IMAP folder. When you click Get Mail, - Evolution will also check for news - messages. - - - - - Attachments and HTML Mail - - If someone sends you an attachment, a - file attached to an email, - Evolution will display the file - at the bottom of the message to which it's attached. Text, - HTML, and most images will be displayed within the message - itself. For other files, - Evolution will show an icon at - the end of the message. Right-click on the icon to get a - list of options which will vary depending on the type of - attachment. You will have the option to display most files - as part of the message, export them to a different - application (images to Eye of GNOME, spreadsheets to - Gnumeric, and so forth), or save them to disk. - - - - Evolution can also display - HTML-formatted mail, complete with graphics. HTML - formatting will display automatically, although you can - turn it off if you prefer. - - - - - - Writing and Sending Mail - - You can start writing a new email message by selecting - File - New - Mail Message, or by pressing the - Compose button in the Inbox toolbar. - When you do so, the New Message window - will open, as shown in . - - - -
- New Message Window - - Evolution Main Window - - - -
- - - - - Enter an address in the To: field, a - subject in the Subject: and a message in - the big empty box at the bottom of the window, and press - Send. - - - - Saving Messages for Later - - Evolution will send mail immediately unless you tell it to - do otherwise by selecting - File Send - Later. This will add your - messages to the Outbox queue. Then, - when you press Send in another - message, or Get Mail in the main - mail window, 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. - - - To learn more about how you can specify message queue and - filter behavior, see . - - - - You can also choose to save messages as drafts or as text - files. Choose - - File - Save - - or Save As to save your message - as a text file. If you prefer to keep your message in a - folder (the Drafts folder would be the - obvious place), you can select - File Save In - Folder . - - - - Advanced Mail Composition - - You can probably guess the purpose of the buttons labelled - Cut, Copy, - Paste, Undo - and Redo, but there's a bit more to - sending mail that's less obvious. In the next few sections, - you'll see how Evolution handles - additional features, including large recipient lists, - attachments, and forwarding. - - - Attachments - - If you want to attach a file to your email message, you - can drag it from your desktop into the message window, or - click the button in the toolbar with a paper clip on it, - labelled Attach. If you click the - Attach button, - Evolution will open a file - selection dialog box to ask you which file you want to - send. Select the file and click OK. - - - To hide the display of files you've attached to the - message, select - View Hide - Attachments ; to show them - again, choose Show Attachments. - - - When you send the message, a copy of the attached file - will go with it. Be aware that big attachments can take a - long time to download. - - - - Types of Recipients - - Evolution, like most email - programs recognizes three types of addressee: primary - recipients, secondary recipients, and hidden ("blind") - recipients. - - - The simplest way to direct a message is to put the email - address or addresses in the To: - field, which denotes primary recipients. To send mail to - more than one or two people, you can use the the - Cc: field. - - - 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. - - Using the Cc: field - - When Susan sends an email to a client, she puts her - co-worker, Tim, in the in the - Cc: field, so that he know - what's going on. The client can see that Tim also - received the message, and knows that he can talk to - Tim about the message as well. - - - - - 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 - Bcc:. "Bcc" stands for "Blind Carbon - Copy", and it sends messages discreetly. In other words, - the people in the Bcc: field get the - message, but nobody sees that they got it. Note that the - contents of the To: and - Cc: fields are visible to all - recipients, even to people on the - Bcc: list. - - - Using the Bcc: field - - Tim is sending an email announcement to all of his - company's clients, some of whom are in competition - with each other, and all of whom value their - privacy. He needs to use the - Bcc: field here. If he puts - every address from his address book's "Clients" - category into the To: or - Cc: fields, he'll make the - company's entire client list - public. It seems like a small difference, but it can - make a huge difference in some situations. - - - - - - - Choosing Recipients Quickly - - If you have created address cards in the contact manager, - you can also enter nicknames or other portions of address - data, and Evolution will complete - the address for you. 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. - - - - Alternately, you can click on the - To:, Cc:, or - Bcc: buttons to get a list — - potentially a very long one — of the email addresses - in your contact manager. Select addresses and click on - the arrows to move them into the appropriate address - columns. - - - For more information about using email together with the - contact manager and the calendar, see and . - - - - - - Replying to Messages - - To reply to a message, press the - Reply button while it is selected, - or choose Reply to Sender from - the message's right-click menu. That will open the - message composer. The - To: and Subject - fields will already be filled, although you can alter them - if you wish. In addition, the full text of the old message - is inserted into the new message, either in italics (for - HTML display) or with the > character before each line - (in plain text mode), to indicate that it's part of the - previous message. People often intersperse their message - with the quoted material as shown in . - - - -
- Reply Message Window - - Evolution Main Window - - - -
- - - - - If you're reading a message with several recipients, you may - wish to use Reply to All instead of - Reply. If there are large numbers - of people in the Cc: or - To: fields, this can save substantial - amounts of time. - - Using the Reply to All feature - - Susan sends an email to a client and sends copies to Tim - and to an internal company mailing list of co-workers. - If Tim wants to make a comment for all of them to read, - he uses Reply to All, but if he - just wants to tell Susan that he agrees with her, he - uses Reply. Note that his reply - will not reach anyone that Susan put on her - Bcc list, since that list is not - shared with anyone. - - - - - - Searching and Replacing with the Composer - - You're probably familiar with search and replace features, - and if you come from a Linux or Unix background, you - probably know what Find Regex - does. If you aren't among the lucky who already know, - here's a quick rundown of an important section of the - Edit menu. - - - - - Find - Enter a word or phrase, and - Evolution will find it - in your message. - - - - - Find Regex - - - Find a regex, also called a - regular - expression, in your composer window. - - - - - - Find Again - - Select this item to repeat the last search you performed. - - - - - Replace - - Find a word or phrase, and replace it with - something else. - - - - - - - For all of these menu items, you can choose whether or not - to Search Backwards in the document - from the point where your cursor is. For all but the - regular expression search (which doesn't need it), you are - offered a check box to determine whether the search is to - be Case Sensitive when it determines - a match. - - - - Embellish your email with HTML - - Normally, you can't set text styles or insert pictures in - emails, which is why you've probably seen people use far - too many exclamation points for emphasis, or use - emoticons to - convey their feelings. However, most newer email programs - can display images and text styles as well as basic - alignment and paragraph formatting. They do this with - HTML, just like web - pages do. - - - HTML Mail is not a Default Setting - - 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 - Evolution sends plain text - unless you explicitly ask for HTML. To send HTML mail, - you will need to select - Format - HTML. Alternately, you can set - your default mail format preferences in the mail - configuration dialog. See for more information. - - - - HTML formatting tools are located in the toolbar just above - the space where you'll actually compose the message, and - they also appear in the Insert and - Format menus. - - - The icons in the toolbar are explained in tool-tips, which appear when - you hold your mouse over the buttons. The buttons fall - into four categories: - - - Headers and lists - - - At the left edge of the toolbar, you can choose - Normal for a default text style - or Header 1 through - Header 6 for varying sizes of - header from large (1) to tiny (6). Other styles - include pre, to use the HTML - tag for preformatted blocks of text, and three types - of List Item for the highly - organized. - - - - - Text style - - - Use these buttons to determine the way your letters - look. If you have text selected, the style will - apply to the selected text. If you do not have text - selected, the style will apply to whatever you type - next. The buttons are: - - Push B for bold text - Push I for italics - Push U to underline - Push S for a strikethrough. - - - - - - Alignment - - - Located next to the text style buttons, these three - paragraph icons should be familiar to users of most - word processing software. The leftmost button will - make your text aligned to the left, the center - button, centered, and the right hand button, - aligned on the right side. - - - - - - Indentation rules - - - The button with the arrow pointing left will reduce - a paragraph's indentation, and the right arrow will - increase its indentation. - - - - - - Color Selection - - - At the far right is the color section tool. The - colored box displays the current text color; to - choose a new one, click the arrow button just to the - right. If you have text selected, the color will - apply to the selected text. If you do not have text - selected, the color will apply to whatever you type - next. - - - - - - - - - There are three tools that you can find only in the - Insert menu. - - - Insert Link: - - - Use this tool to put hyperlinks in your HTML - messages. When you select it, - Evolution will prompt you - for the Text that will appear, - and the Link, where you should - enter the actual web address (URL). If you don't - want special link text, you can just enter the address - directly, and Evolution - will recognize it as a link. - - - - - Insert Image: - - - Select this item to embed an image into your email, as - was done in the welcome message. Images will appear at - the location of the cursor. This is different from - attaching them to a message, but not very different. - - - - - Insert Rule: - - This will insert a horizontal line, or rule, into your document. - You'll be presented with a dialog box which gives you - the choice of size, percentage of screen, shading, and - alignment; if you leave everything at the default - values you'll get a thin black rule all the way across - the screen. - - - - - - A Technical note on HTML Tags - - The composer is a WYSIWYG (What You See Is What You Get) - editor for HTML. That means that if you enter HTML - directly into the composer— say, <B>Bold Text</B>, the - the composer will assume you meant exactly that string - of characters, and not "make this text bold," as an HTML - composition tool or text editor would. - - - - - - - - - - Forwarding Mail - - The post office forwards your mail for you when you change - addresses, and you can forward mail when you get a letter by - mistake. The email Forward button - works in much the same way. It's particularly useful if you - have received a message and you think someone else would - like to see it. You can forward a message as an attachment - to a new message (this is the default) or - you can send it inline as a quoted - portion of the message you are sending. Attachment - forwarding is best if you want to send the full, unaltered - message on to someone else. 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. - - - To forward a message you are reading, press - Forward on the toolbar, or select - Message - Forward . If you - prefer to forward the message inline - instead of attached, select - Message Forward - Inline from the menu. 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 - composition frame, and press - Send. - - - - Seven Tips for Email Courtesy - - I started with ten, but four were "Don't send - spam." - - - - - Don't send spam or forward chain mail. If you must, - watch out for hoaxes and urban legends, and make sure - the message doesn't have multiple layers of - greater-than signs, (>) indicating multiple layers - of careless in-line forwarding. - - - - - - 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! - - - - - - ALL CAPS MEANS YOU'RE SHOUTING! Don't write a whole - message in capital letters. It hurts people's ears. - - - - - - Never write anything in email you wouldn't say in - public. Old messages have a nasty habit of - resurfacing when you least expect. - - - - - - Check your spelling and use complete sentences. - - - - - - Don't send nasty emails (flames). If you get one, - don't write back. - - - - - - When you reply or forward, include just enough of - the previous message to provide context: not too - much, not too little. - - - - - Happy mailing! - - - - - - Organizing Your Mail - - 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. - Fortunately, Evolution has the tools - to help you do it. - - - Sorting Mail with Column Headers - - By default, the message list has columns with the following - headings: an envelope icon indicating whether you have read - or replied to a message (closed for unread, open for read, - and open with an arrow on it to indicate you've sent a - reply), an exclamation point indicating priority, and the - From, Subject, and - Date fields. You can change their order - and remove them by dragging and dropping them. You can add - new ones with the Field Chooser - item in the right click menu for the column headings. - - - Right-click on one of the column headers to get a list of - options: - - - - Sort Ascending, - Sort Descending, and - Unsort - Which should be pretty obvious. You - can also set these sorts by just clicking on the - column headers. - - - - Group By this Field - - Groups messages instead of sorting them. (FIXME: Explain further) - - - - - Remove this - Column Remove - this column from the display. You can also remove - columns by dragging the header off the list and - letting it drop. - - - - Field - Chooser A list - of column headers; just drag and drop them into - place between two existing headers. A red arrow will - appear to show you where you're about to put the - column. - - - - - - - Getting Organized with Folders - - Evolution keeps mail, as well as - address cards and calendars, in folders. You start out with a - few, like Inbox, - Outbox, and Drafts, - but you can create as many as you like. Create new folders by - selecting New and then - Folder from the - File menu. - Evolution will as you for the name - and the type of the folder, and will provide you with a folder - tree so you can pick where it goes. - - - When you click OK, your new folder will - appear in the folder view. You can - then put messages in it by dragging and dropping them, or by - using the Move button in the - toolbar. If you want to move several messages at once, click - on the ones you want to move while holding down the - CTRL key, or use Shift to - select a range of messages. If you create a filter with the - filter assistant, you can have mail - moved to your folder automatically. - - - - - Searching for Messages - - Most mail clients can search through your messages for you, - but Evolution does it faster. You - can search through just the message subjects, just the message - body, or both body and subject. - - - To start searching, enter a word or phrase in the text area - right below the toolbar, and choose a search type: - - - Body or subject contains: - - - This will search message subjects and the messages - themselves for the word or phrase you've entered in - the search field. - - - - - Body contains: - - - This will search only in message text, not the subject - lines. - - - - - Subject contains: - - - This will show you messages where the search text is - in the subject line. It will not search in the - message body. - - - - - Body does not contain: - - - This finds every email message that does not have the - search text in the message body. It will still show - messages that have the search text in the subject - line, if it is not also in the body. - - - - - Subject does not contain: - - - This finds every mail whose subject does not contain - the search text. - - - - - - When you've entered your search phrase, press - Enter. Evolution - will show your search results in the message list. - - - - If you think you'll want to return to a search again, you can - save it as a virtual folder by selecting Store - Search as Virtual Folder. - - - - When you're done with the search, go back to seeing all your - messages by choosing Show All from - the Search drop-down box. If you're - sneaky, just enter a blank search: since every message has at - least one space in it, you'll see every message in the - folder. - - - - If you'd like to perform a more complex search, open the - advanced search dialog by selecting - Advanced... from the - Search drop-down menu. Then, create your - search criteria (each with the same options you saw in the - regular search bar), and decide whether you want to find - messages that match all of them, or messages that match even - one. Then, click Search to go and find - those messages. - - - - You'll see a similar approach to sorting messages when you - create filters and virtual folders in the next few sections. - - - - - - Staying organized: Mail Filters in Evolution - - I once worked in the mail room of a large company, where my - job was to bundle, sort, and distribute mail to the various - mail boxes and desks throughout the building. Filters do that - same job with email, but they lose much less mail than I did. - In addition, you can have multiple filters performing multiple - actions that may effect the same message in several ways. For - example, your filters could put copies of one message into - multiple folders, or keep a copy and send one to another - person as well, and it can do that in under a second. Which is - to say, it's faster and more flexible than an actual person - with a pile of envelopes. - - - Most often, you'll want to have - Evolution put mail into different - folders, but you can have it do almost anything you like. - People who get lots of mail, or who often need to refer to old - messages, find filters especially helpful, but they're good - for anybody who gets more than a few messages a day. To - create a filter, open the filter - assistant by selecting - - Settings - Mail Filters - . - - -
- The Filter Assistant - - The Filter Assistant - - - -
- - - The filter assistant window contains a - list of your current filters, sorted by the order in which - they are used. From the drop-down box at the top of the - window, choose Incoming to display - filters for incoming mail, and Outgoing - for those which sort only outgoing mail. - - - The filter assistant also has a set of - buttons: - - - - Add — Create a new filter. - - - - Edit — Edit an existing filter. - - - - Delete — Delete the selected filter. - - - Up — Move the - selected filter up in the list so it gets applied first. - - - - Down — Move the selected filter down - in the list, so it comes into play later. - - - - If you don't have any filters set up, the only one of those - buttons you can click is Add, which - will open a dialog to let you add a filter rule. If you do - have filters, you can either add a new filter rule, or select - one from your list and click Edit. - - - The filter rule editor, shown in , is where you'll - actually create your filtering rule. - -
- Creating a new Filter - - Creating a new Filter - - - -
- - - Enter a name for your filter in the Rule - Name field, and then begin choosing the criteria - you'd like to use as you sort your mail. Choose how many - criteria you'd like by pressing Add - Criterion and Remove - Criterion. If you have multiple criteria, you - should then decide whether to have the filter do its job only - if all criteria are met, or if - any criteria are met. - - - For each filter criterion, you must first select what - part of the message you want the filter to examine: - - - Sender - - The sender's address. - - - - - Recipients - - The recipients of the message. - - - - - Subject - - The subject line of the message. - - - - - - Specific Header - - The filter can look at any header you - want, even obscure or custom ones. Enter the header name - in the first text box, and put your search text in the - second one. - - - - - Message Body - - Search in the actual text of the message. - - - - - Expression - - - Enter a regular - expression, and - Evolution will search the - entire message, including headers, to match it for you. - - - - - - - Date Sent - Filter messages by when they were sent: - First, choose the conditions you want a message to - meet— before a given time, - after it, and so forth. Then, choose - the time. The filter will compare the message's time-stamp - to the system clock when the filter is run, or to a - specific time and date you choose from a calendar. You - can even have it look for messages within a range of time - relative to the filter&mdash perhaps you're looking for - messages less than two days old. - - - - Date Recieved - - This works the same way as the Date Sent - option, except that it compares the time you got the message - with the dates you specify. - - - - - Priority - - Emails have a standard priority range from -3 (least - important) to 3 (most important). You can have filters set the - priority of messages you recieve, and then have other filters - applied only to those messages which have a certain priority. - - - - - Regex Match - - - If you know your way around a regex, or - regular expression, put your knowledge to use here. - - - - - - Source - - - Filter messages according the server you got them from. - You can enter a URL or choose one from the drop-down - list. This ability is only relevant if you use more - than one mail source. - - - - - - - Now, tell it what to do with those messages. If you want more - actions, click Add Action; if you want - fewer, click Remove Action. And choose - again: - - - - Copy to Folder - - If you select this item, Evolution - will put the messages into a folder you specify. Click the - <click here to select a folder> button - to select a folder. - - - - - Move to Folder - - If you select this item, Evolution - will put the messages into a folder you specify. Click the - <click here to select a folder> button - to select a folder. - - - - - Forward to Address - - Select this, enter an address, and the addressee will - get a copy of the message. - - - - - Delete - - Marks the message for deletion. You can still get the message - back, at least until you Expunge your - mail yourself. - - - - - Stop Processing - - Select this if you want to tell all other filters to ignore - this message, because whatever you've done with it so far - is plenty. - - - - - Assign Color - - Select this item, and Evolution - will mark the message with whatever color you please. - - - - - Assign Score - If you know that all mail with - "important" somewhere in the message body line is - important, you can give it a high priority score. In a subsequent filter you can - then arrange your messages by their priority score. - - - - - - - You're done. Click OK to use this - filter, or Cancel to close the window - without saving any changes. - - - - - - - - Two Notable Filter Features - - - - Incoming email that your filters don't move goes into the Inbox; - outgoing mail that they don't move ends up in the Sent folder. - - - - If you move a folder, your filters - will follow it. - - - - - - - - - Getting Really Organized with Virtual Folders - - If filters aren't flexible enough for you, or you find - yourself performing the same search again and again, consider - a virtual folder. Virtual folders, or vFolders, are an - advanced way of viewing your email messages within - Evolution. If you get a lot of - mail or often forget where you put messages, virtual folders can help - you stay on top of things. - - - A virtual folder is really a hybrid of all the other organizational - tools: it looks like a folder, it acts like a search, and you - set it up like a filter. In other words, while a conventional - folder actually contains messages, a virtual folder is a view of - messages that may be in several different folders. The - messages it contains are determined on the fly using a set of - criteria you choose in advance. - - - - As messages that meet the virtual folder criteria arrive or are - deleted, Evolution will - automatically place them in and remove them from the - virtual folder contents list. When you delete a message, it gets - erased from the folder in which it actually exists, as well as - any virtual folders which display it. - - - - 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 more mail you need to organize, the less you - can afford the sort of confusion that stems from an - organizational system that's not flexible enough. Virtual folders - make for better organization because they can accept - overlapping groups in a way that regular folders and filing - systems can't. - - - - Using Folders, Searches, and Virtual Folders - - To organize my mail box, I set up a virtual folder for - emails from my friend and co-worker Anna. I have another - one for messages that have "ximian.com" in the address and - "Evolution" in the subject line, so I can keep a record of - what people from work send me about - Evolution. If Anna sends me a - message about anything other than Evolution, it only shows - up in the "Anna" folder. When Anna sends me mail about the - user interface for Evolution, I - can see that message both in the "Anna" virtual folder and - in the "Internal Evolution Discussion" virtual folder. - - - - - - - To create a virtual folder, select - Settings Virtual Folder - Editor . This will bring up a - dialog box that looks suspiciously like the filter window - (for more information on filters, see ), and which - presents you with a list of virtual folders you have previously - created. If you have created any virtual folders, they are listed - here, and you can select, edit or remove them if you wish. - If you have not created any, there will be only one available - option: click Add to add a new - Virtual Folder. - - - You can enter a name for your virtual folder in the - Name. Then, tell - Evolution what messages to look - for. This process is exactly like filter creation: decide - between Match all parts and - Match any part, then choose what part of - the message to look in, what sort of matching to perform, and - specify exactly what it is that you want to find, be it a - line of text, a score, a regular expression, or a particular date or - range of dates. - - - The second part, however, is slightly different. In the - section of the window labelled Virtual Folder Sources - is a list of folders in which - Evolution will search for the - contents of your vFolder. Click Add - to add a folder, or Remove to remove - one. That way, you can have your vFolder search in - newsgroups, or just in one of your mailboxes, or just in a - select few folders you've already screened with filters. - - - The vFolder creation window is shown in - -
- Selecting a vFolder Rule - - Creating a vFolder Rule - - - -
- - - - Subscription Management - - Evolution lets you handle your - IMAP and newsgroup subscriptions with the same tool: the - subscriptions manager. To start using it, choose - Settings Manage - Subscriptions . - - - If you have configured any IMAP (mail) or NNTP (news) - servers, you will see them listed in the left half of the - subscription management window. Click on a server to select - it, and you will see the folders or newsgroups available to - you. You can then select individual folders and subscribe to - them, or remove yourself from the subscription list. - - - Once you have subscribed to a folder or newsgroup, your system - will check for new messages whenever you press the - Get Mail button. - - - - - - - diff --git a/doc/C/usage-mainwindow.sgml b/doc/C/usage-mainwindow.sgml deleted file mode 100644 index bbcb2b5a39..0000000000 --- a/doc/C/usage-mainwindow.sgml +++ /dev/null @@ -1,453 +0,0 @@ - - - - The Main Window: Evolution Basics - - Start Evolution by selecting - Main Panel Menu - Applications - Evolution or by typing - evolution at the command line. The first time - you run the program, it will create a directory called - evolution in your home directory, where it - will keep all your Evolution-related - files. - - - After Evolution starts - up, you will see the main window, with the - Inbox open. It should look a lot like the - picture in . On the left of - the main window is the shortcut - bar, with several buttons in it. Just underneath the - title bar is a series of menus in the menu - bar, and below that, the tool - bar with buttons for different functions. The largest - part of the main window is taken up by the - actual Inbox, where messages are listed - and displayed. If you're running the program for the first time, - you'll have just one message: a welcome from Ximian. - - - -
- Evolution Main Window and Inbox - - Evolution Main Window - - - -
- - - - - - The Way Evolution Looks - - The appearance of both Evolution - and GNOME is very easy to - customize, so your screen might not look like this picture. - You might decide to have Evolution - start with the calendar and a folder bar, or with the contact - manager occupying the entire window. - - - - - - The Shortcut Bar - - Evolution's most important job is - to give you access to your information and help you use it - quickly. One way it does that is through the - shortcut bar, the column on the left - hand side of the main window. The large buttons with names - like Inbox and - Contacts are the shortcuts, and you can - select different groups of shortcuts by clicking the - rectangular group buttons. - - - The shortcut group buttons are Evolution - Shortcuts and Internet - Directories. When you click on them, they'll slide - up and down to give you access to different sorts of shortcuts. - When you first start Evolution, you - are looking at the Evolution Shortcuts - category. If you click Internet - Directories, it will slide up and you'll see buttons - for the Bigfoot and - Netcenter directories, as well as any - others you or your system administrator may have added. You can - add more groups by right-clicking on the background of the - shortcut bar and selecting Menu - Group. Internet directories behave a lot like - the local contact manager, which is covered in . - - - Take a look at the Evolution Shortcuts - again. The shortcut buttons in that category are: - - - - - - - - Executive Summary: - - - Start your day here. The Executive summary gives you - lists of new or important messages, daily appointments - and urgent tasks. You can customize its appearance and - content, and use it to access Evolution services. - - - - - - - Inbox: - - - Click the Inbox button to start - reading your mail. Your Inbox is also where you can - access Evolution's tools to filter, sort, organize, and - search your mail. - - - - - - Calendar: - - - The Calendar can store your appointments and To do lists - for you. Connected to a network, you can use it to keep - a group of people on schedule and up to date. - - - - - - Tasks: - - - A full-size view of your calendar's task pad. - - - - - - Contacts: - - - The Contact Manager 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. - - - - - - - - - - If you don't like the shortcut bar, you can use the folder bar - or the menu bar to navigate the main window. Press - - Ctrl - O - - to choose from a list of folders you'd like to visit, or use the - drop-down folder bar. You can hide and show the folder bar and - the shortcut bar by selecting those items in the - View menu. - - - - Shortcut Bar Tricks - - To remove a shortcut from the shortcut bar, right-click on it - and select Remove. To add one, - select File - New Evolution Bar - Shortcut . - - - To change the way the shortcut bar looks, right-click in an - empty space on the shortcut bar. From the menu that appears, - you can select icon sizes. - - - - - - The Folder Bar - - The folder bar is a more comprehensive - way to view the information you've stored with - Evolution. It displays all your - appointments, address cards, and email in a tree that's a lot - like a file - tree— it starts small at the top, and branches - downwards. On most computers, there will be three or four - folders at the base. First is the Local - folder, which holds all the Evolution - data that's stored on your computer. After that come - Virtual Folders, or virtual folders, discussed in - , followed by any - IMAP mail folders you may - have available to you over your network. Lastly, there are - External Directories, LDAP contact directories stored on a - network. - - - - A typical Local folder contains the following folders: - - - - Calendar, for appointments and - event listings. - - - - - Contacts, for address cards. - - - - - Inbox, for incoming mail. - - - - - Drafts, for messages you started and didn't finish. - - - - - Sent, for sent mail. - - - - - Trash, which is used to store - messages you don't want, but keep around just in case you - change your mind. - - - - - Outbox, for messages you have written - but not yet sent. This will be empty unless you use - Evolution while offline. - - - - - - - - Navigating without the Folder Bar - - You don't need the folder bar or the shortcut bar to move - around the main window. You can use Tab to - switch from one part of the window to another, and the folder - menu on the right side of the window just below the toolbar - to move about the folder tree. - - - - - To create a new folder, select - File New - Folder. You'll be asked where you want to - put it, and what kind of folder it should be. You can choose - from three types: Mail, for storing mail, - Calendar for storing calendars, and - Contacts for storing contacts. - - - - Folders Have Limits - - Calendars must go in calendar folders, mail in mail - folders, and contacts in contact folders. - - - - - Right-clicking will bring up a menu for just about anything - in GNOME, and Evolution is no - exception. If you right-click on a folder, you'll have a - menu with the following options: - - FIXME, for another purpose. - Something else, for another purpose. - . - - - - Context-Sensitive Help - - GNOME 2.0 will support context-sensitive help, which means 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, choosing Help from - the right-click menu is a good way to find out. - - - - - Any time new information arrives in a folder, that folder label - is displayed in bold text. - - - To delete a folder, right-click it and select - Delete from the menu that pops up. - To change the order of folders, or put one inside another, use - drag-and-drop. To move individual - messages, appointments, and address cards between folders, you - can do the same thing: drag them where you want them, and - they'll go. - - - - The Menu Bar - - The menu bar's contents will always - provide all the possible actions for any given view of your - data. That means that, depending on the context, menu bar items - will change. If you're looking at your Inbox, most of the menu - items will relate to mail; some will relate to other components - of Evolution and some, especially - those in the File Menu will relate to the - application as a whole. The contents of the menu bar are - described in . - - - - - File Menu - - - Anything even related to a file or to the operations - of the application generally falls under this - menu: creating things, saving them to disk, - printing them, and quitting the program itself. - - - - - - Edit Menu - - The Edit menu holds - useful tools that help you edit text and move it around. - - - - - View Menu - - This menu lets you decide how Evolution - should look. Some of the features control the appearance of - Evolution as a whole, and others - the way a particular kind of information appears. - - - - - Settings Menu - Tools for configuring, changing, and - setting up go here. For mail, that means things like - Mail Configuration and the - Virtual Folder Editor. For the - Calendar and the Contact - Manager, it's color, network, and layout - configuration. - - - - Help Menu - - Select among these items to open the - Help Browser - and read the Evolution manual. - - - - - - Other menus, like Folder, - Message, and Actions, - appear only occasionally. Message and - Folder, for example, have commands that only - relate to email, so they're only available when you're looking at - email. - - - Once you've familiarized yourself with the main - window you can start doing things with it. We'll - start with your email inbox, since you've got a letter waiting - for you already. - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/doc/C/usage-notes.sgml b/doc/C/usage-notes.sgml deleted file mode 100644 index 1ff2283128..0000000000 --- a/doc/C/usage-notes.sgml +++ /dev/null @@ -1,49 +0,0 @@ - - Evolution Notes - - An Overview of the Evolution Notes - - In the dark ages before email was invented, there were little - scraps of people which people used for short-term information - storage. These scraps of paper were called notes. Now, notes - are an almost necessary part of our lives, albeit in electronic - form. It only makes sense, then, that - Evolution will eventually have a - Notes feature. Evolution can help - you take notes in the following ways: - - - - Take down phone numbers, take school notes, take phone - messages, or even write poetry. - - - - - Color code notes to organize them, or just to - make them look good. - - - - - Turn a note into an email or a text file. - - - - - Write Haiku - - - - - - You can start writing notes by clicking - Notes in the shortcut bar. Of course, - it's not there yet. But when it is, it'll take you to the - notepad. - - - - - - diff --git a/doc/C/usage-print.sgml b/doc/C/usage-print.sgml deleted file mode 100644 index cc1ac16357..0000000000 --- a/doc/C/usage-print.sgml +++ /dev/null @@ -1,105 +0,0 @@ - -Printing with Evolution - - This is a very short chapter, because printing with - Evolution is not a complex task. Like - most GNOME applications, Evolution uses - the gnome-print system, so if you've used any other GNOME - application to print, you should be able to print from - Evolution immediately. - - - Whether you're printing a message, a calendar page, or a selection - of address cards, you can choose to print directly to a printer, or - save the print output to a postscript file. You can also use the - preview feature to see how your printed output will look. - - - - Print Preview - - Print Preview appears both as a button in - the printing dialog and as an item in the - File menu. In both places, it does the same - thing: it opens a new window that shows you what would happen if - you were to print the current message, calendar, appointment, or - address card. - - - That window allows you to select which pages you want to see, - and how close you'd like to look at them. Zoom in or out, fit - the page to the window (the Fit button) - or match the width of the page and the window (the - Fit Width button). None of these buttons - changes the way the page will be printed, but they do let you - get a better look. If you're satisfied with the way the things - look, click Print to send your document - on its way. If you'd like to change it, just close the - Print Preview window and make the changes - you want from the Mail, Calendar, or Contact Manager. - - - - - - - - - - - - File or Printer? - - The printer selection window, shown in , lets you choose the format for - printing— at this time, only Generic - Postscript is available— and whether to print - to a file or to an actual printer. If you choose a printer, - you'll be asked for the printer command (probably - lpr) which your system uses. If you - choose to print to a file, you'll need to decide upon a - filename. And of course, you'll want to choose a number of - copies, and whether to collate them. - - - - - - - - - If you're printing a message that's more than one page, you'll - have the option of choosing which pages to print. If you're - printing a calendar entry, you can decide what range of dates to - print. And, if you're printing contact cards, you can decide - whether to print only the selected cards, or all of them. - - - When you're ready, click Print to print, - Preview to have a look (or another look) - at the preview, or Cancel to cancel the - whole deal. - - - - - - - - - - diff --git a/doc/C/usage-sync.sgml b/doc/C/usage-sync.sgml deleted file mode 100644 index a6b53e9526..0000000000 --- a/doc/C/usage-sync.sgml +++ /dev/null @@ -1,20 +0,0 @@ - - - Synchronizing with a Hand-held Device - - This chapter covers is how to synchronize data - installed and configured. If you need information on how to - set up a synchronization system, consult . - - - Using HotSync - - Put your hand-held device on its cradle and press the - HotSync button. - - - No, really. That's all there is to it. - - - \ No newline at end of file diff --git a/doc/COPYING-DOCS b/doc/COPYING-DOCS deleted file mode 100644 index b42936beb3..0000000000 --- a/doc/COPYING-DOCS +++ /dev/null @@ -1,355 +0,0 @@ - GNU Free Documentation License - Version 1.1, March 2000 - - Copyright (C) 2000 Free Software Foundation, Inc. - 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - -0. PREAMBLE - -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. - -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. - -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. - - -1. APPLICABILITY AND DEFINITIONS - -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 "Document", below, refers to any -such manual or work. Any member of the public is a licensee, and is -addressed as "you". - -A "Modified Version" 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. - -A "Secondary Section" is a named appendix or a front-matter section of -the Document that deals exclusively with the relationship of the -publishers or authors of the Document to the Document's overall subject -(or to related matters) and contains nothing that could fall directly -within that overall subject. (For example, if the Document is in part a -textbook of mathematics, a Secondary Section may not explain any -mathematics.) The relationship could be a matter of historical -connection with the subject or with related matters, or of legal, -commercial, philosophical, ethical or political position regarding -them. - -The "Invariant Sections" are certain Secondary Sections whose titles -are designated, as being those of Invariant Sections, in the notice -that says that the Document is released under this License. - -The "Cover Texts" are certain short passages of text that are listed, -as Front-Cover Texts or Back-Cover Texts, in the notice that says that -the Document is released under this License. - -A "Transparent" copy of the Document means a machine-readable copy, -represented in a format whose specification is available to the -general public, whose contents can be viewed and edited directly and -straightforwardly with generic text editors or (for images composed of -pixels) generic paint programs or (for drawings) some widely available -drawing editor, and that is suitable for input to text formatters or -for automatic translation to a variety of formats suitable for input -to text formatters. A copy made in an otherwise Transparent file -format whose markup has been designed to thwart or discourage -subsequent modification by readers is not Transparent. A copy that is -not "Transparent" is called "Opaque". - -Examples of suitable formats for Transparent copies include plain -ASCII without markup, Texinfo input format, LaTeX input format, SGML -or XML using a publicly available DTD, and standard-conforming simple -HTML designed for human modification. Opaque formats include -PostScript, PDF, proprietary formats that can be read and edited only -by proprietary word processors, SGML or XML for which the DTD and/or -processing tools are not generally available, and the -machine-generated HTML produced by some word processors for output -purposes only. - -The "Title Page" 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, "Title Page" means -the text near the most prominent appearance of the work's title, -preceding the beginning of the body of the text. - - -2. VERBATIM COPYING - -You may copy and distribute the Document in any medium, either -commercially or noncommercially, provided that this License, the -copyright notices, and the license notice saying this License applies -to the Document are reproduced in all copies, and that you add no other -conditions whatsoever to those of this License. You may not use -technical measures to obstruct or control the reading or further -copying of the copies you make or distribute. However, you may accept -compensation in exchange for copies. If you distribute a large enough -number of copies you must also follow the conditions in section 3. - -You may also lend copies, under the same conditions stated above, and -you may publicly display copies. - - -3. COPYING IN QUANTITY - -If you publish printed copies of the Document numbering more than 100, -and the Document's license notice requires Cover Texts, you must enclose -the copies in covers that carry, clearly and legibly, all these Cover -Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on -the back cover. Both covers must also clearly and legibly identify -you as the publisher of these copies. The front cover must present -the full title with all words of the title equally prominent and -visible. You may add other material on the covers in addition. -Copying with changes limited to the covers, as long as they preserve -the title of the Document and satisfy these conditions, can be treated -as verbatim copying in other respects. - -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. - -If you publish or distribute Opaque copies of the Document numbering -more than 100, you must either include a machine-readable Transparent -copy along with each Opaque copy, or state in or with each Opaque copy -a publicly-accessible computer-network location containing a complete -Transparent copy of the Document, free of added material, which the -general network-using public has access to download anonymously at no -charge using public-standard network protocols. If you use the latter -option, you must take reasonably prudent steps, when you begin -distribution of Opaque copies in quantity, to ensure that this -Transparent copy will remain thus accessible at the stated location -until at least one year after the last time you distribute an Opaque -copy (directly or through your agents or retailers) of that edition to -the public. - -It is requested, but not required, that you contact the authors of the -Document well before redistributing any large number of copies, to give -them a chance to provide you with an updated version of the Document. - - -4. MODIFICATIONS - -You may copy and distribute a Modified Version of the Document under -the conditions of sections 2 and 3 above, provided that you release -the Modified Version under precisely this License, with the Modified -Version filling the role of the Document, thus licensing distribution -and modification of the Modified Version to whoever possesses a copy -of it. In addition, you must do these things in the Modified Version: - -A. Use in the Title Page (and on the covers, if any) a title distinct - from that of the Document, and from those of previous versions - (which should, if there were any, be listed in the History section - of the Document). You may use the same title as a previous version - if the original publisher of that version gives permission. -B. List on the Title Page, as authors, one or more persons or entities - responsible for authorship of the modifications in the Modified - Version, together with at least five of the principal authors of the - Document (all of its principal authors, if it has less than five). -C. State on the Title page the name of the publisher of the - Modified Version, as the publisher. -D. Preserve all the copyright notices of the Document. -E. Add an appropriate copyright notice for your modifications - adjacent to the other copyright notices. -F. Include, immediately after the copyright notices, a license notice - giving the public permission to use the Modified Version under the - terms of this License, in the form shown in the Addendum below. -G. Preserve in that license notice the full lists of Invariant Sections - and required Cover Texts given in the Document's license notice. -H. Include an unaltered copy of this License. -I. 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 Modified Version as given on the Title Page. If - there is no section entitled "History" in the Document, create one - stating the title, year, authors, and publisher of the Document as - given on its Title Page, then add an item describing the Modified - Version as stated in the previous sentence. -J. Preserve the network location, if any, given in the Document for - public access to a Transparent copy of the Document, and likewise - the network locations given in the Document for previous versions - it was based on. These may be placed in the "History" section. - You may omit a network location for a work that was published at - least four years before the Document itself, or if the original - publisher of the version it refers to gives permission. -K. 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. -L. Preserve all the Invariant Sections of the Document, - unaltered in their text and in their titles. Section numbers - or the equivalent are not considered part of the section titles. -M. Delete any section entitled "Endorsements". Such a section - may not be included in the Modified Version. -N. Do not retitle any existing section as "Endorsements" - or to conflict in title with any Invariant Section. - -If the Modified Version includes new front-matter sections or -appendices that qualify as Secondary Sections 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 Invariant Sections in the Modified Version's license notice. -These titles must be distinct from any other section titles. - -You may add a section entitled "Endorsements", provided it contains -nothing but endorsements of your Modified Version 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. - -You may add a passage of up to five words as a Front-Cover Text, and a -passage of up to 25 words as a Back-Cover Text, to the end of the list -of Cover Texts in the Modified Version. Only one passage of -Front-Cover Text and one of Back-Cover Text may be added by (or -through arrangements made by) any one entity. If the Document 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. - -The author(s) and publisher(s) of the Document do not by this License -give permission to use their names for publicity for or to assert or -imply endorsement of any Modified Version. - - -5. COMBINING DOCUMENTS - -You may combine the Document with other documents released under this -License, under the terms defined in section 4 above for modified -versions, provided that you include in the combination all of the -Invariant Sections of all of the original documents, unmodified, and -list them all as Invariant Sections of your combined work in its -license notice. - -The combined work need only contain one copy of this License, and -multiple identical Invariant Sections may be replaced with a single -copy. If there are multiple Invariant Sections with the same name but -different contents, make the title of each such section unique by -adding at the end of it, in parentheses, the name of the original -author or publisher of that section if known, or else a unique number. -Make the same adjustment to the section titles in the list of -Invariant Sections in the license notice of the combined work. - -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." - - -6. COLLECTIONS OF DOCUMENTS - -You may make a collection consisting of the Document 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. - -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. - - -7. AGGREGATION WITH INDEPENDENT WORKS - -A compilation of the Document 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 Modified Version -of the Document, 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 Document, on account of their being thus compiled, if they -are not themselves derivative works of the Document. - -If the Cover Text requirement of section 3 is applicable to these -copies of the Document, then if the Document is less than one quarter -of the entire aggregate, the Document's Cover Texts may be placed on -covers that surround only the Document within the aggregate. -Otherwise they must appear on covers around the whole aggregate. - - -8. TRANSLATION - -Translation is considered a kind of modification, so you may -distribute translations of the Document under the terms of section 4. -Replacing Invariant Sections with translations requires special -permission from their copyright holders, but you may include -translations of some or all Invariant Sections in addition to the -original versions of these Invariant Sections. You may include a -translation of this License provided that you also include the -original English version of this License. In case of a disagreement -between the translation and the original English version of this -License, the original English version will prevail. - - -9. TERMINATION - -You may not copy, modify, sublicense, or distribute the Document except -as expressly provided for under this License. Any other attempt to -copy, modify, sublicense or distribute the Document is void, and will -automatically terminate your rights under this License. However, -parties who have received copies, or rights, from you under this -License will not have their licenses terminated so long as such -parties remain in full compliance. - - -10. FUTURE REVISIONS OF THIS LICENSE - -The Free Software Foundation 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 -http://www.gnu.org/copyleft/. - -Each version of the License is given a distinguishing version number. -If the Document 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 Document does not specify a version -number of this License, you may choose any version ever published (not -as a draft) by the Free Software Foundation. - - -ADDENDUM: How to use this License for your documents - -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: - - Copyright (c) YEAR YOUR NAME. - 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 Invariant Sections being LIST THEIR TITLES, with the - Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. - A copy of the license is included in the section entitled "GNU - Free Documentation License". - -If you have no Invariant Sections, write "with no Invariant Sections" -instead of saying which ones are invariant. If you have no -Front-Cover Texts, write "no Front-Cover Texts" instead of -"Front-Cover Texts being LIST"; likewise for Back-Cover Texts. - -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 GNU General Public License, -to permit their use in free software. diff --git a/doc/Camel-Classes b/doc/Camel-Classes deleted file mode 100644 index 93aec087dd..0000000000 --- a/doc/Camel-Classes +++ /dev/null @@ -1,35 +0,0 @@ -CamelException -CamelProvider -CamelThreadProxy -CamelURL -GtkObject - + CamelObject - + CamelAddress - | + CamelInternetAddress - | ` CamelNewsAddress - + CamelDataWrapper - | + CamelMedium - | | ` CamelMimePart - | | ` CamelMimeMessage - | ` CamelMultipart - + CamelFolder - | ` CamelFolderPtProxy - + CamelFolderSearch - + CamelFolderSummary - + CamelMimeFilter - | + CamelMimeFilterBasic - | + CamelMimeFilterCharset - | + CamelMimeFilterIndex - | ` CamelMimeFilterSave - + CamelService - | + CamelStore - | ` CamelTransport - + CamelSession - + CamelStream - | + CamelSeekableStream - | | + CamelSeekableSubstream - | | + CamelStreamFs - | | ` CamelStreamMem - | + CamelStreamBuffer - | ` CamelStreamFilter - ` CamelThreadProxy \ No newline at end of file diff --git a/doc/ChangeLog b/doc/ChangeLog deleted file mode 100644 index 407bbbdde6..0000000000 --- a/doc/ChangeLog +++ /dev/null @@ -1,694 +0,0 @@ -2001-02-23 Aaron Weber - - * C/usage-mail.sgml: IMAP subscriptions stuff. - -2001-02-21 Aaron Weber - - * C/usage-mail.sgml: Advanced search/show all/save search stuff. - - * C/evolution.sgml: This file replaces evolution-guide.sgml, for Nautilus Readiness. - - * C/apx-gloss.sgml: glossterm conduit. - - * C/config-sync.sgml: Glossterm conduit. - - * C/preface.sgml: Checked over for Keyboard-Shortcut and other truthfulness. - -2001-02-15 Aaron Weber - - * C/evolution-guide.sgml: Validated. Verified. Markup fixed in - several individual files. - - * C/apx-gpl.sgml: cvs-removed for GNOME 1.4 compliance. - - * C/apx-fdl.sgml: cvs-removed for GNOME 1.4 compliance. - -2001-02-09 Aaron Weber - - * C/config-sync.sgml: Overhaul. Now accurate and truthful and clear. - - * C/usage-calendar.sgml: Minor Changes. - -2001-02-08 Aaron Weber - - * C/usage-contact.sgml: Minor Changes. - - * C/usage-mail.sgml: Minor Changes. - -2001-02-07 Aaron Weber - - * C/menuref.sgml: Added section, but left blank til UI stabilizes. - - * C/usage-exec-summary.sgml: A little functionality described. - - * C/usage-mainwindow.sgml: Added tasks and Exec-summary. - - * C/usage-calendar.sgml: Describe semi-autonomy of task pad. - -2001-02-06 Aaron Weber - - * C/usage-contact.sgml: s/contact manager/address book/ and - revised text. - - * C/usage-exec-summary.sgml: New file. Describes Executive Summary. - -2001-01-19 Aaron Weber - - * C/usage-mail.sgml: More of Megan's revisions, and Field Chooser - functions in the Sort section. - - * C/apx-gloss.sgml: added "ToolTip" - -2001-01-18 Aaron Weber - - * C/preface.sgml: s/Helix Code/Ximian, and Megan's comments. - - * C/usage-mainwindow.sgml: s/Helix Code/Ximian/, and Megan's - comments. - - * C/evolution-guide.sgml: s/Helix Code/Ximian/ - -2000-12-13 Aaron Weber - - * C/usage-mail.sgml: Revisions as suggested by Dan. Especially to - filter dialogs... which still need some renaming, IMHO. - - * C/usage-mainwindow.sgml: Revisions as suggested by - Dan. Especially to the Folder Limits thing, which still upsets me - somehow. - - * C/preface.sgml: Revisions as suggested by Dan. - -2000-11-29 Aaron Weber - - * C/config-setupassist.sgml: added some , added linkends to existing glossterms. - -2000-11-28 Aaron Weber - - * C/evolution-guide.sgml: Changed intro to Config section. Now - defines what, exactly, "configurable" means. - - * C/usage-print.sgml: Stylistic revisions. - - * C/usage-calendar.sgml: Stylistic revisions. - - * C/usage-contact.sgml: Stylistic revisions. - -2000-11-09 Aaron Weber - - * C/menuref.sgml: Message heading Right-Click Menu. - -2000-11-03 Aaron Weber - - * C/apx-gloss.sgml: The regexp example was quite wrong. Props to Sasha. - -2000-11-02 Aaron Weber - - * C/usage-contact.sgml: Style and spelling. - -2000-11-01 Aaron Weber - - * C/config-prefs.sgml: Fixed validation errors. - - * C/apx-gloss.sgml: Fixed HTML, style stuff. - - * C/usage-mail.sgml: Stylistic overhaul. - - * C/usage-mainwindow.sgml: Fixed groups in shortcut bar, fixed - folder navigation tips. - -2000-10-31 Aaron Weber - - * C/preface.sgml: Minor stylistic revisions. - -2000-10-30 Aaron Weber - - * COPYING-DOCS: New file. This is the official place to put the - FDL now. - - -2000-11-01 Radek Doulik - - * Keybindings: added composer keybindings description - -2000-10-25 Aaron Weber - - * C/menuref.sgml: Actions -> New Directory Server added. - - * C/config-prefs.sgml: Actions -> New Directory Server added. - - * C/usage-contact.sgml: Actions -> New Directory Server added. - - * C/menuref.sgml: Added mail Settings->Manage Subscriptions menu. - - * C/usage-mail.sgml: Subscriptions section added. Quite - incomplete, though. - -2000-10-11 Aaron Weber - - * C/evolution-guide.sgml: Re-checked validity of all files. Made - minor changes to menuref.sgml, usage-mail.sgml, usage-print.sgml to - bring up to spec. - - * C/usage-mail.sgml: Redid Filter & Vfolder to match the new & - improved functionality. - - * C/fig/*: Re-did remaining screenshots. - -2000-10-10 Aaron Weber - - * C/usage-print.sgml: New file, describing printing and print-preview. - - * C/fig/print-preview.png: New file. - - * C/fig/print-dest.png: New file. - - * C/evolution-guide.sgml: Added usage-print entity. - - * C/menuref.sgml: Fixed calendar menu stuff. - - * C/usage-mail.sgml: No more "Actions" menu, other assorted - menu-related changes. - -2000-10-06 Aaron Weber - - * C/fig/ * replaced a whole bunch of screenshots. - -2000-10-05 Aaron Weber - - * C/usage-contact.sgml: Described Search features. - - * C/menuref.sgml: Contact Manager menus fixed. - -2000-10-04 Aaron Weber - - * C/usage-contact.sgml: Fixed glossterms. - - * C/usage-mail.sgml: Fixed glossterms, filenames, spellchecked. - - * C/apx-gloss.sgml: Added "Inline," "VCard". - - * C/usage-mainwindow.sgml: Fixed glossterms, filenames. Spellchecked. - - * C/usage-mail.sgml: Fixed glossterms, filenames. Spellchecked. - - * C/evolution-guide.sgml: New Legalnotice. Removed FDL and GPL, - which are now included as part of the gnome-help package. - - * C/usage-contact.sgml: Spellcheck. Fixed some wording, and - responded to clahey's suggestions-- notably, commented out the - "add to master list" category feature. - - * C/usage-calendar.sgml: Spellcheck. Fixed wording, event overlap - description. - - * C/evolution-guide.sgml: Spellcheck. Commented out Notes - entities. - - * C/usage-notes.sgml: Spellchecked, then decided to comment out - this file/chapter and all references to it, since it's unlikely to - be implemented any time soon. - - * C/config-setupassist.sgml: Spellcheck. Other minor updates. May - need more work in the near future. - - * C/usage-sync.sgml: Now it's really short. And spelled correctly. - -2000-10-03 Aaron Weber - - * C/config-prefs.sgml: Mostly spelling. Still needs major - alteration. - - * C/menuref.sgml: s/Appintment/Appointment, fixed small errors, - ran spellcheck. Still needs lots of work, since many menus have - changed. - - * C/apx-gloss.sgml: Added Virus, Protocol, fixed vFolder, - spellchecked. - -2000-09-26 Aaron Weber - - * C/apx-gloss.sgml: Added sendmail and SMTP. - -2000-09-22 Aaron Weber - - * C/menuref.sgml: Changed to reflect new menu layout. - - * C/usage-mainwindow.sgml: Changed to reflect new menu layout. Again. - - * C/usage-contact.sgml: Stop and Display All features. - -2000-09-21 Aaron Weber - - * C/evolution-guide.sgml: Switched to the "official" FSF markup. - I will have to make changes to the markup-- adding ids, etc, or - switch to another version of the markup. Pending discussion by - GDP. - - * C/apx-authors.sgml: Changed Matt Loper's email address to - loper.org; added Jeff Stedfast and Peter Williams to authors list, - realphebetized. - - * C/config-prefs.sgml: Revision to reflect current options labelling. - - * C/evolution-guide.sgml: Changes to part intros. - - * C/preface.sgml: Spelling and menu fixes. Will need more work tomorrow. - -2000-09-20 Aaron Weber - - * C/config-prefs.sgml: Fixed sig stuff here and in setupassist. - - * C/config-sync.sgml: Fixed description of conduit usage. - -2000-09-18 Aaron Weber - - * C/preface.sgml: Spelling fixes, etc. - -======= -2000-09-19 Federico Mena Quintero - - * C/Makefile.am: Fixed to install the stylesheet-images as well. - ->>>>>>> 1.26 -2000-09-07 Aaron Weber - - * C/fig/ New files: contact-editor.png, mail-composer.png, - filter-assist-fig.png, mail-inbox.png - -2000-09-07 Aaron Weber - - * C/preface.sgml: Redid "soft" intro stuff. - - * C/evolution-guide.sgml: Accidentally broke docs, now valid. - -2000-09-06 Aaron Weber - - * C/usage-contact.sgml: Editing, proofing. - -2000-09-05 Aaron Weber - - * C/usage-contact.sgml: Grammar, links, screenshots. - - * fig/* Re-took most screenshots. - - * C/usage-mail.sgml: Filters, proofing. - -2000-09-01 Aaron Weber - - * C/config-prefs.sgml: Added coverage of news, clarified POP/IMAP - distinction (there's a theme to these four log entries here). - - * C/usage-mail.sgml: Added coverage of news. - - * C/config-setupassist.sgml: Revised mail sources content for - IMAP/POP stuff. - - * C/apx-gloss.sgml: Added IMAP and POP. - -2000-08-31 Aaron Weber - - * C/apx-gloss.sgml: Added regular expressions to glossary. - Explanation should be removed from other portions of the book now. - - * C/usage-mainwindow.sgml: Revisions, minor. - - * C/apx-menuref.sgml: Now named menuref.sgml, to reflect its new - status as a part. - - * C/evolution-guide.sgml: Structural alterations: Menuref is now a - part, not an appendix. - - * C/apx-menuref.sgml: Added contextual menus for mail. - - * C/preface.sgml: Added "quickref and pointers" sections. Props to - O'Reilly for the copy of Outlook in a Nutshell which gave me the - idea. - -2000-08-30 Aaron Weber - - * C/usage-mainwindow.sgml: Minor fixes. - - * C/preface.sgml: Corrected grammar, added glossterms, described - menuref. - -2000-08-25 Aaron Weber - - * C/usage-mail.sgml: Redid filter and vFolder assistant - descriptions. - - * C/fig/filter-new-fig.png: Replaced with new assistant pic. - - * C/fig/filter-assist-fig.png: New file, showing only assistant. - - - * C/apx-menuref.sgml: Finished message composer and calendar - editor menus. Looked at Contact Editor menus and decided to - document those features after implementation. - -2000-08-24 Aaron Weber - - * C/apx-menuref.sgml: Message Composer File and Edit menus. - -2000-08-23 Aaron Weber - - * C/apx-menuref.sgml: Added editor sections. - - * C/evolution-guide.sgml: Included Menu Reference Appendix. - -2000-08-22 Aaron Weber - - * C/usage-mail.sgml: Minor markup changes. - - * C/apx-menuref.sgml: New File. Menu Reference. Still needs much - work, but not bad for an evening. - -2000-08-21 Aaron Weber - - * C/usage-mail.sgml: Kevin's diff applied, with minor changes. - -2000-08-09 Aaron Weber - - * C/evolution-guide.sgml: Fixed bugs in validation. Went home to - sleep. - - * C/usage-mainwindow.sgml: Redid menubar description. - - - * C/config-prefs.sgml: Added coverage of folder config, requested - that feature be transferred to config section. Switched to - variablelist in "Other" config section. - - * C/usage-mail.sgml: Added coverage of right-click on messages, - threaded-view. - - * C/usage-mainwindow.sgml: Right-click on folder menu reinstated. - -2000-08-07 Aaron Weber - - * C/config-prefs.sgml: Added news server coverage. Other config - proofing changes. - - -2000-08-05 Aaron Weber - - * C/apx-gpl.sgml: New file. Contains contents of "COPYING", - but marked up (probably not very well, but valid) as docbook - (SGML). - - * C/evolution-guide.sgml: Subtle change to the legal notice: - distinguished manual license from software license. Linked to - apx-gpl.sgml above. - - * C/usage-calendar.sgml: I redid all the usage files. - -2000-07-21 Aaron Weber - - * C/usage-mail.sgml: Added password remembering/forgetting feature. - - * C/config-prefs.sgml: Mostly moved to variablelists, a few - language changes. - - * C/config-setupassist.sgml: Minor changes to formatting, wording. - - * C/usage-notes.sgml: Changed trademark references, other minor - changes. - - * C/usage-calendar.sgml: Minor fixes, added additional calendar - section, removed references to unimplemented features. Spellcheck, - prep for 0.3 release. - -2000-07-19 Aaron Weber - - * C/usage-mail.sgml: lots of minor fixes to language. added - desc. of clahey's cool button-address thing. - - * C/usage-mainwindow.sgml: fixed itemizedlists, ch. to shortcut - bar & folder descs, removed refs to trash. - -2000-07-18 Aaron Weber - - * C/usage-contact.sgml: Altered category addition stuff, plus - suggestions from Kevin. - - * C/apx-gloss.sgml: Added ldap and signature definitions (from - Kevin). - - * C/usage-mail.sgml: Move to variablelists from itemizedlists. - -2000-07-14 Aaron Weber - - * C/usage-contact.sgml: moved to variablelists from itemizedlists - * C/usage-calendar.sgml: moved to variablelists from itemizedlists - -2000-06-29 Aaron Weber - - * C/preface.sgml: Minor fixes. - - * C/usage-notes.sgml: New File for feature that is yet to come. - * C/evolution-guide.sgml: Added entity for notes chapter. - * C/usage-mainwindow.sgml: Un-commented references to notes section. - - * C/apx-authors.sgml: Removed dcm from author list. - - * C/usage-calendar.sgml: Added to-do list features. - -2000-06-28 Aaron Weber - - * C/usage-contact.sgml: commented out future features; redid - contact editor stuff. - - * C/apx-gloss.sgml: Removed "live doc" and added "minicard" - -2000-06-27 Aaron Weber - - * C/devel-action.sgml: Removed file. - * C/devel-script.sgml: Same. - * C/devel-component.sgml: Same. - * C/preface.sgml: Removed references to devel section. - * C/evolution-guide.sgml: Removed references to devel section. - -2000-06-23 Aaron Weber - - * C/evolution-guide.sgml: Made moderate to major stylistic updates - to this, apx-gloss.sgml, and to all files beginning with "usage," - especially wrt HTML mail. - - -2000-06-15 Aaron Weber - - * C/usage-contact.sgml: Category stuff improved. - - * C/usage-calendar.sgml: Now covers how to add an event properly. - -2000-07-17 Federico Mena Quintero - - * Makefile.am (SUBDIRS): Added the devel directory. - -2000-06-28 Peter Williams - - * C/Makefile.am (SGML_FILES): Don't depend on the newly-removed - devel-*.sgml files. - -2000-06-16 Damon Chaplin - - * C/.cvsignore: added evolution-guide and evolution-guide.junk - so we don't get the '? doc/C/evolution-guide' messages each time we - do a cvs update. - -2000-06-14 Aaron Weber - - * C/usage-mainwindow.sgml: added sect on menubar, other minor changes. - - * C/usage-mail.sgml: Improved filter and vfolder - description, and some minor changes from me and Kevin. - -2000-06-07 Aaron Weber - - * C/config-prefs.sgml: finished adding calendar prefs. screenshots. - * C/fig/config-cal.png: new file (screenshot for above) - * C/fig/config-mail.png: same - -2000-06-05 Aaron Weber - - * C/usage-calendar.sgml: Incorporated chgs from Kevin. - - * C/config-prefs.sgml: began total overhaul of structure and added - content reflecting new prefs items. needs LOTS more work. - - * C/usage-mail.sgml: changed some references to id's in the - config-prefs section. - - * C/fig/config-mail.png: changed filename from config-prefs.png - -2000-06-01 Aaron Weber - - * C/config-prefs.sgml: filename was wrong, altered. - - * C/usage-mail.sgml: improved filter instructions, vFolder - instructions. still need work though. - - - * C/usage-contact.sgml: added screenshot. - - * C/usage-calendar.sgml: added screenshot. - - * C/config-prefs.sgml: added screenshots, and now describes the - actual prefs dialogs. - - * C/fig/config-camel.png: new (screenshot) file - * C/fig/filter-druid.png: same - * C/fig/vfolder-druid.png: same - * C/fig/calendar.png: same - * C/fig/contact.png: same - * C/fig/vfolder-createrule-fig.png: same - * C/fig/filter-new-fig.png: same - * C/fig/config-camel.png: same - -2000-06-01 Dan Winship - - * Makefile.am: recurse into the C directory - - * C/Makefile.am: Rules to build and install the docs. Mostly - stolen from gnomecal. Only works if you have GDP stuff - (http://www.gnome.org/gdp/) set up on your machine, but won't make - the build fail if you don't. - -2000-05-29 Aaron Weber - - * C/usage-contact.sgml: incorporated kevins notes. - * C/usage-mainwindow.sgml: incorporated kevins notes. - -2000-05-27 Aaron Weber - - * C/evolution-guide.sgml: added Kevin Breit to author and - copyright. - - * C/apx-authors.sgml: Put app authors in a simplelist. - - * C/usage-mail.sgml: Removed USAGE-SETUP insertion, added xref to send - users to config-setupassist chapter. This and the following changes - take setup druid coverage out of usage - section and put it in config section. - * C/config-setupassist.sgml: Added mail druid coverage from - usage-setup.sgml. - * C/usage-setup.sgml: Removed file. contents in - config-setupassist.sgml. - * C/evolution-guide.sgml: Removed - USAGE-SETUP entity (and file usage-setup.sgml.) - - -2000-05-26 Aaron Weber - - * C/fig/mainwindow-pic.png: new file - * C/fig/mail-druid-pic.png: new file - * C/fig: New directory, for figure graphics. - - * C/apx-gloss.sgml: new file. glossary. thx. to kevin from chicago. - - * C/usage-setup.sgml: More accurate description of druid, and - moved to mail section-- see usage-mail.sgml entry. This is a new - location for this entity, and it may move more later. - - - * C/usage-mainwindow.sgml: altered description of starting - evolution. added screenshot for main-window picture. - - * C/usage-mail.sgml: added screenshots, added coverage of setup - druid and put it into get-and-send section, which is probably not - where it should stay. Also started filter druid coverage and - clarified examples, esp. in Bcc: section. - - * C/usage-contact.sgml: Clarified examples. - - * C/preface.sgml: rewording of "what is" and "about book" sections. - - * C/evolution-guide.sgml: added glossary entity APX-GLOSS, altered - phrasing in part intros, changed order of Setup-assistant section. - - * C/config-prefs.sgml: changed wording, removed ref. to re-running - setup assistant. - -2000-05-18 Aaron Weber - - * C/evo_book_0.1.sgml: removed. - - * C/apx-authors.sgml: new file. - * C/apx-bugs.sgml: same. - * C/apx-fdl.sgml: same. - * C/config-prefs.sgml: same. - * C/config-setupassist.sgml: same. - * C/config-sync.sgml: same. - * C/devel-action.sgml: same. - * C/devel-component.sgml: same. - * C/devel-script.sgml: same. - * C/evolution-guide.sgml: same. - * C/preface.sgml: same. - * C/usage-calendar.sgml: same. - * C/usage-contact.sgml: same. - * C/usage-mail.sgml: same. - * C/usage-mainwindow.sgml: same. - * C/usage-setup.sgml: same. - * C/usage-sync.sgml: same. - -2000-05-07 Dan Winship - - * Camel-Classes: sync - -2000-04-16 Aaron Weber - - * C/evo_book_0.1.sgml: new file (doc sgml) - - * C/ : New directory for doc sgml & graphics - -2000-03-05 Christopher James Lahey - - * white-papers/widgets/e-table.sgml: Added Miguel to the author - list for ETable. - -2000-03-03 Christopher James Lahey - - * white-papers/widgets/, white-papers/widgets/e-table.sgml: New - doc for the ETable widget. - - * ChangeLog: Created a ChangeLog file for the docs file and - integrated the individual ChangeLogs. - -2000-03-01 Dan Winship - - * ibex.sgml: Ibex white paper - -2000-02-29 Federico Mena Quintero - - * calendar.sgml: Sections for the calendar user agent and the - calendar client library. - -2000-02-29 Dan Winship - - * camel.sgml: Reorg a bit more, make the 
 section narrower,
-	add more references to graphics (the graphics themselves are
-	still in beta), add a section on CamelStream.
-
-2000-02-28  Federico Mena Quintero  
-
-	* calendar.sgml: Section for the personal calendar server.
-
-2000-02-28  Dan Winship  
-
-	* camel.sgml: add Bertrand to authors, edit his additions
-
-2000-02-28  bertrand  
-
-	* camel.sgml: add a blurb about camel offering
-	uniform interface. needs style and grammar corrections. 
-	Talk about virtual folders.
-	Talk about lightweight messages
-	Talk about IMAP. 
-
-2000-02-28  Dan Winship  
-
-	* camel.sgml: Beginnings of a Camel white paper
-
-2000-02-25  Federico Mena Quintero  
-
-	* calendar.sgml: New file for the Evolution calendaring white paper.
diff --git a/doc/Design b/doc/Design
deleted file mode 100644
index 7b7cf6f821..0000000000
--- a/doc/Design
+++ /dev/null
@@ -1,201 +0,0 @@
-
-The Evolution Project specification
-Miguel de Icaza.
-
-
-* Introduction
-
-	Evolution is a project aiming at providing the free software
-	community with a professional, high-quality tool for managing
-	mail, appointments, tasks and other personal information
-	tools.  
-
-	We want to make Evolution a system that addresses our needs
-	(the free software development community) and we believe that
-	by addressing our needs, we will provide a system that will
-	scale in the years to come for other users that are just
-	starting to use computers and the internet.
-
-	The main objectives of Evolution are to provide these powerful
-	features, and to make the user interface as pretty and
-	polished as possible.
-
-	Evolution is a GNOME application and a number of auxiliary
-	CORBA servers that act as the storage backends. 
-
-	Evolution will copy the best user interface bits and the best
-	ideas and features found on contemporary groupware systems.
-
-* Evolution internals.
-
-	Evolution can store its information locally (files for mail,
-	calendar and address book) or on a remote server (imap/pop,
-	cap, ldap).  
-
-	Given the importance of syncing in this modern PDA world,
-	the Evolution GUI acts as a client to the data repository.
-	The data repository is a GUI-less CORBA server called Wombat.
-
-	Wombat provides a unified access system to the calendar and
-	addressbook data (doing mail is a bit hard, so we are leaving
-	this as a TODO item for now).
-
-	Wombat's CORBA interfaces are notifier-based.  This means that
-	CORBA requests sent to Wombat do not return values
-	inmediately, but rather than for Wombat requests the user has
-	to provide a CORBA object that will be notified of what
-	happened.
-
-	Yes, that sounds hairy.  It is actually pretty simple.  It
-	basically means that you submit requests to Wombat, and a
-	callback is invoked in your code when the request has been
-	carried away. 
-
-	This enables a Palm to sync to the repository without having
-	the GUI for Evolution running.  It also means that volunteers
-	will be able to write text-based and web-based versions of
-	Evolution (not me though :-).
-
-* Evolution as a platform
-
-	Evolution is more than a client for managing the above
-	information: Evolution is a platform for building groupware
-	applications that use the above components to get their work done.
-
-	To achieve this Evolution is designed to be scriptable, and it
-	exports its internals trough CORBA/Bonobo.  It is implemented
-	as a collection of Bonobo containers and Bonobo components.
-
-	There is a clean separation between the views (the user
-	interface) and the model (the view).  The views that we are
-	writing are GNOME based, and they talk to the Wombat CORBA
-	server.
-
-	Wombat takes care of notifications to the various clients for
-	the data. 
-
-* The overall organization
-
-	A bar similar to outlook provides shortcuts for accessing the
-	various resources managed by Evolution: mail folders,
-	contacts, tasks, journal entries, notes, messages and other
-	user-defined destinations. 
-
-* User interface widgets
-
-** The ETable package
-
-	This package provides a way of displaying and editing tables.
-
-	Tables are displayed based on a TableColumn definition that
-	defines the layout used for the display.  Table Columns can be
-	nested, and the package does grouping of information displayed
-	according to the criteria defined there.
-
-	This is used in multiple places troughout evolution: it is
-	used for the Mail summary display, for the TODO display and
-	TODO new data entry and for the address book.
-
-	Nesting in the address book can be performed on various
-	fields.  For example, a first level of nesting could be
-	"Company" and a second level would be "Country" the result is
-	a 2-level tree that can be collapsed expanded and contains the
-	information sorted/grouped by those two criteria.
-
-	The user interface for this will be copied from Outlook: the
-	possibility of adding and removing fields with drag and drop
-	as well as grouping using drag and drop.
-
-* The Mail system
-
-** The Mail sources
-
-	The mail system will support 4 sources of mail:
-
-		POP3 (transfer to a local file).
-		IMAP
-		Local mbox format in $MAIL.
-		Local mbox format that have other delivery points.
-
-	On top of that, it will be possible to browse existing mbox
-	archives (and possibly other formats in the future, like
-	Mailbox and Maildir).
-
-** Storing the mail
-
-	Mail that gets incorporated into the system is stored in mbox
-	format, and summary files are provided for quick access to the
-	files.  No modifications to the file on disk is performed (I
-	am not quite sure about this, perhaps we want to add the
-	status flags and some method for adding metadata to the mail).
-
-	Summary files are rebuilt on demand or rebuild if the mbox
-	file and the summary file have got out of sync.
-
-	A Metadata system that will enable us to attach information to
-	a message will have to be designed and implemented (enabling
-	users to add annotations to mails, and special keywords and
-	flags in a per-message fashion).
-
-** Folders
-
-	Michael Zucchi is working on a system that will let users
-	easily define rules for splitting their incoming mail into
-	physical folders.  
-
-	A further refinement to Folders are Virtual Folders.  This
-	basically provides a powerful search and viewing facility for
-	mail.  It works like this: when a mail is "incorporated" into
-	Evolution it is scanned and indexed.
-
-	Then users can enter queries into Evolution that will search
-	the entire database of messages.	
-
-** Virtual folders
-
-	Virtual folders will enable users to read/browse their mail in
-	new ways: by specifying search criterias, these folders will
-	contain messages that match the criteria given.  
-
-	There is more information about this in the libcamel
-	directory. 
-
-	We will index all headers from a message, and possible the
-	contents of messages and keep those on a separate file, to
-	enable users to query their mail database.
-
-** Mail summary display
-
-	The summary will be displayed using the ETable package, to
-	enable users to add a number of sorting criteria and various
-	display methods for the summary view.
-
-	The Outlook methods for displaying will be present on the
-	system.
-
-	Message threading will be supported in Evolution.
-
-** Message display engine
-
-	We are going to be using a combination of
-	libcamel/limime/libjamie to parse messages and render them
-	into an HTML buffer.
-
-* The HTML engine
-
-	The GtkHTML engine will be used to display messages, and will
-	be extended to support a number of features that we require:
-	internal handling of characters will be based on Unicode
-
-* The message composer
-
-	Regular features found in composers will be added: connecting
-	the composer to the address book, support for drag and drop
-	for including attachments, editing the message, archiving
-	drafts and archiving messages sent.
-
-	Ettore has been working on adding editing support to the
-	GtkHTML and he is working currently on a Bonobo component that
-	will provide a ready-to-use Bonobo control for embedding into
-	other applications.
-
diff --git a/doc/Keybindings b/doc/Keybindings
deleted file mode 100644
index f232802110..0000000000
--- a/doc/Keybindings
+++ /dev/null
@@ -1,13 +0,0 @@
-* Keybindings for the mailer
-
-	Delete key: 	Deletes message, moves forward.
-	
-* Keybindings for the composer
-
-	Control-s:		Saves message to file.
-	Control-w:		Closes composer window.
-	Control-Return: 	Sends message now.
-
-	F6:			Opens find dialog.
-	F7:			Opens replace dialog.
-
diff --git a/doc/Makefile.am b/doc/Makefile.am
deleted file mode 100644
index 7b5420fee8..0000000000
--- a/doc/Makefile.am
+++ /dev/null
@@ -1 +0,0 @@
-SUBDIRS = C devel
diff --git a/doc/NAMESPACE b/doc/NAMESPACE
deleted file mode 100644
index 4ca7c454d1..0000000000
--- a/doc/NAMESPACE
+++ /dev/null
@@ -1,65 +0,0 @@
-
-	Here is how both the Evolution implementation and IDL namespacing
-is to be organized, NB. for implementations and oafinfo filenames we replace
-'/' with '_'
-
-Files:
-
-/GNOME/Evolution/
-
-	Addressbook/
-	Calendar/
-		Control
-		gnomecal
-	Composer/
-	Mail/
-	Notes/		
-	Shell/
-	Summary/
-		test
-		rdf
-	Wombat/
-
-Components:
-
-	Shell components end in _ShellComponent, controls in _Control,
-executive summary components in _ExecutiveSummaryComponent and
-factories append 'Factory'.
-
-GNOME/
-	Evolution/
-
-		Shell
-
-		Addressbook/
-			MiniCard/
-				Control, ControlFactory
-			SelectNames, SelectNamesFactory
-			Control, ControlFactory
-			ShellComponent, ShellComponentFactory
-		Calendar/		
-			iTip/
-				Control, ControlFactory
-			Control, ControlFactory
-			ShellComponent, ShellComponentFactory
-			ExecutiveSummaryComponent, ExecutiveSummaryComponentFactory
-		Mail/
-			Control, ControlFactory
-			ShellComponent, ShellComponentFactory
-			ExecutiveSummaryComponent, ExecutiveSummaryComponentFactory
-			Composer, ComposerFactory
-		Notes/
-			control, controlFactory
-			shellComponent, shellComponentFactory
-		Summary/
-			rdf/
-				SummaryComponent, SummaryComponentFactory
-			test/
-				Component, ComponentFactory
-
-			ShellComponent, ShellComponentFactory
-
-		Wombat/
-			ServerFactory
-			CalendarFactory
-
diff --git a/doc/devel/.cvsignore b/doc/devel/.cvsignore
deleted file mode 100644
index c24a54fbcc..0000000000
--- a/doc/devel/.cvsignore
+++ /dev/null
@@ -1,4 +0,0 @@
-Makefile
-Makefile.in
-html
-evolution-devel-guide.html
diff --git a/doc/devel/ChangeLog b/doc/devel/ChangeLog
deleted file mode 100644
index d00a1df434..0000000000
--- a/doc/devel/ChangeLog
+++ /dev/null
@@ -1,159 +0,0 @@
-2001-01-26  John R. Sheets  
-
-	* importer/Makefile.am: Change (nonexistant) importer.sgml
-	references to evolution-importer.sgml to fix dependency problem.
-
-2001-01-17  Iain Holmes  
-
-	* Makefile.am (local_entities): Added the importer stuff.
-
-	* evolution-devel-guide.sgml: Added entities for the importer documents.
-
-	* reference.sgml: Added the public and private APIs for the importer.
-
-	* importer/*: New directory containing all the documenation for the
-	importer.
-
-2001-01-17  Federico Mena Quintero  
-
-	* evolution-devel-guide.sgml: Ximianified.
-
-	* calendar/evolution-calendar.sgml: Ditto.
-
-	* calendar/cal-util/evolution-cal-util-sections.txt: Updated.
-
-	* calendar/cal-client/evolution-cal-client-sections.txt: Updated.
-
-2001-01-10  Federico Mena Quintero  
-
-	* Makefile.am: Make it work when gtk-doc is not installed.
-
-	* calendar/cal-client/Makefile.am: Likewise.
-
-	* calendar/cal-util/Makefile.am: Likewise.
-
-2000-12-19  Federico Mena Quintero  
-
-	Added proper dependency lists to the gtk-doc mess.
-
-	* calendar/cal-client/Makefile.am (TARGET_DIR): Removed unused
-	variable.
-	(SOURCE_FILES): New variable with the list of source files we
-	depend on.
-	(IGNORED_SOURCE_HEADERS): New variable with the headers we ignore
-	for the gtkdoc-scan phase.
-	(scan_generated):
-	(tmpl_dependencies):
-	(tmpl_sources):
-	(tmpl_generated);
-	(sgml_dependencies):
-	(sgml_generated): Lists of stuff that is generated and that other
-	stuff depends on.
-	(all): Added the $(sgml_generated) as the final target.
-	(install-data-local): Added an installation hook; gtk-doc seems to
-	want some of its generated files to be installed.
-
-	* calendar/cal-client/evolution-cal-client-sections.txt: Updated.
-
-	* calendar/cal-util/Makefile.am: Made the same changes as for
-	calendar/cal-client/Makefile.am.
-
-	* calendar/cal-util/evolution-cal-util-sections.txt: Updated.
-
-	* Makefile.am (local_entities): Added alarm-generation.sgml.
-	(all): Made the main target be the html/index.html.
-
-2000-12-18  Federico Mena Quintero  
-
-	* calendar/alarm-generation.sgml: New file with a description of
-	the algorithm used to generate alarm instances.
-
-	* evolution-devel-guide.sgml: Added an entity for the above
-	chapter.
-
-	* calendar/evolution-calendar.sgml: Reference the entity here.
-
-	* calendar/Makefile.am (EXTRA_DIST): Added alarm-generation.sgml.
-
-2000-12-13  Larry Ewing  
-
-	* calendar/Makefile.am (EXTRA_DIST): make it public-reference.sgml
-	not referenc.sgml here.
-
-2000-11-29  Federico Mena Quintero  
-
-	* calendar/architecture.sgml: Finished the calendar architecture
-	chapter.
-
-2000-11-29  Federico Mena Quintero  
-
-	* evolution-devel-guide.sgml: Added an id for the API reference .
-	Added the FDL .
-	Added the preface and toplevel reference entities.
-	Added entities for Evolution, Wombat, and Camel.
-	Added an appendix for the GNU FDL.
-	
-	* preface.sgml: New file with the introduction to the Evolution
-	Developer's Guide.
-
-	* reference.sgml: Split the toplevel reference part into its own
-	file.
-
-	* fdl.sgml: Added the GNU Free Documentation License.
-
-	* calendar/evolution-calendar.sgml: Added an id for the .
-
-	* calendar/public-reference.sgml: Added an id for the .
-	Moved this file over from calendar/reference.sgml.
-
-	* Makefile.am (local_entities): Added a list of the SGML files
-	that define entities for inclusion in the toplevel document.  This
-	way we can track documentation file dependencies down to all
-	levels.
-	(html/index.html): Made the toplevel document depend on
-	$(local_entities).  Also, removed the "html" target and put its
-	contents directly here; this way we avoid having .PHONY targets.
-	(EXTRA_DIST): Removed the evolution_devel_guideDATA; it made no
-	sense.
-	(content_files): Added preface.sgml and reference.sgml.
-
-2000-09-15  Federico Mena Quintero  
-
-	* evolution-devel-guide.sgml: Made the toplevel  id be
-	"index".
-
-2000-08-14  Federico Mena Quintero  
-
-	* calendar/cal-util/*: Integrated the cal-util library into the
-	documentation framework.
-
-	* calendar/Makefile.am (SUBDIRS): Added the cal-util directory.
-
-	* evolution-devel-guide.sgml: Added entities for the cal-util stuff.
-	Added entity for libical.
-
-	* calendar/reference.sgml: Added the cal-util reference entries.
-
-	* calendar/cal-client/evolution-cal-client-sections.txt: Updated
-	for new API.
-
-2000-08-09  Peter Williams  
-
-	* Makefile.am (maintainer-clean-local): Don't depend
-	on 'clean'; this messes up maintainer-clean.
-
-2000-07-17  Federico Mena Quintero  
-
-	* calendar/cal-client/tmpl/cal-client.sgml: Populated.
-
-	* evolution-devel-guide.sgml: New  toplevel for the
-	Evolution Developer's Guide.
-
-	* calendar/evolution-calendar.sgml: New  for the calendar
-	developer's documentation.
-
-	* calendar/architecture.sgml: New  for the calendar
-	architecture.
-
-	* calendar/reference.sgml: New  for the calendar API
-	reference.
diff --git a/doc/devel/Makefile.am b/doc/devel/Makefile.am
deleted file mode 100644
index c5ee7a8e50..0000000000
--- a/doc/devel/Makefile.am
+++ /dev/null
@@ -1,84 +0,0 @@
-SUBDIRS = calendar importer executive-summary
-
-# The name of the module.
-DOC_MODULE=evolution-devel-guide
-
-# The top-level SGML file.
-DOC_MAIN_SGML_FILE=evolution-devel-guide.sgml
-
-HTML_DIR=$(datadir)/gnome/html
-
-TARGET_DIR=$(HTML_DIR)/$(DOC_MODULE)
-
-# Add your toplevel files here
-
-content_files =				\
-	evolution-devel-guide.sgml	\
-	fdl.sgml			\
-	preface.sgml			\
-	reference.sgml
-
-# Add your module's hand-written and auto-generated files here; these
-# are used for dependency tracking.
-
-local_entities =					\
-	calendar/alarm-generation.sgml			\
-	calendar/architecture.sgml			\
-	calendar/evolution-calendar.sgml		\
-	calendar/public-reference.sgml			\
-							\
-	calendar/cal-client/sgml/cal-client.sgml	\
-							\
-	calendar/cal-util/sgml/cal-component.sgml	\
-	calendar/cal-util/sgml/cal-recur.sgml		\
-	calendar/cal-util/sgml/cal-util.sgml		\
-	calendar/cal-util/sgml/timeutil.sgml		\
-							\
-	importer/sgml/evolution-importer.sgml		\
-	importer/sgml/evolution-importer-client.sgml	\
-							\
-	executive-summary/sgml/executive-summary-component.sgml	\
-	executive-summary/sgml/executive-summary-component-factory.sgml	\
-	executive-summary/sgml/executive-summary-component-factory-client.sgml	\
-	executive-summary/sgml/executive-summary-html-view.sgml
-
-EXTRA_DIST =			\
-	$(content_files)
-
-all: html/index.html
-
-if ENABLE_GTK_DOC
-html/index.html: $(content_files) $(local_entities)
-	test -d $(srcdir)/html || mkdir $(srcdir)/html
-	-cd $(srcdir)/html && gtkdoc-mkhtml $(DOC_MODULE) ../$(DOC_MAIN_SGML_FILE)
-else
-html/index.html:
-endif
-
-clean-local:
-	rm -f *~ *.bak *.signals *-unused.txt
-
-maintainer-clean-local:
-	cd $(srcdir) && rm -rf html
-
-if ENABLE_GTK_DOC
-install-data-local:
-	$(mkinstalldirs) $(DESTDIR)$(TARGET_DIR)
-	(installfiles=`echo $(srcdir)/html/*.html`; \
-	if test "$$installfiles" = '$(srcdir)/html/*.html'; \
-	then echo '-- Nothing to install' ; \
-	else \
-	  for i in $$installfiles; do \
-	    echo '-- Installing '$$i ; \
-	    $(INSTALL_DATA) $$i $(DESTDIR)$(TARGET_DIR); \
-	  done; \
-	  echo '-- Installing $(srcdir)/html/index.sgml' ; \
-	  $(INSTALL_DATA) $(srcdir)/html/index.sgml $(DESTDIR)$(TARGET_DIR); \
-	  echo '-- Fixing Crossreferences' ; \
-	  gtkdoc-fixxref --module=$(DOC_MODULE) --html-dir=$(HTML_DIR)|| true; \
-	fi)
-endif
-
-dist-hook:
-	mkdir $(distdir)/html
-	-cp $(srcdir)/html/*.html $(srcdir)/html/*.css $(distdir)/html
diff --git a/doc/devel/calendar/.cvsignore b/doc/devel/calendar/.cvsignore
deleted file mode 100644
index 282522db03..0000000000
--- a/doc/devel/calendar/.cvsignore
+++ /dev/null
@@ -1,2 +0,0 @@
-Makefile
-Makefile.in
diff --git a/doc/devel/calendar/Makefile.am b/doc/devel/calendar/Makefile.am
deleted file mode 100644
index 207672f303..0000000000
--- a/doc/devel/calendar/Makefile.am
+++ /dev/null
@@ -1,7 +0,0 @@
-SUBDIRS = cal-client cal-util
-
-EXTRA_DIST =				\
-	alarm-generation.sgml		\
-	architecture.sgml		\
-	evolution-calendar.sgml		\
-	public-reference.sgml
diff --git a/doc/devel/calendar/alarm-generation.sgml b/doc/devel/calendar/alarm-generation.sgml
deleted file mode 100644
index 77d35258da..0000000000
--- a/doc/devel/calendar/alarm-generation.sgml
+++ /dev/null
@@ -1,139 +0,0 @@
-  
-    How the Wombat generates alarm instances
-
-    
-      This chapter describes the algorithm that the &Wombat; uses
-      internally to generate instances of a calendar component's
-      alarms.  You do not need to read this chapter if you are simply
-      using the client-side functions.
-    
-
-    
-      What makes up an alarm trigger
-
-      
-	VTODO and VEVENT calendar components can have any number of
-	alarms defined for them.  Each alarm has a trigger
-	specification, an alarm type (display, audio, email, or
-	procedure), and data corresponding to the alarm type.  The
-	Wombat side of things is interested only in the trigger
-	specification, since this is all that the Wombat needs to
-	produce alarm instances.
-      
-
-      
-	An alarm trigger can be relative or absolute.  Relative
-	triggers occur a certain time before or after the start or end
-	of a calendar component's occurrence.  For example, you could
-	configure a trigger to notify you 15 minutes before an
-	appointment starts, so that you can get to its location on
-	time; or another one to notify you 5 minutes after another
-	person's meeting has ended, so that you can call that person
-	on the phone after the meeting and not disturb him while
-	there.  Absolute triggers occur at a specific point in time;
-	you can configure an alarm to trigger exactly at a particular
-	date and time that has no relation to the component's
-	occurrences at all.
-      
-    
-
-    
-      Generating trigger instances
-
-      
-	Generating absolute triggers is trivial; you just use the date
-	and time they specify.  However, relative triggers are
-	associated to recurrence instances, so in order to generate
-	trigger instances we must generate the corresponding
-	recurrence instances and compute the trigger times based on
-	those.
-      
-
-      
-	Since relative triggers are specified as occurring a certain
-	amount of time before or after each of a calendar component's
-	recurrence instances, we can compute a trigger time by adding
-	or subtracting that amount of time to the corresponding
-	recurrence instance's time.
-      
-
-      
-	Recurrence instances are generated by specifying a range of
-	time and asking the Wombat to generate the instances that
-	occur within that range.  We shall see that the range of time
-	in which instances occur is not necessarily the same range of
-	time in which those instances' alarm triggers occur.
-      
-
-      
-	Consider an alarm that is set to trigger 10 minutes before the
-	start time of an event's occurrence, that is, the trigger has
-	an offset of -10 minutes.  Say this event recurs every hour at
-	5 minutes past the hour:  it would occur at 1:05, 2:05, 3:05,
-	etc.; the corresponding triggers would occur at 12:55, 1:55,
-	2:55, etc.  If we wish to compute the alarm triggers that
-	occur between 4:00 and 6:00 (which would be at 4:55 and 5:55),
-	then we cannot just generate recurrence instances between 4:00
-	and 6:00 because we will miss the 6:05 occurrence which
-	corresponds to the 5:55 trigger.
-      
-
-      
-	The solution is to expand the range of time on both sides to
-	fit the relative triggers that have the largest time periods.
-	If a trigger's offset is negative, like the -10 minutes in the
-	example above, then we must expand the
-	end of the time range: in the case above,
-	the range's ending time of 6:00 must be grown by 10 minutes to
-	6:10 so that the last recurrence instance will be that of
-	6:05; computing the trigger's offset we will get the 5:55
-	trigger, which is what we wanted.  For triggers with positive
-	offsets, like if an alarm were to trigger 20 minutes after an
-	event's occurrence, we must expand the
-	start of the time range in an analogous
-	way, by subtracting the time offset from it.
-      
-
-      
-	Again, absolute triggers need no special computation.  We can
-	just see if the trigger time is within the requested range of
-	time, and if so, we take that trigger occurrence into account
-	for the final result.
-      
-    
-
-    
-      Alarm trigger generation code
-
-      
-	The main function to generate alarm trigger instances is
-	generate_alarms_for_comp() in
-	evolution/calendar/pcs/cal-backend-file.c.
-	This function calls compute_alarm_range()
-	to expand the specified range of time in the way described in
-	the previous section.  It then generates the instances for
-	relative alarm triggers inside the
-	add_alarm_occurrences_cb() callback,
-	which is used by
-	cal_recur_generate_instances() with the
-	expanded range of time.  The callback goes through all of the
-	calendar component's relative alarm triggers and adds the
-	trigger offsets to the occurrence's time; the results are
-	added as CalAlarmInstance structures
-	to the final list of trigger instances.  Finally,
-	generate_alarms_for_comp() calls
-	generate_absolute_triggers(), which
-	simply adds the instances for absolute alarm triggers; these
-	are the absolute times that are within the time range that was
-	requested originally.  In the very end, the list of instances
-	is sorted to produce nicer results.
-      
-    
-  
-
-
diff --git a/doc/devel/calendar/architecture.sgml b/doc/devel/calendar/architecture.sgml
deleted file mode 100644
index d261f0a7f4..0000000000
--- a/doc/devel/calendar/architecture.sgml
+++ /dev/null
@@ -1,162 +0,0 @@
-  
-    Architecture of the Calendar
-
-    
-      This chapter gives an overview of the &Evolution; Calendar
-      architecture.  It describes the model/view split of the calendar
-      into a personal calendar server, or &PCS;, and the GUI clients
-      that appear inside the &Evolution; Shell.
-    
-
-    
-
-    
-      Model/View Separation
-
-      
-	Like other base components in &Evolution;, the calendar
-	separates the data model from the views or clients.  This is
-	done so that multiple clients can access the same calendar
-	data in an orderly fashion and without clashes.  For example,
-	the user may be running a graphical calendar client.  If he
-	then wants to synchronize his calendar with a handheld device,
-	then the corresponding synchronization program (e.g. a conduit
-	for the gnome-pilot package) will
-	also need to access the calendar storage.  It is important
-	that both the GUI client and the synchronization program keep
-	a consistent view of the calendar at all times, otherwise one
-	of them will be left in an inconsistent state if the
-	calendar's data changes unexpectedly.
-      
-
-      
-	&Evolution; puts the calendar storage in a daemon called the
-	&Wombat; and completely separates it from clients who wants to
-	access calendar data.  This part of the &Wombat; is called the
-	personal calendar server, or &PCS;.  Clients must contact the
-	&PCS; and ask it to open an existing calendar or create a new
-	one.  When a calendar component object (e.g. an appointment or
-	to-do item) changes in the &PCS; it will notify all the
-	clients that are using the component's parent calendar.
-      
-    
-
-    
-
-    
-      Personal Calendar Server
-
-      
-	The personal calendar server, or &PCS;, provides centralized
-	management and storage of a user's personal calendar.
-	Multiple clients can connect to the &PCS; simultaneously to
-	query and modify the user's calendar in a synchronized
-	fashion.  The main features of the &PCS; are as follows:
-      
-
-      
-	Storage
-
-	
-	  The &PCS; is responsible for loading and saving calendars.
-	  Centralizing the loading and saving functionality allows
-	  multiple clients to use the same calendar at the same time
-	  without having to worry about each other.
-	
-      
-
-      
-	Basic Queries
-
-	
-	  The &PCS; provides functions to do basic queries on a
-	  calendar, for example, a client can ask the server for a
-	  list of all the appointments in the calendar, or for all the
-	  data for a specific appointment.
-	
-      
-
-      
-	Recurrence and Alarm Queries
-
-	
-	  Looking for the events that recur or have alarm triggers in
-	  a specific period of time involves scanning all the
-	  appointments in a calendar.  To keep clients from having to
-	  load whole calendars at once, the &PCS; can do these
-	  computations and send the results to clients.
-	
-      
-
-      
-	Modification Log
-
-	
-	  To allow multiple handheld devices to be synchronized
-	  against a calendar, the &PCS; keeps a log of all the
-	  modifications that are done to the calendar.  When an
-	  appointment is updated or removed, the &PCS; logs this
-	  action in the modification log.  Synchronization conduit
-	  programs can then use this information to do their work.
-	
-      
-    
-
-    
-
-    
-      Data Views
-
-      
-	&Evolution; provides a graphical calendar client inside the
-	shell that is just a view onto the data stored in the personal
-	calendar server.  You can launch as many views of a calendar
-	as you like and they will all receive notification from the
-	&PCS; when changes occur.  The views are then responsible for
-	updating their respective displays.
-      
-
-      
-	Even within a single calendar view in the &Evolution; shell
-	there can be multiple clients of a single calendar.  For
-	example, in the day view of the &Evolution; calendar there are
-	three widgets that act as three different clients of the
-	&PCS;:  the multi-day view, the busy days calendar, and the
-	task list.
-      
-    
-
-    
-
-    
-      Non-graphical Clients
-
-      
-	Clients of the personal calendar server can be non-graphical,
-	that is, they do not have to provide views of the data to the
-	user.  Examples of such clients are the synchronization
-	conduit programs for handheld devices.  These usually run with
-	no user interface as a result of being invoked by a daemon
-	that watches the connection to a handheld device.  For
-	example, the calendar synchronization conduit in &Evolution;
-	gets run when the gpilotd daemon
-	from the gnome-pilot package
-	detects that the HotSync button has been pressed on a Palm
-	Pilot device.
-      
-
-      
-	Such clients simply take advantage of the centralized storage
-	in the &PCS; without presenting any graphical display of the
-	data; they just act as middlemen between the &PCS; and other
-	applications.
-      
-    
-  
-
-
diff --git a/doc/devel/calendar/cal-client/.cvsignore b/doc/devel/calendar/cal-client/.cvsignore
deleted file mode 100644
index 0842a93f7a..0000000000
--- a/doc/devel/calendar/cal-client/.cvsignore
+++ /dev/null
@@ -1,3 +0,0 @@
-sgml
-Makefile
-Makefile.in
diff --git a/doc/devel/calendar/cal-client/Makefile.am b/doc/devel/calendar/cal-client/Makefile.am
deleted file mode 100644
index f3a2b39ec6..0000000000
--- a/doc/devel/calendar/cal-client/Makefile.am
+++ /dev/null
@@ -1,131 +0,0 @@
-# The name of the module.
-DOC_MODULE=evolution-cal-client
-
-# The directory containing the source code (if it contains documentation).
-DOC_SOURCE_DIR=$(EVOLUTION_DIR)/calendar/cal-client
-
-CFLAGS ="						\
-	-I$(top_srcdir)/calendar			\
-	-I$(top_srcdir)					\
-	-I$(top_builddir)				\
-	-I$(top_builddir)/libical/src/libical		\
-	-I$(top_srcdir)/libical/src/libical		\
-	$(BONOBO_VFS_GNOME_CFLAGS)			\
-	"
-
-LDFLAGS="								\
-	$(BONOBO_VFS_GNOME_LIBS)					\
-	$(top_builddir)/calendar/cal-client/.libs/libcal-client.a	\
-	$(top_builddir)/calendar/cal-util/.libs/libcal-util.a		\
-	$(top_builddir)/libical/src/libical/.libs/libical.a		\
-	$(top_builddir)/libversit/.libs/libversit.al			\
-	"
-
-DOC_DIR=$(datadir)/gnome/html
-
-DOC_DIR_INSTALL_FILES =				\
-	 evolution-cal-client.args		\
-	 evolution-cal-client.hierarchy		\
-	 evolution-cal-client.signals		\
-	 evolution-cal-client.types		\
-	 evolution-cal-client-decl.txt		\
-	 evolution-cal-client-sections.txt
-
-SOURCE_FILES =							\
-	$(top_srcdir)/calendar/cal-client/cal-client.c		\
-	$(top_srcdir)/calendar/cal-client/cal-client.h		\
-	$(top_srcdir)/calendar/cal-client/cal-client-types.c	\
-	$(top_srcdir)/calendar/cal-client/cal-client-types.h
-
-IGNORED_HEADER_FILES =		\
-	cal-listener.h		\
-	evolution-calendar.h
-
-scan_generated =				\
-	evolution-cal-client-decl.txt		\
-	evolution-cal-client.args		\
-	evolution-cal-client.hierarchy		\
-	evolution-cal-client.signals		\
-	evolution-cal-client.types
-
-tmpl_dependencies =				\
-	evolution-cal-client-decl.txt		\
-	evolution-cal-client-sections.txt	\
-	evolution-cal-client.args		\
-	evolution-cal-client.hierarchy		\
-	evolution-cal-client.signals
-
-tmpl_sources =					\
-	tmpl/cal-client.sgml			\
-	tmpl/evolution-cal-client-unused.sgml
-
-tmpl_generated =				\
-	evolution-cal-client-unused.txt
-
-sgml_dependencies =				\
-	evolution-cal-client-decl.txt		\
-	evolution-cal-client-sections.txt	\
-	evolution-cal-client.args		\
-	evolution-cal-client.hierarchy		\
-	evolution-cal-client.signals		\
-	tmpl/cal-client.sgml
-
-sgml_generated = 				\
-	sgml/cal-client.sgml			\
-	sgml/evolution-cal-client-doc.bottom	\
-	sgml/evolution-cal-client-doc.top	\
-	sgml/object_index.sgml			\
-	sgml/tree_index.sgml
-
-EXTRA_DIST = 					\
-	 evolution-cal-client.args		\
-	 evolution-cal-client.hierarchy		\
-	 evolution-cal-client.signals		\
-	 evolution-cal-client.types		\
-	 evolution-cal-client-decl.txt		\
-	 evolution-cal-client-sections.txt
-
-all: $(sgml_generated)
-
-if ENABLE_GTK_DOC
-scan $(scan_generated): $(SOURCE_FILES)
-	-(cd $(srcdir)									\
-	  && env CFLAGS=$(CFLAGS) LDFLAGS=$(LDFLAGS)					\
-		 gtkdoc-scanobj --module=$(DOC_MODULE)					\
-	  && gtkdoc-scan --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR)		\
-			 --ignore-headers="$(IGNORED_HEADER_FILES)" )
-
-templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies)
-	cd $(srcdir) && gtkdoc-mktmpl --module=$(DOC_MODULE)
-
-sgml $(sgml_generated): $(sgml_dependencies)
-	cd $(srcdir) \
-	&& gtkdoc-mkdb --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR)
-else
-scan $(scan_generated): $(SOURCE_FILES)
-
-templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies)
-
-sgml $(sgml_generated): $(sgml_dependencies)
-endif
-
-clean-local:
-	rm -f *~ *.bak *.signals *-unused.txt
-
-maintainer-clean-local: clean
-	cd $(srcdir) && rm -rf sgml $(DOC_MODULE)-decl-list.txt $(DOC_MODULE)-decl.txt
-
-install-data-local:
-	$(mkinstalldirs) $(DOC_DIR)
-	for i in $(DOC_DIR_INSTALL_FILES); do		\
-		$(INSTALL_DATA) $$i $(DOC_DIR);		\
-	done
-
-dist-hook:
-	mkdir $(distdir)/sgml
-	mkdir $(distdir)/tmpl
-	-cp $(srcdir)/tmpl/*.sgml $(distdir)/tmpl
-	-cp $(srcdir)/sgml/*.sgml $(distdir)/sgml
-	-cp $(srcdir)/sgml/*.bottom $(srcdir)/sgml/*.top $(distdir)/sgml
-
-.PHONY: scan templates sgml
diff --git a/doc/devel/calendar/cal-client/evolution-cal-client-decl.txt b/doc/devel/calendar/cal-client/evolution-cal-client-decl.txt
deleted file mode 100644
index 0bc30e6462..0000000000
--- a/doc/devel/calendar/cal-client/evolution-cal-client-decl.txt
+++ /dev/null
@@ -1,161 +0,0 @@
-
-CAL_CLIENT_TYPE
-#define CAL_CLIENT_TYPE            (cal_client_get_type ())
-
-
-CAL_CLIENT
-#define CAL_CLIENT(obj)            (GTK_CHECK_CAST ((obj), CAL_CLIENT_TYPE, CalClient))
-
-
-CAL_CLIENT_CLASS
-#define CAL_CLIENT_CLASS(klass)    (GTK_CHECK_CLASS_CAST ((klass), CAL_CLIENT_TYPE, CalClientClass))
-
-
-IS_CAL_CLIENT
-#define IS_CAL_CLIENT(obj)         (GTK_CHECK_TYPE ((obj), CAL_CLIENT_TYPE))
-
-
-IS_CAL_CLIENT_CLASS
-#define IS_CAL_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((klass), CAL_CLIENT_TYPE))
-
-
-CalClient
-
-
-CalClientClass
-
-
-CalClientPrivate
-
-
-CalClientOpenStatus
-typedef enum {
-	CAL_CLIENT_OPEN_SUCCESS,
-	CAL_CLIENT_OPEN_ERROR,
-	CAL_CLIENT_OPEN_NOT_FOUND,
-	CAL_CLIENT_OPEN_METHOD_NOT_SUPPORTED
-} CalClientOpenStatus;
-
-
-CalClientGetStatus
-typedef enum {
-	CAL_CLIENT_GET_SUCCESS,
-	CAL_CLIENT_GET_NOT_FOUND,
-	CAL_CLIENT_GET_SYNTAX_ERROR
-} CalClientGetStatus;
-
-
-CalClientLoadState
-typedef enum {
-	CAL_CLIENT_LOAD_NOT_LOADED,
-	CAL_CLIENT_LOAD_LOADING,
-	CAL_CLIENT_LOAD_LOADED
-} CalClientLoadState;
-
-
-CalClient
-struct CalClient {
-	GtkObject object;
-
-	/* Private data */
-	CalClientPrivate *priv;
-};
-
-
-cal_client_get_type
-GtkType  
-void
-
-
-cal_client_construct
-CalClient  *
-CalClient *client
-
-
-cal_client_new
-CalClient  *
-void
-
-
-cal_client_open_calendar
-gboolean  
-CalClient *client, const char *str_uri, gboolean only_if_exists
-
-
-cal_client_get_load_state
-CalClientLoadState  
-CalClient *client
-
-
-cal_client_get_uri
-const char  *
-CalClient *client
-
-
-cal_client_get_n_objects
-int  
-CalClient *client, CalObjType type
-
-
-cal_client_get_object
-CalClientGetStatus  
-CalClient *client,const char *uid,CalComponent **comp
-
-
-cal_client_get_uids
-GList  *
-CalClient *client, CalObjType type
-
-
-cal_client_get_changes
-GList  *
-CalClient *client, CalObjType type, const char *change_id
-
-
-cal_client_get_objects_in_range
-GList  *
-CalClient *client, CalObjType type,time_t start, time_t end
-
-
-cal_client_generate_instances
-void  
-CalClient *client, CalObjType type,time_t start, time_t end,CalRecurInstanceFn cb, gpointer cb_data
-
-
-cal_client_get_alarms_in_range
-GSList  *
-CalClient *client, time_t start, time_t end
-
-
-cal_client_free_alarms
-void  
-GSList *comp_alarms
-
-
-cal_client_get_alarms_for_object
-gboolean  
-CalClient *client, const char *uid,time_t start, time_t end,CalComponentAlarms **alarms
-
-
-cal_client_update_object
-gboolean  
-CalClient *client, CalComponent *comp
-
-
-cal_client_remove_object
-gboolean  
-CalClient *client, const char *uid
-
-
-CalClientChangeType
-typedef enum {
-	CAL_CLIENT_CHANGE_ADDED = 1 << 0,
-	CAL_CLIENT_CHANGE_MODIFIED = 1 << 1,
-	CAL_CLIENT_CHANGE_DELETED = 1 << 2
-} CalClientChangeType;
-
-
-cal_client_change_list_free
-void  
-GList *list
-
diff --git a/doc/devel/calendar/cal-client/evolution-cal-client-sections.txt b/doc/devel/calendar/cal-client/evolution-cal-client-sections.txt
deleted file mode 100644
index 0ce8d9427d..0000000000
--- a/doc/devel/calendar/cal-client/evolution-cal-client-sections.txt
+++ /dev/null
@@ -1,44 +0,0 @@
-cal-client/cal-client.h
-
-

-cal-client
-CAL_CLIENT
-CalClient
-
-CalClientOpenStatus
-CalClientGetStatus
-CalClientLoadState
-
-CalClientChangeType
-
-cal_client_new
-cal_client_open_calendar
-cal_client_get_load_state
-cal_client_get_uri
-cal_client_get_n_objects
-cal_client_get_uids
-cal_client_get_object
-cal_client_get_changes
-cal_client_change_list_free
-cal_client_get_objects_in_range
-cal_client_generate_instances
-cal_client_get_alarms_in_range
-cal_client_free_alarms
-cal_client_get_alarms_for_object
-cal_client_update_object
-cal_client_remove_object
-
-
-
-CAL_CLIENT_TYPE
-IS_CAL_CLIENT
-CAL_CLIENT_CLASS
-IS_CAL_CLIENT_CLASS
-cal_client_get_type
-cal_client_construct
-
-
-CalClient
-CalClientPrivate
-
-

diff --git a/doc/devel/calendar/cal-client/evolution-cal-client.args b/doc/devel/calendar/cal-client/evolution-cal-client.args
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/doc/devel/calendar/cal-client/evolution-cal-client.hierarchy b/doc/devel/calendar/cal-client/evolution-cal-client.hierarchy
deleted file mode 100644
index 88efa3e673..0000000000
--- a/doc/devel/calendar/cal-client/evolution-cal-client.hierarchy
+++ /dev/null
@@ -1,2 +0,0 @@
-GtkObject
-  CalClient
diff --git a/doc/devel/calendar/cal-client/evolution-cal-client.signals b/doc/devel/calendar/cal-client/evolution-cal-client.signals
deleted file mode 100644
index 65d142777a..0000000000
--- a/doc/devel/calendar/cal-client/evolution-cal-client.signals
+++ /dev/null
@@ -1,21 +0,0 @@
-
-CalClient::cal-opened
-void
-CalClient *calclient
-gint  arg1
-
-
-
-CalClient::obj-updated
-void
-CalClient *calclient
-gchar *arg1
-
-
-
-CalClient::obj-removed
-void
-CalClient *calclient
-gchar *arg1
-
-
diff --git a/doc/devel/calendar/cal-client/evolution-cal-client.types b/doc/devel/calendar/cal-client/evolution-cal-client.types
deleted file mode 100644
index 84d65a6637..0000000000
--- a/doc/devel/calendar/cal-client/evolution-cal-client.types
+++ /dev/null
@@ -1,4 +0,0 @@
-#include 
-#include 
-
-cal_client_get_type
diff --git a/doc/devel/calendar/cal-client/tmpl/cal-client.sgml b/doc/devel/calendar/cal-client/tmpl/cal-client.sgml
deleted file mode 100644
index 06195ca454..0000000000
--- a/doc/devel/calendar/cal-client/tmpl/cal-client.sgml
+++ /dev/null
@@ -1,303 +0,0 @@
-
-CalClient
-
-
-GTK+ object for communication with personal calendar server.
-
-
-  
-    The #CalClient object provides a nice GTK+ wrapper for the CORBA
-    interfaces that are used to communicate between calendar clients
-    and the personal calendar server in the user's Wombat daemon.  The
-    CORBA interfaces transfer calendar components in RFC 2445 text
-    format; the #CalClient object automatically converts these into
-    #CalComponent structures that are easier to handle.
-  
-
-  
-    After a #CalClient object is created with cal_client_new(), it
-    should be asked to send a request to the personal calendar server
-    to load or create a calendar based on its URI.  The server will
-    asynchronously notify the client about completion of the request,
-    and will return an appropriate result code; this should be noted
-    by the client with the cal_loaded signal.
-  
-
-  
-    When a client asks the server to update or delete a calendar
-    component from the storage, the server will do so and then notify
-    all the clients about the update or removal.  This is the core of
-    the model/view split between calendar clients and the storage in
-    the personal calendar server.  Clients should watch the obj_updated and obj_removed signals on the
-    CalClient objects they create so that they can be notified about
-    changes in the storage.
-  
-
-
-  
-    #CalComponent
-  
-
-
-  
-    Casts a #GtkObject to a #CalClient.
-  
-
-@obj: A GTK+ object.
-
-
-
-
-
-
-
-@CAL_CLIENT_OPEN_SUCCESS: 
-@CAL_CLIENT_OPEN_ERROR: 
-@CAL_CLIENT_OPEN_NOT_FOUND: 
-@CAL_CLIENT_OPEN_METHOD_NOT_SUPPORTED: 
-
-
-  
-    These values describe the result of the cal_client_get_object()
-    function.
-  
-
-@CAL_CLIENT_GET_SUCCESS: 
-@CAL_CLIENT_GET_NOT_FOUND: 
-@CAL_CLIENT_GET_SYNTAX_ERROR: 
-
-
-
-
-
-
-@CAL_CLIENT_LOAD_NOT_LOADED: 
-@CAL_CLIENT_LOAD_LOADING: 
-@CAL_CLIENT_LOAD_LOADED: 
-
-
-
-
-
-
-@CAL_CLIENT_CHANGE_ADDED: 
-@CAL_CLIENT_CHANGE_MODIFIED: 
-@CAL_CLIENT_CHANGE_DELETED: 
-
-
-
-
-
-
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@str_uri: 
-@only_if_exists: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@type: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@type: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@uid: 
-@comp: 
-@Returns: 
-
-@ico: 
-
-
-
-
-
-
-
-@client: 
-@type: 
-@change_id: 
-@Returns: 
-
-
-
-
-
-
-
-@list: 
-
-
-
-
-
-
-
-@client: 
-@type: 
-@start: 
-@end: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@type: 
-@start: 
-@end: 
-@cb: 
-@cb_data: 
-
-
-
-
-
-
-
-@client: 
-@start: 
-@end: 
-@Returns: 
-
-
-
-
-
-
-
-@comp_alarms: 
-
-
-
-
-
-
-
-@client: 
-@uid: 
-@start: 
-@end: 
-@alarms: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@comp: 
-@Returns: 
-
-@ico: 
-
-
-
-
-
-
-
-@client: 
-@uid: 
-@Returns: 
-
-
-
-
-
-
-
-@calclient: the object which received the signal.
-@arg1: 
-
-
-  
-    This signal is emitted when the calendar clients receives
-    notification of a calendar component's data being changed in the
-    personal calendar server.  Graphical clients may want to get the
-    new version of the object and update their display, for example.
-  
-
-@calclient: the object which received the signal.
-@arg1: 
-
-@client: Calendar client which received the notification.
-@uid: Unique identifier of the calendar component that changed in the
-  personal calendar server's storage.
-
-
-  
-    This signal is emitted when the calendar client receives
-    notification for a calendar component being removed from the
-    storage in the personal calendar server.  Graphical clients may
-    want to delete the corresponding object from their display, for
-    example.
-  
-
-@calclient: the object which received the signal.
-@arg1: 
-
-@client: Calendar client which received the notification.
-@uid: Unique identifier of the calendar component that was removed
-  from the personal calendar server's storage.
-
-
-
diff --git a/doc/devel/calendar/cal-client/tmpl/evolution-cal-client-unused.sgml b/doc/devel/calendar/cal-client/tmpl/evolution-cal-client-unused.sgml
deleted file mode 100644
index 56bcf3aff5..0000000000
--- a/doc/devel/calendar/cal-client/tmpl/evolution-cal-client-unused.sgml
+++ /dev/null
@@ -1,84 +0,0 @@
-
-
-
-
-
-@client: 
-@uid: 
-@pilot_id: 
-@pilot_status: 
-
-
-
-
-
-
-@client: 
-@str_uri: 
-@Returns: 
-
-
-  
-    These values describe the status of a calendar load or create
-    request.  After asking a calendar factory to load or create a
-    calendar, the provided listener will get notification about the
-    result in asynchronous fashion.  Such notification is represented
-    by one of these enumeration values.  For values other than
-    #CAL_CLIENT_LOAD_SUCCESS, the #CalClient object will not accept
-    any other operations on the calendar and it should just be
-    destroyed.
-  
-
-
-
-
-
-
-
-@client: 
-@start: 
-@end: 
-@Returns: 
-
-
-  
-    This signal is emitted some time after the calendar clients sends
-    a load or create request to the personal calendar server.  The
-    server will notify the client asynchronously of the completion of
-    the request.  The @status parameter indicates the status of the
-    request.
-  
-
-@calclient: the object which received the signal.
-@arg1: 
-@client: Calendar client which received the notification.
-@status: Status of the request.  See the description of
-  #CalClientLoadStatus for more details.
-
-
-
-
-
-
-@client: 
-@Returns: 
-
-
-
-
-
-
-@client: 
-@str_uri: 
-@Returns: 
-
-
-
-
-
-
-@client: 
-@pilot_id: 
-@uid: 
-@Returns: 
-
diff --git a/doc/devel/calendar/cal-util/.cvsignore b/doc/devel/calendar/cal-util/.cvsignore
deleted file mode 100644
index 0842a93f7a..0000000000
--- a/doc/devel/calendar/cal-util/.cvsignore
+++ /dev/null
@@ -1,3 +0,0 @@
-sgml
-Makefile
-Makefile.in
diff --git a/doc/devel/calendar/cal-util/Makefile.am b/doc/devel/calendar/cal-util/Makefile.am
deleted file mode 100644
index 7f567652ef..0000000000
--- a/doc/devel/calendar/cal-util/Makefile.am
+++ /dev/null
@@ -1,142 +0,0 @@
-# The name of the module.
-DOC_MODULE=evolution-cal-util
-
-# The directory containing the source code (if it contains documentation).
-DOC_SOURCE_DIR=$(EVOLUTION_DIR)/calendar/cal-util
-
-CFLAGS ="						\
-	-I$(top_srcdir)/calendar			\
-	-I$(top_srcdir)					\
-	-I$(top_builddir)				\
-	-I$(top_builddir)/libical/src/libical		\
-	-I$(top_srcdir)/libical/src/libical		\
-	$(BONOBO_VFS_GNOME_CFLAGS)			\
-	"
-
-LDFLAGS="								\
-	$(BONOBO_VFS_GNOME_LIBS)					\
-	$(top_builddir)/calendar/cal-util/.libs/libcal-util.a		\
-	$(top_builddir)/libical/src/libical/.libs/libical.a		\
-	$(top_builddir)/libversit/.libs/libversit.al			\
-	"
-
-DOC_DIR=$(datadir)/gnome/html
-
-DOC_DIR_INSTALL_FILES =				\
-	 evolution-cal-util.args		\
-	 evolution-cal-util.hierarchy		\
-	 evolution-cal-util.signals		\
-	 evolution-cal-util.types		\
-	 evolution-cal-util-decl.txt		\
-	 evolution-cal-util-sections.txt
-
-SOURCE_FILES =							\
-	$(top_srcdir)/calendar/cal-util/cal-component.c		\
-	$(top_srcdir)/calendar/cal-util/cal-component.h		\
-	$(top_srcdir)/calendar/cal-util/cal-recur.c		\
-	$(top_srcdir)/calendar/cal-util/cal-recur.h		\
-	$(top_srcdir)/calendar/cal-util/cal-util.c		\
-	$(top_srcdir)/calendar/cal-util/cal-util.h		\
-	$(top_srcdir)/calendar/cal-util/timeutil.c		\
-	$(top_srcdir)/calendar/cal-util/timeutil.h
-
-IGNORED_HEADER_FILES =	\
-	calobj.h
-
-scan_generated =				\
-	evolution-cal-util-decl.txt		\
-	evolution-cal-util.args			\
-	evolution-cal-util.hierarchy		\
-	evolution-cal-util.signals		\
-	evolution-cal-util.types
-
-tmpl_dependencies =				\
-	evolution-cal-util-decl.txt		\
-	evolution-cal-util-sections.txt		\
-	evolution-cal-util.args			\
-	evolution-cal-util.hierarchy		\
-	evolution-cal-util.signals
-
-tmpl_sources =					\
-	tmpl/cal-component.sgml			\
-	tmpl/cal-recur.sgml			\
-	tmpl/cal-util.sgml			\
-	tmpl/evolution-cal-util-unused.sgml	\
-	tmpl/timeutil.sgml
-
-tmpl_generated =				\
-	evolution-cal-util-unused.txt
-
-sgml_dependencies =				\
-	evolution-cal-util-decl.txt		\
-	evolution-cal-util-sections.txt		\
-	evolution-cal-util.args			\
-	evolution-cal-util.hierarchy		\
-	evolution-cal-util.signals		\
-	tmpl/cal-component.sgml			\
-	tmpl/cal-recur.sgml			\
-	tmpl/cal-util.sgml			\
-	tmpl/timeutil.sgml
-
-sgml_generated = 				\
-	sgml/cal-component.sgml			\
-	sgml/cal-recur.sgml			\
-	sgml/cal-util.sgml			\
-	sgml/evolution-cal-util-doc.bottom	\
-	sgml/evolution-cal-util-doc.top		\
-	sgml/object_index.sgml			\
-	sgml/timeutil.sgml			\
-	sgml/tree_index.sgml
-
-EXTRA_DIST = 					\
-	 evolution-cal-util.args		\
-	 evolution-cal-util.hierarchy		\
-	 evolution-cal-util.signals		\
-	 evolution-cal-util.types		\
-	 evolution-cal-util-decl.txt		\
-	 evolution-cal-util-sections.txt
-
-all: $(sgml_generated)
-
-if ENABLE_GTK_DOC
-scan $(scan_generated): $(SOURCE_FILES)
-	-(cd $(srcdir)									\
-	  && env CFLAGS=$(CFLAGS) LDFLAGS=$(LDFLAGS)					\
-		 gtkdoc-scanobj --module=$(DOC_MODULE)					\
-	  && gtkdoc-scan --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR)		\
-			 --ignore-headers="$(IGNORED_HEADER_FILES)" )
-
-templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies)
-	cd $(srcdir) && gtkdoc-mktmpl --module=$(DOC_MODULE)
-
-sgml $(sgml_generated): $(sgml_dependencies)
-	cd $(srcdir) \
-	&& gtkdoc-mkdb --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR)
-else
-scan $(scan_generated): $(SOURCE_FILES)
-
-templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies)
-
-sgml $(sgml_generated): $(sgml_dependencies)
-endif
-
-clean-local:
-	rm -f *~ *.bak *.signals *-unused.txt
-
-maintainer-clean-local: clean
-	cd $(srcdir) && rm -rf sgml $(DOC_MODULE)-decl-list.txt $(DOC_MODULE)-decl.txt
-
-install-data-local:
-	$(mkinstalldirs) $(DOC_DIR)
-	for i in $(DOC_DIR_INSTALL_FILES); do		\
-		$(INSTALL_DATA) $$i $(DOC_DIR);		\
-	done
-
-dist-hook:
-	mkdir $(distdir)/sgml
-	mkdir $(distdir)/tmpl
-	-cp $(srcdir)/tmpl/*.sgml $(distdir)/tmpl
-	-cp $(srcdir)/sgml/*.sgml $(distdir)/sgml
-	-cp $(srcdir)/sgml/*.bottom $(srcdir)/sgml/*.top $(distdir)/sgml
-
-.PHONY: scan templates sgml
diff --git a/doc/devel/calendar/cal-util/evolution-cal-util-decl.txt b/doc/devel/calendar/cal-util/evolution-cal-util-decl.txt
deleted file mode 100644
index b524235de2..0000000000
--- a/doc/devel/calendar/cal-util/evolution-cal-util-decl.txt
+++ /dev/null
@@ -1,780 +0,0 @@
-
-CAL_COMPONENT_TYPE
-#define CAL_COMPONENT_TYPE            (cal_component_get_type ())
-
-
-CAL_COMPONENT
-#define CAL_COMPONENT(obj)            (GTK_CHECK_CAST ((obj), CAL_COMPONENT_TYPE, CalComponent))
-
-
-CAL_COMPONENT_CLASS
-#define CAL_COMPONENT_CLASS(klass)    (GTK_CHECK_CLASS_CAST ((klass), CAL_COMPONENT_TYPE,	\
-				       CalComponentClass))
-
-
-IS_CAL_COMPONENT
-#define IS_CAL_COMPONENT(obj)         (GTK_CHECK_TYPE ((obj), CAL_COMPONENT_TYPE))
-
-
-IS_CAL_COMPONENT_CLASS
-#define IS_CAL_COMPONENT_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((klass), CAL_COMPONENT_TYPE))
-
-
-CalComponentVType
-typedef enum {
-	CAL_COMPONENT_NO_TYPE,
-	CAL_COMPONENT_EVENT,
-	CAL_COMPONENT_TODO,
-	CAL_COMPONENT_JOURNAL,
-	CAL_COMPONENT_FREEBUSY,
-	CAL_COMPONENT_TIMEZONE
-} CalComponentVType;
-
-
-CalComponentField
-typedef enum {
-	CAL_COMPONENT_FIELD_CATEGORIES,		/* concatenation of the categories list */
-	CAL_COMPONENT_FIELD_CLASSIFICATION,
-	CAL_COMPONENT_FIELD_COMPLETED,
-	CAL_COMPONENT_FIELD_DTEND,
-	CAL_COMPONENT_FIELD_DTSTART,
-	CAL_COMPONENT_FIELD_DUE,
-	CAL_COMPONENT_FIELD_GEO,
-	CAL_COMPONENT_FIELD_PERCENT,
-	CAL_COMPONENT_FIELD_PRIORITY,
-	CAL_COMPONENT_FIELD_SUMMARY,
-	CAL_COMPONENT_FIELD_TRANSPARENCY,
-	CAL_COMPONENT_FIELD_URL,
-	CAL_COMPONENT_FIELD_HAS_ALARMS,		/* not a real field */
-	CAL_COMPONENT_FIELD_ICON,		/* not a real field */
-	CAL_COMPONENT_FIELD_COMPLETE,		/* not a real field */
-	CAL_COMPONENT_FIELD_RECURRING,		/* not a real field */
-	CAL_COMPONENT_FIELD_OVERDUE,		/* not a real field */
-	CAL_COMPONENT_FIELD_COLOR,		/* not a real field */
-	CAL_COMPONENT_FIELD_NUM_FIELDS
-} CalComponentField;
-
-
-CalComponentClassification
-typedef enum {
-	CAL_COMPONENT_CLASS_NONE,
-	CAL_COMPONENT_CLASS_PUBLIC,
-	CAL_COMPONENT_CLASS_PRIVATE,
-	CAL_COMPONENT_CLASS_CONFIDENTIAL,
-	CAL_COMPONENT_CLASS_UNKNOWN
-} CalComponentClassification;
-
-
-CalComponentDateTime
-typedef struct {
-	/* Actual date/time value */
-	struct icaltimetype *value;
-
-	/* Timezone ID */
-	const char *tzid;
-} CalComponentDateTime;
-
-
-CalComponentPeriodType
-typedef enum {
-	CAL_COMPONENT_PERIOD_DATETIME,
-	CAL_COMPONENT_PERIOD_DURATION
-} CalComponentPeriodType;
-
-
-CalComponentPeriod
-typedef struct {
-	CalComponentPeriodType type;
-
-	struct icaltimetype start;
-
-	union {
-		struct icaltimetype end;
-		struct icaldurationtype duration;
-	} u;
-} CalComponentPeriod;
-
-
-CalComponentText
-typedef struct {
-	/* Description string */
-	const char *value;
-
-	/* Alternate representation URI */
-	const char *altrep;
-} CalComponentText;
-
-
-CalComponentTransparency
-typedef enum {
-	CAL_COMPONENT_TRANSP_NONE,
-	CAL_COMPONENT_TRANSP_TRANSPARENT,
-	CAL_COMPONENT_TRANSP_OPAQUE,
-	CAL_COMPONENT_TRANSP_UNKNOWN
-} CalComponentTransparency;
-
-
-CalComponent
-
-
-CalComponentClass
-
-
-CalComponentPrivate
-
-
-CalComponent
-struct CalComponent {
-	GtkObject object;
-
-	/* Private data */
-	CalComponentPrivate *priv;
-};
-
-
-cal_component_get_type
-GtkType  
-void
-
-
-cal_component_gen_uid
-char  *
-void
-
-
-cal_component_new
-CalComponent  *
-void
-
-
-cal_component_clone
-CalComponent  *
-CalComponent *comp
-
-
-cal_component_set_new_vtype
-void  
-CalComponent *comp, CalComponentVType type
-
-
-cal_component_set_icalcomponent
-gboolean  
-CalComponent *comp, icalcomponent *icalcomp
-
-
-cal_component_get_icalcomponent
-icalcomponent  *
-CalComponent *comp
-
-
-cal_component_get_vtype
-CalComponentVType  
-CalComponent *comp
-
-
-cal_component_get_as_string
-char  *
-CalComponent *comp
-
-
-cal_component_commit_sequence
-void  
-CalComponent *comp
-
-
-cal_component_get_uid
-void  
-CalComponent *comp, const char **uid
-
-
-cal_component_set_uid
-void  
-CalComponent *comp, const char *uid
-
-
-cal_component_get_categories
-void  
-CalComponent *comp, const char **categories
-
-
-cal_component_set_categories
-void  
-CalComponent *comp, const char *categories
-
-
-cal_component_get_categories_list
-void  
-CalComponent *comp, GSList **categ_list
-
-
-cal_component_set_categories_list
-void  
-CalComponent *comp, GSList *categ_list
-
-
-cal_component_get_classification
-void  
-CalComponent *comp, CalComponentClassification *classif
-
-
-cal_component_set_classification
-void  
-CalComponent *comp, CalComponentClassification classif
-
-
-cal_component_get_comment_list
-void  
-CalComponent *comp, GSList **text_list
-
-
-cal_component_set_comment_list
-void  
-CalComponent *comp, GSList *text_list
-
-
-cal_component_get_completed
-void  
-CalComponent *comp, struct icaltimetype **t
-
-
-cal_component_set_completed
-void  
-CalComponent *comp, struct icaltimetype *t
-
-
-cal_component_get_created
-void  
-CalComponent *comp, struct icaltimetype **t
-
-
-cal_component_set_created
-void  
-CalComponent *comp, struct icaltimetype *t
-
-
-cal_component_get_description_list
-void  
-CalComponent *comp, GSList **text_list
-
-
-cal_component_set_description_list
-void  
-CalComponent *comp, GSList *text_list
-
-
-cal_component_get_dtend
-void  
-CalComponent *comp, CalComponentDateTime *dt
-
-
-cal_component_set_dtend
-void  
-CalComponent *comp, CalComponentDateTime *dt
-
-
-cal_component_get_dtstamp
-void  
-CalComponent *comp, struct icaltimetype *t
-
-
-cal_component_set_dtstamp
-void  
-CalComponent *comp, struct icaltimetype *t
-
-
-cal_component_get_dtstart
-void  
-CalComponent *comp, CalComponentDateTime *dt
-
-
-cal_component_set_dtstart
-void  
-CalComponent *comp, CalComponentDateTime *dt
-
-
-cal_component_get_due
-void  
-CalComponent *comp, CalComponentDateTime *dt
-
-
-cal_component_set_due
-void  
-CalComponent *comp, CalComponentDateTime *dt
-
-
-cal_component_get_exdate_list
-void  
-CalComponent *comp, GSList **exdate_list
-
-
-cal_component_set_exdate_list
-void  
-CalComponent *comp, GSList *exdate_list
-
-
-cal_component_has_exdates
-gboolean  
-CalComponent *comp
-
-
-cal_component_get_exrule_list
-void  
-CalComponent *comp, GSList **recur_list
-
-
-cal_component_get_exrule_property_list
-void  
-CalComponent *comp, GSList **recur_list
-
-
-cal_component_set_exrule_list
-void  
-CalComponent *comp, GSList *recur_list
-
-
-cal_component_has_exrules
-gboolean  
-CalComponent *comp
-
-
-cal_component_has_exceptions
-gboolean  
-CalComponent *comp
-
-
-cal_component_get_geo
-void  
-CalComponent *comp, struct icalgeotype **geo
-
-
-cal_component_set_geo
-void  
-CalComponent *comp, struct icalgeotype *geo
-
-
-cal_component_get_last_modified
-void  
-CalComponent *comp, struct icaltimetype **t
-
-
-cal_component_set_last_modified
-void  
-CalComponent *comp, struct icaltimetype *t
-
-
-cal_component_get_percent
-void  
-CalComponent *comp, int **percent
-
-
-cal_component_set_percent
-void  
-CalComponent *comp, int *percent
-
-
-cal_component_get_priority
-void  
-CalComponent *comp, int **priority
-
-
-cal_component_set_priority
-void  
-CalComponent *comp, int *priority
-
-
-cal_component_get_rdate_list
-void  
-CalComponent *comp, GSList **period_list
-
-
-cal_component_set_rdate_list
-void  
-CalComponent *comp, GSList *period_list
-
-
-cal_component_has_rdates
-gboolean  
-CalComponent *comp
-
-
-cal_component_get_rrule_list
-void  
-CalComponent *comp, GSList **recur_list
-
-
-cal_component_get_rrule_property_list
-void  
-CalComponent *comp, GSList **recur_list
-
-
-cal_component_set_rrule_list
-void  
-CalComponent *comp, GSList *recur_list
-
-
-cal_component_has_rrules
-gboolean  
-CalComponent *comp
-
-
-cal_component_has_recurrences
-gboolean  
-CalComponent *comp
-
-
-cal_component_get_sequence
-void  
-CalComponent *comp, int **sequence
-
-
-cal_component_set_sequence
-void  
-CalComponent *comp, int *sequence
-
-
-cal_component_get_status
-void  
-CalComponent *comp, icalproperty_status *status
-
-
-cal_component_set_status
-void  
-CalComponent *comp, icalproperty_status status
-
-
-cal_component_get_summary
-void  
-CalComponent *comp, CalComponentText *summary
-
-
-cal_component_set_summary
-void  
-CalComponent *comp, CalComponentText *summary
-
-
-cal_component_get_transparency
-void  
-CalComponent *comp, CalComponentTransparency *transp
-
-
-cal_component_set_transparency
-void  
-CalComponent *comp, CalComponentTransparency transp
-
-
-cal_component_get_url
-void  
-CalComponent *comp, const char **url
-
-
-cal_component_set_url
-void  
-CalComponent *comp, const char *url
-
-
-cal_component_event_dates_match
-gboolean  
-CalComponent *comp1, CalComponent *comp2
-
-
-cal_component_free_categories_list
-void  
-GSList *categ_list
-
-
-cal_component_free_datetime
-void  
-CalComponentDateTime *dt
-
-
-cal_component_free_exdate_list
-void  
-GSList *exdate_list
-
-
-cal_component_free_geo
-void  
-struct icalgeotype *geo
-
-
-cal_component_free_icaltimetype
-void  
-struct icaltimetype *t
-
-
-cal_component_free_percent
-void  
-int *percent
-
-
-cal_component_free_priority
-void  
-int *priority
-
-
-cal_component_free_period_list
-void  
-GSList *period_list
-
-
-cal_component_free_recur_list
-void  
-GSList *recur_list
-
-
-cal_component_free_sequence
-void  
-int *sequence
-
-
-cal_component_free_text_list
-void  
-GSList *text_list
-
-
-CalComponentAlarm
-
-
-CalAlarmInstance
-typedef struct {
-	/* UID of the alarm that triggered */
-	const char *auid;
-
-	/* Trigger time, i.e. "5 minutes before the appointment" */
-	time_t trigger;
-
-	/* Actual event occurrence to which this trigger corresponds */
-	time_t occur;
-} CalAlarmInstance;
-
-
-CalComponentAlarms
-typedef struct {
-	/* The actual component */
-	CalComponent *comp;
-
-	/* List of CalAlarmInstance structures */
-	GSList *alarms;
-} CalComponentAlarms;
-
-
-CalAlarmAction
-typedef enum {
-	CAL_ALARM_NONE,
-	CAL_ALARM_AUDIO,
-	CAL_ALARM_DISPLAY,
-	CAL_ALARM_EMAIL,
-	CAL_ALARM_PROCEDURE,
-	CAL_ALARM_UNKNOWN
-} CalAlarmAction;
-
-
-CalAlarmTriggerType
-typedef enum {
-	CAL_ALARM_TRIGGER_NONE,
-	CAL_ALARM_TRIGGER_RELATIVE_START,
-	CAL_ALARM_TRIGGER_RELATIVE_END,
-	CAL_ALARM_TRIGGER_ABSOLUTE
-} CalAlarmTriggerType;
-
-
-CalAlarmTrigger
-typedef struct {
-	CalAlarmTriggerType type;
-
-	union {
-		struct icaldurationtype rel_duration;
-		struct icaltimetype abs_time;
-	} u;
-} CalAlarmTrigger;
-
-
-cal_component_has_alarms
-gboolean  
-CalComponent *comp
-
-
-cal_component_add_alarm
-void  
-CalComponent *comp, CalComponentAlarm *alarm
-
-
-cal_component_remove_alarm
-void  
-CalComponent *comp, const char *auid
-
-
-cal_component_get_alarm_uids
-GList  *
-CalComponent *comp
-
-
-cal_component_get_alarm
-CalComponentAlarm  *
-CalComponent *comp, const char *auid
-
-
-cal_component_alarms_free
-void  
-CalComponentAlarms *alarms
-
-
-cal_component_alarm_new
-CalComponentAlarm  *
-void
-
-
-cal_component_alarm_get_uid
-const char  *
-CalComponentAlarm *alarm
-
-
-cal_component_alarm_get_action
-void  
-CalComponentAlarm *alarm, CalAlarmAction *action
-
-
-cal_component_alarm_set_action
-void  
-CalComponentAlarm *alarm, CalAlarmAction action
-
-
-cal_component_alarm_get_trigger
-void  
-CalComponentAlarm *alarm, CalAlarmTrigger *trigger
-
-
-cal_component_alarm_set_trigger
-void  
-CalComponentAlarm *alarm, CalAlarmTrigger trigger
-
-
-cal_component_alarm_free
-void  
-CalComponentAlarm *alarm
-
-
-CalRecurInstanceFn
-gboolean 
-CalComponent *comp,
-					 time_t        instance_start,
-					 time_t        instance_end,
-					 gpointer      data
-
-
-cal_recur_generate_instances
-void 	
-CalComponent		*comp,time_t			 start,time_t			 end,CalRecurInstanceFn	 cb,gpointer                cb_data
-
-
-CalObjInstance
-typedef struct {
-	char *uid;			/* UID of the object */
-	time_t start;			/* Start time of instance */
-	time_t end;			/* End time of instance */
-} CalObjInstance;
-
-
-cal_obj_instance_list_free
-void  
-GList *list
-
-
-CalObjType
-typedef enum {
-	CALOBJ_TYPE_EVENT   = 1 << 0,
-	CALOBJ_TYPE_TODO    = 1 << 1,
-	CALOBJ_TYPE_JOURNAL = 1 << 2,
-	CALOBJ_TYPE_ANY     = 0x07
-} CalObjType;
-
-
-cal_obj_uid_list_free
-void  
-GList *list
-
-
-isodate_from_time_t
-char    *
-time_t t
-
-
-time_add_minutes
-time_t  
-time_t time, int minutes
-
-
-time_add_day
-time_t  
-time_t time, int days
-
-
-time_add_week
-time_t  
-time_t time, int weeks
-
-
-time_add_month
-time_t  
-time_t time, int months
-
-
-time_add_year
-time_t  
-time_t time, int years
-
-
-time_days_in_month
-int  
-int year, int month
-
-
-time_from_day
-time_t  
-int year, int month, int day
-
-
-time_year_begin
-time_t  
-time_t t
-
-
-time_year_end
-time_t  
-time_t t
-
-
-time_month_begin
-time_t  
-time_t t
-
-
-time_month_end
-time_t  
-time_t t
-
-
-time_week_begin
-time_t  
-time_t t
-
-
-time_week_end
-time_t  
-time_t t
-
-
-time_day_begin
-time_t  
-time_t t
-
-
-time_day_end
-time_t  
-time_t t
-
-
-print_time_t
-void  
-time_t t
-
diff --git a/doc/devel/calendar/cal-util/evolution-cal-util-sections.txt b/doc/devel/calendar/cal-util/evolution-cal-util-sections.txt
deleted file mode 100644
index 1a03226591..0000000000
--- a/doc/devel/calendar/cal-util/evolution-cal-util-sections.txt
+++ /dev/null
@@ -1,161 +0,0 @@
-

-cal-component
-CAL_COMPONENT
-CalComponent
-
-CalComponentVType
-CalComponentField
-CalComponentClassification
-CalComponentDateTime
-CalComponentPeriodType
-CalComponentPeriod
-CalComponentText
-CalComponentTransparency
-
-cal_component_gen_uid
-cal_component_new
-cal_component_clone
-cal_component_set_new_vtype
-cal_component_set_icalcomponent
-cal_component_get_icalcomponent
-cal_component_get_vtype
-cal_component_get_as_string
-cal_component_commit_sequence
-cal_component_get_uid
-cal_component_set_uid
-cal_component_get_categories
-cal_component_set_categories
-cal_component_get_categories_list
-cal_component_set_categories_list
-cal_component_get_classification
-cal_component_set_classification
-cal_component_get_comment_list
-cal_component_set_comment_list
-cal_component_get_completed
-cal_component_set_completed
-cal_component_get_created
-cal_component_set_created
-cal_component_get_description_list
-cal_component_set_description_list
-cal_component_get_dtend
-cal_component_set_dtend
-cal_component_get_dtstamp
-cal_component_set_dtstamp
-cal_component_get_dtstart
-cal_component_set_dtstart
-cal_component_get_due
-cal_component_set_due
-cal_component_get_exdate_list
-cal_component_set_exdate_list
-cal_component_has_exdates
-cal_component_get_exrule_list
-cal_component_get_exrule_property_list
-cal_component_set_exrule_list
-cal_component_has_exrules
-cal_component_has_exceptions
-cal_component_get_geo
-cal_component_set_geo
-cal_component_get_last_modified
-cal_component_set_last_modified
-cal_component_get_percent
-cal_component_set_percent
-cal_component_get_priority
-cal_component_set_priority
-cal_component_get_rdate_list
-cal_component_set_rdate_list
-cal_component_has_rdates
-cal_component_get_rrule_list
-cal_component_get_rrule_property_list
-cal_component_set_rrule_list
-cal_component_has_rrules
-cal_component_has_recurrences
-cal_component_get_sequence
-cal_component_set_sequence
-cal_component_get_status
-cal_component_set_status
-cal_component_get_summary
-cal_component_set_summary
-cal_component_get_transparency
-cal_component_set_transparency
-cal_component_get_url
-cal_component_set_url
-
-
-cal_component_free_categories_list
-cal_component_free_datetime
-cal_component_free_exdate_list
-cal_component_free_geo
-cal_component_free_icaltimetype
-cal_component_free_percent
-cal_component_free_priority
-cal_component_free_period_list
-cal_component_free_recur_list
-cal_component_free_sequence
-cal_component_free_text_list
-
-
-CalComponentAlarm
-CalAlarmInstance
-CalComponentAlarms
-CalAlarmAction
-CalAlarmTriggerType
-CalAlarmTrigger
-
-cal_component_has_alarms
-cal_component_get_alarm_uids
-cal_component_get_alarm
-cal_component_alarm_free
-cal_component_alarms_free
-cal_component_alarm_get_uid
-cal_component_alarm_get_action
-cal_component_alarm_set_action
-cal_component_alarm_get_trigger
-cal_component_alarm_set_trigger
-
-
-CAL_COMPONENT_TYPE
-CAL_COMPONENT_CLASS
-IS_CAL_COMPONENT
-IS_CAL_COMPONENT_CLASS
-cal_component_get_type
-
-
-CalComponent
-CalComponentPrivate
-
-

-
-

-cal-recur
-CalRecurInstanceFn
-cal_recur_generate_instances
-

-
-

-cal-util
-CalObjInstance
-cal_obj_instance_list_free
-CalObjType
-cal_obj_uid_list_free
-

-
-

-timeutil
-isodate_from_time_t
-time_add_minutes
-time_add_day
-time_add_week
-time_add_month
-time_add_year
-time_days_in_month
-time_from_day
-time_year_begin
-time_year_end
-time_month_begin
-time_month_end
-time_week_begin
-time_week_end
-time_day_begin
-time_day_end
-print_time_t
-

diff --git a/doc/devel/calendar/cal-util/evolution-cal-util.args b/doc/devel/calendar/cal-util/evolution-cal-util.args
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/doc/devel/calendar/cal-util/evolution-cal-util.hierarchy b/doc/devel/calendar/cal-util/evolution-cal-util.hierarchy
deleted file mode 100644
index cc235653f2..0000000000
--- a/doc/devel/calendar/cal-util/evolution-cal-util.hierarchy
+++ /dev/null
@@ -1,2 +0,0 @@
-GtkObject
-  CalComponent
diff --git a/doc/devel/calendar/cal-util/evolution-cal-util.signals b/doc/devel/calendar/cal-util/evolution-cal-util.signals
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/doc/devel/calendar/cal-util/evolution-cal-util.types b/doc/devel/calendar/cal-util/evolution-cal-util.types
deleted file mode 100644
index 52b2d9bf90..0000000000
--- a/doc/devel/calendar/cal-util/evolution-cal-util.types
+++ /dev/null
@@ -1,4 +0,0 @@
-#include 
-#include 
-
-cal_component_get_type
diff --git a/doc/devel/calendar/cal-util/tmpl/cal-component.sgml b/doc/devel/calendar/cal-util/tmpl/cal-component.sgml
deleted file mode 100644
index 0cf6089d60..0000000000
--- a/doc/devel/calendar/cal-util/tmpl/cal-component.sgml
+++ /dev/null
@@ -1,991 +0,0 @@
-
-CalComponent
-
-
-RFC 2445 iCalendar component object.
-
-
-  
-    The #CalComponent object provides a wrapper over the &libical;
-    functions for manipulating calendar components.  #CalComponent
-    presents a GTK+-like interface to calendar components according to
-    RFC 2445.
-  
-
-  
-    While &libical; supports almost all of the features of the
-    iCalendar RFCs, applications are normally not interested in all
-    the mindless gunk that is there.  Still, applications should do
-    their best not to drop extension fields from calendar components
-    or any other extra information they do not support (including
-    standard fields they are not interested in).  The #CalComponent
-    object provides a wrapper over
-    icalcomponent structures from &libical;
-    so that no information in them will be lost even if the
-    application is not designed to handle it.  Also, #CalComponent
-    provides a higher-level API to many of the &libical; operations so
-    as to make it less painful to deal with iCalendar components.
-  
-
-  
-    A #CalComponent object starts out empty.  It must be initialized
-    from an existing icalcomponent structure
-    by using the cal_component_set_icalcomponent() function, or from a
-    completely new data by specifying the desired component type to
-    the cal_component_set_new_vtype() function.
-  
-
-  
-    #CalComponent will create an internal map of the properties in the
-    icalcomponent structure and then allow
-    random access to them via the #CalComponent API functions;
-    normally the &libical; API would have to be used by creating many
-    iterators and other unpleasant constructs.  #CalComponent keeps
-    handles to the properties it scanned from the
-    icalcomponent and will let the parent
-    application modify them at any time without having to do any
-    iteration.
-  
-
-  
-    Eventually a #CalComponent may be turned into the RFC 2445 string
-    representation of an iCalendar component by using the
-    cal_component_get_as_string() function.  Applications can then
-    transfer this interoperable
-    
-      
-	“Interoperable.”  Heavens, I love that word.
-      
-    
-    string to other programs that deal with iCalendar.
-  
-
-
-  
-
-  
-
-
-  
-    Casts a #GtkObject to a #CalComponent.
-  
-
-@obj: A GTK+ object.
-
-
-
-  
-    Calendar component types as defined by RFC 2445.  These values can
-    be used to create a new calendar component by passing them to the
-    cal_component_set_new_vtype() function.  They are also the return
-    value of the cal_component_get_vtype() function.  The only time
-    the @CAL_COMPONENT_NO_TYPE value is used is when querying the
-    vtype of an uninitialized #CalComponent.
-  
-
-@CAL_COMPONENT_NO_TYPE: 
-@CAL_COMPONENT_EVENT: 
-@CAL_COMPONENT_TODO: 
-@CAL_COMPONENT_JOURNAL: 
-@CAL_COMPONENT_FREEBUSY: 
-@CAL_COMPONENT_TIMEZONE: 
-
-
-  
-    These values are used as identifiers for #ETable columns.  These
-    are used by the calendar GUI code in &Evolution;.
-  
-
-@CAL_COMPONENT_FIELD_CATEGORIES: 
-@CAL_COMPONENT_FIELD_CLASSIFICATION: 
-@CAL_COMPONENT_FIELD_COMPLETED: 
-@CAL_COMPONENT_FIELD_DTEND: 
-@CAL_COMPONENT_FIELD_DTSTART: 
-@CAL_COMPONENT_FIELD_DUE: 
-@CAL_COMPONENT_FIELD_GEO: 
-@CAL_COMPONENT_FIELD_PERCENT: 
-@CAL_COMPONENT_FIELD_PRIORITY: 
-@CAL_COMPONENT_FIELD_SUMMARY: 
-@CAL_COMPONENT_FIELD_TRANSPARENCY: 
-@CAL_COMPONENT_FIELD_URL: 
-@CAL_COMPONENT_FIELD_HAS_ALARMS: 
-@CAL_COMPONENT_FIELD_ICON: 
-@CAL_COMPONENT_FIELD_COMPLETE: 
-@CAL_COMPONENT_FIELD_RECURRING: 
-@CAL_COMPONENT_FIELD_OVERDUE: 
-@CAL_COMPONENT_FIELD_COLOR: 
-@CAL_COMPONENT_FIELD_NUM_FIELDS: 
-
-
-  
-    Values for the access classification property of a calendar
-    component.
-  
-
-@CAL_COMPONENT_CLASS_NONE: 
-@CAL_COMPONENT_CLASS_PUBLIC: 
-@CAL_COMPONENT_CLASS_PRIVATE: 
-@CAL_COMPONENT_CLASS_CONFIDENTIAL: 
-@CAL_COMPONENT_CLASS_UNKNOWN: 
-
-
-  
-    This structure defines a date and time value.
-  
-
-
-
-  
-    Defines how a period of time is specified.
-  
-
-@CAL_COMPONENT_PERIOD_DATETIME: 
-@CAL_COMPONENT_PERIOD_DURATION: 
-
-
-  
-    This structure defines a period of time.
-  
-
-
-
-  
-    This structure defines the value of a text property that may have
-    an alternate representation parameter.
-  
-
-
-
-
-
-
-
-@CAL_COMPONENT_TRANSP_NONE: 
-@CAL_COMPONENT_TRANSP_TRANSPARENT: 
-@CAL_COMPONENT_TRANSP_OPAQUE: 
-@CAL_COMPONENT_TRANSP_UNKNOWN: 
-
-
-
-
-
-
-@Returns: 
-
-
-
-
-
-
-
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@type: 
-
-
-
-
-
-
-
-@comp: 
-@icalcomp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-
-
-
-
-
-
-
-@comp: 
-@uid: 
-
-
-
-
-
-
-
-@comp: 
-@uid: 
-
-
-
-
-
-
-
-@comp: 
-@categories: 
-
-
-
-
-
-
-
-@comp: 
-@categories: 
-
-
-
-
-
-
-
-@comp: 
-@categ_list: 
-
-
-
-
-
-
-
-@comp: 
-@categ_list: 
-
-
-
-
-
-
-
-@comp: 
-@classif: 
-
-
-
-
-
-
-
-@comp: 
-@classif: 
-
-
-
-
-
-
-
-@comp: 
-@text_list: 
-
-
-
-
-
-
-
-@comp: 
-@text_list: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@text_list: 
-
-
-
-
-
-
-
-@comp: 
-@text_list: 
-
-
-
-
-
-
-
-@comp: 
-@dt: 
-
-
-
-
-
-
-
-@comp: 
-@dt: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@dt: 
-
-
-
-
-
-
-
-@comp: 
-@dt: 
-
-
-
-
-
-
-
-@comp: 
-@dt: 
-
-
-
-
-
-
-
-@comp: 
-@dt: 
-
-
-
-
-
-
-
-@comp: 
-@exdate_list: 
-
-
-
-
-
-
-
-@comp: 
-@exdate_list: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@recur_list: 
-
-
-
-
-
-
-
-@comp: 
-@recur_list: 
-
-
-
-
-
-
-
-@comp: 
-@recur_list: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@geo: 
-
-
-
-
-
-
-
-@comp: 
-@geo: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@percent: 
-
-
-
-
-
-
-
-@comp: 
-@percent: 
-
-
-
-
-
-
-
-@comp: 
-@priority: 
-
-
-
-
-
-
-
-@comp: 
-@priority: 
-
-
-
-
-
-
-
-@comp: 
-@period_list: 
-
-
-
-
-
-
-
-@comp: 
-@period_list: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@recur_list: 
-
-
-
-
-
-
-
-@comp: 
-@recur_list: 
-
-
-
-
-
-
-
-@comp: 
-@recur_list: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@sequence: 
-
-
-
-
-
-
-
-@comp: 
-@sequence: 
-
-
-
-
-
-
-
-@comp: 
-@status: 
-
-
-
-
-
-
-
-@comp: 
-@status: 
-
-
-
-
-
-
-
-@comp: 
-@summary: 
-
-
-
-
-
-
-
-@comp: 
-@summary: 
-
-
-
-
-
-
-
-@comp: 
-@transp: 
-
-
-
-
-
-
-
-@comp: 
-@transp: 
-
-
-
-
-
-
-
-@comp: 
-@url: 
-
-
-
-
-
-
-
-@comp: 
-@url: 
-
-
-
-
-
-
-
-@categ_list: 
-
-
-
-
-
-
-
-@dt: 
-
-
-
-
-
-
-
-@exdate_list: 
-
-
-
-
-
-
-
-@geo: 
-
-
-
-
-
-
-
-@t: 
-
-
-
-
-
-
-
-@percent: 
-
-
-
-
-
-
-
-@priority: 
-
-
-
-
-
-
-
-@period_list: 
-
-
-
-
-
-
-
-@recur_list: 
-
-
-
-
-
-
-
-@sequence: 
-
-
-
-
-
-
-
-@text_list: 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-@CAL_ALARM_NONE: 
-@CAL_ALARM_AUDIO: 
-@CAL_ALARM_DISPLAY: 
-@CAL_ALARM_EMAIL: 
-@CAL_ALARM_PROCEDURE: 
-@CAL_ALARM_UNKNOWN: 
-
-
-
-
-
-
-@CAL_ALARM_TRIGGER_NONE: 
-@CAL_ALARM_TRIGGER_RELATIVE_START: 
-@CAL_ALARM_TRIGGER_RELATIVE_END: 
-@CAL_ALARM_TRIGGER_ABSOLUTE: 
-
-
-
-
-
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@auid: 
-@Returns: 
-
-
-
-
-
-
-
-@alarm: 
-
-
-
-
-
-
-
-@alarms: 
-
-
-
-
-
-
-
-@alarm: 
-@Returns: 
-
-
-
-
-
-
-
-@alarm: 
-@action: 
-
-
-
-
-
-
-
-@alarm: 
-@action: 
-
-
-
-
-
-
-
-@alarm: 
-@trigger: 
-
-
-
-
-
-
-
-@alarm: 
-@trigger: 
-
-
diff --git a/doc/devel/calendar/cal-util/tmpl/cal-recur.sgml b/doc/devel/calendar/cal-util/tmpl/cal-recur.sgml
deleted file mode 100644
index 092b547809..0000000000
--- a/doc/devel/calendar/cal-util/tmpl/cal-recur.sgml
+++ /dev/null
@@ -1,42 +0,0 @@
-
-cal-recur
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-@comp: 
-@instance_start: 
-@instance_end: 
-@data: 
-@Returns: 
-
-@instace_end: 
-
-
-
-
-
-
-
-@comp: 
-@start: 
-@end: 
-@cb: 
-@cb_data: 
-
-
diff --git a/doc/devel/calendar/cal-util/tmpl/cal-util.sgml b/doc/devel/calendar/cal-util/tmpl/cal-util.sgml
deleted file mode 100644
index ccd35fac2e..0000000000
--- a/doc/devel/calendar/cal-util/tmpl/cal-util.sgml
+++ /dev/null
@@ -1,48 +0,0 @@
-
-Miscellaneous utilities
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-@list: 
-
-
-
-
-
-
-
-@CALOBJ_TYPE_EVENT: 
-@CALOBJ_TYPE_TODO: 
-@CALOBJ_TYPE_JOURNAL: 
-@CALOBJ_TYPE_ANY: 
-
-
-
-
-
-
-@list: 
-
-
diff --git a/doc/devel/calendar/cal-util/tmpl/evolution-cal-util-unused.sgml b/doc/devel/calendar/cal-util/tmpl/evolution-cal-util-unused.sgml
deleted file mode 100644
index ff68fae99d..0000000000
--- a/doc/devel/calendar/cal-util/tmpl/evolution-cal-util-unused.sgml
+++ /dev/null
@@ -1,228 +0,0 @@
-
-
-
-
-
-@CAL_COMPONENT_ALARM_TRIGGER_RELATED_START: 
-@CAL_COMPONENT_ALARM_TRIGGER_RELATED_END: 
-
-
-
-
-
-
-@r: 
-
-
-
-
-
-
-@CAL_RECUR_YEARLY: 
-@CAL_RECUR_MONTHLY: 
-@CAL_RECUR_WEEKLY: 
-@CAL_RECUR_DAILY: 
-@CAL_RECUR_HOURLY: 
-@CAL_RECUR_MINUTELY: 
-@CAL_RECUR_SECONDLY: 
-
-
-
-
-
-
-
-
-
-
-
-
-@comp: 
-@pilot_id: 
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-@trigger: 
-
-
-
-
-
-
-@t: 
-@hour: 
-@Returns: 
-
-
-
-
-
-
-@str: 
-@Returns: 
-
-
-
-
-
-
-@comp: 
-@pilot_status: 
-
-
-
-
-
-
-@year: 
-@month: 
-@day: 
-@hour: 
-@minute: 
-@second: 
-
-
-
-
-
-
-
-
-
-
-
-
-@CAL_COMPONENT_ALARM_TRIGGER_RELATIVE: 
-@CAL_COMPONENT_ALARM_TRIGGER_ABSOLUTE: 
-
-
-
-
-
-
-@ir: 
-@Returns: 
-
-
-
-
-
-
-@list: 
-
-
-
-
-
-
-@str: 
-@Returns: 
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-@itt: 
-@Returns: 
-
-
-
-
-
-
-@CAL_COMPONENT_ALARM_NONE: 
-@CAL_COMPONENT_ALARM_AUDIO: 
-@CAL_COMPONENT_ALARM_DISPLAY: 
-@CAL_COMPONENT_ALARM_EMAIL: 
-@CAL_COMPONENT_ALARM_PROCEDURE: 
-@CAL_COMPONENT_ALARM_UNKNOWN: 
-
-
-
-
-
-
-@start: 
-@duration: 
-@Returns: 
-
-
-
-
-
-
-@comp: 
-@pilot_id: 
-
-
-
-
-
-
-@secs: 
-@Returns: 
-
-
-
-
-
-
-@hour: 
-@use_am_pm: 
-@Returns: 
-
-
-
-
-
-
-@comp: 
-@pilot_status: 
-
-
-
-
-
-
-@str: 
-@Returns: 
-
diff --git a/doc/devel/calendar/cal-util/tmpl/timeutil.sgml b/doc/devel/calendar/cal-util/tmpl/timeutil.sgml
deleted file mode 100644
index 2b197ad685..0000000000
--- a/doc/devel/calendar/cal-util/tmpl/timeutil.sgml
+++ /dev/null
@@ -1,176 +0,0 @@
-
-timeutil
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@time: 
-@minutes: 
-@Returns: 
-
-
-
-
-
-
-
-@time: 
-@days: 
-@Returns: 
-
-
-
-
-
-
-
-@time: 
-@weeks: 
-@Returns: 
-
-
-
-
-
-
-
-@time: 
-@months: 
-@Returns: 
-
-
-
-
-
-
-
-@time: 
-@years: 
-@Returns: 
-
-
-
-
-
-
-
-@year: 
-@month: 
-@Returns: 
-
-
-
-
-
-
-
-@year: 
-@month: 
-@day: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-
-
diff --git a/doc/devel/calendar/evolution-calendar.sgml b/doc/devel/calendar/evolution-calendar.sgml
deleted file mode 100644
index ea0d8c7127..0000000000
--- a/doc/devel/calendar/evolution-calendar.sgml
+++ /dev/null
@@ -1,52 +0,0 @@
-  
-    
-      
-	
-	  Federico
-	  Mena Quintero
-	  
-	    

-	      federico@ximian.com
-	    

-	  
-	
-      
-    
-
-    Developing Applications with the &Evolution; Calendar
-
-    
-      
-	This part of the &Evolution; Developer's Guide describes how
-	to write applications for the &Evolution; Calendar by using
-	its public interfaces.  The &Evolution; Calendar exports its
-	functionality through a number of interfaces, including CORBA,
-	GTK+ wrappers for Bonobo objects, and other utility libraries.
-	This part also describes the internals of the calendar so that
-	it will be easy for you to make changes to &Evolution;'s core
-	code.
-      
-
-      
-	You should read this part of the &Evolution; Developer's guide
-	if you intend to write client applications that use the
-	functionality of the &Evolution; Calendar, such as its storage
-	interfaces and generic recurrence engine.  If you intend to
-	make changes to the calendar's core code, it will be useful to
-	read the sections on the calendar internals as well.  Even if
-	you do not intend to modify the core code of the calendar, it
-	may be useful to know a few things about the way it works so
-	that you can make better use of the public interfaces.
-      
-    
-
-    &calendar-architecture;
-    &calendar-alarm-generation;
-  
-
-
diff --git a/doc/devel/calendar/public-reference.sgml b/doc/devel/calendar/public-reference.sgml
deleted file mode 100644
index b880bd2972..0000000000
--- a/doc/devel/calendar/public-reference.sgml
+++ /dev/null
@@ -1,24 +0,0 @@
-  
-    Calendar Public API Reference
-
-    
-      
-	This part presents the class and function reference for the
-	public APIs of the different components of the &Evolution;
-	Calendar.
-      
-    
-
-    &CalClient;
-    &CalComponent;
-    &cal-util;
-    &cal-recur;
-    &timeutil;
-  
-
-
diff --git a/doc/devel/evolution-devel-guide.sgml b/doc/devel/evolution-devel-guide.sgml
deleted file mode 100644
index 4a88261da4..0000000000
--- a/doc/devel/evolution-devel-guide.sgml
+++ /dev/null
@@ -1,97 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Evolution">
-Wombat">
-Camel">
-PCS">
-libical">
-Executive Summary">
-]>
-
-
-  
-    &Evolution; Developer's Guide
-
-    
-      
-	Ximian, Inc.
-      
-    
-
-    
-      2000
-      Helix Code, Inc.
-    
-
-    
-      2001
-      Ximian, Inc.
-    
-
-    
-      
-	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 no Invariant
-	Sections, no Front-Cover Texts, and no Back-Cover Texts. You
-	may obtain a copy of the GNU Free Documentation
-	License from the Free Software Foundation by
-	visiting their Web
-	site or by writing to: Free Software Foundation, Inc.,
-	59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
-      
-
-      
-	Many of the names used by companies to distinguish their
-	products and services are claimed as trademarks. Where those
-	names appear in any GNOME documentation, and those trademarks
-	are made aware to the members of the GNOME Documentation
-	Project, the names have been printed in caps or initial caps.
-       
-    
-  
-
-  
-
-  &preface;
-
-  
-
-  &evolution-calendar;
-
-  
-
-  &evolution-reference;
-
-  
-
-  &FDL;
-
diff --git a/doc/devel/executive-summary/Makefile.am b/doc/devel/executive-summary/Makefile.am
deleted file mode 100644
index 9aa53af4ec..0000000000
--- a/doc/devel/executive-summary/Makefile.am
+++ /dev/null
@@ -1,125 +0,0 @@
-# The name of the module.
-DOC_MODULE=evolution-services
-
-# The directory containing the source code
-DOC_SOURCE_DIR=$(EVOLUTION_DIR)/executive-summary/evolution-services
-
-CFLAGS ="						\
-	-I$(top_srcdir)/executive-summary/evolution-services	\
-	-I$(top_srcdir)/executive-summary			\
-	-I$(top_srcdir)					\
-	-I$(top_builddir)				\
-	$(BONOBO_VFS_GNOME_CFLAGS)			\
-	"
-
-LDFLAGS="								\
-	$(BONOBO_VFS_GNOME_LIBS)					\
-	$(top_builddir)/executive-summary/evolution-services/.libs/libevolution-services.a	\
-	"
-
-DOC_DIR=$(datadir)/gnome/html
-
-DOC_DIR_INSTALL_FILES =					\
-	evolution-services.args			\
-	evolution-services.hierarchy		\
-	evolution-services.signals		\
-	evolution-services.types			\
-	evolution-services-decl.txt		\
-	evolution-services-sections.txt
-
-SOURCE_FILES =							\
-	$(top_srcdir)/executive-summary/evolution-services/executive-summary-component.c	\
-	$(top_srcdir)/executive-summary/evolution-services/executive-summary-component-factory-client.c		\
-	$(top_srcdir)/executive-summary/evolution-services/executive-summary-html-view.c
-
-IGNORED_HEADER_FILES =		\
-	Executive-Summary.h
-	
-scan_generated =						\
-	evolution-services-decl.txt			\
-	evolution-services.args				\
-	evolution-services.hierarchy			\
-	evolution-services.signals			\
-	evolution-services.types
-
-tmpl_dependencies =						\
-	evolution-services-decl.txt			\
-	evolution-services-sections.txt			\
-	evolution-services.args				\
-	evolution-services.hierarchy			\
-	evolution-services.signals
-
-tmpl_sources = 						\
-	tmpl/evolution-services.sgml		\
-	tmpl/evolution-services-unused.sgml
-
-tmpl_generated =					\
-	evolution-services-unused.txt
-
-sgml_dependencies =					\
-	evolution-services-decl.txt		\
-	evolution-services-sections.txt		\
-	evolution-services.args			\
-	evolution-services.hierarchy		\
-	evolution-services.signals		\
-	tmpl/evolution-services.sgml
-
-sgml_generated =						\
-	sgml/evolution-services.sgml					\
-	sgml/evolution-services-doc.bottom		\
-	sgml/evolution-services-doc.top			\
-	sgml/object_index.sgml					\
-	sgml/tree_index.sgml
-
-EXTRA_DIST =							\
-	evolution-services.args				\
-	evolution-services.hierarchy			\
-	evolution-services.signals			\
-	evolution-services.types				\
-	evolution-services-decl.txt			\
-	evolution-services-sections.txt
-
-all: $(sgml_generated)
-
-if ENABLE_GTK_DOC
-scan $(scan_generated): $(SOURCE_FILES)
-	-(cd $(srcdir)						\
-	  && env CFLAGS=$(CFLAGS) LDFLAGS=$(LDFLAGS)		\
-		 gtkdoc-scanobj --module=$(DOC_MODULE)		\
-	  && gtkdoc-scan --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR)		\
-			 --ignore-headers="$(IGNORED_HEADER_FILES)" )
-
-templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies)
-	cd $(srcdir) && gtkdoc-mktmpl --module=$(DOC_MODULE)
-
-sgml $(sgml_generated): $(sgml_dependencies)
-	cd $(srcdir) \
-	&& gtkdoc-mkdb --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR)
-else
-scan $(scan_generated): $(SOURCE_FILE)
-
-templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies)
-
-sgml $(sgml_generated): $(sgml_dependencies)
-endif
-
-clean-local:
-	rm -f *~ *.bak *.signals *-unused.txt
-
-maintainer-clean-local: clean
-	cd $(srcdir) && rm -rf sgml $(DOC_MODULE)-decl-list.txt $(DOC_MODULE)-decl.txt
-
-install-data-local:
-	$(mkinstalldirs) $(DOC_DIR)
-	for i in $(DOC_DIR_INSTALL_FILES); do		\
-		$(INSTALL_DATA) $$i $(DOC_DIR);		\
-	done
-
-dist-hook:
-	mkdir $(distdir)/sgml
-	mkdir $(distdir)/tmpl
-	-cp $(srcdir)/tmpl/*.sgml $(distdir)/tmpl
-	-cp $(srcdir)/sgml/*.sgml $(distdir)/sgml
-	-cp $(srcdir)/sgml/*.bottom $(srcdir)/sgml/*.top $(distdir)/sgml
-
-.PHONY: scan templates sgml
diff --git a/doc/devel/executive-summary/evolution-services-decl.txt b/doc/devel/executive-summary/evolution-services-decl.txt
deleted file mode 100644
index df84080700..0000000000
--- a/doc/devel/executive-summary/evolution-services-decl.txt
+++ /dev/null
@@ -1,599 +0,0 @@
-
-EXECUTIVE_SUMMARY_CLIENT_TYPE
-#define EXECUTIVE_SUMMARY_CLIENT_TYPE (executive_summary_client_get_type ())
-
-
-EXECUTIVE_SUMMARY_CLIENT
-#define EXECUTIVE_SUMMARY_CLIENT(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_CLIENT_TYPE, ExecutiveSummaryClient))
-
-
-EXECUTIVE_SUMMARY_CLIENT_CLASS
-#define EXECUTIVE_SUMMARY_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_CLIENT_TYPE, ExecutiveSummaryClientClass))
-
-
-IS_EXECUTIVE_SUMMARY_CLIENT
-#define IS_EXECUTIVE_SUMMARY_CLIENT(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_CLIENT_TYPE))
-
-
-IS_EXECUTIVE_SUMMARY_CLIENT_CLASS
-#define IS_EXECUTIVE_SUMMARY_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_CLIENT_TYPE))
-
-
-ExecutiveSummaryClientPrivate
-
-
-ExecutiveSummaryClient
-
-
-ExecutiveSummaryClientClass
-
-
-ExecutiveSummaryClient
-struct ExecutiveSummaryClient {
-	BonoboObjectClient parent;
-	
-	ExecutiveSummaryClientPrivate *private;
-};
-
-
-ExecutiveSummaryClientClass
-struct ExecutiveSummaryClientClass {
-	BonoboObjectClientClass parent_class;
-};
-
-
-executive_summary_client_get_type
-GtkType  
-void
-
-
-executive_summary_client_construct
-void  
-ExecutiveSummaryClient *client,CORBA_Object object
-
-
-executive_summary_client_set_title
-void  
-ExecutiveSummaryClient *client,int id,const char *title
-
-
-executive_summary_client_set_icon
-void  
-ExecutiveSummaryClient *client,int id,const char *icon
-
-
-executive_summary_client_flash
-void  
-ExecutiveSummaryClient *client,int id
-
-
-executive_summary_client_update
-void  
-ExecutiveSummaryClient *client,int id,const char *html
-
-
-EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_TYPE
-#define EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_TYPE (executive_summary_component_factory_client_get_type ())
-
-
-EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT
-#define EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_TYPE, ExecutiveSummaryComponentFactoryClient))
-
-
-EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_CLASS
-#define EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_TYPE, ExecutiveSummaryComponentFactoryClientClass))
-
-
-IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT
-#define IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_TYPE))
-
-
-IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_CLASS
-#define IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_TYPE))
-
-
-ExecutiveSummaryComponentFactoryClientPrivate
-
-
-ExecutiveSummaryComponentFactoryClient
-
-
-ExecutiveSummaryComponentFactoryClientClass
-
-
-ExecutiveSummaryComponentFactoryClient
-struct ExecutiveSummaryComponentFactoryClient {
-  BonoboObjectClient parent;
-
-  ExecutiveSummaryComponentFactoryClientPrivate *private;
-};
-
-
-ExecutiveSummaryComponentFactoryClientClass
-struct ExecutiveSummaryComponentFactoryClientClass {
-  BonoboObjectClientClass parent_class;
-};
-
-
-executive_summary_component_factory_client_get_type
-GtkType  
-void
-
-
-executive_summary_component_factory_client_construct
-void  
-ExecutiveSummaryComponentFactoryClient *client,CORBA_Object corba_object
-
-
-executive_summary_component_factory_client_new
-ExecutiveSummaryComponentFactoryClient  *
-const char *id
-
-
-executive_summary_component_factory_client_create_view
-CORBA_Object  
-ExecutiveSummaryComponentFactoryClient *client
-
-
-EXECUTIVE_SUMMARY_COMPONENT_TYPE
-#define EXECUTIVE_SUMMARY_COMPONENT_TYPE (executive_summary_component_get_type ())
-
-
-EXECUTIVE_SUMMARY_COMPONENT
-#define EXECUTIVE_SUMMARY_COMPONENT(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_COMPONENT_TYPE, ExecutiveSummaryComponent))
-
-
-EXECUTIVE_SUMMARY_COMPONENT_CLASS
-#define EXECUTIVE_SUMMARY_COMPONENT_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_COMPONENT_TYPE, ExecutiveSummaryComponentClass))
-
-
-IS_EXECUTIVE_SUMMARY_COMPONENT
-#define IS_EXECUTIVE_SUMMARY_COMPONENT(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_TYPE))
-
-
-IS_EXECUTIVE_SUMMARY_COMPONENT_CLASS
-#define IS_EXECUTIVE_SUMMARY_COMPONENT_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_TYPE))
-
-
-ExecutiveSummaryComponentPrivate
-
-
-ExecutiveSummaryComponent
-
-
-ExecutiveSummaryComponentClass
-
-
-ExecutiveSummaryComponent
-struct ExecutiveSummaryComponent {
-  BonoboObject parent;
-
-  ExecutiveSummaryComponentPrivate *private;
-};
-
-
-ExecutiveSummaryComponentClass
-struct ExecutiveSummaryComponentClass {
-  BonoboObjectClass parent_class;
-};
-
-
-executive_summary_component_get_type
-GtkType  
-void
-
-
-executive_summary_component_new
-BonoboObject  *
-void
-
-
-EXECUTIVE_SUMMARY_COMPONENT_FACTORY_TYPE
-#define EXECUTIVE_SUMMARY_COMPONENT_FACTORY_TYPE (executive_summary_component_factory_get_type ())
-
-
-EXECUTIVE_SUMMARY_COMPONENT_FACTORY
-#define EXECUTIVE_SUMMARY_COMPONENT_FACTORY(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_TYPE, ExecutiveSummaryComponentFactory))
-
-
-EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLASS
-#define EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_TYPE, ExecutiveSummaryComponentFactoryClass))
-
-
-IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY
-#define IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_TYPE))
-
-
-IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLASS
-#define IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_TYPE))
-
-
-ExecutiveSummaryComponentFactoryPrivate
-
-
-ExecutiveSummaryComponentFactory
-
-
-ExecutiveSummaryComponentFactoryClass
-
-
-EvolutionServicesCreateViewFn
-BonoboObject *
-ExecutiveSummaryComponentFactory *factory,
-							 void *closure
-
-
-ExecutiveSummaryComponentFactory
-struct ExecutiveSummaryComponentFactory {
-	BonoboObject parent;
-
-	ExecutiveSummaryComponentFactoryPrivate *private;
-};
-
-
-ExecutiveSummaryComponentFactoryClass
-struct ExecutiveSummaryComponentFactoryClass {
-	BonoboObjectClass parent_class;
-};
-
-
-executive_summary_component_factory_get_type
-GtkType  
-void
-
-
-executive_summary_component_factory_new
-BonoboObject  *
-EvolutionServicesCreateViewFn create_view,void *closure
-
-
-EXECUTIVE_SUMMARY_HTML_VIEW_HTML_CHANGED
-#define EXECUTIVE_SUMMARY_HTML_VIEW_HTML_CHANGED "GNOME:Evolution:Summary:HTMLView:html_changed"
-
-
-EXECUTIVE_SUMMARY_HTML_VIEW_TYPE
-#define EXECUTIVE_SUMMARY_HTML_VIEW_TYPE (executive_summary_html_view_get_type ())
-
-
-EXECUTIVE_SUMMARY_HTML_VIEW
-#define EXECUTIVE_SUMMARY_HTML_VIEW(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_HTML_VIEW_TYPE, ExecutiveSummaryHtmlView))
-
-
-EXECUTIVE_SUMMARY_HTML_VIEW_CLASS
-#define EXECUTIVE_SUMMARY_HTML_VIEW_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_HTML_VIEW_TYPE, ExecutiveSummaryHtmlViewClass))
-
-
-IS_EXECUTIVE_SUMMARY_HTML_VIEW
-#define IS_EXECUTIVE_SUMMARY_HTML_VIEW(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_HTML_VIEW_TYPE))
-
-
-IS_EXECUTIVE_SUMMARY_HTML_VIEW_CLASS
-#define IS_EXECUTIVE_SUMMARY_HTML_VIEW_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_HTML_VIEW_TYPE))
-
-
-ExecutiveSummaryHtmlViewPrivate
-
-
-ExecutiveSummaryHtmlView
-
-
-ExecutiveSummaryHtmlViewClass
-
-
-ExecutiveSummaryHtmlView
-struct ExecutiveSummaryHtmlView {
-	BonoboObject parent;
-	
-	ExecutiveSummaryHtmlViewPrivate *private;
-};
-
-
-ExecutiveSummaryHtmlViewClass
-struct ExecutiveSummaryHtmlViewClass {
-	BonoboObjectClass parent_class;
-};
-
-
-executive_summary_html_view_get_type
-GtkType  
-void
-
-
-executive_summary_html_view_new_full
-BonoboObject  *
-BonoboEventSource *event_source
-
-
-executive_summary_html_view_new
-BonoboObject  *
-void
-
-
-executive_summary_html_view_set_html
-void  
-ExecutiveSummaryHtmlView *view,const char *html
-
-
-executive_summary_html_view_get_html
-const char  *
-ExecutiveSummaryHtmlView *view
-
-
-executive_summary_html_view_get_event_source
-BonoboEventSource  *
-ExecutiveSummaryHtmlView *view
-
-
-EXECUTIVE_SUMMARY_COMPONENT_CLIENT_TYPE
-#define EXECUTIVE_SUMMARY_COMPONENT_CLIENT_TYPE (executive_summary_component_client_get_type ())
-
-
-EXECUTIVE_SUMMARY_COMPONENT_CLIENT
-#define EXECUTIVE_SUMMARY_COMPONENT_CLIENT(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_COMPONENT_CLIENT_TYPE, ExecutiveSummaryComponentClient))
-
-
-EXECUTIVE_SUMMARY_COMPONENT_CLIENT_CLASS
-#define EXECUTIVE_SUMMARY_COMPONENT_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_COMPONENT_CLIENT_TYPE, ExecutiveSummaryComponentClientClass))
-
-
-IS_EXECUTIVE_SUMMARY_COMPONENT_CLIENT
-#define IS_EXECUTIVE_SUMMARY_COMPONENT_CLIENT(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_CLIENT_TYPE))
-
-
-IS_EXECUTIVE_SUMMARY_COMPONENT_CLIENT_CLASS
-#define IS_EXECUTIVE_SUMMARY_COMPONENT_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_CLIENT_TYPE))
-
-
-ExecutiveSummaryComponentClientPrivate
-
-
-ExecutiveSummaryComponentClient
-
-
-ExecutiveSummaryComponentClientClass
-
-
-ExecutiveSummaryComponentClient
-struct ExecutiveSummaryComponentClient {
-  BonoboObjectClient parent;
-
-  ExecutiveSummaryComponentClientPrivate *private;
-};
-
-
-ExecutiveSummaryComponentClientClass
-struct ExecutiveSummaryComponentClientClass {
-  BonoboObjectClientClass parent_class;
-};
-
-
-executive_summary_component_client_get_type
-GtkType  
-void
-
-
-executive_summary_component_client_new
-ExecutiveSummaryComponentClient  *
-const char *id
-
-
-executive_summary_component_client_set_owner
-void  
-ExecutiveSummaryComponentClient *client,ExecutiveSummary *summary
-
-
-executive_summary_component_client_unset_owner
-void  
-ExecutiveSummaryComponentClient *client
-
-
-executive_summary_component_client_supports
-void  
-ExecutiveSummaryComponentClient *client,gboolean *bonobo,gboolean *html
-
-
-executive_summary_component_client_configure
-void  
-ExecutiveSummaryComponentClient *client,ExecutiveSummaryComponentView *view
-
-
-executive_summary_component_client_destroy_view
-void  
-ExecutiveSummaryComponentClient *client,ExecutiveSummaryComponentView *view
-
-
-EXECUTIVE_SUMMARY_TYPE
-#define EXECUTIVE_SUMMARY_TYPE (executive_summary_get_type ())
-
-
-EXECUTIVE_SUMMARY
-#define EXECUTIVE_SUMMARY(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_TYPE, ExecutiveSummary))
-
-
-EXECUTIVE_SUMMARY_CLASS
-#define EXECUTIVE_SUMMARY_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_TYPE, ExecutiveSummaryClass))
-
-
-IS_EXECUTIVE_SUMMARY
-#define IS_EXECUTIVE_SUMMARY(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_TYPE))
-
-
-IS_EXECUTIVE_SUMMARY_CLASS
-#define IS_EXECUTIVE_SUMMARY_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_TYPE))
-
-
-ExecutiveSummaryPrivate
-
-
-ExecutiveSummary
-
-
-ExecutiveSummaryClass
-
-
-ExecutiveSummary
-struct ExecutiveSummary {
-	BonoboObject parent;
-	
-	ExecutiveSummaryPrivate *private;
-};
-
-
-ExecutiveSummaryClass
-struct ExecutiveSummaryClass {
-	BonoboObjectClass parent_class;
-
-	void (* update) (ExecutiveSummary *summary,
-			 const GNOME_Evolution_Summary_Component component,
-			 const char *html);
-	void (* set_title) (ExecutiveSummary *summary,
-			    const GNOME_Evolution_Summary_Component component,
-			    const char *title);
-	void (* set_icon) (ExecutiveSummary *summary,
-			   const GNOME_Evolution_Summary_Component component,
-			   const char *icon);
-	void (* flash) (ExecutiveSummary *summary,
-			const GNOME_Evolution_Summary_Component component);
-};
-
-
-executive_summary_get_type
-GtkType  
-void
-
-
-executive_summary_construct
-void  
-ExecutiveSummary *es,GNOME_Evolution_Summary_ViewFrame corba_object
-
-
-executive_summary_new
-BonoboObject  *
-void
-
-
-EXECUTIVE_SUMMARY_COMPONENT_VIEW_TYPE
-#define EXECUTIVE_SUMMARY_COMPONENT_VIEW_TYPE (executive_summary_component_view_get_type ())
-
-
-EXECUTIVE_SUMMARY_COMPONENT_VIEW
-#define EXECUTIVE_SUMMARY_COMPONENT_VIEW(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_COMPONENT_VIEW_TYPE, ExecutiveSummaryComponentView))
-
-
-EXECUTIVE_SUMMARY_COMPONENT_VIEW_CLASS
-#define EXECUTIVE_SUMMARY_COMPONENT_VIEW_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_COMPONENT_VIEW_TYPE, ExecutiveSummaryComponentClass))
-
-
-IS_EXECUTIVE_SUMMARY_COMPONENT_VIEW
-#define IS_EXECUTIVE_SUMMARY_COMPONENT_VIEW(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_VIEW_TYPE))
-
-
-IS_EXECUTIVE_SUMMARY_COMPONENT_VIEW_CLASS
-#define IS_EXECUTIVE_SUMMARY_COMPONENT_VIEW_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_VIEW_CLASS_TYPE))
-
-
-ExecutiveSummaryComponentViewPrivate
-
-
-ExecutiveSummaryComponentView
-
-
-ExecutiveSummaryComponentViewClass
-
-
-ExecutiveSummaryComponentView
-struct ExecutiveSummaryComponentView {
-	GtkObject object;
-	
-	ExecutiveSummaryComponentViewPrivate *private;
-};
-
-
-ExecutiveSummaryComponentViewClass
-struct ExecutiveSummaryComponentViewClass {
-	GtkObjectClass parent_class;
-
-	/* Signals */
-	void (* configure) (ExecutiveSummaryComponentView *view);
-};
-
-
-executive_summary_component_view_get_type
-GtkType  
-void
-
-
-executive_summary_component_view_construct
-void
-ExecutiveSummaryComponentView *view,ExecutiveSummaryComponent *component,BonoboControl *control,const char *html,const char *title,const char *icon
-
-
-executive_summary_component_view_new
-ExecutiveSummaryComponentView  *
-ExecutiveSummaryComponent *component,BonoboControl *control,const char *html,const char *title,const char *icon
-
-
-executive_summary_component_view_set_title
-void  
-ExecutiveSummaryComponentView *view,const char *title
-
-
-executive_summary_component_view_get_title
-const char  *
-ExecutiveSummaryComponentView *view
-
-
-executive_summary_component_view_set_icon
-void  
-ExecutiveSummaryComponentView *view,const char *icon
-
-
-executive_summary_component_view_get_icon
-const char  *
-ExecutiveSummaryComponentView *view
-
-
-executive_summary_component_view_flash
-void  
-ExecutiveSummaryComponentView *view
-
-
-executive_summary_component_view_set_html
-void  
-ExecutiveSummaryComponentView *view,const char *html
-
-
-executive_summary_component_view_get_html
-const char  *
-ExecutiveSummaryComponentView *view
-
-
-executive_summary_component_view_get_control
-BonoboObject  *
-ExecutiveSummaryComponentView *view
-
-
-executive_summary_component_view_get_id
-int  
-ExecutiveSummaryComponentView *view
-
-
-executive_summary_component_view_set_id
-void  
-ExecutiveSummaryComponentView *view,int id
-
-
-executive_summary_component_view_configure
-void  
-ExecutiveSummaryComponentView *view
-
-
-executive_summary_component_view_set_objref
-void  
-ExecutiveSummaryComponentView *view,Bonobo_Control objref
-
-
-executive_summary_component_view_get_widget
-GtkWidget  *
-ExecutiveSummaryComponentView *view
-
diff --git a/doc/devel/executive-summary/evolution-services-sections.txt b/doc/devel/executive-summary/evolution-services-sections.txt
deleted file mode 100644
index 8ba2b42317..0000000000
--- a/doc/devel/executive-summary/evolution-services-sections.txt
+++ /dev/null
@@ -1,95 +0,0 @@
-executive-summary-component.h
-

-executive-summary-component
-EXECUTIVE_SUMMARY_COMPONENT
-ExecutiveSummaryComponent
-
-executive_summary_component_new
-
-
-EXECUTIVE_SUMMARY_COMPONENT_TYPE
-EXECUTIVE_SUMMARY_COMPONENT
-EXECUTIVE_SUMMARY_COMPONENT_CLASS
-IS_EXECUTIVE_SUMMARY_COMPONENT
-IS_EXECUTIVE_SUMMARY_COMPONENT_CLASS
-executive_summary_component_get_type
-
-
-ExecutiveSummaryComponent
-ExecutiveSummaryComponentPrivate
-
-

-
-

-executive-summary-component-factory
-EXECUTIVE_SUMMARY_COMPONENT_FACTORY
-ExecutiveSummaryComponentFactory
-
-EvolutionServicesCreateViewFn
-
-executive_summary_component_factory_new
-
-
-EXECUTIVE_SUMMARY_COMPONENT_FACTORY_TYPE
-EXECUTIVE_SUMMARY_COMPONENT_FACTORY
-EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLASS
-IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY
-IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLASS
-executive_summary_component_factory_get_type
-
-
-ExecutiveSummaryComponentFactory
-ExecutiveSummaryComponentFactoryPrivate
-
-

-
-executive-summary-component-factory-client.h
-

-executive-summary-component-factory-client
-EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT
-ExecutiveSummaryComponentFactoryClient
-
-executive_summary_component_factory_client_construct
-executive_summary_component_factory_client_new
-executive_summary_component_factory_client_create_view
-
-
-EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_TYPE
-EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT
-EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_CLASS
-IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT
-IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_CLASS
-executive_summary_component_factory_client_get_type
-
-
-ExecutiveSummaryComponentFactoryClient
-ExecutiveSummaryComponentFactoryClientPrivate
-
-

-
-executive-summary-html-view.h
-

-executive-summary-html-view
-EXECUTIVE_SUMMARY_HTML_VIEW
-ExecutiveSummaryHtmlView
-
-EXECUTIVE_SUMMARY_HTML_VIEW_HTML_CHANGED
-
-executive_summary_html_view_new_full
-executive_summary_html_view_new
-executive_summary_html_view_set_html
-executive_summary_html_view_get_html
-executive_summary_html_view_get_event_source
-
-
-EXECUTIVE_SUMMARY_HTML_VIEW_TYPE
-EXECUTIVE_SUMMARY_HTML_VIEW
-IS_EXECUTIVE_SUMMARY_HTML_VIEW
-EXECUTIVE_SUMMARY_HTML_VIEW_CLASS
-IS_EXECUTIVE_SUMMARY_HTML_VIEW_CLASS
-executive_summary_html_view_get_type
-
-
-ExecutiveSummaryHtmlView
-ExecutiveSummaryHtmlViewPrivate
-

diff --git a/doc/devel/executive-summary/evolution-services.args b/doc/devel/executive-summary/evolution-services.args
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/doc/devel/executive-summary/evolution-services.hierarchy b/doc/devel/executive-summary/evolution-services.hierarchy
deleted file mode 100644
index 07e7aad6ff..0000000000
--- a/doc/devel/executive-summary/evolution-services.hierarchy
+++ /dev/null
@@ -1,15 +0,0 @@
-GtkObject
-  GtkWidget
-    GtkRange
-      GtkScale
-    GtkContainer
-      GtkBin
-        GtkButton
-          GtkToggleButton
-            GtkCheckButton
-  BonoboObject
-    ExecutiveSummaryComponent
-    ExecutiveSummaryComponentFactory
-    Handle to remote Bonobo::Unknown
-      ExecutiveSummaryComponentFactoryClient
-    ExecutiveSummaryHtmlView
diff --git a/doc/devel/executive-summary/evolution-services.signals b/doc/devel/executive-summary/evolution-services.signals
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/doc/devel/executive-summary/evolution-services.types b/doc/devel/executive-summary/evolution-services.types
deleted file mode 100644
index b7ac05b89c..0000000000
--- a/doc/devel/executive-summary/evolution-services.types
+++ /dev/null
@@ -1,10 +0,0 @@
-#include 
-#include 
-#include 
-#include 
-#include 
-
-executive_summary_component_get_type
-executive_summary_component_factory_get_type
-executive_summary_component_factory_client_get_type
-executive_summary_html_view_get_type
diff --git a/doc/devel/executive-summary/private-reference.sgml b/doc/devel/executive-summary/private-reference.sgml
deleted file mode 100644
index e06d7c1690..0000000000
--- a/doc/devel/executive-summary/private-reference.sgml
+++ /dev/null
@@ -1,20 +0,0 @@
-  
-    Evolution Services Private API Reference
-
-    
-      
-	This part presents the class and function reference for the
-	private APIs of the different components of the &Evolution;
-	Executive Summary Services Framework.
-      
-    
-    
-    &ExecutiveSummaryComponentFactoryClient;
-  
-
-
diff --git a/doc/devel/executive-summary/public-reference.sgml b/doc/devel/executive-summary/public-reference.sgml
deleted file mode 100644
index 7758a9a5c8..0000000000
--- a/doc/devel/executive-summary/public-reference.sgml
+++ /dev/null
@@ -1,22 +0,0 @@
- 
-    Evolution Services Public API Reference
-
-    
-      
-        This part presents the class and function reference for the
-        public APIs of the different components of the &Evolution;
-        Executive Summary Services Framework.
-      
-    
-
-    &ExecutiveSummaryComponent;
-    &ExecutiveSummaryComponentFactory;
-    &ExecutiveSummaryHtmlView;
-  
-
-
diff --git a/doc/devel/executive-summary/tmpl/evolution-services-unused.sgml b/doc/devel/executive-summary/tmpl/evolution-services-unused.sgml
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/doc/devel/executive-summary/tmpl/executive-summary-component-factory-client.sgml b/doc/devel/executive-summary/tmpl/executive-summary-component-factory-client.sgml
deleted file mode 100644
index ee8ef25689..0000000000
--- a/doc/devel/executive-summary/tmpl/executive-summary-component-factory-client.sgml
+++ /dev/null
@@ -1,53 +0,0 @@
-
-ExecutiveSummaryComponentFactoryClient
-
-
-GtkObject client to simplfy use of GNOME_Evolution_Summary_ComponentFactory
-
-
-
-This object provides an easy wrapper around the CORBA object that represents the
- GNOME_Evolution_Summary_ComponentFactory interface. It handles conversion from
-normal types to CORBA types and has error checking.
-
-
-
-
-
-
-
-
-
-Casts a #GtkObject into an #ExecutiveSummaryComponentFactoryClient
-
-
-@obj: 
-
-
-
-
-
-
-
-@client: 
-@corba_object: 
-
-
-
-
-
-
-
-@id: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@Returns: 
-
-
diff --git a/doc/devel/executive-summary/tmpl/executive-summary-component-factory.sgml b/doc/devel/executive-summary/tmpl/executive-summary-component-factory.sgml
deleted file mode 100644
index 7069eea9d0..0000000000
--- a/doc/devel/executive-summary/tmpl/executive-summary-component-factory.sgml
+++ /dev/null
@@ -1,46 +0,0 @@
-
-ExecutiveSummaryComponentFactory
-
-
-GtkObject wrapper for GNOME/Evolution/Summary/ComponentFactory.
-
-
-
-An ExecutiveSummaryComponentFactory simplifies the creation of a 
-GNOME_Evolution_Summary_ComponentFactory object. It also allows error checking
-and all the standard #GtkObject signals.
-
-
-
-
-
-
-
-
-
-Casts a #GtkObject to an #ExecutiveSummaryComponentFactory.
-
-
-@obj: A #GtkObject.
-
-
-
-
-The type of function that is called when the factory has to create a new view.
-
-
-@factory: The #ExecutiveSummaryComponent that is creating the view.
-@closure: The data that was passed into executive_summary_factory_new ().
-@Returns: An #ExecutiveSummaryComponent.
-
-
-
-
-
-
-
-@create_view: 
-@closure: 
-@Returns: 
-
-
diff --git a/doc/devel/executive-summary/tmpl/executive-summary-component.sgml b/doc/devel/executive-summary/tmpl/executive-summary-component.sgml
deleted file mode 100644
index 04768b1b1c..0000000000
--- a/doc/devel/executive-summary/tmpl/executive-summary-component.sgml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-ExecutiveSummaryComponent
-
-
-The base #BonoboObject that implements GNOME/Evolution/Summary/Component.
-
-
-
-This #GtkObject wrapper around the GNOME/Evolution/Summary/Component, is the
-base object that has all the other interfaces aggregated onto it. These
-interfaces are: GNOME/Evolution/HTMLView, Bonobo/Control, Bonobo/EventSource,
-Bonobo/PropertyBag, Bonobo/PropertyControl and Bonobo/PersistStream. Each of
-the aggregated interfaces performs a specific job in the creation of the service.
-
-
-
-
-#ExecutiveSummaryHtmlView, #BonoboControl, #BonoboEventSource, #BonoboPropertyBag,
-#BonoboPropertyControl, #BonoboPersistStream.
-
-
-
-
-Casts a #GtkObject to an #ExecutiveSummaryComponent.
-
-
-@obj: A #GtkObject.
-
-
-
-
-
-
-
-@Returns: 
-
-
diff --git a/doc/devel/executive-summary/tmpl/executive-summary-html-view.sgml b/doc/devel/executive-summary/tmpl/executive-summary-html-view.sgml
deleted file mode 100644
index 2fb66a2035..0000000000
--- a/doc/devel/executive-summary/tmpl/executive-summary-html-view.sgml
+++ /dev/null
@@ -1,75 +0,0 @@
-
-ExecutiveSummaryHtmlView
-
-
-A Bonobo component used to implement HTML based services.
-
-
-
-When writing HTML services, this component is aggregated onto an #ExecutiveSummaryComponent, to allow the Executive Summary to be able to find the HTML.
-
-
-
-
-#ExecutiveSummaryComponent, #BonoboEventSource
-
-
-
-
-  Casts a #GtkObject into an #ExecutiveSummaryHtmlView
-
-
-@obj: A #GtkObject
-
-
-
-
-This is the event that is emitted on the BonoboEventSource when the HTML is changed.
-
-
-
-
-
-
-
-
-
-@event_source: 
-@Returns: 
-
-
-
-
-
-
-
-@Returns: 
-
-
-
-
-
-
-
-@view: 
-@html: 
-
-
-
-
-
-
-
-@view: 
-@Returns: 
-
-
-
-
-
-
-
-@view: 
-@Returns: 
-
-
diff --git a/doc/devel/fdl.sgml b/doc/devel/fdl.sgml
deleted file mode 100644
index 817adbdbb7..0000000000
--- a/doc/devel/fdl.sgml
+++ /dev/null
@@ -1,671 +0,0 @@
-
-
-
-  
-    
-      Version 1.1, March 2000
-    
-    
-      2000Free Software Foundation, Inc.
-    
-    
-      
-	
Free Software Foundation, Inc. 59 Temple Place, 
-        Suite 330, Boston, MA  
-        02111-1307  USA
 
-	Everyone is permitted to copy and distribute verbatim copies of this 
-        license document, but changing it is not allowed.
-      
-    
-  
-  GNU Free Documentation License
-
-  
-    0. PREAMBLE
-    
-      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.
-    
-    
-    
-      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.
-    
-    
-    
-      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.
-    
-  
-  
-    1. APPLICABILITY AND DEFINITIONS
-    
-      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
-      Document, below, refers to any such manual or
-      work. Any member of the public is a licensee, and is addressed
-      as you.
-    
-    
-    
-      A Modified Version 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.
-    
-	
-    
-      A Secondary Section is a named appendix or a
-      front-matter section of the Document that deals exclusively
-      with the relationship of the publishers or authors of the
-      Document to the Document's overall subject (or to related
-      matters) and contains nothing that could fall directly within
-      that overall subject. (For example, if the Document is in part a
-      textbook of mathematics, a Secondary Section may not explain any
-      mathematics.)  The relationship could be a matter of historical
-      connection with the subject or with related matters, or of
-      legal, commercial, philosophical, ethical or political position
-      regarding them.
-    
-
-    
-      The Invariant Sections are certain  Secondary Sections whose titles
-      are designated, as being those of Invariant Sections, in the
-      notice that says that the Document is released under this
-      License.
-    
-    
-    
-      The Cover Texts are certain short passages of
-      text that are listed, as Front-Cover Texts or Back-Cover Texts,
-      in the notice that says that the Document is released under this
-      License.
-    
-	
-    
-      A Transparent copy of the  Document means a machine-readable
-      copy, represented in a format whose specification is available
-      to the general public, whose contents can be viewed and edited
-      directly and straightforwardly with generic text editors or (for
-      images composed of pixels) generic paint programs or (for
-      drawings) some widely available drawing editor, and that is
-      suitable for input to text formatters or for automatic
-      translation to a variety of formats suitable for input to text
-      formatters. A copy made in an otherwise Transparent file format
-      whose markup has been designed to thwart or discourage
-      subsequent modification by readers is not Transparent.  A copy
-      that is not Transparent is called
-      Opaque.
-    
-    
-    
-      Examples of suitable formats for Transparent copies include
-      plain ASCII without markup, Texinfo input format, LaTeX input
-      format, SGML or XML using a publicly available DTD, and
-      standard-conforming simple HTML designed for human
-      modification. Opaque formats include PostScript, PDF,
-      proprietary formats that can be read and edited only by
-      proprietary word processors, SGML or XML for which the DTD
-      and/or processing tools are not generally available, and the
-      machine-generated HTML produced by some word processors for
-      output purposes only.
-    
-    
-    
-      The Title Page 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, Title Page means the text near the
-      most prominent appearance of the work's title, preceding the
-      beginning of the body of the text.
-    
-  
-    
-  
-    2. VERBATIM COPYING
-    
-      You may copy and distribute the Document in any medium, either
-      commercially or noncommercially, provided that this License, the
-      copyright notices, and the license notice saying this License
-      applies to the Document are reproduced in all copies, and that
-      you add no other conditions whatsoever to those of this
-      License. You may not use technical measures to obstruct or
-      control the reading or further copying of the copies you make or
-      distribute. However, you may accept compensation in exchange for
-      copies. If you distribute a large enough number of copies you
-      must also follow the conditions in section 3.
-    
-    
-    
-      You may also lend copies, under the same conditions stated
-      above, and you may publicly display copies.
-    
-    
-    
-  
-    3. COPYING IN QUANTITY
-    
-      If you publish printed copies of the Document numbering more than 100,
-      and the Document's license notice requires Cover Texts, you must enclose
-      the copies in covers that carry, clearly and legibly, all these
-      Cover Texts: Front-Cover Texts on the front cover, and
-      Back-Cover Texts on the back cover. Both covers must also
-      clearly and legibly identify you as the publisher of these
-      copies. The front cover must present the full title with all
-      words of the title equally prominent and visible. You may add
-      other material on the covers in addition. Copying with changes
-      limited to the covers, as long as they preserve the title of the
-      Document and satisfy these
-      conditions, can be treated as verbatim copying in other
-      respects.
-    
-    
-    
-      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.
-    
-    
-    
-      If you publish or distribute Opaque copies of the Document numbering more than 100,
-      you must either include a machine-readable Transparent copy along with
-      each Opaque copy, or state in or with each Opaque copy a
-      publicly-accessible computer-network location containing a
-      complete Transparent copy of the Document, free of added
-      material, which the general network-using public has access to
-      download anonymously at no charge using public-standard network
-      protocols. If you use the latter option, you must take
-      reasonably prudent steps, when you begin distribution of Opaque
-      copies in quantity, to ensure that this Transparent copy will
-      remain thus accessible at the stated location until at least one
-      year after the last time you distribute an Opaque copy (directly
-      or through your agents or retailers) of that edition to the
-      public.
-    
-    
-    
-      It is requested, but not required, that you contact the authors
-      of the Document well before
-      redistributing any large number of copies, to give them a chance
-      to provide you with an updated version of the Document.
-    
-    
-    
-  
-    4. MODIFICATIONS
-    
-      You may copy and distribute a Modified Version of the Document under the conditions of
-      sections 2 and 3 above, provided that you release
-      the Modified Version under precisely this License, with the
-      Modified Version filling the role of the Document, thus
-      licensing distribution and modification of the Modified Version
-      to whoever possesses a copy of it. In addition, you must do
-      these things in the Modified Version:
-    
-    
-    
-      
-	
-	  A
-	  
-	    Use in the Title
-	    Page (and on the covers, if any) a title distinct
-	    from that of the Document, and from those of
-	    previous versions (which should, if there were any, be
-	    listed in the History section of the Document). You may
-	    use the same title as a previous version if the original
-	    publisher of that version gives permission.
-	  
-	
-      
-      
-      
-	
-	  B
-	  
-	    List on the Title
-	    Page, as authors, one or more persons or entities
-	    responsible for authorship of the modifications in the
-	    Modified Version,
-	    together with at least five of the principal authors of
-	    the Document (all of
-	    its principal authors, if it has less than five).
-	  
-	
-      
-      
-      
-	
-	  C
-	  
-	    State on the Title
-	    Page the name of the publisher of the Modified Version, as the
-	    publisher.
-	  
-	
-      
-      
-      
-	
-	  D
-	  
-	    Preserve all the copyright notices of the Document.
-	  
-	
-      
-      
-      
-	
-	  E
-	  
-	    Add an appropriate copyright notice for your modifications
-	    adjacent to the other copyright notices.
-	  
-	
-      
-      
-      
-	
-	  F
-	  
-	    Include, immediately after the copyright notices, a
-	    license notice giving the public permission to use the
-	    Modified Version under
-	    the terms of this License, in the form shown in the
-	    Addendum below.
-	  
-	
-      
-      
-      
-	
-	  G
-	  
-	    Preserve in that license notice the full lists of  Invariant Sections and
-	    required Cover
-	    Texts given in the Document's license notice.
-	  
-	
-      
-      
-      
-	
-	  H
-	  
-	    Include an unaltered copy of this License.
-	  
-	
-      
-      
-      
-	
-	  I
-	  
-	    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 Modified Version as given on
-	    the Title Page.  If
-	    there is no section entitled History in the
-	    Document, create one
-	    stating the title, year, authors, and publisher of the
-	    Document as given on its Title Page, then add an item
-	    describing the Modified Version as stated in the previous
-	    sentence.
-	  
-	
-      
-      
-      
-	
-	  J
-	  
-	    Preserve the network location, if any, given in the Document for public access
-	    to a Transparent
-	    copy of the Document, and likewise the network locations
-	    given in the Document for previous versions it was based
-	    on. These may be placed in the History
-	    section.  You may omit a network location for a work that
-	    was published at least four years before the Document
-	    itself, or if the original publisher of the version it
-	    refers to gives permission.
-	  
-	
-      
-      
-      
-	
-	  K
-	  
-	    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.
-	  
-	
-      
-      
-      
-	
-	  L
-	  
-	    Preserve all the Invariant
-	    Sections of the Document, unaltered in their
-	    text and in their titles.  Section numbers or the
-	    equivalent are not considered part of the section titles.
-	  
-	
-      
-      
-      
-	
-	  M
-	  
-	    Delete any section entitled
-	    Endorsements. Such a section may not be
-	    included in the Modified
-	    Version.
-	  
-	
-      
-      
-      
-	
-	  N
-	  
-	    Do not retitle any existing section as
-	    Endorsements or to conflict in title with
-	    any Invariant
-	    Section.
-	  
-	
-      
-    
-    
-    
-      If the Modified Version
-      includes new front-matter sections or appendices that qualify as
-      Secondary Sections 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 Invariant Sections in the
-      Modified Version's license notice.  These titles must be
-      distinct from any other section titles.
-    
-    
-    
-      You may add a section entitled Endorsements,
-      provided it contains nothing but endorsements of your Modified Version 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.
-    
-    
-    
-      You may add a passage of up to five words as a Front-Cover Text, and a passage
-      of up to 25 words as a Back-Cover Text, to the end of
-      the list of Cover Texts
-      in the Modified Version.
-      Only one passage of Front-Cover Text and one of Back-Cover Text
-      may be added by (or through arrangements made by) any one
-      entity. If the Document
-      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.
-    
-    
-    
-      The author(s) and publisher(s) of the Document do not by this License
-      give permission to use their names for publicity for or to
-      assert or imply endorsement of any Modified Version .
-    
-  
-    
-  
-    5. COMBINING DOCUMENTS
-    
-      You may combine the Document
-      with other documents released under this License, under the
-      terms defined in section 4
-      above for modified versions, provided that you include in the
-      combination all of the Invariant
-      Sections of all of the original documents, unmodified,
-      and list them all as Invariant Sections of your combined work in
-      its license notice.
-    
-    
-    
-      The combined work need only contain one copy of this License,
-      and multiple identical Invariant
-      Sections may be replaced with a single copy. If there are
-      multiple Invariant Sections with the same name but different
-      contents, make the title of each such section unique by adding
-      at the end of it, in parentheses, the name of the original
-      author or publisher of that section if known, or else a unique
-      number. Make the same adjustment to the section titles in the
-      list of Invariant Sections in the license notice of the combined
-      work.
-    
-    
-    
-      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.
-    
-    
-    
-  
-    6. COLLECTIONS OF DOCUMENTS
-    
-      You may make a collection consisting of the Document 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.
-    
-    
-    
-      You may extract a single document from such a collection, and
-      dispbibute it individually under this License, provided you
-      insert a copy of this License into the extracted document, and
-      follow this License in all other respects regarding verbatim
-      copying of that document.
-    
-    
-    
-  
-    7. AGGREGATION WITH INDEPENDENT WORKS
-    
-      A compilation of the Document 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 Modified Version
-      of the Document, 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 Document , on
-      account of their being thus compiled, if they are not themselves
-      derivative works of the Document.  If the Cover Text requirement of section 3 is applicable to these
-      copies of the Document, then if the Document is less than one
-      quarter of the entire aggregate, the Document's Cover Texts may
-      be placed on covers that surround only the Document within the
-      aggregate. Otherwise they must appear on covers around the whole
-      aggregate.
-    
-    
-    
-  
-    8. TRANSLATION
-    
-      Translation is considered a kind of modification, so you may
-      distribute translations of the Document under the terms of section 4. Replacing  Invariant Sections with
-      translations requires special permission from their copyright
-      holders, but you may include translations of some or all
-      Invariant Sections in addition to the original versions of these
-      Invariant Sections. You may include a translation of this
-      License provided that you also include the original English
-      version of this License. In case of a disagreement between the
-      translation and the original English version of this License,
-      the original English version will prevail.
-    
-    
-    
-  
-    9. TERMINATION
-    
-      You may not copy, modify, sublicense, or distribute the Document except as expressly
-      provided for under this License. Any other attempt to copy,
-      modify, sublicense or distribute the Document is void, and will
-      automatically terminate your rights under this License. However,
-      parties who have received copies, or rights, from you under this
-      License will not have their licenses terminated so long as such
-      parties remain in full compliance.
-    
-    
-    
-  
-    10. FUTURE REVISIONS OF THIS LICENSE
-    
-      The Free Software
-      Foundation 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 http://www.gnu.org/copyleft/.
-    
-    
-    
-      Each version of the License is given a distinguishing version
-      number. If the Document
-      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 Document does not specify a version number of this License,
-      you may choose any version ever published (not as a draft) by
-      the Free Software Foundation.
-    
-  
-
-  
-    Addendum
-    
-      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:
-    
-    
-    

-      
-	Copyright © YEAR YOUR NAME.
-      
-      
-	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 Invariant Sections being LIST
-	THEIR TITLES, with the Front-Cover Texts being LIST,
-	and with the Back-Cover
-	Texts being LIST.  A copy of the license is included in
-	the section entitled GNU Free Documentation
-	License.
-      
-    

-      
-    
-      If you have no Invariant
-      Sections, write with no Invariant Sections
-      instead of saying which ones are invariant.  If you have no
-      Front-Cover Texts, write
-      no Front-Cover Texts instead of
-      Front-Cover Texts being LIST; likewise for Back-Cover Texts.
-    
-    
-    
-      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  GNU General Public
-      License, to permit their use in free software.
-    
-  
-  
-
-
-
-
-
-
diff --git a/doc/devel/importer/.cvsignore b/doc/devel/importer/.cvsignore
deleted file mode 100644
index 0842a93f7a..0000000000
--- a/doc/devel/importer/.cvsignore
+++ /dev/null
@@ -1,3 +0,0 @@
-sgml
-Makefile
-Makefile.in
diff --git a/doc/devel/importer/Makefile.am b/doc/devel/importer/Makefile.am
deleted file mode 100644
index ef3b2b98ee..0000000000
--- a/doc/devel/importer/Makefile.am
+++ /dev/null
@@ -1,127 +0,0 @@
-# The name of the module.
-DOC_MODULE=evolution-shell-importer
-
-# The directory containing the source code
-DOC_SOURCE_DIR=$(EVOLUTION_DIR)/shell/importer
-
-CFLAGS ="						\
-	-I$(top_srcdir)/shell/importer			\
-	-I$(top_srcdir)/shell				\
-	-I$(top_srcdir)					\
-	-I$(top_builddir)				\
-	$(BONOBO_VFS_GNOME_CFLAGS)			\
-	"
-
-LDFLAGS="								\
-	$(BONOBO_VFS_GNOME_LIBS)					\
-	$(top_builddir)/shell/importer/.libs/libevolution-importer.a	\
-	"
-
-DOC_DIR=$(datadir)/gnome/html
-
-DOC_DIR_INSTALL_FILES =					\
-	evolution-shell-importer.args			\
-	evolution-shell-importer.hierarchy		\
-	evolution-shell-importer.signals		\
-	evolution-shell-importer.types			\
-	evolution-shell-importer-decl.txt		\
-	evolution-shell-importer-sections.txt
-
-SOURCE_FILES =								\
-	$(top_srcdir)/shell/importer/evolution-importer.c		\
-	$(top_srcdir)/shell/importer/evolution-importer.h		\
-	$(top_srcdir)/shell/importer/evolution-importer-client.c	\
-	$(top_srcdir)/shell/importer/evolution-importer-client.h
-
-IGNORED_HEADER_FILES =			\
-	GNOME_Evolution_Importer.h	\
-	importer.h
-
-scan_generated =						\
-	evolution-shell-importer-decl.txt			\
-	evolution-shell-importer.args				\
-	evolution-shell-importer.hierarchy			\
-	evolution-shell-importer.signals			\
-	evolution-shell-importer.types
-
-tmpl_dependencies =						\
-	evolution-shell-importer-decl.txt			\
-	evolution-shell-importer-sections.txt			\
-	evolution-shell-importer.args				\
-	evolution-shell-importer.hierarchy			\
-	evolution-shell-importer.signals
-
-tmpl_sources = 						\
-	tmpl/evolution-importer.sgml			\
-	tmpl/evolution-shell-importer-unused.sgml
-
-tmpl_generated =					\
-	evolution-shell-importer-unused.txt
-
-sgml_dependencies =					\
-	evolution-shell-importer-decl.txt		\
-	evolution-shell-importer-sections.txt		\
-	evolution-shell-importer.args			\
-	evolution-shell-importer.hierarchy		\
-	evolution-shell-importer.signals		\
-	tmpl/evolution-importer.sgml
-
-sgml_generated =					\
-	sgml/evolution-importer.sgml			\
-	sgml/evolution-shell-importer-doc.bottom	\
-	sgml/evolution-shell-importer-doc.top		\
-	sgml/object_index.sgml				\
-	sgml/tree_index.sgml
-
-EXTRA_DIST =							\
-	evolution-shell-importer.args				\
-	evolution-shell-importer.hierarchy			\
-	evolution-shell-importer.signals			\
-	evolution-shell-importer.types				\
-	evolution-shell-importer-decl.txt			\
-	evolution-shell-importer-sections.txt
-
-all: $(sgml_generated)
-
-if ENABLE_GTK_DOC
-scan $(scan_generated): $(SOURCE_FILES)
-	-(cd $(srcdir)						\
-	  && env CFLAGS=$(CFLAGS) LDFLAGS=$(LDFLAGS)		\
-		 gtkdoc-scanobj --module=$(DOC_MODULE)		\
-	  && gtkdoc-scan --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR)		\
-			 --ignore-headers="$(IGNORED_HEADER_FILES)" )
-
-templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies)
-	cd $(srcdir) && gtkdoc-mktmpl --module=$(DOC_MODULE)
-
-sgml $(sgml_generated): $(sgml_dependencies)
-	cd $(srcdir) \
-	&& gtkdoc-mkdb --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR)
-else
-scan $(scan_generated): $(SOURCE_FILE)
-
-templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies)
-
-sgml $(sgml_generated): $(sgml_dependencies)
-endif
-
-clean-local:
-	rm -f *~ *.bak *.signals *-unused.txt
-
-maintainer-clean-local: clean
-	cd $(srcdir) && rm -rf sgml $(DOC_MODULE)-decl-list.txt $(DOC_MODULE)-decl.txt
-
-install-data-local:
-	$(mkinstalldirs) $(DOC_DIR)
-	for i in $(DOC_DIR_INSTALL_FILES); do		\
-		$(INSTALL_DATA) $$i $(DOC_DIR);		\
-	done
-
-dist-hook:
-	mkdir $(distdir)/sgml
-	mkdir $(distdir)/tmpl
-	-cp $(srcdir)/tmpl/*.sgml $(distdir)/tmpl
-	-cp $(srcdir)/sgml/*.sgml $(distdir)/sgml
-	-cp $(srcdir)/sgml/*.bottom $(srcdir)/sgml/*.top $(distdir)/sgml
-
-.PHONY: scan templates sgml
diff --git a/doc/devel/importer/evolution-shell-importer-sections.txt b/doc/devel/importer/evolution-shell-importer-sections.txt
deleted file mode 100644
index e2474f6375..0000000000
--- a/doc/devel/importer/evolution-shell-importer-sections.txt
+++ /dev/null
@@ -1,79 +0,0 @@
-evolution-importer.h
-
-

-evolution-importer
-EVOLUTION_IMPORTER
-EvolutionImporter
-
-EvolutionImporterSupportFormatFn
-EvolutionImporterLoadFileFn
-EvolutionImporterProcessItemFn
-EvolutionImporterGetErrorFn
-
-EvolutionImporterResult
-
-evolution_importer_new
-
-
-EVOLUTION_TYPE_IMPORTER
-EVOLUTION_IMPORTER
-EVOLUTION_IS_IMPORTER
-EVOLUTION_IMPORTER_CLASS
-EVOLUTION_IS_IMPORTER_CLASS
-evolution_importer_get_type
-
-
-EvolutionImporter
-EvolutionImporterPrivate
-
-

-
-evolution-importer-listener.h
-

-evolution-importer-listener
-EVOLUTION_IMPORTER_LISTENER
-EvolutionImporterListener
-
-EvolutionImporterListenerCallback
-
-evolution_importer_listener_new
-
-
-EVOLUTION_TYPE_IMPORTER_LISTENER
-EVOLUTION_IMPORTER_LISTENER
-EVOLUTION_IMPORTER_LISTENER_CLASS
-EVOLUTION_IS_IMPORTER_LISTENER
-EVOLUTION_IS_IMPORTER_LISTENER_CLASS
-evolution_importer_listener_get_type
-
-
-EvolutionImporterListener
-EvolutionImporterListenerPrivate
-
-

-
-evolution-importer-client.h
-

-evolution-importer-client
-EVOLUTION_IMPORTER_CLIENT
-EvolutionImporterClient
-
-evolution_importer_client_new
-evolution_importer_client_new_from_id
-evolution_importer_client_support_format
-evolution_importer_client_load_file
-evolution_importer_client_process_item
-evolution_importer_client_get_error
-
-
-EVOLUTION_TYPE_IMPORTER_CLIENT
-EVOLUTION_IMPORTER_CLIENT
-EVOLUTION_IMPORTER_CLIENT_CLASS
-EVOLUTION_IS_IMPORTER_CLIENT
-EVOLUTION_IS_IMPORTER_CLIENT_CLASS
-evolution_importer_client_get_type
-
-
-EvolutionImporterClient
-
-

diff --git a/doc/devel/importer/evolution-shell-importer.args b/doc/devel/importer/evolution-shell-importer.args
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/doc/devel/importer/evolution-shell-importer.heirarchy b/doc/devel/importer/evolution-shell-importer.heirarchy
deleted file mode 100644
index 78e430d311..0000000000
--- a/doc/devel/importer/evolution-shell-importer.heirarchy
+++ /dev/null
@@ -1,5 +0,0 @@
-GtkObject
-  BonoboObject
-    EvolutionImporter
-  BonoboObjectClient
-    EvolutionImporterClient
diff --git a/doc/devel/importer/evolution-shell-importer.hierarchy b/doc/devel/importer/evolution-shell-importer.hierarchy
deleted file mode 100644
index 5f1b55c709..0000000000
--- a/doc/devel/importer/evolution-shell-importer.hierarchy
+++ /dev/null
@@ -1,14 +0,0 @@
-GtkObject
-  GtkWidget
-    GtkRange
-      GtkScale
-    GtkContainer
-      GtkBin
-        GtkButton
-          GtkToggleButton
-            GtkCheckButton
-  BonoboObject
-    EvolutionImporter
-    Handle to remote Bonobo::Unknown
-      EvolutionImporterClient
-    EvolutionImporterListener
diff --git a/doc/devel/importer/evolution-shell-importer.types b/doc/devel/importer/evolution-shell-importer.types
deleted file mode 100644
index 9dcdf5f0f1..0000000000
--- a/doc/devel/importer/evolution-shell-importer.types
+++ /dev/null
@@ -1,9 +0,0 @@
-#include 
-#include 
-#include 
-#include 
-#include 
-
-evolution_importer_get_type
-evolution_importer_client_get_type
-evolution_importer_listener_get_type
diff --git a/doc/devel/importer/private-reference.sgml b/doc/devel/importer/private-reference.sgml
deleted file mode 100644
index d28c7b8591..0000000000
--- a/doc/devel/importer/private-reference.sgml
+++ /dev/null
@@ -1,21 +0,0 @@
-  
-    Importer Private API Reference
-
-    
-      
-	This part presents the class and function reference for the
-	private APIs of the different components of the &Evolution;
-	Import Framework.
-      
-    
-
-    &EvolutionImporterListener;
-    &EvolutionImporterClient;
-  
-
-
diff --git a/doc/devel/importer/public-reference.sgml b/doc/devel/importer/public-reference.sgml
deleted file mode 100644
index ba99c9b309..0000000000
--- a/doc/devel/importer/public-reference.sgml
+++ /dev/null
@@ -1,20 +0,0 @@
-  
-    Importer Public API Reference
-
-    
-      
-	This part presents the class and function reference for the
-	public APIs of the different components of the &Evolution;
-	Import Framework.
-      
-    
-
-    &EvolutionImporter;
-  
-
-
diff --git a/doc/devel/importer/tmpl/evolution-importer-client.sgml b/doc/devel/importer/tmpl/evolution-importer-client.sgml
deleted file mode 100644
index 8122e4fb2d..0000000000
--- a/doc/devel/importer/tmpl/evolution-importer-client.sgml
+++ /dev/null
@@ -1,83 +0,0 @@
-
-EvolutionImporterClient
-
-
-A #GtkObject based client to simplify use of a GNOME_Evolution_Importer object.
-
-
-
-This #GtkObject provides a convience wrapper to the GNOME_Evolution_Importer object, providing error checking and hiding all the CORBA internals from the user.
-
-
-
-
-
-
-
-
-
-Casts a #GtkObject into an #EvolutionImporterClient
-
-
-@obj: A #GtkObject
-
-
-
-
-
-
-
-@objref: 
-@Returns: 
-
-
-
-
-
-
-
-@id: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@filename: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@filename: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@listener: 
-
-@callback: 
-@closure: 
-
-
-
-
-
-
-
-@client: 
-@Returns: 
-
-
diff --git a/doc/devel/importer/tmpl/evolution-importer.sgml b/doc/devel/importer/tmpl/evolution-importer.sgml
deleted file mode 100644
index 8d8351aed2..0000000000
--- a/doc/devel/importer/tmpl/evolution-importer.sgml
+++ /dev/null
@@ -1,86 +0,0 @@
-
-EvolutionImporter
-
-
-A #BonoboObject that implements the GNOME/Evolution/Importer interface.
-
-
-
-A #BonoboObject wrapper around the GNOME/Evolution/Importer interface, providing error checking and reference counting, hiding the CORBA internals from the user and providing a simple way to create a GNOME_Evolution_Importer object.
-
-
-
-
-
-
-
-
-
-Casts a #GtkObject into an #EvolutionImporter.
-
-
-@obj: A #GtkObject.
-
-
-
-
-The type of function that is called when the importer wishes to find out if the importing component can support the file given in @filename.
-
-
-@importer: The #EvolutionImporter.
-@filename: The filename of the file to check.
-@closure: The data passed into evolution_importer_new ().
-@Returns: A #gboolean. TRUE if the importing component can import the file, FALSE otherwise.
-
-
-
-
-The type of function that is called when the importer wishes the importing component to load the file given in @filename, and initialise itself.
-
-
-@importer: The #EvolutionImporter.
-@filename: The filename of the file to load.
-@closure: The data passed into evolution_importer_new ().
-@Returns: A #gboolean. TRUE if the load and initialisation was successful, FALSE otherwise.
-
-
-
-
-The type of function that is called when the importer wants the importing component to process the next item (or items) in a file.
-
-
-@importer: The #EvolutionImporter
-@listener: A GNOME_Evolution_Importer_Listener CORBA object.
-@closure: The data passed into evolution_importer_new ().
-@ev: A #CORBA_Environment for returning any CORBA exceptions.
-
-
-
-
-The type of function that is called when the importer wants to get a string version of an error. Not all importing components support this function.
-
-
-@importer: The #EvolutionImporter.
-@closure: The data passed to evolution_importer_new ().
-@Returns: A string representation of the error, or NULL if there was no error, or the importing component does not support the getError method.
-
-
-
-
-
-
-
-
-
-
-
-
-
-@support_format_fn: 
-@load_file_fn: 
-@process_item_fn: 
-@get_error_fn: 
-@closure: 
-@Returns: 
-
-
diff --git a/doc/devel/importer/tmpl/evolution-shell-importer-unused.sgml b/doc/devel/importer/tmpl/evolution-shell-importer-unused.sgml
deleted file mode 100644
index 7a9a98034b..0000000000
--- a/doc/devel/importer/tmpl/evolution-shell-importer-unused.sgml
+++ /dev/null
@@ -1,10 +0,0 @@
-
-
-
-
-
-@client: 
-@result: 
-@more_items: 
-@data: 
-
diff --git a/doc/devel/preface.sgml b/doc/devel/preface.sgml
deleted file mode 100644
index fdaa824a8b..0000000000
--- a/doc/devel/preface.sgml
+++ /dev/null
@@ -1,113 +0,0 @@
-  
-    Introduction
-
-    
-      This is the &Evolution; Developer's Guide or programming guide
-      for the &Evolution; groupware suite.  If you are a programmer
-      and you wish to use &Evolution;'s functionality from your own
-      applications or if you wish to modify the &Evolution; core code,
-      you should read this guide.
-    
-
-    
-      If you are an end-user of &Evolution; you do not need to read
-      this guide; please read the &Evolution; User's Guide instead.
-    
-
-    
-      This guide contains the information you need to know to do the
-      following:
-
-      
-	
-	  
-	    Write applications that use &Evolution;'s data
-	    repositories via the &Wombat; personal information server.
-	    Examples of this would be a GNOME
-	    Panel applet that displays today's
-	    appointments, or a telephone dialer application that uses
-	    the contents of the &Evolution; Addressbook.
-	  
-	
-
-	
-	  
-	    Write applications that use the &Camel; mail library.
-	    This includes extending &Evolution;'s own mail component
-	    to perform additional functions.
-	  
-	
-
-	
-	  
-	    Write new components for the &Evolution; Shell.  Instead
-	    of writing a stand-alone application, you can provide your
-	    users with the benefit of having integrated views of their
-	    data from within Evolution.
-	  
-	
-
-	
-	  
-	    Write new modules for the &Evolution; Executive Summary.
-	    This allows you to present commonly-accessed information
-	    in a convenient fashion directly in the &Evolution; Shell.
-	  
-	
-
-	
-	  
-	    Modify the core &Evolution; code to add new features or
-	    change its architecture.
-	  
-	
-      
-    
-
-    
-      Organization of this Guide
-
-      
-	This guide is organized in two big sections.  The first is a
-	programming guide, which consists of one part for each one of
-	&Evolution;'s components:  there are separate parts for the
-	calendar, the addressbook, the mailer, the executive summary,
-	and the shell.  Each part gives a description of the
-	architecture of its corresponding component, and also gives
-	information about the component's internal architecture and
-	some implementation details.
-      
-
-      
-	The second section of this guide is a reference guide for
-	&Evolution;'s programming interfaces.  We have separated these
-	into public and private interfaces.  The public ones are those
-	that most people will need to use when writing extensions or
-	third-party components; the private interfaces are those used
-	internally in &Evolution;.  Even if you do not intend to
-	modify the &Evolution; core code, it may be useful to know a
-	bit about the way it is organized internally.
-      
-
-      
-	&Evolution; is free software, and we want you as a programmer
-	to make the most of it.  We have provided many useful
-	interfaces that you can use in your own applications.  Still,
-	we want you to view &Evolution; as a framework for building
-	groupware applications, and this may occasionally involve
-	making changes to its core code.  We want you to learn from
-	&Evolution;'s design because we think it marks an important
-	milestone in the development of large-scale free software
-	applications.  We want you to modify it as you see fit.  Free
-	software gives you this freedom, and we want the whole world
-	to benefit from it.
-      
-    
-  
-
-
diff --git a/doc/devel/reference.sgml b/doc/devel/reference.sgml
deleted file mode 100644
index b0c81de77f..0000000000
--- a/doc/devel/reference.sgml
+++ /dev/null
@@ -1,49 +0,0 @@
-  
-    &Evolution; API Reference
-
-    
-      
-	This part presents the class and function reference for the
-	different libraries and interfaces that &Evolution; provides.
-	Classes are described together with their methods; individual
-	functions are grouped by functional group.
-      
-
-      
-	&Evolution; provides two kinds of interfaces, public and
-	private.  The public interfaces are those designed to be used
-	from third-party applications or components; if you wanted to
-	write an application that uses &Evolution;'s data repositories
-	to display data in a particular way, you would use the public
-	interfaces.  The private interfaces are those used inside
-	&Evolution; itself; these are generally not interesting unless
-	you intend to make modifications to the &Evolution; code base.
-      
-
-      
-	While the public and private interfaces are described in
-	separate reference sections, we have decided to put them
-	together in the same book, this guide, because we want to
-	encourage you to regard &Evolution; as something more than a
-	black box that stores and dispatches personal information.  We
-	want you to make modifications to the &Evolution; core if
-	these would allow you to present or store your data in better
-	ways.  &Evolution; is free software; we want you to learn from
-	its design and implementation details so that you can make it
-	even better for the whole world to use.
-      
-    
-
-    &calendar-public-reference;
-    &importer-public-reference;
-    &evolution-services-public-reference;
-    &importer-private-reference;
-    &evolution-services-private-reference;
-  
-
-
diff --git a/doc/white-papers/calendar/calendar.sgml b/doc/white-papers/calendar/calendar.sgml
deleted file mode 100644
index 2cb3132e2b..0000000000
--- a/doc/white-papers/calendar/calendar.sgml
+++ /dev/null
@@ -1,209 +0,0 @@
-Evolution">
-CUA">
-PCS">
-Bonobo">
-CORBA">
-GTK+">
-]>
-
-

-
-  
-    &Evolution; Calendaring Framework
-
-    
-      
-	Federico
-	Mena Quintero
-	
-	  

-	    federico@helixcode.com
-	  

-	
-      
-    
-
-    
-      2000
-      Helix Code, Inc.
-    
-
-    
-      
-	The &Evolution; groupware suite provides a framework for
-	developing calendaring applications, as well as a graphical
-	calendar client and a personal calendar server.  This white
-	paper describes the architecture of the &Evolution;
-	calendaring framework.
-      
-    
-  
-
-  
-
-  
-    Introduction
-
-    
-      Calendaring is an important part of a groupware suite.  A
-      calendaring framework will allow a user to keep a personal
-      calendar and have several applications use it.  Such
-      applications could be a graphical calendar client that the user
-      employs to schedule appointments and keep track of his time, a
-      Palm Pilot synchronization client, or
-      a simple alarm or reminder utility.  A comprehensive calendaring
-      framework will also allow multiple users to schedule
-      appointments between each other; for example, a project director
-      may want to schedule a weekly meeting with the rest of the
-      project members, or a person who owns a large house may want to
-      schedule a big party with his friends.  The attendees will then
-      want to reply with messages such as, “I will
-      attend”, or “I will attend only if the proposed time
-      is changed”.
-    
-
-    
-      The &Evolution; groupware suite provides a framework for
-      developing calendaring applications, as well as a graphical
-      calendar client or calendar user agent (&CUA;) and a personal
-      calendar server (&PCS;).
-    
-
-    
-      The following sections explain the basic calendaring framework,
-      the functions of the calendar user agent and the personal
-      calendar server, and the relationship between the two.
-    
-  
-
-  
-
-  
-    Personal Calendar Server
-
-    
-      The personal calendar server (&PCS;) provides centralized
-      management and storage of a user's personal calendar.  Multiple
-      clients can connect to the &PCS; simultaneously to query and
-      modify the user's calendar in a synchronized fashion.  The main
-      features of the &PCS; are as follows:
-    
-
-    
-      Storage
-
-      
-	The &PCS; is responsible for loading and saving calendars.
-	Centralizing the loading and saving functionality allows
-	multiple clients to use the same calendar at the same time
-	without having to worry about each other.
-      
-    
-
-    
-      Basic Queries
-
-      
-	The &PCS; provides functions to do basic queries on a
-	calendar, for example, a client can ask the server for a list
-	of all the appointments in the calendar, or for all the data
-	for a specific appointment.
-      
-    
-
-    
-      Recurrence and Alarm Queries
-
-      
-	Clients can ask the &PCS; for a list of the appointments that
-	occur within a specified time range; for example a graphical
-	client that has a per-week view could ask the &PCS; for all
-	the appointments that occur in a particular week.  This
-	includes multiple occurrences of a single recurring event; for
-	example, the object for “a 1-hour meeting that occurs on
-	every Tuesday and Thursday” is represented inside the
-	&PCS; as a single event with a recurrence rule.  Similarly,
-	clients can ask the &PCS; for a list of events that have
-	alarms that trigger within a specified time range.
-      
-    
-
-    
-      Notification of Changes
-
-      
-	This is the most important function of the &PCS;, as it allows
-	multiple calendar clients to maintain a unified view of the
-	calendar between the server and themselves.  When a client
-	asks the &PCS; to modify or remove an event, the &PCS;
-	notifies all the clients that are connected to it about the
-	change.  The policy is that “the server is always
-	right”; clients can act as dumb views onto the
-	calendar's data and they will be notified by the &PCS; when
-	something changes.
-      
-    
-  
-
-  
-
-  
-    Calendar User Agent
-
-    
-      A calendar user agent (&CUA;) is a program that lets a user
-      manipulate a calendar.  &Evolution; provides an attractive,
-      graphical calendar client that communicates with the &Evolution;
-      personal calendar server.
-    
-
-    
-      The &Evolution; calendar client just provides a view onto the
-      data that is stored and managed by the personal calendar server.
-      The calendar client does not perform direct manipulations on a
-      calendar's data; instead it offloads those requests to the
-      calendar server, which takes care of making the appropriate
-      modifications in the calendar and then notifies all the clients
-      about the changes.
-    
-  
-
-  
-
-  
-    Calendar Client Library
-
-    
-      Communication between the personal calendar server and calendar
-      clients is defined by a set of &Bonobo; &CORBA; interfaces.
-      Clients can be written by implementing the client-side
-      Listener interface, which defines the
-      notification callbacks that the PCS uses to inform clients about
-      changes to the calendar.
-    
-
-    
-      As a convenience for >K; programmers, &Evolution; also
-      includes a library which provides a
-      CalClient class which can be used for
-      communication with the personal calendar server.  Objects of
-      this class automatically contact the PCS when they are created.
-      CalClient provides functions to request
-      changes in the calendar, and it also emits signals when it gets
-      notification about changes from the PCS.  This makes it easy and
-      convenient to write calendar clients for &Evolution; using
-      >K;.
-    
-
-    
-      The implementation of the CalClient class
-      simply wraps the &Evolution; &CORBA; interfaces for calendaring
-      with a familiar-looking >K; object.  Calls to the
-      Listener interface get translated to
-      signal emissions from the CalClient, thus
-      shielding programmers from the details of the &CORBA;
-      interfaces.
-    
-  
-

diff --git a/doc/white-papers/mail/camel.sgml b/doc/white-papers/mail/camel.sgml
deleted file mode 100644
index a339909f54..0000000000
--- a/doc/white-papers/mail/camel.sgml
+++ /dev/null
@@ -1,339 +0,0 @@
-Evolution">
-
-]>
-
-

-
-  
-    The &Camel; Messaging Library
-
-    
-      
-	Dan
-	Winship
-	
-	  

-	    danw@helixcode.com
-	  

-	
-      
-
-      
-	Bertrand
-	Guiheneuf
-	
-	  

-	    bertrand@helixcode.com
-	  

-	
-      
-    
-
-    
-      2000
-      Helix Code, Inc.
-    
-
-  
-
-  
-    Introduction
-
-    
-      &Camel; is a generic messaging library. It is being used as the
-      back end for the mail component of &Evolution;. The name
-      "&Camel;" is an acronym; it refers to the fact that the
-      library is capable of going several days without food or water.
-      It means : Camel's Acronym Makes Everyone Laugh.
-    
-
-    
-      &Camel;'s initial design is heavily based on Sun's
-      JavaMail API. It uses the Gtk+ object
-      system, and many of its classes are direct analags of JavaMail
-      classes. Its design has also been influenced by the features of
-      IMAP, and the limitations of the standard UNIX mbox mail store,
-      which set some of the boundaries on its requirements and
-      extensibility.
-    
-
-    
-      &Camel; sees all message repositories as stores containing
-      folders. These folders in turn contain the messages the client
-      actually accesses. The use of such a unified interface allows
-      the client applications to be very extensible. &Camel; includes
-      an external provider mechanism which allows applications to
-      dynamically load and use protocols which were not available when
-      the application was initially written.
-    
-
-    
-      The abstract store/folder mechanism is a powerful and versatile
-      way of accessing messages. No particular asumptions are made on
-      the client side, thus allowing new ways of managing the
-      messages. For example, the messages stored in the folders don't
-      necessarily have to share some common physical location. The
-      folder can be a purely virtual folder, containing only
-      references to the actual messages. This is used by the "vFolder"
-      provider, which allows you select messages meeting particular
-      criteria and deal with them as a group.
-    
-
-    
-      In addition to these possibilities, &Camel; has full MIME
-      support. &Camel; MIME messages are lightweight objects
-      representing the MIME skeleton of the actual message. The data
-      contained in the subparts are never stored in memory except when
-      they are actually needed. The application, when accessing the
-      various MIME objects contained in the message (text parts,
-      attachments, embedded binary objects ...) asks &Camel; for a
-      stream that it can read data from. This scheme is particularly
-      useful with the IMAP provider. IMAP has strong MIME support
-      built-in, which allows &Camel; to download only the parts of
-      messages that it actually needs: attachments need not be
-      downloaded until they are viewed, and unnecessary
-      "multipart/alternative" parts will never be read off the server.
-    
-  
-
-  
-    Overview
-
-    
-
-    
-      To begin using &Camel;, an application first creates a
-      CamelSession object. This object is used
-      to store application defaults, and to coordinate communication
-      between providers and the application.
-    
-
-    
-      A CamelProvider is a dynamically-loadable
-      module that provides functionality associated with a specific
-      service. Examples of providers are IMAP and SMTP. Providers
-      include subclasses of the various other &Camel; classes for
-      accessing and manipulating messages.
-    
-
-    
-      CamelService is an abstract class for
-      describing a connection to a local or remote service. It
-      currently has two subclasses: CamelStore,
-      for services that store messages (such as IMAP servers and mbox
-      files), and CamelTransport, for services
-      that deliver messages (such as SMTP, or a local MTA). A provider
-      could also be both a store and a transport, as in the case of
-      NNTP.
-    
-
-    
-      A CamelStore contains some number of
-      CamelFolder objects, which in turn
-      contain messages. A CamelFolder provides
-      a CamelFolderSummary object, which
-      includes details about the subject, date, and sender of each
-      message in the folder. The folder also includes the messages
-      themselves, as subclasses of CamelMedium.
-    
-
-    
-      Email messages are represented by the
-      CamelMimeMessage class, a subclass of
-      CamelMedium. This class includes
-      operations for accessing RFC822 and MIME headers, accessing
-      subparts of MIME messages, encoding and decoding Base64 and
-      Quoted-Printable, etc.
-    
-
-    
-      CamelTransport includes methods for
-      delivering messages. While the abstract
-      CamelTransport::send method takes a
-      CamelMedium, its subclasses may only be
-      able to deliver messages of specific
-      CamelMedium subclasses. For instance,
-      CamelSendmailTransport requires a
-      CamelMimeMessage, because it needs a
-      message that includes a "To:" header. A hypothetical
-      CamelNNTPTransport would need a
-      CamelNewsMessage, which would have a
-      "Newsgroups:" header.
-    
-
-    
-      The content of messages are referred to using
-      CamelStream and its subclasses. In the
-      case of an mbox-based store, the
-      CamelStream would abstract the operation
-      of reading the correct section of the mbox file. For IMAP,
-      reading off the CamelStream might result
-      in commands being issued to the remote IMAP server and data
-      being read off a socket.
-    
-
-    
-      The final major class in &Camel; is
-      CamelException, which is used to
-      propagate information about errors. Many methods take a
-      CamelException as an argument, which the
-      caller can then check if an error occurs. It includes both a
-      numeric error code which can be interpreted by the program, and
-      a text error message that can be displayed to the user.
-    
-  
-
-  
-    Major Subcomponents
-
-    
-      The Message Store
-
-      
-        A CamelStore inherits the ability to
-        connect and authenticate to a service from its parent class,
-        CamelService. It then adds the ability
-        to retrieve folders. A store must contain at least one folder,
-        which can be retrieved with
-        CamelStore::get_default_folder. There are
-        also methods to retrieve the "top-level" folder (for
-        hieararchical stores), and to retrieve an arbitrary folder by
-        name.
-      
-
-      
-        All CamelFolders must implement certain
-        core operations, most notably generating a summary and
-        retrieving and deleting messages. A
-        CamelFolder must assign a permanently
-        unique identifier to each message it contains. Messages can
-        then be retrieved via
-        CamelFolder::get_message_by_uid. Alternately,
-        within a single mail-reading session, messages can be referred
-        to by their linear position within the store using
-        CamelFolder::get_message_by_number.
-      
-
-      
-        Folders must also implement the
-        get_parent_folder and
-        list_subfolders methods. For stores that
-        don't allow multiple folders, they would return NULL and an
-        empty list, respectively. Stores that do allow multiple
-        folders will also define methods for creating and deleting
-        folders, and for moving messages between them (assuming the
-        folders are writable).
-      
-
-      
-        Folders that support searching can define the
-        search_by_expression method. For mbox
-        folders, this is implemented by indexing the messages with the
-        ibex library and using that to search them later. For IMAP
-        folders, this uses the IMAP SEARCH command. Other folder types
-        might not be able to implement this functionality, in which
-        case users would not be able to do full-content searches on
-        them.
-      
-    
-
-    
-      Messages
-
-      
-        As mentioned before, messages are represented by subclasses of
-        CamelMedium.
-        CamelMedium itself is a subclass of
-        CamelDataWrapper, a generic class for
-        connecting a typed data source to a data sink.
-        CamelMedium adds the concept of message
-        headers versus message body.
-        (CamelDataWrapper has one other
-        important subclass, CamelMultipart,
-        which is used to provide separate access to the multiple
-        independent parts of a multipart MIME type.)
-        CamelMedium's subclasses provide more
-        specialized handling of various headers:
-        CamelMimePart adds special handling for
-        the &ldquot;Content-*&rdquot; headers in MIME messages, and
-        its subclass CamelMimeMessage adds
-        handling for the RFC822 headers.
-      
-
-      
-
-      
-        Consider a message with two parts: a text part (in both plain
-        text and HTML), and an attached image:
-
-	
-
-	  From: Dan Winship <danw@helixcode.com>
-	  To: Matt Loper <matt@helixcode.com>
-	  Subject: the Camel white paper
-	  MIME-Version: 1.0
-	  Content-Type: multipart/mixed;
-		boundary="jhTYrnsRrdhDFGa"
-
-	  This is a multi-part message in MIME format.
-	  --jhTYrnsRrdhDFGa
-	  Content-Type: multipart/alternative;
-		boundary="sFSenbAFDSgDfg"
-
-	  --sFSenbAFDSgDfg
-	  Content-Type: text/plain
-
-	  Hey, Matt
-
-	  Check out this graphic...
-
-	  -- Dan
-
-	  --sFSenbAFDSgDfg
-	  Content-Type: text/html
-
-	  Hey, Matt<br>
-	  <br>
-	  Check out this graphic...<br>
-	  <br>
-	  -- Dan<br>
-	  <br>
-	  --sFSenbAFDSgDfg--
-
-	  --jhTYrnsRrdhDFGa
-	  Content-Type: image/png
-	  Content-Transfer-Encoding: base64
-
-	  F4JLw0ORrkRa8AwAMQJLAaI3UDIGsco9RAaB92...
-	  --jhTYrnsRrdhDFGa--
-	
-
-	
-	  In &Camel;, this would be represented as follows:
-	
-
-        
-      
-
-      
-        Streams
-
-	
-	  Streams are a generic data transport layer. Two basic stream
-	  classes are CamelStreamFs, for
-	  reading and writing files, and
-	  CamelStreamMem, for reading from and
-	  writing to objects that are already in memory.
-	
-
-	
-	  Streams can also be chained together. So a CamelMimePart
-	  containing base64-encoded data can filter its output through
-	  a CamelStreamB64. Other parts of the application that want
-	  to read its data will never need to even realize that the
-	  original data was encoded.
-	
-      
-
-

diff --git a/doc/white-papers/mail/ibex.sgml b/doc/white-papers/mail/ibex.sgml
deleted file mode 100644
index dcb8f5ca4b..0000000000
--- a/doc/white-papers/mail/ibex.sgml
+++ /dev/null
@@ -1,158 +0,0 @@
-Evolution">
-
-
-]>
-
-

-
-  
-    Ibex: an Indexing System
-
-    
-      
-	Dan
-	Winship
-	
-	  

-	    danw@helixcode.com
-	  

-	
-      
-    
-
-    
-      2000
-      Helix Code, Inc.
-    
-
-  
-
-  
-    Introduction
-
-    
-      &Ibex; is a library for text indexing. It is being used by
-      &Camel; to allow it to quickly search locally-stored messages,
-      either because the user is looking for a specific piece of text,
-      or because the application is contructing a vFolder or filtering
-      incoming mail.
-    
-  
-
-  
-    Design Goals and Requirements for Ibex
-
-    
-      The design of &Ibex; is based on a number of requirements.
-
-    
-      
-        
-	  First, obviously, it must be fast. In particular, searching
-	  the index must be appreciably faster than searching through
-	  the messages themselves, and constructing and maintaining
-	  the index must not take a noticeable amount of time.
-	
-      
-
-      
-        
-	  The indexes must not take up too much space. Many users have
-	  limited filesystem quotas on the systems where they read
-	  their mail, and even users who read mail on private machines
-	  have to worry about running out of space on their disks. The
-	  indexes should be able to do their job without taking up so
-	  much space that the user decides he would be better off
-	  without them.
-	
-
-	
-	  Another aspect of this problem is that the system as a whole
-	  must be clever about what it does and does not index:
-	  accidentally indexing a "text" mail message containing
-	  uuencoded, BinHexed, or PGP-encrypted data will drastically
-	  affect the size of the index file. Either the caller or the
-	  indexer itself has to avoid trying to index these sorts of
-	  things.
-	
-      
-
-      
-        
-	  The indexing system must allow data to be added to the index
-	  incrementally, so that new messages can be added to the
-	  index (and deleted messages can be removed from it) without
-	  having to re-scan all existing messages.
-	
-      
-
-      
-        
-	  It must allow the calling application to explain the
-	  structure of the data however it wants to, rather than
-	  requiring that the unit of indexing be individual files.
-	  This way, &Camel; can index a single mbox-format file and
-	  treat it as multiple messages.
-	
-      
-
-      
-        
-	  It must support non-ASCII text, given that many people send
-	  and receive non-English email, and even people who only
-	  speak English may receive email from people whose names
-	  cannot be written in the US-ASCII character set.
-	
-      
-    
-
-    
-      While there are a number of existing indexing systems, none of
-      them met all (or even most) of our requirements.
-    
-  
-
-  
-    The Implementation
-
-    
-      &Ibex; is still young, and many of the details of the current
-      implementation are not yet finalized.
-    
-
-    
-      With the current index file format, 13 megabytes of Info files
-      can be indexed into a 371 kilobyte index file—a bit under
-      3% of the original size. This is reasonable, but making it
-      smaller would be nice. (The file format includes some simple
-      compression, but gzip can compress an
-      index file to about half its size, so we can clearly do better.)
-    
-
-    
-      The implementation has been profiled and optimized for speed to
-      some degree. But, it has so far only been run on a 500MHz
-      Pentium III system with very fast disks, so we have no solid
-      benchmarks.
-    
-
-    
-      Further optimization (of both the file format and the in-memory
-      data structures) awaits seeing how the library is most easily
-      used by &Evolution;: if the indexes are likely to be kept in
-      memory for long periods of time, the in-memory data structures
-      need to be kept small, but the reading and writing operations
-      can be slow. On the other hand, if the indexes will only be
-      opened when they are needed, reading and writing must be fast,
-      and memory usage is less critical.
-    
-
-    
-      Of course, to be useful for other applications that have
-      indexing needs, the library should provide several options, so
-      that each application can use the library in the way that is
-      most suited for its needs.
-    
-  
-

diff --git a/doc/white-papers/widgets/e-table.sgml b/doc/white-papers/widgets/e-table.sgml
deleted file mode 100644
index 5ff4faf2ae..0000000000
--- a/doc/white-papers/widgets/e-table.sgml
+++ /dev/null
@@ -1,279 +0,0 @@
-Evolution">
-ETable">
-ETableModel">
-ETableSimple">
-ETableHeader">
-ETableSpecification">
-ETableCol">
-]>
-
-

-
-  
-    The ETable Widget
-
-    
-      
-	Chris
-	Lahey
-	
-	  

-	    clahey@helixcode.com
-	  

-	
-      
-      
-	Miguel
-	de Icaza
-	
-	  

-	    miguel@helixcode.com
-	  

-	
-      
-    
-
-    
-      2000
-      Helix Code, Inc.
-    
-
-  
-
-  
-    Introduction
-
-    
-      &ETable; is a table widget on steroids. It is intended to provide
-      all the table functionality needed throughout &Evolution;, and
-      hopefully be general purpose enough to be used in other projects.
-    
-
-    
-      &ETable; provides a lot of interactive control over the data in the
-      table.  Without any work from the programmer, &ETable; provides
-      rearrangeable columns and editable data.  When finished, &ETable; will
-      also provide, again with no programmer intervention, easy interactive
-      sorting and grouping.  
-    
-
-    
-      &ETable; gives you a great deal of functionality, flexibility, and
-      power. Most of this power is internal to the widget, but some of
-      the flexibility requires a bit of work by the programmer.
-      However, once you learn it, &ETable; is not very hard at all to
-      use.
-    
-
-    
-      &ETable;'s power comes from the fact that it is fully
-      model/view/controller based.  Various models are involved into
-      the process of rendering the information, and various views are
-      provided.  The programmer has a wide range of options: from the
-      most finely hand-tuned table to a generic all-encompasing widget
-      that takes over most of tasks.  It is up to the programmer: he
-      can use the simple to use &ETable; widget that takes care of
-      everything in a generic way, or he can use the various
-      components to roll his own tabular display.
-    
-
-    
-      &ETable; ships with a standard set of information renderers:
-      strings, bitmaps, toggle-buttons, check-boxes, and multi-line
-      strings.  But the programmer can write and implement his own
-      renderer for his information.  This means that by default
-      &ETable; provides the basic display facilities that programmers
-      required, but they offer the programmer a complete freedom to
-      incorporate new cell renderers.
-    
-    
-  
-
-  
-    ETableModel
-
-    
-      The data back end for the &ETable; is an &ETableModel;. The
-      &ETableModel is an abstract interface that acts as the
-      information repository for the various &ETable components.
-    
-    
-    
-      To use &ETable; you have to create a subclass of the abstract
-      &ETableModel; class.  However, to save you the work of defining
-      a new GtkClass every time you use
-      &ETable, there is a predefined subclass of &ETableModel; called
-      &ETableSimple; which simply takes a list of function callbacks
-      to perform the various operations.
-    
-
-  
-    
-  
-    Columns
-
-    
-      There are two different meanings to the word "column". The first
-      is the model column (defined by the &ETableCol: object). A model
-      column describes how it maps to the column in the &ETableModel;
-      as well as containing information about its properties (name,
-      resizability, resize dimensions, and a renderer for this
-      specific columns). 
-    
-
-    
-      &ETable; distinguishes between a model column index, and a view
-      column index.  The former reflects the column in which the data
-      is stored in the &ETableModel;  The later represents the actual
-      location at which the column is being displayed in the screen.
-    
-
-    
-      Each view column index corresponds to a specific model column,
-      though a model column may have any number of view columns
-      associated with it (including zero).  For example the same
-      column might be rendered twice, or the data from one column
-      could be used to display different bits of information
-    
-
-    
-      The view column does not necessarily depend on only one model
-      column. In some cases, the view column renderer can be given a
-      reference to another model column to get extra information about
-      its display. For example, a mail program could display deleted
-      messages with a line through them by creating a model column
-      with no corresponding view column that told whether or not the
-      message is deleted, and then having the text column
-      strikethrough the display if the invisible column had a value
-      corresponding to "deleted".
-    
-
-    
-      The view column also specifies a few other pieces of
-      information. One piece of information is the renderer. &ETable;
-      provides a number of renderers to choose from, or you can write
-      your own. Currently, there are renderers for text, image sets,
-      and checkboxes.
-    
-
-    
-      The view column also includes information about the header.
-      There are two types of headers: text, and pixbuf. The first
-      allows you to specify a string which is rendered in the header.
-      The second allows you to specify an image to copy into the
-      header.
-    
-  
-
-  
-    Header
-
-    
-      The &ETableHeader; represents the header information for the
-      table. The &ETableHeader; is used in two different ways. The
-      first is the in the full_header
-      element of an &ETable;. This is the list of possible columns in
-      the view. You add each of your columns to this &ETableHeader;
-      and then pass it into the &ETable;.
-    
-
-    
-      The second use is completely internal. &ETable; uses another
-      &ETableHeader; to store the actual displayed columns. Many of
-      the &ETableHeader; functions are for this purpose. The only
-      functions that users of the library should need to use are
-      e_table_header_new and
-      e_table_header_add_col.
-    
-  
-
-  
-    Layout Specification
-
-    
-      &ETable; uses an &ETableSpecification; to layout the columns of
-      the widget. The &ETableSpecification; is specified as XML data
-      passed into the &ETable; as a string.
-    
-
-    
-      The most powerful part of the &ETableSpecification; is that when
-      finished, &ETable; will allow you to get a copy of an
-      &ETableSpecification; that describes the current view of the
-      tree. This allows the developer to save the current view so that
-      next time the user opens this table, they find it in exactly the
-      state that they left it.
-    
-
-    
-      The XML specification allows for a number of things. First, it
-      allows you to pick a set of default columns to be shown. Thus,
-      even if you had hundreds of pieces of data, you could choose to
-      only display a few that fit on the screen by default.
-    
-
-    
-      The second major thing that the &ETableSpecification; allows you
-      to specify is the column grouping and sorting. &ETable; has a
-      powerful mechanism for allowing the user to choose columns to
-      group by, thus allowing multiple columns of sorting, as well as
-      visual grouping of similar elements and interactive selection of
-      what data to display.
-    
-
-    
-      The grouping in &ETableSpecification; is specified as a
-      hierarchy of columns to group by. Each level of the hierarchy
-      lets you sort by a particular column, either ascending or
-      descending. All levels except the last cause the canvas to group
-      by the given column.
-    
-
-    
-      An example &ETableSpecification; follows.
-    
-
-    
-      <ETableSpecification>
-        <columns-shown frozen_columns="2">
-	  <column> 0 </column>
-	  <column> 1 </column>
-	  <column> 2 </column>
-	  <column> 3 </column>
-	  <column> 4 </column>
-	</columns-shown>
-	<grouping>
-	  <group column="3" ascending="1">
-	    <group column="4" ascending="0">
-	      <leaf column="2" ascending="1"/>
-	    </group>
-	  </group>
-	</grouping>
-      </ETableSpecification>
-    
-
-    
-      This example has 5 columns which are initially in order. It has
-      2 levels of grouping. The first is grouped by the 4th column
-      (all indexes are 0 based) and sorts those groups in ascending
-      order. Inside those groups, the data is grouped by the fifth
-      column and sorted in descending order of the fifth column.
-      Finally, the data in those groups is sorted by the third column
-      in ascending order. Due to the "frozen_columns" attribute on the
-      columns-shown element, the user will not be
-      able to rearrange the first two columns. They will always be the
-      first two.
-    
-  
-
-  
-    Conclusion
-
-    
-      All in all, &ETable; is a very powerful widget. Once you learn
-      to use it, you have access to a vast amount of power requiring a
-      comparatively small amount of work.
-    
-  
-

-- 
cgit v1.2.3