Sylpheed FAQ <author>Paul Kater (paul@nlpagan.net) and Jens Oberender (j.obi@troja.net) Maintained by François Barrière (barriere.francois@libertysurf.fr) <abstract> Sylpheed FAQ (for version 0.8.0) </abstract> <toc> Copyright (c) 2002 <tt>The sylpheed documentation team</tt>. 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, with no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the <ref id="GNU Free Documentation License" name="section"> entitled "GNU Free Documentation License". The list of the members of <tt>The sylpheed documentation team</tt> is detailed in the <ref id="The Sylpheed documentation team" name="appendix">. In this FAQ, the question starting with the <tt>C</tt> letter (instead of the usual <tt>Q</tt>) concern features that are only present in the <tt>claws</tt> branch of Sylpheed. This FAQ consists of the following sections: <sect> Sylpheed FAQ - General information <sect1> Q01 Are there FAQ's in other languages? A. Yes. Here are links to several translations: <itemize> <item><url url="http://sylpheeddoc.sourceforge.net/fr/faq/faq.html" name="SYLPHEED FAQ in French"> Translated by Olivier Delhomme. <item><url url="http://sylpheeddoc.sourceforge.net/de/faq/faq.html" name="SYLPHEED FAQ in German"> Translated by Nicolas Kaiser. <item><url url="http://sylpheeddoc.sourceforge.net/es/faq/faq.html" name="SYLPHEED FAQ in Spanish"> Translated by Ricardo Mones Lastra.  <item><url url="http://silver.lacmhacarh.gr.jp/sylpheed/sylpheedfaq-ja.htm" name="SYLPHEED FAQ in Japanese"> courtesy of WAKAI "SilverRain" Kazunao. <item><url url="http://www.cs.uoi.gr/~csst9910/el_sylfaq.html" name="SYLPHEED FAQ in Greek"> courtesy of Theofilos Intzoglou. <item><url url="http://hem.passagen.se/webplats/sylpheed-faq-se.html" name="Swedish FAQ">, courtesy of Mattias Stergren. <item><url url="http://sylpheed.goodhorse.idv.tw/faq/sylpheed-faq.html" name="Traditional Chinese FAQ">, courtesy of Franklin. </itemize> You can download this FAQ from <url url="http://sylpheeddoc.sf.net" name="http://sylpheeddoc.sf.net"> </sect1> <sect1> Q02 What is Sylpheed? A. Sylpheed is an e-mail client (& news reader) based on GTK+, running on the X Window System, and aiming for <itemize> <item>Quick response <item>Graceful, and sophisticated interface <item>Easy configuration, intuitive operation <item>Abundant features </itemize> </sect1> <sect1> Q03 Where can I get Sylpheed? A. You can download it from <tt><url url="http://sylpheed.good-day.net" name="sylpheed.good-day.net"></tt> There are links to download the tarball sources, and also links to sites where you can download RPM's (for Redhat and Mandrake), DEB packages for Debian, and installations for Solaris and FreeBSD. </sect1> <sect1> Q04 Who writes Sylpheed? A. Hiroyuki Yamamoto (<tt>hiro-y@kcn.ne.jp</tt>) </sect1> <sect1> Q05 What does the name Sylpheed mean? A. It means 'light weight', like air. This comes from the name of the wind spirits, the Sylphs. </sect1> <sect1> Q06 How does Sylpheed store mails? A. Mails are stored in the MH mailfile format as used by MH and EMH. Maildir and mbox format are not (yet) supported, although it is possible to import an mbox file into a Sylpheed mailbox. </sect1> <sect1> Q07 Why does the auto collection of mail not work? A. Autocollection works since version 0.5.1. If you need it or want it, you should upgrade. </sect1> <sect1> Q08 Does Sylpheed have mail filtering? A. Yes. You can find it in Configuration -> filtering tab. Please note that filtering is not yet implemented for IMAP accounts. </sect1> <sect1> Q09 Can Sylpheed handle IMAP mail? A. Yes. As of version 0.4.99 IMAP is supported. </sect1> <sect1> Q10 Can Sylpheed handle local unix mailboxes? A. Yes. </sect1> <sect1> Q11 Can Sylpheed handle IPv6? A. Yes, IPv6 is fully supported in Sylpheed. </sect1> <sect1> Q12 Does Sylpheed support encryption like GPG? A. Yes. GPG is implemented and works fine. For activating it in Sylpheed, see Q14 in the Installation section. </sect1> <sect1> Q13 How does Sylpheed check for MIME types? A. Sylpheed uses the Mutt type of mime checking. </sect1> <sect1> Q14 Does Sylpheed allow me to write HTML styled messages? A. No. A discussion has gone around over this topic, and the outcome was that HTML mail is not wanted. If you really need to send HTML, you can of course attach a webpage to an e-mail. Several patches have been made to facilitate better HTML handling in Sylpheed. You can find these patches at the Sylpheed Patch Page (see further down in the document). </sect1> <sect1> Q15 Does Sylpheed have name completion in the address fields? A. Yes. When you search for a name that starts with "<tt>don</tt>", type "<tt>don</tt>" (without the quotes) and press the TAB key. This will show you the correct name (when only one "don" exists in your addressbook. Otherwise a dropdown list appears, which allows you to select the name you want. E.g. Donald Duck, Don Johnson. But also e-mail addresses starting with "<tt>don</tt>" will appear in the list (like "<tt>don.giovanni@maffia.org</tt>"). </sect1> <sect1> Q16 Fine, but when I hit the TAB key I get an error message. A. When you want to use name completion, make sure that there are names in your address book. If there are no names, even Sylpheed has a hard time completing something. </sect1> <sect1> Q17 Why is Sylpheed so fast? A. That's what it is designed for! </sect1> <sect1> Q18 Where can I get the current patches for Sylpheed? A. The Sylpheed Patch homepage: <tt><url url="http://www.thewildbeast.co.uk/sylpheed/" name="http://www.thewildbeast.co.uk/sylpheed/"></tt> (Also see section on Installation on how to install a patch) </sect1> <sect1> Q19 How can I send in patches, report bugs, talk about Sylpheed with others? A. To talk to others, you should join the Sylpheed mailing list at <tt>http://sylpheed.good-day.net</tt>. Note that there is a japanese and an english list, so pick the right one! If you have made a patch that you want the world to know of, please get in touch with the manager of the Sylpheed Patch homepage, at <tt>sylpheed@thewildbeast.co.uk</tt> </sect1> <sect1> Q20 When I send mail, the Content-Type header says the mail is in US-ASCII, even when I specified ISO-8859-1? A. If ISO-8859-1 characters (>= 0x80) are not used in the message body, Sylpheed will automatically set the charset value in the Content-Type header as US-ASCII. </sect1> <sect1> Q21 Why does it look like word wrap is not working? A. Word wrapping is a bit peculiar perhaps. You can type lines as long as you like. By the time you send or queue a mail with long lines, Sylpheed will first wrap the lines to the line length you set up, and then the mail is queued. This is more convenient than you think. Once a line is wrapped (hard line breaks are inserted in the text) and you add something in a line there, the next line will move to a separate new line, leaving one or two words from the previous line "hanging there" alone. E.g. <verb> This is a long line that is wrapped. </verb> Now you add one word in the first line: <verb> This is a very long line that is wrapped </verb> This would cause you a lot of manual reformatting to get a presentable mail again. Note: As of Sylpheed 0.8.0., active wordwrap has been implemented. You can turn it on in Common Preferences->Compose->wrap on input. </sect1> <sect1> Q22 Where can I find the latest FAQ on Sylpheed? A. Go to <url url="http://sylpheeddoc.sf.net" name="http://sylpheeddoc.sf.net"> and check out the FAQ and manual from the sylpheeddoc project. Both documents are available in multiple languages there and usually contain the latest updates. </sect1> <sect1> Q23 Can I import a mbox into Sylpheed's MH mailfolders? A. Yes, just create/select the folder you want your mails in, and select "Import mbox file" in the File menu. </sect1> <sect1> Q24 Can I use procmail to sort my mails with the MH mail handling? A. Yes. Just make sure that you add /. to the end of a rule so procmail knows you are filtering into an MH mail folder. Example: <tt>0:</tt> <tt>* ^Subject:.*sylpheed</tt> <tt> sylpheedmail/.</tt> Check man procmail for details. </sect1> <sect1> Q25 When I upgrade Sylpheed, are there things I should be aware of? A. Yes! Upgrade to 0.4.50: you should reconfigure your newsgroup settings Upgrade to 0.4.63: you should set the URL string colors from the Configuration menu. Upgrade to 0.4.65: some menu items have been moved Upgrade to 0.7.3: many keybindings have changed </sect1> <sect1> Q26 How can I quickly update the views in Sylpheed? A. Just press Alt-U or select "update" from the summary menu. </sect1> <sect1> Q27 Why can't I use gvim as external editor? A. If one wishes to use gvim as an external editor it's necessary to start it with the no-fork option -f, i.e. in the configuration dialog box you need to enter "gvim -f %s". If not the editor forks and open up a separate file and when one quits the editor the changes are lost and don't show up in the composer window. (Thanks, Ed Collins!) </sect1> <sect1> Q28 Can I quote just parts of the original message when replying? A. Yes, select the part in the textview and choose "reply". </sect1> <sect1> Q29 Can I reply without quoting at all? A. Right click on the "reply" button in the toolbar and choose "reply without quote" (also works with "forward"). Tip: You can also assign hotkeys to these menu entries. </sect1> <sect1> C30 How does selective download work? A. There are two ways using it. 1. Manually: Open "Tools/Selective download" and choose "Fetch" to retrieve the mail headers. Afterwards, select the mails to delete and pres the remove button. 2. Automatic: Create a -global- filtering rule to delete mails on server. If you then choose "Selective download", all mails that conform to this rule are marked for deletion. Note: By default, selective download only retrieves new (unread) messages. If you want to process the read mails also, you need to set "retrieve all messages". </sect1> <sect1> C31 Why are there two filter options? A. "Filter setting" is the traditional one with less options. The "Filtering" option is new in sylpheed-claws and more powerful and may replace the old option in the future. Tip: To convert your old filter rules into the new format, you can use the "filter_conv.pl" script, that can be found in "tools" subdirectory from sylphed-claws sources. </sect1> <sect1> C32 Can I use both filter options? A. No, as soon as you define a new "filtering" rule, the traditional "filter" rules are ignored. </sect1> </sect> <sect> Sylpheed FAQ - Installation and Configuration <sect1> Q01 What does it take to compile Sylpheed? A. Any POSIX compliant UNIX or similar OS eg. Linux, FreeBSD, Solaris GTK+ 1.2.6 or later A recent ANSI C compiler (gcc 2.7.2.3 should also work) Note: it is reported that Sun C will not compile Sylpheed. Optionally: <itemize> <item>Imlib or gdk-pixbuf (for built-in image view) <item>libcompface (for X-Face) <item>libjconv (for I18N) <item>GPGME (for GnuPG) <item>the equivalent of GTK+-devel and Xfree86-devel. </itemize> Otherwise ./configure will fail. </sect1> <sect1> Q02 How do I set up Sylpheed? A. When you run Sylpheed for the first time, it will ask you where you want to store your mailboxes. The default is <homedir>/Mail. You can change this to anything you like as long as it is a valid directory name. Please note: When Sylpheed is executed for the first time, it automatically creates the configuration files under $HOME/.sylpheed/, and asks you the location of mailbox. The default is $HOME/Mail. If some files which are non-MH format already exist on the directory, you will have to specify another location. </sect1> <sect1> Q03 Why did the creation of the mailbox fail? A. Sylpheed reports such an error if it can't create the default mailboxes (inbox, outbox, etc ...). This can be because <homedir>/Mail already contains files with the same names. This occurs when switching from Kmail to Sylpheed, in this case backup and remove the existing Mail directory or use another name for the Sylpheed mail directory. </sect1> <sect1> Q04 How do I set up an account? A. After loading Sylpheed for the first time, you can add an e-mail account by clicking the "Configuration" menu. Select the option "Create new account" and fill in the appropriate fields. </sect1> <sect1> Q05 How many accounts can I set up in Sylpheed? A. The number is unlimited. The limit is reached when your computer stops responding. </sect1> <sect1> Q06 Why does Sylpheed not delete my mails when I press "delete"? I set a filter, and Sylpheed does not filter. I moved a mail to a different mailbox and it did not move. A. You have to click the "execute" button. The other solution: in the configuration settings (common preferences -> interface tab) you have to check the "execute commands immediately" box. </sect1> <sect1> Q07 Can I set up special addresses/ports for my mailserver / newsserver? A. Yes, you can. In the configuration per account you can specify the exact port addresses you want to use. </sect1> <sect1> Q08 Does Sylpheed have options for threading messages? A. Yes. You can switch it on and off in the Summary Menu, just select "Thread View" or press Ctrl+T. </sect1> <sect1> Q09 Can I create multiple levels of subfolders to store mail? A. Absolutely. This is no problem. </sect1> <sect1> Q10 Why isn't Sylpheed sending my mail out? A. You need to create at least one account in order to send. (This is a wonderful gotcha on LAN installs with only a local mailbox feed). </sect1> <sect1> Q11 How do I apply a patch after downloading it? A. Copy patch to sylpheed directory Apply the patch: <tt>% patch -p0 < some.patch</tt> Or, if it's gzipped: <tt>% gzip -dc some.patch.gz | patch -p0</tt> Run <tt>./autogen.sh</tt>, remove the generated <tt>/config.cache</tt> file (unless you want to install in prefix <tt>/usr/local</tt>). Run <tt>./configure</tt> with the appropriate options and then <tt>make</tt>. (Text as found on the Sylpheed patches page.) </sect1> <sect1> Q12 How do I compile in support for compface pictures? A. You have to have a package called <tt>libcompface</tt> installed, so this is available for compiling into Sylpheed. </sect1> <sect1> Q13 How do I make my own compface image? A. The faces package contains a program called xbm2ikon script, which converts a 48x48 xbm to the format suitable for compface. Thanks to Jeff Dairiki, you can have a complete online course in this. Visit <url url="http://www.dairiki.org/xface/" name="this page"> for the details. </sect1> <sect1> Q14 How can I tell my browser/newsclient/other program to use Sylpheed as e-mail program? A. In the settings part of the program, write <tt>sylpheed --compose</tt> Specific options for typical browsers: <itemize> <item>Opera: <tt>sylpheed --compose [mailto:%t][?subject=%s] </tt></item> <item>Galeon: <tt>sylpheed --compose "mailto:%t?subject=%s"</tt></item> </itemize> </sect1> <sect1>Q15 How do I enable GPG support in Sylpheed? A. When compiling Sylpheed, make sure you add <tt>--enable-gpgme</tt> in the ./configure command. When that completes successfully, there is a "privacy" section in the Common preferences. </sect1> <sect1>Q16 Mutt does not recognize Sylpheed's MH structure A. For this to work you need to use the "touch" command in every MH folder. "touch" the file .xmhcache and Mutt should do just fine. </sect1> <sect1>Q17 Viewing a GIF file within Sylpheed causes a segmentation fault. A. In case this happens, you can easily fix that by adding the following to /etc/mime.types: <tt>image/gif gif</tt> </sect1> <sect1>Q18 How can I make Sylpheed notify me when new mail arrives? A. For this you can do several things: * Look at the Sylpheed patch page at <url url="http://www.thewildbeast.co.uk/sylpheed/" name="http://www.thewildbeast.co.uk/sylpheed/"> for a new mail patch. * Download Gkrellm or a similar program that is able to notify you of new incoming mail. Gkrellm is available at <url url="http://www.gkrellm.net" name="the Gkrellm page"> </sect1> <sect1>Q19 Can I use a spell checker with Sylpheed? A. Yes. You can use ispell for this. In Common Preferences, in the spot where you can define an alternative editor (as long as you do not use that, of course), you enter "xterm -e ispell %s". Do not enter the quotes. With this set up, you can have spell checked when writing an e-mail by hitting the "Editor" button in the compose window. Note that you can enter the xterm type of your choice, so wterm, eterm and aterm should also work, as long as they are installed on your system.</sect1> <sect1>Q20 How can I make Sylpheed send my compface image in the mails? A. In the Configuration menu, Preferences for current account, Send tab, check Add user-defined header and press Edit button. A dialog appears, add a header named "X-Face" and fill the value field with your face data. Note that if you paste the data from a terminal into the field some spurious newlines can be added, and these can mangle your face, be careful.</sect1> <sect1> Q21 I checked out the sources using cvs and cant find any configure script. A. The cvs versions are meant to be used by developers rather than "normal" users, so the source (or binary) distributions are easier to use. - Yeah, but the latest features from cvs really look sexy... You need to generate the configure script by running "autgen.sh". Be sure to have autoconf and automake packages installed for this. </sect1> <sect1> Q22 Running "autogen.sh" gives errormessages that "AM_PATH_GDK_PIXBUF" or "AM_PATH_(whatever)" is not found. A. There are some *.m4 files in the "ac/missing" directory. Try to copy them into the "ac" directory and run "autogen.sh" again. If there are still some .m4 files not found (e.g. those from Gtk), try to run <verb> % locate m4 | less </verb> or <verb> &percnt locate aclocal | less </verb> to find additional directories containing those macros. If you find e.g. a "gtk.m4" in "/opt/gnome/share/aclocal", change following line in "autogen.sh" from <verb> aclocal -I ac \ </verb> to <verb> aclocal -I ac -I /opt/gnome/share/aclocal \ </verb> and run it again. </sect1> <sect1> Q23 I dont want to compile in support for ... any longer, but after running "configure", those libraries are still used. A. Remove the "config.cache" file and run "configure" again. You should also use "make clean" to avoid undefined references. </sect1> <sect1> Q24 How can I select different applications to open with specific MIME types? A. The MIME-type->application associations are kept in /etc/mailcap. </sect1> <sect1> Q25 How can I change the suggested mimetype for attachments? A. The extension->MIME-type associations are kept in /etc/mime.types </sect1> <sect1> Q26 The folderlist is not updated after I manually moved/copied folders. A. You need to update Sylpheeds cache. Right click on the mailbox and choose "rescan folder tree". </sect1> <sect1> Q27 How can I revert original settings, e.g. for fonts, keybindings, etc.? A. Sylpheed keeps its configuration files in $HOME/.sylpheed/sylpheedrc and creates default entries, if none are found. So the easiest way is to quit sylpheed, temporarily renaming your $HOME/.sylpheed e.g. to *.bak and restarting sylpheed in order to get default entries. </sect1> <sect1> Q28 What environment variables have effect on Sylpheed? A. Here are the most common variables: <itemize> <item>HOME - location of .sylpheed (config directory) and default folder for Mailboxes. <item>LANG, <item>LC_ALL, <item>LC_CTYPE, <item>LC_MESSAGES - locale settings, e.g. language and date format. </itemize> </sect1> <sect1> Q29 Special characters (e.g. umlauts) are not displayed correctly. A. In most cases, this is caused by fonts, that use an unsuitable encoding. Standard Sylpheed currently doesnt offer all font settings in the settings window, so if you take a look into your $HOME/.sylpheedrc, you will find some more font entries in the following form: <verb> bold_font=-unknown-Helvetica-bold-r-normal-*-*-110-*-*-p-*-iso8859-1 </verb> The last two entries ("iso8859" and "1") define the encodig. You can try to use wildcards ("*") or force a specific encoding. <verb> bold_font=-unknown-Helvetica-bold-r-normal-*-*-110-*-*-p-*-*-* </verb> You should also make sure that your environment variables regarding locale settings have sensible values. </sect1> <sect1> Q30 How can I convert my old mailbox / adressbook from (some mailclient). A. In the source distribution, you can find some scripts in the "tools" subdirectory, maybe your application is supported. You can also try to export your old mailbox to MH or MBOX format. Tip: Take a look at the "harvest addresses" function from the "tools" menu, it could be a useful alternative or addition, when importing your old contacts. </sect1> <sect1> Q31 What config files are there, and what are they used for? A. Sylpheeds config files can be found in $HOME/.sylpheed. They are in plain text format and quite easy to understand, so dont fear to take a look into them using a texteditor. <itemize> <item>sylpheedrc - main configuration: nearly all options from the settings window, e.g. mailbox location, font entries, etc. <item>accountrc - settings for pop/imap/nntp accounts <item>actionsrc - user defined actions <item>customheaderrc - contains user defined header lines <item>dispheaderrc - headers to display above the mail body <item>filterrc - traditional filter settings <item>folderitemrc - folder specific settings, e.g. default outbox <item>matcherrc - new filtering and scoring settings <item>menurc - Key bindings <item>addrbook-*.xml - contents of your addressbook <item>folderlist.xml - additional folder specific settings, e.g. hiding read messages, sort order, etc. </itemize> </sect1> <sect1> Q32 What to do when printing an e-mail prints off the paper? A. You can use enscript for this. Use enscript %s to print everything on one page, or enscript -U2 %s for printing two logical pages on one physical page. </sect1> </sect> <sect> Sylpheed FAQ - Interface <sect1> Q01 How do I make Sylpheed display my language? A. You have to set some environment variables such as <tt>LANG,LC_CTYPE, LC_MESSAGES</tt> to your local language. Usually <tt>LANG</tt> (or <tt>LC_ALL</tt>) is sufficient. </sect1> <sect1> Q02 I don't like the default font. Can I change that? A. Yes. In Configuration->common preferences under the "Display" tab. </sect1> <sect1> Q03 There are too many columns in the message list!! A. In Configuration->common preferences under the "Display" tab you can press the button "Set display item of summary". That pops up a screen with all the options you can show or leave out of the message list. </sect1> <sect1> Q04 Can I use a different editor to write my mails? A. You can. In Configuration->common preferences under the "Other" tab you can define your editor of choice. Remember, if you want to use a command line editor like vi or emacs, to write the name of the shell (term, term, rxvt) with the -e parameter in front of the editor. E.g.: <tt>rxvt -e vi %s</tt> </sect1> <sect1> Q05 How to change the font size in the Sylpheed interface? A. You can set the GTK+ font by <tt>$HOME/.gtkrc</tt>, or <tt>$HOME/.gtkrc.mine</tt>, (which is included by <tt>$HOME/.gtkrc</tt>). For example: <tt>style "default" { font = "-adobe-helvetica-medium-r-normal--12-*-*-*-*-*-iso8859-1 " } widget_class "*" style "default"</tt> </sect1> <sect1> Q06 Sylpheed saves my outgoing mail (in Outbox). Can I make it stop doing that? A. In Configuration->common preferences there's a checkbox "Save sent message to outbox". Uncheck it, and it's solved. </sect1> <sect1> Q07 How can I change the key-bindings (hot-keys) in Sylpheed? A. That is very simple. Suppose you want to assign a shortcut key to a function, e.g. sending all mail out should start when you press Ctrl-Y. Click the Message' menu and move the mouse over "Send all messages". Now you press Ctrl-Y. Immediately the menu text is updated and the function is in place. Please note that a previous function that Ctrl-Y was assigned to, will no longer have a shortcut key. If you want to remove the key binding, do the same thing, but press the "delete" key on the menu-item. Then the key binding is removed. </sect1> <sect1> Q08 Can I close windows without the mouse? A. Of course!! Not all windows, but by pressing ESCape, you can close the addressbook, the window of viewing a mail-source (message->view source), the window of viewing the headers, and several others. Just give it a try and you will find all of them. </sect1> <sect1> Q09 Can I change the way the date is displayed in the message summary? A. As of 0.4.65 you can. The options are: %y = year in numbers %m = month in number %d = day in numbers %c = date/time for locale %A = full weekday name %a = short month name %B = full month name %b = short month name %H = hours in 24-clock %I = hours in 12-clock For more information go to the configuration menu, select Common preferences / Display and move the mouse cursor over the input box for the date display format. </sect1> <sect1> Q10 Why can't I see the compface pictures? A. You need to enable displaying of the header pane in the general preferences </sect1> <sect1> Q11 I still can't see the pictures. Why not? A. You may not have compiled in Compface support. See Q11 in the Installation/Configuration section. </sect1> <sect1> Q12 Why does the URL Launcher not launch my webbrowser? A. You need to double-click the url. </sect1> <sect1> Q13 Attachments with spaces in the name won't open! A. When you try to launch a helper application, like an image viewer, with an attachment that has spaces in the name, put quotes around the %s parameter. Example: gedit '%s' </sect1> <sect1> Q14. Where is the Bcc when I compose a mail? A. Open Configuration -> Preferences for current account -> Compose. There you can check the Bcc checkbox and optionally enter an e-mail address. </sect1> <appendix> <sect> The Sylpheed documentation team:<label id="The Sylpheed documentation team"/> <verb> Francois Barriere fbarriere@users.sourceforge.net Martin Bretschneider furbour@users.sourceforge.net Olivier Delhomme dup@users.sourceforge.net Doruk Fisek dobidik@users.sourceforge.net Melvin Hadasht mhadasht@users.sourceforge.net Nicolas Kaiser nikai@users.sourceforge.net Paul Kater pkater@users.sourceforge.net Ricardo Mones Lastra mones@users.sourceforge.net Jens Oberender jobi@users.sourceforge.net Marcelo Ramos hackpando@users.sourceforge.net Guido Rudolphi malatesta@users.sourceforge.net Frank Weng fweng@users.sourceforge.net </verb>   <sect> GNU Free Documentation License<label id="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. <sect1> 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. </sect1> <sect1> 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. </sect1> <sect1> 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. </sect1> <sect1> 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. </sect1> <sect1> 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: <itemize> <item>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. </item> <item>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). </item> <item>State on the Title page the name of the publisher of the Modified Version, as the publisher. </item> <item>Preserve all the copyright notices of the Document. </item> <item>Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. </item> <item>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. </item> <item>Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice. </item> <item>Include an unaltered copy of this License. </item> <item>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. </item> <item>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. </item> <item>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. </item> <item>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. </item> <item>Delete any section entitled "Endorsements". Such a section may not be included in the Modified Version. </item> <item>Do not retitle any existing section as "Endorsements" or to conflict in title with any Invariant Section. </item> </itemize> 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. </sect1> <sect1> 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." </sect1> <sect1> 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. </sect1> <sect1> 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. </sect1> <sect1> 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. </sect1> <sect1> 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. </sect1> <sect1> 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 <url url="http://www.gnu.org/copyleft/" name="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. </sect1> <sect1> 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: <tt> 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". </tt> 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. </sect1>  </article>