Copyright © 2009 The Sylpheed Documentation Project.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 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 section entitled "GNU Free Documentation License".
Revision History | ||
---|---|---|
Revision 1.9 | 2005/07/08 | OD |
Ported to DocBook XML. | ||
Revision 2.0 | 2009/10/02 | PK |
Finished porting to DocBook XML, updated many questions across the document to conform with Sylpheed 2.7.1. |
Abstract
This document contains answers to various questions, which are frequently asked by Sylpheed users. It consists of three sections providing general information, information on Sylpheed installation and configuration, and on Sylpheed interface.
Table of Contents
1.1. |
Are there FAQ's in other languages? |
Yes. Here are links to several translations:
You can always download this FAQ from the Sylpheed Documentation Project website. NoteDid not find your language in the list? Would you like to contribute with a new translation to the Sylpheed Documentation Project? Then please contact the Project members at their website. Thanks in advance. |
|
1.2. |
What is Sylpheed? |
Sylpheed is an email client (and news reader) based on GTK+, running on the X Window System or Microsoft Windows, and aiming for:
As the Sylpheed README file reads: The appearance and interface are similar to some popular e-mail clients for Windows, such as Outlook Express or Becky!. Many commands are accessible with the keyboard like the Emacs-based mailers such as Mew and Wanderlust. So you will be able to migrate to Sylpheed without much discomfort, even if you are accustomed to other mailers. |
|
1.3. |
Where can I get Sylpheed? |
You can download it from the download page on Sylpheed website. There are links to download tarball sources, patches to the previous version, and also links to the Sylpheed for Windows binaries, including the installer, the ZIP archive, and the patch to the previous Sylpheed for Windows version. Depending on the state of the Sylpheed development cycle, you may be offered links to development versions such as beta and RC releases. These might not be suitable for everyday use, however, so you may want to stick with the stable release, anyway. Also on the download page, you can download Sylph-Searcher (which is a program that enables fast full-text search of messages stored in mailboxes of Sylpheed, or normal MH folders), and LibSylph (which is a library that provides Sylpheed core features independent from the UI of Sylpheed). |
|
1.4. |
Who writes Sylpheed? |
Hiroyuki Yamamoto |
|
1.5. |
What does the name Sylpheed mean? |
It means light weight, like air. This comes from the name of the wind spirits, the Sylphs. |
|
1.6. |
How does Sylpheed store mails? |
Mails are stored in the MH mailfile format as used by MH and EMH. Maildir, mbox, and eml formats are not (yet) supported, although it is possible to import an mbox file or an eml file into a Sylpheed mailbox. You can manage your mails just with Sylpheed, or together with another mailer based on the MH format (e.g. Mew). The MH format has less possibility of losing mails on failures since one file corresponds to one mail. You can also utilize fetchmail and/or procmail, and external programs on receiving (like inc or imget). |
|
1.7. |
Why does the auto collection of mail not work? |
Auto collection works since version 0.5.1. If you need it or want it, you should upgrade. |
|
1.8. |
Does Sylpheed have mail filtering? |
Yes. You can find it in ->Please note that filtering is not yet implemented for IMAP accounts. |
|
1.9. |
Can Sylpheed handle IMAP mail? |
Yes. As of version 0.4.99 IMAP is supported. |
|
1.10. |
Can Sylpheed handle local unix mailboxes? |
Yes. |
|
1.11. |
Can Sylpheed handle IPv6? |
Yes, IPv6 is fully supported in Sylpheed. |
|
1.12. |
Does Sylpheed support encryption like GPG? |
Yes. GPG is implemented and works fine. For activating it in Sylpheed, see the appropriate question in the Installation section. |
|
1.13. |
How does Sylpheed check for MIME types? |
Sylpheed uses the Mutt type of mime checking. |
|
1.14. |
Does Sylpheed allow me to write HTML styled messages? |
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 web page to an email. |
|
1.15. |
Does Sylpheed have name completion in the address fields? |
Yes. When you search for a name that starts with " |
|
1.16. |
Fine, but when I hit the Tab key I get an error message. |
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. |
|
1.17. |
Why is Sylpheed so fast? |
That's what it is designed for! |
|
1.18. |
Where can I get the current patches for Sylpheed? |
In most cases, current patches are being posted by Sylpheed users and contributors to the Sylpheed mailing list |
|
1.19. |
How can I send in patches, report bugs, talk about Sylpheed with others? |
To talk to others, you should join the Sylpheed mailing
list at
Please supply the information of |
|
1.20. |
When I send mail, the Content-Type header says the mail is in US-ASCII, even when I specified ISO-8859-1? |
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. |
|
1.21. |
Why does it look like word wrap is not working? |
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. This is a long line that Now you add one word in the first line: This is a very long line This would cause you a lot of manual reformatting to get a presentable mail again. NoteAs of Sylpheed 0.8.0., active word wrap has been implemented. You can turn it on in Wrap on input. -> -> + |
|
1.22. |
How do I copy my mail archive to another machine? |
You need to copy the Under UNIX, the user profile is stored in While under Windows 2000/XP, the user profile is stored in Under Windows Vista, the directory paths are |
|
1.23. |
Can I import a mbox into Sylpheed's MH mailfolders? |
Yes, just create/select the folder you want your mails in, and select in the menu. |
|
1.24. |
Can I use procmail to sort my mails with the MH mail handling? |
Yes. Just make sure that you add 0: * ^Subject:.*sylpheed sylpheedmail/. Check man procmail for details. |
|
1.25. |
When I upgrade Sylpheed, are there things I should be aware of? |
Yes!
You should always read the |
|
1.26. |
How can I quickly update the views in Sylpheed? |
Just press Alt-U or select from the menu. |
|
1.27. |
Why can't I use gvim as external editor? |
If one wishes to use gvim as an external editor it's
necessary to start it with the no-fork option |
|
1.28. |
Can I quote just parts of the original message when replying? |
Yes, select the part in the text view and choose Reply. |
|
1.29. |
Can I reply without quoting at all? |
You need to disable quoting by editing the reply format under -> -> -> (also works with forward format which you can see below the reply format in the configuration dialog). |
|
1.30. |
Does Sylpheed provide an anti-spam feature? |
Yes. It has a bogofilter and a bsfilter support. Just go to -> -> and check Enable Junk mail control. Then you can select a Learning command preset of your choice, or possibly use custom commands. You can also use other spam filters thanks to the Actions functionality (available under -> ).NoteYou need to have bogofilter, bsfilter, or other spam filter properly installed on your system prior to the junk mail configuration in Sylpheed, unless you use Sylpheed for Windows, which comes with bsfilter included in the installation program (since version 2.7.0). |
|
1.31. |
Where can I find the latest Sylpheed FAQ and manual? |
Go to http://sylpheeddoc.sourceforge.net and check out the FAQ and manual from the Sylpheed Documentation Project (sylpheeddoc). Both documents are available in multiple languages there and usually contain the latest updates. The direct links are as follows: Also see the question about available language versions at the top of this section. |
|
1.32. |
I have found an error and/or outdated information in this document! |
Please report any errors, misleading and/or outdated information to the Sylpheed Documentation Project. You can see the list of Project members in the following question, so you can also contact them directly. |
|
1.33. |
Who are the members of the Sylpheed Documentation Project? |
The current members of the Sylpheed Documentation Project are: Francois Barriere fbarriere at users.sourceforge.net Petr Kovar pknbe at users.sourceforge.net Below is the list of former members of the Sylpheed Documentation Project. Big thank you goes to all of them! Martin Bretschneider furbour at users.sourceforge.net Olivier Delhomme dup at users.sourceforge.net Doruk Fisek dobidik at users.sourceforge.net Melvin Hadasht mhadasht at users.sourceforge.net Nicolas Kaiser nikai at users.sourceforge.net Paul Kater pkater at users.sourceforge.net Ricardo Mones Lastra mones at users.sourceforge.net Jens Oberender jobi at users.sourceforge.net Marcelo Ramos hackpando at users.sourceforge.net Guido Rudolphi malatesta at users.sourceforge.net Frank Weng fweng at users.sourceforge.net |
2.1. |
What does it take to compile Sylpheed? |
Any POSIX compliant UNIX or similar OS, e.g. Linux, FreeBSD, Solaris. GTK+ 2.4.0 or later (GTK+ 2.6.0 or later is recommended). A recent ANSI C compiler (gcc 2.7.2.3 should also work). NoteIt is reported that Sun C will not compile Sylpheed. Optionally:
Otherwise ./configure will fail.
See also the Note that as Sylpheed now supports the Windows platform, you can also compile it using MinGW. |
|
2.2. |
How do I set up Sylpheed? |
When you run Sylpheed for the first time, it will
ask you where you want to store your mailboxes. The
default is NoteWhen Sylpheed is executed for the first time, it automatically creates the configuration files under |
|
2.3. |
Why did the creation of the mailbox fail? |
Sylpheed reports such an error if it can't create the default
mailboxes (inbox, outbox, etc.). This can be because |
|
2.4. |
How do I set up an account? |
After loading Sylpheed for the first time, you can add an email account by clicking the menu. Select the option and fill in the appropriate fields. |
|
2.5. |
How many accounts can I set up in Sylpheed? |
The number is unlimited. The limit is reached when your computer stops responding. |
|
2.6. |
Can I set up an account for sending mail only? |
Yes, set up a new account using -> and set the Protocol to None (local). |
|
2.7. |
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. |
You have to click the Execute button. The other solution: in the configuration settings ( -> -> ), you have to check the Execute immediately when moving or deleting messages box. |
|
2.8. |
Can I set up special addresses/ports for my mailserver/newsserver? |
Yes, you can. Under -> -> , you can specify the exact port addresses you want to use. |
|
2.9. |
Does Sylpheed have options for threading messages? |
Yes. You can switch it on and off in the Ctrl-T. menu, just select or press |
|
2.10. |
Can I create multiple levels of subfolders to store mail? |
Absolutely. This is no problem. |
|
2.11. |
Why isn't Sylpheed sending my mail out? |
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). |
|
2.12. |
How do I apply a patch after downloading it? |
Copy patch to sylpheed directory. Apply the patch as follows: % patch -p0 < some.patch Or, if it's gzipped: % gzip -dc some.patch.gz | patch -p0
Run |
|
2.13. |
How do I compile in support for compface pictures? |
You have to have a package called |
|
2.14. |
How do I make my own compface image? |
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 this page for the details. |
|
2.15. |
How can I tell my browser/newsclient/other program to use Sylpheed as email program? |
In the settings part of the program, write sylpheed --compose Specific options for typical browsers:
|
|
2.16. |
How do I enable GPG support in Sylpheed? |
When compiling Sylpheed, make sure you add |
|
2.17. |
Mutt does not recognize Sylpheed's MH structure |
For this to work you need to use the touch command in every MH folder. "touch" the file |
|
2.18. |
Viewing a GIF file within Sylpheed causes a segmentation fault. |
In case this happens, you can easily fix that by adding the following to image/gif gif |
|
2.19. |
How can I make Sylpheed notify me when new mail arrives? |
Download Gkrellm or a similar program that is able to notify you of new incoming mail. Gkrellm is available at the Gkrellm page. |
|
2.20. |
Can I use a spell checker with Sylpheed? |
Yes. You need to have GtkSpell installed prior to Sylpheed compilation. The support for GtkSpell is enabled by default in
configure. (If you want to disable it, make sure you add The GtkSpell option is not supported in Sylpheed for Windows (yet), so you will have no spell checking under this OS. |
|
2.21. |
How can I make Sylpheed send my compface image in the mails? |
In the Add user-defined header and press 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. -> -> check |
|
2.22. |
How can I get the newest source code from the Sylpheed Subversion (SVN) repository? |
Move to an appropriate directory, and after you run the command specified below, a source tree named svn checkout svn://sylpheed.sraoss.jp/sylpheed/trunk The subdirectories under the
To update to the newest source tree, run the following command in the target directory: svn update |
|
2.23. |
I checked out the sources using SVN and can't find any configure script. |
The SVN versions are meant to be used by developers rather than "normal" users, so the source (or binary) distributions are easier to use.
You need to generate the configure script by running |
|
2.24. |
Running "autogen.sh" gives error messages that "AM_PATH_GDK_PIXBUF" or "AM_PATH_(whatever)" is not found. |
There are some
If there are still some aclocal -I ac \ to aclocal -I ac -I /opt/gnome/share/aclocal \ and run it again. |
|
2.25. |
I don't want to compile in support for (...) any longer, but after running "configure", those libraries are still used. |
Remove the |
|
2.26. |
How can I select different applications to open with specific MIME types? |
The MIME-type to application associations are kept in |
|
2.27. |
How can I change the suggested mimetype for attachments? |
The extension to MIME-type associations are kept in |
|
2.28. |
The folder list is not updated after I manually moved/copied folders. |
You need to update Sylpheed cache. Right click on the mailbox and choose . |
|
2.29. |
How can I revert original settings, e.g. for fonts, key bindings, etc.? |
Sylpheed keeps its configuration files in |
|
2.30. |
What environment variables have effect on Sylpheed? |
Here are the most common variables:
|
|
2.31. |
Special characters (e.g. umlauts) are not displayed correctly. |
In most cases, this is caused by fonts that use an unsuitable encoding on a not Unicode-based system. (On a Unicode-based system, fonts should support all thinkable characters for the vast majority of languages.) Choose Text font. Now, a special dialog appears that allows you to pick a desirable font family, style, and size. -> -> -> , and click the button right toYou should also make sure that your environment variables regarding locale settings have sensible values. |
|
2.32. |
How can I convert my old mailbox/adress book from (some mail client). |
You can try to export your old mailbox to MH, MBOX or EML format. TipTake a look at the item from the menu, it could be a useful alternative or addition, when importing your old contacts. |
|
2.33. |
What config files are there, and what are they used for? |
Sylpheed config files can be found in
|
|
2.34. |
How do I change the location of user profile directory under Windows? |
The configuration files and the mailboxes are saved under the following
location (
If you want to change the location of the configuration files, you can
specify it by the command line option "C:\Program Files\Sylpheed\sylpheed.exe" --configdir "D:\Sylpheed" If NoteThe installer version, and GnuPG and GPGME use registry. The sample INI file is included in the Sylpheed for Windows installation package as (The text above is a slightly modified excerpt from the |
|
2.35. |
What to do when printing an email prints off the paper? |
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. |
Version 1.2, November 2002
Copyright © 2000,2001,2002 Free Software Foundation, Inc.
Version 1.2, November 2002
The purpose of this License is to make a manual, textbook, or other functional and useful 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.
This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.
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. (Thus, 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. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.
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 Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document 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, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. 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, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include 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, PostScript or PDF 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.
A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.
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.
If you publish printed copies (or copies in media that commonly have printed covers) 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 computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. 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.
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:
GNU FDL Modification Conditions
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.
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, and that you preserve all their Warranty Disclaimers.
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".
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.
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, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which 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 half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.
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, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.
If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.
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.
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.
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:
Sample Invariant Sections list
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.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with...Texts." line with this:
Sample Invariant Sections list
with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.
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.