summaryrefslogtreecommitdiff
path: root/faq/en
diff options
context:
space:
mode:
authorSimeon Simeonov2018-02-26 11:23:00 +0100
committerSimeon Simeonov2018-02-26 11:23:00 +0100
commit0b3cbf57875fd692e4ba0b336fefa4bee1ed00dc (patch)
treeaf916a30553c78ce9d4f2d8658656a175c5b6921 /faq/en
Initial commit for sylpheed 3.7.0
Diffstat (limited to 'faq/en')
-rw-r--r--faq/en/COPYING397
-rw-r--r--faq/en/ChangeLog92
-rw-r--r--faq/en/LICENSE9
-rw-r--r--faq/en/Makefile.am18
-rw-r--r--faq/en/Makefile.in560
-rw-r--r--faq/en/NEWS137
-rw-r--r--faq/en/faq.xml94
-rw-r--r--faq/en/faq_001.xml591
-rw-r--r--faq/en/faq_002.xml606
-rw-r--r--faq/en/faq_003.xml309
-rw-r--r--faq/en/fdl.xml383
-rw-r--r--faq/en/sylpheed-faq-1.html964
-rw-r--r--faq/en/sylpheed-faq-2.html913
-rw-r--r--faq/en/sylpheed-faq-3.html432
-rw-r--r--faq/en/sylpheed-faq-4.html601
-rw-r--r--faq/en/sylpheed-faq.html161
16 files changed, 6267 insertions, 0 deletions
diff --git a/faq/en/COPYING b/faq/en/COPYING
new file mode 100644
index 0000000..4a0fe1c
--- /dev/null
+++ b/faq/en/COPYING
@@ -0,0 +1,397 @@
1 GNU Free Documentation License
2 Version 1.2, November 2002
3
4
5 Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
6 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
7 Everyone is permitted to copy and distribute verbatim copies
8 of this license document, but changing it is not allowed.
9
10
110. PREAMBLE
12
13The purpose of this License is to make a manual, textbook, or other
14functional and useful document "free" in the sense of freedom: to
15assure everyone the effective freedom to copy and redistribute it,
16with or without modifying it, either commercially or noncommercially.
17Secondarily, this License preserves for the author and publisher a way
18to get credit for their work, while not being considered responsible
19for modifications made by others.
20
21This License is a kind of "copyleft", which means that derivative
22works of the document must themselves be free in the same sense. It
23complements the GNU General Public License, which is a copyleft
24license designed for free software.
25
26We have designed this License in order to use it for manuals for free
27software, because free software needs free documentation: a free
28program should come with manuals providing the same freedoms that the
29software does. But this License is not limited to software manuals;
30it can be used for any textual work, regardless of subject matter or
31whether it is published as a printed book. We recommend this License
32principally for works whose purpose is instruction or reference.
33
34
351. APPLICABILITY AND DEFINITIONS
36
37This License applies to any manual or other work, in any medium, that
38contains a notice placed by the copyright holder saying it can be
39distributed under the terms of this License. Such a notice grants a
40world-wide, royalty-free license, unlimited in duration, to use that
41work under the conditions stated herein. The "Document", below,
42refers to any such manual or work. Any member of the public is a
43licensee, and is addressed as "you". You accept the license if you
44copy, modify or distribute the work in a way requiring permission
45under copyright law.
46
47A "Modified Version" of the Document means any work containing the
48Document or a portion of it, either copied verbatim, or with
49modifications and/or translated into another language.
50
51A "Secondary Section" is a named appendix or a front-matter section of
52the Document that deals exclusively with the relationship of the
53publishers or authors of the Document to the Document's overall subject
54(or to related matters) and contains nothing that could fall directly
55within that overall subject. (Thus, if the Document is in part a
56textbook of mathematics, a Secondary Section may not explain any
57mathematics.) The relationship could be a matter of historical
58connection with the subject or with related matters, or of legal,
59commercial, philosophical, ethical or political position regarding
60them.
61
62The "Invariant Sections" are certain Secondary Sections whose titles
63are designated, as being those of Invariant Sections, in the notice
64that says that the Document is released under this License. If a
65section does not fit the above definition of Secondary then it is not
66allowed to be designated as Invariant. The Document may contain zero
67Invariant Sections. If the Document does not identify any Invariant
68Sections then there are none.
69
70The "Cover Texts" are certain short passages of text that are listed,
71as Front-Cover Texts or Back-Cover Texts, in the notice that says that
72the Document is released under this License. A Front-Cover Text may
73be at most 5 words, and a Back-Cover Text may be at most 25 words.
74
75A "Transparent" copy of the Document means a machine-readable copy,
76represented in a format whose specification is available to the
77general public, that is suitable for revising the document
78straightforwardly with generic text editors or (for images composed of
79pixels) generic paint programs or (for drawings) some widely available
80drawing editor, and that is suitable for input to text formatters or
81for automatic translation to a variety of formats suitable for input
82to text formatters. A copy made in an otherwise Transparent file
83format whose markup, or absence of markup, has been arranged to thwart
84or discourage subsequent modification by readers is not Transparent.
85An image format is not Transparent if used for any substantial amount
86of text. A copy that is not "Transparent" is called "Opaque".
87
88Examples of suitable formats for Transparent copies include plain
89ASCII without markup, Texinfo input format, LaTeX input format, SGML
90or XML using a publicly available DTD, and standard-conforming simple
91HTML, PostScript or PDF designed for human modification. Examples of
92transparent image formats include PNG, XCF and JPG. Opaque formats
93include proprietary formats that can be read and edited only by
94proprietary word processors, SGML or XML for which the DTD and/or
95processing tools are not generally available, and the
96machine-generated HTML, PostScript or PDF produced by some word
97processors for output purposes only.
98
99The "Title Page" means, for a printed book, the title page itself,
100plus such following pages as are needed to hold, legibly, the material
101this License requires to appear in the title page. For works in
102formats which do not have any title page as such, "Title Page" means
103the text near the most prominent appearance of the work's title,
104preceding the beginning of the body of the text.
105
106A section "Entitled XYZ" means a named subunit of the Document whose
107title either is precisely XYZ or contains XYZ in parentheses following
108text that translates XYZ in another language. (Here XYZ stands for a
109specific section name mentioned below, such as "Acknowledgements",
110"Dedications", "Endorsements", or "History".) To "Preserve the Title"
111of such a section when you modify the Document means that it remains a
112section "Entitled XYZ" according to this definition.
113
114The Document may include Warranty Disclaimers next to the notice which
115states that this License applies to the Document. These Warranty
116Disclaimers are considered to be included by reference in this
117License, but only as regards disclaiming warranties: any other
118implication that these Warranty Disclaimers may have is void and has
119no effect on the meaning of this License.
120
121
1222. VERBATIM COPYING
123
124You may copy and distribute the Document in any medium, either
125commercially or noncommercially, provided that this License, the
126copyright notices, and the license notice saying this License applies
127to the Document are reproduced in all copies, and that you add no other
128conditions whatsoever to those of this License. You may not use
129technical measures to obstruct or control the reading or further
130copying of the copies you make or distribute. However, you may accept
131compensation in exchange for copies. If you distribute a large enough
132number of copies you must also follow the conditions in section 3.
133
134You may also lend copies, under the same conditions stated above, and
135you may publicly display copies.
136
137
1383. COPYING IN QUANTITY
139
140If you publish printed copies (or copies in media that commonly have
141printed covers) of the Document, numbering more than 100, and the
142Document's license notice requires Cover Texts, you must enclose the
143copies in covers that carry, clearly and legibly, all these Cover
144Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
145the back cover. Both covers must also clearly and legibly identify
146you as the publisher of these copies. The front cover must present
147the full title with all words of the title equally prominent and
148visible. You may add other material on the covers in addition.
149Copying with changes limited to the covers, as long as they preserve
150the title of the Document and satisfy these conditions, can be treated
151as verbatim copying in other respects.
152
153If the required texts for either cover are too voluminous to fit
154legibly, you should put the first ones listed (as many as fit
155reasonably) on the actual cover, and continue the rest onto adjacent
156pages.
157
158If you publish or distribute Opaque copies of the Document numbering
159more than 100, you must either include a machine-readable Transparent
160copy along with each Opaque copy, or state in or with each Opaque copy
161a computer-network location from which the general network-using
162public has access to download using public-standard network protocols
163a complete Transparent copy of the Document, free of added material.
164If you use the latter option, you must take reasonably prudent steps,
165when you begin distribution of Opaque copies in quantity, to ensure
166that this Transparent copy will remain thus accessible at the stated
167location until at least one year after the last time you distribute an
168Opaque copy (directly or through your agents or retailers) of that
169edition to the public.
170
171It is requested, but not required, that you contact the authors of the
172Document well before redistributing any large number of copies, to give
173them a chance to provide you with an updated version of the Document.
174
175
1764. MODIFICATIONS
177
178You may copy and distribute a Modified Version of the Document under
179the conditions of sections 2 and 3 above, provided that you release
180the Modified Version under precisely this License, with the Modified
181Version filling the role of the Document, thus licensing distribution
182and modification of the Modified Version to whoever possesses a copy
183of it. In addition, you must do these things in the Modified Version:
184
185A. Use in the Title Page (and on the covers, if any) a title distinct
186 from that of the Document, and from those of previous versions
187 (which should, if there were any, be listed in the History section
188 of the Document). You may use the same title as a previous version
189 if the original publisher of that version gives permission.
190B. List on the Title Page, as authors, one or more persons or entities
191 responsible for authorship of the modifications in the Modified
192 Version, together with at least five of the principal authors of the
193 Document (all of its principal authors, if it has fewer than five),
194 unless they release you from this requirement.
195C. State on the Title page the name of the publisher of the
196 Modified Version, as the publisher.
197D. Preserve all the copyright notices of the Document.
198E. Add an appropriate copyright notice for your modifications
199 adjacent to the other copyright notices.
200F. Include, immediately after the copyright notices, a license notice
201 giving the public permission to use the Modified Version under the
202 terms of this License, in the form shown in the Addendum below.
203G. Preserve in that license notice the full lists of Invariant Sections
204 and required Cover Texts given in the Document's license notice.
205H. Include an unaltered copy of this License.
206I. Preserve the section Entitled "History", Preserve its Title, and add
207 to it an item stating at least the title, year, new authors, and
208 publisher of the Modified Version as given on the Title Page. If
209 there is no section Entitled "History" in the Document, create one
210 stating the title, year, authors, and publisher of the Document as
211 given on its Title Page, then add an item describing the Modified
212 Version as stated in the previous sentence.
213J. Preserve the network location, if any, given in the Document for
214 public access to a Transparent copy of the Document, and likewise
215 the network locations given in the Document for previous versions
216 it was based on. These may be placed in the "History" section.
217 You may omit a network location for a work that was published at
218 least four years before the Document itself, or if the original
219 publisher of the version it refers to gives permission.
220K. For any section Entitled "Acknowledgements" or "Dedications",
221 Preserve the Title of the section, and preserve in the section all
222 the substance and tone of each of the contributor acknowledgements
223 and/or dedications given therein.
224L. Preserve all the Invariant Sections of the Document,
225 unaltered in their text and in their titles. Section numbers
226 or the equivalent are not considered part of the section titles.
227M. Delete any section Entitled "Endorsements". Such a section
228 may not be included in the Modified Version.
229N. Do not retitle any existing section to be Entitled "Endorsements"
230 or to conflict in title with any Invariant Section.
231O. Preserve any Warranty Disclaimers.
232
233If the Modified Version includes new front-matter sections or
234appendices that qualify as Secondary Sections and contain no material
235copied from the Document, you may at your option designate some or all
236of these sections as invariant. To do this, add their titles to the
237list of Invariant Sections in the Modified Version's license notice.
238These titles must be distinct from any other section titles.
239
240You may add a section Entitled "Endorsements", provided it contains
241nothing but endorsements of your Modified Version by various
242parties--for example, statements of peer review or that the text has
243been approved by an organization as the authoritative definition of a
244standard.
245
246You may add a passage of up to five words as a Front-Cover Text, and a
247passage of up to 25 words as a Back-Cover Text, to the end of the list
248of Cover Texts in the Modified Version. Only one passage of
249Front-Cover Text and one of Back-Cover Text may be added by (or
250through arrangements made by) any one entity. If the Document already
251includes a cover text for the same cover, previously added by you or
252by arrangement made by the same entity you are acting on behalf of,
253you may not add another; but you may replace the old one, on explicit
254permission from the previous publisher that added the old one.
255
256The author(s) and publisher(s) of the Document do not by this License
257give permission to use their names for publicity for or to assert or
258imply endorsement of any Modified Version.
259
260
2615. COMBINING DOCUMENTS
262
263You may combine the Document with other documents released under this
264License, under the terms defined in section 4 above for modified
265versions, provided that you include in the combination all of the
266Invariant Sections of all of the original documents, unmodified, and
267list them all as Invariant Sections of your combined work in its
268license notice, and that you preserve all their Warranty Disclaimers.
269
270The combined work need only contain one copy of this License, and
271multiple identical Invariant Sections may be replaced with a single
272copy. If there are multiple Invariant Sections with the same name but
273different contents, make the title of each such section unique by
274adding at the end of it, in parentheses, the name of the original
275author or publisher of that section if known, or else a unique number.
276Make the same adjustment to the section titles in the list of
277Invariant Sections in the license notice of the combined work.
278
279In the combination, you must combine any sections Entitled "History"
280in the various original documents, forming one section Entitled
281"History"; likewise combine any sections Entitled "Acknowledgements",
282and any sections Entitled "Dedications". You must delete all sections
283Entitled "Endorsements".
284
285
2866. COLLECTIONS OF DOCUMENTS
287
288You may make a collection consisting of the Document and other documents
289released under this License, and replace the individual copies of this
290License in the various documents with a single copy that is included in
291the collection, provided that you follow the rules of this License for
292verbatim copying of each of the documents in all other respects.
293
294You may extract a single document from such a collection, and distribute
295it individually under this License, provided you insert a copy of this
296License into the extracted document, and follow this License in all
297other respects regarding verbatim copying of that document.
298
299
3007. AGGREGATION WITH INDEPENDENT WORKS
301
302A compilation of the Document or its derivatives with other separate
303and independent documents or works, in or on a volume of a storage or
304distribution medium, is called an "aggregate" if the copyright
305resulting from the compilation is not used to limit the legal rights
306of the compilation's users beyond what the individual works permit.
307When the Document is included in an aggregate, this License does not
308apply to the other works in the aggregate which are not themselves
309derivative works of the Document.
310
311If the Cover Text requirement of section 3 is applicable to these
312copies of the Document, then if the Document is less than one half of
313the entire aggregate, the Document's Cover Texts may be placed on
314covers that bracket the Document within the aggregate, or the
315electronic equivalent of covers if the Document is in electronic form.
316Otherwise they must appear on printed covers that bracket the whole
317aggregate.
318
319
3208. TRANSLATION
321
322Translation is considered a kind of modification, so you may
323distribute translations of the Document under the terms of section 4.
324Replacing Invariant Sections with translations requires special
325permission from their copyright holders, but you may include
326translations of some or all Invariant Sections in addition to the
327original versions of these Invariant Sections. You may include a
328translation of this License, and all the license notices in the
329Document, and any Warranty Disclaimers, provided that you also include
330the original English version of this License and the original versions
331of those notices and disclaimers. In case of a disagreement between
332the translation and the original version of this License or a notice
333or disclaimer, the original version will prevail.
334
335If a section in the Document is Entitled "Acknowledgements",
336"Dedications", or "History", the requirement (section 4) to Preserve
337its Title (section 1) will typically require changing the actual
338title.
339
340
3419. TERMINATION
342
343You may not copy, modify, sublicense, or distribute the Document except
344as expressly provided for under this License. Any other attempt to
345copy, modify, sublicense or distribute the Document is void, and will
346automatically terminate your rights under this License. However,
347parties who have received copies, or rights, from you under this
348License will not have their licenses terminated so long as such
349parties remain in full compliance.
350
351
35210. FUTURE REVISIONS OF THIS LICENSE
353
354The Free Software Foundation may publish new, revised versions
355of the GNU Free Documentation License from time to time. Such new
356versions will be similar in spirit to the present version, but may
357differ in detail to address new problems or concerns. See
358http://www.gnu.org/copyleft/.
359
360Each version of the License is given a distinguishing version number.
361If the Document specifies that a particular numbered version of this
362License "or any later version" applies to it, you have the option of
363following the terms and conditions either of that specified version or
364of any later version that has been published (not as a draft) by the
365Free Software Foundation. If the Document does not specify a version
366number of this License, you may choose any version ever published (not
367as a draft) by the Free Software Foundation.
368
369
370ADDENDUM: How to use this License for your documents
371
372To use this License in a document you have written, include a copy of
373the License in the document and put the following copyright and
374license notices just after the title page:
375
376 Copyright (c) YEAR YOUR NAME.
377 Permission is granted to copy, distribute and/or modify this document
378 under the terms of the GNU Free Documentation License, Version 1.2
379 or any later version published by the Free Software Foundation;
380 with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
381 A copy of the license is included in the section entitled "GNU
382 Free Documentation License".
383
384If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
385replace the "with...Texts." line with this:
386
387 with the Invariant Sections being LIST THEIR TITLES, with the
388 Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
389
390If you have Invariant Sections without Cover Texts, or some other
391combination of the three, merge those two alternatives to suit the
392situation.
393
394If your document contains nontrivial examples of program code, we
395recommend releasing these examples in parallel under your choice of
396free software license, such as the GNU General Public License,
397to permit their use in free software.
diff --git a/faq/en/ChangeLog b/faq/en/ChangeLog
new file mode 100644
index 0000000..b7bb11a
--- /dev/null
+++ b/faq/en/ChangeLog
@@ -0,0 +1,92 @@
12010-08-09 Petr Kovar <pknbe@volny.cz>
2
3 * NEWS: Prepare for the FAQ_EN_2_2 release.
4 * faq_001.xml: Minor fixes.
5 * faq_003.xml: Ditto.
6
72010-08-09 Petr Kovar <pknbe@volny.cz>
8
9 * faq.xml: Second round of updates with regard to Sylpheed 3.1.
10 * faq_001.xml: Ditto.
11 * faq_002.xml: Ditto.
12 * faq_003.xml: Ditto.
13
142010-08-04 Petr Kovar <pknbe@volny.cz>
15
16 * faq_001.xml: Some fixes to the recent updates.
17 * faq_002.xml: Ditto.
18 * faq_003.xml: Ditto.
19
202010-07-30 Petr Kovar <pknbe@volny.cz>
21
22 * COPYING: Add a copy of the GFDL 1.2 to distribute it within release
23 tarball.
24 * LICENSE: Add a legal notice to distribute it within release tarball.
25 * faq_001.xml: First round of updates with regard to Sylpheed 3.1.
26 * faq_002.xml: Ditto.
27 * faq_003.xml: Ditto.
28 * sylpheed-faq.sgml: Remove old SGML FAQ document.
29
302010-04-14 Petr Kovar <pknbe@volny.cz>
31
32 * NEWS: Prepare for the FAQ_EN_2_1 release.
33 * faq.xml: Prepare for the FAQ_EN_2_1 release.
34 * faq_001.xml: Minor edits.
35 * faq_002.xml: Ditto.
36 * faq_003.xml: Ditto.
37
382010-03-22 Petr Kovar <pknbe@volny.cz>
39
40 * faq.xml: Updated with regard to Sylpheed 3.0.1.
41 * faq_001.xml: Ditto.
42 * faq_002.xml: Ditto.
43 * faq_003.xml: Ditto.
44
452009-10-02 Petr Kovar <pknbe@volny.cz>
46
47 * NEWS: Add the file & prepare for the FAQ_EN_2_0 release.
48 * faq.xml: Prepare for the FAQ_EN_2_0 release.
49
502009-10-02 Petr Kovar <pknbe@volny.cz>
51
52 * faq_001.xml: Minor addition.
53
542009-10-01 Petr Kovar <pknbe@volny.cz>
55
56 * faq.xml: Expanded question about key bindings, and other minor
57 edits across the FAQ.
58 * faq_001.xml: Ditto.
59 * faq_002.xml: Ditto.
60 * faq_003.xml: Ditto.
61 * faq_004.xml: Delete the obsolete file.
62
632009-09-24 Petr Kovar <pknbe@volny.cz>
64
65 * faq.xml: Change revision numbers to respect 'beta' and
66 'stable'.
67 * faq_001.xml: Fix typo, thanks to Randy Dunlap.
68
692009-09-18 Petr Kovar <pknbe@volny.cz>
70
71 * *.xml: Updated several questions across the FAQ to conform
72 with Sylpheed 2.7.1, added couple of new ones.
73
742009-08-31 Petr Kovar <pknbe@volny.cz>
75
76 * *.xml: Even better formatting of qandaset tables. Markup
77 cleaning.
78
792009-08-27 Petr Kovar <pknbe@volny.cz>
80
81 * *.xml: Better formatting of qandaset tables. Still using
82 the shade.verbatim parameter for the IE compatibility's sake.
83 qandaset TOCs are now generated in each FAQ chunk.
84
852009-08-23 Petr Kovar <pknbe@volny.cz>
86
87 * *.xml: First round of very basic FAQ updates.
88
892009-08-12 Petr Kovar <pknbe@volny.cz>
90
91 * *.xml: Finished porting to DocBook XML.
92 * ChangeLog: Add the file.
diff --git a/faq/en/LICENSE b/faq/en/LICENSE
new file mode 100644
index 0000000..bb2cce1
--- /dev/null
+++ b/faq/en/LICENSE
@@ -0,0 +1,9 @@
1Sylpheed FAQ
2
3 Copyright (c) 2010 The Sylpheed Documentation Project.
4 Permission is granted to copy, distribute and/or modify this document
5 under the terms of the GNU Free Documentation License, Version 1.2
6 or any later version published by the Free Software Foundation;
7 with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
8 A copy of the license is included in the file "COPYING".
9
diff --git a/faq/en/Makefile.am b/faq/en/Makefile.am
new file mode 100644
index 0000000..eaa74da
--- /dev/null
+++ b/faq/en/Makefile.am
@@ -0,0 +1,18 @@
1faqdatadir = $(faqdir)/en
2
3faqdata_DATA = \
4 sylpheed-faq-1.html \
5 sylpheed-faq-2.html \
6 sylpheed-faq-3.html \
7 sylpheed-faq-4.html \
8 sylpheed-faq.html
9
10# generated by `ls -1 | sed -e 's/\(.*\)/ \1 \'`
11
12EXTRA_DIST = $(faqdata_DATA) \
13 faq.xml \
14 faq_001.xml \
15 faq_002.xml \
16 faq_003.xml \
17 fdl.xml \
18 LICENSE
diff --git a/faq/en/Makefile.in b/faq/en/Makefile.in
new file mode 100644
index 0000000..1c970de
--- /dev/null
+++ b/faq/en/Makefile.in
@@ -0,0 +1,560 @@
1# Makefile.in generated by automake 1.14.1 from Makefile.am.
2# @configure_input@
3
4# Copyright (C) 1994-2013 Free Software Foundation, Inc.
5
6# This Makefile.in is free software; the Free Software Foundation
7# gives unlimited permission to copy and/or distribute it,
8# with or without modifications, as long as this notice is preserved.
9
10# This program is distributed in the hope that it will be useful,
11# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
12# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
13# PARTICULAR PURPOSE.
14
15@SET_MAKE@
16
17VPATH = @srcdir@
18am__is_gnu_make = test -n '$(MAKEFILE_LIST)' && test -n '$(MAKELEVEL)'
19am__make_running_with_option = \
20 case $${target_option-} in \
21 ?) ;; \
22 *) echo "am__make_running_with_option: internal error: invalid" \
23 "target option '$${target_option-}' specified" >&2; \
24 exit 1;; \
25 esac; \
26 has_opt=no; \
27 sane_makeflags=$$MAKEFLAGS; \
28 if $(am__is_gnu_make); then \
29 sane_makeflags=$$MFLAGS; \
30 else \
31 case $$MAKEFLAGS in \
32 *\\[\ \ ]*) \
33 bs=\\; \
34 sane_makeflags=`printf '%s\n' "$$MAKEFLAGS" \
35 | sed "s/$$bs$$bs[$$bs $$bs ]*//g"`;; \
36 esac; \
37 fi; \
38 skip_next=no; \
39 strip_trailopt () \
40 { \
41 flg=`printf '%s\n' "$$flg" | sed "s/$$1.*$$//"`; \
42 }; \
43 for flg in $$sane_makeflags; do \
44 test $$skip_next = yes && { skip_next=no; continue; }; \
45 case $$flg in \
46 *=*|--*) continue;; \
47 -*I) strip_trailopt 'I'; skip_next=yes;; \
48 -*I?*) strip_trailopt 'I';; \
49 -*O) strip_trailopt 'O'; skip_next=yes;; \
50 -*O?*) strip_trailopt 'O';; \
51 -*l) strip_trailopt 'l'; skip_next=yes;; \
52 -*l?*) strip_trailopt 'l';; \
53 -[dEDm]) skip_next=yes;; \
54 -[JT]) skip_next=yes;; \
55 esac; \
56 case $$flg in \
57 *$$target_option*) has_opt=yes; break;; \
58 esac; \
59 done; \
60 test $$has_opt = yes
61am__make_dryrun = (target_option=n; $(am__make_running_with_option))
62am__make_keepgoing = (target_option=k; $(am__make_running_with_option))
63pkgdatadir = $(datadir)/@PACKAGE@
64pkgincludedir = $(includedir)/@PACKAGE@
65pkglibdir = $(libdir)/@PACKAGE@
66pkglibexecdir = $(libexecdir)/@PACKAGE@
67am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
68install_sh_DATA = $(install_sh) -c -m 644
69install_sh_PROGRAM = $(install_sh) -c
70install_sh_SCRIPT = $(install_sh) -c
71INSTALL_HEADER = $(INSTALL_DATA)
72transform = $(program_transform_name)
73NORMAL_INSTALL = :
74PRE_INSTALL = :
75POST_INSTALL = :
76NORMAL_UNINSTALL = :
77PRE_UNINSTALL = :
78POST_UNINSTALL = :
79build_triplet = @build@
80host_triplet = @host@
81target_triplet = @target@
82subdir = faq/en
83DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/Makefile.am \
84 $(top_srcdir)/mkinstalldirs COPYING ChangeLog NEWS
85ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
86am__aclocal_m4_deps = $(top_srcdir)/ac/aclocal-include.m4 \
87 $(top_srcdir)/ac/gnupg-check-typedef.m4 \
88 $(top_srcdir)/configure.ac
89am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
90 $(ACLOCAL_M4)
91mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
92CONFIG_HEADER = $(top_builddir)/config.h
93CONFIG_CLEAN_FILES =
94CONFIG_CLEAN_VPATH_FILES =
95AM_V_P = $(am__v_P_@AM_V@)
96am__v_P_ = $(am__v_P_@AM_DEFAULT_V@)
97am__v_P_0 = false
98am__v_P_1 = :
99AM_V_GEN = $(am__v_GEN_@AM_V@)
100am__v_GEN_ = $(am__v_GEN_@AM_DEFAULT_V@)
101am__v_GEN_0 = @echo " GEN " $@;
102am__v_GEN_1 =
103AM_V_at = $(am__v_at_@AM_V@)
104am__v_at_ = $(am__v_at_@AM_DEFAULT_V@)
105am__v_at_0 = @
106am__v_at_1 =
107SOURCES =
108DIST_SOURCES =
109am__can_run_installinfo = \
110 case $$AM_UPDATE_INFO_DIR in \
111 n|no|NO) false;; \
112 *) (install-info --version) >/dev/null 2>&1;; \
113 esac
114am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`;
115am__vpath_adj = case $$p in \
116 $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \
117 *) f=$$p;; \
118 esac;
119am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`;
120am__install_max = 40
121am__nobase_strip_setup = \
122 srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'`
123am__nobase_strip = \
124 for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||"
125am__nobase_list = $(am__nobase_strip_setup); \
126 for p in $$list; do echo "$$p $$p"; done | \
127 sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \
128 $(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \
129 if (++n[$$2] == $(am__install_max)) \
130 { print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \
131 END { for (dir in files) print dir, files[dir] }'
132am__base_list = \
133 sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \
134 sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g'
135am__uninstall_files_from_dir = { \
136 test -z "$$files" \
137 || { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \
138 || { echo " ( cd '$$dir' && rm -f" $$files ")"; \
139 $(am__cd) "$$dir" && rm -f $$files; }; \
140 }
141am__installdirs = "$(DESTDIR)$(faqdatadir)"
142DATA = $(faqdata_DATA)
143am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) $(LISP)
144DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
145ACLOCAL = @ACLOCAL@
146ALLOCA = @ALLOCA@
147AMTAR = @AMTAR@
148AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@
149AR = @AR@
150AUTOCONF = @AUTOCONF@
151AUTOHEADER = @AUTOHEADER@
152AUTOMAKE = @AUTOMAKE@
153AWK = @AWK@
154BUILD_REVISION = @BUILD_REVISION@
155CATALOGS = @CATALOGS@
156CATOBJEXT = @CATOBJEXT@
157CC = @CC@
158CCDEPMODE = @CCDEPMODE@
159CFLAGS = @CFLAGS@
160CPP = @CPP@
161CPPFLAGS = @CPPFLAGS@
162CYGPATH_W = @CYGPATH_W@
163DATADIRNAME = @DATADIRNAME@
164DEFS = @DEFS@
165DEPDIR = @DEPDIR@
166DEVEL_VERSION = @DEVEL_VERSION@
167DLLTOOL = @DLLTOOL@
168DSYMUTIL = @DSYMUTIL@
169DUMPBIN = @DUMPBIN@
170ECHO_C = @ECHO_C@
171ECHO_N = @ECHO_N@
172ECHO_T = @ECHO_T@
173EGREP = @EGREP@
174EXEEXT = @EXEEXT@
175EXTRA_VERSION = @EXTRA_VERSION@
176FGREP = @FGREP@
177GETTEXT_PACKAGE = @GETTEXT_PACKAGE@
178GLIB_CFLAGS = @GLIB_CFLAGS@
179GLIB_COMPILE_RESOURCES = @GLIB_COMPILE_RESOURCES@
180GLIB_GENMARSHAL = @GLIB_GENMARSHAL@
181GLIB_LIBS = @GLIB_LIBS@
182GLIB_MKENUMS = @GLIB_MKENUMS@
183GMOFILES = @GMOFILES@
184GMSGFMT = @GMSGFMT@
185GOBJECT_QUERY = @GOBJECT_QUERY@
186GPGME_CFLAGS = @GPGME_CFLAGS@
187GPGME_CONFIG = @GPGME_CONFIG@
188GPGME_LIBS = @GPGME_LIBS@
189GREP = @GREP@
190GTK_CFLAGS = @GTK_CFLAGS@
191GTK_LIBS = @GTK_LIBS@
192INSTALL = @INSTALL@
193INSTALL_DATA = @INSTALL_DATA@
194INSTALL_PROGRAM = @INSTALL_PROGRAM@
195INSTALL_SCRIPT = @INSTALL_SCRIPT@
196INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
197INSTOBJEXT = @INSTOBJEXT@
198INTLLIBS = @INTLLIBS@
199LD = @LD@
200LDAP_LIBS = @LDAP_LIBS@
201LDFLAGS = @LDFLAGS@
202LEX = @LEX@
203LEXLIB = @LEXLIB@
204LEX_OUTPUT_ROOT = @LEX_OUTPUT_ROOT@
205LIBICONV = @LIBICONV@
206LIBOBJS = @LIBOBJS@
207LIBS = @LIBS@
208LIBSYLPH_CFLAGS = @LIBSYLPH_CFLAGS@
209LIBSYLPH_LIBS = @LIBSYLPH_LIBS@
210LIBTOOL = @LIBTOOL@
211LIPO = @LIPO@
212LN_S = @LN_S@
213LTLIBICONV = @LTLIBICONV@
214LTLIBOBJS = @LTLIBOBJS@
215LT_AGE = @LT_AGE@
216LT_CURRENT = @LT_CURRENT@
217LT_RELEASE = @LT_RELEASE@
218LT_REVISION = @LT_REVISION@
219MAINT = @MAINT@
220MAJOR_VERSION = @MAJOR_VERSION@
221MAKEINFO = @MAKEINFO@
222MANIFEST_TOOL = @MANIFEST_TOOL@
223MICRO_VERSION = @MICRO_VERSION@
224MINOR_VERSION = @MINOR_VERSION@
225MKDIR_P = @MKDIR_P@
226MKINSTALLDIRS = @MKINSTALLDIRS@
227MSGFMT = @MSGFMT@
228MSGFMT_OPTS = @MSGFMT_OPTS@
229NM = @NM@
230NMEDIT = @NMEDIT@
231OBJDUMP = @OBJDUMP@
232OBJEXT = @OBJEXT@
233OPENSSL_CFLAGS = @OPENSSL_CFLAGS@
234OPENSSL_LIBS = @OPENSSL_LIBS@
235OTOOL = @OTOOL@
236OTOOL64 = @OTOOL64@
237PACKAGE = @PACKAGE@
238PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
239PACKAGE_NAME = @PACKAGE_NAME@
240PACKAGE_STRING = @PACKAGE_STRING@
241PACKAGE_TARNAME = @PACKAGE_TARNAME@
242PACKAGE_URL = @PACKAGE_URL@
243PACKAGE_VERSION = @PACKAGE_VERSION@
244PATH_SEPARATOR = @PATH_SEPARATOR@
245PKG_CONFIG = @PKG_CONFIG@
246PKG_CONFIG_LIBDIR = @PKG_CONFIG_LIBDIR@
247PKG_CONFIG_PATH = @PKG_CONFIG_PATH@
248POFILES = @POFILES@
249POSUB = @POSUB@
250PO_IN_DATADIR_FALSE = @PO_IN_DATADIR_FALSE@
251PO_IN_DATADIR_TRUE = @PO_IN_DATADIR_TRUE@
252RANLIB = @RANLIB@
253SED = @SED@
254SET_MAKE = @SET_MAKE@
255SHELL = @SHELL@
256STRIP = @STRIP@
257SYLPHEED_LIBS = @SYLPHEED_LIBS@
258USE_NLS = @USE_NLS@
259VERSION = @VERSION@
260WINDRES = @WINDRES@
261XGETTEXT = @XGETTEXT@
262YACC = @YACC@
263YFLAGS = @YFLAGS@
264abs_builddir = @abs_builddir@
265abs_srcdir = @abs_srcdir@
266abs_top_builddir = @abs_top_builddir@
267abs_top_srcdir = @abs_top_srcdir@
268ac_ct_AR = @ac_ct_AR@
269ac_ct_CC = @ac_ct_CC@
270ac_ct_DUMPBIN = @ac_ct_DUMPBIN@
271am__include = @am__include@
272am__leading_dot = @am__leading_dot@
273am__quote = @am__quote@
274am__tar = @am__tar@
275am__untar = @am__untar@
276bindir = @bindir@
277build = @build@
278build_alias = @build_alias@
279build_cpu = @build_cpu@
280build_os = @build_os@
281build_vendor = @build_vendor@
282builddir = @builddir@
283datadir = @datadir@
284datarootdir = @datarootdir@
285docdir = @docdir@
286dvidir = @dvidir@
287exec_prefix = @exec_prefix@
288faqdir = @faqdir@
289host = @host@
290host_alias = @host_alias@
291host_cpu = @host_cpu@
292host_os = @host_os@
293host_vendor = @host_vendor@
294htmldir = @htmldir@
295includedir = @includedir@
296infodir = @infodir@
297install_sh = @install_sh@
298libdir = @libdir@
299libexecdir = @libexecdir@
300localedir = @localedir@
301localstatedir = @localstatedir@
302mandir = @mandir@
303manualdir = @manualdir@
304mkdir_p = @mkdir_p@
305oldincludedir = @oldincludedir@
306pdfdir = @pdfdir@
307plugindir = @plugindir@
308prefix = @prefix@
309program_transform_name = @program_transform_name@
310psdir = @psdir@
311sbindir = @sbindir@
312sharedstatedir = @sharedstatedir@
313srcdir = @srcdir@
314sysconfdir = @sysconfdir@
315target = @target@
316target_alias = @target_alias@
317target_cpu = @target_cpu@
318target_os = @target_os@
319target_vendor = @target_vendor@
320themedir = @themedir@
321top_build_prefix = @top_build_prefix@
322top_builddir = @top_builddir@
323top_srcdir = @top_srcdir@
324faqdatadir = $(faqdir)/en
325faqdata_DATA = \
326 sylpheed-faq-1.html \
327 sylpheed-faq-2.html \
328 sylpheed-faq-3.html \
329 sylpheed-faq-4.html \
330 sylpheed-faq.html
331
332
333# generated by `ls -1 | sed -e 's/\(.*\)/ \1 \'`
334EXTRA_DIST = $(faqdata_DATA) \
335 faq.xml \
336 faq_001.xml \
337 faq_002.xml \
338 faq_003.xml \
339 fdl.xml \
340 LICENSE
341
342all: all-am
343
344.SUFFIXES:
345$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.am $(am__configure_deps)
346 @for dep in $?; do \
347 case '$(am__configure_deps)' in \
348 *$$dep*) \
349 ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \
350 && { if test -f $@; then exit 0; else break; fi; }; \
351 exit 1;; \
352 esac; \
353 done; \
354 echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign faq/en/Makefile'; \
355 $(am__cd) $(top_srcdir) && \
356 $(AUTOMAKE) --foreign faq/en/Makefile
357.PRECIOUS: Makefile
358Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
359 @case '$?' in \
360 *config.status*) \
361 cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
362 *) \
363 echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
364 cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
365 esac;
366
367$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
368 cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
369
370$(top_srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(am__configure_deps)
371 cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
372$(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ $(am__aclocal_m4_deps)
373 cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
374$(am__aclocal_m4_deps):
375
376mostlyclean-libtool:
377 -rm -f *.lo
378
379clean-libtool:
380 -rm -rf .libs _libs
381install-faqdataDATA: $(faqdata_DATA)
382 @$(NORMAL_INSTALL)
383 @list='$(faqdata_DATA)'; test -n "$(faqdatadir)" || list=; \
384 if test -n "$$list"; then \
385 echo " $(MKDIR_P) '$(DESTDIR)$(faqdatadir)'"; \
386 $(MKDIR_P) "$(DESTDIR)$(faqdatadir)" || exit 1; \
387 fi; \
388 for p in $$list; do \
389 if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
390 echo "$$d$$p"; \
391 done | $(am__base_list) | \
392 while read files; do \
393 echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(faqdatadir)'"; \
394 $(INSTALL_DATA) $$files "$(DESTDIR)$(faqdatadir)" || exit $$?; \
395 done
396
397uninstall-faqdataDATA:
398 @$(NORMAL_UNINSTALL)
399 @list='$(faqdata_DATA)'; test -n "$(faqdatadir)" || list=; \
400 files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \
401 dir='$(DESTDIR)$(faqdatadir)'; $(am__uninstall_files_from_dir)
402tags TAGS:
403
404ctags CTAGS:
405
406cscope cscopelist:
407
408
409distdir: $(DISTFILES)
410 @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
411 topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
412 list='$(DISTFILES)'; \
413 dist_files=`for file in $$list; do echo $$file; done | \
414 sed -e "s|^$$srcdirstrip/||;t" \
415 -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
416 case $$dist_files in \
417 */*) $(MKDIR_P) `echo "$$dist_files" | \
418 sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
419 sort -u` ;; \
420 esac; \
421 for file in $$dist_files; do \
422 if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
423 if test -d $$d/$$file; then \
424 dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
425 if test -d "$(distdir)/$$file"; then \
426 find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
427 fi; \
428 if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
429 cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \
430 find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
431 fi; \
432 cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \
433 else \
434 test -f "$(distdir)/$$file" \
435 || cp -p $$d/$$file "$(distdir)/$$file" \
436 || exit 1; \
437 fi; \
438 done
439check-am: all-am
440check: check-am
441all-am: Makefile $(DATA)
442installdirs:
443 for dir in "$(DESTDIR)$(faqdatadir)"; do \
444 test -z "$$dir" || $(MKDIR_P) "$$dir"; \
445 done
446install: install-am
447install-exec: install-exec-am
448install-data: install-data-am
449uninstall: uninstall-am
450
451install-am: all-am
452 @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
453
454installcheck: installcheck-am
455install-strip:
456 if test -z '$(STRIP)'; then \
457 $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
458 install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
459 install; \
460 else \
461 $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
462 install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
463 "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \
464 fi
465mostlyclean-generic:
466
467clean-generic:
468
469distclean-generic:
470 -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
471 -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES)
472
473maintainer-clean-generic:
474 @echo "This command is intended for maintainers to use"
475 @echo "it deletes files that may require special tools to rebuild."
476clean: clean-am
477
478clean-am: clean-generic clean-libtool mostlyclean-am
479
480distclean: distclean-am
481 -rm -f Makefile
482distclean-am: clean-am distclean-generic
483
484dvi: dvi-am
485
486dvi-am:
487
488html: html-am
489
490html-am:
491
492info: info-am
493
494info-am:
495
496install-data-am: install-faqdataDATA
497
498install-dvi: install-dvi-am
499
500install-dvi-am:
501
502install-exec-am:
503
504install-html: install-html-am
505
506install-html-am:
507
508install-info: install-info-am
509
510install-info-am:
511
512install-man:
513
514install-pdf: install-pdf-am
515
516install-pdf-am:
517
518install-ps: install-ps-am
519
520install-ps-am:
521
522installcheck-am:
523
524maintainer-clean: maintainer-clean-am
525 -rm -f Makefile
526maintainer-clean-am: distclean-am maintainer-clean-generic
527
528mostlyclean: mostlyclean-am
529
530mostlyclean-am: mostlyclean-generic mostlyclean-libtool
531
532pdf: pdf-am
533
534pdf-am:
535
536ps: ps-am
537
538ps-am:
539
540uninstall-am: uninstall-faqdataDATA
541
542.MAKE: install-am install-strip
543
544.PHONY: all all-am check check-am clean clean-generic clean-libtool \
545 cscopelist-am ctags-am distclean distclean-generic \
546 distclean-libtool distdir dvi dvi-am html html-am info info-am \
547 install install-am install-data install-data-am install-dvi \
548 install-dvi-am install-exec install-exec-am \
549 install-faqdataDATA install-html install-html-am install-info \
550 install-info-am install-man install-pdf install-pdf-am \
551 install-ps install-ps-am install-strip installcheck \
552 installcheck-am installdirs maintainer-clean \
553 maintainer-clean-generic mostlyclean mostlyclean-generic \
554 mostlyclean-libtool pdf pdf-am ps ps-am tags-am uninstall \
555 uninstall-am uninstall-faqdataDATA
556
557
558# Tell versions [3.59,3.63) of GNU make to not export all variables.
559# Otherwise a system limit (for SysV at least) may be exceeded.
560.NOEXPORT:
diff --git a/faq/en/NEWS b/faq/en/NEWS
new file mode 100644
index 0000000..63b3d86
--- /dev/null
+++ b/faq/en/NEWS
@@ -0,0 +1,137 @@
1Sylpheed FAQ revision 2.2 released on 2010-08-09
2================================================
3
4New revision of Sylpheed FAQ has been officially released from the Sylpheed
5Documentation Project to reflect changes in the upcoming Sylpheed 3.1.
6
7You can view the FAQ either as a multi-page or single-page HTML document at:
8
9http://sylpheeddoc.sourceforge.net/en/doc_faq.html
10
11Or download it together with source DocBook XML files in a .tar.gz or .zip
12archive from:
13
14https://sourceforge.net/projects/sylpheeddoc/files/
15
16The source DocBook XML files are also available in the Project CVS repository,
17see:
18
19https://sourceforge.net/scm/?type=cvs&group_id=20952
20
21
22Changes over the past 4 months
23------------------------------
24
25* New Q&A "Can I run multiple instances of Sylpheed?"
26* New Q&A "Execute command for my dynamic signature seems not to be working!"
27* Updated Q&A on environment variables
28* Updated Q&A on automatic name completion
29* Updated Q&A on Sylpheed plug-ins
30* Other minor edits throughout the document
31* To better comply with the GFDL license, the source DocBook XML files together
32 with the plain text copy of the GFDL license and appropriate legal notice are
33 now distributed in tarballs with each documentation release, and the exact way
34 of how to obtain the source files is mentioned explicitly in the document;
35 thanks to Ricardo Mones for pointing these legal issues out
36
37All other information on the Sylpheed Documentation Project including how to
38contribute to the documentation effort is available at:
39
40http://sylpheeddoc.sourceforge.net/
41
42
43Contributors to this and previous releases
44------------------------------------------
45
46Paul Kater, Jens Oberender, Francois Barriere, Olivier Delhomme, Petr Kovar
47
48
49Enjoy!
50
51
52Sylpheed FAQ revision 2.1 released on 2010-04-14
53================================================
54
55New revision of Sylpheed FAQ has been officially released from the Sylpheed
56Documentation Project to reflect changes in Sylpheed 3.0.
57
58You can view the FAQ either as a multi-page or single-page HTML document at:
59
60http://sylpheeddoc.sourceforge.net/en/doc_faq.html
61
62Or download it in a .tar.gz or .zip archive from:
63
64https://sourceforge.net/projects/sylpheeddoc/files/
65
66DocBook XML source files are available in the Project CVS repository, see:
67
68https://sourceforge.net/scm/?type=cvs&group_id=20952
69
70
71Changes over the past 6 months
72------------------------------
73
74* New Q&A regarding new mail retrieval
75* New Q&A regarding Sylpheed plug-in interface
76* New Q&A on disabling/enabling the alternating row colors in the message list
77* Updated Q&A on setting up a new account
78* Corrected configuration directory paths under Windows Vista/Seven
79* Other minor edits throughout the document
80
81All other information on the Sylpheed Documentation Project including how to
82contribute to the documentation effort is available at:
83
84http://sylpheeddoc.sourceforge.net/
85
86
87Contributors to this and previous releases
88------------------------------------------
89
90Paul Kater, Jens Oberender, Francois Barriere, Olivier Delhomme, Petr Kovar
91
92
93Enjoy!
94
95
96Sylpheed FAQ revision 2.0 released on 2009-10-02
97================================================
98
99After a couple of dormant years, the Sylpheed FAQ has been officially released
100from the Sylpheed Documentation Project.
101
102You can view the FAQ either as a multi-page or single-page HTML document at:
103
104http://sylpheeddoc.sourceforge.net/en/doc_faq.html
105
106Or download it in a .tar.gz archive from:
107
108https://sourceforge.net/projects/sylpheeddoc/files/
109
110DocBook XML source files are available in the Project CVS repository, see:
111
112https://sourceforge.net/scm/?type=cvs&group_id=20952
113
114
115Changes over the past 6 years
116-----------------------------
117
118* Many questions across the document have been updated to conform with the
119 latest Sylpheed version 2.7.1
120* The document has been migrated from LinuxDoc SGML to DocBook XML
121* The document is now licensed under the terms of the GFDL 1.2 or later
122 (was 1.1 or later)
123* A copy of the GFDL 1.2 is now distributed with the FAQ
124
125All other information on the Sylpheed Documentation Project including how to
126contribute to the documentation effort is available at:
127
128http://sylpheeddoc.sourceforge.net/
129
130
131Contributors to this and previous releases
132------------------------------------------
133
134Paul Kater, Jens Oberender, Francois Barriere, Olivier Delhomme, Petr Kovar
135
136
137Enjoy!
diff --git a/faq/en/faq.xml b/faq/en/faq.xml
new file mode 100644
index 0000000..5fa63f0
--- /dev/null
+++ b/faq/en/faq.xml
@@ -0,0 +1,94 @@
1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
3<!ENTITY __faq__001 SYSTEM "faq_001.xml">
4<!ENTITY __faq__002 SYSTEM "faq_002.xml">
5<!ENTITY __faq__003 SYSTEM "faq_003.xml">
6<!ENTITY __license SYSTEM "fdl.xml">
7]>
8<book>
9 <title>Sylpheed FAQ</title>
10 <bookinfo>
11 <abstract>
12 <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>
13 </abstract>
14 <copyright>
15 <year>2010</year>
16 <holder>The Sylpheed Documentation Project.</holder>
17 </copyright>
18 <legalnotice>
19 <para>Permission is granted to copy, distribute and/or modify this
20 document under the terms of the GNU Free Documentation License, Version
21 1.2 or any later version published by the Free Software Foundation; with
22 no Invariant Sections, with no Front-Cover Texts, and no Back-Cover
23 Texts. A copy of the license is included in the section entitled &quot;GNU
24 Free Documentation License&quot;.
25 </para>
26 </legalnotice>
27 <author>
28 <firstname>Paul</firstname>
29 <surname>Kater</surname>
30<!-- affiliation>
31 <address>
32 <email>paul at nlpagan.net</email>
33 </address>
34 </affiliation --> </author>
35 <author>
36 <firstname>Jens</firstname>
37 <surname>Oberender</surname>
38<!-- affiliation>
39 <address>
40 <email>j.obi at troja.net</email>
41 </address>
42 </affiliation --> </author>
43 <author>
44 <firstname>Francois</firstname>
45 <surname>Barriere</surname>
46<!-- affiliation>
47 <address>
48 <email>barriere.francois at libertysurf.fr</email>
49 </address>
50 </affiliation --> </author>
51 <author>
52 <firstname>Olivier</firstname>
53 <surname>Delhomme</surname>
54<!-- affiliation>
55 <address>
56 <email>olivier.delhomme at free.fr</email>
57 </address>
58 </affiliation --> </author>
59 <author>
60 <firstname>Petr</firstname>
61 <surname>Kovar</surname>
62<!-- affiliation>
63 <address>
64 <email>pknbe at volny.cz</email>
65 </address>
66 </affiliation --> </author>
67 <revhistory>
68<!-- ******************************************************************************** --> <revision>
69 <revnumber>1.9</revnumber>
70 <date>2005/07/08</date>
71 <authorinitials>OD</authorinitials>
72 <revremark>Ported to DocBook XML.</revremark>
73 </revision>
74 <revision>
75 <revnumber>2.0</revnumber>
76 <date>2009/10/02</date>
77 <authorinitials>PK</authorinitials>
78 <revremark>Finished porting to DocBook XML, updated many questions across the document to conform with Sylpheed 2.7.1.</revremark>
79 </revision>
80 <revision>
81 <revnumber>2.1</revnumber>
82 <date>2010/04/14</date>
83 <authorinitials>PK</authorinitials>
84 <revremark>Updated with regard to Sylpheed 3.0.2.</revremark>
85 </revision>
86 <revision>
87 <revnumber>2.2</revnumber>
88 <date>2010/08/09</date>
89 <authorinitials>PK</authorinitials>
90 <revremark>Updates for the upcoming Sylpheed 3.1.</revremark>
91 </revision>
92<!-- ******************************************************************************** --> </revhistory>
93 </bookinfo>
94&__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 0000000..802b6cd
--- /dev/null
+++ b/faq/en/faq_001.xml
@@ -0,0 +1,591 @@
1<?xml version='1.0' encoding='UTF-8'?><chapter id="sylpheed-faq-1">
2 <title>Sylpheed FAQ - General Information</title>
3 <qandaset id="faq-general">
4<?dbhtml cellspacing="13px" ?> <qandaentry>
5 <question id="faq-languages">
6 <para>
7 Are there FAQ&apos;s in other languages?
8 </para>
9 </question>
10 <answer>
11 <para>
12 Yes. Here are links to several translations:</para>
13 <itemizedlist>
14 <listitem>
15 <para><ulink url="http://sylpheeddoc.sourceforge.net/fr/faq/faq.html">Sylpheed FAQ in French</ulink>, translated by Olivier Delhomme.</para>
16 </listitem>
17 <listitem>
18 <para><ulink url="http://sylpheeddoc.sourceforge.net/de/faq/faq.html">Sylpheed FAQ in German</ulink>, translated by Nicolas Kaiser.</para>
19 </listitem>
20 <listitem>
21 <para><ulink url="http://sylpheeddoc.sourceforge.net/es/faq/faq.html">Sylpheed FAQ in Spanish</ulink>, translated by Ricardo Mones Lastra.</para>
22 </listitem>
23 <listitem>
24 <para><ulink url="http://sylpheeddoc.sourceforge.net/zh_TW.Big5/sylpheed-faq.html">Sylpheed FAQ in Traditional Chinese</ulink>, courtesy of Franklin.</para>
25 </listitem>
26 </itemizedlist>
27 <para>
28 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>
29 <note>
30 <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>
31 </note>
32 </answer>
33 </qandaentry>
34 <qandaentry>
35 <question id="faq-what-sylpheed">
36 <para>
37 What is Sylpheed?
38 </para>
39 </question>
40 <answer>
41 <para>
42 Sylpheed is an email client (and news reader) based on GTK+,
43 running on the X Window System or Microsoft Windows, and aiming for:</para>
44 <itemizedlist>
45 <listitem>
46 <para>Quick response</para>
47 </listitem>
48 <listitem>
49 <para>Graceful, and sophisticated interface</para>
50 </listitem>
51 <listitem>
52 <para>Easy configuration, intuitive operation</para>
53 </listitem>
54 <listitem>
55 <para>High reliability</para>
56 </listitem>
57 <listitem>
58 <para>Internationalization and multilingualization support</para>
59 </listitem>
60 <listitem>
61 <para>Abundant features</para>
62 </listitem>
63 </itemizedlist>
64 <para>As the Sylpheed <filename>README</filename> file reads: The appearance and interface are similar to some popular e-mail clients for
65Windows, such as Outlook Express or Becky!. Many commands are accessible with
66the keyboard like the Emacs-based mailers such as Mew and Wanderlust.
67So you will be able to migrate to Sylpheed without much discomfort, even if
68you are accustomed to other mailers.</para>
69 </answer>
70 </qandaentry>
71 <qandaentry>
72 <question id="faq-get-sylpheed">
73 <para>
74 Where can I get Sylpheed?
75 </para>
76 </question>
77 <answer>
78 <para>
79 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
80 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>
81 <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>
82 <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>
83 </answer>
84 </qandaentry>
85 <qandaentry>
86 <question id="faq-writes-sylpheed">
87 <para>
88 Who writes Sylpheed?
89 </para>
90 </question>
91 <answer>
92 <para>
93 Hiroyuki Yamamoto <email>hiro-y@kcn.ne.jp</email>.
94 </para>
95 </answer>
96 </qandaentry>
97 <qandaentry>
98 <question id="faq-sylpheed-name">
99 <para>
100 What does the name Sylpheed mean?
101 </para>
102 </question>
103 <answer>
104 <para>
105 It means <emphasis>light weight</emphasis>, like air. This comes from the
106 name of the wind spirits, the Sylphs.
107 </para>
108 </answer>
109 </qandaentry>
110 <qandaentry>
111 <question id="faq-sylpheed-store-mail">
112 <para>
113 How does Sylpheed store mails?
114 </para>
115 </question>
116 <answer>
117 <para>
118 Mails are stored in the MH mailfile format as used by MH
119 and EMH. Maildir, mbox, and eml formats are not (yet)
120 supported, although it is possible to import an mbox
121 file or an eml file into a Sylpheed mailbox.</para>
122 <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
123of losing mails on failures since one file corresponds to one mail. You can also utilize fetchmail
124and/or procmail, and external programs on receiving (like inc or imget).</para>
125 </answer>
126 </qandaentry>
127 <qandaentry>
128 <question id="faq-auto-collection-sylpheed">
129 <para>
130 Why does the auto collection of mail not work?
131 </para>
132 </question>
133 <answer>
134 <para>
135 Auto collection works since version 0.5.1. If you need it
136 or want it, you should upgrade.
137 </para>
138 </answer>
139 </qandaentry>
140 <qandaentry>
141 <question id="faq-filtering-sylpheed">
142 <para>
143 Does Sylpheed have mail filtering?
144 </para>
145 </question>
146 <answer>
147 <para>
148 Yes. You can find it in <guimenu>Configuration</guimenu> -&gt; <guimenuitem>Filter settings...</guimenuitem></para>
149 <para>
150 Please note that filtering is not yet implemented for IMAP accounts.
151 </para>
152 </answer>
153 </qandaentry>
154 <qandaentry>
155 <question id="faq-imap-sylpheed">
156 <para>
157 Can Sylpheed handle IMAP mail?
158 </para>
159 </question>
160 <answer>
161 <para>
162 Yes. As of version 0.4.99 IMAP is supported.
163 </para>
164 </answer>
165 </qandaentry>
166 <qandaentry>
167 <question id="faq-local-unix-sylpheed">
168 <para>
169 Can Sylpheed handle local unix mailboxes?
170 </para>
171 </question>
172 <answer>
173 <para>
174 Yes.
175 </para>
176 </answer>
177 </qandaentry>
178 <qandaentry>
179 <question id="faq-ipv6-sylpheed">
180 <para>
181 Can Sylpheed handle IPv6?
182 </para>
183 </question>
184 <answer>
185 <para>
186 Yes, IPv6 is fully supported in Sylpheed.
187 </para>
188 </answer>
189 </qandaentry>
190 <qandaentry>
191 <question id="faq-encryption-gpg-sylpheed">
192 <para>
193 Does Sylpheed support encryption like GPG?
194 </para>
195 </question>
196 <answer>
197 <para>
198 Yes. GPG is implemented and works fine. For activating it in Sylpheed,
199 see the appropriate question in the Installation section.
200 </para>
201 </answer>
202 </qandaentry>
203 <qandaentry>
204 <question id="faq-mime-types-sylpheed">
205 <para>
206 How does Sylpheed check for MIME types?
207 </para>
208 </question>
209 <answer>
210 <para>
211 Sylpheed uses the Mutt type of mime checking.
212 </para>
213 </answer>
214 </qandaentry>
215 <qandaentry>
216 <question id="faq-html-sylpheed">
217 <para>Does Sylpheed allow me to write HTML styled messages?
218 </para>
219 </question>
220 <answer>
221 <para>
222 No. A discussion has gone around over this topic, and
223 the outcome was that HTML mail is not wanted. If you
224 really need to send HTML, you can of course attach a
225 web page to an email.</para>
226 </answer>
227 </qandaentry>
228 <qandaentry>
229 <question id="faq-completion-adress-sylpheed">
230 <para>Does Sylpheed have automatic name completion in the address fields?
231 </para>
232 </question>
233 <answer>
234 <para>
235 Yes. When you search for a name that starts with &quot;<literal>don</literal>&quot;,
236 type &quot;<literal>don</literal>&quot; (without the quotes) and it will show you the correct name (when only one &quot;don&quot;
237 exists in your address book. Otherwise a drop-down list
238 appears, which allows you to select the name you want.
239 E.g. Donald Duck, Don Johnson. But also email addresses
240 starting with &quot;<literal>don</literal>&quot; will appear in the list (like
241 &quot;<literal>don.giovanni@maffia.org</literal>&quot;).</para>
242 <para>Prior to Sylpheed 3.1, users needed to press the <keycap>Tab</keycap> key before the search would start. If you still prefer the previous behavior, you can enable it by checking <menuchoice>
243 <guimenu>Configuration</guimenu>
244 <guimenuitem>Common preferences...</guimenuitem>
245 <guimenuitem>Details</guimenuitem>
246 <guimenuitem>Other</guimenuitem>
247 <guisubmenu>Address book</guisubmenu>
248 <guilabel>Address auto-completion:</guilabel>
249 <guilabel>Start with Tab</guilabel>
250 </menuchoice>.</para>
251 </answer>
252 </qandaentry>
253 <qandaentry>
254 <question id="faq-tab-error-sylpheed">
255 <para>Fine, but when I hit the Tab key I either get an error message or nothing happens at all.
256 </para>
257 </question>
258 <answer>
259 <para>
260 When you want to use name completion, make sure that
261 there are names in your address book. If there are no
262 names, even Sylpheed has a hard time completing
263 something.</para>
264 <para>If nothing happens at all when typing text in the address fields, make sure that you have the address auto-completion enabled by checking that the following preference is not selected: <menuchoice>
265 <guimenu>Configuration</guimenu>
266 <guimenuitem>Common preferences...</guimenuitem>
267 <guimenuitem>Details</guimenuitem>
268 <guimenuitem>Other</guimenuitem>
269 <guisubmenu>Address book</guisubmenu>
270 <guilabel>Address auto-completion:</guilabel>
271 <guilabel>Disabled</guilabel>
272 </menuchoice>.</para>
273 </answer>
274 </qandaentry>
275 <qandaentry>
276 <question id="faq-sylpheed-fast">
277 <para>Why is Sylpheed so fast?
278 </para>
279 </question>
280 <answer>
281 <para>That&apos;s what it is designed for!
282 </para>
283 </answer>
284 </qandaentry>
285 <qandaentry>
286 <question id="faq-patches-sylpheed">
287 <para>Where can I get the current patches for Sylpheed?
288 </para>
289 </question>
290 <answer>
291 <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>.
292 (Also see the Installation section on how to install a patch.)
293 </para>
294 </answer>
295 </qandaentry>
296 <qandaentry>
297 <question id="faq-send-patches-sylpheed">
298 <para>How can I send in patches, report bugs, talk about Sylpheed with others?
299 </para>
300 </question>
301 <answer>
302 <para>To talk to others, you should join the Sylpheed mailing
303 list at <ulink url="http://www.sraoss.jp/mailman/listinfo/sylpheed">
304 <literal>http://www.sraoss.jp/mailman/listinfo/sylpheed</literal>
305 </ulink>. Note that there is
306 a Japanese and an English list, so pick the right one!
307 If you have made a patch that you want the world to know
308 of, please post it either to the mailing list, or contact the Sylpheed author, Hiroyuki Yamamoto <email>hiro-y@kcn.ne.jp</email>. </para>
309 <para>Please supply the information of <menuchoice>
310 <guimenu>Tools</guimenu>
311 <guimenuitem>Log window</guimenuitem>
312 </menuchoice>, or the contents of
313<filename>sylpheed.log</filename>, which is located under the configuration folder, when
314reporting bugs.</para>
315 </answer>
316 </qandaentry>
317 <qandaentry>
318 <question id="faq-content-type-header-sylpheed">
319 <para>When I send mail, the Content-Type header says the mail is in
320 US-ASCII, even when I specified ISO-8859-1?
321 </para>
322 </question>
323 <answer>
324 <para>If ISO-8859-1 characters (&gt;= 0x80) are not used in the
325 message body, Sylpheed will automatically set the
326 charset value in the Content-Type header as US-ASCII.
327 </para>
328 </answer>
329 </qandaentry>
330 <qandaentry>
331 <question id="faq-word-wrap-sylpheed">
332 <para>Why does it look like word wrap is not working?
333 </para>
334 </question>
335 <answer>
336 <para>Word wrapping is a bit peculiar perhaps. You can type
337 lines as long as you like. By the time you send or queue
338 a mail with long lines, Sylpheed will first wrap the
339 lines to the line length you set up, and then the mail
340 is queued. This is more convenient than you think. Once
341 a line is wrapped (hard line breaks are inserted in the
342 text) and you add something in a line there, the next
343 line will move to a separate new line, leaving one or
344 two words from the previous line &quot;hanging there&quot; alone.
345 E.g.
346 <literallayout> This is a long line that
347 is wrapped. </literallayout>Now you add one word in the first line:
348 <literallayout> This is a very long line
349 that
350 is wrapped </literallayout>This would cause you a lot of manual reformatting to get
351 a presentable mail again.
352
353 </para>
354 <note>
355 <para>As of Sylpheed 0.8.0., active word wrap has been
356 implemented. You can turn it on in <menuchoice>
357 <guisubmenu>Common Preferences</guisubmenu>
358 <guimenuitem>Compose</guimenuitem>
359 <guimenuitem>Editor</guimenuitem>
360 <guilabel>Wrap on input</guilabel>
361 </menuchoice>.
362 </para>
363 </note>
364 </answer>
365 </qandaentry>
366 <qandaentry>
367 <question>
368 <para>How do I copy my mail archive to another machine? </para>
369 </question>
370 <answer>
371 <para>You need to copy the <filename>sylpheed-2.0</filename> directory with your user profile, and your entire local mail archive. </para>
372 <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>
373 <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>
374 <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>
375 </answer>
376 </qandaentry>
377 <qandaentry>
378 <question id="faq-import-mbox-sylpheed">
379 <para>Can I import a mbox into Sylpheed&apos;s MH mailfolders?
380 </para>
381 </question>
382 <answer>
383 <para>
384 Yes, just create/select the folder you want your
385 mails in, and select <guimenuitem>Import mbox file...</guimenuitem> in the <guimenu>File</guimenu>
386 menu.</para>
387 </answer>
388 </qandaentry>
389 <qandaentry>
390 <question id="faq-procmail-use-sylpheed">
391 <para>
392 Can I use procmail to sort my mails with the MH mail handling?
393 </para>
394 </question>
395 <answer>
396 <para>
397 Yes. Just make sure that you add <computeroutput>/.</computeroutput> to the end of a rule so
398 procmail knows you are filtering into an MH mail folder. Example:
399 </para>
400 <programlisting>0:
401* ^Subject:.*sylpheed
402sylpheedmail/.
403</programlisting>
404 <para>Check <command>man procmail</command> for details.
405 </para>
406 </answer>
407 </qandaentry>
408 <qandaentry>
409 <question id="faq-upgrade-sylpheed">
410 <para>
411 When I upgrade Sylpheed, are there things I should be aware of?
412 </para>
413 </question>
414 <answer>
415 <para>
416 Yes!</para>
417 <itemizedlist>
418 <listitem>
419 <para>Upgrade to 0.4.50: you should reconfigure your newsgroup settings</para>
420 </listitem>
421 <listitem>
422 <para>Upgrade to 0.4.63: you should set the URL string colors from the <guimenu>Configuration</guimenu> menu</para>
423 </listitem>
424 <listitem>
425 <para>Upgrade to 0.4.65: some menu items have been moved</para>
426 </listitem>
427 <listitem>
428 <para>Upgrade to 0.7.3: many key bindings have changed</para>
429 </listitem>
430 <listitem>
431 <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>
432 </listitem>
433 </itemizedlist>
434 <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>
435 </answer>
436 </qandaentry>
437 <qandaentry>
438 <question id="faq-update-views-sylpheed">
439 <para>How can I quickly update the views in Sylpheed?
440 </para>
441 </question>
442 <answer>
443 <para>
444 Just press <keycombo>
445 <keycap>Alt</keycap>
446 <keycap>U</keycap>
447 </keycombo> or select <guimenuitem>Update summary</guimenuitem> from the <guimenu>View</guimenu> menu.
448 </para>
449 </answer>
450 </qandaentry>
451 <qandaentry>
452 <question id="faq-gvim-external-editor-sylpheed">
453 <para>Why can&apos;t I use gvim as external editor?
454 </para>
455 </question>
456 <answer>
457 <para>
458 If one wishes to use gvim as an external editor it&apos;s
459 necessary to start it with the no-fork option <parameter>-f</parameter>, i.e.
460 in the configuration dialog box you need to enter
461 <command>gvim -f %s</command>. If not the editor forks and open up a
462 separate file and when one quits the editor the changes
463 are lost and don&apos;t show up in the composer window.
464 (Thanks, Ed Collins!)
465 </para>
466 </answer>
467 </qandaentry>
468 <qandaentry>
469 <question id="faq-quote-messages-sylpheed">
470 <para>Can I quote just parts of the original message when replying?
471 </para>
472 </question>
473 <answer>
474 <para>
475 Yes, select the part in the text view and choose <guiicon>Reply</guiicon>.
476 </para>
477 </answer>
478 </qandaentry>
479 <qandaentry>
480 <question id="faq-not-quoting-sylpheed">
481 <para>Can I reply without quoting at all?
482 </para>
483 </question>
484 <answer>
485 <para>You need to disable quoting by editing the reply format under <menuchoice>
486 <guimenu>Configuration</guimenu>
487 <guimenuitem>Common preferences</guimenuitem>
488 <guimenuitem>Compose tab</guimenuitem>
489 <guimenuitem>Format tab</guimenuitem>
490 </menuchoice>
491 (also works with
492 forward format which you can see below the reply format in the configuration dialog).</para>
493 </answer>
494 </qandaentry>
495 <qandaentry>
496 <question>
497 <para> Does Sylpheed provide an anti-spam feature? </para>
498 </question>
499 <answer>
500 <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>
501 <guimenu>Configuration</guimenu>
502 <guimenuitem>Common preferences...</guimenuitem>
503 <guimenuitem>Junk mail</guimenuitem>
504 </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>
505 <para>You can also use other spam filters thanks to the Actions functionality (available under <menuchoice>
506 <guimenu>Configuration</guimenu>
507 <guimenuitem>Actions...</guimenuitem>
508 </menuchoice>).</para>
509 <note>
510 <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>
511 </note>
512 </answer>
513 </qandaentry>
514 <qandaentry>
515 <question>
516 <para>Are there any plug-ins extending standard Sylpheed functionality?</para>
517 </question>
518 <answer>
519 <para>As of Sylpheed 3.1, there is an Attachment Tool Plug-in distributed with the Sylpheed source code and available under <filename>plugin/attachment_tool/</filename>. Its only function is to remove attachments from
520selected messages and is provided more or less as a technology preview. More plug-ins 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>
521 <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>
522 <note>
523 <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>
524 </note>
525 </answer>
526 </qandaentry>
527 <qandaentry>
528 <question id="faq-faq-sylpheed">
529 <para>Where I can find the latest Sylpheed FAQ and manual?
530 </para>
531 </question>
532 <answer>
533 <para>
534 Go to <ulink url="http://sylpheeddoc.sourceforge.net/">http://sylpheeddoc.sourceforge.net</ulink> and check out
535 the FAQ and manual from the Sylpheed Documentation Project (sylpheeddoc). Both
536 documents are available in multiple languages there and
537 usually contain the latest updates. The direct links are as follows:</para>
538 <itemizedlist>
539 <listitem>
540 <para><ulink url="http://sylpheeddoc.sourceforge.net/en/faq/sylpheed-faq.html">current version of the English FAQ</ulink></para>
541 </listitem>
542 <listitem>
543 <para><ulink url="http://sylpheeddoc.sourceforge.net/en/manual/sylpheed.html">current version of the English manual</ulink></para>
544 </listitem>
545 </itemizedlist>
546 <para>Also see the question about available language versions at the top of this section. </para>
547 </answer>
548 </qandaentry>
549 <qandaentry>
550 <question>
551 <para>Where I can obtain source files for this document?</para>
552 </question>
553 <answer>
554 <para>The source DocBook XML files in which this document is written can be obtained from a <ulink url="http://sylpheeddoc.cvs.sourceforge.net/sylpheeddoc/">public CVS repository</ulink> that is part of the <ulink url="http://sylpheeddoc.sourceforge.net/">Sylpheed Documentation Project</ulink>. The source files with all the necessary build system, XSL stylesheets or snapshots are stored under the &quot;<ulink url="http://sylpheeddoc.cvs.sourceforge.net/viewvc/sylpheeddoc/doc/">doc</ulink>&quot; module in the CVS repository and can be checked out through anonymous CVS with the following commands (simply press Enter when prompted for a password):</para>
555 <para><command>cvs -d:pserver:anonymous@sylpheeddoc.cvs.sourceforge.net:/cvsroot/sylpheeddoc login</command></para>
556 <para><command>cvs -z3 -d:pserver:anonymous@sylpheeddoc.cvs.sourceforge.net:/cvsroot/sylpheeddoc co -P doc</command></para>
557 <para>The source files are also included in .tar.gz and .zip archives made available with each documentation release, these can be downloaded from the <ulink url="http://sourceforge.net/projects/sylpheeddoc/files/">appropriate project page</ulink>. For more information on the used project infrastructure, please see the <ulink url="http://sylpheeddoc.sourceforge.net/en/tools.html">project website</ulink>.</para>
558 </answer>
559 </qandaentry>
560 <qandaentry>
561 <question>
562 <para>I have found an error and/or outdated information in this document!</para>
563 </question>
564 <answer>
565 <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>
566 </answer>
567 </qandaentry>
568 <qandaentry>
569 <question>
570 <para>Who are the members of the Sylpheed Documentation Project?</para>
571 </question>
572 <answer>
573 <para>The current members of the Sylpheed Documentation Project are:</para>
574 <programlisting>Francois Barriere fbarriere at users.sourceforge.net
575Petr Kovar pknbe at users.sourceforge.net</programlisting>
576 <para>Below is the list of former members of the Sylpheed Documentation Project. Big thank you goes to all of them!</para>
577 <programlisting>Martin Bretschneider furbour at users.sourceforge.net
578Olivier Delhomme dup at users.sourceforge.net
579Doruk Fisek dobidik at users.sourceforge.net
580Melvin Hadasht mhadasht at users.sourceforge.net
581Nicolas Kaiser nikai at users.sourceforge.net
582Paul Kater pkater at users.sourceforge.net
583Ricardo Mones Lastra mones at users.sourceforge.net
584Jens Oberender jobi at users.sourceforge.net
585Marcelo Ramos hackpando at users.sourceforge.net
586Guido Rudolphi malatesta at users.sourceforge.net
587Frank Weng fweng at users.sourceforge.net</programlisting>
588 </answer>
589 </qandaentry>
590 </qandaset>
591</chapter>
diff --git a/faq/en/faq_002.xml b/faq/en/faq_002.xml
new file mode 100644
index 0000000..58da0f3
--- /dev/null
+++ b/faq/en/faq_002.xml
@@ -0,0 +1,606 @@
1<?xml version='1.0' encoding='UTF-8'?><chapter id="sylpheed-faq-2">
2 <title>Sylpheed FAQ - Installation and Configuration</title>
3 <qandaset id="faq-installation">
4<?dbhtml cellspacing="13px" ?> <qandaentry>
5 <question>
6 <para>What does it take to compile Sylpheed?</para>
7 </question>
8 <answer>
9 <para>Any POSIX compliant UNIX or similar OS, e.g. Linux,
10FreeBSD, Solaris.
11GTK+ 2.4.0 or later (GTK+ 2.6.0 or later
12is recommended).
13A recent ANSI C compiler (gcc 2.7.2.3 should also
14work).</para>
15 <note>
16 <para>It is reported that Sun C will not compile
17Sylpheed.</para>
18 </note>
19 <para>Optionally:</para>
20 <itemizedlist>
21 <listitem>
22 <para>compface (for X-Face)</para>
23 </listitem>
24 <listitem>
25 <para>GPGME (for GnuPG)</para>
26 </listitem>
27 <listitem>
28 <para>OpenSSL for SSL support</para>
29 </listitem>
30 <listitem>
31 <para>GtkSpell for a spell checking feature</para>
32 </listitem>
33 <listitem>
34 <para>cURL for allowing Sylpheed to check for updates</para>
35 </listitem>
36 <listitem>
37 <para>JPilot</para>
38 </listitem>
39 <listitem>
40 <para>LDAP</para>
41 </listitem>
42 <listitem>
43 <para>the equivalent of GTK+-devel and Xfree86-devel</para>
44 </listitem>
45 <listitem>
46 <para>you may also require flex (lex) and bison
47(yacc).</para>
48 </listitem>
49 </itemizedlist>
50 <para>Otherwise ./configure will fail.
51See also the <filename>INSTALL</filename> file that is being distributed with the Sylpheed tarball.</para>
52 <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>
53 </answer>
54 </qandaentry>
55 <qandaentry>
56 <question>
57 <para>How do I set up Sylpheed?</para>
58 </question>
59 <answer>
60 <para>When you run Sylpheed for the first time, it will
61ask you where you want to store your mailboxes. The
62default is <filename>$HOME/Mail</filename> (or <filename>%APPDATA%\Sylpheed\Mailboxes\Mail</filename> under Windows). You can change this to
63anything you like as long as it is a valid directory
64name.</para>
65 <note>
66 <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>
67 </note>
68 <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>
69 </answer>
70 </qandaentry>
71 <qandaentry>
72 <question>
73 <para>Why did the creation of the mailbox fail?</para>
74 </question>
75 <answer>
76 <para>Sylpheed reports such an error if it can&apos;t create the default
77mailboxes (inbox, outbox, etc.). This can be because <filename>$HOME/Mail</filename>
78(or <filename>%APPDATA%\Sylpheed\Mailboxes\Mail</filename> under Windows) already contains files with the same names. This occurs when switching from
79Kmail to Sylpheed, in this case backup and remove the existing Mail
80directory or use another name for the Sylpheed mail directory.</para>
81 </answer>
82 </qandaentry>
83 <qandaentry>
84 <question id="faq-account-setup">
85 <para>How do I set up an account?</para>
86 </question>
87 <answer>
88 <para>After loading Sylpheed for the first time, you can
89add 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.
90In a few easy steps, the assistant allows you to conveniently configure your POP3, IMAP4, or Gmail account.</para>
91 <tip>
92 <para>If you want later to change your account configuration, just select <menuchoice>
93 <guimenuitem>Configuration</guimenuitem>
94 <guimenuitem>Preferences for current account...</guimenuitem>
95 </menuchoice>, or <menuchoice>
96 <guimenuitem>Configuration</guimenuitem>
97 <guimenuitem>Edit accounts...</guimenuitem>
98 </menuchoice></para>
99 </tip>
100 </answer>
101 </qandaentry>
102 <qandaentry>
103 <question>
104 <para>How many accounts can I set up in Sylpheed?</para>
105 </question>
106 <answer>
107 <para>The number is unlimited. The limit is reached when
108your computer stops responding.</para>
109 </answer>
110 </qandaentry>
111 <qandaentry>
112 <question>
113 <para>Can I set up an account for sending mail only?</para>
114 </question>
115 <answer>
116 <para>Yes, add a new account using <menuchoice>
117 <guimenuitem>Configuration</guimenuitem>
118 <guimenuitem>Edit accounts...</guimenuitem>
119 <guibutton>Add</guibutton>
120 </menuchoice> and set the Protocol to None (local).</para>
121 </answer>
122 </qandaentry>
123 <qandaentry>
124 <question>
125 <para>Why does Sylpheed not delete my mails when I press &quot;Delete&quot;? I set a filter, and Sylpheed does not filter. I moved a mail to a different mailbox and it did not move.</para>
126 </question>
127 <answer>
128 <para>You have to click the <guiicon>Execute</guiicon> button.
129The other solution: in the configuration settings
130(<menuchoice>
131 <guimenuitem>Common preferences...</guimenuitem>
132 <guimenuitem>Details</guimenuitem>
133 <guimenuitem>Interface</guimenuitem>
134 </menuchoice>), you have to
135check the <guilabel>Execute immediately when moving or deleting messages</guilabel> box.</para>
136 </answer>
137 </qandaentry>
138 <qandaentry>
139 <question>
140 <para>Can I set up special addresses/ports for my mailserver/newsserver?</para>
141 </question>
142 <answer>
143 <para>Yes, you can. Under <menuchoice>
144 <guimenu>Configuration</guimenu>
145 <guimenuitem>Preferences for current account...</guimenuitem>
146 <guimenuitem>Advanced</guimenuitem>
147 </menuchoice>, you
148can specify the exact port addresses you want to use.</para>
149 </answer>
150 </qandaentry>
151 <qandaentry>
152 <question>
153 <para>Does Sylpheed have options for threading messages?</para>
154 </question>
155 <answer>
156 <para>Yes. You can switch it on and off in the <guimenu>View</guimenu>
157 menu, just select <guimenuitem>Thread view</guimenuitem> or press <keycombo>
158 <keycap>Ctrl</keycap>
159 <keycap>T</keycap>
160 </keycombo>.</para>
161 </answer>
162 </qandaentry>
163 <qandaentry>
164 <question>
165 <para>Can I create multiple levels of subfolders to store mail?</para>
166 </question>
167 <answer>
168 <para>Absolutely. This is no problem.</para>
169 </answer>
170 </qandaentry>
171 <qandaentry>
172 <question>
173 <para>Why isn&apos;t Sylpheed sending my mail out?</para>
174 </question>
175 <answer>
176 <para>You need to create at least one account in order to
177 send. (This is a wonderful gotcha on LAN installs
178 with only a local mailbox feed).</para>
179 </answer>
180 </qandaentry>
181 <qandaentry>
182 <question>
183 <para>How do I apply a patch after downloading it?</para>
184 </question>
185 <answer>
186 <para>Copy patch to sylpheed directory.
187 Apply the patch as follows:</para>
188 <para>
189 <command>% patch -p0 &lt; some.patch</command></para>
190 <para>
191 Or, if it&apos;s gzipped:</para>
192 <para>
193 <command>% gzip -dc some.patch.gz | patch -p0</command></para>
194 <para>
195 Run <filename>./autogen.sh</filename>, remove the generated <filename>/config.cache</filename>
196 file (unless you want to install in prefix
197 <filename>/usr/local</filename>).
198 Run <filename>./configure</filename> with the appropriate options and
199 then <filename>make</filename>.
200 (Text as found on the former Sylpheed patches page.)</para>
201 </answer>
202 </qandaentry>
203 <qandaentry>
204 <question>
205 <para>How do I compile in support for compface pictures?</para>
206 </question>
207 <answer>
208 <para>You have to have a package called <computeroutput>libcompface</computeroutput>
209 installed, so this is available for compiling into
210 Sylpheed. Note that the exact name of the package depends on OS or distribution you use.</para>
211 </answer>
212 </qandaentry>
213 <qandaentry>
214 <question>
215 <para>How do I make my own compface image?</para>
216 </question>
217 <answer>
218 <para>The faces package contains a program called xbm2ikon script,
219 which converts a 48x48 xbm to the format suitable for
220 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>
221 </answer>
222 </qandaentry>
223 <qandaentry>
224 <question>
225 <para>How can I tell my browser/newsclient/other program to use Sylpheed as email program?</para>
226 </question>
227 <answer>
228 <para> In the settings part of the program, write
229 <command>sylpheed --compose</command></para>
230 <para>
231Specific options for typical browsers:</para>
232 <itemizedlist>
233 <listitem>
234 <para>Opera: <command>sylpheed --compose [mailto:%t][?subject=%s] </command></para>
235 </listitem>
236 <listitem>
237 <para>Galeon: <command>sylpheed --compose &quot;mailto:%t?subject=%s&quot;</command></para>
238 </listitem>
239 </itemizedlist>
240 </answer>
241 </qandaentry>
242 <qandaentry>
243 <question>
244 <para>How do I enable GPG support in Sylpheed?</para>
245 </question>
246 <answer>
247 <para> When compiling Sylpheed, make sure you add <parameter>--enable-gpgme</parameter> in the <command>./configure</command> command.
248When that completes successfully, there is a <guimenuitem>Privacy</guimenuitem> section in the <guimenuitem>Common Preferences</guimenuitem>.</para>
249 </answer>
250 </qandaentry>
251 <qandaentry>
252 <question>
253 <para>Mutt does not recognize Sylpheed&apos;s MH structure</para>
254 </question>
255 <answer>
256 <para>For this to work you need to use the <command>touch</command> command in every MH folder. &quot;<command>touch</command>&quot; the file <filename>.xmhcache</filename> and Mutt should do just fine.</para>
257 </answer>
258 </qandaentry>
259 <qandaentry>
260 <question>
261 <para>Viewing a GIF file within Sylpheed causes a segmentation fault.</para>
262 </question>
263 <answer>
264 <para>In case this happens, you can easily fix that by adding the following to <filename>/etc/mime.types</filename>:</para>
265 <programlisting>image/gif gif</programlisting>
266 </answer>
267 </qandaentry>
268 <qandaentry>
269 <question>
270 <para>How Sylpheed checks for new mail?</para>
271 </question>
272 <answer>
273 <para>New mail can be retrieved either manually or automatically.</para>
274 <para>To check for new mail the manual way, you can:</para>
275 <orderedlist>
276 <listitem>
277 <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>
278 </listitem>
279 <listitem>
280 <para>Or choose <menuchoice>
281 <guimenu>File</guimenu>
282 <guimenuitem>Mailbox</guimenuitem>
283 <guimenuitem>Check for new messages</guimenuitem>
284 </menuchoice>, or <guimenuitem>Check for new messages in all mailboxes</guimenuitem>.</para>
285 </listitem>
286 <listitem>
287 <para>Or select <menuchoice>
288 <guimenu>Message</guimenu>
289 <guimenuitem>Receive</guimenuitem>
290 <guimenuitem>Get from current account</guimenuitem>
291 </menuchoice>, or <guimenuitem>Get from all accounts</guimenuitem>.</para>
292 </listitem>
293 </orderedlist>
294 <tip>
295 <para>If you have a POP3 account and don&apos;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>
296 <guimenu>Message</guimenu>
297 <guimenuitem>Receive</guimenuitem>
298 <guimenuitem>Remote mailbox...</guimenuitem>
299 </menuchoice></para>
300 </tip>
301 <para>If you prefer autochecking for new mail instead, first of all, make sure that you have checked <menuchoice>
302 <guimenu>Configuration</guimenu>
303 <guimenuitem>Common preferences...</guimenuitem>
304 <guimenuitem>Receive</guimenuitem>
305 <guilabel>Autocheck new mail every <replaceable>10</replaceable> minute(s)</guilabel>
306 </menuchoice>. Optionally, you can adjust the interval value (in minutes) as well.</para>
307 <para>Also check your settings under <menuchoice>
308 <guimenu>Configuration</guimenu>
309 <guimenuitem>Edit accounts...</guimenuitem>
310 </menuchoice> You will find this
311at the top: <guilabel>Check the boxes on the &apos;G&apos; column to enable message retrieval by &apos;Get all&apos;</guilabel>. The setting applies on both manual and automatic
312mail checks.</para>
313 </answer>
314 </qandaentry>
315 <qandaentry>
316 <question>
317 <para>How can I make Sylpheed notify me when new mail arrives?</para>
318 </question>
319 <answer>
320 <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>
321 </answer>
322 </qandaentry>
323 <qandaentry>
324 <question>
325 <para>Can I use a spell checker with Sylpheed?</para>
326 </question>
327 <answer>
328 <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>
329 <para>The GtkSpell option is not supported in Sylpheed for Windows (yet), so you will have no spell checking under this OS.</para>
330 </answer>
331 </qandaentry>
332 <qandaentry>
333 <question>
334 <para>How can I make Sylpheed send my compface image in the mails?</para>
335 </question>
336 <answer>
337 <para>In the <menuchoice>
338 <guimenu>Configuration</guimenu>
339 <guimenuitem>Preferences for current account...</guimenuitem>
340 <guimenuitem>Send</guimenuitem>
341 </menuchoice> check <guilabel>Add user-defined header</guilabel> and press <guibutton>Edit</guibutton> button. A dialog appears, add a header named &quot;X-Face&quot; 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>
342 </answer>
343 </qandaentry>
344 <qandaentry>
345 <question>
346 <para>How can I get the newest source code from the Sylpheed Subversion (SVN) repository?</para>
347 </question>
348 <answer>
349 <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>
350 <para><command>svn checkout svn://sylpheed.sraoss.jp/sylpheed/trunk</command></para>
351 <para>The subdirectories under the <filename>sylpheed</filename> directory are as follows:</para>
352 <itemizedlist>
353 <listitem>
354 <para><filename>trunk/</filename> - main tree</para>
355 </listitem>
356 <listitem>
357 <para><filename>branches/</filename> - miscellaneous experimental branches</para>
358 </listitem>
359 <listitem>
360 <para><filename>tags/</filename> - release-tagged branches</para>
361 </listitem>
362 </itemizedlist>
363 <para>To update to the newest source tree, run the following command in the target directory:</para>
364 <para><command>svn update</command></para>
365 </answer>
366 </qandaentry>
367 <qandaentry>
368 <question>
369 <para>I checked out the sources using SVN and can&apos;t find any configure script.</para>
370 </question>
371 <answer>
372 <para>The SVN versions are meant to be used by developers rather than &quot;normal&quot;
373 users, so the source (or binary) distributions are easier to use.</para>
374 <blockquote>
375 <para>Yeah, but the latest features from SVN really look sexy...</para>
376 </blockquote>
377 <para>You need to generate the configure script by running <filename>autogen.sh</filename>.
378 Be sure to have autoconf and automake packages installed for this.</para>
379 </answer>
380 </qandaentry>
381 <qandaentry>
382 <question>
383 <para>Running &quot;autogen.sh&quot; gives error messages that &quot;AM_PATH_GDK_PIXBUF&quot; or
384 &quot;AM_PATH_(whatever)&quot; is not found.</para>
385 </question>
386 <answer>
387 <para>There are some <filename>*.m4</filename> files in the <filename>ac/missing</filename> directory. Try to copy
388 them into the <filename>ac</filename> directory and run <filename>autogen.sh</filename> again.</para>
389 <para>
390 If there are still some <filename>.m4</filename> files not found (e.g. those from GTK+), try
391 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
392 <filename>gtk.m4</filename> in <filename>/opt/gnome/share/aclocal</filename>, change following line in
393 <filename>autogen.sh</filename> from</para>
394 <programlisting>aclocal -I ac \</programlisting>
395 <para> to</para>
396 <programlisting>aclocal -I ac -I /opt/gnome/share/aclocal \</programlisting>
397 <para>and run it again.</para>
398 </answer>
399 </qandaentry>
400 <qandaentry>
401 <question>
402 <para>I don&apos;t want to compile in support for (...) any longer, but after running
403 &quot;configure&quot;, those libraries are still used.</para>
404 </question>
405 <answer>
406 <para>Remove the <filename>config.cache</filename> file and run <command>./configure</command> again. You should
407 also use <command>make clean</command> to avoid undefined references.</para>
408 </answer>
409 </qandaentry>
410 <qandaentry>
411 <question>
412 <para>How can I select different applications to open with specific MIME types?</para>
413 </question>
414 <answer>
415 <para>The MIME-type to application associations are kept in <filename>/etc/mailcap</filename>.</para>
416 </answer>
417 </qandaentry>
418 <qandaentry>
419 <question>
420 <para>How can I change the suggested mimetype for attachments?</para>
421 </question>
422 <answer>
423 <para>The extension to MIME-type associations are kept in <filename>/etc/mime.types</filename></para>
424 </answer>
425 </qandaentry>
426 <qandaentry>
427 <question>
428 <para>The folder list is not updated after I manually moved/copied folders.</para>
429 </question>
430 <answer>
431 <para>You need to update Sylpheed cache. Right click on the mailbox and choose
432 <guimenuitem>Rebuild folder tree</guimenuitem>.</para>
433 </answer>
434 </qandaentry>
435 <qandaentry>
436 <question>
437 <para>How can I revert original settings, e.g. for fonts, key bindings, etc.?</para>
438 </question>
439 <answer>
440 <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
441 entries, if none are found. So the easiest way is to quit Sylpheed,
442 temporarily renaming your <filename>$HOME/.sylpheed-2.0</filename> (or <filename>%APPDATA%\Sylpheed\sylpheedrc</filename>) e.g. to <filename>*.bak</filename> and restarting
443 Sylpheed in order to get default entries.</para>
444 </answer>
445 </qandaentry>
446 <qandaentry>
447 <question id="faq-environment-variables">
448 <para>What environment variables have effect on Sylpheed?</para>
449 </question>
450 <answer>
451 <para>Here are the most common variables:</para>
452 <itemizedlist>
453 <listitem>
454 <para><envar>HOME</envar>
455 - location of <filename>.sylpheed-2.0</filename> (config directory) and default folder for Mailboxes.</para>
456 </listitem>
457 <listitem>
458 <para><envar>LANG</envar>,</para>
459 </listitem>
460 <listitem>
461 <para><envar>LC_ALL</envar>,</para>
462 </listitem>
463 <listitem>
464 <para><envar>LC_CTYPE</envar>,</para>
465 </listitem>
466 <listitem>
467 <para><envar>LC_MESSAGES</envar> - locale settings, e.g. language and date format.</para>
468 </listitem>
469 </itemizedlist>
470 <para>For more information on how to make Sylpheed display your language, see the <link linkend="faq-display-language">relevant question</link>.</para>
471 </answer>
472 </qandaentry>
473 <qandaentry>
474 <question>
475 <para>Special characters (e.g. umlauts) are not displayed correctly.</para>
476 </question>
477 <answer>
478 <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>
479 <para>Choose <menuchoice>
480 <guimenu>Configuration</guimenu>
481 <guimenuitem>Common preferences...</guimenuitem>
482 <guimenuitem>Display</guimenuitem>
483 <guimenuitem>General</guimenuitem>
484 </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>
485 <para>You should also make sure that your environment variables regarding locale
486 settings have sensible values.</para>
487 </answer>
488 </qandaentry>
489 <qandaentry>
490 <question>
491 <para>How can I convert my old mailbox/address book from (some mail client).</para>
492 </question>
493 <answer>
494 <para>You can try to
495 export your old mailbox to MH, MBOX or EML format.</para>
496 <tip>
497 <para>Take a look at the <guimenuitem>Add sender to address book...</guimenuitem> item from the <guimenu>Tools</guimenu>
498 menu, it could be a useful alternative or addition, when importing your old
499 contacts.</para>
500 </tip>
501 </answer>
502 </qandaentry>
503 <qandaentry>
504 <question>
505 <para>What config files are there, and what are they used for?</para>
506 </question>
507 <answer>
508 <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
509 text format and quite easy to understand, so don&apos;t fear to take a look
510 into them using a text editor.</para>
511 <itemizedlist>
512 <listitem>
513 <para><filename>sylpheedrc</filename> - main configuration: nearly all options from the
514 settings window, e.g. mailbox location, font
515 entries, etc.</para>
516 </listitem>
517 <listitem>
518 <para><filename>accountrc</filename> - settings for POP/IMAP/NNTP accounts</para>
519 </listitem>
520 <listitem>
521 <para><filename>actionsrc</filename> - user-defined actions</para>
522 </listitem>
523 <listitem>
524 <para><filename>addrbook-*.xml</filename> - contents of your address book</para>
525 </listitem>
526 <listitem>
527 <para><filename>customheaderrc</filename> - contains user-defined header lines</para>
528 </listitem>
529 <listitem>
530 <para><filename>dispheaderrc</filename> - headers to display above the mail body</para>
531 </listitem>
532 <listitem>
533 <para><filename>filter.xml</filename> - filter settings</para>
534 </listitem>
535 <listitem>
536 <para><filename>folderlist.xml</filename> - folder specific settings, e.g. hiding
537 read messages, sort order, etc.</para>
538 </listitem>
539 <listitem>
540 <para><filename>menurc</filename> - key bindings</para>
541 </listitem>
542 </itemizedlist>
543 </answer>
544 </qandaentry>
545 <qandaentry>
546 <question>
547 <para>How do I change the location of user profile directory under Windows?</para>
548 </question>
549 <answer>
550 <para>The configuration files and the mailboxes are saved under the following
551location (<filename>%APPDATA%\Sylpheed</filename>) by default:</para>
552 <para><itemizedlist>
553 <listitem>
554 <para>Windows 2000/XP:
555<filename>C:\Documents and Settings\<replaceable>(user name)</replaceable>\Application Data\Sylpheed</filename></para>
556 </listitem>
557 <listitem>
558 <para>Windows Vista/Seven:
559<filename>C:\Users\<replaceable>(user name)</replaceable>\AppData\Roaming\Sylpheed</filename></para>
560 </listitem>
561 </itemizedlist></para>
562 <para>If you want to change the location of the configuration files, you can
563specify it by the command line option <parameter>--configdir &quot;<replaceable>directory name</replaceable>&quot;</parameter>.
564Create a shortcut of <filename>sylpheed.exe</filename>, and append the option to the link target
565like the following:</para>
566 <screen>&quot;C:\Program Files\Sylpheed\sylpheed.exe&quot; --configdir &quot;D:\Sylpheed&quot;</screen>
567 <para>If <filename>sylpheed.ini</filename> file exists at the same location as <filename>sylpheed.exe</filename>, it will be
568loaded at startup. With this approach, you can make Sylpheed completely portable
569independent of drive letters etc., and you can install it in removable media
570such as USB memory.</para>
571 <note>
572 <para>The installer version, and GnuPG and GPGME use registry.</para>
573 </note>
574 <para>The sample INI file is included in the Sylpheed for Windows installation package as <filename>sample-sylpheed.ini</filename>.
575Please copy or rename it to use.
576<literal>ipcport</literal> specifies the port number of socket for IPC (default is 50215).
577<literal>configdir</literal> specifies the location of configuration files as a relative
578path from the folder in which <filename>sylpheed.exe</filename> is located, or an absolute path.</para>
579 <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>
580 </answer>
581 </qandaentry>
582 <qandaentry>
583 <question>
584 <para>Can I run multiple instances of Sylpheed?</para>
585 </question>
586 <answer>
587 <para>Yes, Sylpheed 3.1 adds support for this often requested feature. The format of the multiple instances command is as follows:</para>
588 <para><command>sylpheed --instance-id <replaceable>ID</replaceable> --configdir <replaceable>path-to-alternative-configdir</replaceable></command></para>
589 <para>Default <parameter>ID</parameter> is set to <literal>sylpheed</literal>, so you can specify any other instance
590<parameter>ID</parameter>. The <parameter>ID</parameter> is used for the name of unix domain
591socket (under UNIX), or mutex name (under Windows). <parameter>configdir</parameter> specifies the configuration directory, i.e. the location of configuration files you want to use with the given instance.</para>
592 <warning>
593 <para>Do not share same configuration directories or mailboxes across multiple instances as this may lead to an unexpected application behavior!</para>
594 </warning>
595 </answer>
596 </qandaentry>
597 <qandaentry>
598 <question>
599 <para>What to do when printing an email prints off the paper?</para>
600 </question>
601 <answer>
602 <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>
603 </answer>
604 </qandaentry>
605 </qandaset>
606</chapter>
diff --git a/faq/en/faq_003.xml b/faq/en/faq_003.xml
new file mode 100644
index 0000000..7fded96
--- /dev/null
+++ b/faq/en/faq_003.xml
@@ -0,0 +1,309 @@
1<?xml version='1.0' encoding='UTF-8'?><chapter id="sylpheed-faq-3">
2 <title>Sylpheed FAQ - Interface</title>
3 <qandaset id="faq-interface">
4<?dbhtml cellspacing="13px" ?> <qandaentry>
5 <question id="faq-display-language">
6 <para>How do I make Sylpheed display my language?</para>
7 </question>
8 <answer>
9 <para>You have to set some environment variables, such as
10 <envar>LANG</envar>, <envar>LC_CTYPE</envar>, <envar>LC_MESSAGES</envar> to your local language.
11 Usually <envar>LANG</envar> (or <envar>LC_ALL</envar>) is sufficient. Note that modern distributions and operating systems do this for you automatically.</para>
12 <para>Under UNIX, if you need to set e.g. the <envar>LANG</envar> environment variable manually, execute the following command (using <literal>sh</literal> or related shell):</para>
13 <para><command>export LANG=<replaceable>value</replaceable></command></para>
14 <para>Replace <replaceable>value</replaceable> with a valid ISO <ulink url="http://en.wikipedia.org/wiki/Language_code">language code</ulink> (e.g. <literal>en_GB</literal> for British English).</para>
15 <para>If you intend to set the displayed language manually under Windows, you can do so by creating the
16<envar>LANG</envar> environment variable with a valid ISO language code value under <menuchoice>
17 <guimenu>Control Panel</guimenu>
18 <guimenuitem>System</guimenuitem>
19 <guisubmenu>Advanced</guisubmenu>
20 <guibutton>Environment Variables</guibutton>
21 </menuchoice>.</para>
22 <para>Also see the <link linkend="faq-environment-variables">question</link> regarding environment variables that have effect on Sylpheed.</para>
23 </answer>
24 </qandaentry>
25 <qandaentry>
26 <question>
27 <para>I don&apos;t like the default font. Can I change that?</para>
28 </question>
29 <answer>
30 <para>Yes. In <menuchoice>
31 <guimenu>Configuration</guimenu>
32 <guimenuitem>Common preferences...</guimenuitem>
33 </menuchoice>, under the
34 <guimenuitem>Display</guimenuitem> tab.</para>
35 </answer>
36 </qandaentry>
37 <qandaentry>
38 <question>
39 <para>There are too many columns in the message list!</para>
40 </question>
41 <answer>
42 <para>In <menuchoice>
43 <guimenu>Configuration</guimenu>
44 <guimenuitem>Common preferences...</guimenuitem>
45 </menuchoice> under the
46 <guimenuitem>Display</guimenuitem> tab, you can press the button <guibutton>Set display item of summary...</guibutton>. That pops up a screen with all the
47 options you can show or leave out of the message
48 list.</para>
49 </answer>
50 </qandaentry>
51 <qandaentry>
52 <question>
53 <para>How do I disable or enable the alternating row colors in the message list?</para>
54 </question>
55 <answer>
56 <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>
57 <programlisting>enable_rules_hint=0</programlisting>
58 <tip>
59 <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>
60 </tip>
61 <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>
62 <programlisting>GtkTreeView::allow-rules = 1</programlisting>
63 <note>
64 <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>
65 </note>
66 </answer>
67 </qandaentry>
68 <qandaentry>
69 <question>
70 <para>Can I use a different editor to write my mails?</para>
71 </question>
72 <answer>
73 <para>You can. In <menuchoice>
74 <guimenu>Configuration</guimenu>
75 <guimenuitem>Common preferences</guimenuitem>
76 </menuchoice>, under
77 the <guimenuitem>Details</guimenuitem> and <guimenuitem>External commands</guimenuitem> tabs, you can define your editor of choice.
78 Remember, if you want to use a command line editor
79 like vi or emacs, to write the name of the shell
80 (term, term, rxvt) with the <parameter>-e</parameter> parameter in front of
81 the editor. E.g.: <command>rxvt -e vi %s</command>.</para>
82 <para>Also, make sure that you have checked <guilabel>Automatically launch the external editor</guilabel> in <menuchoice>
83 <guimenuitem>Common preferences</guimenuitem>
84 <guimenuitem>Compose</guimenuitem>
85 <guimenuitem>Editor</guimenuitem>
86 </menuchoice>, if you want the editor of your choice to be launched every time you begin composing a message.</para>
87 </answer>
88 </qandaentry>
89 <qandaentry>
90 <question>
91 <para>How to change the font size in the Sylpheed interface?</para>
92 </question>
93 <answer>
94 <para>You can set the GTK+ font by <filename>$HOME/.gtkrc-2.0</filename>, or
95 <filename>$HOME/.gtkrc-2.0.mine</filename>,
96 (which is included by <filename>$HOME/.gtkrc-2.0</filename>).
97 For example:</para>
98 <programlisting>style &quot;default&quot; {
99 font = &quot;-adobe-helvetica-medium-r-normal--12-*-*-*-*-*-iso8859-1 &quot;
100}
101widget_class &quot;*&quot; style &quot;default&quot;
102</programlisting>
103 </answer>
104 </qandaentry>
105 <qandaentry>
106 <question>
107 <para>Sylpheed saves my outgoing mail (in Outbox). Can I make it stop doing that?</para>
108 </question>
109 <answer>
110 <para>In <menuchoice>
111 <guimenu>Configuration</guimenu>
112 <guimenuitem>Common preferences...</guimenuitem>
113 </menuchoice>, there is a
114 checkbox <guilabel>Save sent message to outbox</guilabel>. Uncheck it,
115 and it&apos;s solved.</para>
116 </answer>
117 </qandaentry>
118 <qandaentry>
119 <question>
120 <para>How can I change the key bindings (hotkeys) in Sylpheed?</para>
121 </question>
122 <answer>
123 <para>Unlike Sylpheed 1.x, Sylpheed 2.x and 3.x doesn&apos;t allow direct modification of the menu shortcuts by default. Nevertheless, you can use the following methods to configure them:</para>
124 <orderedlist>
125 <listitem>
126 <para><emphasis>Using GNOME 2.8 or later:</emphasis> run gconf-editor from <menuchoice>
127 <guimenu>Applications</guimenu>
128 <guisubmenu>System Tools</guisubmenu>
129 <guimenuitem>Configuration Editor</guimenuitem>
130 </menuchoice>. Select <menuchoice>
131 <guimenu>desktop</guimenu>
132 <guisubmenu>gnome</guisubmenu>
133 <guisubmenu>interface</guisubmenu>
134 </menuchoice> and check <guilabel>can-change-accels</guilabel> there.</para>
135 </listitem>
136 <listitem>
137 <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&apos;t exist):</para>
138 <programlisting>gtk-can-change-accels = 1</programlisting>
139 </listitem>
140 <listitem>
141 <para>When Sylpheed is not running, directly edit <filename>~/.sylpheed-2.0/menurc</filename> with a text editor.</para>
142 </listitem>
143 </orderedlist>
144 <para>After that, the key binding change itself is very simple. Suppose you want to assign a
145 shortcut key to a function, e.g. sending all mail
146 out should start when you press <keycombo>
147 <keycap>Ctrl</keycap>
148 <keycap>Y</keycap>
149 </keycombo>. Click the
150 <guimenu>Message</guimenu> menu and move the mouse over <guimenuitem>Send all messages</guimenuitem>. Now you press <keycombo>
151 <keycap>Ctrl</keycap>
152 <keycap>Y</keycap>
153 </keycombo>. Immediately the menu
154 text is updated and the function is in place. Please
155 note that a previous function that <keycombo>
156 <keycap>Ctrl</keycap>
157 <keycap>Y</keycap>
158 </keycombo> was
159 assigned to, will no longer have a shortcut key. If
160 you want to remove the key binding, do the same
161 thing, but press the <keycap>Delete</keycap> key on the menu item.
162 Then the key binding is removed.</para>
163 <para>Also see <menuchoice>
164 <guimenu>Configuration</guimenu>
165 <guimenuitem>Common preferences...</guimenuitem>
166 <guimenuitem>Details</guimenuitem>
167 <guimenuitem>Interface</guimenuitem>
168 <guilabel>Set key bindings...</guilabel>
169 </menuchoice> where you are able to reset the Default key bindings, or use other predefined key bindings.</para>
170 </answer>
171 </qandaentry>
172 <qandaentry>
173 <question>
174 <para>Can I close windows without the mouse?</para>
175 </question>
176 <answer>
177 <para>Of course! Not all windows, but by pressing <keycap>Escape</keycap>,
178 you can close the address book, the window of viewing
179 a mail source (<menuchoice>
180 <guimenu>View</guimenu>
181 <guimenuitem>Message source</guimenuitem>
182 </menuchoice>), the window of
183 viewing the headers, and several others. Just give
184 it a try and you will find all of them.</para>
185 </answer>
186 </qandaentry>
187 <qandaentry>
188 <question>
189 <para>Can I change the way the date is displayed in the message summary?</para>
190 </question>
191 <answer>
192 <para>As of 0.4.65 you can. The options are:</para>
193 <programlisting> %y = year in numbers %m = month in number
194 %d = day in numbers %c = date/time for locale
195 %A = full weekday name %a = short month name
196 %B = full month name %b = short month name
197 %H = hours in 24-clock %I = hours in 12-clock</programlisting>
198 <para>For more information, go to the <menuchoice>
199 <guimenu>Configuration</guimenu>
200 <guimenuitem>Common preferences</guimenuitem>
201 <guimenuitem>Display</guimenuitem>
202 <guimenuitem>General</guimenuitem>
203 </menuchoice> and choose the <guibutton>...</guibutton> labeled button.
204For more options, see <command>man 3 strftime</command>.</para>
205 </answer>
206 </qandaentry>
207 <qandaentry>
208 <question>
209 <para>Why can&apos;t I see the compface pictures?</para>
210 </question>
211 <answer>
212 <para>You need to enable displaying of the header pane in the
213 general preferences.</para>
214 </answer>
215 </qandaentry>
216 <qandaentry>
217 <question>
218 <para>I still can&apos;t see the pictures. Why not?</para>
219 </question>
220 <answer>
221 <para>You may not have compiled in Compface support. See the appropriate question in the Installation and Configuration section.</para>
222 </answer>
223 </qandaentry>
224 <qandaentry>
225 <question>
226 <para>Why does the URL launcher not launch my web browser?</para>
227 </question>
228 <answer>
229 <para>You need to double click the URL.
230Also, check that you have configured your web browser correctly in <menuchoice>
231 <guimenu>Configuration</guimenu>
232 <guimenuitem>Common preferences...</guimenuitem>
233 <guimenuitem> Details</guimenuitem>
234 <guimenuitem>External commands</guimenuitem>
235 </menuchoice>. </para>
236 </answer>
237 </qandaentry>
238 <qandaentry>
239 <question>
240 <para>Attachments with spaces in the name won&apos;t open!</para>
241 </question>
242 <answer>
243 <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>
244parameter. Example: <command>gedit &apos;%s&apos;</command></para>
245 </answer>
246 </qandaentry>
247 <qandaentry>
248 <question>
249 <para>Execute command for my dynamic signature seems not to be working!</para>
250 </question>
251 <answer>
252 <para>Under Windows, if you have created e.g. a simple batch file to echo a line to be included in your dynamic signature, you need to execute the command (specified under <menuchoice>
253 <guimenu>Account preferences</guimenu>
254 <guisubmenu>Compose</guisubmenu>
255 <guimenuitem>Signature</guimenuitem>
256 <guilabel>Command output</guilabel>
257 </menuchoice>) using either forward slashes or double
258backslashes for paths, for example:</para>
259 <para><command>cmd /c &apos;c:\\signature.bat&apos;</command></para>
260 <para>Note that it is also recommended to enclose paths with single quotes, as is illustrated above.</para>
261 </answer>
262 </qandaentry>
263 <qandaentry>
264 <question>
265 <para>Where is the Bcc when I compose a mail?</para>
266 </question>
267 <answer>
268 <para>Open <menuchoice>
269 <guimenu>Configuration</guimenu>
270 <guimenuitem>Preferences for current account...</guimenuitem>
271 <guimenuitem>Compose</guimenuitem>
272 </menuchoice>. There you can check the <guilabel>Bcc</guilabel> checkbox and optionally enter an email address.</para>
273 </answer>
274 </qandaentry>
275 <qandaentry>
276 <question>
277 <para>How do I change the toolbar?</para>
278 </question>
279 <answer>
280 <para>Go to <menuchoice>
281 <guimenu>View</guimenu>
282 <guimenuitem>Customize toolbar...</guimenuitem>
283 </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>
284 </answer>
285 </qandaentry>
286 <qandaentry>
287 <question>
288 <para>Why isn&apos;t the next message displayed when I delete a message? </para>
289 </question>
290 <answer>
291 <para>Go to <menuchoice>
292 <guimenu>Configuration</guimenu>
293 <guimenuitem>Common preferences...</guimenuitem>
294 <guimenuitem>Details</guimenuitem>
295 <guimenuitem>Interface</guimenuitem>
296 </menuchoice>, and select <guilabel>Always open messages in summary when selected</guilabel>. </para>
297 </answer>
298 </qandaentry>
299 <qandaentry>
300 <question>
301 <para>How can I remove mailing list information from Subject headers?</para>
302 </question>
303 <answer>
304 <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>
305 <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&apos;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>
306 </answer>
307 </qandaentry>
308 </qandaset>
309</chapter>
diff --git a/faq/en/fdl.xml b/faq/en/fdl.xml
new file mode 100644
index 0000000..b4d6c67
--- /dev/null
+++ b/faq/en/fdl.xml
@@ -0,0 +1,383 @@
1<?xml version='1.0' encoding='UTF-8'?>
2<appendix id="sylpheed-faq-4">
3 <appendixinfo>
4 <title>GNU Free Documentation License</title>
5 <pubdate>Version 1.2, November 2002</pubdate>
6 <copyright>
7 <year>2000,2001,2002</year>
8 <holder>Free Software Foundation, Inc.</holder>
9 </copyright>
10 <legalnotice id="gfdl-legalnotice">
11 <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>
12 <para>Everyone is permitted to copy and distribute verbatim copies
13 of this license document, but changing it is not allowed.</para>
14 </legalnotice>
15 <releaseinfo>Version 1.2, November 2002</releaseinfo>
16 </appendixinfo>
17 <title>GNU Free Documentation License</title>
18 <section id="gfdl-0">
19 <title>PREAMBLE</title>
20 <para>The purpose of this License is to make a manual, textbook, or
21other functional and useful document &quot;free&quot; in the sense of freedom: to
22assure everyone the effective freedom to copy and redistribute it, with
23or without modifying it, either commercially or noncommercially.
24Secondarily, this License preserves for the author and publisher a way
25to get credit for their work, while not being considered responsible for
26modifications made by others.</para>
27 <para>This License is a kind of &quot;copyleft&quot;, which means that derivative
28works of the document must themselves be free in the same sense. It
29complements the GNU General Public License, which is a copyleft license
30designed for free software.</para>
31 <para>We have designed this License in order to use it for manuals for
32free software, because free software needs free documentation: a free
33program should come with manuals providing the same freedoms that the
34software does. But this License is not limited to software manuals; it
35can be used for any textual work, regardless of subject matter or
36whether it is published as a printed book. We recommend this License
37principally for works whose purpose is instruction or reference.</para>
38 </section>
39 <section id="gfdl-1">
40 <title>APPLICABILITY AND DEFINITIONS</title>
41 <para id="gfdl-doc">This License applies to any manual or other work, in
42any medium, that contains a notice placed by the copyright holder saying
43it can be distributed under the terms of this License. Such a notice
44grants a world-wide, royalty-free license, unlimited in duration, to use
45that work under the conditions stated herein. The &quot;Document&quot;, below,
46refers to any such manual or work. Any member of the public is a
47licensee, and is addressed as &quot;you&quot;. You accept the license if you
48copy, modify or distribute the work in a way requiring permission under
49copyright law.</para>
50 <para id="gfdl-mod-ver">A &quot;Modified Version&quot; of the Document means any
51work containing the Document or a portion of it, either copied verbatim,
52or with modifications and/or translated into another language.</para>
53 <para id="gfdl-secnd-sect">A &quot;Secondary Section&quot; is a named appendix or
54a front-matter section of the Document that deals exclusively with the
55relationship of the publishers or authors of the Document to the
56Document&apos;s overall subject (or to related matters) and contains nothing
57that could fall directly within that overall subject. (Thus, if the
58Document is in part a textbook of mathematics, a Secondary Section may
59not explain any mathematics.) The relationship could be a matter of
60historical connection with the subject or with related matters, or of
61legal, commercial, philosophical, ethical or political position
62regarding them.</para>
63 <para id="gfdl-inv-sect">The &quot;Invariant Sections&quot; are certain Secondary
64Sections whose titles are designated, as being those of Invariant
65Sections, in the notice that says that the Document is released under
66this License. If a section does not fit the above definition of
67Secondary then it is not allowed to be designated as Invariant. The
68Document may contain zero Invariant Sections. If the Document does not
69identify any Invariant Sections then there are none.</para>
70 <para id="gfdl-cov-text">The &quot;Cover Texts&quot; are certain short passages of
71text that are listed, as Front-Cover Texts or Back-Cover Texts, in the
72notice that says that the Document is released under this License. A
73Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at
74most 25 words.</para>
75 <para id="gfdl-transparent">A &quot;Transparent&quot; copy of the Document means a
76machine-readable copy, represented in a format whose specification is
77available to the general public, that is suitable for revising the
78document straightforwardly with generic text editors or (for images
79composed of pixels) generic paint programs or (for drawings) some widely
80available drawing editor, and that is suitable for input to text
81formatters or for automatic translation to a variety of formats suitable
82for input to text formatters. A copy made in an otherwise Transparent
83file format whose markup, or absence of markup, has been arranged to
84thwart or discourage subsequent modification by readers is not
85Transparent. An image format is not Transparent if used for any
86substantial amount of text. A copy that is not &quot;Transparent&quot; is called
87&quot;Opaque&quot;.</para>
88 <para>Examples of suitable formats for Transparent copies include plain
89ASCII without markup, Texinfo input format, LaTeX input format, SGML or
90XML using a publicly available DTD, and standard-conforming simple HTML,
91PostScript or PDF designed for human modification. Examples of
92transparent image formats include PNG, XCF and JPG. Opaque formats
93include proprietary formats that can be read and edited only by
94proprietary word processors, SGML or XML for which the DTD and/or
95processing tools are not generally available, and the machine-generated
96HTML, PostScript or PDF produced by some word processors for output
97purposes only.</para>
98 <para id="gfdl-title-page">The &quot;Title Page&quot; means, for a printed book,
99the title page itself, plus such following pages as are needed to hold,
100legibly, the material this License requires to appear in the title page.
101For works in formats which do not have any title page as such, &quot;Title
102Page&quot; means the text near the most prominent appearance of the work&apos;s
103title, preceding the beginning of the body of the text.</para>
104 <para id="gfdl-entitled">A section &quot;Entitled XYZ&quot; means a named subunit
105of the Document whose title either is precisely XYZ or contains XYZ in
106parentheses following text that translates XYZ in another language.
107(Here XYZ stands for a specific section name mentioned below, such as
108&quot;Acknowledgements&quot;, &quot;Dedications&quot;, &quot;Endorsements&quot;, or &quot;History&quot;.) To
109&quot;Preserve the Title&quot; of such a section when you modify the Document
110means that it remains a section &quot;Entitled XYZ&quot; according to this
111definition.</para>
112 <para>The Document may include Warranty Disclaimers next to the notice
113which states that this License applies to the Document. These Warranty
114Disclaimers are considered to be included by reference in this License,
115but only as regards disclaiming warranties: any other implication that
116these Warranty Disclaimers may have is void and has no effect on the
117meaning of this License.</para>
118 </section>
119 <section id="gfdl-2">
120 <title>VERBATIM COPYING</title>
121 <para>You may copy and distribute the Document in any medium, either
122commercially or noncommercially, provided that this License, the
123copyright notices, and the license notice saying this License applies to
124the Document are reproduced in all copies, and that you add no other
125conditions whatsoever to those of this License. You may not use
126technical measures to obstruct or control the reading or further copying
127of the copies you make or distribute. However, you may accept
128compensation in exchange for copies. If you distribute a large enough
129number of copies you must also follow the conditions in section 3.
130</para>
131 <para>You may also lend copies, under the same conditions stated above,
132and you may publicly display copies.</para>
133 </section>
134 <section id="gfdl-3">
135 <title>COPYING IN QUANTITY</title>
136 <para>If you publish printed copies (or copies in media that commonly
137have printed covers) of the Document, numbering more than 100, and the
138Document&apos;s license notice requires Cover Texts, you must enclose the
139copies in covers that carry, clearly and legibly, all these Cover Texts:
140Front-Cover Texts on the front cover, and Back-Cover Texts on the back
141cover. Both covers must also clearly and legibly identify you as the
142publisher of these copies. The front cover must present the full title
143with all words of the title equally prominent and visible. You may add
144other material on the covers in addition. Copying with changes limited
145to the covers, as long as they preserve the title of the Document and
146satisfy these conditions, can be treated as verbatim copying in other
147respects.</para>
148 <para>If the required texts for either cover are too voluminous to fit
149legibly, you should put the first ones listed (as many as fit
150reasonably) on the actual cover, and continue the rest onto adjacent
151pages.</para>
152 <para>If you publish or distribute Opaque copies of the Document
153numbering more than 100, you must either include a machine-readable
154Transparent copy along with each Opaque copy, or state in or with each
155Opaque copy a computer-network location from which the general
156network-using public has access to download using public-standard
157network protocols a complete Transparent copy of the Document, free of
158added material. If you use the latter option, you must take reasonably
159prudent steps, when you begin distribution of Opaque copies in quantity,
160to ensure that this Transparent copy will remain thus accessible at the
161stated location until at least one year after the last time you
162distribute an Opaque copy (directly or through your agents or retailers)
163of that edition to the public.</para>
164 <para>It is requested, but not required, that you contact the authors of
165the Document well before redistributing any large number of copies, to
166give them a chance to provide you with an updated version of the
167Document.</para>
168 </section>
169 <section id="gfdl-4">
170 <title>MODIFICATIONS</title>
171 <para>You may copy and distribute a Modified Version of the Document
172under the conditions of sections 2 and 3 above, provided that you
173release the Modified Version under precisely this License, with the
174Modified Version filling the role of the Document, thus licensing
175distribution and modification of the Modified Version to whoever
176possesses a copy of it. In addition, you must do these things in the
177Modified Version:</para>
178 <orderedlist numeration="upperalpha" id="gfdl-modif-cond">
179 <title>GNU FDL Modification Conditions</title>
180 <listitem>
181 <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>
182 </listitem>
183 <listitem>
184 <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>
185 </listitem>
186 <listitem>
187 <simpara>State on the Title page the name of the publisher of the Modified Version, as the publisher.</simpara>
188 </listitem>
189 <listitem>
190 <simpara>Preserve all the copyright notices of the Document. </simpara>
191 </listitem>
192 <listitem>
193 <simpara>Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. </simpara>
194 </listitem>
195 <listitem>
196 <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>
197 </listitem>
198 <listitem>
199 <simpara>Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document&apos;s license notice.</simpara>
200 </listitem>
201 <listitem>
202 <simpara>Include an unaltered copy of this License. </simpara>
203 </listitem>
204 <listitem>
205 <simpara>Preserve the section Entitled &quot;History&quot;, 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 &quot;History&quot; 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>
206 </listitem>
207 <listitem>
208 <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 &quot;History&quot; 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>
209 </listitem>
210 <listitem>
211 <simpara>For any section Entitled &quot;Acknowledgements&quot; or &quot;Dedications&quot;, 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>
212 </listitem>
213 <listitem>
214 <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>
215 </listitem>
216 <listitem>
217 <simpara>Delete any section Entitled &quot;Endorsements&quot;. Such a section may not be included in the Modified Version. </simpara>
218 </listitem>
219 <listitem>
220 <simpara>Do not retitle any existing section to be Entitled &quot;Endorsements&quot; or to conflict in title with any Invariant Section. </simpara>
221 </listitem>
222 <listitem>
223 <simpara>Preserve any Warranty Disclaimers. </simpara>
224 </listitem>
225 </orderedlist>
226 <para>If the Modified Version includes new front-matter sections or
227appendices that qualify as Secondary Sections and contain no material
228copied from the Document, you may at your option designate some or all
229of these sections as invariant. To do this, add their titles to the
230list of Invariant Sections in the Modified Version&apos;s license notice.
231These titles must be distinct from any other section titles.</para>
232 <para>You may add a section Entitled &quot;Endorsements&quot;, provided it
233contains nothing but endorsements of your Modified Version by various
234parties--for example, statements of peer review or that the text has
235been approved by an organization as the authoritative definition of a
236standard.</para>
237 <para>You may add a passage of up to five words as a Front-Cover Text,
238and a passage of up to 25 words as a Back-Cover Text, to the end of the
239list of Cover Texts in the Modified Version. Only one passage of
240Front-Cover Text and one of Back-Cover Text may be added by (or through
241arrangements made by) any one entity. If the Document already includes
242a cover text for the same cover, previously added by you or by
243arrangement made by the same entity you are acting on behalf of, you may
244not add another; but you may replace the old one, on explicit permission
245from the previous publisher that added the old one.</para>
246 <para>The author(s) and publisher(s) of the Document do not by this
247License give permission to use their names for publicity for or to
248assert or imply endorsement of any Modified Version.</para>
249 </section>
250 <section id="gfdl-5">
251 <title>COMBINING DOCUMENTS</title>
252 <para>You may combine the Document with other documents released under
253this License, under the terms defined in <link linkend="gfdl-4">section 4</link> above for modified versions, provided that you include in the
254combination all of the Invariant Sections of all of the original
255documents, unmodified, and list them all as Invariant Sections of your
256combined work in its license notice, and that you preserve all their
257Warranty Disclaimers.</para>
258 <para>The combined work need only contain one copy of this License, and
259multiple identical Invariant Sections may be replaced with a single
260copy. If there are multiple Invariant Sections with the same name but
261different contents, make the title of each such section unique by adding
262at the end of it, in parentheses, the name of the original author or
263publisher of that section if known, or else a unique number. Make the
264same adjustment to the section titles in the list of Invariant Sections
265in the license notice of the combined work.</para>
266 <para>In the combination, you must combine any sections Entitled
267&quot;History&quot; in the various original documents, forming one section
268Entitled &quot;History&quot;; likewise combine any sections Entitled
269&quot;Acknowledgements&quot;, and any sections Entitled &quot;Dedications&quot;. You must
270delete all sections Entitled &quot;Endorsements&quot;.</para>
271 </section>
272 <section id="gfdl-6">
273 <title>COLLECTIONS OF DOCUMENTS</title>
274 <para>You may make a collection consisting of the Document and other
275documents released under this License, and replace the individual copies
276of this License in the various documents with a single copy that is
277included in the collection, provided that you follow the rules of this
278License for verbatim copying of each of the documents in all other
279respects.</para>
280 <para>You may extract a single document from such a collection, and
281distribute it individually under this License, provided you insert a
282copy of this License into the extracted document, and follow this
283License in all other respects regarding verbatim copying of that
284document.</para>
285 </section>
286 <section id="gfdl-7">
287 <title>AGGREGATION WITH INDEPENDENT WORKS</title>
288 <para>A compilation of the Document or its derivatives with other
289separate and independent documents or works, in or on a volume of a
290storage or distribution medium, is called an &quot;aggregate&quot; if the
291copyright resulting from the compilation is not used to limit the legal
292rights of the compilation&apos;s users beyond what the individual works
293permit. When the Document is included in an aggregate, this License does
294not apply to the other works in the aggregate which are not themselves
295derivative works of the Document.</para>
296 <para>If the Cover Text requirement of section 3 is applicable to these
297copies of the Document, then if the Document is less than one half of
298the entire aggregate, the Document&apos;s Cover Texts may be placed on covers
299that bracket the Document within the aggregate, or the electronic
300equivalent of covers if the Document is in electronic form. Otherwise
301they must appear on printed covers that bracket the whole
302aggregate.</para>
303 </section>
304 <section id="gfdl-8">
305 <title>TRANSLATION</title>
306 <para>Translation is considered a kind of modification, so you may
307distribute translations of the Document under the terms of section 4.
308Replacing Invariant Sections with translations requires special
309permission from their copyright holders, but you may include
310translations of some or all Invariant Sections in addition to the
311original versions of these Invariant Sections. You may include a
312translation of this License, and all the license notices in the
313Document, and any Warranty Disclaimers, provided that you also include
314the original English version of this License and the original versions
315of those notices and disclaimers. In case of a disagreement between the
316translation and the original version of this License or a notice or
317disclaimer, the original version will prevail.</para>
318 <para>If a section in the Document is Entitled &quot;Acknowledgements&quot;,
319&quot;Dedications&quot;, or &quot;History&quot;, the requirement (section 4) to Preserve its
320Title (section 1) will typically require changing the actual
321title.</para>
322 </section>
323 <section id="gfdl-9">
324 <title>TERMINATION</title>
325 <para>You may not copy, modify, sublicense, or distribute the Document
326except as expressly provided for under this License. Any other attempt
327to copy, modify, sublicense or distribute the Document is void, and will
328automatically terminate your rights under this License. However,
329parties who have received copies, or rights, from you under this License
330will not have their licenses terminated so long as such parties remain
331in full compliance.</para>
332 </section>
333 <section id="gfdl-10">
334 <title>FUTURE REVISIONS OF THIS LICENSE</title>
335 <para>The Free Software Foundation may publish new, revised versions of
336the GNU Free Documentation License from time to time. Such new versions
337will be similar in spirit to the present version, but may differ in
338detail to address new problems or concerns. See
339http://www.gnu.org/copyleft/.</para>
340 <para>Each version of the License is given a distinguishing version
341number. If the Document specifies that a particular numbered version of
342this License &quot;or any later version&quot; applies to it, you have the option
343of following the terms and conditions either of that specified version
344or of any later version that has been published (not as a draft) by the
345Free Software Foundation. If the Document does not specify a version
346number of this License, you may choose any version ever published (not
347as a draft) by the Free Software Foundation.</para>
348 </section>
349 <section id="gfdl-addendum">
350 <title>ADDENDUM: How to use this License for your documents</title>
351 <para>To use this License in a document you have written, include a copy
352of the License in the document and put the following copyright and
353license notices just after the title page:</para>
354 <blockquote id="copyright-sample">
355 <title>Sample Invariant Sections list</title>
356 <para>
357 Copyright (c) YEAR YOUR NAME.
358 Permission is granted to copy, distribute and/or modify this document
359 under the terms of the GNU Free Documentation License, Version 1.2
360 or any later version published by the Free Software Foundation;
361 with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
362 A copy of the license is included in the section entitled &quot;GNU
363 Free Documentation License&quot;.
364</para>
365 </blockquote>
366 <para>If you have Invariant Sections, Front-Cover Texts and Back-Cover
367Texts, replace the &quot;with...Texts.&quot; line with this:</para>
368 <blockquote id="inv-cover-sample">
369 <title>Sample Invariant Sections list</title>
370 <para>
371 with the Invariant Sections being LIST THEIR TITLES, with the
372 Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
373</para>
374 </blockquote>
375 <para>If you have Invariant Sections without Cover Texts, or some other
376combination of the three, merge those two alternatives to suit the
377situation.</para>
378 <para>If your document contains nontrivial examples of program code, we
379recommend releasing these examples in parallel under your choice of free
380software license, such as the GNU General Public License, to permit
381their use in free software.</para>
382 </section>
383</appendix>
diff --git a/faq/en/sylpheed-faq-1.html b/faq/en/sylpheed-faq-1.html
new file mode 100644
index 0000000..3c2f329
--- /dev/null
+++ b/faq/en/sylpheed-faq-1.html
@@ -0,0 +1,964 @@
1<html>
2 <head>
3 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4
5 <title>Chapter&nbsp;1.&nbsp;Sylpheed FAQ - General Information</title>
6 <meta name="generator" content="DocBook XSL Stylesheets V1.68.1">
7 <link rel="start" href="sylpheed-faq.html" title="Sylpheed FAQ">
8 <link rel="up" href="sylpheed-faq.html" title="Sylpheed FAQ">
9 <link rel="prev" href="sylpheed-faq.html" title="Sylpheed FAQ">
10 <link rel="next" href="sylpheed-faq-2.html" title="Chapter&nbsp;2.&nbsp;Sylpheed FAQ - Installation and Configuration">
11 <link rel="chapter" href="sylpheed-faq-1.html" title="Chapter&nbsp;1.&nbsp;Sylpheed FAQ - General Information">
12 <link rel="chapter" href="sylpheed-faq-2.html" title="Chapter&nbsp;2.&nbsp;Sylpheed FAQ - Installation and Configuration">
13 <link rel="chapter" href="sylpheed-faq-3.html" title="Chapter&nbsp;3.&nbsp;Sylpheed FAQ - Interface">
14 <link rel="appendix" href="sylpheed-faq-4.html" title="Appendix&nbsp;A.&nbsp;GNU Free Documentation License"><style type="text/css">
15pre.programlisting, pre.screen {
16background-color : #e0e0e0;
17padding : 0.2cm;
18}
19.question {
20font-weight : bold;
21}
22
23</style></head>
24 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
25 <div class="navheader">
26 <table width="100%" summary="Navigation header">
27 <tr>
28 <th colspan="3" align="center">Chapter&nbsp;1.&nbsp;Sylpheed FAQ - General Information</th>
29 </tr>
30 <tr>
31 <td width="20%" align="left"><a accesskey="p" href="sylpheed-faq.html">Prev</a>&nbsp;
32 </td>
33 <th width="60%" align="center">&nbsp;</th>
34 <td width="20%" align="right">&nbsp;<a accesskey="n" href="sylpheed-faq-2.html">Next</a></td>
35 </tr>
36 </table>
37 <hr>
38 </div>
39 <div class="chapter" lang="en">
40 <div class="titlepage">
41 <div>
42 <div>
43 <h2 class="title"><a name="sylpheed-faq-1"></a>Chapter&nbsp;1.&nbsp;Sylpheed FAQ - General Information
44 </h2>
45 </div>
46 </div>
47 </div>
48 <div class="qandaset">
49 <dl>
50 <dt>1.1. <a href="sylpheed-faq-1.html#d0e90">
51 Are there FAQ's in other languages?
52 </a></dt>
53 <dt>1.2. <a href="sylpheed-faq-1.html#d0e129">
54 What is Sylpheed?
55 </a></dt>
56 <dt>1.3. <a href="sylpheed-faq-1.html#d0e160">
57 Where can I get Sylpheed?
58 </a></dt>
59 <dt>1.4. <a href="sylpheed-faq-1.html#d0e177">
60 Who writes Sylpheed?
61 </a></dt>
62 <dt>1.5. <a href="sylpheed-faq-1.html#d0e187">
63 What does the name Sylpheed mean?
64 </a></dt>
65 <dt>1.6. <a href="sylpheed-faq-1.html#d0e197">
66 How does Sylpheed store mails?
67 </a></dt>
68 <dt>1.7. <a href="sylpheed-faq-1.html#d0e206">
69 Why does the auto collection of mail not work?
70 </a></dt>
71 <dt>1.8. <a href="sylpheed-faq-1.html#d0e213">
72 Does Sylpheed have mail filtering?
73 </a></dt>
74 <dt>1.9. <a href="sylpheed-faq-1.html#d0e227">
75 Can Sylpheed handle IMAP mail?
76 </a></dt>
77 <dt>1.10. <a href="sylpheed-faq-1.html#d0e234">
78 Can Sylpheed handle local unix mailboxes?
79 </a></dt>
80 <dt>1.11. <a href="sylpheed-faq-1.html#d0e241">
81 Can Sylpheed handle IPv6?
82 </a></dt>
83 <dt>1.12. <a href="sylpheed-faq-1.html#d0e248">
84 Does Sylpheed support encryption like GPG?
85 </a></dt>
86 <dt>1.13. <a href="sylpheed-faq-1.html#d0e255">
87 How does Sylpheed check for MIME types?
88 </a></dt>
89 <dt>1.14. <a href="sylpheed-faq-1.html#d0e262">Does Sylpheed allow me to write HTML styled messages?
90 </a></dt>
91 <dt>1.15. <a href="sylpheed-faq-1.html#d0e269">Does Sylpheed have automatic name completion in the address fields?
92 </a></dt>
93 <dt>1.16. <a href="sylpheed-faq-1.html#d0e309">Fine, but when I hit the Tab key I either get an error message or nothing happens at all.
94 </a></dt>
95 <dt>1.17. <a href="sylpheed-faq-1.html#d0e334">Why is Sylpheed so fast?
96 </a></dt>
97 <dt>1.18. <a href="sylpheed-faq-1.html#d0e341">Where can I get the current patches for Sylpheed?
98 </a></dt>
99 <dt>1.19. <a href="sylpheed-faq-1.html#d0e354">How can I send in patches, report bugs, talk about Sylpheed with others?
100 </a></dt>
101 <dt>1.20. <a href="sylpheed-faq-1.html#d0e381">When I send mail, the Content-Type header says the mail is in
102 US-ASCII, even when I specified ISO-8859-1?
103 </a></dt>
104 <dt>1.21. <a href="sylpheed-faq-1.html#d0e388">Why does it look like word wrap is not working?
105 </a></dt>
106 <dt>1.22. <a href="sylpheed-faq-1.html#d0e414">How do I copy my mail archive to another machine? </a></dt>
107 <dt>1.23. <a href="sylpheed-faq-1.html#d0e460">Can I import a mbox into Sylpheed's MH mailfolders?
108 </a></dt>
109 <dt>1.24. <a href="sylpheed-faq-1.html#d0e473">
110 Can I use procmail to sort my mails with the MH mail handling?
111 </a></dt>
112 <dt>1.25. <a href="sylpheed-faq-1.html#d0e490">
113 When I upgrade Sylpheed, are there things I should be aware of?
114 </a></dt>
115 <dt>1.26. <a href="sylpheed-faq-1.html#d0e530">How can I quickly update the views in Sylpheed?
116 </a></dt>
117 <dt>1.27. <a href="sylpheed-faq-1.html#d0e549">Why can't I use gvim as external editor?
118 </a></dt>
119 <dt>1.28. <a href="sylpheed-faq-1.html#d0e562">Can I quote just parts of the original message when replying?
120 </a></dt>
121 <dt>1.29. <a href="sylpheed-faq-1.html#d0e572">Can I reply without quoting at all?
122 </a></dt>
123 <dt>1.30. <a href="sylpheed-faq-1.html#d0e589"> Does Sylpheed provide an anti-spam feature? </a></dt>
124 <dt>1.31. <a href="sylpheed-faq-1.html#d0e627">Are there any plug-ins extending standard Sylpheed functionality?</a></dt>
125 <dt>1.32. <a href="sylpheed-faq-1.html#d0e651">Where I can find the latest Sylpheed FAQ and manual?
126 </a></dt>
127 <dt>1.33. <a href="sylpheed-faq-1.html#d0e672">Where I can obtain source files for this document?</a></dt>
128 <dt>1.34. <a href="sylpheed-faq-1.html#d0e702">I have found an error and/or outdated information in this document!</a></dt>
129 <dt>1.35. <a href="sylpheed-faq-1.html#d0e712">Who are the members of the Sylpheed Documentation Project?</a></dt>
130 </dl>
131 <table border="0" summary="Q and A Set" cellspacing="13px">
132 <col align="left" width="1%">
133 <tbody>
134 <tr class="question">
135 <td align="left" valign="top"><a name="d0e90"></a><a name="faq-languages"></a><b>1.1.</b></td>
136 <td align="left" valign="top">
137 <p>
138 Are there FAQ's in other languages?
139
140 </p>
141 </td>
142 </tr>
143 <tr class="answer">
144 <td align="left" valign="top"><b></b></td>
145 <td align="left" valign="top">
146 <p>
147 Yes. Here are links to several translations:
148 </p>
149 <div class="itemizedlist">
150 <ul type="disc">
151 <li>
152 <p><a href="http://sylpheeddoc.sourceforge.net/fr/faq/faq.html" target="_top">Sylpheed FAQ in French</a>, translated by Olivier Delhomme.
153 </p>
154 </li>
155 <li>
156 <p><a href="http://sylpheeddoc.sourceforge.net/de/faq/faq.html" target="_top">Sylpheed FAQ in German</a>, translated by Nicolas Kaiser.
157 </p>
158 </li>
159 <li>
160 <p><a href="http://sylpheeddoc.sourceforge.net/es/faq/faq.html" target="_top">Sylpheed FAQ in Spanish</a>, translated by Ricardo Mones Lastra.
161 </p>
162 </li>
163 <li>
164 <p><a href="http://sylpheeddoc.sourceforge.net/zh_TW.Big5/sylpheed-faq.html" target="_top">Sylpheed FAQ in Traditional Chinese</a>, courtesy of Franklin.
165 </p>
166 </li>
167 </ul>
168 </div>
169 <p>
170 You can always download this FAQ from the <a href="http://sylpheeddoc.sourceforge.net/en/faq/sylpheed-faq.html" target="_top">Sylpheed Documentation Project website</a>.
171 </p>
172 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
173 <h3 class="title">Note</h3>
174 <p>Did not find your language in the list? Would you like to contribute with a new translation to the Sylpheed Documentation
175 Project? Then please contact the Project members at <a href="http://sylpheeddoc.sourceforge.net/" target="_top">their website</a>. Thanks in advance.
176 </p>
177 </div>
178 </td>
179 </tr>
180 <tr class="question">
181 <td align="left" valign="top"><a name="d0e129"></a><a name="faq-what-sylpheed"></a><b>1.2.</b></td>
182 <td align="left" valign="top">
183 <p>
184 What is Sylpheed?
185
186 </p>
187 </td>
188 </tr>
189 <tr class="answer">
190 <td align="left" valign="top"><b></b></td>
191 <td align="left" valign="top">
192 <p>
193 Sylpheed is an email client (and news reader) based on GTK+,
194 running on the X Window System or Microsoft Windows, and aiming for:
195 </p>
196 <div class="itemizedlist">
197 <ul type="disc">
198 <li>
199 <p>Quick response</p>
200 </li>
201 <li>
202 <p>Graceful, and sophisticated interface</p>
203 </li>
204 <li>
205 <p>Easy configuration, intuitive operation</p>
206 </li>
207 <li>
208 <p>High reliability</p>
209 </li>
210 <li>
211 <p>Internationalization and multilingualization support</p>
212 </li>
213 <li>
214 <p>Abundant features</p>
215 </li>
216 </ul>
217 </div>
218 <p>As the Sylpheed <code class="filename">README</code> file reads: The appearance and interface are similar to some popular e-mail clients for
219 Windows, such as Outlook Express or Becky!. Many commands are accessible with
220 the keyboard like the Emacs-based mailers such as Mew and Wanderlust.
221 So you will be able to migrate to Sylpheed without much discomfort, even if
222 you are accustomed to other mailers.
223 </p>
224 </td>
225 </tr>
226 <tr class="question">
227 <td align="left" valign="top"><a name="d0e160"></a><a name="faq-get-sylpheed"></a><b>1.3.</b></td>
228 <td align="left" valign="top">
229 <p>
230 Where can I get Sylpheed?
231
232 </p>
233 </td>
234 </tr>
235 <tr class="answer">
236 <td align="left" valign="top"><b></b></td>
237 <td align="left" valign="top">
238 <p>
239 You can download it from the <a href="http://sylpheed.sraoss.jp/en/download.html" target="_top">download page</a> on <a href="http://sylpheed.sraoss.jp/en/" target="_top">Sylpheed website</a>. There are links to download
240 tarball sources, patches to the previous version, and also links to the Sylpheed for Windows binaries, including
241 the installer, the ZIP archive, and the patch to the previous Sylpheed for Windows version.
242 </p>
243 <p>Depending on the state of the Sylpheed development cycle, you may be offered links to development versions such as beta and
244 RC releases. These might not be suitable for everyday use, however, so you may want to stick with the stable release, anyway.
245 </p>
246 <p>Also on the download page, you can download Sylph-Searcher (which is a program that enables fast full-text search of messages
247 stored in mailboxes of Sylpheed, or normal MH folders), and LibSylph (which is a library that provides Sylpheed core features
248 independent from the UI of Sylpheed).
249 </p>
250 </td>
251 </tr>
252 <tr class="question">
253 <td align="left" valign="top"><a name="d0e177"></a><a name="faq-writes-sylpheed"></a><b>1.4.</b></td>
254 <td align="left" valign="top">
255 <p>
256 Who writes Sylpheed?
257
258 </p>
259 </td>
260 </tr>
261 <tr class="answer">
262 <td align="left" valign="top"><b></b></td>
263 <td align="left" valign="top">
264 <p>
265 Hiroyuki Yamamoto <code class="email">&lt;<a href="mailto:hiro-y@kcn.ne.jp">hiro-y@kcn.ne.jp</a>&gt;</code>.
266
267 </p>
268 </td>
269 </tr>
270 <tr class="question">
271 <td align="left" valign="top"><a name="d0e187"></a><a name="faq-sylpheed-name"></a><b>1.5.</b></td>
272 <td align="left" valign="top">
273 <p>
274 What does the name Sylpheed mean?
275
276 </p>
277 </td>
278 </tr>
279 <tr class="answer">
280 <td align="left" valign="top"><b></b></td>
281 <td align="left" valign="top">
282 <p>
283 It means <span class="emphasis"><em>light weight</em></span>, like air. This comes from the
284 name of the wind spirits, the Sylphs.
285
286 </p>
287 </td>
288 </tr>
289 <tr class="question">
290 <td align="left" valign="top"><a name="d0e197"></a><a name="faq-sylpheed-store-mail"></a><b>1.6.</b></td>
291 <td align="left" valign="top">
292 <p>
293 How does Sylpheed store mails?
294
295 </p>
296 </td>
297 </tr>
298 <tr class="answer">
299 <td align="left" valign="top"><b></b></td>
300 <td align="left" valign="top">
301 <p>
302 Mails are stored in the MH mailfile format as used by MH
303 and EMH. Maildir, mbox, and eml formats are not (yet)
304 supported, although it is possible to import an mbox
305 file or an eml file into a Sylpheed mailbox.
306 </p>
307 <p>You can manage your mails just with Sylpheed, or together with another mailer based on the MH format (e.g. Mew). The MH format
308 has less possibility
309 of losing mails on failures since one file corresponds to one mail. You can also utilize fetchmail
310 and/or procmail, and external programs on receiving (like inc or imget).
311 </p>
312 </td>
313 </tr>
314 <tr class="question">
315 <td align="left" valign="top"><a name="d0e206"></a><a name="faq-auto-collection-sylpheed"></a><b>1.7.</b></td>
316 <td align="left" valign="top">
317 <p>
318 Why does the auto collection of mail not work?
319
320 </p>
321 </td>
322 </tr>
323 <tr class="answer">
324 <td align="left" valign="top"><b></b></td>
325 <td align="left" valign="top">
326 <p>
327 Auto collection works since version 0.5.1. If you need it
328 or want it, you should upgrade.
329
330 </p>
331 </td>
332 </tr>
333 <tr class="question">
334 <td align="left" valign="top"><a name="d0e213"></a><a name="faq-filtering-sylpheed"></a><b>1.8.</b></td>
335 <td align="left" valign="top">
336 <p>
337 Does Sylpheed have mail filtering?
338
339 </p>
340 </td>
341 </tr>
342 <tr class="answer">
343 <td align="left" valign="top"><b></b></td>
344 <td align="left" valign="top">
345 <p>
346 Yes. You can find it in <span class="guimenu">Configuration</span> -&gt; <span class="guimenuitem">Filter settings...</span></p>
347 <p>
348 Please note that filtering is not yet implemented for IMAP accounts.
349
350 </p>
351 </td>
352 </tr>
353 <tr class="question">
354 <td align="left" valign="top"><a name="d0e227"></a><a name="faq-imap-sylpheed"></a><b>1.9.</b></td>
355 <td align="left" valign="top">
356 <p>
357 Can Sylpheed handle IMAP mail?
358
359 </p>
360 </td>
361 </tr>
362 <tr class="answer">
363 <td align="left" valign="top"><b></b></td>
364 <td align="left" valign="top">
365 <p>
366 Yes. As of version 0.4.99 IMAP is supported.
367
368 </p>
369 </td>
370 </tr>
371 <tr class="question">
372 <td align="left" valign="top"><a name="d0e234"></a><a name="faq-local-unix-sylpheed"></a><b>1.10.</b></td>
373 <td align="left" valign="top">
374 <p>
375 Can Sylpheed handle local unix mailboxes?
376
377 </p>
378 </td>
379 </tr>
380 <tr class="answer">
381 <td align="left" valign="top"><b></b></td>
382 <td align="left" valign="top">
383 <p>
384 Yes.
385
386 </p>
387 </td>
388 </tr>
389 <tr class="question">
390 <td align="left" valign="top"><a name="d0e241"></a><a name="faq-ipv6-sylpheed"></a><b>1.11.</b></td>
391 <td align="left" valign="top">
392 <p>
393 Can Sylpheed handle IPv6?
394
395 </p>
396 </td>
397 </tr>
398 <tr class="answer">
399 <td align="left" valign="top"><b></b></td>
400 <td align="left" valign="top">
401 <p>
402 Yes, IPv6 is fully supported in Sylpheed.
403
404 </p>
405 </td>
406 </tr>
407 <tr class="question">
408 <td align="left" valign="top"><a name="d0e248"></a><a name="faq-encryption-gpg-sylpheed"></a><b>1.12.</b></td>
409 <td align="left" valign="top">
410 <p>
411 Does Sylpheed support encryption like GPG?
412
413 </p>
414 </td>
415 </tr>
416 <tr class="answer">
417 <td align="left" valign="top"><b></b></td>
418 <td align="left" valign="top">
419 <p>
420 Yes. GPG is implemented and works fine. For activating it in Sylpheed,
421 see the appropriate question in the Installation section.
422
423 </p>
424 </td>
425 </tr>
426 <tr class="question">
427 <td align="left" valign="top"><a name="d0e255"></a><a name="faq-mime-types-sylpheed"></a><b>1.13.</b></td>
428 <td align="left" valign="top">
429 <p>
430 How does Sylpheed check for MIME types?
431
432 </p>
433 </td>
434 </tr>
435 <tr class="answer">
436 <td align="left" valign="top"><b></b></td>
437 <td align="left" valign="top">
438 <p>
439 Sylpheed uses the Mutt type of mime checking.
440
441 </p>
442 </td>
443 </tr>
444 <tr class="question">
445 <td align="left" valign="top"><a name="d0e262"></a><a name="faq-html-sylpheed"></a><b>1.14.</b></td>
446 <td align="left" valign="top">
447 <p>Does Sylpheed allow me to write HTML styled messages?
448
449 </p>
450 </td>
451 </tr>
452 <tr class="answer">
453 <td align="left" valign="top"><b></b></td>
454 <td align="left" valign="top">
455 <p>
456 No. A discussion has gone around over this topic, and
457 the outcome was that HTML mail is not wanted. If you
458 really need to send HTML, you can of course attach a
459 web page to an email.
460 </p>
461 </td>
462 </tr>
463 <tr class="question">
464 <td align="left" valign="top"><a name="d0e269"></a><a name="faq-completion-adress-sylpheed"></a><b>1.15.</b></td>
465 <td align="left" valign="top">
466 <p>Does Sylpheed have automatic name completion in the address fields?
467
468 </p>
469 </td>
470 </tr>
471 <tr class="answer">
472 <td align="left" valign="top"><b></b></td>
473 <td align="left" valign="top">
474 <p>
475 Yes. When you search for a name that starts with "<code class="literal">don</code>",
476 type "<code class="literal">don</code>" (without the quotes) and it will show you the correct name (when only one "don"
477 exists in your address book. Otherwise a drop-down list
478 appears, which allows you to select the name you want.
479 E.g. Donald Duck, Don Johnson. But also email addresses
480 starting with "<code class="literal">don</code>" will appear in the list (like
481 "<code class="literal">don.giovanni@maffia.org</code>").
482 </p>
483 <p>Prior to Sylpheed 3.1, users needed to press the <span><strong class="keycap">Tab</strong></span> key before the search would start. If you still prefer the previous behavior, you can enable it by checking <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Common preferences...</span>-&gt;<span class="guimenuitem">Details</span>-&gt;<span class="guimenuitem">Other</span>-&gt;<span class="guisubmenu">Address book</span>+<span class="guilabel">Address auto-completion:</span>+<span class="guilabel">Start with Tab</span>.
484 </p>
485 </td>
486 </tr>
487 <tr class="question">
488 <td align="left" valign="top"><a name="d0e309"></a><a name="faq-tab-error-sylpheed"></a><b>1.16.</b></td>
489 <td align="left" valign="top">
490 <p>Fine, but when I hit the Tab key I either get an error message or nothing happens at all.
491
492 </p>
493 </td>
494 </tr>
495 <tr class="answer">
496 <td align="left" valign="top"><b></b></td>
497 <td align="left" valign="top">
498 <p>
499 When you want to use name completion, make sure that
500 there are names in your address book. If there are no
501 names, even Sylpheed has a hard time completing
502 something.
503 </p>
504 <p>If nothing happens at all when typing text in the address fields, make sure that you have the address auto-completion enabled
505 by checking that the following preference is not selected: <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Common preferences...</span>-&gt;<span class="guimenuitem">Details</span>-&gt;<span class="guimenuitem">Other</span>-&gt;<span class="guisubmenu">Address book</span>+<span class="guilabel">Address auto-completion:</span>+<span class="guilabel">Disabled</span>.
506 </p>
507 </td>
508 </tr>
509 <tr class="question">
510 <td align="left" valign="top"><a name="d0e334"></a><a name="faq-sylpheed-fast"></a><b>1.17.</b></td>
511 <td align="left" valign="top">
512 <p>Why is Sylpheed so fast?
513
514 </p>
515 </td>
516 </tr>
517 <tr class="answer">
518 <td align="left" valign="top"><b></b></td>
519 <td align="left" valign="top">
520 <p>That's what it is designed for!
521
522 </p>
523 </td>
524 </tr>
525 <tr class="question">
526 <td align="left" valign="top"><a name="d0e341"></a><a name="faq-patches-sylpheed"></a><b>1.18.</b></td>
527 <td align="left" valign="top">
528 <p>Where can I get the current patches for Sylpheed?
529
530 </p>
531 </td>
532 </tr>
533 <tr class="answer">
534 <td align="left" valign="top"><b></b></td>
535 <td align="left" valign="top">
536 <p>In most cases, current patches are being posted by Sylpheed users and contributors to the <a href="http://www.sraoss.jp/mailman/listinfo/sylpheed" target="_top">Sylpheed mailing list</a> <code class="email">&lt;<a href="mailto:sylpheed@sraoss.jp">sylpheed@sraoss.jp</a>&gt;</code>.
537 (Also see the Installation section on how to install a patch.)
538
539 </p>
540 </td>
541 </tr>
542 <tr class="question">
543 <td align="left" valign="top"><a name="d0e354"></a><a name="faq-send-patches-sylpheed"></a><b>1.19.</b></td>
544 <td align="left" valign="top">
545 <p>How can I send in patches, report bugs, talk about Sylpheed with others?
546
547 </p>
548 </td>
549 </tr>
550 <tr class="answer">
551 <td align="left" valign="top"><b></b></td>
552 <td align="left" valign="top">
553 <p>To talk to others, you should join the Sylpheed mailing
554 list at <a href="http://www.sraoss.jp/mailman/listinfo/sylpheed" target="_top">
555 <code class="literal">http://www.sraoss.jp/mailman/listinfo/sylpheed</code>
556 </a>. Note that there is
557 a Japanese and an English list, so pick the right one!
558 If you have made a patch that you want the world to know
559 of, please post it either to the mailing list, or contact the Sylpheed author, Hiroyuki Yamamoto <code class="email">&lt;<a href="mailto:hiro-y@kcn.ne.jp">hiro-y@kcn.ne.jp</a>&gt;</code>.
560 </p>
561 <p>Please supply the information of <span class="guimenu">Tools</span>-&gt;<span class="guimenuitem">Log window</span>, or the contents of
562 <code class="filename">sylpheed.log</code>, which is located under the configuration folder, when
563 reporting bugs.
564 </p>
565 </td>
566 </tr>
567 <tr class="question">
568 <td align="left" valign="top"><a name="d0e381"></a><a name="faq-content-type-header-sylpheed"></a><b>1.20.</b></td>
569 <td align="left" valign="top">
570 <p>When I send mail, the Content-Type header says the mail is in
571 US-ASCII, even when I specified ISO-8859-1?
572
573 </p>
574 </td>
575 </tr>
576 <tr class="answer">
577 <td align="left" valign="top"><b></b></td>
578 <td align="left" valign="top">
579 <p>If ISO-8859-1 characters (&gt;= 0x80) are not used in the
580 message body, Sylpheed will automatically set the
581 charset value in the Content-Type header as US-ASCII.
582
583 </p>
584 </td>
585 </tr>
586 <tr class="question">
587 <td align="left" valign="top"><a name="d0e388"></a><a name="faq-word-wrap-sylpheed"></a><b>1.21.</b></td>
588 <td align="left" valign="top">
589 <p>Why does it look like word wrap is not working?
590
591 </p>
592 </td>
593 </tr>
594 <tr class="answer">
595 <td align="left" valign="top"><b></b></td>
596 <td align="left" valign="top">
597 <p>Word wrapping is a bit peculiar perhaps. You can type
598 lines as long as you like. By the time you send or queue
599 a mail with long lines, Sylpheed will first wrap the
600 lines to the line length you set up, and then the mail
601 is queued. This is more convenient than you think. Once
602 a line is wrapped (hard line breaks are inserted in the
603 text) and you add something in a line there, the next
604 line will move to a separate new line, leaving one or
605 two words from the previous line "hanging there" alone.
606 E.g.
607
608 </p>
609 <div class="literallayout">
610 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This&nbsp;is&nbsp;a&nbsp;long&nbsp;line&nbsp;that<br>
611 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;is&nbsp;wrapped.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
612 </p>
613 </div>
614 <p>Now you add one word in the first line:
615
616 </p>
617 <div class="literallayout">
618 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This&nbsp;is&nbsp;a&nbsp;very&nbsp;long&nbsp;line<br>
619 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;that<br>
620 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;is&nbsp;wrapped&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
621 </p>
622 </div>
623 <p>This would cause you a lot of manual reformatting to get
624 a presentable mail again.
625
626
627 </p>
628 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
629 <h3 class="title">Note</h3>
630 <p>As of Sylpheed 0.8.0., active word wrap has been
631 implemented. You can turn it on in <span class="guisubmenu">Common Preferences</span>-&gt;<span class="guimenuitem">Compose</span>-&gt;<span class="guimenuitem">Editor</span>+<span class="guilabel">Wrap on input</span>.
632
633 </p>
634 </div>
635 </td>
636 </tr>
637 <tr class="question">
638 <td align="left" valign="top"><a name="d0e414"></a><a name="d0e415"></a><b>1.22.</b></td>
639 <td align="left" valign="top">
640 <p>How do I copy my mail archive to another machine? </p>
641 </td>
642 </tr>
643 <tr class="answer">
644 <td align="left" valign="top"><b></b></td>
645 <td align="left" valign="top">
646 <p>You need to copy the <code class="filename">sylpheed-2.0</code> directory with your user profile, and your entire local mail archive.
647 </p>
648 <p>Under UNIX, the user profile is stored in <code class="filename">$HOME/.sylpheed-2.0</code> by default, and your local mail archive is by default located in <code class="filename">$HOME/Mail</code>.
649 </p>
650 <p>While under Windows 2000/XP, the user profile is stored in <code class="filename">C:\Documents and Settings\<em class="replaceable"><code>(user name)</code></em>\Application Data\Sylpheed</code> by default, and your local mail archive is by default located in <code class="filename">C:\Documents and Settings\<em class="replaceable"><code>(user name)</code></em>\Application Data\Sylpheed\Mailboxes\Mail</code>.
651 </p>
652 <p>Under Windows Vista/Seven, the directory paths are <code class="filename">C:\Users\<em class="replaceable"><code>(user name)</code></em>\AppData\Roaming\Sylpheed</code>, and <code class="filename">C:\Users\<em class="replaceable"><code>(user name)</code></em>\AppData\Roaming\Sylpheed\Mailboxes\Mail</code>, respectively.
653 </p>
654 </td>
655 </tr>
656 <tr class="question">
657 <td align="left" valign="top"><a name="d0e460"></a><a name="faq-import-mbox-sylpheed"></a><b>1.23.</b></td>
658 <td align="left" valign="top">
659 <p>Can I import a mbox into Sylpheed's MH mailfolders?
660
661 </p>
662 </td>
663 </tr>
664 <tr class="answer">
665 <td align="left" valign="top"><b></b></td>
666 <td align="left" valign="top">
667 <p>
668 Yes, just create/select the folder you want your
669 mails in, and select <span class="guimenuitem">Import mbox file...</span> in the <span class="guimenu">File</span>
670 menu.
671 </p>
672 </td>
673 </tr>
674 <tr class="question">
675 <td align="left" valign="top"><a name="d0e473"></a><a name="faq-procmail-use-sylpheed"></a><b>1.24.</b></td>
676 <td align="left" valign="top">
677 <p>
678 Can I use procmail to sort my mails with the MH mail handling?
679
680 </p>
681 </td>
682 </tr>
683 <tr class="answer">
684 <td align="left" valign="top"><b></b></td>
685 <td align="left" valign="top">
686 <p>
687 Yes. Just make sure that you add <code class="computeroutput">/.</code> to the end of a rule so
688 procmail knows you are filtering into an MH mail folder. Example:
689
690 </p><pre class="programlisting">0:
691* ^Subject:.*sylpheed
692sylpheedmail/.
693</pre><p>Check <span><strong class="command">man procmail</strong></span> for details.
694
695 </p>
696 </td>
697 </tr>
698 <tr class="question">
699 <td align="left" valign="top"><a name="d0e490"></a><a name="faq-upgrade-sylpheed"></a><b>1.25.</b></td>
700 <td align="left" valign="top">
701 <p>
702 When I upgrade Sylpheed, are there things I should be aware of?
703
704 </p>
705 </td>
706 </tr>
707 <tr class="answer">
708 <td align="left" valign="top"><b></b></td>
709 <td align="left" valign="top">
710 <p>
711 Yes!
712 </p>
713 <div class="itemizedlist">
714 <ul type="disc">
715 <li>
716 <p>Upgrade to 0.4.50: you should reconfigure your newsgroup settings</p>
717 </li>
718 <li>
719 <p>Upgrade to 0.4.63: you should set the URL string colors from the <span class="guimenu">Configuration</span> menu
720 </p>
721 </li>
722 <li>
723 <p>Upgrade to 0.4.65: some menu items have been moved</p>
724 </li>
725 <li>
726 <p>Upgrade to 0.7.3: many key bindings have changed</p>
727 </li>
728 <li>
729 <p>Upgrade to 2.2.3 or former on Windows: all configuration files such as mailboxes or bsfilter files are removed when performing
730 the upgrade and/or uninstallation, so please be careful and backup your data
731 </p>
732 </li>
733 </ul>
734 </div>
735 <p>You should always read the <code class="filename">NEWS</code> document (and also <code class="filename">NEWS-<em class="replaceable"><code>x</code></em>.0</code> if you are upgrading from a very old version) that is included in the release tarballs. The NEWS can also be viewed on the
736 <a href="http://sylpheed.sraoss.jp/en/news.html" target="_top">appropriate Sylpheed website page</a>.
737 </p>
738 </td>
739 </tr>
740 <tr class="question">
741 <td align="left" valign="top"><a name="d0e530"></a><a name="faq-update-views-sylpheed"></a><b>1.26.</b></td>
742 <td align="left" valign="top">
743 <p>How can I quickly update the views in Sylpheed?
744
745 </p>
746 </td>
747 </tr>
748 <tr class="answer">
749 <td align="left" valign="top"><b></b></td>
750 <td align="left" valign="top">
751 <p>
752 Just press <span><strong class="keycap">Alt</strong></span>-<span><strong class="keycap">U</strong></span> or select <span class="guimenuitem">Update summary</span> from the <span class="guimenu">View</span> menu.
753
754 </p>
755 </td>
756 </tr>
757 <tr class="question">
758 <td align="left" valign="top"><a name="d0e549"></a><a name="faq-gvim-external-editor-sylpheed"></a><b>1.27.</b></td>
759 <td align="left" valign="top">
760 <p>Why can't I use gvim as external editor?
761
762 </p>
763 </td>
764 </tr>
765 <tr class="answer">
766 <td align="left" valign="top"><b></b></td>
767 <td align="left" valign="top">
768 <p>
769 If one wishes to use gvim as an external editor it's
770 necessary to start it with the no-fork option <em class="parameter"><code>-f</code></em>, i.e.
771 in the configuration dialog box you need to enter
772 <span><strong class="command">gvim -f %s</strong></span>. If not the editor forks and open up a
773 separate file and when one quits the editor the changes
774 are lost and don't show up in the composer window.
775 (Thanks, Ed Collins!)
776
777 </p>
778 </td>
779 </tr>
780 <tr class="question">
781 <td align="left" valign="top"><a name="d0e562"></a><a name="faq-quote-messages-sylpheed"></a><b>1.28.</b></td>
782 <td align="left" valign="top">
783 <p>Can I quote just parts of the original message when replying?
784
785 </p>
786 </td>
787 </tr>
788 <tr class="answer">
789 <td align="left" valign="top"><b></b></td>
790 <td align="left" valign="top">
791 <p>
792 Yes, select the part in the text view and choose <span class="guiicon">Reply</span>.
793
794 </p>
795 </td>
796 </tr>
797 <tr class="question">
798 <td align="left" valign="top"><a name="d0e572"></a><a name="faq-not-quoting-sylpheed"></a><b>1.29.</b></td>
799 <td align="left" valign="top">
800 <p>Can I reply without quoting at all?
801
802 </p>
803 </td>
804 </tr>
805 <tr class="answer">
806 <td align="left" valign="top"><b></b></td>
807 <td align="left" valign="top">
808 <p>You need to disable quoting by editing the reply format under <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Common preferences</span>-&gt;<span class="guimenuitem">Compose tab</span>-&gt;<span class="guimenuitem">Format tab</span>
809 (also works with
810 forward format which you can see below the reply format in the configuration dialog).
811 </p>
812 </td>
813 </tr>
814 <tr class="question">
815 <td align="left" valign="top"><a name="d0e589"></a><a name="d0e590"></a><b>1.30.</b></td>
816 <td align="left" valign="top">
817 <p> Does Sylpheed provide an anti-spam feature? </p>
818 </td>
819 </tr>
820 <tr class="answer">
821 <td align="left" valign="top"><b></b></td>
822 <td align="left" valign="top">
823 <p>Yes. It has a <a href="http://www.bogofilter.org/" target="_top">bogofilter</a> and a <a href="http://bsfilter.org/index-e.html" target="_top">bsfilter</a> support. Just go to <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Common preferences...</span>-&gt;<span class="guimenuitem">Junk mail</span> and check <span class="guilabel">Enable Junk mail control</span>. Then you can select a <span class="guilabel">Learning command</span> preset of your choice, or possibly use custom commands.
824 </p>
825 <p>You can also use other spam filters thanks to the Actions functionality (available under <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Actions...</span>).
826 </p>
827 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
828 <h3 class="title">Note</h3>
829 <p>You need to have bogofilter, bsfilter, or other spam filter properly installed on your system prior to the junk mail configuration
830 in Sylpheed, unless you use Sylpheed for Windows, which comes with bsfilter included in the installation program (since version
831 2.7.0).
832 </p>
833 </div>
834 </td>
835 </tr>
836 <tr class="question">
837 <td align="left" valign="top"><a name="d0e627"></a><a name="d0e628"></a><b>1.31.</b></td>
838 <td align="left" valign="top">
839 <p>Are there any plug-ins extending standard Sylpheed functionality?</p>
840 </td>
841 </tr>
842 <tr class="answer">
843 <td align="left" valign="top"><b></b></td>
844 <td align="left" valign="top">
845 <p>As of Sylpheed 3.1, there is an Attachment Tool Plug-in distributed with the Sylpheed source code and available under <code class="filename">plugin/attachment_tool/</code>. Its only function is to remove attachments from
846 selected messages and is provided more or less as a technology preview. More plug-ins are planned since Sylpheed 3.0, released
847 in early 2010, and later supports a plug-in interface. In the future, some of the Sylpheed features will be re-implemented
848 as plug-ins, and, moreover, various other plug-ins will be released.
849 </p>
850 <p>There is a page on the Sylpheed website dedicated to the <a href="http://sylpheed.sraoss.jp/en/plugin.html" target="_top">plug-in interface</a>. Additionally, the <code class="filename">PLUGIN.txt</code> file distributed directly with Sylpheed can provide you with some basic information on the topic.
851 </p>
852 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
853 <h3 class="title">Note</h3>
854 <p>If you are a developer interested in creating plug-ins for Sylpheed, see the <a href="http://sylpheed.sraoss.jp/wiki/index.php?PluginSpec" target="_top">plug-in specification</a> on the Sylpheed wiki.
855 </p>
856 </div>
857 </td>
858 </tr>
859 <tr class="question">
860 <td align="left" valign="top"><a name="d0e651"></a><a name="faq-faq-sylpheed"></a><b>1.32.</b></td>
861 <td align="left" valign="top">
862 <p>Where I can find the latest Sylpheed FAQ and manual?
863
864 </p>
865 </td>
866 </tr>
867 <tr class="answer">
868 <td align="left" valign="top"><b></b></td>
869 <td align="left" valign="top">
870 <p>
871 Go to <a href="http://sylpheeddoc.sourceforge.net/" target="_top">http://sylpheeddoc.sourceforge.net</a> and check out
872 the FAQ and manual from the Sylpheed Documentation Project (sylpheeddoc). Both
873 documents are available in multiple languages there and
874 usually contain the latest updates. The direct links are as follows:
875 </p>
876 <div class="itemizedlist">
877 <ul type="disc">
878 <li>
879 <p><a href="http://sylpheeddoc.sourceforge.net/en/faq/sylpheed-faq.html" target="_top">current version of the English FAQ</a></p>
880 </li>
881 <li>
882 <p><a href="http://sylpheeddoc.sourceforge.net/en/manual/sylpheed.html" target="_top">current version of the English manual</a></p>
883 </li>
884 </ul>
885 </div>
886 <p>Also see the question about available language versions at the top of this section. </p>
887 </td>
888 </tr>
889 <tr class="question">
890 <td align="left" valign="top"><a name="d0e672"></a><a name="d0e673"></a><b>1.33.</b></td>
891 <td align="left" valign="top">
892 <p>Where I can obtain source files for this document?</p>
893 </td>
894 </tr>
895 <tr class="answer">
896 <td align="left" valign="top"><b></b></td>
897 <td align="left" valign="top">
898 <p>The source DocBook XML files in which this document is written can be obtained from a <a href="http://sylpheeddoc.cvs.sourceforge.net/sylpheeddoc/" target="_top">public CVS repository</a> that is part of the <a href="http://sylpheeddoc.sourceforge.net/" target="_top">Sylpheed Documentation Project</a>. The source files with all the necessary build system, XSL stylesheets or snapshots are stored under the "<a href="http://sylpheeddoc.cvs.sourceforge.net/viewvc/sylpheeddoc/doc/" target="_top">doc</a>" module in the CVS repository and can be checked out through anonymous CVS with the following commands (simply press Enter
899 when prompted for a password):
900 </p>
901 <p><span><strong class="command">cvs -d:pserver:anonymous@sylpheeddoc.cvs.sourceforge.net:/cvsroot/sylpheeddoc login</strong></span></p>
902 <p><span><strong class="command">cvs -z3 -d:pserver:anonymous@sylpheeddoc.cvs.sourceforge.net:/cvsroot/sylpheeddoc co -P doc</strong></span></p>
903 <p>The source files are also included in .tar.gz and .zip archives made available with each documentation release, these can
904 be downloaded from the <a href="http://sourceforge.net/projects/sylpheeddoc/files/" target="_top">appropriate project page</a>. For more information on the used project infrastructure, please see the <a href="http://sylpheeddoc.sourceforge.net/en/tools.html" target="_top">project website</a>.
905 </p>
906 </td>
907 </tr>
908 <tr class="question">
909 <td align="left" valign="top"><a name="d0e702"></a><a name="d0e703"></a><b>1.34.</b></td>
910 <td align="left" valign="top">
911 <p>I have found an error and/or outdated information in this document!</p>
912 </td>
913 </tr>
914 <tr class="answer">
915 <td align="left" valign="top"><b></b></td>
916 <td align="left" valign="top">
917 <p>Please report any errors, misleading and/or outdated information to the <a href="http://sylpheeddoc.sourceforge.net/" target="_top">Sylpheed Documentation Project</a>. You can see the list of Project members in the following question, so you can also contact them directly.
918 </p>
919 </td>
920 </tr>
921 <tr class="question">
922 <td align="left" valign="top"><a name="d0e712"></a><a name="d0e713"></a><b>1.35.</b></td>
923 <td align="left" valign="top">
924 <p>Who are the members of the Sylpheed Documentation Project?</p>
925 </td>
926 </tr>
927 <tr class="answer">
928 <td align="left" valign="top"><b></b></td>
929 <td align="left" valign="top">
930 <p>The current members of the Sylpheed Documentation Project are:</p><pre class="programlisting">Francois Barriere fbarriere at users.sourceforge.net
931Petr Kovar pknbe at users.sourceforge.net</pre><p>Below is the list of former members of the Sylpheed Documentation Project. Big thank you goes to all of them!</p><pre class="programlisting">Martin Bretschneider furbour at users.sourceforge.net
932Olivier Delhomme dup at users.sourceforge.net
933Doruk Fisek dobidik at users.sourceforge.net
934Melvin Hadasht mhadasht at users.sourceforge.net
935Nicolas Kaiser nikai at users.sourceforge.net
936Paul Kater pkater at users.sourceforge.net
937Ricardo Mones Lastra mones at users.sourceforge.net
938Jens Oberender jobi at users.sourceforge.net
939Marcelo Ramos hackpando at users.sourceforge.net
940Guido Rudolphi malatesta at users.sourceforge.net
941Frank Weng fweng at users.sourceforge.net</pre></td>
942 </tr>
943 </tbody>
944 </table>
945 </div>
946 </div>
947 <div class="navfooter">
948 <hr>
949 <table width="100%" summary="Navigation footer">
950 <tr>
951 <td width="40%" align="left"><a accesskey="p" href="sylpheed-faq.html">Prev</a>&nbsp;
952 </td>
953 <td width="20%" align="center">&nbsp;</td>
954 <td width="40%" align="right">&nbsp;<a accesskey="n" href="sylpheed-faq-2.html">Next</a></td>
955 </tr>
956 <tr>
957 <td width="40%" align="left" valign="top">Sylpheed FAQ&nbsp;</td>
958 <td width="20%" align="center"><a accesskey="h" href="sylpheed-faq.html">Home</a></td>
959 <td width="40%" align="right" valign="top">&nbsp;Chapter&nbsp;2.&nbsp;Sylpheed FAQ - Installation and Configuration</td>
960 </tr>
961 </table>
962 </div>
963 </body>
964</html> \ No newline at end of file
diff --git a/faq/en/sylpheed-faq-2.html b/faq/en/sylpheed-faq-2.html
new file mode 100644
index 0000000..5e0d3ae
--- /dev/null
+++ b/faq/en/sylpheed-faq-2.html
@@ -0,0 +1,913 @@
1<html>
2 <head>
3 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4
5 <title>Chapter&nbsp;2.&nbsp;Sylpheed FAQ - Installation and Configuration</title>
6 <meta name="generator" content="DocBook XSL Stylesheets V1.68.1">
7 <link rel="start" href="sylpheed-faq.html" title="Sylpheed FAQ">
8 <link rel="up" href="sylpheed-faq.html" title="Sylpheed FAQ">
9 <link rel="prev" href="sylpheed-faq-1.html" title="Chapter&nbsp;1.&nbsp;Sylpheed FAQ - General Information">
10 <link rel="next" href="sylpheed-faq-3.html" title="Chapter&nbsp;3.&nbsp;Sylpheed FAQ - Interface">
11 <link rel="chapter" href="sylpheed-faq-1.html" title="Chapter&nbsp;1.&nbsp;Sylpheed FAQ - General Information">
12 <link rel="chapter" href="sylpheed-faq-2.html" title="Chapter&nbsp;2.&nbsp;Sylpheed FAQ - Installation and Configuration">
13 <link rel="chapter" href="sylpheed-faq-3.html" title="Chapter&nbsp;3.&nbsp;Sylpheed FAQ - Interface">
14 <link rel="appendix" href="sylpheed-faq-4.html" title="Appendix&nbsp;A.&nbsp;GNU Free Documentation License"><style type="text/css">
15pre.programlisting, pre.screen {
16background-color : #e0e0e0;
17padding : 0.2cm;
18}
19.question {
20font-weight : bold;
21}
22
23</style></head>
24 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
25 <div class="navheader">
26 <table width="100%" summary="Navigation header">
27 <tr>
28 <th colspan="3" align="center">Chapter&nbsp;2.&nbsp;Sylpheed FAQ - Installation and Configuration</th>
29 </tr>
30 <tr>
31 <td width="20%" align="left"><a accesskey="p" href="sylpheed-faq-1.html">Prev</a>&nbsp;
32 </td>
33 <th width="60%" align="center">&nbsp;</th>
34 <td width="20%" align="right">&nbsp;<a accesskey="n" href="sylpheed-faq-3.html">Next</a></td>
35 </tr>
36 </table>
37 <hr>
38 </div>
39 <div class="chapter" lang="en">
40 <div class="titlepage">
41 <div>
42 <div>
43 <h2 class="title"><a name="sylpheed-faq-2"></a>Chapter&nbsp;2.&nbsp;Sylpheed FAQ - Installation and Configuration
44 </h2>
45 </div>
46 </div>
47 </div>
48 <div class="qandaset">
49 <dl>
50 <dt>2.1. <a href="sylpheed-faq-2.html#d0e730">What does it take to compile Sylpheed?</a></dt>
51 <dt>2.2. <a href="sylpheed-faq-2.html#d0e780">How do I set up Sylpheed?</a></dt>
52 <dt>2.3. <a href="sylpheed-faq-2.html#d0e813">Why did the creation of the mailbox fail?</a></dt>
53 <dt>2.4. <a href="sylpheed-faq-2.html#d0e826">How do I set up an account?</a></dt>
54 <dt>2.5. <a href="sylpheed-faq-2.html#d0e853">How many accounts can I set up in Sylpheed?</a></dt>
55 <dt>2.6. <a href="sylpheed-faq-2.html#d0e860">Can I set up an account for sending mail only?</a></dt>
56 <dt>2.7. <a href="sylpheed-faq-2.html#d0e875">Why does Sylpheed not delete my mails when I press "Delete"? I set a filter, and Sylpheed does not filter. I moved a mail
57 to a different mailbox and it did not move.</a></dt>
58 <dt>2.8. <a href="sylpheed-faq-2.html#d0e896">Can I set up special addresses/ports for my mailserver/newsserver?</a></dt>
59 <dt>2.9. <a href="sylpheed-faq-2.html#d0e911">Does Sylpheed have options for threading messages?</a></dt>
60 <dt>2.10. <a href="sylpheed-faq-2.html#d0e930">Can I create multiple levels of subfolders to store mail?</a></dt>
61 <dt>2.11. <a href="sylpheed-faq-2.html#d0e937">Why isn't Sylpheed sending my mail out?</a></dt>
62 <dt>2.12. <a href="sylpheed-faq-2.html#d0e944">How do I apply a patch after downloading it?</a></dt>
63 <dt>2.13. <a href="sylpheed-faq-2.html#d0e978">How do I compile in support for compface pictures?</a></dt>
64 <dt>2.14. <a href="sylpheed-faq-2.html#d0e988">How do I make my own compface image?</a></dt>
65 <dt>2.15. <a href="sylpheed-faq-2.html#d0e998">How can I tell my browser/newsclient/other program to use Sylpheed as email program?</a></dt>
66 <dt>2.16. <a href="sylpheed-faq-2.html#d0e1020">How do I enable GPG support in Sylpheed?</a></dt>
67 <dt>2.17. <a href="sylpheed-faq-2.html#d0e1039">Mutt does not recognize Sylpheed's MH structure</a></dt>
68 <dt>2.18. <a href="sylpheed-faq-2.html#d0e1055">Viewing a GIF file within Sylpheed causes a segmentation fault.</a></dt>
69 <dt>2.19. <a href="sylpheed-faq-2.html#d0e1067">How Sylpheed checks for new mail?</a></dt>
70 <dt>2.20. <a href="sylpheed-faq-2.html#d0e1150">How can I make Sylpheed notify me when new mail arrives?</a></dt>
71 <dt>2.21. <a href="sylpheed-faq-2.html#d0e1160">Can I use a spell checker with Sylpheed?</a></dt>
72 <dt>2.22. <a href="sylpheed-faq-2.html#d0e1178">How can I make Sylpheed send my compface image in the mails?</a></dt>
73 <dt>2.23. <a href="sylpheed-faq-2.html#d0e1199">How can I get the newest source code from the Sylpheed Subversion (SVN) repository?</a></dt>
74 <dt>2.24. <a href="sylpheed-faq-2.html#d0e1238">I checked out the sources using SVN and can't find any configure script.</a></dt>
75 <dt>2.25. <a href="sylpheed-faq-2.html#d0e1253">Running "autogen.sh" gives error messages that "AM_PATH_GDK_PIXBUF" or
76 "AM_PATH_(whatever)" is not found.</a></dt>
77 <dt>2.26. <a href="sylpheed-faq-2.html#d0e1300">I don't want to compile in support for (...) any longer, but after running
78 "configure", those libraries are still used.</a></dt>
79 <dt>2.27. <a href="sylpheed-faq-2.html#d0e1316">How can I select different applications to open with specific MIME types?</a></dt>
80 <dt>2.28. <a href="sylpheed-faq-2.html#d0e1326">How can I change the suggested mimetype for attachments?</a></dt>
81 <dt>2.29. <a href="sylpheed-faq-2.html#d0e1335">The folder list is not updated after I manually moved/copied folders.</a></dt>
82 <dt>2.30. <a href="sylpheed-faq-2.html#d0e1345">How can I revert original settings, e.g. for fonts, key bindings, etc.?</a></dt>
83 <dt>2.31. <a href="sylpheed-faq-2.html#d0e1367">What environment variables have effect on Sylpheed?</a></dt>
84 <dt>2.32. <a href="sylpheed-faq-2.html#d0e1408">Special characters (e.g. umlauts) are not displayed correctly.</a></dt>
85 <dt>2.33. <a href="sylpheed-faq-2.html#d0e1432">How can I convert my old mailbox/address book from (some mail client).</a></dt>
86 <dt>2.34. <a href="sylpheed-faq-2.html#d0e1448">What config files are there, and what are they used for?</a></dt>
87 <dt>2.35. <a href="sylpheed-faq-2.html#d0e1507">How do I change the location of user profile directory under Windows?</a></dt>
88 <dt>2.36. <a href="sylpheed-faq-2.html#d0e1581">Can I run multiple instances of Sylpheed?</a></dt>
89 <dt>2.37. <a href="sylpheed-faq-2.html#d0e1616">What to do when printing an email prints off the paper?</a></dt>
90 </dl>
91 <table border="0" summary="Q and A Set" cellspacing="13px">
92 <col align="left" width="1%">
93 <tbody>
94 <tr class="question">
95 <td align="left" valign="top"><a name="d0e730"></a><a name="d0e731"></a><b>2.1.</b></td>
96 <td align="left" valign="top">
97 <p>What does it take to compile Sylpheed?</p>
98 </td>
99 </tr>
100 <tr class="answer">
101 <td align="left" valign="top"><b></b></td>
102 <td align="left" valign="top">
103 <p>Any POSIX compliant UNIX or similar OS, e.g. Linux,
104 FreeBSD, Solaris.
105 GTK+ 2.4.0 or later (GTK+ 2.6.0 or later
106 is recommended).
107 A recent ANSI C compiler (gcc 2.7.2.3 should also
108 work).
109 </p>
110 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
111 <h3 class="title">Note</h3>
112 <p>It is reported that Sun C will not compile
113 Sylpheed.
114 </p>
115 </div>
116 <p>Optionally:</p>
117 <div class="itemizedlist">
118 <ul type="disc">
119 <li>
120 <p>compface (for X-Face)</p>
121 </li>
122 <li>
123 <p>GPGME (for GnuPG)</p>
124 </li>
125 <li>
126 <p>OpenSSL for SSL support</p>
127 </li>
128 <li>
129 <p>GtkSpell for a spell checking feature</p>
130 </li>
131 <li>
132 <p>cURL for allowing Sylpheed to check for updates</p>
133 </li>
134 <li>
135 <p>JPilot</p>
136 </li>
137 <li>
138 <p>LDAP</p>
139 </li>
140 <li>
141 <p>the equivalent of GTK+-devel and Xfree86-devel</p>
142 </li>
143 <li>
144 <p>you may also require flex (lex) and bison
145 (yacc).
146 </p>
147 </li>
148 </ul>
149 </div>
150 <p>Otherwise ./configure will fail.
151 See also the <code class="filename">INSTALL</code> file that is being distributed with the Sylpheed tarball.
152 </p>
153 <p>Note that as Sylpheed now supports the Windows platform, you can also compile it using <a href="http://www.mingw.org/" target="_top">MinGW</a>.
154 </p>
155 </td>
156 </tr>
157 <tr class="question">
158 <td align="left" valign="top"><a name="d0e780"></a><a name="d0e781"></a><b>2.2.</b></td>
159 <td align="left" valign="top">
160 <p>How do I set up Sylpheed?</p>
161 </td>
162 </tr>
163 <tr class="answer">
164 <td align="left" valign="top"><b></b></td>
165 <td align="left" valign="top">
166 <p>When you run Sylpheed for the first time, it will
167 ask you where you want to store your mailboxes. The
168 default is <code class="filename">$HOME/Mail</code> (or <code class="filename">%APPDATA%\Sylpheed\Mailboxes\Mail</code> under Windows). You can change this to
169 anything you like as long as it is a valid directory
170 name.
171 </p>
172 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
173 <h3 class="title">Note</h3>
174 <p>When Sylpheed is executed for the first time, it automatically creates the configuration files under <code class="filename">$HOME/.sylpheed-2.0/</code> (or <code class="filename">%APPDATA%\Sylpheed\</code> under Windows), and asks you the location of mailbox. As stated above, the default is <code class="filename">$HOME/Mail</code>, or <code class="filename">%APPDATA%\Sylpheed\Mailboxes\Mail</code> under Windows. If some files, which are non-MH format, already exist on the directory, you will have to specify another location.
175 </p>
176 </div>
177 <p>Furthermore, you need to <a href="sylpheed-faq-2.html#faq-account-setup">create at least one account</a> to be able to receive or send messages.
178 </p>
179 </td>
180 </tr>
181 <tr class="question">
182 <td align="left" valign="top"><a name="d0e813"></a><a name="d0e814"></a><b>2.3.</b></td>
183 <td align="left" valign="top">
184 <p>Why did the creation of the mailbox fail?</p>
185 </td>
186 </tr>
187 <tr class="answer">
188 <td align="left" valign="top"><b></b></td>
189 <td align="left" valign="top">
190 <p>Sylpheed reports such an error if it can't create the default
191 mailboxes (inbox, outbox, etc.). This can be because <code class="filename">$HOME/Mail</code>
192 (or <code class="filename">%APPDATA%\Sylpheed\Mailboxes\Mail</code> under Windows) already contains files with the same names. This occurs when switching from
193 Kmail to Sylpheed, in this case backup and remove the existing Mail
194 directory or use another name for the Sylpheed mail directory.
195 </p>
196 </td>
197 </tr>
198 <tr class="question">
199 <td align="left" valign="top"><a name="d0e826"></a><a name="faq-account-setup"></a><b>2.4.</b></td>
200 <td align="left" valign="top">
201 <p>How do I set up an account?</p>
202 </td>
203 </tr>
204 <tr class="answer">
205 <td align="left" valign="top"><b></b></td>
206 <td align="left" valign="top">
207 <p>After loading Sylpheed for the first time, you can
208 add an email account by clicking the <span class="guimenu">Configuration</span> menu. Select the option <span class="guimenuitem">Create new account</span> and let the configuration assistant help you with the initial setup.
209 In a few easy steps, the assistant allows you to conveniently configure your POP3, IMAP4, or Gmail account.
210 </p>
211 <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;">
212 <h3 class="title">Tip</h3>
213 <p>If you want later to change your account configuration, just select <span class="guimenuitem">Configuration</span>-&gt;<span class="guimenuitem">Preferences for current account...</span>, or <span class="guimenuitem">Configuration</span>-&gt;<span class="guimenuitem">Edit accounts...</span></p>
214 </div>
215 </td>
216 </tr>
217 <tr class="question">
218 <td align="left" valign="top"><a name="d0e853"></a><a name="d0e854"></a><b>2.5.</b></td>
219 <td align="left" valign="top">
220 <p>How many accounts can I set up in Sylpheed?</p>
221 </td>
222 </tr>
223 <tr class="answer">
224 <td align="left" valign="top"><b></b></td>
225 <td align="left" valign="top">
226 <p>The number is unlimited. The limit is reached when
227 your computer stops responding.
228 </p>
229 </td>
230 </tr>
231 <tr class="question">
232 <td align="left" valign="top"><a name="d0e860"></a><a name="d0e861"></a><b>2.6.</b></td>
233 <td align="left" valign="top">
234 <p>Can I set up an account for sending mail only?</p>
235 </td>
236 </tr>
237 <tr class="answer">
238 <td align="left" valign="top"><b></b></td>
239 <td align="left" valign="top">
240 <p>Yes, add a new account using <span class="guimenuitem">Configuration</span>-&gt;<span class="guimenuitem">Edit accounts...</span>+<span class="guibutton">Add</span> and set the Protocol to None (local).
241 </p>
242 </td>
243 </tr>
244 <tr class="question">
245 <td align="left" valign="top"><a name="d0e875"></a><a name="d0e876"></a><b>2.7.</b></td>
246 <td align="left" valign="top">
247 <p>Why does Sylpheed not delete my mails when I press "Delete"? I set a filter, and Sylpheed does not filter. I moved a mail
248 to a different mailbox and it did not move.
249 </p>
250 </td>
251 </tr>
252 <tr class="answer">
253 <td align="left" valign="top"><b></b></td>
254 <td align="left" valign="top">
255 <p>You have to click the <span class="guiicon">Execute</span> button.
256 The other solution: in the configuration settings
257 (<span class="guimenuitem">Common preferences...</span>-&gt;<span class="guimenuitem">Details</span>-&gt;<span class="guimenuitem">Interface</span>), you have to
258 check the <span class="guilabel">Execute immediately when moving or deleting messages</span> box.
259 </p>
260 </td>
261 </tr>
262 <tr class="question">
263 <td align="left" valign="top"><a name="d0e896"></a><a name="d0e897"></a><b>2.8.</b></td>
264 <td align="left" valign="top">
265 <p>Can I set up special addresses/ports for my mailserver/newsserver?</p>
266 </td>
267 </tr>
268 <tr class="answer">
269 <td align="left" valign="top"><b></b></td>
270 <td align="left" valign="top">
271 <p>Yes, you can. Under <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Preferences for current account...</span>-&gt;<span class="guimenuitem">Advanced</span>, you
272 can specify the exact port addresses you want to use.
273 </p>
274 </td>
275 </tr>
276 <tr class="question">
277 <td align="left" valign="top"><a name="d0e911"></a><a name="d0e912"></a><b>2.9.</b></td>
278 <td align="left" valign="top">
279 <p>Does Sylpheed have options for threading messages?</p>
280 </td>
281 </tr>
282 <tr class="answer">
283 <td align="left" valign="top"><b></b></td>
284 <td align="left" valign="top">
285 <p>Yes. You can switch it on and off in the <span class="guimenu">View</span>
286 menu, just select <span class="guimenuitem">Thread view</span> or press <span><strong class="keycap">Ctrl</strong></span>-<span><strong class="keycap">T</strong></span>.
287 </p>
288 </td>
289 </tr>
290 <tr class="question">
291 <td align="left" valign="top"><a name="d0e930"></a><a name="d0e931"></a><b>2.10.</b></td>
292 <td align="left" valign="top">
293 <p>Can I create multiple levels of subfolders to store mail?</p>
294 </td>
295 </tr>
296 <tr class="answer">
297 <td align="left" valign="top"><b></b></td>
298 <td align="left" valign="top">
299 <p>Absolutely. This is no problem.</p>
300 </td>
301 </tr>
302 <tr class="question">
303 <td align="left" valign="top"><a name="d0e937"></a><a name="d0e938"></a><b>2.11.</b></td>
304 <td align="left" valign="top">
305 <p>Why isn't Sylpheed sending my mail out?</p>
306 </td>
307 </tr>
308 <tr class="answer">
309 <td align="left" valign="top"><b></b></td>
310 <td align="left" valign="top">
311 <p>You need to create at least one account in order to
312 send. (This is a wonderful gotcha on LAN installs
313 with only a local mailbox feed).
314 </p>
315 </td>
316 </tr>
317 <tr class="question">
318 <td align="left" valign="top"><a name="d0e944"></a><a name="d0e945"></a><b>2.12.</b></td>
319 <td align="left" valign="top">
320 <p>How do I apply a patch after downloading it?</p>
321 </td>
322 </tr>
323 <tr class="answer">
324 <td align="left" valign="top"><b></b></td>
325 <td align="left" valign="top">
326 <p>Copy patch to sylpheed directory.
327 Apply the patch as follows:
328 </p>
329 <p>
330 <span><strong class="command">% patch -p0 &lt; some.patch</strong></span></p>
331 <p>
332 Or, if it's gzipped:
333 </p>
334 <p>
335 <span><strong class="command">% gzip -dc some.patch.gz | patch -p0</strong></span></p>
336 <p>
337 Run <code class="filename">./autogen.sh</code>, remove the generated <code class="filename">/config.cache</code>
338 file (unless you want to install in prefix
339 <code class="filename">/usr/local</code>).
340 Run <code class="filename">./configure</code> with the appropriate options and
341 then <code class="filename">make</code>.
342 (Text as found on the former Sylpheed patches page.)
343 </p>
344 </td>
345 </tr>
346 <tr class="question">
347 <td align="left" valign="top"><a name="d0e978"></a><a name="d0e979"></a><b>2.13.</b></td>
348 <td align="left" valign="top">
349 <p>How do I compile in support for compface pictures?</p>
350 </td>
351 </tr>
352 <tr class="answer">
353 <td align="left" valign="top"><b></b></td>
354 <td align="left" valign="top">
355 <p>You have to have a package called <code class="computeroutput">libcompface</code>
356 installed, so this is available for compiling into
357 Sylpheed. Note that the exact name of the package depends on OS or distribution you use.
358 </p>
359 </td>
360 </tr>
361 <tr class="question">
362 <td align="left" valign="top"><a name="d0e988"></a><a name="d0e989"></a><b>2.14.</b></td>
363 <td align="left" valign="top">
364 <p>How do I make my own compface image?</p>
365 </td>
366 </tr>
367 <tr class="answer">
368 <td align="left" valign="top"><b></b></td>
369 <td align="left" valign="top">
370 <p>The faces package contains a program called xbm2ikon script,
371 which converts a 48x48 xbm to the format suitable for
372 compface. Thanks to Jeff Dairiki, you can have a complete online course in this. Visit <a href="http://www.dairiki.org/xface/" target="_top">this page</a> for the details.
373 </p>
374 </td>
375 </tr>
376 <tr class="question">
377 <td align="left" valign="top"><a name="d0e998"></a><a name="d0e999"></a><b>2.15.</b></td>
378 <td align="left" valign="top">
379 <p>How can I tell my browser/newsclient/other program to use Sylpheed as email program?</p>
380 </td>
381 </tr>
382 <tr class="answer">
383 <td align="left" valign="top"><b></b></td>
384 <td align="left" valign="top">
385 <p> In the settings part of the program, write
386 <span><strong class="command">sylpheed --compose</strong></span></p>
387 <p>
388 Specific options for typical browsers:
389 </p>
390 <div class="itemizedlist">
391 <ul type="disc">
392 <li>
393 <p>Opera: <span><strong class="command">sylpheed --compose [mailto:%t][?subject=%s] </strong></span></p>
394 </li>
395 <li>
396 <p>Galeon: <span><strong class="command">sylpheed --compose "mailto:%t?subject=%s"</strong></span></p>
397 </li>
398 </ul>
399 </div>
400 </td>
401 </tr>
402 <tr class="question">
403 <td align="left" valign="top"><a name="d0e1020"></a><a name="d0e1021"></a><b>2.16.</b></td>
404 <td align="left" valign="top">
405 <p>How do I enable GPG support in Sylpheed?</p>
406 </td>
407 </tr>
408 <tr class="answer">
409 <td align="left" valign="top"><b></b></td>
410 <td align="left" valign="top">
411 <p> When compiling Sylpheed, make sure you add <em class="parameter"><code>--enable-gpgme</code></em> in the <span><strong class="command">./configure</strong></span> command.
412 When that completes successfully, there is a <span class="guimenuitem">Privacy</span> section in the <span class="guimenuitem">Common Preferences</span>.
413 </p>
414 </td>
415 </tr>
416 <tr class="question">
417 <td align="left" valign="top"><a name="d0e1039"></a><a name="d0e1040"></a><b>2.17.</b></td>
418 <td align="left" valign="top">
419 <p>Mutt does not recognize Sylpheed's MH structure</p>
420 </td>
421 </tr>
422 <tr class="answer">
423 <td align="left" valign="top"><b></b></td>
424 <td align="left" valign="top">
425 <p>For this to work you need to use the <span><strong class="command">touch</strong></span> command in every MH folder. "<span><strong class="command">touch</strong></span>" the file <code class="filename">.xmhcache</code> and Mutt should do just fine.
426 </p>
427 </td>
428 </tr>
429 <tr class="question">
430 <td align="left" valign="top"><a name="d0e1055"></a><a name="d0e1056"></a><b>2.18.</b></td>
431 <td align="left" valign="top">
432 <p>Viewing a GIF file within Sylpheed causes a segmentation fault.</p>
433 </td>
434 </tr>
435 <tr class="answer">
436 <td align="left" valign="top"><b></b></td>
437 <td align="left" valign="top">
438 <p>In case this happens, you can easily fix that by adding the following to <code class="filename">/etc/mime.types</code>:
439 </p><pre class="programlisting">image/gif gif</pre></td>
440 </tr>
441 <tr class="question">
442 <td align="left" valign="top"><a name="d0e1067"></a><a name="d0e1068"></a><b>2.19.</b></td>
443 <td align="left" valign="top">
444 <p>How Sylpheed checks for new mail?</p>
445 </td>
446 </tr>
447 <tr class="answer">
448 <td align="left" valign="top"><b></b></td>
449 <td align="left" valign="top">
450 <p>New mail can be retrieved either manually or automatically.</p>
451 <p>To check for new mail the manual way, you can:</p>
452 <div class="orderedlist">
453 <ol type="1">
454 <li>
455 <p>Either press the <span class="guibutton">Get </span>button on the toolbar to incorporate new mail for the current account only, or use the <span class="guibutton">Get all</span> button to incorporate new mail for all configured accounts.
456 </p>
457 </li>
458 <li>
459 <p>Or choose <span class="guimenu">File</span>-&gt;<span class="guimenuitem">Mailbox</span>-&gt;<span class="guimenuitem">Check for new messages</span>, or <span class="guimenuitem">Check for new messages in all mailboxes</span>.
460 </p>
461 </li>
462 <li>
463 <p>Or select <span class="guimenu">Message</span>-&gt;<span class="guimenuitem">Receive</span>-&gt;<span class="guimenuitem">Get from current account</span>, or <span class="guimenuitem">Get from all accounts</span>.
464 </p>
465 </li>
466 </ol>
467 </div>
468 <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;">
469 <h3 class="title">Tip</h3>
470 <p>If you have a POP3 account and don't want to retrieve all the new messages stored on remote server to your computer, you
471 can manage your account remotely (e.g. open or delete individual messages) by choosing <span class="guimenu">Message</span>-&gt;<span class="guimenuitem">Receive</span>-&gt;<span class="guimenuitem">Remote mailbox...</span></p>
472 </div>
473 <p>If you prefer autochecking for new mail instead, first of all, make sure that you have checked <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Common preferences...</span>-&gt;<span class="guimenuitem">Receive</span>+<span class="guilabel">Autocheck new mail every <em class="replaceable"><code>10</code></em> minute(s)</span>. Optionally, you can adjust the interval value (in minutes) as well.
474 </p>
475 <p>Also check your settings under <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Edit accounts...</span> You will find this
476 at the top: <span class="guilabel">Check the boxes on the 'G' column to enable message retrieval by 'Get all'</span>. The setting applies on both manual and automatic
477 mail checks.
478 </p>
479 </td>
480 </tr>
481 <tr class="question">
482 <td align="left" valign="top"><a name="d0e1150"></a><a name="d0e1151"></a><b>2.20.</b></td>
483 <td align="left" valign="top">
484 <p>How can I make Sylpheed notify me when new mail arrives?</p>
485 </td>
486 </tr>
487 <tr class="answer">
488 <td align="left" valign="top"><b></b></td>
489 <td align="left" valign="top">
490 <p>Download Gkrellm or a similar program that is able to notify you of new incoming mail. Gkrellm is available at <a href="http://www.gkrellm.net" target="_top">the Gkrellm page</a>.
491 </p>
492 </td>
493 </tr>
494 <tr class="question">
495 <td align="left" valign="top"><a name="d0e1160"></a><a name="d0e1161"></a><b>2.21.</b></td>
496 <td align="left" valign="top">
497 <p>Can I use a spell checker with Sylpheed?</p>
498 </td>
499 </tr>
500 <tr class="answer">
501 <td align="left" valign="top"><b></b></td>
502 <td align="left" valign="top">
503 <p>Yes. You need to have GtkSpell installed prior to Sylpheed compilation. The support for GtkSpell is enabled by default in
504 <span><strong class="command">configure</strong></span>. (If you want to disable it, make sure you add <em class="parameter"><code>--disable-gtkspell</code></em> in the <span><strong class="command">./configure</strong></span> command.)
505 </p>
506 <p>The GtkSpell option is not supported in Sylpheed for Windows (yet), so you will have no spell checking under this OS.</p>
507 </td>
508 </tr>
509 <tr class="question">
510 <td align="left" valign="top"><a name="d0e1178"></a><a name="d0e1179"></a><b>2.22.</b></td>
511 <td align="left" valign="top">
512 <p>How can I make Sylpheed send my compface image in the mails?</p>
513 </td>
514 </tr>
515 <tr class="answer">
516 <td align="left" valign="top"><b></b></td>
517 <td align="left" valign="top">
518 <p>In the <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Preferences for current account...</span>-&gt;<span class="guimenuitem">Send</span> check <span class="guilabel">Add user-defined header</span> and press <span class="guibutton">Edit</span> button. A dialog appears, add a header named "X-Face" and fill the value field with your face data. Note that if you paste
519 the data from a terminal into the field, some spurious newlines can be added, and these can mangle your face, be careful.
520 </p>
521 </td>
522 </tr>
523 <tr class="question">
524 <td align="left" valign="top"><a name="d0e1199"></a><a name="d0e1200"></a><b>2.23.</b></td>
525 <td align="left" valign="top">
526 <p>How can I get the newest source code from the Sylpheed Subversion (SVN) repository?</p>
527 </td>
528 </tr>
529 <tr class="answer">
530 <td align="left" valign="top"><b></b></td>
531 <td align="left" valign="top">
532 <p>Move to an appropriate directory, and after you run the command specified below, a source tree named <code class="filename">trunk</code> will be created under that directory:
533 </p>
534 <p><span><strong class="command">svn checkout svn://sylpheed.sraoss.jp/sylpheed/trunk</strong></span></p>
535 <p>The subdirectories under the <code class="filename">sylpheed</code> directory are as follows:
536 </p>
537 <div class="itemizedlist">
538 <ul type="disc">
539 <li>
540 <p><code class="filename">trunk/</code> - main tree
541 </p>
542 </li>
543 <li>
544 <p><code class="filename">branches/</code> - miscellaneous experimental branches
545 </p>
546 </li>
547 <li>
548 <p><code class="filename">tags/</code> - release-tagged branches
549 </p>
550 </li>
551 </ul>
552 </div>
553 <p>To update to the newest source tree, run the following command in the target directory:</p>
554 <p><span><strong class="command">svn update</strong></span></p>
555 </td>
556 </tr>
557 <tr class="question">
558 <td align="left" valign="top"><a name="d0e1238"></a><a name="d0e1239"></a><b>2.24.</b></td>
559 <td align="left" valign="top">
560 <p>I checked out the sources using SVN and can't find any configure script.</p>
561 </td>
562 </tr>
563 <tr class="answer">
564 <td align="left" valign="top"><b></b></td>
565 <td align="left" valign="top">
566 <p>The SVN versions are meant to be used by developers rather than "normal"
567 users, so the source (or binary) distributions are easier to use.
568 </p>
569 <div class="blockquote">
570 <blockquote class="blockquote">
571 <p>Yeah, but the latest features from SVN really look sexy...</p>
572 </blockquote>
573 </div>
574 <p>You need to generate the configure script by running <code class="filename">autogen.sh</code>.
575 Be sure to have autoconf and automake packages installed for this.
576 </p>
577 </td>
578 </tr>
579 <tr class="question">
580 <td align="left" valign="top"><a name="d0e1253"></a><a name="d0e1254"></a><b>2.25.</b></td>
581 <td align="left" valign="top">
582 <p>Running "autogen.sh" gives error messages that "AM_PATH_GDK_PIXBUF" or
583 "AM_PATH_(whatever)" is not found.
584 </p>
585 </td>
586 </tr>
587 <tr class="answer">
588 <td align="left" valign="top"><b></b></td>
589 <td align="left" valign="top">
590 <p>There are some <code class="filename">*.m4</code> files in the <code class="filename">ac/missing</code> directory. Try to copy
591 them into the <code class="filename">ac</code> directory and run <code class="filename">autogen.sh</code> again.
592 </p>
593 <p>
594 If there are still some <code class="filename">.m4</code> files not found (e.g. those from GTK+), try
595 to run <span><strong class="command">% locate m4 | less</strong></span> or <span><strong class="command">% locate aclocal | less</strong></span> to find additional directories containing those macros. If you find e.g. a
596 <code class="filename">gtk.m4</code> in <code class="filename">/opt/gnome/share/aclocal</code>, change following line in
597 <code class="filename">autogen.sh</code> from
598 </p><pre class="programlisting">aclocal -I ac \</pre><p> to</p><pre class="programlisting">aclocal -I ac -I /opt/gnome/share/aclocal \</pre><p>and run it again.</p>
599 </td>
600 </tr>
601 <tr class="question">
602 <td align="left" valign="top"><a name="d0e1300"></a><a name="d0e1301"></a><b>2.26.</b></td>
603 <td align="left" valign="top">
604 <p>I don't want to compile in support for (...) any longer, but after running
605 "configure", those libraries are still used.
606 </p>
607 </td>
608 </tr>
609 <tr class="answer">
610 <td align="left" valign="top"><b></b></td>
611 <td align="left" valign="top">
612 <p>Remove the <code class="filename">config.cache</code> file and run <span><strong class="command">./configure</strong></span> again. You should
613 also use <span><strong class="command">make clean</strong></span> to avoid undefined references.
614 </p>
615 </td>
616 </tr>
617 <tr class="question">
618 <td align="left" valign="top"><a name="d0e1316"></a><a name="d0e1317"></a><b>2.27.</b></td>
619 <td align="left" valign="top">
620 <p>How can I select different applications to open with specific MIME types?</p>
621 </td>
622 </tr>
623 <tr class="answer">
624 <td align="left" valign="top"><b></b></td>
625 <td align="left" valign="top">
626 <p>The MIME-type to application associations are kept in <code class="filename">/etc/mailcap</code>.
627 </p>
628 </td>
629 </tr>
630 <tr class="question">
631 <td align="left" valign="top"><a name="d0e1326"></a><a name="d0e1327"></a><b>2.28.</b></td>
632 <td align="left" valign="top">
633 <p>How can I change the suggested mimetype for attachments?</p>
634 </td>
635 </tr>
636 <tr class="answer">
637 <td align="left" valign="top"><b></b></td>
638 <td align="left" valign="top">
639 <p>The extension to MIME-type associations are kept in <code class="filename">/etc/mime.types</code></p>
640 </td>
641 </tr>
642 <tr class="question">
643 <td align="left" valign="top"><a name="d0e1335"></a><a name="d0e1336"></a><b>2.29.</b></td>
644 <td align="left" valign="top">
645 <p>The folder list is not updated after I manually moved/copied folders.</p>
646 </td>
647 </tr>
648 <tr class="answer">
649 <td align="left" valign="top"><b></b></td>
650 <td align="left" valign="top">
651 <p>You need to update Sylpheed cache. Right click on the mailbox and choose
652 <span class="guimenuitem">Rebuild folder tree</span>.
653 </p>
654 </td>
655 </tr>
656 <tr class="question">
657 <td align="left" valign="top"><a name="d0e1345"></a><a name="d0e1346"></a><b>2.30.</b></td>
658 <td align="left" valign="top">
659 <p>How can I revert original settings, e.g. for fonts, key bindings, etc.?</p>
660 </td>
661 </tr>
662 <tr class="answer">
663 <td align="left" valign="top"><b></b></td>
664 <td align="left" valign="top">
665 <p>Sylpheed keeps its configuration files in <code class="filename">$HOME/.sylpheed-2.0/sylpheedrc</code> (or <code class="filename">%APPDATA%\Sylpheed\sylpheedrc</code> under Windows) and creates default
666 entries, if none are found. So the easiest way is to quit Sylpheed,
667 temporarily renaming your <code class="filename">$HOME/.sylpheed-2.0</code> (or <code class="filename">%APPDATA%\Sylpheed\sylpheedrc</code>) e.g. to <code class="filename">*.bak</code> and restarting
668 Sylpheed in order to get default entries.
669 </p>
670 </td>
671 </tr>
672 <tr class="question">
673 <td align="left" valign="top"><a name="d0e1367"></a><a name="faq-environment-variables"></a><b>2.31.</b></td>
674 <td align="left" valign="top">
675 <p>What environment variables have effect on Sylpheed?</p>
676 </td>
677 </tr>
678 <tr class="answer">
679 <td align="left" valign="top"><b></b></td>
680 <td align="left" valign="top">
681 <p>Here are the most common variables:</p>
682 <div class="itemizedlist">
683 <ul type="disc">
684 <li>
685 <p><code class="envar">HOME</code>
686 - location of <code class="filename">.sylpheed-2.0</code> (config directory) and default folder for Mailboxes.
687 </p>
688 </li>
689 <li>
690 <p><code class="envar">LANG</code>,
691 </p>
692 </li>
693 <li>
694 <p><code class="envar">LC_ALL</code>,
695 </p>
696 </li>
697 <li>
698 <p><code class="envar">LC_CTYPE</code>,
699 </p>
700 </li>
701 <li>
702 <p><code class="envar">LC_MESSAGES</code> - locale settings, e.g. language and date format.
703 </p>
704 </li>
705 </ul>
706 </div>
707 <p>For more information on how to make Sylpheed display your language, see the <a href="sylpheed-faq-3.html#faq-display-language">relevant question</a>.
708 </p>
709 </td>
710 </tr>
711 <tr class="question">
712 <td align="left" valign="top"><a name="d0e1408"></a><a name="d0e1409"></a><b>2.32.</b></td>
713 <td align="left" valign="top">
714 <p>Special characters (e.g. umlauts) are not displayed correctly.</p>
715 </td>
716 </tr>
717 <tr class="answer">
718 <td align="left" valign="top"><b></b></td>
719 <td align="left" valign="top">
720 <p>In most cases, this is caused by fonts that use an unsuitable encoding on a not Unicode-based system. (On a Unicode-based
721 system, fonts should support all thinkable characters for the vast majority of languages.)
722 </p>
723 <p>Choose <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Common preferences...</span>-&gt;<span class="guimenuitem">Display</span>-&gt;<span class="guimenuitem">General</span>, and click the button right to <span class="guilabel">Text font</span>. Now, a special dialog appears that allows you to pick a desirable font family, style, and size.
724 </p>
725 <p>You should also make sure that your environment variables regarding locale
726 settings have sensible values.
727 </p>
728 </td>
729 </tr>
730 <tr class="question">
731 <td align="left" valign="top"><a name="d0e1432"></a><a name="d0e1433"></a><b>2.33.</b></td>
732 <td align="left" valign="top">
733 <p>How can I convert my old mailbox/address book from (some mail client).</p>
734 </td>
735 </tr>
736 <tr class="answer">
737 <td align="left" valign="top"><b></b></td>
738 <td align="left" valign="top">
739 <p>You can try to
740 export your old mailbox to MH, MBOX or EML format.
741 </p>
742 <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;">
743 <h3 class="title">Tip</h3>
744 <p>Take a look at the <span class="guimenuitem">Add sender to address book...</span> item from the <span class="guimenu">Tools</span>
745 menu, it could be a useful alternative or addition, when importing your old
746 contacts.
747 </p>
748 </div>
749 </td>
750 </tr>
751 <tr class="question">
752 <td align="left" valign="top"><a name="d0e1448"></a><a name="d0e1449"></a><b>2.34.</b></td>
753 <td align="left" valign="top">
754 <p>What config files are there, and what are they used for?</p>
755 </td>
756 </tr>
757 <tr class="answer">
758 <td align="left" valign="top"><b></b></td>
759 <td align="left" valign="top">
760 <p>Sylpheed config files can be found in <code class="filename">$HOME/.sylpheed-2.0</code> (under Windows, the path is <code class="filename">%APPDATA%\Sylpheed</code>). They are in plain
761 text format and quite easy to understand, so don't fear to take a look
762 into them using a text editor.
763 </p>
764 <div class="itemizedlist">
765 <ul type="disc">
766 <li>
767 <p><code class="filename">sylpheedrc</code> - main configuration: nearly all options from the
768 settings window, e.g. mailbox location, font
769 entries, etc.
770 </p>
771 </li>
772 <li>
773 <p><code class="filename">accountrc</code> - settings for POP/IMAP/NNTP accounts
774 </p>
775 </li>
776 <li>
777 <p><code class="filename">actionsrc</code> - user-defined actions
778 </p>
779 </li>
780 <li>
781 <p><code class="filename">addrbook-*.xml</code> - contents of your address book
782 </p>
783 </li>
784 <li>
785 <p><code class="filename">customheaderrc</code> - contains user-defined header lines
786 </p>
787 </li>
788 <li>
789 <p><code class="filename">dispheaderrc</code> - headers to display above the mail body
790 </p>
791 </li>
792 <li>
793 <p><code class="filename">filter.xml</code> - filter settings
794 </p>
795 </li>
796 <li>
797 <p><code class="filename">folderlist.xml</code> - folder specific settings, e.g. hiding
798 read messages, sort order, etc.
799 </p>
800 </li>
801 <li>
802 <p><code class="filename">menurc</code> - key bindings
803 </p>
804 </li>
805 </ul>
806 </div>
807 </td>
808 </tr>
809 <tr class="question">
810 <td align="left" valign="top"><a name="d0e1507"></a><a name="d0e1508"></a><b>2.35.</b></td>
811 <td align="left" valign="top">
812 <p>How do I change the location of user profile directory under Windows?</p>
813 </td>
814 </tr>
815 <tr class="answer">
816 <td align="left" valign="top"><b></b></td>
817 <td align="left" valign="top">
818 <p>The configuration files and the mailboxes are saved under the following
819 location (<code class="filename">%APPDATA%\Sylpheed</code>) by default:
820 </p>
821 <div class="itemizedlist">
822 <ul type="disc">
823 <li>
824 <p>Windows 2000/XP:
825 <code class="filename">C:\Documents and Settings\<em class="replaceable"><code>(user name)</code></em>\Application Data\Sylpheed</code></p>
826 </li>
827 <li>
828 <p>Windows Vista/Seven:
829 <code class="filename">C:\Users\<em class="replaceable"><code>(user name)</code></em>\AppData\Roaming\Sylpheed</code></p>
830 </li>
831 </ul>
832 </div>
833 <p>If you want to change the location of the configuration files, you can
834 specify it by the command line option <em class="parameter"><code>--configdir "<em class="replaceable"><code>directory name</code></em>"</code></em>.
835 Create a shortcut of <code class="filename">sylpheed.exe</code>, and append the option to the link target
836 like the following:
837 </p><pre class="screen">"C:\Program Files\Sylpheed\sylpheed.exe" --configdir "D:\Sylpheed"</pre><p>If <code class="filename">sylpheed.ini</code> file exists at the same location as <code class="filename">sylpheed.exe</code>, it will be
838 loaded at startup. With this approach, you can make Sylpheed completely portable
839 independent of drive letters etc., and you can install it in removable media
840 such as USB memory.
841 </p>
842 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
843 <h3 class="title">Note</h3>
844 <p>The installer version, and GnuPG and GPGME use registry.</p>
845 </div>
846 <p>The sample INI file is included in the Sylpheed for Windows installation package as <code class="filename">sample-sylpheed.ini</code>.
847 Please copy or rename it to use.
848 <code class="literal">ipcport</code> specifies the port number of socket for IPC (default is 50215).
849 <code class="literal">configdir</code> specifies the location of configuration files as a relative
850 path from the folder in which <code class="filename">sylpheed.exe</code> is located, or an absolute path.
851 </p>
852 <p>(The text above is a slightly modified excerpt from the <code class="filename">README-win32.txt</code> file, which you should find within the <code class="filename">C:\Program Files\Sylpheed</code> directory.)
853 </p>
854 </td>
855 </tr>
856 <tr class="question">
857 <td align="left" valign="top"><a name="d0e1581"></a><a name="d0e1582"></a><b>2.36.</b></td>
858 <td align="left" valign="top">
859 <p>Can I run multiple instances of Sylpheed?</p>
860 </td>
861 </tr>
862 <tr class="answer">
863 <td align="left" valign="top"><b></b></td>
864 <td align="left" valign="top">
865 <p>Yes, Sylpheed 3.1 adds support for this often requested feature. The format of the multiple instances command is as follows:</p>
866 <p><span><strong class="command">sylpheed --instance-id <em class="replaceable"><code>ID</code></em> --configdir <em class="replaceable"><code>path-to-alternative-configdir</code></em></strong></span></p>
867 <p>Default <em class="parameter"><code>ID</code></em> is set to <code class="literal">sylpheed</code>, so you can specify any other instance
868 <em class="parameter"><code>ID</code></em>. The <em class="parameter"><code>ID</code></em> is used for the name of unix domain
869 socket (under UNIX), or mutex name (under Windows). <em class="parameter"><code>configdir</code></em> specifies the configuration directory, i.e. the location of configuration files you want to use with the given instance.
870 </p>
871 <div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
872 <h3 class="title">Warning</h3>
873 <p>Do not share same configuration directories or mailboxes across multiple instances as this may lead to an unexpected application
874 behavior!
875 </p>
876 </div>
877 </td>
878 </tr>
879 <tr class="question">
880 <td align="left" valign="top"><a name="d0e1616"></a><a name="d0e1617"></a><b>2.37.</b></td>
881 <td align="left" valign="top">
882 <p>What to do when printing an email prints off the paper?</p>
883 </td>
884 </tr>
885 <tr class="answer">
886 <td align="left" valign="top"><b></b></td>
887 <td align="left" valign="top">
888 <p>You can use enscript for this. Use <span><strong class="command">enscript %s</strong></span> to print everything on one page, or <span><strong class="command">enscript -U2 %s</strong></span> for printing two logical pages on one physical page.
889 </p>
890 </td>
891 </tr>
892 </tbody>
893 </table>
894 </div>
895 </div>
896 <div class="navfooter">
897 <hr>
898 <table width="100%" summary="Navigation footer">
899 <tr>
900 <td width="40%" align="left"><a accesskey="p" href="sylpheed-faq-1.html">Prev</a>&nbsp;
901 </td>
902 <td width="20%" align="center">&nbsp;</td>
903 <td width="40%" align="right">&nbsp;<a accesskey="n" href="sylpheed-faq-3.html">Next</a></td>
904 </tr>
905 <tr>
906 <td width="40%" align="left" valign="top">Chapter&nbsp;1.&nbsp;Sylpheed FAQ - General Information&nbsp;</td>
907 <td width="20%" align="center"><a accesskey="h" href="sylpheed-faq.html">Home</a></td>
908 <td width="40%" align="right" valign="top">&nbsp;Chapter&nbsp;3.&nbsp;Sylpheed FAQ - Interface</td>
909 </tr>
910 </table>
911 </div>
912 </body>
913</html> \ No newline at end of file
diff --git a/faq/en/sylpheed-faq-3.html b/faq/en/sylpheed-faq-3.html
new file mode 100644
index 0000000..c667c22
--- /dev/null
+++ b/faq/en/sylpheed-faq-3.html
@@ -0,0 +1,432 @@
1<html>
2 <head>
3 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4
5 <title>Chapter&nbsp;3.&nbsp;Sylpheed FAQ - Interface</title>
6 <meta name="generator" content="DocBook XSL Stylesheets V1.68.1">
7 <link rel="start" href="sylpheed-faq.html" title="Sylpheed FAQ">
8 <link rel="up" href="sylpheed-faq.html" title="Sylpheed FAQ">
9 <link rel="prev" href="sylpheed-faq-2.html" title="Chapter&nbsp;2.&nbsp;Sylpheed FAQ - Installation and Configuration">
10 <link rel="next" href="sylpheed-faq-4.html" title="Appendix&nbsp;A.&nbsp;GNU Free Documentation License">
11 <link rel="chapter" href="sylpheed-faq-1.html" title="Chapter&nbsp;1.&nbsp;Sylpheed FAQ - General Information">
12 <link rel="chapter" href="sylpheed-faq-2.html" title="Chapter&nbsp;2.&nbsp;Sylpheed FAQ - Installation and Configuration">
13 <link rel="chapter" href="sylpheed-faq-3.html" title="Chapter&nbsp;3.&nbsp;Sylpheed FAQ - Interface">
14 <link rel="appendix" href="sylpheed-faq-4.html" title="Appendix&nbsp;A.&nbsp;GNU Free Documentation License"><style type="text/css">
15pre.programlisting, pre.screen {
16background-color : #e0e0e0;
17padding : 0.2cm;
18}
19.question {
20font-weight : bold;
21}
22
23</style></head>
24 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
25 <div class="navheader">
26 <table width="100%" summary="Navigation header">
27 <tr>
28 <th colspan="3" align="center">Chapter&nbsp;3.&nbsp;Sylpheed FAQ - Interface</th>
29 </tr>
30 <tr>
31 <td width="20%" align="left"><a accesskey="p" href="sylpheed-faq-2.html">Prev</a>&nbsp;
32 </td>
33 <th width="60%" align="center">&nbsp;</th>
34 <td width="20%" align="right">&nbsp;<a accesskey="n" href="sylpheed-faq-4.html">Next</a></td>
35 </tr>
36 </table>
37 <hr>
38 </div>
39 <div class="chapter" lang="en">
40 <div class="titlepage">
41 <div>
42 <div>
43 <h2 class="title"><a name="sylpheed-faq-3"></a>Chapter&nbsp;3.&nbsp;Sylpheed FAQ - Interface
44 </h2>
45 </div>
46 </div>
47 </div>
48 <div class="qandaset">
49 <dl>
50 <dt>3.1. <a href="sylpheed-faq-3.html#d0e1634">How do I make Sylpheed display my language?</a></dt>
51 <dt>3.2. <a href="sylpheed-faq-3.html#d0e1700">I don't like the default font. Can I change that?</a></dt>
52 <dt>3.3. <a href="sylpheed-faq-3.html#d0e1716">There are too many columns in the message list!</a></dt>
53 <dt>3.4. <a href="sylpheed-faq-3.html#d0e1735">How do I disable or enable the alternating row colors in the message list?</a></dt>
54 <dt>3.5. <a href="sylpheed-faq-3.html#d0e1769">Can I use a different editor to write my mails?</a></dt>
55 <dt>3.6. <a href="sylpheed-faq-3.html#d0e1807">How to change the font size in the Sylpheed interface?</a></dt>
56 <dt>3.7. <a href="sylpheed-faq-3.html#d0e1825">Sylpheed saves my outgoing mail (in Outbox). Can I make it stop doing that?</a></dt>
57 <dt>3.8. <a href="sylpheed-faq-3.html#d0e1841">How can I change the key bindings (hotkeys) in Sylpheed?</a></dt>
58 <dt>3.9. <a href="sylpheed-faq-3.html#d0e1932">Can I close windows without the mouse?</a></dt>
59 <dt>3.10. <a href="sylpheed-faq-3.html#d0e1948">Can I change the way the date is displayed in the message summary?</a></dt>
60 <dt>3.11. <a href="sylpheed-faq-3.html#d0e1975">Why can't I see the compface pictures?</a></dt>
61 <dt>3.12. <a href="sylpheed-faq-3.html#d0e1982">I still can't see the pictures. Why not?</a></dt>
62 <dt>3.13. <a href="sylpheed-faq-3.html#d0e1989">Why does the URL launcher not launch my web browser?</a></dt>
63 <dt>3.14. <a href="sylpheed-faq-3.html#d0e2006">Attachments with spaces in the name won't open!</a></dt>
64 <dt>3.15. <a href="sylpheed-faq-3.html#d0e2018">Execute command for my dynamic signature seems not to be working!</a></dt>
65 <dt>3.16. <a href="sylpheed-faq-3.html#d0e2040">Where is the Bcc when I compose a mail?</a></dt>
66 <dt>3.17. <a href="sylpheed-faq-3.html#d0e2058">How do I change the toolbar?</a></dt>
67 <dt>3.18. <a href="sylpheed-faq-3.html#d0e2080">Why isn't the next message displayed when I delete a message? </a></dt>
68 <dt>3.19. <a href="sylpheed-faq-3.html#d0e2100">How can I remove mailing list information from Subject headers?</a></dt>
69 </dl>
70 <table border="0" summary="Q and A Set" cellspacing="13px">
71 <col align="left" width="1%">
72 <tbody>
73 <tr class="question">
74 <td align="left" valign="top"><a name="d0e1634"></a><a name="faq-display-language"></a><b>3.1.</b></td>
75 <td align="left" valign="top">
76 <p>How do I make Sylpheed display my language?</p>
77 </td>
78 </tr>
79 <tr class="answer">
80 <td align="left" valign="top"><b></b></td>
81 <td align="left" valign="top">
82 <p>You have to set some environment variables, such as
83 <code class="envar">LANG</code>, <code class="envar">LC_CTYPE</code>, <code class="envar">LC_MESSAGES</code> to your local language.
84 Usually <code class="envar">LANG</code> (or <code class="envar">LC_ALL</code>) is sufficient. Note that modern distributions and operating systems do this for you automatically.
85 </p>
86 <p>Under UNIX, if you need to set e.g. the <code class="envar">LANG</code> environment variable manually, execute the following command (using <code class="literal">sh</code> or related shell):
87 </p>
88 <p><span><strong class="command">export LANG=<em class="replaceable"><code>value</code></em></strong></span></p>
89 <p>Replace <em class="replaceable"><code>value</code></em> with a valid ISO <a href="http://en.wikipedia.org/wiki/Language_code" target="_top">language code</a> (e.g. <code class="literal">en_GB</code> for British English).
90 </p>
91 <p>If you intend to set the displayed language manually under Windows, you can do so by creating the
92 <code class="envar">LANG</code> environment variable with a valid ISO language code value under <span class="guimenu">Control Panel</span>-&gt;<span class="guimenuitem">System</span>-&gt;<span class="guisubmenu">Advanced</span>+<span class="guibutton">Environment Variables</span>.
93 </p>
94 <p>Also see the <a href="sylpheed-faq-2.html#faq-environment-variables">question</a> regarding environment variables that have effect on Sylpheed.
95 </p>
96 </td>
97 </tr>
98 <tr class="question">
99 <td align="left" valign="top"><a name="d0e1700"></a><a name="d0e1701"></a><b>3.2.</b></td>
100 <td align="left" valign="top">
101 <p>I don't like the default font. Can I change that?</p>
102 </td>
103 </tr>
104 <tr class="answer">
105 <td align="left" valign="top"><b></b></td>
106 <td align="left" valign="top">
107 <p>Yes. In <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Common preferences...</span>, under the
108 <span class="guimenuitem">Display</span> tab.
109 </p>
110 </td>
111 </tr>
112 <tr class="question">
113 <td align="left" valign="top"><a name="d0e1716"></a><a name="d0e1717"></a><b>3.3.</b></td>
114 <td align="left" valign="top">
115 <p>There are too many columns in the message list!</p>
116 </td>
117 </tr>
118 <tr class="answer">
119 <td align="left" valign="top"><b></b></td>
120 <td align="left" valign="top">
121 <p>In <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Common preferences...</span> under the
122 <span class="guimenuitem">Display</span> tab, you can press the button <span class="guibutton">Set display item of summary...</span>. That pops up a screen with all the
123 options you can show or leave out of the message
124 list.
125 </p>
126 </td>
127 </tr>
128 <tr class="question">
129 <td align="left" valign="top"><a name="d0e1735"></a><a name="d0e1736"></a><b>3.4.</b></td>
130 <td align="left" valign="top">
131 <p>How do I disable or enable the alternating row colors in the message list?</p>
132 </td>
133 </tr>
134 <tr class="answer">
135 <td align="left" valign="top"><b></b></td>
136 <td align="left" valign="top">
137 <p>Under UNIX, you can directly edit the appropriate hidden setting stored in the <code class="filename">$HOME/.sylpheed-2.0/sylpheedrc</code> configuration file by changing the setting value to 0, or 1, respectively (default is on, i.e. 1):
138 </p><pre class="programlisting">enable_rules_hint=0</pre><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;">
139 <h3 class="title">Tip</h3>
140 <p>There are various other hidden settings that can be adjusted in your <code class="filename">sylpheedrc</code> configuration file, see the <code class="filename">README</code> file for details.
141 </p>
142 </div>
143 <p>The above does not work under Windows, however, so you have to edit the <code class="filename">C:\Program Files\Sylpheed\share\themes\MS-Windows\gtk-2.0\gtkrc</code> file and set the following setting to 1, or 0, respectively (default is off under Windows, i.e. 0):
144 </p><pre class="programlisting">GtkTreeView::allow-rules = 1</pre><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
145 <h3 class="title">Note</h3>
146 <p>Since the hidden setting described above is not stored within your user profile under Windows, it may be overwritten when
147 installing a new version of Sylpheed. To avoid this at least partially, keep a backup copy of the <code class="filename">gtkrc</code> file somewhere safe.
148 </p>
149 </div>
150 </td>
151 </tr>
152 <tr class="question">
153 <td align="left" valign="top"><a name="d0e1769"></a><a name="d0e1770"></a><b>3.5.</b></td>
154 <td align="left" valign="top">
155 <p>Can I use a different editor to write my mails?</p>
156 </td>
157 </tr>
158 <tr class="answer">
159 <td align="left" valign="top"><b></b></td>
160 <td align="left" valign="top">
161 <p>You can. In <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Common preferences</span>, under
162 the <span class="guimenuitem">Details</span> and <span class="guimenuitem">External commands</span> tabs, you can define your editor of choice.
163 Remember, if you want to use a command line editor
164 like vi or emacs, to write the name of the shell
165 (term, term, rxvt) with the <em class="parameter"><code>-e</code></em> parameter in front of
166 the editor. E.g.: <span><strong class="command">rxvt -e vi %s</strong></span>.
167 </p>
168 <p>Also, make sure that you have checked <span class="guilabel">Automatically launch the external editor</span> in <span class="guimenuitem">Common preferences</span>-&gt;<span class="guimenuitem">Compose</span>-&gt;<span class="guimenuitem">Editor</span>, if you want the editor of your choice to be launched every time you begin composing a message.
169 </p>
170 </td>
171 </tr>
172 <tr class="question">
173 <td align="left" valign="top"><a name="d0e1807"></a><a name="d0e1808"></a><b>3.6.</b></td>
174 <td align="left" valign="top">
175 <p>How to change the font size in the Sylpheed interface?</p>
176 </td>
177 </tr>
178 <tr class="answer">
179 <td align="left" valign="top"><b></b></td>
180 <td align="left" valign="top">
181 <p>You can set the GTK+ font by <code class="filename">$HOME/.gtkrc-2.0</code>, or
182 <code class="filename">$HOME/.gtkrc-2.0.mine</code>,
183 (which is included by <code class="filename">$HOME/.gtkrc-2.0</code>).
184 For example:
185 </p><pre class="programlisting">style "default" {
186 font = "-adobe-helvetica-medium-r-normal--12-*-*-*-*-*-iso8859-1 "
187}
188widget_class "*" style "default"
189</pre></td>
190 </tr>
191 <tr class="question">
192 <td align="left" valign="top"><a name="d0e1825"></a><a name="d0e1826"></a><b>3.7.</b></td>
193 <td align="left" valign="top">
194 <p>Sylpheed saves my outgoing mail (in Outbox). Can I make it stop doing that?</p>
195 </td>
196 </tr>
197 <tr class="answer">
198 <td align="left" valign="top"><b></b></td>
199 <td align="left" valign="top">
200 <p>In <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Common preferences...</span>, there is a
201 checkbox <span class="guilabel">Save sent message to outbox</span>. Uncheck it,
202 and it's solved.
203 </p>
204 </td>
205 </tr>
206 <tr class="question">
207 <td align="left" valign="top"><a name="d0e1841"></a><a name="d0e1842"></a><b>3.8.</b></td>
208 <td align="left" valign="top">
209 <p>How can I change the key bindings (hotkeys) in Sylpheed?</p>
210 </td>
211 </tr>
212 <tr class="answer">
213 <td align="left" valign="top"><b></b></td>
214 <td align="left" valign="top">
215 <p>Unlike Sylpheed 1.x, Sylpheed 2.x and 3.x doesn't allow direct modification of the menu shortcuts by default. Nevertheless,
216 you can use the following methods to configure them:
217 </p>
218 <div class="orderedlist">
219 <ol type="1">
220 <li>
221 <p><span class="emphasis"><em>Using GNOME 2.8 or later:</em></span> run gconf-editor from <span class="guimenu">Applications</span>-&gt;<span class="guisubmenu">System Tools</span>-&gt;<span class="guimenuitem">Configuration Editor</span>. Select <span class="guimenu">desktop</span>-&gt;<span class="guisubmenu">gnome</span>-&gt;<span class="guisubmenu">interface</span> and check <span class="guilabel">can-change-accels</span> there.
222 </p>
223 </li>
224 <li>
225 <p><span class="emphasis"><em>Using GNOME before 2.8, or other environments:</em></span> add the following line to the file <code class="filename">~/.gtkrc-2.0</code> (or create a new one, if it doesn't exist):
226 </p><pre class="programlisting">gtk-can-change-accels = 1</pre></li>
227 <li>
228 <p>When Sylpheed is not running, directly edit <code class="filename">~/.sylpheed-2.0/menurc</code> with a text editor.
229 </p>
230 </li>
231 </ol>
232 </div>
233 <p>After that, the key binding change itself is very simple. Suppose you want to assign a
234 shortcut key to a function, e.g. sending all mail
235 out should start when you press <span><strong class="keycap">Ctrl</strong></span>-<span><strong class="keycap">Y</strong></span>. Click the
236 <span class="guimenu">Message</span> menu and move the mouse over <span class="guimenuitem">Send all messages</span>. Now you press <span><strong class="keycap">Ctrl</strong></span>-<span><strong class="keycap">Y</strong></span>. Immediately the menu
237 text is updated and the function is in place. Please
238 note that a previous function that <span><strong class="keycap">Ctrl</strong></span>-<span><strong class="keycap">Y</strong></span> was
239 assigned to, will no longer have a shortcut key. If
240 you want to remove the key binding, do the same
241 thing, but press the <span><strong class="keycap">Delete</strong></span> key on the menu item.
242 Then the key binding is removed.
243 </p>
244 <p>Also see <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Common preferences...</span>-&gt;<span class="guimenuitem">Details</span>-&gt;<span class="guimenuitem">Interface</span>+<span class="guilabel">Set key bindings...</span> where you are able to reset the Default key bindings, or use other predefined key bindings.
245 </p>
246 </td>
247 </tr>
248 <tr class="question">
249 <td align="left" valign="top"><a name="d0e1932"></a><a name="d0e1933"></a><b>3.9.</b></td>
250 <td align="left" valign="top">
251 <p>Can I close windows without the mouse?</p>
252 </td>
253 </tr>
254 <tr class="answer">
255 <td align="left" valign="top"><b></b></td>
256 <td align="left" valign="top">
257 <p>Of course! Not all windows, but by pressing <span><strong class="keycap">Escape</strong></span>,
258 you can close the address book, the window of viewing
259 a mail source (<span class="guimenu">View</span>-&gt;<span class="guimenuitem">Message source</span>), the window of
260 viewing the headers, and several others. Just give
261 it a try and you will find all of them.
262 </p>
263 </td>
264 </tr>
265 <tr class="question">
266 <td align="left" valign="top"><a name="d0e1948"></a><a name="d0e1949"></a><b>3.10.</b></td>
267 <td align="left" valign="top">
268 <p>Can I change the way the date is displayed in the message summary?</p>
269 </td>
270 </tr>
271 <tr class="answer">
272 <td align="left" valign="top"><b></b></td>
273 <td align="left" valign="top">
274 <p>As of 0.4.65 you can. The options are:</p><pre class="programlisting"> %y = year in numbers %m = month in number
275 %d = day in numbers %c = date/time for locale
276 %A = full weekday name %a = short month name
277 %B = full month name %b = short month name
278 %H = hours in 24-clock %I = hours in 12-clock</pre><p>For more information, go to the <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Common preferences</span>-&gt;<span class="guimenuitem">Display</span>-&gt;<span class="guimenuitem">General</span> and choose the <span class="guibutton">...</span> labeled button.
279 For more options, see <span><strong class="command">man 3 strftime</strong></span>.
280 </p>
281 </td>
282 </tr>
283 <tr class="question">
284 <td align="left" valign="top"><a name="d0e1975"></a><a name="d0e1976"></a><b>3.11.</b></td>
285 <td align="left" valign="top">
286 <p>Why can't I see the compface pictures?</p>
287 </td>
288 </tr>
289 <tr class="answer">
290 <td align="left" valign="top"><b></b></td>
291 <td align="left" valign="top">
292 <p>You need to enable displaying of the header pane in the
293 general preferences.
294 </p>
295 </td>
296 </tr>
297 <tr class="question">
298 <td align="left" valign="top"><a name="d0e1982"></a><a name="d0e1983"></a><b>3.12.</b></td>
299 <td align="left" valign="top">
300 <p>I still can't see the pictures. Why not?</p>
301 </td>
302 </tr>
303 <tr class="answer">
304 <td align="left" valign="top"><b></b></td>
305 <td align="left" valign="top">
306 <p>You may not have compiled in Compface support. See the appropriate question in the Installation and Configuration section.</p>
307 </td>
308 </tr>
309 <tr class="question">
310 <td align="left" valign="top"><a name="d0e1989"></a><a name="d0e1990"></a><b>3.13.</b></td>
311 <td align="left" valign="top">
312 <p>Why does the URL launcher not launch my web browser?</p>
313 </td>
314 </tr>
315 <tr class="answer">
316 <td align="left" valign="top"><b></b></td>
317 <td align="left" valign="top">
318 <p>You need to double click the URL.
319 Also, check that you have configured your web browser correctly in <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Common preferences...</span>-&gt;<span class="guimenuitem"> Details</span>-&gt;<span class="guimenuitem">External commands</span>.
320 </p>
321 </td>
322 </tr>
323 <tr class="question">
324 <td align="left" valign="top"><a name="d0e2006"></a><a name="d0e2007"></a><b>3.14.</b></td>
325 <td align="left" valign="top">
326 <p>Attachments with spaces in the name won't open!</p>
327 </td>
328 </tr>
329 <tr class="answer">
330 <td align="left" valign="top"><b></b></td>
331 <td align="left" valign="top">
332 <p>When you try to launch a helper application, like an image viewer, with an attachment that has spaces in the name, put quotes
333 around the <em class="parameter"><code>%s</code></em>
334 parameter. Example: <span><strong class="command">gedit '%s'</strong></span></p>
335 </td>
336 </tr>
337 <tr class="question">
338 <td align="left" valign="top"><a name="d0e2018"></a><a name="d0e2019"></a><b>3.15.</b></td>
339 <td align="left" valign="top">
340 <p>Execute command for my dynamic signature seems not to be working!</p>
341 </td>
342 </tr>
343 <tr class="answer">
344 <td align="left" valign="top"><b></b></td>
345 <td align="left" valign="top">
346 <p>Under Windows, if you have created e.g. a simple batch file to echo a line to be included in your dynamic signature, you need
347 to execute the command (specified under <span class="guimenu">Account preferences</span>-&gt;<span class="guisubmenu">Compose</span>-&gt;<span class="guimenuitem">Signature</span>+<span class="guilabel">Command output</span>) using either forward slashes or double
348 backslashes for paths, for example:
349 </p>
350 <p><span><strong class="command">cmd /c 'c:\\signature.bat'</strong></span></p>
351 <p>Note that it is also recommended to enclose paths with single quotes, as is illustrated above.</p>
352 </td>
353 </tr>
354 <tr class="question">
355 <td align="left" valign="top"><a name="d0e2040"></a><a name="d0e2041"></a><b>3.16.</b></td>
356 <td align="left" valign="top">
357 <p>Where is the Bcc when I compose a mail?</p>
358 </td>
359 </tr>
360 <tr class="answer">
361 <td align="left" valign="top"><b></b></td>
362 <td align="left" valign="top">
363 <p>Open <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Preferences for current account...</span>-&gt;<span class="guimenuitem">Compose</span>. There you can check the <span class="guilabel">Bcc</span> checkbox and optionally enter an email address.
364 </p>
365 </td>
366 </tr>
367 <tr class="question">
368 <td align="left" valign="top"><a name="d0e2058"></a><a name="d0e2059"></a><b>3.17.</b></td>
369 <td align="left" valign="top">
370 <p>How do I change the toolbar?</p>
371 </td>
372 </tr>
373 <tr class="answer">
374 <td align="left" valign="top"><b></b></td>
375 <td align="left" valign="top">
376 <p>Go to <span class="guimenu">View</span>-&gt;<span class="guimenuitem">Customize toolbar...</span> and select items from the <span class="guilabel">Available items</span> list to be displayed on the toolbar. You can modify the order by using the <span class="guibutton">Up</span> or <span class="guibutton">Down</span> button. The customization dialog also offers you to revert your modifications to default.
377 </p>
378 </td>
379 </tr>
380 <tr class="question">
381 <td align="left" valign="top"><a name="d0e2080"></a><a name="d0e2081"></a><b>3.18.</b></td>
382 <td align="left" valign="top">
383 <p>Why isn't the next message displayed when I delete a message? </p>
384 </td>
385 </tr>
386 <tr class="answer">
387 <td align="left" valign="top"><b></b></td>
388 <td align="left" valign="top">
389 <p>Go to <span class="guimenu">Configuration</span>-&gt;<span class="guimenuitem">Common preferences...</span>-&gt;<span class="guimenuitem">Details</span>-&gt;<span class="guimenuitem">Interface</span>, and select <span class="guilabel">Always open messages in summary when selected</span>.
390 </p>
391 </td>
392 </tr>
393 <tr class="question">
394 <td align="left" valign="top"><a name="d0e2100"></a><a name="d0e2101"></a><b>3.19.</b></td>
395 <td align="left" valign="top">
396 <p>How can I remove mailing list information from Subject headers?</p>
397 </td>
398 </tr>
399 <tr class="answer">
400 <td align="left" valign="top"><b></b></td>
401 <td align="left" valign="top">
402 <p>Very often, when you are subscribed to a mailing list, you will store each message from that list in a folder dedicated to
403 that list. Depending on remote software solution and configuration, mailing lists tend to include some words in the Subject
404 header to identify the messages, optionally accompanied with a message number, for instance <code class="literal">[sylpheed:33101]</code>. These additions do not provide useful info if you have organized your folders as described, but Sylpheed allows you to disable
405 displaying the additions in summary, and/or, if you wish, delete the additions on reply.
406 </p>
407 <p>To do that, right-click on a folder from the folder tree, and select <span class="guimenuitem">Properties...</span> In the <span class="guilabel">Folder properties</span> dialog, check <span class="guilabel">Don't display [...] or (...) at the beginning of subject in summary</span>, or <span class="guilabel">Delete [...] or (...) at the beginning of subject on reply</span>, respectively.
408 </p>
409 </td>
410 </tr>
411 </tbody>
412 </table>
413 </div>
414 </div>
415 <div class="navfooter">
416 <hr>
417 <table width="100%" summary="Navigation footer">
418 <tr>
419 <td width="40%" align="left"><a accesskey="p" href="sylpheed-faq-2.html">Prev</a>&nbsp;
420 </td>
421 <td width="20%" align="center">&nbsp;</td>
422 <td width="40%" align="right">&nbsp;<a accesskey="n" href="sylpheed-faq-4.html">Next</a></td>
423 </tr>
424 <tr>
425 <td width="40%" align="left" valign="top">Chapter&nbsp;2.&nbsp;Sylpheed FAQ - Installation and Configuration&nbsp;</td>
426 <td width="20%" align="center"><a accesskey="h" href="sylpheed-faq.html">Home</a></td>
427 <td width="40%" align="right" valign="top">&nbsp;Appendix&nbsp;A.&nbsp;GNU Free Documentation License</td>
428 </tr>
429 </table>
430 </div>
431 </body>
432</html> \ No newline at end of file
diff --git a/faq/en/sylpheed-faq-4.html b/faq/en/sylpheed-faq-4.html
new file mode 100644
index 0000000..20a7f02
--- /dev/null
+++ b/faq/en/sylpheed-faq-4.html
@@ -0,0 +1,601 @@
1<html>
2 <head>
3 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4
5 <title>Appendix&nbsp;A.&nbsp;GNU Free Documentation License</title>
6 <meta name="generator" content="DocBook XSL Stylesheets V1.68.1">
7 <link rel="start" href="sylpheed-faq.html" title="Sylpheed FAQ">
8 <link rel="up" href="sylpheed-faq.html" title="Sylpheed FAQ">
9 <link rel="prev" href="sylpheed-faq-3.html" title="Chapter&nbsp;3.&nbsp;Sylpheed FAQ - Interface">
10 <link rel="chapter" href="sylpheed-faq-1.html" title="Chapter&nbsp;1.&nbsp;Sylpheed FAQ - General Information">
11 <link rel="chapter" href="sylpheed-faq-2.html" title="Chapter&nbsp;2.&nbsp;Sylpheed FAQ - Installation and Configuration">
12 <link rel="chapter" href="sylpheed-faq-3.html" title="Chapter&nbsp;3.&nbsp;Sylpheed FAQ - Interface">
13 <link rel="appendix" href="sylpheed-faq-4.html" title="Appendix&nbsp;A.&nbsp;GNU Free Documentation License">
14 <link rel="section" href="sylpheed-faq-4.html#gfdl-0" title="A.1.&nbsp;PREAMBLE">
15 <link rel="section" href="sylpheed-faq-4.html#gfdl-1" title="A.2.&nbsp;APPLICABILITY AND DEFINITIONS">
16 <link rel="section" href="sylpheed-faq-4.html#gfdl-2" title="A.3.&nbsp;VERBATIM COPYING">
17 <link rel="section" href="sylpheed-faq-4.html#gfdl-3" title="A.4.&nbsp;COPYING IN QUANTITY">
18 <link rel="section" href="sylpheed-faq-4.html#gfdl-4" title="A.5.&nbsp;MODIFICATIONS">
19 <link rel="section" href="sylpheed-faq-4.html#gfdl-5" title="A.6.&nbsp;COMBINING DOCUMENTS">
20 <link rel="section" href="sylpheed-faq-4.html#gfdl-6" title="A.7.&nbsp;COLLECTIONS OF DOCUMENTS">
21 <link rel="section" href="sylpheed-faq-4.html#gfdl-7" title="A.8.&nbsp;AGGREGATION WITH INDEPENDENT WORKS">
22 <link rel="section" href="sylpheed-faq-4.html#gfdl-8" title="A.9.&nbsp;TRANSLATION">
23 <link rel="section" href="sylpheed-faq-4.html#gfdl-9" title="A.10.&nbsp;TERMINATION">
24 <link rel="section" href="sylpheed-faq-4.html#gfdl-10" title="A.11.&nbsp;FUTURE REVISIONS OF THIS LICENSE">
25 <link rel="section" href="sylpheed-faq-4.html#gfdl-addendum" title="A.12.&nbsp;ADDENDUM: How to use this License for your documents"><style type="text/css">
26pre.programlisting, pre.screen {
27background-color : #e0e0e0;
28padding : 0.2cm;
29}
30.question {
31font-weight : bold;
32}
33
34</style></head>
35 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
36 <div class="navheader">
37 <table width="100%" summary="Navigation header">
38 <tr>
39 <th colspan="3" align="center">Appendix&nbsp;A.&nbsp;GNU Free Documentation License</th>
40 </tr>
41 <tr>
42 <td width="20%" align="left"><a accesskey="p" href="sylpheed-faq-3.html">Prev</a>&nbsp;
43 </td>
44 <th width="60%" align="center">&nbsp;</th>
45 <td width="20%" align="right">&nbsp;</td>
46 </tr>
47 </table>
48 <hr>
49 </div>
50 <div class="appendix" lang="en">
51 <div class="titlepage">
52 <div>
53 <div>
54 <h1 class="title"><a name="sylpheed-faq-4"></a>GNU Free Documentation License
55 </h1>
56 </div>
57 <div>
58 <p class="releaseinfo">Version 1.2, November 2002</p>
59 </div>
60 <div>
61 <p class="copyright">Copyright &copy; 2000,2001,2002 Free Software Foundation, Inc.</p>
62 </div>
63 <div>
64 <div class="legalnotice"><a name="gfdl-legalnotice"></a><div class="address">
65 <p>Free&nbsp;Software&nbsp;Foundation,&nbsp;Inc.&nbsp;<span class="street">51&nbsp;Franklin&nbsp;St,&nbsp;Fifth&nbsp;Floor</span>,&nbsp;<span class="city">Boston</span>,&nbsp;<span class="state">MA</span><span class="postcode">02110-1301</span><span class="country">USA</span></p>
66 </div>
67 <p>Everyone is permitted to copy and distribute verbatim copies
68 of this license document, but changing it is not allowed.
69 </p>
70 </div>
71 </div>
72 <div>
73 <p class="pubdate">Version 1.2, November 2002</p>
74 </div>
75 </div>
76 </div>
77 <div class="toc">
78 <dl>
79 <dt><span class="section"><a href="sylpheed-faq-4.html#gfdl-0">A.1. PREAMBLE</a></span></dt>
80 <dt><span class="section"><a href="sylpheed-faq-4.html#gfdl-1">A.2. APPLICABILITY AND DEFINITIONS</a></span></dt>
81 <dt><span class="section"><a href="sylpheed-faq-4.html#gfdl-2">A.3. VERBATIM COPYING</a></span></dt>
82 <dt><span class="section"><a href="sylpheed-faq-4.html#gfdl-3">A.4. COPYING IN QUANTITY</a></span></dt>
83 <dt><span class="section"><a href="sylpheed-faq-4.html#gfdl-4">A.5. MODIFICATIONS</a></span></dt>
84 <dt><span class="section"><a href="sylpheed-faq-4.html#gfdl-5">A.6. COMBINING DOCUMENTS</a></span></dt>
85 <dt><span class="section"><a href="sylpheed-faq-4.html#gfdl-6">A.7. COLLECTIONS OF DOCUMENTS</a></span></dt>
86 <dt><span class="section"><a href="sylpheed-faq-4.html#gfdl-7">A.8. AGGREGATION WITH INDEPENDENT WORKS</a></span></dt>
87 <dt><span class="section"><a href="sylpheed-faq-4.html#gfdl-8">A.9. TRANSLATION</a></span></dt>
88 <dt><span class="section"><a href="sylpheed-faq-4.html#gfdl-9">A.10. TERMINATION</a></span></dt>
89 <dt><span class="section"><a href="sylpheed-faq-4.html#gfdl-10">A.11. FUTURE REVISIONS OF THIS LICENSE</a></span></dt>
90 <dt><span class="section"><a href="sylpheed-faq-4.html#gfdl-addendum">A.12. ADDENDUM: How to use this License for your documents</a></span></dt>
91 </dl>
92 </div>
93 <div class="section" lang="en">
94 <div class="titlepage">
95 <div>
96 <div>
97 <h2 class="title" style="clear: both"><a name="gfdl-0"></a>A.1.&nbsp;PREAMBLE
98 </h2>
99 </div>
100 </div>
101 </div>
102 <p>The purpose of this License is to make a manual, textbook, or
103 other functional and useful document "free" in the sense of freedom: to
104 assure everyone the effective freedom to copy and redistribute it, with
105 or without modifying it, either commercially or noncommercially.
106 Secondarily, this License preserves for the author and publisher a way
107 to get credit for their work, while not being considered responsible for
108 modifications made by others.
109 </p>
110 <p>This License is a kind of "copyleft", which means that derivative
111 works of the document must themselves be free in the same sense. It
112 complements the GNU General Public License, which is a copyleft license
113 designed for free software.
114 </p>
115 <p>We have designed this License in order to use it for manuals for
116 free software, because free software needs free documentation: a free
117 program should come with manuals providing the same freedoms that the
118 software does. But this License is not limited to software manuals; it
119 can be used for any textual work, regardless of subject matter or
120 whether it is published as a printed book. We recommend this License
121 principally for works whose purpose is instruction or reference.
122 </p>
123 </div>
124 <div class="section" lang="en">
125 <div class="titlepage">
126 <div>
127 <div>
128 <h2 class="title" style="clear: both"><a name="gfdl-1"></a>A.2.&nbsp;APPLICABILITY AND DEFINITIONS
129 </h2>
130 </div>
131 </div>
132 </div>
133 <p><a name="gfdl-doc"></a>This License applies to any manual or other work, in
134 any medium, that contains a notice placed by the copyright holder saying
135 it can be distributed under the terms of this License. Such a notice
136 grants a world-wide, royalty-free license, unlimited in duration, to use
137 that work under the conditions stated herein. The "Document", below,
138 refers to any such manual or work. Any member of the public is a
139 licensee, and is addressed as "you". You accept the license if you
140 copy, modify or distribute the work in a way requiring permission under
141 copyright law.
142 </p>
143 <p><a name="gfdl-mod-ver"></a>A "Modified Version" of the Document means any
144 work containing the Document or a portion of it, either copied verbatim,
145 or with modifications and/or translated into another language.
146 </p>
147 <p><a name="gfdl-secnd-sect"></a>A "Secondary Section" is a named appendix or
148 a front-matter section of the Document that deals exclusively with the
149 relationship of the publishers or authors of the Document to the
150 Document's overall subject (or to related matters) and contains nothing
151 that could fall directly within that overall subject. (Thus, if the
152 Document is in part a textbook of mathematics, a Secondary Section may
153 not explain any mathematics.) The relationship could be a matter of
154 historical connection with the subject or with related matters, or of
155 legal, commercial, philosophical, ethical or political position
156 regarding them.
157 </p>
158 <p><a name="gfdl-inv-sect"></a>The "Invariant Sections" are certain Secondary
159 Sections whose titles are designated, as being those of Invariant
160 Sections, in the notice that says that the Document is released under
161 this License. If a section does not fit the above definition of
162 Secondary then it is not allowed to be designated as Invariant. The
163 Document may contain zero Invariant Sections. If the Document does not
164 identify any Invariant Sections then there are none.
165 </p>
166 <p><a name="gfdl-cov-text"></a>The "Cover Texts" are certain short passages of
167 text that are listed, as Front-Cover Texts or Back-Cover Texts, in the
168 notice that says that the Document is released under this License. A
169 Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at
170 most 25 words.
171 </p>
172 <p><a name="gfdl-transparent"></a>A "Transparent" copy of the Document means a
173 machine-readable copy, represented in a format whose specification is
174 available to the general public, that is suitable for revising the
175 document straightforwardly with generic text editors or (for images
176 composed of pixels) generic paint programs or (for drawings) some widely
177 available drawing editor, and that is suitable for input to text
178 formatters or for automatic translation to a variety of formats suitable
179 for input to text formatters. A copy made in an otherwise Transparent
180 file format whose markup, or absence of markup, has been arranged to
181 thwart or discourage subsequent modification by readers is not
182 Transparent. An image format is not Transparent if used for any
183 substantial amount of text. A copy that is not "Transparent" is called
184 "Opaque".
185 </p>
186 <p>Examples of suitable formats for Transparent copies include plain
187 ASCII without markup, Texinfo input format, LaTeX input format, SGML or
188 XML using a publicly available DTD, and standard-conforming simple HTML,
189 PostScript or PDF designed for human modification. Examples of
190 transparent image formats include PNG, XCF and JPG. Opaque formats
191 include proprietary formats that can be read and edited only by
192 proprietary word processors, SGML or XML for which the DTD and/or
193 processing tools are not generally available, and the machine-generated
194 HTML, PostScript or PDF produced by some word processors for output
195 purposes only.
196 </p>
197 <p><a name="gfdl-title-page"></a>The "Title Page" means, for a printed book,
198 the title page itself, plus such following pages as are needed to hold,
199 legibly, the material this License requires to appear in the title page.
200 For works in formats which do not have any title page as such, "Title
201 Page" means the text near the most prominent appearance of the work's
202 title, preceding the beginning of the body of the text.
203 </p>
204 <p><a name="gfdl-entitled"></a>A section "Entitled XYZ" means a named subunit
205 of the Document whose title either is precisely XYZ or contains XYZ in
206 parentheses following text that translates XYZ in another language.
207 (Here XYZ stands for a specific section name mentioned below, such as
208 "Acknowledgements", "Dedications", "Endorsements", or "History".) To
209 "Preserve the Title" of such a section when you modify the Document
210 means that it remains a section "Entitled XYZ" according to this
211 definition.
212 </p>
213 <p>The Document may include Warranty Disclaimers next to the notice
214 which states that this License applies to the Document. These Warranty
215 Disclaimers are considered to be included by reference in this License,
216 but only as regards disclaiming warranties: any other implication that
217 these Warranty Disclaimers may have is void and has no effect on the
218 meaning of this License.
219 </p>
220 </div>
221 <div class="section" lang="en">
222 <div class="titlepage">
223 <div>
224 <div>
225 <h2 class="title" style="clear: both"><a name="gfdl-2"></a>A.3.&nbsp;VERBATIM COPYING
226 </h2>
227 </div>
228 </div>
229 </div>
230 <p>You may copy and distribute the Document in any medium, either
231 commercially or noncommercially, provided that this License, the
232 copyright notices, and the license notice saying this License applies to
233 the Document are reproduced in all copies, and that you add no other
234 conditions whatsoever to those of this License. You may not use
235 technical measures to obstruct or control the reading or further copying
236 of the copies you make or distribute. However, you may accept
237 compensation in exchange for copies. If you distribute a large enough
238 number of copies you must also follow the conditions in section 3.
239
240 </p>
241 <p>You may also lend copies, under the same conditions stated above,
242 and you may publicly display copies.
243 </p>
244 </div>
245 <div class="section" lang="en">
246 <div class="titlepage">
247 <div>
248 <div>
249 <h2 class="title" style="clear: both"><a name="gfdl-3"></a>A.4.&nbsp;COPYING IN QUANTITY
250 </h2>
251 </div>
252 </div>
253 </div>
254 <p>If you publish printed copies (or copies in media that commonly
255 have printed covers) of the Document, numbering more than 100, and the
256 Document's license notice requires Cover Texts, you must enclose the
257 copies in covers that carry, clearly and legibly, all these Cover Texts:
258 Front-Cover Texts on the front cover, and Back-Cover Texts on the back
259 cover. Both covers must also clearly and legibly identify you as the
260 publisher of these copies. The front cover must present the full title
261 with all words of the title equally prominent and visible. You may add
262 other material on the covers in addition. Copying with changes limited
263 to the covers, as long as they preserve the title of the Document and
264 satisfy these conditions, can be treated as verbatim copying in other
265 respects.
266 </p>
267 <p>If the required texts for either cover are too voluminous to fit
268 legibly, you should put the first ones listed (as many as fit
269 reasonably) on the actual cover, and continue the rest onto adjacent
270 pages.
271 </p>
272 <p>If you publish or distribute Opaque copies of the Document
273 numbering more than 100, you must either include a machine-readable
274 Transparent copy along with each Opaque copy, or state in or with each
275 Opaque copy a computer-network location from which the general
276 network-using public has access to download using public-standard
277 network protocols a complete Transparent copy of the Document, free of
278 added material. If you use the latter option, you must take reasonably
279 prudent steps, when you begin distribution of Opaque copies in quantity,
280 to ensure that this Transparent copy will remain thus accessible at the
281 stated location until at least one year after the last time you
282 distribute an Opaque copy (directly or through your agents or retailers)
283 of that edition to the public.
284 </p>
285 <p>It is requested, but not required, that you contact the authors of
286 the Document well before redistributing any large number of copies, to
287 give them a chance to provide you with an updated version of the
288 Document.
289 </p>
290 </div>
291 <div class="section" lang="en">
292 <div class="titlepage">
293 <div>
294 <div>
295 <h2 class="title" style="clear: both"><a name="gfdl-4"></a>A.5.&nbsp;MODIFICATIONS
296 </h2>
297 </div>
298 </div>
299 </div>
300 <p>You may copy and distribute a Modified Version of the Document
301 under the conditions of sections 2 and 3 above, provided that you
302 release the Modified Version under precisely this License, with the
303 Modified Version filling the role of the Document, thus licensing
304 distribution and modification of the Modified Version to whoever
305 possesses a copy of it. In addition, you must do these things in the
306 Modified Version:
307 </p>
308 <div class="orderedlist"><a name="gfdl-modif-cond"></a><p class="title"><b>GNU FDL Modification Conditions</b></p>
309 <ol type="A">
310 <li>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
311 (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous
312 version if the original publisher of that version gives permission.
313 </li>
314 <li>List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the
315 Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it
316 has fewer than five), unless they release you from this requirement.
317 </li>
318 <li>State on the Title page the name of the publisher of the Modified Version, as the publisher.</li>
319 <li>Preserve all the copyright notices of the Document. </li>
320 <li>Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. </li>
321 <li>Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version
322 under the terms of this License, in the form shown in the <a href="sylpheed-faq-4.html#gfdl-addendum" title="A.12.&nbsp;ADDENDUM: How to use this License for your documents">Addendum</a> below.
323 </li>
324 <li>Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license
325 notice.
326 </li>
327 <li>Include an unaltered copy of this License. </li>
328 <li>Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors,
329 and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document,
330 create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing
331 the Modified Version as stated in the previous sentence.
332 </li>
333 <li>Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and
334 likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History"
335 section. You may omit a network location for a work that was published at least four years before the Document itself, or
336 if the original publisher of the version it refers to gives permission.
337 </li>
338 <li>For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section
339 all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
340 </li>
341 <li>Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent
342 are not considered part of the section titles.
343 </li>
344 <li>Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. </li>
345 <li>Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section. </li>
346 <li>Preserve any Warranty Disclaimers. </li>
347 </ol>
348 </div>
349 <p>If the Modified Version includes new front-matter sections or
350 appendices that qualify as Secondary Sections and contain no material
351 copied from the Document, you may at your option designate some or all
352 of these sections as invariant. To do this, add their titles to the
353 list of Invariant Sections in the Modified Version's license notice.
354 These titles must be distinct from any other section titles.
355 </p>
356 <p>You may add a section Entitled "Endorsements", provided it
357 contains nothing but endorsements of your Modified Version by various
358 parties--for example, statements of peer review or that the text has
359 been approved by an organization as the authoritative definition of a
360 standard.
361 </p>
362 <p>You may add a passage of up to five words as a Front-Cover Text,
363 and a passage of up to 25 words as a Back-Cover Text, to the end of the
364 list of Cover Texts in the Modified Version. Only one passage of
365 Front-Cover Text and one of Back-Cover Text may be added by (or through
366 arrangements made by) any one entity. If the Document already includes
367 a cover text for the same cover, previously added by you or by
368 arrangement made by the same entity you are acting on behalf of, you may
369 not add another; but you may replace the old one, on explicit permission
370 from the previous publisher that added the old one.
371 </p>
372 <p>The author(s) and publisher(s) of the Document do not by this
373 License give permission to use their names for publicity for or to
374 assert or imply endorsement of any Modified Version.
375 </p>
376 </div>
377 <div class="section" lang="en">
378 <div class="titlepage">
379 <div>
380 <div>
381 <h2 class="title" style="clear: both"><a name="gfdl-5"></a>A.6.&nbsp;COMBINING DOCUMENTS
382 </h2>
383 </div>
384 </div>
385 </div>
386 <p>You may combine the Document with other documents released under
387 this License, under the terms defined in <a href="sylpheed-faq-4.html#gfdl-4" title="A.5.&nbsp;MODIFICATIONS">section 4</a> above for modified versions, provided that you include in the
388 combination all of the Invariant Sections of all of the original
389 documents, unmodified, and list them all as Invariant Sections of your
390 combined work in its license notice, and that you preserve all their
391 Warranty Disclaimers.
392 </p>
393 <p>The combined work need only contain one copy of this License, and
394 multiple identical Invariant Sections may be replaced with a single
395 copy. If there are multiple Invariant Sections with the same name but
396 different contents, make the title of each such section unique by adding
397 at the end of it, in parentheses, the name of the original author or
398 publisher of that section if known, or else a unique number. Make the
399 same adjustment to the section titles in the list of Invariant Sections
400 in the license notice of the combined work.
401 </p>
402 <p>In the combination, you must combine any sections Entitled
403 "History" in the various original documents, forming one section
404 Entitled "History"; likewise combine any sections Entitled
405 "Acknowledgements", and any sections Entitled "Dedications". You must
406 delete all sections Entitled "Endorsements".
407 </p>
408 </div>
409 <div class="section" lang="en">
410 <div class="titlepage">
411 <div>
412 <div>
413 <h2 class="title" style="clear: both"><a name="gfdl-6"></a>A.7.&nbsp;COLLECTIONS OF DOCUMENTS
414 </h2>
415 </div>
416 </div>
417 </div>
418 <p>You may make a collection consisting of the Document and other
419 documents released under this License, and replace the individual copies
420 of this License in the various documents with a single copy that is
421 included in the collection, provided that you follow the rules of this
422 License for verbatim copying of each of the documents in all other
423 respects.
424 </p>
425 <p>You may extract a single document from such a collection, and
426 distribute it individually under this License, provided you insert a
427 copy of this License into the extracted document, and follow this
428 License in all other respects regarding verbatim copying of that
429 document.
430 </p>
431 </div>
432 <div class="section" lang="en">
433 <div class="titlepage">
434 <div>
435 <div>
436 <h2 class="title" style="clear: both"><a name="gfdl-7"></a>A.8.&nbsp;AGGREGATION WITH INDEPENDENT WORKS
437 </h2>
438 </div>
439 </div>
440 </div>
441 <p>A compilation of the Document or its derivatives with other
442 separate and independent documents or works, in or on a volume of a
443 storage or distribution medium, is called an "aggregate" if the
444 copyright resulting from the compilation is not used to limit the legal
445 rights of the compilation's users beyond what the individual works
446 permit. When the Document is included in an aggregate, this License does
447 not apply to the other works in the aggregate which are not themselves
448 derivative works of the Document.
449 </p>
450 <p>If the Cover Text requirement of section 3 is applicable to these
451 copies of the Document, then if the Document is less than one half of
452 the entire aggregate, the Document's Cover Texts may be placed on covers
453 that bracket the Document within the aggregate, or the electronic
454 equivalent of covers if the Document is in electronic form. Otherwise
455 they must appear on printed covers that bracket the whole
456 aggregate.
457 </p>
458 </div>
459 <div class="section" lang="en">
460 <div class="titlepage">
461 <div>
462 <div>
463 <h2 class="title" style="clear: both"><a name="gfdl-8"></a>A.9.&nbsp;TRANSLATION
464 </h2>
465 </div>
466 </div>
467 </div>
468 <p>Translation is considered a kind of modification, so you may
469 distribute translations of the Document under the terms of section 4.
470 Replacing Invariant Sections with translations requires special
471 permission from their copyright holders, but you may include
472 translations of some or all Invariant Sections in addition to the
473 original versions of these Invariant Sections. You may include a
474 translation of this License, and all the license notices in the
475 Document, and any Warranty Disclaimers, provided that you also include
476 the original English version of this License and the original versions
477 of those notices and disclaimers. In case of a disagreement between the
478 translation and the original version of this License or a notice or
479 disclaimer, the original version will prevail.
480 </p>
481 <p>If a section in the Document is Entitled "Acknowledgements",
482 "Dedications", or "History", the requirement (section 4) to Preserve its
483 Title (section 1) will typically require changing the actual
484 title.
485 </p>
486 </div>
487 <div class="section" lang="en">
488 <div class="titlepage">
489 <div>
490 <div>
491 <h2 class="title" style="clear: both"><a name="gfdl-9"></a>A.10.&nbsp;TERMINATION
492 </h2>
493 </div>
494 </div>
495 </div>
496 <p>You may not copy, modify, sublicense, or distribute the Document
497 except as expressly provided for under this License. Any other attempt
498 to copy, modify, sublicense or distribute the Document is void, and will
499 automatically terminate your rights under this License. However,
500 parties who have received copies, or rights, from you under this License
501 will not have their licenses terminated so long as such parties remain
502 in full compliance.
503 </p>
504 </div>
505 <div class="section" lang="en">
506 <div class="titlepage">
507 <div>
508 <div>
509 <h2 class="title" style="clear: both"><a name="gfdl-10"></a>A.11.&nbsp;FUTURE REVISIONS OF THIS LICENSE
510 </h2>
511 </div>
512 </div>
513 </div>
514 <p>The Free Software Foundation may publish new, revised versions of
515 the GNU Free Documentation License from time to time. Such new versions
516 will be similar in spirit to the present version, but may differ in
517 detail to address new problems or concerns. See
518 http://www.gnu.org/copyleft/.
519 </p>
520 <p>Each version of the License is given a distinguishing version
521 number. If the Document specifies that a particular numbered version of
522 this License "or any later version" applies to it, you have the option
523 of following the terms and conditions either of that specified version
524 or of any later version that has been published (not as a draft) by the
525 Free Software Foundation. If the Document does not specify a version
526 number of this License, you may choose any version ever published (not
527 as a draft) by the Free Software Foundation.
528 </p>
529 </div>
530 <div class="section" lang="en">
531 <div class="titlepage">
532 <div>
533 <div>
534 <h2 class="title" style="clear: both"><a name="gfdl-addendum"></a>A.12.&nbsp;ADDENDUM: How to use this License for your documents
535 </h2>
536 </div>
537 </div>
538 </div>
539 <p>To use this License in a document you have written, include a copy
540 of the License in the document and put the following copyright and
541 license notices just after the title page:
542 </p>
543 <div class="blockquote"><a name="copyright-sample"></a><blockquote class="blockquote">
544 <div class="blockquote-title">
545 <p><b>Sample Invariant Sections list</b></p>
546 </div>
547 <p>
548 Copyright (c) YEAR YOUR NAME.
549 Permission is granted to copy, distribute and/or modify this document
550 under the terms of the GNU Free Documentation License, Version 1.2
551 or any later version published by the Free Software Foundation;
552 with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
553 A copy of the license is included in the section entitled "GNU
554 Free Documentation License".
555
556 </p>
557 </blockquote>
558 </div>
559 <p>If you have Invariant Sections, Front-Cover Texts and Back-Cover
560 Texts, replace the "with...Texts." line with this:
561 </p>
562 <div class="blockquote"><a name="inv-cover-sample"></a><blockquote class="blockquote">
563 <div class="blockquote-title">
564 <p><b>Sample Invariant Sections list</b></p>
565 </div>
566 <p>
567 with the Invariant Sections being LIST THEIR TITLES, with the
568 Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
569
570 </p>
571 </blockquote>
572 </div>
573 <p>If you have Invariant Sections without Cover Texts, or some other
574 combination of the three, merge those two alternatives to suit the
575 situation.
576 </p>
577 <p>If your document contains nontrivial examples of program code, we
578 recommend releasing these examples in parallel under your choice of free
579 software license, such as the GNU General Public License, to permit
580 their use in free software.
581 </p>
582 </div>
583 </div>
584 <div class="navfooter">
585 <hr>
586 <table width="100%" summary="Navigation footer">
587 <tr>
588 <td width="40%" align="left"><a accesskey="p" href="sylpheed-faq-3.html">Prev</a>&nbsp;
589 </td>
590 <td width="20%" align="center">&nbsp;</td>
591 <td width="40%" align="right">&nbsp;</td>
592 </tr>
593 <tr>
594 <td width="40%" align="left" valign="top">Chapter&nbsp;3.&nbsp;Sylpheed FAQ - Interface&nbsp;</td>
595 <td width="20%" align="center"><a accesskey="h" href="sylpheed-faq.html">Home</a></td>
596 <td width="40%" align="right" valign="top">&nbsp;</td>
597 </tr>
598 </table>
599 </div>
600 </body>
601</html> \ No newline at end of file
diff --git a/faq/en/sylpheed-faq.html b/faq/en/sylpheed-faq.html
new file mode 100644
index 0000000..eada76e
--- /dev/null
+++ b/faq/en/sylpheed-faq.html
@@ -0,0 +1,161 @@
1<html>
2 <head>
3 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4
5 <title>Sylpheed FAQ</title>
6 <meta name="generator" content="DocBook XSL Stylesheets V1.68.1">
7 <meta name="description" content="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.">
8 <link rel="start" href="sylpheed-faq.html" title="Sylpheed FAQ">
9 <link rel="next" href="sylpheed-faq-1.html" title="Chapter&nbsp;1.&nbsp;Sylpheed FAQ - General Information">
10 <link rel="chapter" href="sylpheed-faq-1.html" title="Chapter&nbsp;1.&nbsp;Sylpheed FAQ - General Information">
11 <link rel="chapter" href="sylpheed-faq-2.html" title="Chapter&nbsp;2.&nbsp;Sylpheed FAQ - Installation and Configuration">
12 <link rel="chapter" href="sylpheed-faq-3.html" title="Chapter&nbsp;3.&nbsp;Sylpheed FAQ - Interface">
13 <link rel="appendix" href="sylpheed-faq-4.html" title="Appendix&nbsp;A.&nbsp;GNU Free Documentation License"><style type="text/css">
14pre.programlisting, pre.screen {
15background-color : #e0e0e0;
16padding : 0.2cm;
17}
18.question {
19font-weight : bold;
20}
21
22</style></head>
23 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
24 <div class="navheader">
25 <table width="100%" summary="Navigation header">
26 <tr>
27 <th colspan="3" align="center">Sylpheed FAQ</th>
28 </tr>
29 <tr>
30 <td width="20%" align="left">&nbsp;</td>
31 <th width="60%" align="center">&nbsp;</th>
32 <td width="20%" align="right">&nbsp;<a accesskey="n" href="sylpheed-faq-1.html">Next</a></td>
33 </tr>
34 </table>
35 <hr>
36 </div>
37 <div class="book" lang="en">
38 <div class="titlepage">
39 <div>
40 <div>
41 <h1 class="title"><a name="d0e1"></a>Sylpheed FAQ
42 </h1>
43 </div>
44 <div>
45 <div class="author">
46 <h3 class="author"><span class="firstname">Paul</span> <span class="surname">Kater</span></h3>
47 </div>
48 </div>
49 <div>
50 <div class="author">
51 <h3 class="author"><span class="firstname">Jens</span> <span class="surname">Oberender</span></h3>
52 </div>
53 </div>
54 <div>
55 <div class="author">
56 <h3 class="author"><span class="firstname">Francois</span> <span class="surname">Barriere</span></h3>
57 </div>
58 </div>
59 <div>
60 <div class="author">
61 <h3 class="author"><span class="firstname">Olivier</span> <span class="surname">Delhomme</span></h3>
62 </div>
63 </div>
64 <div>
65 <div class="author">
66 <h3 class="author"><span class="firstname">Petr</span> <span class="surname">Kovar</span></h3>
67 </div>
68 </div>
69 <div>
70 <p class="copyright">Copyright &copy; 2010 The Sylpheed Documentation Project.</p>
71 </div>
72 <div>
73 <div class="legalnotice"><a name="d0e13"></a><p>Permission is granted to copy, distribute and/or modify this
74 document under the terms of the GNU Free Documentation License, Version
75 1.2 or any later version published by the Free Software Foundation; with
76 no Invariant Sections, with no Front-Cover Texts, and no Back-Cover
77 Texts. A copy of the license is included in the section entitled "GNU
78 Free Documentation License".
79
80 </p>
81 </div>
82 </div>
83 <div>
84 <div class="revhistory">
85 <table border="1" width="100%" summary="Revision history">
86 <tr>
87 <th align="left" valign="top" colspan="3"><b>Revision History</b></th>
88 </tr>
89 <tr>
90 <td align="left">Revision 1.9</td>
91 <td align="left">2005/07/08</td>
92 <td align="left">OD</td>
93 </tr>
94 <tr>
95 <td align="left" colspan="3">Ported to DocBook XML.</td>
96 </tr>
97 <tr>
98 <td align="left">Revision 2.0</td>
99 <td align="left">2009/10/02</td>
100 <td align="left">PK</td>
101 </tr>
102 <tr>
103 <td align="left" colspan="3">Finished porting to DocBook XML, updated many questions across the document to conform with Sylpheed 2.7.1.</td>
104 </tr>
105 <tr>
106 <td align="left">Revision 2.1</td>
107 <td align="left">2010/04/14</td>
108 <td align="left">PK</td>
109 </tr>
110 <tr>
111 <td align="left" colspan="3">Updated with regard to Sylpheed 3.0.2.</td>
112 </tr>
113 <tr>
114 <td align="left">Revision 2.2</td>
115 <td align="left">2010/08/09</td>
116 <td align="left">PK</td>
117 </tr>
118 <tr>
119 <td align="left" colspan="3">Updates for the upcoming Sylpheed 3.1.</td>
120 </tr>
121 </table>
122 </div>
123 </div>
124 <div>
125 <div class="abstract">
126 <p class="title"><b>Abstract</b></p>
127 <p>This document contains answers to various questions, which are frequently asked by Sylpheed users. It consists of three sections
128 providing general information, information on Sylpheed installation and configuration, and on Sylpheed interface.
129 </p>
130 </div>
131 </div>
132 </div>
133 <hr>
134 </div>
135 <div class="toc">
136 <p><b>Table of Contents</b></p>
137 <dl>
138 <dt><span class="chapter"><a href="sylpheed-faq-1.html">1. Sylpheed FAQ - General Information</a></span></dt>
139 <dt><span class="chapter"><a href="sylpheed-faq-2.html">2. Sylpheed FAQ - Installation and Configuration</a></span></dt>
140 <dt><span class="chapter"><a href="sylpheed-faq-3.html">3. Sylpheed FAQ - Interface</a></span></dt>
141 <dt><span class="appendix"><a href="sylpheed-faq-4.html">A. GNU Free Documentation License</a></span></dt>
142 </dl>
143 </div>
144 </div>
145 <div class="navfooter">
146 <hr>
147 <table width="100%" summary="Navigation footer">
148 <tr>
149 <td width="40%" align="left">&nbsp;</td>
150 <td width="20%" align="center">&nbsp;</td>
151 <td width="40%" align="right">&nbsp;<a accesskey="n" href="sylpheed-faq-1.html">Next</a></td>
152 </tr>
153 <tr>
154 <td width="40%" align="left" valign="top">&nbsp;</td>
155 <td width="20%" align="center">&nbsp;</td>
156 <td width="40%" align="right" valign="top">&nbsp;Chapter&nbsp;1.&nbsp;Sylpheed FAQ - General Information</td>
157 </tr>
158 </table>
159 </div>
160 </body>
161</html> \ No newline at end of file
generated by cgit v1.3 (git 2.53.0) at 2026-09-26 20:52:52 +0000