diff options
| author | hiro <hiro@ee746299-78ed-0310-b773-934348b2243d> | 2010-07-08 02:58:08 +0000 |
|---|---|---|
| committer | hiro <hiro@ee746299-78ed-0310-b773-934348b2243d> | 2010-07-08 02:58:08 +0000 |
| commit | af81f08052caa5dd3bf88b31d9eed3cf6158e9df (patch) | |
| tree | 618f4d7cdaa624acc3e062f1e4f87cad77135791 /faq | |
| parent | fe4c422a379068a38be8f3f3f8d9dc06a0cecd6a (diff) | |
added missing source files of English FAQ and GFDL text.
git-svn-id: svn://sylpheed.sraoss.jp/sylpheed/trunk@2604 ee746299-78ed-0310-b773-934348b2243d
Diffstat (limited to 'faq')
| -rw-r--r-- | faq/GFDL-1.2 | 397 | ||||
| -rw-r--r-- | faq/Makefile.am | 2 | ||||
| -rw-r--r-- | faq/en/Makefile.am | 7 | ||||
| -rw-r--r-- | faq/en/faq.xml | 88 | ||||
| -rw-r--r-- | faq/en/faq_001.xml | 564 | ||||
| -rw-r--r-- | faq/en/faq_002.xml | 590 | ||||
| -rw-r--r-- | faq/en/faq_003.xml | 282 | ||||
| -rw-r--r-- | faq/en/fdl.xml | 383 |
8 files changed, 2312 insertions, 1 deletions
diff --git a/faq/GFDL-1.2 b/faq/GFDL-1.2 new file mode 100644 index 00000000..4a0fe1c8 --- /dev/null +++ b/faq/GFDL-1.2 @@ -0,0 +1,397 @@ + GNU Free Documentation License + Version 1.2, November 2002 + + + Copyright (C) 2000,2001,2002 Free Software Foundation, Inc. + 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 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 +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. + + +1. APPLICABILITY AND DEFINITIONS + +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. + + +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 (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. + + +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 fewer than five), + unless they release you from this requirement. +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", Preserve 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. For any section Entitled "Acknowledgements" or "Dedications", + Preserve the Title of the section, 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 to be Entitled "Endorsements" + or to conflict in title with any Invariant Section. +O. Preserve any Warranty Disclaimers. + +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, 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". + + +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, 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. + + +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, 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. + + +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.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: + + 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. diff --git a/faq/Makefile.am b/faq/Makefile.am index d69aa494..82fa2005 100644 --- a/faq/Makefile.am +++ b/faq/Makefile.am @@ -1 +1,3 @@ SUBDIRS = de en es fr it + +EXTRA_DIST = GFDL-1.2 diff --git a/faq/en/Makefile.am b/faq/en/Makefile.am index c3661303..e5bbaed1 100644 --- a/faq/en/Makefile.am +++ b/faq/en/Makefile.am @@ -9,4 +9,9 @@ faqdata_DATA = \ # generated by `ls -1 | sed -e 's/\(.*\)/ \1 \'` -EXTRA_DIST = $(faqdata_DATA) +EXTRA_DIST = $(faqdata_DATA) \ + faq.xml \ + faq_001.xml \ + faq_002.xml \ + faq_003.xml \ + fdl.xml diff --git a/faq/en/faq.xml b/faq/en/faq.xml new file mode 100644 index 00000000..f9dbc6d7 --- /dev/null +++ b/faq/en/faq.xml @@ -0,0 +1,88 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ +<!ENTITY __faq__001 SYSTEM "faq_001.xml"> +<!ENTITY __faq__002 SYSTEM "faq_002.xml"> +<!ENTITY __faq__003 SYSTEM "faq_003.xml"> +<!ENTITY __license SYSTEM "fdl.xml"> +]> +<book> + <title>Sylpheed FAQ</title> + <bookinfo> + <abstract> + <para>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.</para> + </abstract> + <copyright> + <year>2010</year> + <holder>The Sylpheed Documentation Project.</holder> + </copyright> + <legalnotice> + <para>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". + </para> + </legalnotice> + <author> + <firstname>Paul</firstname> + <surname>Kater</surname> +<!-- affiliation> + <address> + <email>paul at nlpagan.net</email> + </address> + </affiliation --> </author> + <author> + <firstname>Jens</firstname> + <surname>Oberender</surname> +<!-- affiliation> + <address> + <email>j.obi at troja.net</email> + </address> + </affiliation --> </author> + <author> + <firstname>Francois</firstname> + <surname>Barriere</surname> +<!-- affiliation> + <address> + <email>barriere.francois at libertysurf.fr</email> + </address> + </affiliation --> </author> + <author> + <firstname>Olivier</firstname> + <surname>Delhomme</surname> +<!-- affiliation> + <address> + <email>olivier.delhomme at free.fr</email> + </address> + </affiliation --> </author> + <author> + <firstname>Petr</firstname> + <surname>Kovar</surname> +<!-- affiliation> + <address> + <email>pknbe at volny.cz</email> + </address> + </affiliation --> </author> + <revhistory> +<!-- ******************************************************************************** --> <revision> + <revnumber>1.9</revnumber> + <date>2005/07/08</date> + <authorinitials>OD</authorinitials> + <revremark>Ported to DocBook XML.</revremark> + </revision> + <revision> + <revnumber>2.0</revnumber> + <date>2009/10/02</date> + <authorinitials>PK</authorinitials> + <revremark>Finished porting to DocBook XML, updated many questions across the document to conform with Sylpheed 2.7.1.</revremark> + </revision> + <revision> + <revnumber>2.1</revnumber> + <date>2010/04/14</date> + <authorinitials>PK</authorinitials> + <revremark>Updated with regard to Sylpheed 3.0.2.</revremark> + </revision> +<!-- ******************************************************************************** --> </revhistory> + </bookinfo> +&__faq__001;&__faq__002;&__faq__003;&__license;</book> diff --git a/faq/en/faq_001.xml b/faq/en/faq_001.xml new file mode 100644 index 00000000..90413c19 --- /dev/null +++ b/faq/en/faq_001.xml @@ -0,0 +1,564 @@ +<?xml version='1.0' encoding='UTF-8'?><chapter id="sylpheed-faq-1"> + <title>Sylpheed FAQ - General Information</title> + <qandaset id="faq-general"> +<?dbhtml cellspacing="13px" ?> <qandaentry> + <question id="faq-languages"> + <para> + Are there FAQ's in other languages? + </para> + </question> + <answer> + <para> + Yes. Here are links to several translations:</para> + <itemizedlist> + <listitem> + <para><ulink url="http://sylpheeddoc.sourceforge.net/fr/faq/faq.html">Sylpheed FAQ in French</ulink>, translated by Olivier Delhomme.</para> + </listitem> + <listitem> + <para><ulink url="http://sylpheeddoc.sourceforge.net/de/faq/faq.html">Sylpheed FAQ in German</ulink>, translated by Nicolas Kaiser.</para> + </listitem> + <listitem> + <para><ulink url="http://sylpheeddoc.sourceforge.net/es/faq/faq.html">Sylpheed FAQ in Spanish</ulink>, translated by Ricardo Mones Lastra.</para> + </listitem> + <listitem> + <para><ulink url="http://sylpheeddoc.sourceforge.net/zh_TW.Big5/sylpheed-faq.html">Sylpheed FAQ in Traditional Chinese</ulink>, courtesy of Franklin.</para> + </listitem> + </itemizedlist> + <para> + You can always download this FAQ from the <ulink url="http://sylpheeddoc.sourceforge.net/en/faq/sylpheed-faq.html">Sylpheed Documentation Project website</ulink>.</para> + <note> + <para>Did 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 <ulink url="http://sylpheeddoc.sourceforge.net/">their website</ulink>. Thanks in advance.</para> + </note> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-what-sylpheed"> + <para> + What is Sylpheed? + </para> + </question> + <answer> + <para> + Sylpheed is an email client (and news reader) based on GTK+, + running on the X Window System or Microsoft Windows, and aiming for:</para> + <itemizedlist> + <listitem> + <para>Quick response</para> + </listitem> + <listitem> + <para>Graceful, and sophisticated interface</para> + </listitem> + <listitem> + <para>Easy configuration, intuitive operation</para> + </listitem> + <listitem> + <para>High reliability</para> + </listitem> + <listitem> + <para>Internationalization and multilingualization support</para> + </listitem> + <listitem> + <para>Abundant features</para> + </listitem> + </itemizedlist> + <para>As the Sylpheed <filename>README</filename> 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.</para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-get-sylpheed"> + <para> + Where can I get Sylpheed? + </para> + </question> + <answer> + <para> + You can download it from the <ulink url="http://sylpheed.sraoss.jp/en/download.html">download page</ulink> on <ulink url="http://sylpheed.sraoss.jp/en/">Sylpheed website</ulink>. 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. </para> + <para>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.</para> + <para>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).</para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-writes-sylpheed"> + <para> + Who writes Sylpheed? + </para> + </question> + <answer> + <para> + Hiroyuki Yamamoto <email>hiro-y@kcn.ne.jp</email>. + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-sylpheed-name"> + <para> + What does the name Sylpheed mean? + </para> + </question> + <answer> + <para> + It means <emphasis>light weight</emphasis>, like air. This comes from the + name of the wind spirits, the Sylphs. + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-sylpheed-store-mail"> + <para> + How does Sylpheed store mails? + </para> + </question> + <answer> + <para> + 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.</para> + <para>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).</para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-auto-collection-sylpheed"> + <para> + Why does the auto collection of mail not work? + </para> + </question> + <answer> + <para> + Auto collection works since version 0.5.1. If you need it + or want it, you should upgrade. + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-filtering-sylpheed"> + <para> + Does Sylpheed have mail filtering? + </para> + </question> + <answer> + <para> + Yes. You can find it in <guimenu>Configuration</guimenu> -> <guimenuitem>Filter settings...</guimenuitem></para> + <para> + Please note that filtering is not yet implemented for IMAP accounts. + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-imap-sylpheed"> + <para> + Can Sylpheed handle IMAP mail? + </para> + </question> + <answer> + <para> + Yes. As of version 0.4.99 IMAP is supported. + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-local-unix-sylpheed"> + <para> + Can Sylpheed handle local unix mailboxes? + </para> + </question> + <answer> + <para> + Yes. + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-ipv6-sylpheed"> + <para> + Can Sylpheed handle IPv6? + </para> + </question> + <answer> + <para> + Yes, IPv6 is fully supported in Sylpheed. + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-encryption-gpg-sylpheed"> + <para> + Does Sylpheed support encryption like GPG? + </para> + </question> + <answer> + <para> + Yes. GPG is implemented and works fine. For activating it in Sylpheed, + see the appropriate question in the Installation section. + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-mime-types-sylpheed"> + <para> + How does Sylpheed check for MIME types? + </para> + </question> + <answer> + <para> + Sylpheed uses the Mutt type of mime checking. + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-html-sylpheed"> + <para>Does Sylpheed allow me to write HTML styled messages? + </para> + </question> + <answer> + <para> + 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.</para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-completion-adress-sylpheed"> + <para>Does Sylpheed have name completion in the address fields? + </para> + </question> + <answer> + <para> + Yes. When you search for a name that starts with "<literal>don</literal>", + type "<literal>don</literal>" (without the quotes) and press the <keycap>Tab</keycap> key. + This will show you the correct name (when only one "don" + exists in your address book. Otherwise a drop-down list + appears, which allows you to select the name you want. + E.g. Donald Duck, Don Johnson. But also email addresses + starting with "<literal>don</literal>" will appear in the list (like + "<literal>don.giovanni@maffia.org</literal>"). + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-tab-error-sylpheed"> + <para>Fine, but when I hit the Tab key I get an error message. + </para> + </question> + <answer> + <para> + 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. + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-sylpheed-fast"> + <para>Why is Sylpheed so fast? + </para> + </question> + <answer> + <para>That's what it is designed for! + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-patches-sylpheed"> + <para>Where can I get the current patches for Sylpheed? + </para> + </question> + <answer> + <para>In most cases, current patches are being posted by Sylpheed users and contributors to the <ulink url="http://www.sraoss.jp/mailman/listinfo/sylpheed">Sylpheed mailing list</ulink> <email>sylpheed@sraoss.jp</email>. + (Also see the Installation section on how to install a patch.) + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-send-patches-sylpheed"> + <para>How can I send in patches, report bugs, talk about Sylpheed with others? + </para> + </question> + <answer> + <para>To talk to others, you should join the Sylpheed mailing + list at <ulink url="http://www.sraoss.jp/mailman/listinfo/sylpheed"> + <literal>http://www.sraoss.jp/mailman/listinfo/sylpheed</literal> + </ulink>. 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 post it either to the mailing list, or contact the Sylpheed author, Hiroyuki Yamamoto <email>hiro-y@kcn.ne.jp</email>. </para> + <para>Please supply the information of <menuchoice> + <guimenu>Tools</guimenu> + <guimenuitem>Log window</guimenuitem> + </menuchoice>, or the contents of +<filename>sylpheed.log</filename>, which is located under the configuration folder, when +reporting bugs.</para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-content-type-header-sylpheed"> + <para>When I send mail, the Content-Type header says the mail is in + US-ASCII, even when I specified ISO-8859-1? + </para> + </question> + <answer> + <para>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. + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-word-wrap-sylpheed"> + <para>Why does it look like word wrap is not working? + </para> + </question> + <answer> + <para>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. + <literallayout> This is a long line that + is wrapped. </literallayout>Now you add one word in the first line: + <literallayout> This is a very long line + that + is wrapped </literallayout>This would cause you a lot of manual reformatting to get + a presentable mail again. + + </para> + <note> + <para>As of Sylpheed 0.8.0., active word wrap has been + implemented. You can turn it on in <menuchoice> + <guisubmenu>Common Preferences</guisubmenu> + <guimenuitem>Compose</guimenuitem> + <guimenuitem>Editor</guimenuitem> + <guilabel>Wrap on input</guilabel> + </menuchoice>. + </para> + </note> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How do I copy my mail archive to another machine? </para> + </question> + <answer> + <para>You need to copy the <filename>sylpheed-2.0</filename> directory with your user profile, and your entire local mail archive. </para> + <para>Under UNIX, the user profile is stored in <filename>$HOME/.sylpheed-2.0</filename> by default, and your local mail archive is by default located in <filename>$HOME/Mail</filename>. </para> + <para>While under Windows 2000/XP, the user profile is stored in <filename>C:\Documents and Settings\<replaceable>(user name)</replaceable>\Application Data\Sylpheed</filename> by default, and your local mail archive is by default located in <filename>C:\Documents and Settings\<replaceable>(user name)</replaceable>\Application Data\Sylpheed\Mailboxes\Mail</filename>. </para> + <para>Under Windows Vista/Seven, the directory paths are <filename>C:\Users\<replaceable>(user name)</replaceable>\AppData\Roaming\Sylpheed</filename>, and <filename>C:\Users\<replaceable>(user name)</replaceable>\AppData\Roaming\Sylpheed\Mailboxes\Mail</filename>, respectively.</para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-import-mbox-sylpheed"> + <para>Can I import a mbox into Sylpheed's MH mailfolders? + </para> + </question> + <answer> + <para> + Yes, just create/select the folder you want your + mails in, and select <guimenuitem>Import mbox file...</guimenuitem> in the <guimenu>File</guimenu> + menu.</para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-procmail-use-sylpheed"> + <para> + Can I use procmail to sort my mails with the MH mail handling? + </para> + </question> + <answer> + <para> + Yes. Just make sure that you add <computeroutput>/.</computeroutput> to the end of a rule so + procmail knows you are filtering into an MH mail folder. Example: + </para> + <programlisting>0: +* ^Subject:.*sylpheed +sylpheedmail/. +</programlisting> + <para>Check <command>man procmail</command> for details. + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-upgrade-sylpheed"> + <para> + When I upgrade Sylpheed, are there things I should be aware of? + </para> + </question> + <answer> + <para> + Yes!</para> + <itemizedlist> + <listitem> + <para>Upgrade to 0.4.50: you should reconfigure your newsgroup settings</para> + </listitem> + <listitem> + <para>Upgrade to 0.4.63: you should set the URL string colors from the <guimenu>Configuration</guimenu> menu</para> + </listitem> + <listitem> + <para>Upgrade to 0.4.65: some menu items have been moved</para> + </listitem> + <listitem> + <para>Upgrade to 0.7.3: many key bindings have changed</para> + </listitem> + <listitem> + <para>Upgrade to 2.2.3 or former on Windows: all configuration files such as mailboxes or bsfilter files are removed when performing the upgrade and/or uninstallation, so please be careful and backup your data</para> + </listitem> + </itemizedlist> + <para>You should always read the <filename>NEWS</filename> document (and also <filename>NEWS-<replaceable>x</replaceable>.0</filename> if you are upgrading from a very old version) that is included in the release tarballs. The NEWS can also be viewed on the <ulink url="http://sylpheed.sraoss.jp/en/news.html">appropriate Sylpheed website page</ulink>. </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-update-views-sylpheed"> + <para>How can I quickly update the views in Sylpheed? + </para> + </question> + <answer> + <para> + Just press <keycombo> + <keycap>Alt</keycap> + <keycap>U</keycap> + </keycombo> or select <guimenuitem>Update summary</guimenuitem> from the <guimenu>View</guimenu> menu. + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-gvim-external-editor-sylpheed"> + <para>Why can't I use gvim as external editor? + </para> + </question> + <answer> + <para> + If one wishes to use gvim as an external editor it's + necessary to start it with the no-fork option <parameter>-f</parameter>, i.e. + in the configuration dialog box you need to enter + <command>gvim -f %s</command>. 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!) + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-quote-messages-sylpheed"> + <para>Can I quote just parts of the original message when replying? + </para> + </question> + <answer> + <para> + Yes, select the part in the text view and choose <guiicon>Reply</guiicon>. + </para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-not-quoting-sylpheed"> + <para>Can I reply without quoting at all? + </para> + </question> + <answer> + <para>You need to disable quoting by editing the reply format under <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Common preferences</guimenuitem> + <guimenuitem>Compose tab</guimenuitem> + <guimenuitem>Format tab</guimenuitem> + </menuchoice> + (also works with + forward format which you can see below the reply format in the configuration dialog).</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> Does Sylpheed provide an anti-spam feature? </para> + </question> + <answer> + <para>Yes. It has a <ulink url="http://www.bogofilter.org/">bogofilter</ulink> and a <ulink url="http://bsfilter.org/index-e.html">bsfilter</ulink> support. Just go to <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Common preferences...</guimenuitem> + <guimenuitem>Junk mail</guimenuitem> + </menuchoice> and check <guilabel>Enable Junk mail control</guilabel>. Then you can select a <guilabel>Learning command</guilabel> preset of your choice, or possibly use custom commands.</para> + <para>You can also use other spam filters thanks to the Actions functionality (available under <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Actions...</guimenuitem> + </menuchoice>).</para> + <note> + <para>You 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).</para> + </note> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Are there any plug-ins extending standard Sylpheed functionality?</para> + </question> + <answer> + <para>Not yet, but they are planned, since Sylpheed 3.0, released in early 2010, and later supports a plug-in interface. In the future, some of the Sylpheed features will be re-implemented as plug-ins, and, moreover, various other plug-ins will be released.</para> + <para>There is a page on the Sylpheed website dedicated to the <ulink url="http://sylpheed.sraoss.jp/en/plugin.html">plug-in interface</ulink>. Additionally, the <filename>PLUGIN.txt</filename> file distributed directly with Sylpheed can provide you with some basic information on the topic.</para> + <note> + <para>If you are a developer interested in creating plug-ins for Sylpheed, see the <ulink url="http://sylpheed.sraoss.jp/wiki/index.php?PluginSpec">plug-in specification</ulink> on the Sylpheed wiki.</para> + </note> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-faq-sylpheed"> + <para>Where can I find the latest Sylpheed FAQ and manual? + </para> + </question> + <answer> + <para> + Go to <ulink url="http://sylpheeddoc.sourceforge.net/">http://sylpheeddoc.sourceforge.net</ulink> 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:</para> + <itemizedlist> + <listitem> + <para><ulink url="http://sylpheeddoc.sourceforge.net/en/faq/sylpheed-faq.html">current version of the English FAQ</ulink></para> + </listitem> + <listitem> + <para><ulink url="http://sylpheeddoc.sourceforge.net/en/manual/sylpheed.html">current version of the English manual</ulink></para> + </listitem> + </itemizedlist> + <para>Also see the question about available language versions at the top of this section. </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>I have found an error and/or outdated information in this document!</para> + </question> + <answer> + <para>Please report any errors, misleading and/or outdated information to the <ulink url="http://sylpheeddoc.sourceforge.net/">Sylpheed Documentation Project</ulink>. You can see the list of Project members in the following question, so you can also contact them directly.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Who are the members of the Sylpheed Documentation Project?</para> + </question> + <answer> + <para>The current members of the Sylpheed Documentation Project are:</para> + <programlisting>Francois Barriere fbarriere at users.sourceforge.net +Petr Kovar pknbe at users.sourceforge.net</programlisting> + <para>Below is the list of former members of the Sylpheed Documentation Project. Big thank you goes to all of them!</para> + <programlisting>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</programlisting> + </answer> + </qandaentry> + </qandaset> +</chapter>
\ No newline at end of file diff --git a/faq/en/faq_002.xml b/faq/en/faq_002.xml new file mode 100644 index 00000000..212449eb --- /dev/null +++ b/faq/en/faq_002.xml @@ -0,0 +1,590 @@ +<?xml version='1.0' encoding='UTF-8'?><chapter id="sylpheed-faq-2"> + <title>Sylpheed FAQ - Installation and Configuration</title> + <qandaset id="faq-installation"> +<?dbhtml cellspacing="13px" ?> <qandaentry> + <question> + <para>What does it take to compile Sylpheed?</para> + </question> + <answer> + <para>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).</para> + <note> + <para>It is reported that Sun C will not compile +Sylpheed.</para> + </note> + <para>Optionally:</para> + <itemizedlist> + <listitem> + <para>compface (for X-Face)</para> + </listitem> + <listitem> + <para>GPGME (for GnuPG)</para> + </listitem> + <listitem> + <para>OpenSSL for SSL support</para> + </listitem> + <listitem> + <para>GtkSpell for a spell checking feature</para> + </listitem> + <listitem> + <para>cURL for allowing Sylpheed to check for updates</para> + </listitem> + <listitem> + <para>JPilot</para> + </listitem> + <listitem> + <para>LDAP</para> + </listitem> + <listitem> + <para>the equivalent of GTK+-devel and Xfree86-devel</para> + </listitem> + <listitem> + <para>you may also require flex (lex) and bison +(yacc).</para> + </listitem> + </itemizedlist> + <para>Otherwise ./configure will fail. +See also the <filename>INSTALL</filename> file that is being distributed with the Sylpheed tarball.</para> + <para>Note that as Sylpheed now supports the Windows platform, you can also compile it using <ulink url="http://www.mingw.org/">MinGW</ulink>.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How do I set up Sylpheed?</para> + </question> + <answer> + <para>When you run Sylpheed for the first time, it will +ask you where you want to store your mailboxes. The +default is <filename>$HOME/Mail</filename> (or <filename>%APPDATA%\Sylpheed\Mailboxes\Mail</filename> under Windows). You can change this to +anything you like as long as it is a valid directory +name.</para> + <note> + <para>When Sylpheed is executed for the first time, it automatically creates the configuration files under <filename>$HOME/.sylpheed-2.0/</filename> (or <filename>%APPDATA%\Sylpheed\</filename> under Windows), and asks you the location of mailbox. As stated above, the default is <filename>$HOME/Mail</filename>, or <filename>%APPDATA%\Sylpheed\Mailboxes\Mail</filename> under Windows. If some files, which are non-MH format, already exist on the directory, you will have to specify another location.</para> + </note> + <para>Furthermore, you need to <link linkend="faq-account-setup">create at least one account</link> to be able to receive or send messages.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Why did the creation of the mailbox fail?</para> + </question> + <answer> + <para>Sylpheed reports such an error if it can't create the default +mailboxes (inbox, outbox, etc.). This can be because <filename>$HOME/Mail</filename> +(or <filename>%APPDATA%\Sylpheed\Mailboxes\Mail</filename> under Windows) 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.</para> + </answer> + </qandaentry> + <qandaentry> + <question id="faq-account-setup"> + <para>How do I set up an account?</para> + </question> + <answer> + <para>After loading Sylpheed for the first time, you can +add an email account by clicking the <guimenu>Configuration</guimenu> menu. Select the option <guimenuitem>Create new account</guimenuitem> and let the configuration assistant help you with the initial setup. +In a few easy steps, the assistant allows you to conveniently configure your POP3, IMAP4, or Gmail account.</para> + <tip> + <para>If you want later to change your account configuration, just select <menuchoice> + <guimenuitem>Configuration</guimenuitem> + <guimenuitem>Preferences for current account...</guimenuitem> + </menuchoice>, or <menuchoice> + <guimenuitem>Configuration</guimenuitem> + <guimenuitem>Edit accounts...</guimenuitem> + </menuchoice></para> + </tip> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How many accounts can I set up in Sylpheed?</para> + </question> + <answer> + <para>The number is unlimited. The limit is reached when +your computer stops responding.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Can I set up an account for sending mail only?</para> + </question> + <answer> + <para>Yes, add a new account using <menuchoice> + <guimenuitem>Configuration</guimenuitem> + <guimenuitem>Edit accounts...</guimenuitem> + <guibutton>Add</guibutton> + </menuchoice> and set the Protocol to None (local).</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>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.</para> + </question> + <answer> + <para>You have to click the <guiicon>Execute</guiicon> button. +The other solution: in the configuration settings +(<menuchoice> + <guimenuitem>Common preferences...</guimenuitem> + <guimenuitem>Details</guimenuitem> + <guimenuitem>Interface</guimenuitem> + </menuchoice>), you have to +check the <guilabel>Execute immediately when moving or deleting messages</guilabel> box.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Can I set up special addresses/ports for my mailserver/newsserver?</para> + </question> + <answer> + <para>Yes, you can. Under <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Preferences for current account...</guimenuitem> + <guimenuitem>Advanced</guimenuitem> + </menuchoice>, you +can specify the exact port addresses you want to use.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Does Sylpheed have options for threading messages?</para> + </question> + <answer> + <para>Yes. You can switch it on and off in the <guimenu>View</guimenu> + menu, just select <guimenuitem>Thread view</guimenuitem> or press <keycombo> + <keycap>Ctrl</keycap> + <keycap>T</keycap> + </keycombo>.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Can I create multiple levels of subfolders to store mail?</para> + </question> + <answer> + <para>Absolutely. This is no problem.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Why isn't Sylpheed sending my mail out?</para> + </question> + <answer> + <para>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).</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How do I apply a patch after downloading it?</para> + </question> + <answer> + <para>Copy patch to sylpheed directory. + Apply the patch as follows:</para> + <para> + <command>% patch -p0 < some.patch</command></para> + <para> + Or, if it's gzipped:</para> + <para> + <command>% gzip -dc some.patch.gz | patch -p0</command></para> + <para> + Run <filename>./autogen.sh</filename>, remove the generated <filename>/config.cache</filename> + file (unless you want to install in prefix + <filename>/usr/local</filename>). + Run <filename>./configure</filename> with the appropriate options and + then <filename>make</filename>. + (Text as found on the former Sylpheed patches page.)</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How do I compile in support for compface pictures?</para> + </question> + <answer> + <para>You have to have a package called <computeroutput>libcompface</computeroutput> + installed, so this is available for compiling into + Sylpheed. Note that the exact name of the package depends on OS or distribution you use.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How do I make my own compface image?</para> + </question> + <answer> + <para>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 <ulink url="http://www.dairiki.org/xface/">this page</ulink> for the details.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How can I tell my browser/newsclient/other program to use Sylpheed as email program?</para> + </question> + <answer> + <para> In the settings part of the program, write + <command>sylpheed --compose</command></para> + <para> +Specific options for typical browsers:</para> + <itemizedlist> + <listitem> + <para>Opera: <command>sylpheed --compose [mailto:%t][?subject=%s] </command></para> + </listitem> + <listitem> + <para>Galeon: <command>sylpheed --compose "mailto:%t?subject=%s"</command></para> + </listitem> + </itemizedlist> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How do I enable GPG support in Sylpheed?</para> + </question> + <answer> + <para> When compiling Sylpheed, make sure you add <parameter>--enable-gpgme</parameter> in the <command>./configure</command> command. +When that completes successfully, there is a <guimenuitem>Privacy</guimenuitem> section in the <guimenuitem>Common Preferences</guimenuitem>.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Mutt does not recognize Sylpheed's MH structure</para> + </question> + <answer> + <para>For this to work you need to use the <command>touch</command> command in every MH folder. "<command>touch</command>" the file <filename>.xmhcache</filename> and Mutt should do just fine.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Viewing a GIF file within Sylpheed causes a segmentation fault.</para> + </question> + <answer> + <para>In case this happens, you can easily fix that by adding the following to <filename>/etc/mime.types</filename>:</para> + <programlisting>image/gif gif</programlisting> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How Sylpheed checks for new mail?</para> + </question> + <answer> + <para>New mail can be retrieved either manually or automatically.</para> + <para>To check for new mail the manual way, you can:</para> + <orderedlist> + <listitem> + <para>Either press the <guibutton>Get </guibutton>button on the toolbar to incorporate new mail for the current account only, or use the <guibutton>Get all</guibutton> button to incorporate new mail for all configured accounts.</para> + </listitem> + <listitem> + <para>Or choose <menuchoice> + <guimenu>File</guimenu> + <guimenuitem>Mailbox</guimenuitem> + <guimenuitem>Check for new messages</guimenuitem> + </menuchoice>, or <guimenuitem>Check for new messages in all mailboxes</guimenuitem>.</para> + </listitem> + <listitem> + <para>Or select <menuchoice> + <guimenu>Message</guimenu> + <guimenuitem>Receive</guimenuitem> + <guimenuitem>Get from current account</guimenuitem> + </menuchoice>, or <guimenuitem>Get from all accounts</guimenuitem>.</para> + </listitem> + </orderedlist> + <tip> + <para>If you have a POP3 account and don't want to retrieve all the new messages stored on remote server to your computer, you can manage your account remotely (e.g. open or delete individual messages) by choosing <menuchoice> + <guimenu>Message</guimenu> + <guimenuitem>Receive</guimenuitem> + <guimenuitem>Remote mailbox...</guimenuitem> + </menuchoice></para> + </tip> + <para>If you prefer autochecking for new mail instead, first of all, make sure that you have checked <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Common preferences...</guimenuitem> + <guimenuitem>Receive</guimenuitem> + <guilabel>Autocheck new mail every <replaceable>10</replaceable> minute(s)</guilabel> + </menuchoice>. Optionally, you can adjust the interval value (in minutes) as well.</para> + <para>Also check your settings under <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Edit accounts...</guimenuitem> + </menuchoice> You will find this +at the top: <guilabel>Check the boxes on the 'G' column to enable message retrieval by 'Get all'</guilabel>. The setting applies on both manual and automatic +mail checks.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How can I make Sylpheed notify me when new mail arrives?</para> + </question> + <answer> + <para>Download Gkrellm or a similar program that is able to notify you of new incoming mail. Gkrellm is available at <ulink url="http://www.gkrellm.net">the Gkrellm page</ulink>.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Can I use a spell checker with Sylpheed?</para> + </question> + <answer> + <para>Yes. You need to have GtkSpell installed prior to Sylpheed compilation. The support for GtkSpell is enabled by default in <command>configure</command>. (If you want to disable it, make sure you add <parameter>--disable-gtkspell</parameter> in the <command>./configure</command> command.)</para> + <para>The GtkSpell option is not supported in Sylpheed for Windows (yet), so you will have no spell checking under this OS.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How can I make Sylpheed send my compface image in the mails?</para> + </question> + <answer> + <para>In the <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Preferences for current account...</guimenuitem> + <guimenuitem>Send</guimenuitem> + </menuchoice> check <guilabel>Add user-defined header</guilabel> and press <guibutton>Edit</guibutton> 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.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How can I get the newest source code from the Sylpheed Subversion (SVN) repository?</para> + </question> + <answer> + <para>Move to an appropriate directory, and after you run the command specified below, a source tree named <filename>trunk</filename> will be created under that directory:</para> + <para><command>svn checkout svn://sylpheed.sraoss.jp/sylpheed/trunk</command></para> + <para>The subdirectories under the <filename>sylpheed</filename> directory are as follows:</para> + <itemizedlist> + <listitem> + <para><filename>trunk/</filename> - main tree</para> + </listitem> + <listitem> + <para><filename>branches/</filename> - miscellaneous experimental branches</para> + </listitem> + <listitem> + <para><filename>tags/</filename> - release-tagged branches</para> + </listitem> + </itemizedlist> + <para>To update to the newest source tree, run the following command in the target directory:</para> + <para><command>svn update</command></para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>I checked out the sources using SVN and can't find any configure script.</para> + </question> + <answer> + <para>The SVN versions are meant to be used by developers rather than "normal" + users, so the source (or binary) distributions are easier to use.</para> + <blockquote> + <para>Yeah, but the latest features from SVN really look sexy...</para> + </blockquote> + <para>You need to generate the configure script by running <filename>autogen.sh</filename>. + Be sure to have autoconf and automake packages installed for this.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Running "autogen.sh" gives error messages that "AM_PATH_GDK_PIXBUF" or + "AM_PATH_(whatever)" is not found.</para> + </question> + <answer> + <para>There are some <filename>*.m4</filename> files in the <filename>ac/missing</filename> directory. Try to copy + them into the <filename>ac</filename> directory and run <filename>autogen.sh</filename> again.</para> + <para> + If there are still some <filename>.m4</filename> files not found (e.g. those from GTK+), try + to run <command>% locate m4 | less</command> or <command>% locate aclocal | less</command> to find additional directories containing those macros. If you find e.g. a + <filename>gtk.m4</filename> in <filename>/opt/gnome/share/aclocal</filename>, change following line in + <filename>autogen.sh</filename> from</para> + <programlisting>aclocal -I ac \</programlisting> + <para> to</para> + <programlisting>aclocal -I ac -I /opt/gnome/share/aclocal \</programlisting> + <para>and run it again.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>I don't want to compile in support for (...) any longer, but after running + "configure", those libraries are still used.</para> + </question> + <answer> + <para>Remove the <filename>config.cache</filename> file and run <command>./configure</command> again. You should + also use <command>make clean</command> to avoid undefined references.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How can I select different applications to open with specific MIME types?</para> + </question> + <answer> + <para>The MIME-type to application associations are kept in <filename>/etc/mailcap</filename>.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How can I change the suggested mimetype for attachments?</para> + </question> + <answer> + <para>The extension to MIME-type associations are kept in <filename>/etc/mime.types</filename></para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>The folder list is not updated after I manually moved/copied folders.</para> + </question> + <answer> + <para>You need to update Sylpheed cache. Right click on the mailbox and choose + <guimenuitem>Rebuild folder tree</guimenuitem>.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How can I revert original settings, e.g. for fonts, key bindings, etc.?</para> + </question> + <answer> + <para>Sylpheed keeps its configuration files in <filename>$HOME/.sylpheed-2.0/sylpheedrc</filename> (or <filename>%APPDATA%\Sylpheed\sylpheedrc</filename> under Windows) and creates default + entries, if none are found. So the easiest way is to quit Sylpheed, + temporarily renaming your <filename>$HOME/.sylpheed-2.0</filename> (or <filename>%APPDATA%\Sylpheed\sylpheedrc</filename>) e.g. to <filename>*.bak</filename> and restarting + Sylpheed in order to get default entries.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>What environment variables have effect on Sylpheed?</para> + </question> + <answer> + <para>Here are the most common variables:</para> + <itemizedlist> + <listitem> + <para><envar>HOME</envar> + - location of <filename>.sylpheed-2.0</filename> (config directory) and default folder for Mailboxes.</para> + </listitem> + <listitem> + <para><envar>LANG</envar>,</para> + </listitem> + <listitem> + <para><envar>LC_ALL</envar>,</para> + </listitem> + <listitem> + <para><envar>LC_CTYPE</envar>,</para> + </listitem> + <listitem> + <para><envar>LC_MESSAGES</envar> - locale settings, e.g. language and date format.</para> + </listitem> + </itemizedlist> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Special characters (e.g. umlauts) are not displayed correctly.</para> + </question> + <answer> + <para>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.)</para> + <para>Choose <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Common preferences...</guimenuitem> + <guimenuitem>Display</guimenuitem> + <guimenuitem>General</guimenuitem> + </menuchoice>, and click the button right to <guilabel>Text font</guilabel>. Now, a special dialog appears that allows you to pick a desirable font family, style, and size.</para> + <para>You should also make sure that your environment variables regarding locale + settings have sensible values.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How can I convert my old mailbox/address book from (some mail client).</para> + </question> + <answer> + <para>You can try to + export your old mailbox to MH, MBOX or EML format.</para> + <tip> + <para>Take a look at the <guimenuitem>Add sender to address book...</guimenuitem> item from the <guimenu>Tools</guimenu> + menu, it could be a useful alternative or addition, when importing your old + contacts.</para> + </tip> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>What config files are there, and what are they used for?</para> + </question> + <answer> + <para>Sylpheed config files can be found in <filename>$HOME/.sylpheed-2.0</filename> (under Windows, the path is <filename>%APPDATA%\Sylpheed</filename>). They are in plain + text format and quite easy to understand, so don't fear to take a look + into them using a text editor.</para> + <itemizedlist> + <listitem> + <para><filename>sylpheedrc</filename> - main configuration: nearly all options from the + settings window, e.g. mailbox location, font + entries, etc.</para> + </listitem> + <listitem> + <para><filename>accountrc</filename> - settings for POP/IMAP/NNTP accounts</para> + </listitem> + <listitem> + <para><filename>actionsrc</filename> - user-defined actions</para> + </listitem> + <listitem> + <para><filename>addrbook-*.xml</filename> - contents of your address book</para> + </listitem> + <listitem> + <para><filename>customheaderrc</filename> - contains user-defined header lines</para> + </listitem> + <listitem> + <para><filename>dispheaderrc</filename> - headers to display above the mail body</para> + </listitem> + <listitem> + <para><filename>filter.xml</filename> - filter settings</para> + </listitem> + <listitem> + <para><filename>folderlist.xml</filename> - folder specific settings, e.g. hiding + read messages, sort order, etc.</para> + </listitem> + <listitem> + <para><filename>menurc</filename> - key bindings</para> + </listitem> + </itemizedlist> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How do I change the location of user profile directory under Windows?</para> + </question> + <answer> + <para>The configuration files and the mailboxes are saved under the following +location (<filename>%APPDATA%\Sylpheed</filename>) by default:</para> + <para><itemizedlist> + <listitem> + <para>Windows 2000/XP: +<filename>C:\Documents and Settings\<replaceable>(user name)</replaceable>\Application Data\Sylpheed</filename></para> + </listitem> + <listitem> + <para>Windows Vista/Seven: +<filename>C:\Users\<replaceable>(user name)</replaceable>\AppData\Roaming\Sylpheed</filename></para> + </listitem> + </itemizedlist></para> + <para>If you want to change the location of the configuration files, you can +specify it by the command line option <parameter>--configdir "<replaceable>directory name</replaceable>"</parameter>. +Create a shortcut of <filename>sylpheed.exe</filename>, and append the option to the link target +like the following:</para> + <screen>"C:\Program Files\Sylpheed\sylpheed.exe" --configdir "D:\Sylpheed"</screen> + <para>If <filename>sylpheed.ini</filename> file exists at the same location as <filename>sylpheed.exe</filename>, it will be +loaded at startup. With this approach, you can make Sylpheed completely portable +independent of drive letters etc., and you can install it in removable media +such as USB memory.</para> + <note> + <para>The installer version, and GnuPG and GPGME use registry.</para> + </note> + <para>The sample INI file is included in the Sylpheed for Windows installation package as <filename>sample-sylpheed.ini</filename>. +Please copy or rename it to use. +<literal>ipcport</literal> specifies the port number of socket for IPC (default is 50215). +<literal>configdir</literal> specifies the location of configuration files as a relative +path from the folder in which <filename>sylpheed.exe</filename> is located, or an absolute path.</para> + <para>(The text above is a slightly modified excerpt from the <filename>README-win32.txt</filename> file, which you should find within the <filename>C:\Program Files\Sylpheed</filename> directory.)</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>What to do when printing an email prints off the paper?</para> + </question> + <answer> + <para>You can use enscript for this. Use <command>enscript %s</command> to print everything on one page, or <command>enscript -U2 %s</command> for printing two logical pages on one physical page.</para> + </answer> + </qandaentry> + </qandaset> +</chapter>
\ No newline at end of file diff --git a/faq/en/faq_003.xml b/faq/en/faq_003.xml new file mode 100644 index 00000000..d83ede43 --- /dev/null +++ b/faq/en/faq_003.xml @@ -0,0 +1,282 @@ +<?xml version='1.0' encoding='UTF-8'?><chapter id="sylpheed-faq-3"> + <title>Sylpheed FAQ - Interface</title> + <qandaset id="faq-interface"> +<?dbhtml cellspacing="13px" ?> <qandaentry> + <question> + <para>How do I make Sylpheed display my language?</para> + </question> + <answer> + <para>You have to set some environment variables, such as + <envar>LANG</envar>, <envar>LC_CTYPE</envar>, <envar>LC_MESSAGES</envar> to your local language. + Usually <envar>LANG</envar> (or <envar>LC_ALL</envar>) is sufficient. Note that modern distributions and operating systems do this for you automatically.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>I don't like the default font. Can I change that?</para> + </question> + <answer> + <para>Yes. In <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Common preferences...</guimenuitem> + </menuchoice>, under the + <guimenuitem>Display</guimenuitem> tab.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>There are too many columns in the message list!</para> + </question> + <answer> + <para>In <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Common preferences...</guimenuitem> + </menuchoice> under the + <guimenuitem>Display</guimenuitem> tab, you can press the button <guibutton>Set display item of summary...</guibutton>. That pops up a screen with all the + options you can show or leave out of the message + list.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How do I disable or enable the alternating row colors in the message list?</para> + </question> + <answer> + <para>Under UNIX, you can directly edit the appropriate hidden setting stored in the <filename>$HOME/.sylpheed-2.0/sylpheedrc</filename> configuration file by changing the setting value to 0, or 1, respectively (default is on, i.e. 1): </para> + <programlisting>enable_rules_hint=0</programlisting> + <tip> + <para>There are various other hidden settings that can be adjusted in your <filename>sylpheedrc</filename> configuration file, see the <filename>README</filename> file for details.</para> + </tip> + <para>The above does not work under Windows, however, so you have to edit the <filename>C:\Program Files\Sylpheed\share\themes\MS-Windows\gtk-2.0\gtkrc</filename> file and set the following setting to 1, or 0, respectively (default is off under Windows, i.e. 0):</para> + <programlisting>GtkTreeView::allow-rules = 1</programlisting> + <note> + <para>Since the hidden setting described above is not stored within your user profile under Windows, it may be overwritten when installing a new version of Sylpheed. To avoid this at least partially, keep a backup copy of the <filename>gtkrc</filename> file somewhere safe.</para> + </note> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Can I use a different editor to write my mails?</para> + </question> + <answer> + <para>You can. In <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Common preferences</guimenuitem> + </menuchoice>, under + the <guimenuitem>Details</guimenuitem> and <guimenuitem>External commands</guimenuitem> tabs, 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 <parameter>-e</parameter> parameter in front of + the editor. E.g.: <command>rxvt -e vi %s</command>.</para> + <para>Also, make sure that you have checked <guilabel>Automatically launch the external editor</guilabel> in <menuchoice> + <guimenuitem>Common preferences</guimenuitem> + <guimenuitem>Compose</guimenuitem> + <guimenuitem>Editor</guimenuitem> + </menuchoice>, if you want the editor of your choice to be launched every time you begin composing a message.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How to change the font size in the Sylpheed interface?</para> + </question> + <answer> + <para>You can set the GTK+ font by <filename>$HOME/.gtkrc-2.0</filename>, or + <filename>$HOME/.gtkrc-2.0.mine</filename>, + (which is included by <filename>$HOME/.gtkrc-2.0</filename>). + For example:</para> + <programlisting>style "default" { + font = "-adobe-helvetica-medium-r-normal--12-*-*-*-*-*-iso8859-1 " +} +widget_class "*" style "default" +</programlisting> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Sylpheed saves my outgoing mail (in Outbox). Can I make it stop doing that?</para> + </question> + <answer> + <para>In <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Common preferences...</guimenuitem> + </menuchoice>, there is a + checkbox <guilabel>Save sent message to outbox</guilabel>. Uncheck it, + and it's solved.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How can I change the key bindings (hotkeys) in Sylpheed?</para> + </question> + <answer> + <para>Unlike Sylpheed 1.x, Sylpheed 2.x and 3.x doesn't allow direct modification of the menu shortcuts by default. Nevertheless, you can use the following methods to configure them:</para> + <orderedlist> + <listitem> + <para><emphasis>Using GNOME 2.8 or later:</emphasis> run gconf-editor from <menuchoice> + <guimenu>Applications</guimenu> + <guisubmenu>System Tools</guisubmenu> + <guimenuitem>Configuration Editor</guimenuitem> + </menuchoice>. Select <menuchoice> + <guimenu>desktop</guimenu> + <guisubmenu>gnome</guisubmenu> + <guisubmenu>interface</guisubmenu> + </menuchoice> and check <guilabel>can-change-accels</guilabel> there.</para> + </listitem> + <listitem> + <para><emphasis>Using GNOME before 2.8, or other environments:</emphasis> add the following line to the file <filename>~/.gtkrc-2.0</filename> (or create a new one, if it doesn't exist):</para> + <programlisting>gtk-can-change-accels = 1</programlisting> + </listitem> + <listitem> + <para>When Sylpheed is not running, directly edit <filename>~/.sylpheed-2.0/menurc</filename> with a text editor.</para> + </listitem> + </orderedlist> + <para>After that, the key binding change itself 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 <keycombo> + <keycap>Ctrl</keycap> + <keycap>Y</keycap> + </keycombo>. Click the + <guimenu>Message</guimenu> menu and move the mouse over <guimenuitem>Send all messages</guimenuitem>. Now you press <keycombo> + <keycap>Ctrl</keycap> + <keycap>Y</keycap> + </keycombo>. Immediately the menu + text is updated and the function is in place. Please + note that a previous function that <keycombo> + <keycap>Ctrl</keycap> + <keycap>Y</keycap> + </keycombo> 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 <keycap>Delete</keycap> key on the menu item. + Then the key binding is removed.</para> + <para>Also see <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Common preferences...</guimenuitem> + <guimenuitem>Details</guimenuitem> + <guimenuitem>Interface</guimenuitem> + <guilabel>Set key bindings...</guilabel> + </menuchoice> where you are able to reset the Default key bindings, or use other predefined key bindings.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Can I close windows without the mouse?</para> + </question> + <answer> + <para>Of course! Not all windows, but by pressing <keycap>Escape</keycap>, + you can close the address book, the window of viewing + a mail source (<menuchoice> + <guimenu>View</guimenu> + <guimenuitem>Message source</guimenuitem> + </menuchoice>), the window of + viewing the headers, and several others. Just give + it a try and you will find all of them.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Can I change the way the date is displayed in the message summary?</para> + </question> + <answer> + <para>As of 0.4.65 you can. The options are:</para> + <programlisting> %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</programlisting> + <para>For more information, go to the <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Common preferences</guimenuitem> + <guimenuitem>Display</guimenuitem> + <guimenuitem>General</guimenuitem> + </menuchoice> and choose the <guibutton>...</guibutton> labeled button. +For more options, see <command>man 3 strftime</command>.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Why can't I see the compface pictures?</para> + </question> + <answer> + <para>You need to enable displaying of the header pane in the + general preferences.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>I still can't see the pictures. Why not?</para> + </question> + <answer> + <para>You may not have compiled in Compface support. See the appropriate question in the Installation and Configuration section.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Why does the URL launcher not launch my web browser?</para> + </question> + <answer> + <para>You need to double click the URL. +Also, check that you have configured your web browser correctly in <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Common preferences...</guimenuitem> + <guimenuitem> Details</guimenuitem> + <guimenuitem>External commands</guimenuitem> + </menuchoice>. </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Attachments with spaces in the name won't open!</para> + </question> + <answer> + <para>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 <parameter>%s</parameter> +parameter. Example: <command>gedit '%s'</command></para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Where is the Bcc when I compose a mail?</para> + </question> + <answer> + <para>Open <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Preferences for current account...</guimenuitem> + <guimenuitem>Compose</guimenuitem> + </menuchoice>. There you can check the <guilabel>Bcc</guilabel> checkbox and optionally enter an email address.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How do I change the toolbar?</para> + </question> + <answer> + <para>Go to <menuchoice> + <guimenu>View</guimenu> + <guimenuitem>Customize toolbar...</guimenuitem> + </menuchoice> and select items from the <guilabel>Available items</guilabel> list to be displayed on the toolbar. You can modify the order by using the <guibutton>Up</guibutton> or <guibutton>Down</guibutton> button. The customization dialog also offers you to revert your modifications to default.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>Why isn't the next message displayed when I delete a message? </para> + </question> + <answer> + <para>Go to <menuchoice> + <guimenu>Configuration</guimenu> + <guimenuitem>Common preferences...</guimenuitem> + <guimenuitem>Details</guimenuitem> + <guimenuitem>Interface</guimenuitem> + </menuchoice>, and select <guilabel>Always open messages in summary when selected</guilabel>. </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>How can I remove mailing list information from Subject headers?</para> + </question> + <answer> + <para>Very often, when you are subscribed to a mailing list, you will store each message from that list in a folder dedicated to that list. Depending on remote software solution and configuration, mailing lists tend to include some words in the Subject header to identify the messages, optionally accompanied with a message number, for instance <literal>[sylpheed:33101]</literal>. These additions do not provide useful info if you have organized your folders as described, but Sylpheed allows you to disable displaying the additions in summary, and/or, if you wish, delete the additions on reply.</para> + <para>To do that, right-click on a folder from the folder tree, and select <guimenuitem>Properties...</guimenuitem> In the <guilabel>Folder properties</guilabel> dialog, check <guilabel>Don't display [...] or (...) at the beginning of subject in summary</guilabel>, or <guilabel>Delete [...] or (...) at the beginning of subject on reply</guilabel>, respectively.</para> + </answer> + </qandaentry> + </qandaset> +</chapter>
\ No newline at end of file diff --git a/faq/en/fdl.xml b/faq/en/fdl.xml new file mode 100644 index 00000000..b4d6c670 --- /dev/null +++ b/faq/en/fdl.xml @@ -0,0 +1,383 @@ +<?xml version='1.0' encoding='UTF-8'?> +<appendix id="sylpheed-faq-4"> + <appendixinfo> + <title>GNU Free Documentation License</title> + <pubdate>Version 1.2, November 2002</pubdate> + <copyright> + <year>2000,2001,2002</year> + <holder>Free Software Foundation, Inc.</holder> + </copyright> + <legalnotice id="gfdl-legalnotice"> + <para><address>Free Software Foundation, Inc. <street>51 Franklin St, Fifth Floor</street>, <city>Boston</city>, <state>MA</state><postcode>02110-1301</postcode><country>USA</country></address></para> + <para>Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed.</para> + </legalnotice> + <releaseinfo>Version 1.2, November 2002</releaseinfo> + </appendixinfo> + <title>GNU Free Documentation License</title> + <section id="gfdl-0"> + <title>PREAMBLE</title> + <para>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.</para> + <para>This License is a kind of "copyleft", which means that derivative +works of the document must themselves be free in the same sense. It +complements the GNU General Public License, which is a copyleft license +designed for free software.</para> + <para>We have designed this License in order to use it for manuals for +free software, because free software needs free documentation: a free +program should come with manuals providing the same freedoms that the +software does. But this License is not limited to software manuals; it +can be used for any textual work, regardless of subject matter or +whether it is published as a printed book. We recommend this License +principally for works whose purpose is instruction or reference.</para> + </section> + <section id="gfdl-1"> + <title>APPLICABILITY AND DEFINITIONS</title> + <para id="gfdl-doc">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.</para> + <para id="gfdl-mod-ver">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.</para> + <para id="gfdl-secnd-sect">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.</para> + <para id="gfdl-inv-sect">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.</para> + <para id="gfdl-cov-text">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.</para> + <para id="gfdl-transparent">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".</para> + <para>Examples of suitable formats for Transparent copies include plain +ASCII without markup, Texinfo input format, LaTeX input format, SGML or +XML using a publicly available DTD, and standard-conforming simple HTML, +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.</para> + <para id="gfdl-title-page">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.</para> + <para id="gfdl-entitled">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.</para> + <para>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.</para> + </section> + <section id="gfdl-2"> + <title>VERBATIM COPYING</title> + <para>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. +</para> + <para>You may also lend copies, under the same conditions stated above, +and you may publicly display copies.</para> + </section> + <section id="gfdl-3"> + <title>COPYING IN QUANTITY</title> + <para>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.</para> + <para>If the required texts for either cover are too voluminous to fit +legibly, you should put the first ones listed (as many as fit +reasonably) on the actual cover, and continue the rest onto adjacent +pages.</para> + <para>If you publish or distribute 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.</para> + <para>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.</para> + </section> + <section id="gfdl-4"> + <title>MODIFICATIONS</title> + <para>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:</para> + <orderedlist numeration="upperalpha" id="gfdl-modif-cond"> + <title>GNU FDL Modification Conditions</title> + <listitem> + <simpara>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. </simpara> + </listitem> + <listitem> + <simpara>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 fewer than five), unless they release you from this requirement. </simpara> + </listitem> + <listitem> + <simpara>State on the Title page the name of the publisher of the Modified Version, as the publisher.</simpara> + </listitem> + <listitem> + <simpara>Preserve all the copyright notices of the Document. </simpara> + </listitem> + <listitem> + <simpara>Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. </simpara> + </listitem> + <listitem> + <simpara>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 <link linkend="gfdl-addendum">Addendum</link> below. </simpara> + </listitem> + <listitem> + <simpara>Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.</simpara> + </listitem> + <listitem> + <simpara>Include an unaltered copy of this License. </simpara> + </listitem> + <listitem> + <simpara>Preserve the section Entitled "History", Preserve 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. </simpara> + </listitem> + <listitem> + <simpara>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. </simpara> + </listitem> + <listitem> + <simpara>For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. </simpara> + </listitem> + <listitem> + <simpara>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. </simpara> + </listitem> + <listitem> + <simpara>Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. </simpara> + </listitem> + <listitem> + <simpara>Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section. </simpara> + </listitem> + <listitem> + <simpara>Preserve any Warranty Disclaimers. </simpara> + </listitem> + </orderedlist> + <para>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.</para> + <para>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.</para> + <para>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.</para> + <para>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.</para> + </section> + <section id="gfdl-5"> + <title>COMBINING DOCUMENTS</title> + <para>You may combine the Document with other documents released under +this License, under the terms defined in <link linkend="gfdl-4">section 4</link> 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.</para> + <para>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.</para> + <para>In the combination, you must combine any sections Entitled +"History" in the various original documents, forming one section +Entitled "History"; likewise combine any sections Entitled +"Acknowledgements", and any sections Entitled "Dedications". You must +delete all sections Entitled "Endorsements".</para> + </section> + <section id="gfdl-6"> + <title>COLLECTIONS OF DOCUMENTS</title> + <para>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.</para> + <para>You may extract a single document from such a collection, and +distribute it individually under this License, provided you insert a +copy of this License into the extracted document, and follow this +License in all other respects regarding verbatim copying of that +document.</para> + </section> + <section id="gfdl-7"> + <title>AGGREGATION WITH INDEPENDENT WORKS</title> + <para>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.</para> + <para>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.</para> + </section> + <section id="gfdl-8"> + <title>TRANSLATION</title> + <para>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.</para> + <para>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.</para> + </section> + <section id="gfdl-9"> + <title>TERMINATION</title> + <para>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.</para> + </section> + <section id="gfdl-10"> + <title>FUTURE REVISIONS OF THIS LICENSE</title> + <para>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/.</para> + <para>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.</para> + </section> + <section id="gfdl-addendum"> + <title>ADDENDUM: How to use this License for your documents</title> + <para>To use this License in a document you have written, include a copy +of the License in the document and put the following copyright and +license notices just after the title page:</para> + <blockquote id="copyright-sample"> + <title>Sample Invariant Sections list</title> + <para> + 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". +</para> + </blockquote> + <para>If you have Invariant Sections, Front-Cover Texts and Back-Cover +Texts, replace the "with...Texts." line with this:</para> + <blockquote id="inv-cover-sample"> + <title>Sample Invariant Sections list</title> + <para> + with the Invariant Sections being LIST THEIR TITLES, with the + Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. +</para> + </blockquote> + <para>If you have Invariant Sections without Cover Texts, or some other +combination of the three, merge those two alternatives to suit the +situation.</para> + <para>If your document contains nontrivial examples of program code, we +recommend releasing these examples in parallel under your choice of free +software license, such as the GNU General Public License, to permit +their use in free software.</para> + </section> +</appendix> |