From 0b3cbf57875fd692e4ba0b336fefa4bee1ed00dc Mon Sep 17 00:00:00 2001 From: Simeon Simeonov Date: Mon, 26 Feb 2018 11:23:00 +0100 Subject: Initial commit for sylpheed 3.7.0 --- faq/GFDL-1.2 | 397 +++++++++++++++++++ faq/Makefile.am | 3 + faq/Makefile.in | 669 +++++++++++++++++++++++++++++++ faq/de/Makefile.am | 11 + faq/de/Makefile.in | 552 ++++++++++++++++++++++++++ faq/de/sylpheed-faq-1.html | 221 +++++++++++ faq/de/sylpheed-faq-2.html | 125 ++++++ faq/de/sylpheed-faq-3.html | 107 +++++ faq/de/sylpheed-faq.html | 103 +++++ faq/en/COPYING | 397 +++++++++++++++++++ faq/en/ChangeLog | 92 +++++ faq/en/LICENSE | 9 + faq/en/Makefile.am | 18 + faq/en/Makefile.in | 560 ++++++++++++++++++++++++++ faq/en/NEWS | 137 +++++++ faq/en/faq.xml | 94 +++++ faq/en/faq_001.xml | 591 +++++++++++++++++++++++++++ faq/en/faq_002.xml | 606 ++++++++++++++++++++++++++++ faq/en/faq_003.xml | 309 +++++++++++++++ faq/en/fdl.xml | 383 ++++++++++++++++++ faq/en/sylpheed-faq-1.html | 964 +++++++++++++++++++++++++++++++++++++++++++++ faq/en/sylpheed-faq-2.html | 913 ++++++++++++++++++++++++++++++++++++++++++ faq/en/sylpheed-faq-3.html | 432 ++++++++++++++++++++ faq/en/sylpheed-faq-4.html | 601 ++++++++++++++++++++++++++++ faq/en/sylpheed-faq.html | 161 ++++++++ faq/es/Makefile.am | 11 + faq/es/Makefile.in | 552 ++++++++++++++++++++++++++ faq/es/sylpheed-faq-1.html | 241 ++++++++++++ faq/es/sylpheed-faq-2.html | 125 ++++++ faq/es/sylpheed-faq-3.html | 124 ++++++ faq/es/sylpheed-faq.html | 98 +++++ faq/fr/Makefile.am | 11 + faq/fr/Makefile.in | 552 ++++++++++++++++++++++++++ faq/fr/sylpheed-faq-1.html | 269 +++++++++++++ faq/fr/sylpheed-faq-2.html | 140 +++++++ faq/fr/sylpheed-faq-3.html | 120 ++++++ faq/fr/sylpheed-faq.html | 104 +++++ faq/it/Makefile.am | 11 + faq/it/Makefile.in | 552 ++++++++++++++++++++++++++ faq/it/sylpheed-faq-1.html | 227 +++++++++++ faq/it/sylpheed-faq-2.html | 142 +++++++ faq/it/sylpheed-faq-3.html | 111 ++++++ faq/it/sylpheed-faq.html | 103 +++++ 43 files changed, 11948 insertions(+) create mode 100644 faq/GFDL-1.2 create mode 100644 faq/Makefile.am create mode 100644 faq/Makefile.in create mode 100644 faq/de/Makefile.am create mode 100644 faq/de/Makefile.in create mode 100644 faq/de/sylpheed-faq-1.html create mode 100644 faq/de/sylpheed-faq-2.html create mode 100644 faq/de/sylpheed-faq-3.html create mode 100644 faq/de/sylpheed-faq.html create mode 100644 faq/en/COPYING create mode 100644 faq/en/ChangeLog create mode 100644 faq/en/LICENSE create mode 100644 faq/en/Makefile.am create mode 100644 faq/en/Makefile.in create mode 100644 faq/en/NEWS create mode 100644 faq/en/faq.xml create mode 100644 faq/en/faq_001.xml create mode 100644 faq/en/faq_002.xml create mode 100644 faq/en/faq_003.xml create mode 100644 faq/en/fdl.xml create mode 100644 faq/en/sylpheed-faq-1.html create mode 100644 faq/en/sylpheed-faq-2.html create mode 100644 faq/en/sylpheed-faq-3.html create mode 100644 faq/en/sylpheed-faq-4.html create mode 100644 faq/en/sylpheed-faq.html create mode 100644 faq/es/Makefile.am create mode 100644 faq/es/Makefile.in create mode 100644 faq/es/sylpheed-faq-1.html create mode 100644 faq/es/sylpheed-faq-2.html create mode 100644 faq/es/sylpheed-faq-3.html create mode 100644 faq/es/sylpheed-faq.html create mode 100644 faq/fr/Makefile.am create mode 100644 faq/fr/Makefile.in create mode 100644 faq/fr/sylpheed-faq-1.html create mode 100644 faq/fr/sylpheed-faq-2.html create mode 100644 faq/fr/sylpheed-faq-3.html create mode 100644 faq/fr/sylpheed-faq.html create mode 100644 faq/it/Makefile.am create mode 100644 faq/it/Makefile.in create mode 100644 faq/it/sylpheed-faq-1.html create mode 100644 faq/it/sylpheed-faq-2.html create mode 100644 faq/it/sylpheed-faq-3.html create mode 100644 faq/it/sylpheed-faq.html (limited to 'faq') diff --git a/faq/GFDL-1.2 b/faq/GFDL-1.2 new file mode 100644 index 0000000..4a0fe1c --- /dev/null +++ b/faq/GFDL-1.2 @@ -0,0 +1,397 @@ + GNU Free Documentation License + Version 1.2, November 2002 + + + Copyright (C) 2000,2001,2002 Free Software Foundation, Inc. + 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + +0. PREAMBLE + +The purpose of this License is to make a manual, textbook, or other +functional and useful document "free" in the sense of freedom: to +assure everyone the effective freedom to copy and redistribute it, +with or without modifying it, either commercially or noncommercially. +Secondarily, this License preserves for the author and publisher a way +to get credit for their work, while not being considered responsible +for modifications made by others. + +This License is a kind of "copyleft", which means that derivative +works of the document must themselves be free in the same sense. It +complements the GNU General Public License, which is a copyleft +license designed for free software. + +We have designed this License in order to use it for manuals for free +software, because free software needs free documentation: a free +program should come with manuals providing the same freedoms that the +software does. But this License is not limited to software manuals; +it can be used for any textual work, regardless of subject matter or +whether it is published as a printed book. We recommend this License +principally for works whose purpose is instruction or reference. + + +1. APPLICABILITY AND DEFINITIONS + +This License applies to any manual or other work, in any medium, that +contains a notice placed by the copyright holder saying it can be +distributed under the terms of this License. Such a notice grants a +world-wide, royalty-free license, unlimited in duration, to use that +work under the conditions stated herein. The "Document", below, +refers to any such manual or work. Any member of the public is a +licensee, and is addressed as "you". You accept the license if you +copy, modify or distribute the work in a way requiring permission +under copyright law. + +A "Modified Version" of the Document means any work containing the +Document or a portion of it, either copied verbatim, or with +modifications and/or translated into another language. + +A "Secondary Section" is a named appendix or a front-matter section of +the Document that deals exclusively with the relationship of the +publishers or authors of the Document to the Document's overall subject +(or to related matters) and contains nothing that could fall directly +within that overall subject. (Thus, if the Document is in part a +textbook of mathematics, a Secondary Section may not explain any +mathematics.) The relationship could be a matter of historical +connection with the subject or with related matters, or of legal, +commercial, philosophical, ethical or political position regarding +them. + +The "Invariant Sections" are certain Secondary Sections whose titles +are designated, as being those of Invariant Sections, in the notice +that says that the Document is released under this License. If a +section does not fit the above definition of Secondary then it is not +allowed to be designated as Invariant. The Document may contain zero +Invariant Sections. If the Document does not identify any Invariant +Sections then there are none. + +The "Cover Texts" are certain short passages of text that are listed, +as Front-Cover Texts or Back-Cover Texts, in the notice that says that +the Document is released under this License. A Front-Cover Text may +be at most 5 words, and a Back-Cover Text may be at most 25 words. + +A "Transparent" copy of the Document means a machine-readable copy, +represented in a format whose specification is available to the +general public, that is suitable for revising the document +straightforwardly with generic text editors or (for images composed of +pixels) generic paint programs or (for drawings) some widely available +drawing editor, and that is suitable for input to text formatters or +for automatic translation to a variety of formats suitable for input +to text formatters. A copy made in an otherwise Transparent file +format whose markup, or absence of markup, has been arranged to thwart +or discourage subsequent modification by readers is not Transparent. +An image format is not Transparent if used for any substantial amount +of text. A copy that is not "Transparent" is called "Opaque". + +Examples of suitable formats for Transparent copies include plain +ASCII without markup, Texinfo input format, LaTeX input format, SGML +or XML using a publicly available DTD, and standard-conforming simple +HTML, PostScript or PDF designed for human modification. Examples of +transparent image formats include PNG, XCF and JPG. Opaque formats +include proprietary formats that can be read and edited only by +proprietary word processors, SGML or XML for which the DTD and/or +processing tools are not generally available, and the +machine-generated HTML, PostScript or PDF produced by some word +processors for output purposes only. + +The "Title Page" means, for a printed book, the title page itself, +plus such following pages as are needed to hold, legibly, the material +this License requires to appear in the title page. For works in +formats which do not have any title page as such, "Title Page" means +the text near the most prominent appearance of the work's title, +preceding the beginning of the body of the text. + +A section "Entitled XYZ" means a named subunit of the Document whose +title either is precisely XYZ or contains XYZ in parentheses following +text that translates XYZ in another language. (Here XYZ stands for a +specific section name mentioned below, such as "Acknowledgements", +"Dedications", "Endorsements", or "History".) To "Preserve the Title" +of such a section when you modify the Document means that it remains a +section "Entitled XYZ" according to this definition. + +The Document may include Warranty Disclaimers next to the notice which +states that this License applies to the Document. These Warranty +Disclaimers are considered to be included by reference in this +License, but only as regards disclaiming warranties: any other +implication that these Warranty Disclaimers may have is void and has +no effect on the meaning of this License. + + +2. VERBATIM COPYING + +You may copy and distribute the Document in any medium, either +commercially or noncommercially, provided that this License, the +copyright notices, and the license notice saying this License applies +to the Document are reproduced in all copies, and that you add no other +conditions whatsoever to those of this License. You may not use +technical measures to obstruct or control the reading or further +copying of the copies you make or distribute. However, you may accept +compensation in exchange for copies. If you distribute a large enough +number of copies you must also follow the conditions in section 3. + +You may also lend copies, under the same conditions stated above, and +you may publicly display copies. + + +3. COPYING IN QUANTITY + +If you publish printed copies (or copies in media that commonly have +printed covers) of the Document, numbering more than 100, and the +Document's license notice requires Cover Texts, you must enclose the +copies in covers that carry, clearly and legibly, all these Cover +Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on +the back cover. Both covers must also clearly and legibly identify +you as the publisher of these copies. The front cover must present +the full title with all words of the title equally prominent and +visible. You may add other material on the covers in addition. +Copying with changes limited to the covers, as long as they preserve +the title of the Document and satisfy these conditions, can be treated +as verbatim copying in other respects. + +If the required texts for either cover are too voluminous to fit +legibly, you should put the first ones listed (as many as fit +reasonably) on the actual cover, and continue the rest onto adjacent +pages. + +If you publish or distribute Opaque copies of the Document numbering +more than 100, you must either include a machine-readable Transparent +copy along with each Opaque copy, or state in or with each Opaque copy +a computer-network location from which the general network-using +public has access to download using public-standard network protocols +a complete Transparent copy of the Document, free of added material. +If you use the latter option, you must take reasonably prudent steps, +when you begin distribution of Opaque copies in quantity, to ensure +that this Transparent copy will remain thus accessible at the stated +location until at least one year after the last time you distribute an +Opaque copy (directly or through your agents or retailers) of that +edition to the public. + +It is requested, but not required, that you contact the authors of the +Document well before redistributing any large number of copies, to give +them a chance to provide you with an updated version of the Document. + + +4. MODIFICATIONS + +You may copy and distribute a Modified Version of the Document under +the conditions of sections 2 and 3 above, provided that you release +the Modified Version under precisely this License, with the Modified +Version filling the role of the Document, thus licensing distribution +and modification of the Modified Version to whoever possesses a copy +of it. In addition, you must do these things in the Modified Version: + +A. Use in the Title Page (and on the covers, if any) a title distinct + from that of the Document, and from those of previous versions + (which should, if there were any, be listed in the History section + of the Document). You may use the same title as a previous version + if the original publisher of that version gives permission. +B. List on the Title Page, as authors, one or more persons or entities + responsible for authorship of the modifications in the Modified + Version, together with at least five of the principal authors of the + Document (all of its principal authors, if it has fewer than five), + unless they release you from this requirement. +C. State on the Title page the name of the publisher of the + Modified Version, as the publisher. +D. Preserve all the copyright notices of the Document. +E. Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. +F. Include, immediately after the copyright notices, a license notice + giving the public permission to use the Modified Version under the + terms of this License, in the form shown in the Addendum below. +G. Preserve in that license notice the full lists of Invariant Sections + and required Cover Texts given in the Document's license notice. +H. Include an unaltered copy of this License. +I. Preserve the section Entitled "History", Preserve its Title, and add + to it an item stating at least the title, year, new authors, and + publisher of the Modified Version as given on the Title Page. If + there is no section Entitled "History" in the Document, create one + stating the title, year, authors, and publisher of the Document as + given on its Title Page, then add an item describing the Modified + Version as stated in the previous sentence. +J. Preserve the network location, if any, given in the Document for + public access to a Transparent copy of the Document, and likewise + the network locations given in the Document for previous versions + it was based on. These may be placed in the "History" section. + You may omit a network location for a work that was published at + least four years before the Document itself, or if the original + publisher of the version it refers to gives permission. +K. For any section Entitled "Acknowledgements" or "Dedications", + Preserve the Title of the section, and preserve in the section all + the substance and tone of each of the contributor acknowledgements + and/or dedications given therein. +L. Preserve all the Invariant Sections of the Document, + unaltered in their text and in their titles. Section numbers + or the equivalent are not considered part of the section titles. +M. Delete any section Entitled "Endorsements". Such a section + may not be included in the Modified Version. +N. Do not retitle any existing section to be Entitled "Endorsements" + or to conflict in title with any Invariant Section. +O. Preserve any Warranty Disclaimers. + +If the Modified Version includes new front-matter sections or +appendices that qualify as Secondary Sections and contain no material +copied from the Document, you may at your option designate some or all +of these sections as invariant. To do this, add their titles to the +list of Invariant Sections in the Modified Version's license notice. +These titles must be distinct from any other section titles. + +You may add a section Entitled "Endorsements", provided it contains +nothing but endorsements of your Modified Version by various +parties--for example, statements of peer review or that the text has +been approved by an organization as the authoritative definition of a +standard. + +You may add a passage of up to five words as a Front-Cover Text, and a +passage of up to 25 words as a Back-Cover Text, to the end of the list +of Cover Texts in the Modified Version. Only one passage of +Front-Cover Text and one of Back-Cover Text may be added by (or +through arrangements made by) any one entity. If the Document already +includes a cover text for the same cover, previously added by you or +by arrangement made by the same entity you are acting on behalf of, +you may not add another; but you may replace the old one, on explicit +permission from the previous publisher that added the old one. + +The author(s) and publisher(s) of the Document do not by this License +give permission to use their names for publicity for or to assert or +imply endorsement of any Modified Version. + + +5. COMBINING DOCUMENTS + +You may combine the Document with other documents released under this +License, under the terms defined in section 4 above for modified +versions, provided that you include in the combination all of the +Invariant Sections of all of the original documents, unmodified, and +list them all as Invariant Sections of your combined work in its +license notice, and that you preserve all their Warranty Disclaimers. + +The combined work need only contain one copy of this License, and +multiple identical Invariant Sections may be replaced with a single +copy. If there are multiple Invariant Sections with the same name but +different contents, make the title of each such section unique by +adding at the end of it, in parentheses, the name of the original +author or publisher of that section if known, or else a unique number. +Make the same adjustment to the section titles in the list of +Invariant Sections in the license notice of the combined work. + +In the combination, you must combine any sections Entitled "History" +in the various original documents, forming one section Entitled +"History"; likewise combine any sections Entitled "Acknowledgements", +and any sections Entitled "Dedications". You must delete all sections +Entitled "Endorsements". + + +6. COLLECTIONS OF DOCUMENTS + +You may make a collection consisting of the Document and other documents +released under this License, and replace the individual copies of this +License in the various documents with a single copy that is included in +the collection, provided that you follow the rules of this License for +verbatim copying of each of the documents in all other respects. + +You may extract a single document from such a collection, and distribute +it individually under this License, provided you insert a copy of this +License into the extracted document, and follow this License in all +other respects regarding verbatim copying of that document. + + +7. AGGREGATION WITH INDEPENDENT WORKS + +A compilation of the Document or its derivatives with other separate +and independent documents or works, in or on a volume of a storage or +distribution medium, is called an "aggregate" if the copyright +resulting from the compilation is not used to limit the legal rights +of the compilation's users beyond what the individual works permit. +When the Document is included in an aggregate, this License does not +apply to the other works in the aggregate which are not themselves +derivative works of the Document. + +If the Cover Text requirement of section 3 is applicable to these +copies of the Document, then if the Document is less than one half of +the entire aggregate, the Document's Cover Texts may be placed on +covers that bracket the Document within the aggregate, or the +electronic equivalent of covers if the Document is in electronic form. +Otherwise they must appear on printed covers that bracket the whole +aggregate. + + +8. TRANSLATION + +Translation is considered a kind of modification, so you may +distribute translations of the Document under the terms of section 4. +Replacing Invariant Sections with translations requires special +permission from their copyright holders, but you may include +translations of some or all Invariant Sections in addition to the +original versions of these Invariant Sections. You may include a +translation of this License, and all the license notices in the +Document, and any Warranty Disclaimers, provided that you also include +the original English version of this License and the original versions +of those notices and disclaimers. In case of a disagreement between +the translation and the original version of this License or a notice +or disclaimer, the original version will prevail. + +If a section in the Document is Entitled "Acknowledgements", +"Dedications", or "History", the requirement (section 4) to Preserve +its Title (section 1) will typically require changing the actual +title. + + +9. TERMINATION + +You may not copy, modify, sublicense, or distribute the Document except +as expressly provided for under this License. Any other attempt to +copy, modify, sublicense or distribute the Document is void, and will +automatically terminate your rights under this License. However, +parties who have received copies, or rights, from you under this +License will not have their licenses terminated so long as such +parties remain in full compliance. + + +10. FUTURE REVISIONS OF THIS LICENSE + +The Free Software Foundation may publish new, revised versions +of the GNU Free Documentation License from time to time. Such new +versions will be similar in spirit to the present version, but may +differ in detail to address new problems or concerns. See +http://www.gnu.org/copyleft/. + +Each version of the License is given a distinguishing version number. +If the Document specifies that a particular numbered version of this +License "or any later version" applies to it, you have the option of +following the terms and conditions either of that specified version or +of any later version that has been published (not as a draft) by the +Free Software Foundation. If the Document does not specify a version +number of this License, you may choose any version ever published (not +as a draft) by the Free Software Foundation. + + +ADDENDUM: How to use this License for your documents + +To use this License in a document you have written, include a copy of +the License in the document and put the following copyright and +license notices just after the title page: + + Copyright (c) YEAR YOUR NAME. + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.2 + or any later version published by the Free Software Foundation; + with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. + A copy of the license is included in the section entitled "GNU + Free Documentation License". + +If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, +replace the "with...Texts." line with this: + + with the Invariant Sections being LIST THEIR TITLES, with the + Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. + +If you have Invariant Sections without Cover Texts, or some other +combination of the three, merge those two alternatives to suit the +situation. + +If your document contains nontrivial examples of program code, we +recommend releasing these examples in parallel under your choice of +free software license, such as the GNU General Public License, +to permit their use in free software. diff --git a/faq/Makefile.am b/faq/Makefile.am new file mode 100644 index 0000000..82fa200 --- /dev/null +++ b/faq/Makefile.am @@ -0,0 +1,3 @@ +SUBDIRS = de en es fr it + +EXTRA_DIST = GFDL-1.2 diff --git a/faq/Makefile.in b/faq/Makefile.in new file mode 100644 index 0000000..b869309 --- /dev/null +++ b/faq/Makefile.in @@ -0,0 +1,669 @@ +# Makefile.in generated by automake 1.14.1 from Makefile.am. +# @configure_input@ + +# Copyright (C) 1994-2013 Free Software Foundation, Inc. + +# This Makefile.in is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY, to the extent permitted by law; without +# even the implied warranty of MERCHANTABILITY or FITNESS FOR A +# PARTICULAR PURPOSE. + +@SET_MAKE@ +VPATH = @srcdir@ +am__is_gnu_make = test -n '$(MAKEFILE_LIST)' && test -n '$(MAKELEVEL)' +am__make_running_with_option = \ + case $${target_option-} in \ + ?) ;; \ + *) echo "am__make_running_with_option: internal error: invalid" \ + "target option '$${target_option-}' specified" >&2; \ + exit 1;; \ + esac; \ + has_opt=no; \ + sane_makeflags=$$MAKEFLAGS; \ + if $(am__is_gnu_make); then \ + sane_makeflags=$$MFLAGS; \ + else \ + case $$MAKEFLAGS in \ + *\\[\ \ ]*) \ + bs=\\; \ + sane_makeflags=`printf '%s\n' "$$MAKEFLAGS" \ + | sed "s/$$bs$$bs[$$bs $$bs ]*//g"`;; \ + esac; \ + fi; \ + skip_next=no; \ + strip_trailopt () \ + { \ + flg=`printf '%s\n' "$$flg" | sed "s/$$1.*$$//"`; \ + }; \ + for flg in $$sane_makeflags; do \ + test $$skip_next = yes && { skip_next=no; continue; }; \ + case $$flg in \ + *=*|--*) continue;; \ + -*I) strip_trailopt 'I'; skip_next=yes;; \ + -*I?*) strip_trailopt 'I';; \ + -*O) strip_trailopt 'O'; skip_next=yes;; \ + -*O?*) strip_trailopt 'O';; \ + -*l) strip_trailopt 'l'; skip_next=yes;; \ + -*l?*) strip_trailopt 'l';; \ + -[dEDm]) skip_next=yes;; \ + -[JT]) skip_next=yes;; \ + esac; \ + case $$flg in \ + *$$target_option*) has_opt=yes; break;; \ + esac; \ + done; \ + test $$has_opt = yes +am__make_dryrun = (target_option=n; $(am__make_running_with_option)) +am__make_keepgoing = (target_option=k; $(am__make_running_with_option)) +pkgdatadir = $(datadir)/@PACKAGE@ +pkgincludedir = $(includedir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkglibexecdir = $(libexecdir)/@PACKAGE@ +am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd +install_sh_DATA = $(install_sh) -c -m 644 +install_sh_PROGRAM = $(install_sh) -c +install_sh_SCRIPT = $(install_sh) -c +INSTALL_HEADER = $(INSTALL_DATA) +transform = $(program_transform_name) +NORMAL_INSTALL = : +PRE_INSTALL = : +POST_INSTALL = : +NORMAL_UNINSTALL = : +PRE_UNINSTALL = : +POST_UNINSTALL = : +build_triplet = @build@ +host_triplet = @host@ +target_triplet = @target@ +subdir = faq +DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/Makefile.am \ + $(top_srcdir)/mkinstalldirs +ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 +am__aclocal_m4_deps = $(top_srcdir)/ac/aclocal-include.m4 \ + $(top_srcdir)/ac/gnupg-check-typedef.m4 \ + $(top_srcdir)/configure.ac +am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ + $(ACLOCAL_M4) +mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs +CONFIG_HEADER = $(top_builddir)/config.h +CONFIG_CLEAN_FILES = +CONFIG_CLEAN_VPATH_FILES = +AM_V_P = $(am__v_P_@AM_V@) +am__v_P_ = $(am__v_P_@AM_DEFAULT_V@) +am__v_P_0 = false +am__v_P_1 = : +AM_V_GEN = $(am__v_GEN_@AM_V@) +am__v_GEN_ = $(am__v_GEN_@AM_DEFAULT_V@) +am__v_GEN_0 = @echo " GEN " $@; +am__v_GEN_1 = +AM_V_at = $(am__v_at_@AM_V@) +am__v_at_ = $(am__v_at_@AM_DEFAULT_V@) +am__v_at_0 = @ +am__v_at_1 = +SOURCES = +DIST_SOURCES = +RECURSIVE_TARGETS = all-recursive check-recursive cscopelist-recursive \ + ctags-recursive dvi-recursive html-recursive info-recursive \ + install-data-recursive install-dvi-recursive \ + install-exec-recursive install-html-recursive \ + install-info-recursive install-pdf-recursive \ + install-ps-recursive install-recursive installcheck-recursive \ + installdirs-recursive pdf-recursive ps-recursive \ + tags-recursive uninstall-recursive +am__can_run_installinfo = \ + case $$AM_UPDATE_INFO_DIR in \ + n|no|NO) false;; \ + *) (install-info --version) >/dev/null 2>&1;; \ + esac +RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive \ + distclean-recursive maintainer-clean-recursive +am__recursive_targets = \ + $(RECURSIVE_TARGETS) \ + $(RECURSIVE_CLEAN_TARGETS) \ + $(am__extra_recursive_targets) +AM_RECURSIVE_TARGETS = $(am__recursive_targets:-recursive=) TAGS CTAGS \ + distdir +am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) $(LISP) +# Read a list of newline-separated strings from the standard input, +# and print each of them once, without duplicates. Input order is +# *not* preserved. +am__uniquify_input = $(AWK) '\ + BEGIN { nonempty = 0; } \ + { items[$$0] = 1; nonempty = 1; } \ + END { if (nonempty) { for (i in items) print i; }; } \ +' +# Make sure the list of sources is unique. This is necessary because, +# e.g., the same source file might be shared among _SOURCES variables +# for different programs/libraries. +am__define_uniq_tagged_files = \ + list='$(am__tagged_files)'; \ + unique=`for i in $$list; do \ + if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ + done | $(am__uniquify_input)` +ETAGS = etags +CTAGS = ctags +DIST_SUBDIRS = $(SUBDIRS) +DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) +am__relativize = \ + dir0=`pwd`; \ + sed_first='s,^\([^/]*\)/.*$$,\1,'; \ + sed_rest='s,^[^/]*/*,,'; \ + sed_last='s,^.*/\([^/]*\)$$,\1,'; \ + sed_butlast='s,/*[^/]*$$,,'; \ + while test -n "$$dir1"; do \ + first=`echo "$$dir1" | sed -e "$$sed_first"`; \ + if test "$$first" != "."; then \ + if test "$$first" = ".."; then \ + dir2=`echo "$$dir0" | sed -e "$$sed_last"`/"$$dir2"; \ + dir0=`echo "$$dir0" | sed -e "$$sed_butlast"`; \ + else \ + first2=`echo "$$dir2" | sed -e "$$sed_first"`; \ + if test "$$first2" = "$$first"; then \ + dir2=`echo "$$dir2" | sed -e "$$sed_rest"`; \ + else \ + dir2="../$$dir2"; \ + fi; \ + dir0="$$dir0"/"$$first"; \ + fi; \ + fi; \ + dir1=`echo "$$dir1" | sed -e "$$sed_rest"`; \ + done; \ + reldir="$$dir2" +ACLOCAL = @ACLOCAL@ +ALLOCA = @ALLOCA@ +AMTAR = @AMTAR@ +AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@ +AR = @AR@ +AUTOCONF = @AUTOCONF@ +AUTOHEADER = @AUTOHEADER@ +AUTOMAKE = @AUTOMAKE@ +AWK = @AWK@ +BUILD_REVISION = @BUILD_REVISION@ +CATALOGS = @CATALOGS@ +CATOBJEXT = @CATOBJEXT@ +CC = @CC@ +CCDEPMODE = @CCDEPMODE@ +CFLAGS = @CFLAGS@ +CPP = @CPP@ +CPPFLAGS = @CPPFLAGS@ +CYGPATH_W = @CYGPATH_W@ +DATADIRNAME = @DATADIRNAME@ +DEFS = @DEFS@ +DEPDIR = @DEPDIR@ +DEVEL_VERSION = @DEVEL_VERSION@ +DLLTOOL = @DLLTOOL@ +DSYMUTIL = @DSYMUTIL@ +DUMPBIN = @DUMPBIN@ +ECHO_C = @ECHO_C@ +ECHO_N = @ECHO_N@ +ECHO_T = @ECHO_T@ +EGREP = @EGREP@ +EXEEXT = @EXEEXT@ +EXTRA_VERSION = @EXTRA_VERSION@ +FGREP = @FGREP@ +GETTEXT_PACKAGE = @GETTEXT_PACKAGE@ +GLIB_CFLAGS = @GLIB_CFLAGS@ +GLIB_COMPILE_RESOURCES = @GLIB_COMPILE_RESOURCES@ +GLIB_GENMARSHAL = @GLIB_GENMARSHAL@ +GLIB_LIBS = @GLIB_LIBS@ +GLIB_MKENUMS = @GLIB_MKENUMS@ +GMOFILES = @GMOFILES@ +GMSGFMT = @GMSGFMT@ +GOBJECT_QUERY = @GOBJECT_QUERY@ +GPGME_CFLAGS = @GPGME_CFLAGS@ +GPGME_CONFIG = @GPGME_CONFIG@ +GPGME_LIBS = @GPGME_LIBS@ +GREP = @GREP@ +GTK_CFLAGS = @GTK_CFLAGS@ +GTK_LIBS = @GTK_LIBS@ +INSTALL = @INSTALL@ +INSTALL_DATA = @INSTALL_DATA@ +INSTALL_PROGRAM = @INSTALL_PROGRAM@ +INSTALL_SCRIPT = @INSTALL_SCRIPT@ +INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@ +INSTOBJEXT = @INSTOBJEXT@ +INTLLIBS = @INTLLIBS@ +LD = @LD@ +LDAP_LIBS = @LDAP_LIBS@ +LDFLAGS = @LDFLAGS@ +LEX = @LEX@ +LEXLIB = @LEXLIB@ +LEX_OUTPUT_ROOT = @LEX_OUTPUT_ROOT@ +LIBICONV = @LIBICONV@ +LIBOBJS = @LIBOBJS@ +LIBS = @LIBS@ +LIBSYLPH_CFLAGS = @LIBSYLPH_CFLAGS@ +LIBSYLPH_LIBS = @LIBSYLPH_LIBS@ +LIBTOOL = @LIBTOOL@ +LIPO = @LIPO@ +LN_S = @LN_S@ +LTLIBICONV = @LTLIBICONV@ +LTLIBOBJS = @LTLIBOBJS@ +LT_AGE = @LT_AGE@ +LT_CURRENT = @LT_CURRENT@ +LT_RELEASE = @LT_RELEASE@ +LT_REVISION = @LT_REVISION@ +MAINT = @MAINT@ +MAJOR_VERSION = @MAJOR_VERSION@ +MAKEINFO = @MAKEINFO@ +MANIFEST_TOOL = @MANIFEST_TOOL@ +MICRO_VERSION = @MICRO_VERSION@ +MINOR_VERSION = @MINOR_VERSION@ +MKDIR_P = @MKDIR_P@ +MKINSTALLDIRS = @MKINSTALLDIRS@ +MSGFMT = @MSGFMT@ +MSGFMT_OPTS = @MSGFMT_OPTS@ +NM = @NM@ +NMEDIT = @NMEDIT@ +OBJDUMP = @OBJDUMP@ +OBJEXT = @OBJEXT@ +OPENSSL_CFLAGS = @OPENSSL_CFLAGS@ +OPENSSL_LIBS = @OPENSSL_LIBS@ +OTOOL = @OTOOL@ +OTOOL64 = @OTOOL64@ +PACKAGE = @PACKAGE@ +PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@ +PACKAGE_NAME = @PACKAGE_NAME@ +PACKAGE_STRING = @PACKAGE_STRING@ +PACKAGE_TARNAME = @PACKAGE_TARNAME@ +PACKAGE_URL = @PACKAGE_URL@ +PACKAGE_VERSION = @PACKAGE_VERSION@ +PATH_SEPARATOR = @PATH_SEPARATOR@ +PKG_CONFIG = @PKG_CONFIG@ +PKG_CONFIG_LIBDIR = @PKG_CONFIG_LIBDIR@ +PKG_CONFIG_PATH = @PKG_CONFIG_PATH@ +POFILES = @POFILES@ +POSUB = @POSUB@ +PO_IN_DATADIR_FALSE = @PO_IN_DATADIR_FALSE@ +PO_IN_DATADIR_TRUE = @PO_IN_DATADIR_TRUE@ +RANLIB = @RANLIB@ +SED = @SED@ +SET_MAKE = @SET_MAKE@ +SHELL = @SHELL@ +STRIP = @STRIP@ +SYLPHEED_LIBS = @SYLPHEED_LIBS@ +USE_NLS = @USE_NLS@ +VERSION = @VERSION@ +WINDRES = @WINDRES@ +XGETTEXT = @XGETTEXT@ +YACC = @YACC@ +YFLAGS = @YFLAGS@ +abs_builddir = @abs_builddir@ +abs_srcdir = @abs_srcdir@ +abs_top_builddir = @abs_top_builddir@ +abs_top_srcdir = @abs_top_srcdir@ +ac_ct_AR = @ac_ct_AR@ +ac_ct_CC = @ac_ct_CC@ +ac_ct_DUMPBIN = @ac_ct_DUMPBIN@ +am__include = @am__include@ +am__leading_dot = @am__leading_dot@ +am__quote = @am__quote@ +am__tar = @am__tar@ +am__untar = @am__untar@ +bindir = @bindir@ +build = @build@ +build_alias = @build_alias@ +build_cpu = @build_cpu@ +build_os = @build_os@ +build_vendor = @build_vendor@ +builddir = @builddir@ +datadir = @datadir@ +datarootdir = @datarootdir@ +docdir = @docdir@ +dvidir = @dvidir@ +exec_prefix = @exec_prefix@ +faqdir = @faqdir@ +host = @host@ +host_alias = @host_alias@ +host_cpu = @host_cpu@ +host_os = @host_os@ +host_vendor = @host_vendor@ +htmldir = @htmldir@ +includedir = @includedir@ +infodir = @infodir@ +install_sh = @install_sh@ +libdir = @libdir@ +libexecdir = @libexecdir@ +localedir = @localedir@ +localstatedir = @localstatedir@ +mandir = @mandir@ +manualdir = @manualdir@ +mkdir_p = @mkdir_p@ +oldincludedir = @oldincludedir@ +pdfdir = @pdfdir@ +plugindir = @plugindir@ +prefix = @prefix@ +program_transform_name = @program_transform_name@ +psdir = @psdir@ +sbindir = @sbindir@ +sharedstatedir = @sharedstatedir@ +srcdir = @srcdir@ +sysconfdir = @sysconfdir@ +target = @target@ +target_alias = @target_alias@ +target_cpu = @target_cpu@ +target_os = @target_os@ +target_vendor = @target_vendor@ +themedir = @themedir@ +top_build_prefix = @top_build_prefix@ +top_builddir = @top_builddir@ +top_srcdir = @top_srcdir@ +SUBDIRS = de en es fr it +EXTRA_DIST = GFDL-1.2 +all: all-recursive + +.SUFFIXES: +$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.am $(am__configure_deps) + @for dep in $?; do \ + case '$(am__configure_deps)' in \ + *$$dep*) \ + ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \ + && { if test -f $@; then exit 0; else break; fi; }; \ + exit 1;; \ + esac; \ + done; \ + echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign faq/Makefile'; \ + $(am__cd) $(top_srcdir) && \ + $(AUTOMAKE) --foreign faq/Makefile +.PRECIOUS: Makefile +Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status + @case '$?' in \ + *config.status*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \ + *) \ + echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \ + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \ + esac; + +$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh + +$(top_srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(am__configure_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ $(am__aclocal_m4_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(am__aclocal_m4_deps): + +mostlyclean-libtool: + -rm -f *.lo + +clean-libtool: + -rm -rf .libs _libs + +# This directory's subdirectories are mostly independent; you can cd +# into them and run 'make' without going through this Makefile. +# To change the values of 'make' variables: instead of editing Makefiles, +# (1) if the variable is set in 'config.status', edit 'config.status' +# (which will cause the Makefiles to be regenerated when you run 'make'); +# (2) otherwise, pass the desired values on the 'make' command line. +$(am__recursive_targets): + @fail=; \ + if $(am__make_keepgoing); then \ + failcom='fail=yes'; \ + else \ + failcom='exit 1'; \ + fi; \ + dot_seen=no; \ + target=`echo $@ | sed s/-recursive//`; \ + case "$@" in \ + distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \ + *) list='$(SUBDIRS)' ;; \ + esac; \ + for subdir in $$list; do \ + echo "Making $$target in $$subdir"; \ + if test "$$subdir" = "."; then \ + dot_seen=yes; \ + local_target="$$target-am"; \ + else \ + local_target="$$target"; \ + fi; \ + ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \ + || eval $$failcom; \ + done; \ + if test "$$dot_seen" = "no"; then \ + $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \ + fi; test -z "$$fail" + +ID: $(am__tagged_files) + $(am__define_uniq_tagged_files); mkid -fID $$unique +tags: tags-recursive +TAGS: tags + +tags-am: $(TAGS_DEPENDENCIES) $(am__tagged_files) + set x; \ + here=`pwd`; \ + if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \ + include_option=--etags-include; \ + empty_fix=.; \ + else \ + include_option=--include; \ + empty_fix=; \ + fi; \ + list='$(SUBDIRS)'; for subdir in $$list; do \ + if test "$$subdir" = .; then :; else \ + test ! -f $$subdir/TAGS || \ + set "$$@" "$$include_option=$$here/$$subdir/TAGS"; \ + fi; \ + done; \ + $(am__define_uniq_tagged_files); \ + shift; \ + if test -z "$(ETAGS_ARGS)$$*$$unique"; then :; else \ + test -n "$$unique" || unique=$$empty_fix; \ + if test $$# -gt 0; then \ + $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ + "$$@" $$unique; \ + else \ + $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ + $$unique; \ + fi; \ + fi +ctags: ctags-recursive + +CTAGS: ctags +ctags-am: $(TAGS_DEPENDENCIES) $(am__tagged_files) + $(am__define_uniq_tagged_files); \ + test -z "$(CTAGS_ARGS)$$unique" \ + || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \ + $$unique + +GTAGS: + here=`$(am__cd) $(top_builddir) && pwd` \ + && $(am__cd) $(top_srcdir) \ + && gtags -i $(GTAGS_ARGS) "$$here" +cscopelist: cscopelist-recursive + +cscopelist-am: $(am__tagged_files) + list='$(am__tagged_files)'; \ + case "$(srcdir)" in \ + [\\/]* | ?:[\\/]*) sdir="$(srcdir)" ;; \ + *) sdir=$(subdir)/$(srcdir) ;; \ + esac; \ + for i in $$list; do \ + if test -f "$$i"; then \ + echo "$(subdir)/$$i"; \ + else \ + echo "$$sdir/$$i"; \ + fi; \ + done >> $(top_builddir)/cscope.files + +distclean-tags: + -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags + +distdir: $(DISTFILES) + @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + list='$(DISTFILES)'; \ + dist_files=`for file in $$list; do echo $$file; done | \ + sed -e "s|^$$srcdirstrip/||;t" \ + -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \ + case $$dist_files in \ + */*) $(MKDIR_P) `echo "$$dist_files" | \ + sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \ + sort -u` ;; \ + esac; \ + for file in $$dist_files; do \ + if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ + if test -d $$d/$$file; then \ + dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d "$(distdir)/$$file"; then \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ + if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ + cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ + cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \ + else \ + test -f "$(distdir)/$$file" \ + || cp -p $$d/$$file "$(distdir)/$$file" \ + || exit 1; \ + fi; \ + done + @list='$(DIST_SUBDIRS)'; for subdir in $$list; do \ + if test "$$subdir" = .; then :; else \ + $(am__make_dryrun) \ + || test -d "$(distdir)/$$subdir" \ + || $(MKDIR_P) "$(distdir)/$$subdir" \ + || exit 1; \ + dir1=$$subdir; dir2="$(distdir)/$$subdir"; \ + $(am__relativize); \ + new_distdir=$$reldir; \ + dir1=$$subdir; dir2="$(top_distdir)"; \ + $(am__relativize); \ + new_top_distdir=$$reldir; \ + echo " (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) top_distdir="$$new_top_distdir" distdir="$$new_distdir" \\"; \ + echo " am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)"; \ + ($(am__cd) $$subdir && \ + $(MAKE) $(AM_MAKEFLAGS) \ + top_distdir="$$new_top_distdir" \ + distdir="$$new_distdir" \ + am__remove_distdir=: \ + am__skip_length_check=: \ + am__skip_mode_fix=: \ + distdir) \ + || exit 1; \ + fi; \ + done +check-am: all-am +check: check-recursive +all-am: Makefile +installdirs: installdirs-recursive +installdirs-am: +install: install-recursive +install-exec: install-exec-recursive +install-data: install-data-recursive +uninstall: uninstall-recursive + +install-am: all-am + @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am + +installcheck: installcheck-recursive +install-strip: + if test -z '$(STRIP)'; then \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + install; \ + else \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \ + fi +mostlyclean-generic: + +clean-generic: + +distclean-generic: + -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES) + +maintainer-clean-generic: + @echo "This command is intended for maintainers to use" + @echo "it deletes files that may require special tools to rebuild." +clean: clean-recursive + +clean-am: clean-generic clean-libtool mostlyclean-am + +distclean: distclean-recursive + -rm -f Makefile +distclean-am: clean-am distclean-generic distclean-tags + +dvi: dvi-recursive + +dvi-am: + +html: html-recursive + +html-am: + +info: info-recursive + +info-am: + +install-data-am: + +install-dvi: install-dvi-recursive + +install-dvi-am: + +install-exec-am: + +install-html: install-html-recursive + +install-html-am: + +install-info: install-info-recursive + +install-info-am: + +install-man: + +install-pdf: install-pdf-recursive + +install-pdf-am: + +install-ps: install-ps-recursive + +install-ps-am: + +installcheck-am: + +maintainer-clean: maintainer-clean-recursive + -rm -f Makefile +maintainer-clean-am: distclean-am maintainer-clean-generic + +mostlyclean: mostlyclean-recursive + +mostlyclean-am: mostlyclean-generic mostlyclean-libtool + +pdf: pdf-recursive + +pdf-am: + +ps: ps-recursive + +ps-am: + +uninstall-am: + +.MAKE: $(am__recursive_targets) install-am install-strip + +.PHONY: $(am__recursive_targets) CTAGS GTAGS TAGS all all-am check \ + check-am clean clean-generic clean-libtool cscopelist-am ctags \ + ctags-am distclean distclean-generic distclean-libtool \ + distclean-tags distdir dvi dvi-am html html-am info info-am \ + install install-am install-data install-data-am install-dvi \ + install-dvi-am install-exec install-exec-am install-html \ + install-html-am install-info install-info-am install-man \ + install-pdf install-pdf-am install-ps install-ps-am \ + install-strip installcheck installcheck-am installdirs \ + installdirs-am maintainer-clean maintainer-clean-generic \ + mostlyclean mostlyclean-generic mostlyclean-libtool pdf pdf-am \ + ps ps-am tags tags-am uninstall uninstall-am + + +# Tell versions [3.59,3.63) of GNU make to not export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.NOEXPORT: diff --git a/faq/de/Makefile.am b/faq/de/Makefile.am new file mode 100644 index 0000000..74ba384 --- /dev/null +++ b/faq/de/Makefile.am @@ -0,0 +1,11 @@ +faqdatadir = $(faqdir)/de + +faqdata_DATA = \ + sylpheed-faq-1.html \ + sylpheed-faq-2.html \ + sylpheed-faq-3.html \ + sylpheed-faq.html + +# generated by `ls -1 | sed -e 's/\(.*\)/ \1 \'` + +EXTRA_DIST = $(faqdata_DATA) diff --git a/faq/de/Makefile.in b/faq/de/Makefile.in new file mode 100644 index 0000000..459ea2a --- /dev/null +++ b/faq/de/Makefile.in @@ -0,0 +1,552 @@ +# Makefile.in generated by automake 1.14.1 from Makefile.am. +# @configure_input@ + +# Copyright (C) 1994-2013 Free Software Foundation, Inc. + +# This Makefile.in is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY, to the extent permitted by law; without +# even the implied warranty of MERCHANTABILITY or FITNESS FOR A +# PARTICULAR PURPOSE. + +@SET_MAKE@ + +VPATH = @srcdir@ +am__is_gnu_make = test -n '$(MAKEFILE_LIST)' && test -n '$(MAKELEVEL)' +am__make_running_with_option = \ + case $${target_option-} in \ + ?) ;; \ + *) echo "am__make_running_with_option: internal error: invalid" \ + "target option '$${target_option-}' specified" >&2; \ + exit 1;; \ + esac; \ + has_opt=no; \ + sane_makeflags=$$MAKEFLAGS; \ + if $(am__is_gnu_make); then \ + sane_makeflags=$$MFLAGS; \ + else \ + case $$MAKEFLAGS in \ + *\\[\ \ ]*) \ + bs=\\; \ + sane_makeflags=`printf '%s\n' "$$MAKEFLAGS" \ + | sed "s/$$bs$$bs[$$bs $$bs ]*//g"`;; \ + esac; \ + fi; \ + skip_next=no; \ + strip_trailopt () \ + { \ + flg=`printf '%s\n' "$$flg" | sed "s/$$1.*$$//"`; \ + }; \ + for flg in $$sane_makeflags; do \ + test $$skip_next = yes && { skip_next=no; continue; }; \ + case $$flg in \ + *=*|--*) continue;; \ + -*I) strip_trailopt 'I'; skip_next=yes;; \ + -*I?*) strip_trailopt 'I';; \ + -*O) strip_trailopt 'O'; skip_next=yes;; \ + -*O?*) strip_trailopt 'O';; \ + -*l) strip_trailopt 'l'; skip_next=yes;; \ + -*l?*) strip_trailopt 'l';; \ + -[dEDm]) skip_next=yes;; \ + -[JT]) skip_next=yes;; \ + esac; \ + case $$flg in \ + *$$target_option*) has_opt=yes; break;; \ + esac; \ + done; \ + test $$has_opt = yes +am__make_dryrun = (target_option=n; $(am__make_running_with_option)) +am__make_keepgoing = (target_option=k; $(am__make_running_with_option)) +pkgdatadir = $(datadir)/@PACKAGE@ +pkgincludedir = $(includedir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkglibexecdir = $(libexecdir)/@PACKAGE@ +am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd +install_sh_DATA = $(install_sh) -c -m 644 +install_sh_PROGRAM = $(install_sh) -c +install_sh_SCRIPT = $(install_sh) -c +INSTALL_HEADER = $(INSTALL_DATA) +transform = $(program_transform_name) +NORMAL_INSTALL = : +PRE_INSTALL = : +POST_INSTALL = : +NORMAL_UNINSTALL = : +PRE_UNINSTALL = : +POST_UNINSTALL = : +build_triplet = @build@ +host_triplet = @host@ +target_triplet = @target@ +subdir = faq/de +DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/Makefile.am \ + $(top_srcdir)/mkinstalldirs +ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 +am__aclocal_m4_deps = $(top_srcdir)/ac/aclocal-include.m4 \ + $(top_srcdir)/ac/gnupg-check-typedef.m4 \ + $(top_srcdir)/configure.ac +am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ + $(ACLOCAL_M4) +mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs +CONFIG_HEADER = $(top_builddir)/config.h +CONFIG_CLEAN_FILES = +CONFIG_CLEAN_VPATH_FILES = +AM_V_P = $(am__v_P_@AM_V@) +am__v_P_ = $(am__v_P_@AM_DEFAULT_V@) +am__v_P_0 = false +am__v_P_1 = : +AM_V_GEN = $(am__v_GEN_@AM_V@) +am__v_GEN_ = $(am__v_GEN_@AM_DEFAULT_V@) +am__v_GEN_0 = @echo " GEN " $@; +am__v_GEN_1 = +AM_V_at = $(am__v_at_@AM_V@) +am__v_at_ = $(am__v_at_@AM_DEFAULT_V@) +am__v_at_0 = @ +am__v_at_1 = +SOURCES = +DIST_SOURCES = +am__can_run_installinfo = \ + case $$AM_UPDATE_INFO_DIR in \ + n|no|NO) false;; \ + *) (install-info --version) >/dev/null 2>&1;; \ + esac +am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`; +am__vpath_adj = case $$p in \ + $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \ + *) f=$$p;; \ + esac; +am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`; +am__install_max = 40 +am__nobase_strip_setup = \ + srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'` +am__nobase_strip = \ + for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||" +am__nobase_list = $(am__nobase_strip_setup); \ + for p in $$list; do echo "$$p $$p"; done | \ + sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \ + $(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \ + if (++n[$$2] == $(am__install_max)) \ + { print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \ + END { for (dir in files) print dir, files[dir] }' +am__base_list = \ + sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \ + sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g' +am__uninstall_files_from_dir = { \ + test -z "$$files" \ + || { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \ + || { echo " ( cd '$$dir' && rm -f" $$files ")"; \ + $(am__cd) "$$dir" && rm -f $$files; }; \ + } +am__installdirs = "$(DESTDIR)$(faqdatadir)" +DATA = $(faqdata_DATA) +am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) $(LISP) +DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) +ACLOCAL = @ACLOCAL@ +ALLOCA = @ALLOCA@ +AMTAR = @AMTAR@ +AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@ +AR = @AR@ +AUTOCONF = @AUTOCONF@ +AUTOHEADER = @AUTOHEADER@ +AUTOMAKE = @AUTOMAKE@ +AWK = @AWK@ +BUILD_REVISION = @BUILD_REVISION@ +CATALOGS = @CATALOGS@ +CATOBJEXT = @CATOBJEXT@ +CC = @CC@ +CCDEPMODE = @CCDEPMODE@ +CFLAGS = @CFLAGS@ +CPP = @CPP@ +CPPFLAGS = @CPPFLAGS@ +CYGPATH_W = @CYGPATH_W@ +DATADIRNAME = @DATADIRNAME@ +DEFS = @DEFS@ +DEPDIR = @DEPDIR@ +DEVEL_VERSION = @DEVEL_VERSION@ +DLLTOOL = @DLLTOOL@ +DSYMUTIL = @DSYMUTIL@ +DUMPBIN = @DUMPBIN@ +ECHO_C = @ECHO_C@ +ECHO_N = @ECHO_N@ +ECHO_T = @ECHO_T@ +EGREP = @EGREP@ +EXEEXT = @EXEEXT@ +EXTRA_VERSION = @EXTRA_VERSION@ +FGREP = @FGREP@ +GETTEXT_PACKAGE = @GETTEXT_PACKAGE@ +GLIB_CFLAGS = @GLIB_CFLAGS@ +GLIB_COMPILE_RESOURCES = @GLIB_COMPILE_RESOURCES@ +GLIB_GENMARSHAL = @GLIB_GENMARSHAL@ +GLIB_LIBS = @GLIB_LIBS@ +GLIB_MKENUMS = @GLIB_MKENUMS@ +GMOFILES = @GMOFILES@ +GMSGFMT = @GMSGFMT@ +GOBJECT_QUERY = @GOBJECT_QUERY@ +GPGME_CFLAGS = @GPGME_CFLAGS@ +GPGME_CONFIG = @GPGME_CONFIG@ +GPGME_LIBS = @GPGME_LIBS@ +GREP = @GREP@ +GTK_CFLAGS = @GTK_CFLAGS@ +GTK_LIBS = @GTK_LIBS@ +INSTALL = @INSTALL@ +INSTALL_DATA = @INSTALL_DATA@ +INSTALL_PROGRAM = @INSTALL_PROGRAM@ +INSTALL_SCRIPT = @INSTALL_SCRIPT@ +INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@ +INSTOBJEXT = @INSTOBJEXT@ +INTLLIBS = @INTLLIBS@ +LD = @LD@ +LDAP_LIBS = @LDAP_LIBS@ +LDFLAGS = @LDFLAGS@ +LEX = @LEX@ +LEXLIB = @LEXLIB@ +LEX_OUTPUT_ROOT = @LEX_OUTPUT_ROOT@ +LIBICONV = @LIBICONV@ +LIBOBJS = @LIBOBJS@ +LIBS = @LIBS@ +LIBSYLPH_CFLAGS = @LIBSYLPH_CFLAGS@ +LIBSYLPH_LIBS = @LIBSYLPH_LIBS@ +LIBTOOL = @LIBTOOL@ +LIPO = @LIPO@ +LN_S = @LN_S@ +LTLIBICONV = @LTLIBICONV@ +LTLIBOBJS = @LTLIBOBJS@ +LT_AGE = @LT_AGE@ +LT_CURRENT = @LT_CURRENT@ +LT_RELEASE = @LT_RELEASE@ +LT_REVISION = @LT_REVISION@ +MAINT = @MAINT@ +MAJOR_VERSION = @MAJOR_VERSION@ +MAKEINFO = @MAKEINFO@ +MANIFEST_TOOL = @MANIFEST_TOOL@ +MICRO_VERSION = @MICRO_VERSION@ +MINOR_VERSION = @MINOR_VERSION@ +MKDIR_P = @MKDIR_P@ +MKINSTALLDIRS = @MKINSTALLDIRS@ +MSGFMT = @MSGFMT@ +MSGFMT_OPTS = @MSGFMT_OPTS@ +NM = @NM@ +NMEDIT = @NMEDIT@ +OBJDUMP = @OBJDUMP@ +OBJEXT = @OBJEXT@ +OPENSSL_CFLAGS = @OPENSSL_CFLAGS@ +OPENSSL_LIBS = @OPENSSL_LIBS@ +OTOOL = @OTOOL@ +OTOOL64 = @OTOOL64@ +PACKAGE = @PACKAGE@ +PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@ +PACKAGE_NAME = @PACKAGE_NAME@ +PACKAGE_STRING = @PACKAGE_STRING@ +PACKAGE_TARNAME = @PACKAGE_TARNAME@ +PACKAGE_URL = @PACKAGE_URL@ +PACKAGE_VERSION = @PACKAGE_VERSION@ +PATH_SEPARATOR = @PATH_SEPARATOR@ +PKG_CONFIG = @PKG_CONFIG@ +PKG_CONFIG_LIBDIR = @PKG_CONFIG_LIBDIR@ +PKG_CONFIG_PATH = @PKG_CONFIG_PATH@ +POFILES = @POFILES@ +POSUB = @POSUB@ +PO_IN_DATADIR_FALSE = @PO_IN_DATADIR_FALSE@ +PO_IN_DATADIR_TRUE = @PO_IN_DATADIR_TRUE@ +RANLIB = @RANLIB@ +SED = @SED@ +SET_MAKE = @SET_MAKE@ +SHELL = @SHELL@ +STRIP = @STRIP@ +SYLPHEED_LIBS = @SYLPHEED_LIBS@ +USE_NLS = @USE_NLS@ +VERSION = @VERSION@ +WINDRES = @WINDRES@ +XGETTEXT = @XGETTEXT@ +YACC = @YACC@ +YFLAGS = @YFLAGS@ +abs_builddir = @abs_builddir@ +abs_srcdir = @abs_srcdir@ +abs_top_builddir = @abs_top_builddir@ +abs_top_srcdir = @abs_top_srcdir@ +ac_ct_AR = @ac_ct_AR@ +ac_ct_CC = @ac_ct_CC@ +ac_ct_DUMPBIN = @ac_ct_DUMPBIN@ +am__include = @am__include@ +am__leading_dot = @am__leading_dot@ +am__quote = @am__quote@ +am__tar = @am__tar@ +am__untar = @am__untar@ +bindir = @bindir@ +build = @build@ +build_alias = @build_alias@ +build_cpu = @build_cpu@ +build_os = @build_os@ +build_vendor = @build_vendor@ +builddir = @builddir@ +datadir = @datadir@ +datarootdir = @datarootdir@ +docdir = @docdir@ +dvidir = @dvidir@ +exec_prefix = @exec_prefix@ +faqdir = @faqdir@ +host = @host@ +host_alias = @host_alias@ +host_cpu = @host_cpu@ +host_os = @host_os@ +host_vendor = @host_vendor@ +htmldir = @htmldir@ +includedir = @includedir@ +infodir = @infodir@ +install_sh = @install_sh@ +libdir = @libdir@ +libexecdir = @libexecdir@ +localedir = @localedir@ +localstatedir = @localstatedir@ +mandir = @mandir@ +manualdir = @manualdir@ +mkdir_p = @mkdir_p@ +oldincludedir = @oldincludedir@ +pdfdir = @pdfdir@ +plugindir = @plugindir@ +prefix = @prefix@ +program_transform_name = @program_transform_name@ +psdir = @psdir@ +sbindir = @sbindir@ +sharedstatedir = @sharedstatedir@ +srcdir = @srcdir@ +sysconfdir = @sysconfdir@ +target = @target@ +target_alias = @target_alias@ +target_cpu = @target_cpu@ +target_os = @target_os@ +target_vendor = @target_vendor@ +themedir = @themedir@ +top_build_prefix = @top_build_prefix@ +top_builddir = @top_builddir@ +top_srcdir = @top_srcdir@ +faqdatadir = $(faqdir)/de +faqdata_DATA = \ + sylpheed-faq-1.html \ + sylpheed-faq-2.html \ + sylpheed-faq-3.html \ + sylpheed-faq.html + + +# generated by `ls -1 | sed -e 's/\(.*\)/ \1 \'` +EXTRA_DIST = $(faqdata_DATA) +all: all-am + +.SUFFIXES: +$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.am $(am__configure_deps) + @for dep in $?; do \ + case '$(am__configure_deps)' in \ + *$$dep*) \ + ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \ + && { if test -f $@; then exit 0; else break; fi; }; \ + exit 1;; \ + esac; \ + done; \ + echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign faq/de/Makefile'; \ + $(am__cd) $(top_srcdir) && \ + $(AUTOMAKE) --foreign faq/de/Makefile +.PRECIOUS: Makefile +Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status + @case '$?' in \ + *config.status*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \ + *) \ + echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \ + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \ + esac; + +$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh + +$(top_srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(am__configure_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ $(am__aclocal_m4_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(am__aclocal_m4_deps): + +mostlyclean-libtool: + -rm -f *.lo + +clean-libtool: + -rm -rf .libs _libs +install-faqdataDATA: $(faqdata_DATA) + @$(NORMAL_INSTALL) + @list='$(faqdata_DATA)'; test -n "$(faqdatadir)" || list=; \ + if test -n "$$list"; then \ + echo " $(MKDIR_P) '$(DESTDIR)$(faqdatadir)'"; \ + $(MKDIR_P) "$(DESTDIR)$(faqdatadir)" || exit 1; \ + fi; \ + for p in $$list; do \ + if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \ + echo "$$d$$p"; \ + done | $(am__base_list) | \ + while read files; do \ + echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(faqdatadir)'"; \ + $(INSTALL_DATA) $$files "$(DESTDIR)$(faqdatadir)" || exit $$?; \ + done + +uninstall-faqdataDATA: + @$(NORMAL_UNINSTALL) + @list='$(faqdata_DATA)'; test -n "$(faqdatadir)" || list=; \ + files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \ + dir='$(DESTDIR)$(faqdatadir)'; $(am__uninstall_files_from_dir) +tags TAGS: + +ctags CTAGS: + +cscope cscopelist: + + +distdir: $(DISTFILES) + @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + list='$(DISTFILES)'; \ + dist_files=`for file in $$list; do echo $$file; done | \ + sed -e "s|^$$srcdirstrip/||;t" \ + -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \ + case $$dist_files in \ + */*) $(MKDIR_P) `echo "$$dist_files" | \ + sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \ + sort -u` ;; \ + esac; \ + for file in $$dist_files; do \ + if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ + if test -d $$d/$$file; then \ + dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d "$(distdir)/$$file"; then \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ + if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ + cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ + cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \ + else \ + test -f "$(distdir)/$$file" \ + || cp -p $$d/$$file "$(distdir)/$$file" \ + || exit 1; \ + fi; \ + done +check-am: all-am +check: check-am +all-am: Makefile $(DATA) +installdirs: + for dir in "$(DESTDIR)$(faqdatadir)"; do \ + test -z "$$dir" || $(MKDIR_P) "$$dir"; \ + done +install: install-am +install-exec: install-exec-am +install-data: install-data-am +uninstall: uninstall-am + +install-am: all-am + @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am + +installcheck: installcheck-am +install-strip: + if test -z '$(STRIP)'; then \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + install; \ + else \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \ + fi +mostlyclean-generic: + +clean-generic: + +distclean-generic: + -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES) + +maintainer-clean-generic: + @echo "This command is intended for maintainers to use" + @echo "it deletes files that may require special tools to rebuild." +clean: clean-am + +clean-am: clean-generic clean-libtool mostlyclean-am + +distclean: distclean-am + -rm -f Makefile +distclean-am: clean-am distclean-generic + +dvi: dvi-am + +dvi-am: + +html: html-am + +html-am: + +info: info-am + +info-am: + +install-data-am: install-faqdataDATA + +install-dvi: install-dvi-am + +install-dvi-am: + +install-exec-am: + +install-html: install-html-am + +install-html-am: + +install-info: install-info-am + +install-info-am: + +install-man: + +install-pdf: install-pdf-am + +install-pdf-am: + +install-ps: install-ps-am + +install-ps-am: + +installcheck-am: + +maintainer-clean: maintainer-clean-am + -rm -f Makefile +maintainer-clean-am: distclean-am maintainer-clean-generic + +mostlyclean: mostlyclean-am + +mostlyclean-am: mostlyclean-generic mostlyclean-libtool + +pdf: pdf-am + +pdf-am: + +ps: ps-am + +ps-am: + +uninstall-am: uninstall-faqdataDATA + +.MAKE: install-am install-strip + +.PHONY: all all-am check check-am clean clean-generic clean-libtool \ + cscopelist-am ctags-am distclean distclean-generic \ + distclean-libtool distdir dvi dvi-am html html-am info info-am \ + install install-am install-data install-data-am install-dvi \ + install-dvi-am install-exec install-exec-am \ + install-faqdataDATA install-html install-html-am install-info \ + install-info-am install-man install-pdf install-pdf-am \ + install-ps install-ps-am install-strip installcheck \ + installcheck-am installdirs maintainer-clean \ + maintainer-clean-generic mostlyclean mostlyclean-generic \ + mostlyclean-libtool pdf pdf-am ps ps-am tags-am uninstall \ + uninstall-am uninstall-faqdataDATA + + +# Tell versions [3.59,3.63) of GNU make to not export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.NOEXPORT: diff --git a/faq/de/sylpheed-faq-1.html b/faq/de/sylpheed-faq-1.html new file mode 100644 index 0000000..059e3db --- /dev/null +++ b/faq/de/sylpheed-faq-1.html @@ -0,0 +1,221 @@ + + + + + Sylpheed FAQ: Sylpheed FAQ - Allgemeine Informationen + + + + + +Weiter +Zurück +Inhalt +
+

1. Sylpheed FAQ - Allgemeine Informationen

+ +

1.1 Frage 01: Gibt es FAQs in anderen Sprachen? +

+ +

Antwort: Ja. Hier sind Links zu verschiedenen Übersetzungen der FAQs ("Frequently Asked Questions", oft gestellte Fragen inklusive Antworten): +

+ +Die offizielle Homepage des Sylpheed Dokumentationsprojektes, mit FAQ und Handbuch in mehreren Sprachen befindet sich auf +http://sylpheeddoc.sf.net

1.2 Frage 02: Was ist Sylpheed? +

+ +

Antwort: Sylpheed ist ein E-Mail Client (und Newsreader) basierend auf +GTK+, für das X Window System. +Ziele bei der Entwicklung von Sylpheed sind +

+

1.3 Frage 03: Woher bekomme ich Sylpheed? +

+ +

Antwort: Man bekommt Sylpheed auf +sylpheed.good-day.net +Hier findet man Links auf die Quellen als Tarball, und auf Seiten mit +RPMs (für SuSE, Redhat, Mandrake, etc.), DEB-Paketen für Debian, und Paketen für Solaris und BSD. +

1.4 Frage 04: Wer entwickelt Sylpheed? +

+ +

Antwort: Hiroyuki Yamamoto (hiro-y@kcn.ne.jp) +

1.5 Frage 05: Was bedeutet der Name Sylpheed? +

+ +

Antwort: Er bedeutet 'leicht wie Luft'. Er entstammt dem Namen der Windgeister, den Sylphen. +

1.6 Frage 06: Wie speichert Sylpheed Nachrichten? +

+ +

Antwort: Sylpheed speichert Nachrichten im MH-Format, so wie es von MH und EMH benutzt wird. +Maildir und mbox-Format werden (noch) nicht unterstützt, man kann mbox-Dateien aber direkt +importieren. +

1.7 Frage 07: Wieso funktioniert das automatische Abholen der Nachrichten nicht? +

+ +

Antwort: Das automatische Abholen funktioniert seit Version 0.5.1. Wer es benötigt, +sollte keine ältere Version verwenden. +

1.8 Frage 08: Kann Sylpheed Nachrichten filtern? +

+ +

Antwort: Ja. Der entsprechende Dialog befindet sich in "Einstellungen -> Filterung". +Für IMAP-Accounts ist (noch) keine Filterung implementiert. +

1.9 Frage 09: Kann Sylpheed auf IMAP-Server zugreifen? +

+ +

Antwort: Ja, seit Version 0.4.99 wird IMAP unterstützt. +

1.10 Frage 10: Kann Sylpheed lokale Unix Mailboxen abfragen? +

+ +

Antwort: Ja. +

1.11 Frage 11: Unterstützt Sylpheed IPv6? +

+ +

Antwort: Ja, IPv6 wird von Sylpheed voll unterstützt. +

1.12 Frage 12: Unterstützt Sylpheed digitale Signaturen und Verschlüsselung mit GPG? +

+ +

Antwort: Ja. GPG wird unterstützt. Um es zu verwenden, siehe Frage 14 im Abschnitt Installieren. +

1.13 Frage 13: Wie erkennt Sylpheed MIME Typen? +

+ +

Antwort: Sylpheed erkennt MIME Typen so wie Mutt. +

1.14 Frage 14: Kann ich mit Sylpheed auch HTML-Nachrichten senden? +

+ +

Antwort: Nein. Reifliche Diskussionen ergaben, daß HTML-Nachrichten generell unerwünscht sind. +Wer es wirklich will, kann HTML-Seiten als Anhang an seine Nachrichten heften. +Zusätzlich finden sich verschiedene Patches für erweiterte HTML-Verarbeitung auf den +Sylpheed Patch Seiten (siehe weiter unten). +

1.15 Frage 15: Besitzt Sylpheed eine Autovervollständigung in Adressfeldern? +

+ +

Antwort: Ja. Sucht man nach einem Namen, der mit "don" beginnt, +gibt man "don" ein (ohne Anführungszeichen) und drückt die TAB-Taste. +Gibt es nur einen Namen mit "don" im Adressbuch, so wird dieser nun angezeigt, +gibt es mehrere, so werden diese in einer Dropdown-Liste angezeigt. +Das funktioniert sowohl mit Namen, wie auch mit E-Mail-Adressen. +

1.16 Frage 16: Gut, aber wenn ich die TAB-Taste drücke, werden keine Namen angezeigt. +

+ +

Antwort: Um die Autovervollständigung zu benutzen, müssen die Namen zunächst im +Adressbuch eingetragen sein. Sonst geht's nicht. +

1.17 Frage 17: Warum ist Sylpheed so schnell? +

+ +

Antwort: Dazu wurde es entwickelt! +

1.18 Frage 18: Wo bekomme ich aktuelle Patches für Sylpheed? +

+ +

Antwort: Auf der Sylpheed Patch Homepage: + +http://www.teledix.net/sylpheed/ +

(Siehe auch im Abschnitt "Installieren", wie man einen Patch anwendet) +

1.19 Frage 19: Wohin schicke ich Patches, Fehlermeldungen, oder rede mit anderen Benutzern über Sylpheed? +

+ +

Antwort: Um mit anderen Benutzern über Sylpheed zu reden, abonniert man am besten die Sylpheed Mailingliste auf http://sylpheed.good-day.net. Hier kann man zwischen einer englischen und einer japanischen Mailingliste wählen. +Will man die Welt mit Patches beglücken, so wendet man sich am besten an den Verwalter der Sylpheed Patch Homepage, sylpheed@thewildbeast.co.uk. +

1.20 Frage 20: Wenn ich Nachrichten versende, wieso steht in der "Content-Type"-Kopfzeile US-ASCII, obwohl ich ISO-8859-1 angegeben habe? +

+ +

Antwort: Wenn keine ISO-8859-1 Zeichen (>= 0x80) im Text enthalten sind, wird als Zeichensatz automatisch US-ASCII verwendet, gemäß einem Grundprinzip der Kommunikation, Informationen immer auf dem niedrigst nötigen technischen Nenner anzubieten. +

1.21 Frage 21: Warum habe ich das Gefühl, daß der Zeilenumbruch nicht funktioniert? +

+ +

Antwort: Zeilenumbrüche sind etwas gewöhnungsbedürftig. +

Harte Zeilenumbrüche können zwar jederzeit eingefügt werden, man kann +aber prinzipiell beliebig lange Zeilen schreiben. +Mit der Taste "Zeilenumbruch" können die Zeilen auf die eingestellte +Zeilenlänge umgebrochen werden. Andernfalls geschieht dies automatisch, sobald +die Nachricht abgesandt wird, oder in die Queue-Ablage kommt. +Diese Vorgangsweise soll das Verfassen von Nachrichten vereinfachen. +

Hierzu ein Beispiel, um den Vorteil zu illustrieren: +

+Diese lange, lange Zeile wird
+umgebrochen.
+
+

Nun fügen wir in der ersten Zeile ein Wort ein: +

+Diese lange, lange Zeile wird
+hier
+umgebrochen.
+
+ +Es würde einige händische Arbeit erfordern, um wieder zu +einer anständigen Formatierung zu gelangen. +Diese Arbeit wird uns von Sylpheed abgenommen. +
+Diese lange, lange Zeile wird
+hier umgebrochen.
+
+

1.22 Frage 22: Wo finde ich die neuesten FAQ für Sylpheed? +

+ +

Antwort: Auf +sylpheeddoc.sourceforge.net befinden sich FAQ und Handbuch des Sylpheeddoc Projektes. Beide Dokumente stehen in aktueller Version und mehreren Sprachen zur Verfügung. +

1.23 Frage 23: Kann ich Mbox-Dateien in Sylpheed's MH Ablagen importieren? +

+ +

Antwort: Ja, man muß nur zuerst eine Ablage erstellen, in der Ablagenübersicht auswählen und "Datei > Importiere Mbox-Datei..." wählen. +

1.24 Frage 24: Kann ich procmail benutzen, um meine Nachrichten in MH Ablagen zu sortieren? +

+ +

Antwort: Ja. Es ist nur notwendig, /. an die Adressen der MH Ablagen anzufügen, in den procmail Regeln. z.B. +

0: +

* ^Subject:.*sylpheed +

sylpheedmail/. +

Nähere Einzelheiten findet man in der Dokumentation zu procmail. +

1.25 Frage 25: Worauf sollte ich achten, wenn ich auf eine aktuelle Version von Sylpheed updaten will? +

+ +

Antwort: +

+

1.26 Frage 26: Wie kann ich in Sylpheed die Ansicht schnell erneuern? +

+ +

Antwort: Mit "Ansicht -> Aktualisieren", oder dem entsprechenden Tastaturkürzel. +

1.27 Frage 27: Warum kann ich gvim nicht als externen Editor verwenden? +

+ +

Antwort: Will man gvim als externen Editor verwenden, muß man es mit der no-fork Option starten, also in "Einstellungen -> Allgemeine Einstellungen", Reiter "Weiteres" "gvim -f %s" eintragen. Ansonsten forkt der Editor, öffnet ein eigenes Fenster, und übernimmt beim Beenden den Text nicht. (Danke, Ed Collins!) +

+Weiter +Zurück +Inhalt + + diff --git a/faq/de/sylpheed-faq-2.html b/faq/de/sylpheed-faq-2.html new file mode 100644 index 0000000..02cd9a5 --- /dev/null +++ b/faq/de/sylpheed-faq-2.html @@ -0,0 +1,125 @@ + + + + + Sylpheed FAQ: Sylpheed FAQ - Installieren und Konfigurieren + + + + + +Weiter +Zurück +Inhalt +
+

2. Sylpheed FAQ - Installieren und Konfigurieren

+ +

2.1 Frage 01: Was benötigt man um Sylpheed zu kompilieren? +

+ +

Antwort: +

+ +Achtung: es wurde berichtet, daß Sun C Sylpheed nicht kompiliert. +

Optional: +

+

2.2 Frage 02: Wie konfiguriere ich Sylpheed? +

+ +

Antwort: Beim ersten Start von Sylpheed muß man angeben, wo man seine Nachrichten aufbewahren möchte. Voreingestellt ist $HOME/Mail. Man kan aber auch einen beliebigen, anderen, gültigen Verzeichnisnamen wählen. Sollten in diesem Verzeichnis aber bereits Dateien (nicht im MH-Format) existieren, muß man einen anderen Namen wählen. +

Beim ersten Start werden auch automatisch Konfigurationsdateien im Verzeichnis $HOME/.sylpheed/ angelegt. +

2.3 Frage 03: Wie konfiguriere ich einen Account? +

+ +

Antwort: Accounts können über "Einstellungen -> Neuen Account erstellen..." eingerichtet werden. +

2.4 Frage 04: Wie viele Accounts kann ich in Sylpheed konfigurieren? +

+ +

Antwort: Sehr, sehr viele. Begrenzende Faktoren sind nur Festplattenkapazität, verwendetes Filesystem oder ähnliches. +

2.5 Frage 05: Warum löscht Sylpheed meine E-Mails nicht, wenn ich "Nachricht -> Löschen" drücke? Ich definiere einen Filter, aber Sylpheed filtert nicht. Ich habe eine Nachricht in eine andere Ablage verschoben, aber sie bewegt sich nicht. +

+ +

Antwort: Man muß auf "Ausführen" klicken, oder in "Einstellungen -> Allgemeine Einstellungen", Reiter "Benutzerschnittstelle", "Sofort Ausführen beim Bewegen oder Löschen" wählen. +

2.6 Frage 06: Kann ich spezielle Adressen/Ports für meine Mailserver/Newsserver verwenden? +

+ +

Antwort: Ja, das geht. In den Accounteinstellungen können im Reiter "Einfach" die Adresse, und im Reiter "Speziell" die genauen Ports angegeben werden. +

2.7 Frage 07: Kann Sylpheed Nachrichten in Threads darstellen? +

+ +

Antwort: Ja. Man kann diese Option in "Ansicht > Threads einschalten" ein- und ausschalten. +

2.8 Frage 08: Kann ich meine E-Mails in mehreren Ebenen von Unterablagen verwalten? +

+ +

Antwort: Sicher. Das ist kein Problem. +

2.9 Frage 09: Warum verschickt Sylpheed meine Nachrichten nicht? +

+ +

Antwort: Man muß zumindest einen Account konfigurieren, um Nachrichten senden zu können. +(Beim Installieren im LAN, nur mit lokaler Unix Mailbox, kann man darauf leicht vergessen). +

2.10 Frage 10: Wie wende ich einen Patch an, nachdem ich ihn heruntergeladen habe? +

+ +

Antwort: Man kopiert den Patch ins Verzeichnis der Sylpheed-Sourcen, dann wendet man ihn wie folgt an: +

% patch -p0 < irgendein.patch +

Oder, wenn er als gz vorliegt: +

% gzip -dc irgendein.patch.gz | patch -p0 +

Nun das Kommando ./autogen.sh, man löscht die Datei /config.cache +(ausser man will in /usr/local installieren). +

Dann ruft man ./configure mit den gewünschten Optionen auf (für die verfügbaren Optionen ./configure --help), schließlich make. +

2.11 Frage 11: Wie kompiliere ich Sylpheed mit compface Unterstützung (X-Faces)? +

+ +

Antwort: Man benötigt libcompface, um Sylpheed mit compface Unterstützung kompilieren zu können. +

2.12 Frage 12: Wie kann ich ein eigenes compface Bild (X-Face) erzeugen? +

+ +

Antwort: Es gibt verschiedene Anwendungen für das Konvertieren, wie das xbm2ikon Script aus dem faces-Paket, oder gif2xface aus den claws-tools. +

Außerdem existiert dank Jeff Dairiki eine Online-Konvertierung, zusammen mit einem kompletten X-Face-Kurs auf +http://www.dairiki.org/xface/. +

2.13 Frage 13: Wie kann ich meinem Browser/einer anderen Anwendung ermöglichen, Sylpheed als als E-Mail-Programm zu verwenden? +

+ +

Antwort: In den Einstellungen der anderen Anwendung gibt man sylpheed --compose an. +

2.14 Frage 14: Wie bekomme ich GPG-Unterstützung in Sylpheed? +

+ +

Antwort: Mit einer aktuellen Version von GPGME gibt man beim Kompilieren von Sylpheed --enable-gpgme in der ./configure Anweisung an. Nach erfolgreichem Kompilieren sind die Reiter der "Allgemeinen Einstellungen" um den Reiter "Privat" bereichert. +

2.15 Frage 15: Mutt erkennt Sylpheed's MH-Struktur nicht! +

+ +

Antwort: In diesem Fall sollte man den Befehl "touch" auf die Datei .xmhcache anwenden, die sich in jeder MH Ablage befindet. Dann sollte Mutt die Struktur erkennen können. +

2.16 Frage 16: Das Öffnen einer GIF-Datei in Sylpheed erzeugt einen Segmentation Fault. +

+ +

Antwort: Das kann durch folgenden Eintrag in /etc/mime.types behoben werden: +

image/gif gif +

2.17 Frage 17: Wie kann ich mich von Sylpheed benachrichtigen lassen, wenn neue Nachrichten ankommen? +

+ +

Antwort: Dafür gibt es verschiedene Möglichkeiten: +

+
+Weiter +Zurück +Inhalt + + diff --git a/faq/de/sylpheed-faq-3.html b/faq/de/sylpheed-faq-3.html new file mode 100644 index 0000000..377611c --- /dev/null +++ b/faq/de/sylpheed-faq-3.html @@ -0,0 +1,107 @@ + + + + + Sylpheed FAQ: Sylpheed FAQ - Oberfläche + + + + +Weiter +Zurück +Inhalt +
+

3. Sylpheed FAQ - Oberfläche

+ +

3.1 Frage 01: Wie kann ich Sylpheed in meiner Sprache anzeigen lassen? +

+ +

Antwort: Dafür muß man einige Umgebungsvariablen verändern, wie +LANG,LC_CTYPE, LC_MESSAGES auf die gewünschte Sprache, z.B. de_AT. +Normalerweise genügt es, LANG (oder LC_ALL) anzupassen. +

3.2 Frage 02: Mir gefällt die voreingestellte Schriftart nicht. Kann ich sie ändern? +

+ +

Antwort: Ja. In "Einstellungen -> Allgemeine Einstellungen...", Reiter "Anzeige". +

3.3 Frage 03: Da sind zu viele Spalten in der Nachrichtenliste! +

+ +

Antwort: In "Einstellungen -> Allgemeine Einstellungen...", Reiter "Anzeige", +Setze Einträge der Ablageninhaltsansicht. In diesem Dialog kann man die +anzuzeigenden Informationen auswählen. +

3.4 Frage 04: Kann ich einen anderen Editor verwenden, um meine Nachrichten zu schreiben? +

+ +

Antwort: Ja. In "Einstellungen -> Allgemeine Einstellungen...", Reiter "Weiteres", +kann man unter "Editor" einen externen Editor wählen. Für einen Kommandozeileneditor wie +vi oder emacs muß man noch eine Shell (term, rxvt) angeben, z.B. rxvt -e vi %s +

3.5 Frage 05: Wie kann ich die Schriftgröße für die Oberfläche Sylpheed's verändern? +

+ +

Antwort: Die GTK+ Schriftart kann man in ~/.gtkrc ändern, oder in +~/.gtkrc.mine, (in ~/.gtkrc enthalten). +Zum Beispiel: +

style "default" +

{ +

font = +

"-adobe-helvetica-medium-r-normal--12-*-*-*-*-*-iso8859-1 +

" +

} +

widget_class "*" style "default" +

3.6 Frage 06: Sylpheed speichert meine gesendeten Nachrichten (in der Ablage "Outbox"). Wie kann ich das verhindern? +

+ +

Antwort: In "Einstellungen -> Allgemeine Einstellungen...", Reiter "Senden", "Gesendete Nachrichten in Outbox speichern" deaktivieren. Das war's. +

3.7 Frage 07: Wie kann ich die Tastaturkürzel in Sylpheed verändern? +

+ +

Antwort: Einfach. Um z.B. das Tastaturkürzel für "Ansicht -> Zeige Quellen" +auf Strg+3 ändern, klickt man auf "Ansicht", und fährt mit der Maus über +"Zeige Quellen", klickt aber nicht. Nun drückt man Strg+3, und sofort wird +dies als neues Kürzel angezeigt. +

Sollte das Kürzel für eine andere Funktion eingetragen gewesen sein, so +ist diese nun unbesetzt. Um ein Kürzel zu löschen, drückt man statt einer +Tastenkombination die "Entf"-Taste. +

3.8 Frage 08: Kann ich Fenster auch ohne Maus schließen? +

+ +

Antwort: Natürlich! Zwar nicht alle Fenster, aber die meisten lassen sich mit ESCape schließen. +Dazu gehören das Adressbuch, das Fenster zum Anzeigen des Quelltextes, oder der Kopfzeilen, +und verschiedene andere. Ausprobieren. +

3.9 Frage 09: Wie kann ich die Datumsanzeige in der Ablageninhaltsansicht verändern? +

+ +

Antwort: Seit Version 0.4.65 kann man die Datumsanzeige mit folgenden Optionen konfigurieren: +%y = Jahr als Zahl %m = Monat als Zahl +%d = Tag als Zahl %c = Datum/Zeit der Locale +%A = Wochentagsname %a = Gekürzter Wochentagsname +%B = Monatsname %b = Gekürzter Monatsname +%H = Stunden (24h Anzeige) %I = Stunden (12h Anzeige) +Genauere Informationen findet man unter +"Einstellungen -> Allgemeine Einstellungen", Reiter "Anzeige", Datumsformat "..." +

3.10 Frage 10: Warum sehe ich keine compface Bilder (X-Faces)? +

+ +

Antwort: Dafür muß die Ansicht der Kopfzeilenleiste über der Nachrichtenansicht aktiviert sein, "Einstellungen -> Allgemeine Einstellungen...", Reiter "Nachricht", Zeige Kopfzeilenleiste über Nachrichtenansicht. +

3.11 Frage 11: Warum sehe ich immer noch keine X-Faces? +

+ +

Antwort: Möglicherweise wurde Sylpheed ohne Compface-Unterstützung kompiliert. +Das erkennt man in "Hilfe -> Über", compiled-in features: libcompface. Siehe +Frage 11 im Abschnitt Installieren/Konfigurieren. +

3.12 Frage 12: Wieso öffnet die URL in der Nachricht nicht meinen Webbrowser? +

+ +

Antwort: Man muß die URL doppelclicken. +

3.13 Frage 13: Ich kann Anhänge mit Leerzeichen im Namen nicht öffnen! +

+ +

Antwort: Versucht man einen Anhang an eine Hilfsanwendung zu übergeben, +z.B. einen Videoplayer, und der Name des Anhangs enthält Leerzeichen, dann muß man +den %s Parameter mit ' schützen: noatun '%s' +

+Weiter +Zurück +Inhalt + + diff --git a/faq/de/sylpheed-faq.html b/faq/de/sylpheed-faq.html new file mode 100644 index 0000000..e24b14a --- /dev/null +++ b/faq/de/sylpheed-faq.html @@ -0,0 +1,103 @@ + + + + + Sylpheed FAQ + + + + + +Weiter +Zurück +Inhalt +
+

Sylpheed FAQ

+ + +

Paul Kater (paul@nlpagan.net) +
Jens Oberender (j.obi@troja.net) +
Nicolas Kaiser (nikai@nikai.net) +

+

+ Sylpheed FAQ (für Version 0.7.3) + +
+

+

1. Sylpheed FAQ - Allgemeine Informationen

+ + +

+

2. Sylpheed FAQ - Installieren und Konfigurieren

+ + +

+

3. Sylpheed FAQ - Oberfläche

+ + +
+Weiter +Zurück +Inhalt + + 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 @@ + GNU Free Documentation License + Version 1.2, November 2002 + + + Copyright (C) 2000,2001,2002 Free Software Foundation, Inc. + 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + +0. PREAMBLE + +The purpose of this License is to make a manual, textbook, or other +functional and useful document "free" in the sense of freedom: to +assure everyone the effective freedom to copy and redistribute it, +with or without modifying it, either commercially or noncommercially. +Secondarily, this License preserves for the author and publisher a way +to get credit for their work, while not being considered responsible +for modifications made by others. + +This License is a kind of "copyleft", which means that derivative +works of the document must themselves be free in the same sense. It +complements the GNU General Public License, which is a copyleft +license designed for free software. + +We have designed this License in order to use it for manuals for free +software, because free software needs free documentation: a free +program should come with manuals providing the same freedoms that the +software does. But this License is not limited to software manuals; +it can be used for any textual work, regardless of subject matter or +whether it is published as a printed book. We recommend this License +principally for works whose purpose is instruction or reference. + + +1. APPLICABILITY AND DEFINITIONS + +This License applies to any manual or other work, in any medium, that +contains a notice placed by the copyright holder saying it can be +distributed under the terms of this License. Such a notice grants a +world-wide, royalty-free license, unlimited in duration, to use that +work under the conditions stated herein. The "Document", below, +refers to any such manual or work. Any member of the public is a +licensee, and is addressed as "you". You accept the license if you +copy, modify or distribute the work in a way requiring permission +under copyright law. + +A "Modified Version" of the Document means any work containing the +Document or a portion of it, either copied verbatim, or with +modifications and/or translated into another language. + +A "Secondary Section" is a named appendix or a front-matter section of +the Document that deals exclusively with the relationship of the +publishers or authors of the Document to the Document's overall subject +(or to related matters) and contains nothing that could fall directly +within that overall subject. (Thus, if the Document is in part a +textbook of mathematics, a Secondary Section may not explain any +mathematics.) The relationship could be a matter of historical +connection with the subject or with related matters, or of legal, +commercial, philosophical, ethical or political position regarding +them. + +The "Invariant Sections" are certain Secondary Sections whose titles +are designated, as being those of Invariant Sections, in the notice +that says that the Document is released under this License. If a +section does not fit the above definition of Secondary then it is not +allowed to be designated as Invariant. The Document may contain zero +Invariant Sections. If the Document does not identify any Invariant +Sections then there are none. + +The "Cover Texts" are certain short passages of text that are listed, +as Front-Cover Texts or Back-Cover Texts, in the notice that says that +the Document is released under this License. A Front-Cover Text may +be at most 5 words, and a Back-Cover Text may be at most 25 words. + +A "Transparent" copy of the Document means a machine-readable copy, +represented in a format whose specification is available to the +general public, that is suitable for revising the document +straightforwardly with generic text editors or (for images composed of +pixels) generic paint programs or (for drawings) some widely available +drawing editor, and that is suitable for input to text formatters or +for automatic translation to a variety of formats suitable for input +to text formatters. A copy made in an otherwise Transparent file +format whose markup, or absence of markup, has been arranged to thwart +or discourage subsequent modification by readers is not Transparent. +An image format is not Transparent if used for any substantial amount +of text. A copy that is not "Transparent" is called "Opaque". + +Examples of suitable formats for Transparent copies include plain +ASCII without markup, Texinfo input format, LaTeX input format, SGML +or XML using a publicly available DTD, and standard-conforming simple +HTML, PostScript or PDF designed for human modification. Examples of +transparent image formats include PNG, XCF and JPG. Opaque formats +include proprietary formats that can be read and edited only by +proprietary word processors, SGML or XML for which the DTD and/or +processing tools are not generally available, and the +machine-generated HTML, PostScript or PDF produced by some word +processors for output purposes only. + +The "Title Page" means, for a printed book, the title page itself, +plus such following pages as are needed to hold, legibly, the material +this License requires to appear in the title page. For works in +formats which do not have any title page as such, "Title Page" means +the text near the most prominent appearance of the work's title, +preceding the beginning of the body of the text. + +A section "Entitled XYZ" means a named subunit of the Document whose +title either is precisely XYZ or contains XYZ in parentheses following +text that translates XYZ in another language. (Here XYZ stands for a +specific section name mentioned below, such as "Acknowledgements", +"Dedications", "Endorsements", or "History".) To "Preserve the Title" +of such a section when you modify the Document means that it remains a +section "Entitled XYZ" according to this definition. + +The Document may include Warranty Disclaimers next to the notice which +states that this License applies to the Document. These Warranty +Disclaimers are considered to be included by reference in this +License, but only as regards disclaiming warranties: any other +implication that these Warranty Disclaimers may have is void and has +no effect on the meaning of this License. + + +2. VERBATIM COPYING + +You may copy and distribute the Document in any medium, either +commercially or noncommercially, provided that this License, the +copyright notices, and the license notice saying this License applies +to the Document are reproduced in all copies, and that you add no other +conditions whatsoever to those of this License. You may not use +technical measures to obstruct or control the reading or further +copying of the copies you make or distribute. However, you may accept +compensation in exchange for copies. If you distribute a large enough +number of copies you must also follow the conditions in section 3. + +You may also lend copies, under the same conditions stated above, and +you may publicly display copies. + + +3. COPYING IN QUANTITY + +If you publish printed copies (or copies in media that commonly have +printed covers) of the Document, numbering more than 100, and the +Document's license notice requires Cover Texts, you must enclose the +copies in covers that carry, clearly and legibly, all these Cover +Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on +the back cover. Both covers must also clearly and legibly identify +you as the publisher of these copies. The front cover must present +the full title with all words of the title equally prominent and +visible. You may add other material on the covers in addition. +Copying with changes limited to the covers, as long as they preserve +the title of the Document and satisfy these conditions, can be treated +as verbatim copying in other respects. + +If the required texts for either cover are too voluminous to fit +legibly, you should put the first ones listed (as many as fit +reasonably) on the actual cover, and continue the rest onto adjacent +pages. + +If you publish or distribute Opaque copies of the Document numbering +more than 100, you must either include a machine-readable Transparent +copy along with each Opaque copy, or state in or with each Opaque copy +a computer-network location from which the general network-using +public has access to download using public-standard network protocols +a complete Transparent copy of the Document, free of added material. +If you use the latter option, you must take reasonably prudent steps, +when you begin distribution of Opaque copies in quantity, to ensure +that this Transparent copy will remain thus accessible at the stated +location until at least one year after the last time you distribute an +Opaque copy (directly or through your agents or retailers) of that +edition to the public. + +It is requested, but not required, that you contact the authors of the +Document well before redistributing any large number of copies, to give +them a chance to provide you with an updated version of the Document. + + +4. MODIFICATIONS + +You may copy and distribute a Modified Version of the Document under +the conditions of sections 2 and 3 above, provided that you release +the Modified Version under precisely this License, with the Modified +Version filling the role of the Document, thus licensing distribution +and modification of the Modified Version to whoever possesses a copy +of it. In addition, you must do these things in the Modified Version: + +A. Use in the Title Page (and on the covers, if any) a title distinct + from that of the Document, and from those of previous versions + (which should, if there were any, be listed in the History section + of the Document). You may use the same title as a previous version + if the original publisher of that version gives permission. +B. List on the Title Page, as authors, one or more persons or entities + responsible for authorship of the modifications in the Modified + Version, together with at least five of the principal authors of the + Document (all of its principal authors, if it has fewer than five), + unless they release you from this requirement. +C. State on the Title page the name of the publisher of the + Modified Version, as the publisher. +D. Preserve all the copyright notices of the Document. +E. Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. +F. Include, immediately after the copyright notices, a license notice + giving the public permission to use the Modified Version under the + terms of this License, in the form shown in the Addendum below. +G. Preserve in that license notice the full lists of Invariant Sections + and required Cover Texts given in the Document's license notice. +H. Include an unaltered copy of this License. +I. Preserve the section Entitled "History", Preserve its Title, and add + to it an item stating at least the title, year, new authors, and + publisher of the Modified Version as given on the Title Page. If + there is no section Entitled "History" in the Document, create one + stating the title, year, authors, and publisher of the Document as + given on its Title Page, then add an item describing the Modified + Version as stated in the previous sentence. +J. Preserve the network location, if any, given in the Document for + public access to a Transparent copy of the Document, and likewise + the network locations given in the Document for previous versions + it was based on. These may be placed in the "History" section. + You may omit a network location for a work that was published at + least four years before the Document itself, or if the original + publisher of the version it refers to gives permission. +K. For any section Entitled "Acknowledgements" or "Dedications", + Preserve the Title of the section, and preserve in the section all + the substance and tone of each of the contributor acknowledgements + and/or dedications given therein. +L. Preserve all the Invariant Sections of the Document, + unaltered in their text and in their titles. Section numbers + or the equivalent are not considered part of the section titles. +M. Delete any section Entitled "Endorsements". Such a section + may not be included in the Modified Version. +N. Do not retitle any existing section to be Entitled "Endorsements" + or to conflict in title with any Invariant Section. +O. Preserve any Warranty Disclaimers. + +If the Modified Version includes new front-matter sections or +appendices that qualify as Secondary Sections and contain no material +copied from the Document, you may at your option designate some or all +of these sections as invariant. To do this, add their titles to the +list of Invariant Sections in the Modified Version's license notice. +These titles must be distinct from any other section titles. + +You may add a section Entitled "Endorsements", provided it contains +nothing but endorsements of your Modified Version by various +parties--for example, statements of peer review or that the text has +been approved by an organization as the authoritative definition of a +standard. + +You may add a passage of up to five words as a Front-Cover Text, and a +passage of up to 25 words as a Back-Cover Text, to the end of the list +of Cover Texts in the Modified Version. Only one passage of +Front-Cover Text and one of Back-Cover Text may be added by (or +through arrangements made by) any one entity. If the Document already +includes a cover text for the same cover, previously added by you or +by arrangement made by the same entity you are acting on behalf of, +you may not add another; but you may replace the old one, on explicit +permission from the previous publisher that added the old one. + +The author(s) and publisher(s) of the Document do not by this License +give permission to use their names for publicity for or to assert or +imply endorsement of any Modified Version. + + +5. COMBINING DOCUMENTS + +You may combine the Document with other documents released under this +License, under the terms defined in section 4 above for modified +versions, provided that you include in the combination all of the +Invariant Sections of all of the original documents, unmodified, and +list them all as Invariant Sections of your combined work in its +license notice, and that you preserve all their Warranty Disclaimers. + +The combined work need only contain one copy of this License, and +multiple identical Invariant Sections may be replaced with a single +copy. If there are multiple Invariant Sections with the same name but +different contents, make the title of each such section unique by +adding at the end of it, in parentheses, the name of the original +author or publisher of that section if known, or else a unique number. +Make the same adjustment to the section titles in the list of +Invariant Sections in the license notice of the combined work. + +In the combination, you must combine any sections Entitled "History" +in the various original documents, forming one section Entitled +"History"; likewise combine any sections Entitled "Acknowledgements", +and any sections Entitled "Dedications". You must delete all sections +Entitled "Endorsements". + + +6. COLLECTIONS OF DOCUMENTS + +You may make a collection consisting of the Document and other documents +released under this License, and replace the individual copies of this +License in the various documents with a single copy that is included in +the collection, provided that you follow the rules of this License for +verbatim copying of each of the documents in all other respects. + +You may extract a single document from such a collection, and distribute +it individually under this License, provided you insert a copy of this +License into the extracted document, and follow this License in all +other respects regarding verbatim copying of that document. + + +7. AGGREGATION WITH INDEPENDENT WORKS + +A compilation of the Document or its derivatives with other separate +and independent documents or works, in or on a volume of a storage or +distribution medium, is called an "aggregate" if the copyright +resulting from the compilation is not used to limit the legal rights +of the compilation's users beyond what the individual works permit. +When the Document is included in an aggregate, this License does not +apply to the other works in the aggregate which are not themselves +derivative works of the Document. + +If the Cover Text requirement of section 3 is applicable to these +copies of the Document, then if the Document is less than one half of +the entire aggregate, the Document's Cover Texts may be placed on +covers that bracket the Document within the aggregate, or the +electronic equivalent of covers if the Document is in electronic form. +Otherwise they must appear on printed covers that bracket the whole +aggregate. + + +8. TRANSLATION + +Translation is considered a kind of modification, so you may +distribute translations of the Document under the terms of section 4. +Replacing Invariant Sections with translations requires special +permission from their copyright holders, but you may include +translations of some or all Invariant Sections in addition to the +original versions of these Invariant Sections. You may include a +translation of this License, and all the license notices in the +Document, and any Warranty Disclaimers, provided that you also include +the original English version of this License and the original versions +of those notices and disclaimers. In case of a disagreement between +the translation and the original version of this License or a notice +or disclaimer, the original version will prevail. + +If a section in the Document is Entitled "Acknowledgements", +"Dedications", or "History", the requirement (section 4) to Preserve +its Title (section 1) will typically require changing the actual +title. + + +9. TERMINATION + +You may not copy, modify, sublicense, or distribute the Document except +as expressly provided for under this License. Any other attempt to +copy, modify, sublicense or distribute the Document is void, and will +automatically terminate your rights under this License. However, +parties who have received copies, or rights, from you under this +License will not have their licenses terminated so long as such +parties remain in full compliance. + + +10. FUTURE REVISIONS OF THIS LICENSE + +The Free Software Foundation may publish new, revised versions +of the GNU Free Documentation License from time to time. Such new +versions will be similar in spirit to the present version, but may +differ in detail to address new problems or concerns. See +http://www.gnu.org/copyleft/. + +Each version of the License is given a distinguishing version number. +If the Document specifies that a particular numbered version of this +License "or any later version" applies to it, you have the option of +following the terms and conditions either of that specified version or +of any later version that has been published (not as a draft) by the +Free Software Foundation. If the Document does not specify a version +number of this License, you may choose any version ever published (not +as a draft) by the Free Software Foundation. + + +ADDENDUM: How to use this License for your documents + +To use this License in a document you have written, include a copy of +the License in the document and put the following copyright and +license notices just after the title page: + + Copyright (c) YEAR YOUR NAME. + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.2 + or any later version published by the Free Software Foundation; + with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. + A copy of the license is included in the section entitled "GNU + Free Documentation License". + +If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, +replace the "with...Texts." line with this: + + with the Invariant Sections being LIST THEIR TITLES, with the + Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. + +If you have Invariant Sections without Cover Texts, or some other +combination of the three, merge those two alternatives to suit the +situation. + +If your document contains nontrivial examples of program code, we +recommend releasing these examples in parallel under your choice of +free software license, such as the GNU General Public License, +to permit their use in free software. diff --git a/faq/en/ChangeLog b/faq/en/ChangeLog new file mode 100644 index 0000000..b7bb11a --- /dev/null +++ b/faq/en/ChangeLog @@ -0,0 +1,92 @@ +2010-08-09 Petr Kovar + + * NEWS: Prepare for the FAQ_EN_2_2 release. + * faq_001.xml: Minor fixes. + * faq_003.xml: Ditto. + +2010-08-09 Petr Kovar + + * faq.xml: Second round of updates with regard to Sylpheed 3.1. + * faq_001.xml: Ditto. + * faq_002.xml: Ditto. + * faq_003.xml: Ditto. + +2010-08-04 Petr Kovar + + * faq_001.xml: Some fixes to the recent updates. + * faq_002.xml: Ditto. + * faq_003.xml: Ditto. + +2010-07-30 Petr Kovar + + * COPYING: Add a copy of the GFDL 1.2 to distribute it within release + tarball. + * LICENSE: Add a legal notice to distribute it within release tarball. + * faq_001.xml: First round of updates with regard to Sylpheed 3.1. + * faq_002.xml: Ditto. + * faq_003.xml: Ditto. + * sylpheed-faq.sgml: Remove old SGML FAQ document. + +2010-04-14 Petr Kovar + + * NEWS: Prepare for the FAQ_EN_2_1 release. + * faq.xml: Prepare for the FAQ_EN_2_1 release. + * faq_001.xml: Minor edits. + * faq_002.xml: Ditto. + * faq_003.xml: Ditto. + +2010-03-22 Petr Kovar + + * faq.xml: Updated with regard to Sylpheed 3.0.1. + * faq_001.xml: Ditto. + * faq_002.xml: Ditto. + * faq_003.xml: Ditto. + +2009-10-02 Petr Kovar + + * NEWS: Add the file & prepare for the FAQ_EN_2_0 release. + * faq.xml: Prepare for the FAQ_EN_2_0 release. + +2009-10-02 Petr Kovar + + * faq_001.xml: Minor addition. + +2009-10-01 Petr Kovar + + * faq.xml: Expanded question about key bindings, and other minor + edits across the FAQ. + * faq_001.xml: Ditto. + * faq_002.xml: Ditto. + * faq_003.xml: Ditto. + * faq_004.xml: Delete the obsolete file. + +2009-09-24 Petr Kovar + + * faq.xml: Change revision numbers to respect 'beta' and + 'stable'. + * faq_001.xml: Fix typo, thanks to Randy Dunlap. + +2009-09-18 Petr Kovar + + * *.xml: Updated several questions across the FAQ to conform + with Sylpheed 2.7.1, added couple of new ones. + +2009-08-31 Petr Kovar + + * *.xml: Even better formatting of qandaset tables. Markup + cleaning. + +2009-08-27 Petr Kovar + + * *.xml: Better formatting of qandaset tables. Still using + the shade.verbatim parameter for the IE compatibility's sake. + qandaset TOCs are now generated in each FAQ chunk. + +2009-08-23 Petr Kovar + + * *.xml: First round of very basic FAQ updates. + +2009-08-12 Petr Kovar + + * *.xml: Finished porting to DocBook XML. + * 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 @@ +Sylpheed FAQ + + Copyright (c) 2010 The Sylpheed Documentation Project. + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.2 + or any later version published by the Free Software Foundation; + with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. + A copy of the license is included in the file "COPYING". + 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 @@ +faqdatadir = $(faqdir)/en + +faqdata_DATA = \ + sylpheed-faq-1.html \ + sylpheed-faq-2.html \ + sylpheed-faq-3.html \ + sylpheed-faq-4.html \ + sylpheed-faq.html + +# generated by `ls -1 | sed -e 's/\(.*\)/ \1 \'` + +EXTRA_DIST = $(faqdata_DATA) \ + faq.xml \ + faq_001.xml \ + faq_002.xml \ + faq_003.xml \ + fdl.xml \ + 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 @@ +# Makefile.in generated by automake 1.14.1 from Makefile.am. +# @configure_input@ + +# Copyright (C) 1994-2013 Free Software Foundation, Inc. + +# This Makefile.in is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY, to the extent permitted by law; without +# even the implied warranty of MERCHANTABILITY or FITNESS FOR A +# PARTICULAR PURPOSE. + +@SET_MAKE@ + +VPATH = @srcdir@ +am__is_gnu_make = test -n '$(MAKEFILE_LIST)' && test -n '$(MAKELEVEL)' +am__make_running_with_option = \ + case $${target_option-} in \ + ?) ;; \ + *) echo "am__make_running_with_option: internal error: invalid" \ + "target option '$${target_option-}' specified" >&2; \ + exit 1;; \ + esac; \ + has_opt=no; \ + sane_makeflags=$$MAKEFLAGS; \ + if $(am__is_gnu_make); then \ + sane_makeflags=$$MFLAGS; \ + else \ + case $$MAKEFLAGS in \ + *\\[\ \ ]*) \ + bs=\\; \ + sane_makeflags=`printf '%s\n' "$$MAKEFLAGS" \ + | sed "s/$$bs$$bs[$$bs $$bs ]*//g"`;; \ + esac; \ + fi; \ + skip_next=no; \ + strip_trailopt () \ + { \ + flg=`printf '%s\n' "$$flg" | sed "s/$$1.*$$//"`; \ + }; \ + for flg in $$sane_makeflags; do \ + test $$skip_next = yes && { skip_next=no; continue; }; \ + case $$flg in \ + *=*|--*) continue;; \ + -*I) strip_trailopt 'I'; skip_next=yes;; \ + -*I?*) strip_trailopt 'I';; \ + -*O) strip_trailopt 'O'; skip_next=yes;; \ + -*O?*) strip_trailopt 'O';; \ + -*l) strip_trailopt 'l'; skip_next=yes;; \ + -*l?*) strip_trailopt 'l';; \ + -[dEDm]) skip_next=yes;; \ + -[JT]) skip_next=yes;; \ + esac; \ + case $$flg in \ + *$$target_option*) has_opt=yes; break;; \ + esac; \ + done; \ + test $$has_opt = yes +am__make_dryrun = (target_option=n; $(am__make_running_with_option)) +am__make_keepgoing = (target_option=k; $(am__make_running_with_option)) +pkgdatadir = $(datadir)/@PACKAGE@ +pkgincludedir = $(includedir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkglibexecdir = $(libexecdir)/@PACKAGE@ +am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd +install_sh_DATA = $(install_sh) -c -m 644 +install_sh_PROGRAM = $(install_sh) -c +install_sh_SCRIPT = $(install_sh) -c +INSTALL_HEADER = $(INSTALL_DATA) +transform = $(program_transform_name) +NORMAL_INSTALL = : +PRE_INSTALL = : +POST_INSTALL = : +NORMAL_UNINSTALL = : +PRE_UNINSTALL = : +POST_UNINSTALL = : +build_triplet = @build@ +host_triplet = @host@ +target_triplet = @target@ +subdir = faq/en +DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/Makefile.am \ + $(top_srcdir)/mkinstalldirs COPYING ChangeLog NEWS +ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 +am__aclocal_m4_deps = $(top_srcdir)/ac/aclocal-include.m4 \ + $(top_srcdir)/ac/gnupg-check-typedef.m4 \ + $(top_srcdir)/configure.ac +am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ + $(ACLOCAL_M4) +mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs +CONFIG_HEADER = $(top_builddir)/config.h +CONFIG_CLEAN_FILES = +CONFIG_CLEAN_VPATH_FILES = +AM_V_P = $(am__v_P_@AM_V@) +am__v_P_ = $(am__v_P_@AM_DEFAULT_V@) +am__v_P_0 = false +am__v_P_1 = : +AM_V_GEN = $(am__v_GEN_@AM_V@) +am__v_GEN_ = $(am__v_GEN_@AM_DEFAULT_V@) +am__v_GEN_0 = @echo " GEN " $@; +am__v_GEN_1 = +AM_V_at = $(am__v_at_@AM_V@) +am__v_at_ = $(am__v_at_@AM_DEFAULT_V@) +am__v_at_0 = @ +am__v_at_1 = +SOURCES = +DIST_SOURCES = +am__can_run_installinfo = \ + case $$AM_UPDATE_INFO_DIR in \ + n|no|NO) false;; \ + *) (install-info --version) >/dev/null 2>&1;; \ + esac +am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`; +am__vpath_adj = case $$p in \ + $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \ + *) f=$$p;; \ + esac; +am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`; +am__install_max = 40 +am__nobase_strip_setup = \ + srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'` +am__nobase_strip = \ + for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||" +am__nobase_list = $(am__nobase_strip_setup); \ + for p in $$list; do echo "$$p $$p"; done | \ + sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \ + $(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \ + if (++n[$$2] == $(am__install_max)) \ + { print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \ + END { for (dir in files) print dir, files[dir] }' +am__base_list = \ + sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \ + sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g' +am__uninstall_files_from_dir = { \ + test -z "$$files" \ + || { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \ + || { echo " ( cd '$$dir' && rm -f" $$files ")"; \ + $(am__cd) "$$dir" && rm -f $$files; }; \ + } +am__installdirs = "$(DESTDIR)$(faqdatadir)" +DATA = $(faqdata_DATA) +am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) $(LISP) +DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) +ACLOCAL = @ACLOCAL@ +ALLOCA = @ALLOCA@ +AMTAR = @AMTAR@ +AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@ +AR = @AR@ +AUTOCONF = @AUTOCONF@ +AUTOHEADER = @AUTOHEADER@ +AUTOMAKE = @AUTOMAKE@ +AWK = @AWK@ +BUILD_REVISION = @BUILD_REVISION@ +CATALOGS = @CATALOGS@ +CATOBJEXT = @CATOBJEXT@ +CC = @CC@ +CCDEPMODE = @CCDEPMODE@ +CFLAGS = @CFLAGS@ +CPP = @CPP@ +CPPFLAGS = @CPPFLAGS@ +CYGPATH_W = @CYGPATH_W@ +DATADIRNAME = @DATADIRNAME@ +DEFS = @DEFS@ +DEPDIR = @DEPDIR@ +DEVEL_VERSION = @DEVEL_VERSION@ +DLLTOOL = @DLLTOOL@ +DSYMUTIL = @DSYMUTIL@ +DUMPBIN = @DUMPBIN@ +ECHO_C = @ECHO_C@ +ECHO_N = @ECHO_N@ +ECHO_T = @ECHO_T@ +EGREP = @EGREP@ +EXEEXT = @EXEEXT@ +EXTRA_VERSION = @EXTRA_VERSION@ +FGREP = @FGREP@ +GETTEXT_PACKAGE = @GETTEXT_PACKAGE@ +GLIB_CFLAGS = @GLIB_CFLAGS@ +GLIB_COMPILE_RESOURCES = @GLIB_COMPILE_RESOURCES@ +GLIB_GENMARSHAL = @GLIB_GENMARSHAL@ +GLIB_LIBS = @GLIB_LIBS@ +GLIB_MKENUMS = @GLIB_MKENUMS@ +GMOFILES = @GMOFILES@ +GMSGFMT = @GMSGFMT@ +GOBJECT_QUERY = @GOBJECT_QUERY@ +GPGME_CFLAGS = @GPGME_CFLAGS@ +GPGME_CONFIG = @GPGME_CONFIG@ +GPGME_LIBS = @GPGME_LIBS@ +GREP = @GREP@ +GTK_CFLAGS = @GTK_CFLAGS@ +GTK_LIBS = @GTK_LIBS@ +INSTALL = @INSTALL@ +INSTALL_DATA = @INSTALL_DATA@ +INSTALL_PROGRAM = @INSTALL_PROGRAM@ +INSTALL_SCRIPT = @INSTALL_SCRIPT@ +INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@ +INSTOBJEXT = @INSTOBJEXT@ +INTLLIBS = @INTLLIBS@ +LD = @LD@ +LDAP_LIBS = @LDAP_LIBS@ +LDFLAGS = @LDFLAGS@ +LEX = @LEX@ +LEXLIB = @LEXLIB@ +LEX_OUTPUT_ROOT = @LEX_OUTPUT_ROOT@ +LIBICONV = @LIBICONV@ +LIBOBJS = @LIBOBJS@ +LIBS = @LIBS@ +LIBSYLPH_CFLAGS = @LIBSYLPH_CFLAGS@ +LIBSYLPH_LIBS = @LIBSYLPH_LIBS@ +LIBTOOL = @LIBTOOL@ +LIPO = @LIPO@ +LN_S = @LN_S@ +LTLIBICONV = @LTLIBICONV@ +LTLIBOBJS = @LTLIBOBJS@ +LT_AGE = @LT_AGE@ +LT_CURRENT = @LT_CURRENT@ +LT_RELEASE = @LT_RELEASE@ +LT_REVISION = @LT_REVISION@ +MAINT = @MAINT@ +MAJOR_VERSION = @MAJOR_VERSION@ +MAKEINFO = @MAKEINFO@ +MANIFEST_TOOL = @MANIFEST_TOOL@ +MICRO_VERSION = @MICRO_VERSION@ +MINOR_VERSION = @MINOR_VERSION@ +MKDIR_P = @MKDIR_P@ +MKINSTALLDIRS = @MKINSTALLDIRS@ +MSGFMT = @MSGFMT@ +MSGFMT_OPTS = @MSGFMT_OPTS@ +NM = @NM@ +NMEDIT = @NMEDIT@ +OBJDUMP = @OBJDUMP@ +OBJEXT = @OBJEXT@ +OPENSSL_CFLAGS = @OPENSSL_CFLAGS@ +OPENSSL_LIBS = @OPENSSL_LIBS@ +OTOOL = @OTOOL@ +OTOOL64 = @OTOOL64@ +PACKAGE = @PACKAGE@ +PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@ +PACKAGE_NAME = @PACKAGE_NAME@ +PACKAGE_STRING = @PACKAGE_STRING@ +PACKAGE_TARNAME = @PACKAGE_TARNAME@ +PACKAGE_URL = @PACKAGE_URL@ +PACKAGE_VERSION = @PACKAGE_VERSION@ +PATH_SEPARATOR = @PATH_SEPARATOR@ +PKG_CONFIG = @PKG_CONFIG@ +PKG_CONFIG_LIBDIR = @PKG_CONFIG_LIBDIR@ +PKG_CONFIG_PATH = @PKG_CONFIG_PATH@ +POFILES = @POFILES@ +POSUB = @POSUB@ +PO_IN_DATADIR_FALSE = @PO_IN_DATADIR_FALSE@ +PO_IN_DATADIR_TRUE = @PO_IN_DATADIR_TRUE@ +RANLIB = @RANLIB@ +SED = @SED@ +SET_MAKE = @SET_MAKE@ +SHELL = @SHELL@ +STRIP = @STRIP@ +SYLPHEED_LIBS = @SYLPHEED_LIBS@ +USE_NLS = @USE_NLS@ +VERSION = @VERSION@ +WINDRES = @WINDRES@ +XGETTEXT = @XGETTEXT@ +YACC = @YACC@ +YFLAGS = @YFLAGS@ +abs_builddir = @abs_builddir@ +abs_srcdir = @abs_srcdir@ +abs_top_builddir = @abs_top_builddir@ +abs_top_srcdir = @abs_top_srcdir@ +ac_ct_AR = @ac_ct_AR@ +ac_ct_CC = @ac_ct_CC@ +ac_ct_DUMPBIN = @ac_ct_DUMPBIN@ +am__include = @am__include@ +am__leading_dot = @am__leading_dot@ +am__quote = @am__quote@ +am__tar = @am__tar@ +am__untar = @am__untar@ +bindir = @bindir@ +build = @build@ +build_alias = @build_alias@ +build_cpu = @build_cpu@ +build_os = @build_os@ +build_vendor = @build_vendor@ +builddir = @builddir@ +datadir = @datadir@ +datarootdir = @datarootdir@ +docdir = @docdir@ +dvidir = @dvidir@ +exec_prefix = @exec_prefix@ +faqdir = @faqdir@ +host = @host@ +host_alias = @host_alias@ +host_cpu = @host_cpu@ +host_os = @host_os@ +host_vendor = @host_vendor@ +htmldir = @htmldir@ +includedir = @includedir@ +infodir = @infodir@ +install_sh = @install_sh@ +libdir = @libdir@ +libexecdir = @libexecdir@ +localedir = @localedir@ +localstatedir = @localstatedir@ +mandir = @mandir@ +manualdir = @manualdir@ +mkdir_p = @mkdir_p@ +oldincludedir = @oldincludedir@ +pdfdir = @pdfdir@ +plugindir = @plugindir@ +prefix = @prefix@ +program_transform_name = @program_transform_name@ +psdir = @psdir@ +sbindir = @sbindir@ +sharedstatedir = @sharedstatedir@ +srcdir = @srcdir@ +sysconfdir = @sysconfdir@ +target = @target@ +target_alias = @target_alias@ +target_cpu = @target_cpu@ +target_os = @target_os@ +target_vendor = @target_vendor@ +themedir = @themedir@ +top_build_prefix = @top_build_prefix@ +top_builddir = @top_builddir@ +top_srcdir = @top_srcdir@ +faqdatadir = $(faqdir)/en +faqdata_DATA = \ + sylpheed-faq-1.html \ + sylpheed-faq-2.html \ + sylpheed-faq-3.html \ + sylpheed-faq-4.html \ + sylpheed-faq.html + + +# generated by `ls -1 | sed -e 's/\(.*\)/ \1 \'` +EXTRA_DIST = $(faqdata_DATA) \ + faq.xml \ + faq_001.xml \ + faq_002.xml \ + faq_003.xml \ + fdl.xml \ + LICENSE + +all: all-am + +.SUFFIXES: +$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.am $(am__configure_deps) + @for dep in $?; do \ + case '$(am__configure_deps)' in \ + *$$dep*) \ + ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \ + && { if test -f $@; then exit 0; else break; fi; }; \ + exit 1;; \ + esac; \ + done; \ + echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign faq/en/Makefile'; \ + $(am__cd) $(top_srcdir) && \ + $(AUTOMAKE) --foreign faq/en/Makefile +.PRECIOUS: Makefile +Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status + @case '$?' in \ + *config.status*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \ + *) \ + echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \ + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \ + esac; + +$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh + +$(top_srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(am__configure_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ $(am__aclocal_m4_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(am__aclocal_m4_deps): + +mostlyclean-libtool: + -rm -f *.lo + +clean-libtool: + -rm -rf .libs _libs +install-faqdataDATA: $(faqdata_DATA) + @$(NORMAL_INSTALL) + @list='$(faqdata_DATA)'; test -n "$(faqdatadir)" || list=; \ + if test -n "$$list"; then \ + echo " $(MKDIR_P) '$(DESTDIR)$(faqdatadir)'"; \ + $(MKDIR_P) "$(DESTDIR)$(faqdatadir)" || exit 1; \ + fi; \ + for p in $$list; do \ + if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \ + echo "$$d$$p"; \ + done | $(am__base_list) | \ + while read files; do \ + echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(faqdatadir)'"; \ + $(INSTALL_DATA) $$files "$(DESTDIR)$(faqdatadir)" || exit $$?; \ + done + +uninstall-faqdataDATA: + @$(NORMAL_UNINSTALL) + @list='$(faqdata_DATA)'; test -n "$(faqdatadir)" || list=; \ + files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \ + dir='$(DESTDIR)$(faqdatadir)'; $(am__uninstall_files_from_dir) +tags TAGS: + +ctags CTAGS: + +cscope cscopelist: + + +distdir: $(DISTFILES) + @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + list='$(DISTFILES)'; \ + dist_files=`for file in $$list; do echo $$file; done | \ + sed -e "s|^$$srcdirstrip/||;t" \ + -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \ + case $$dist_files in \ + */*) $(MKDIR_P) `echo "$$dist_files" | \ + sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \ + sort -u` ;; \ + esac; \ + for file in $$dist_files; do \ + if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ + if test -d $$d/$$file; then \ + dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d "$(distdir)/$$file"; then \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ + if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ + cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ + cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \ + else \ + test -f "$(distdir)/$$file" \ + || cp -p $$d/$$file "$(distdir)/$$file" \ + || exit 1; \ + fi; \ + done +check-am: all-am +check: check-am +all-am: Makefile $(DATA) +installdirs: + for dir in "$(DESTDIR)$(faqdatadir)"; do \ + test -z "$$dir" || $(MKDIR_P) "$$dir"; \ + done +install: install-am +install-exec: install-exec-am +install-data: install-data-am +uninstall: uninstall-am + +install-am: all-am + @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am + +installcheck: installcheck-am +install-strip: + if test -z '$(STRIP)'; then \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + install; \ + else \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \ + fi +mostlyclean-generic: + +clean-generic: + +distclean-generic: + -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES) + +maintainer-clean-generic: + @echo "This command is intended for maintainers to use" + @echo "it deletes files that may require special tools to rebuild." +clean: clean-am + +clean-am: clean-generic clean-libtool mostlyclean-am + +distclean: distclean-am + -rm -f Makefile +distclean-am: clean-am distclean-generic + +dvi: dvi-am + +dvi-am: + +html: html-am + +html-am: + +info: info-am + +info-am: + +install-data-am: install-faqdataDATA + +install-dvi: install-dvi-am + +install-dvi-am: + +install-exec-am: + +install-html: install-html-am + +install-html-am: + +install-info: install-info-am + +install-info-am: + +install-man: + +install-pdf: install-pdf-am + +install-pdf-am: + +install-ps: install-ps-am + +install-ps-am: + +installcheck-am: + +maintainer-clean: maintainer-clean-am + -rm -f Makefile +maintainer-clean-am: distclean-am maintainer-clean-generic + +mostlyclean: mostlyclean-am + +mostlyclean-am: mostlyclean-generic mostlyclean-libtool + +pdf: pdf-am + +pdf-am: + +ps: ps-am + +ps-am: + +uninstall-am: uninstall-faqdataDATA + +.MAKE: install-am install-strip + +.PHONY: all all-am check check-am clean clean-generic clean-libtool \ + cscopelist-am ctags-am distclean distclean-generic \ + distclean-libtool distdir dvi dvi-am html html-am info info-am \ + install install-am install-data install-data-am install-dvi \ + install-dvi-am install-exec install-exec-am \ + install-faqdataDATA install-html install-html-am install-info \ + install-info-am install-man install-pdf install-pdf-am \ + install-ps install-ps-am install-strip installcheck \ + installcheck-am installdirs maintainer-clean \ + maintainer-clean-generic mostlyclean mostlyclean-generic \ + mostlyclean-libtool pdf pdf-am ps ps-am tags-am uninstall \ + uninstall-am uninstall-faqdataDATA + + +# Tell versions [3.59,3.63) of GNU make to not export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.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 @@ +Sylpheed FAQ revision 2.2 released on 2010-08-09 +================================================ + +New revision of Sylpheed FAQ has been officially released from the Sylpheed +Documentation Project to reflect changes in the upcoming Sylpheed 3.1. + +You can view the FAQ either as a multi-page or single-page HTML document at: + +http://sylpheeddoc.sourceforge.net/en/doc_faq.html + +Or download it together with source DocBook XML files in a .tar.gz or .zip +archive from: + +https://sourceforge.net/projects/sylpheeddoc/files/ + +The source DocBook XML files are also available in the Project CVS repository, +see: + +https://sourceforge.net/scm/?type=cvs&group_id=20952 + + +Changes over the past 4 months +------------------------------ + +* New Q&A "Can I run multiple instances of Sylpheed?" +* New Q&A "Execute command for my dynamic signature seems not to be working!" +* Updated Q&A on environment variables +* Updated Q&A on automatic name completion +* Updated Q&A on Sylpheed plug-ins +* Other minor edits throughout the document +* To better comply with the GFDL license, the source DocBook XML files together + with the plain text copy of the GFDL license and appropriate legal notice are + now distributed in tarballs with each documentation release, and the exact way + of how to obtain the source files is mentioned explicitly in the document; + thanks to Ricardo Mones for pointing these legal issues out + +All other information on the Sylpheed Documentation Project including how to +contribute to the documentation effort is available at: + +http://sylpheeddoc.sourceforge.net/ + + +Contributors to this and previous releases +------------------------------------------ + +Paul Kater, Jens Oberender, Francois Barriere, Olivier Delhomme, Petr Kovar + + +Enjoy! + + +Sylpheed FAQ revision 2.1 released on 2010-04-14 +================================================ + +New revision of Sylpheed FAQ has been officially released from the Sylpheed +Documentation Project to reflect changes in Sylpheed 3.0. + +You can view the FAQ either as a multi-page or single-page HTML document at: + +http://sylpheeddoc.sourceforge.net/en/doc_faq.html + +Or download it in a .tar.gz or .zip archive from: + +https://sourceforge.net/projects/sylpheeddoc/files/ + +DocBook XML source files are available in the Project CVS repository, see: + +https://sourceforge.net/scm/?type=cvs&group_id=20952 + + +Changes over the past 6 months +------------------------------ + +* New Q&A regarding new mail retrieval +* New Q&A regarding Sylpheed plug-in interface +* New Q&A on disabling/enabling the alternating row colors in the message list +* Updated Q&A on setting up a new account +* Corrected configuration directory paths under Windows Vista/Seven +* Other minor edits throughout the document + +All other information on the Sylpheed Documentation Project including how to +contribute to the documentation effort is available at: + +http://sylpheeddoc.sourceforge.net/ + + +Contributors to this and previous releases +------------------------------------------ + +Paul Kater, Jens Oberender, Francois Barriere, Olivier Delhomme, Petr Kovar + + +Enjoy! + + +Sylpheed FAQ revision 2.0 released on 2009-10-02 +================================================ + +After a couple of dormant years, the Sylpheed FAQ has been officially released +from the Sylpheed Documentation Project. + +You can view the FAQ either as a multi-page or single-page HTML document at: + +http://sylpheeddoc.sourceforge.net/en/doc_faq.html + +Or download it in a .tar.gz archive from: + +https://sourceforge.net/projects/sylpheeddoc/files/ + +DocBook XML source files are available in the Project CVS repository, see: + +https://sourceforge.net/scm/?type=cvs&group_id=20952 + + +Changes over the past 6 years +----------------------------- + +* Many questions across the document have been updated to conform with the + latest Sylpheed version 2.7.1 +* The document has been migrated from LinuxDoc SGML to DocBook XML +* The document is now licensed under the terms of the GFDL 1.2 or later + (was 1.1 or later) +* A copy of the GFDL 1.2 is now distributed with the FAQ + +All other information on the Sylpheed Documentation Project including how to +contribute to the documentation effort is available at: + +http://sylpheeddoc.sourceforge.net/ + + +Contributors to this and previous releases +------------------------------------------ + +Paul Kater, Jens Oberender, Francois Barriere, Olivier Delhomme, Petr Kovar + + +Enjoy! 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 @@ + + + + + +]> + + Sylpheed FAQ + + + 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. + + + 2010 + The Sylpheed Documentation Project. + + + Permission is granted to copy, distribute and/or modify this + document under the terms of the GNU Free Documentation License, Version + 1.2 or any later version published by the Free Software Foundation; with + no Invariant Sections, with no Front-Cover Texts, and no Back-Cover + Texts. A copy of the license is included in the section entitled "GNU + Free Documentation License". + + + + Paul + Kater + + + Jens + Oberender + + + Francois + Barriere + + + Olivier + Delhomme + + + Petr + Kovar + + + + 1.9 + 2005/07/08 + OD + Ported to DocBook XML. + + + 2.0 + 2009/10/02 + PK + Finished porting to DocBook XML, updated many questions across the document to conform with Sylpheed 2.7.1. + + + 2.1 + 2010/04/14 + PK + Updated with regard to Sylpheed 3.0.2. + + + 2.2 + 2010/08/09 + PK + Updates for the upcoming Sylpheed 3.1. + + + +&__faq__001;&__faq__002;&__faq__003;&__license; 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 @@ + + Sylpheed FAQ - General Information + + + + + Are there FAQ's in other languages? + + + + + Yes. Here are links to several translations: + + + Sylpheed FAQ in French, translated by Olivier Delhomme. + + + Sylpheed FAQ in German, translated by Nicolas Kaiser. + + + Sylpheed FAQ in Spanish, translated by Ricardo Mones Lastra. + + + Sylpheed FAQ in Traditional Chinese, courtesy of Franklin. + + + + You can always download this FAQ from the Sylpheed Documentation Project website. + + 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 their website. Thanks in advance. + + + + + + + What is Sylpheed? + + + + + Sylpheed is an email client (and news reader) based on GTK+, + running on the X Window System or Microsoft Windows, and aiming for: + + + Quick response + + + Graceful, and sophisticated interface + + + Easy configuration, intuitive operation + + + High reliability + + + Internationalization and multilingualization support + + + Abundant features + + + As the Sylpheed README file reads: The appearance and interface are similar to some popular e-mail clients for +Windows, such as Outlook Express or Becky!. Many commands are accessible with +the keyboard like the Emacs-based mailers such as Mew and Wanderlust. +So you will be able to migrate to Sylpheed without much discomfort, even if +you are accustomed to other mailers. + + + + + + Where can I get Sylpheed? + + + + + You can download it from the download page on Sylpheed website. There are links to download + tarball sources, patches to the previous version, and also links to the Sylpheed for Windows binaries, including the installer, the ZIP archive, and the patch to the previous Sylpheed for Windows version. + Depending on the state of the Sylpheed development cycle, you may be offered links to development versions such as beta and RC releases. These might not be suitable for everyday use, however, so you may want to stick with the stable release, anyway. + Also on the download page, you can download Sylph-Searcher (which is a program that enables fast full-text search of messages stored in mailboxes of Sylpheed, or normal MH folders), and LibSylph (which is a library that provides Sylpheed core features independent from the UI of Sylpheed). + + + + + + Who writes Sylpheed? + + + + + Hiroyuki Yamamoto hiro-y@kcn.ne.jp. + + + + + + + What does the name Sylpheed mean? + + + + + It means light weight, like air. This comes from the + name of the wind spirits, the Sylphs. + + + + + + + How does Sylpheed store mails? + + + + + Mails are stored in the MH mailfile format as used by MH + and EMH. Maildir, mbox, and eml formats are not (yet) + supported, although it is possible to import an mbox + file or an eml file into a Sylpheed mailbox. + You can manage your mails just with Sylpheed, or together with another mailer based on the MH format (e.g. Mew). The MH format has less possibility +of losing mails on failures since one file corresponds to one mail. You can also utilize fetchmail +and/or procmail, and external programs on receiving (like inc or imget). + + + + + + Why does the auto collection of mail not work? + + + + + Auto collection works since version 0.5.1. If you need it + or want it, you should upgrade. + + + + + + + Does Sylpheed have mail filtering? + + + + + Yes. You can find it in Configuration -> Filter settings... + + Please note that filtering is not yet implemented for IMAP accounts. + + + + + + + Can Sylpheed handle IMAP mail? + + + + + Yes. As of version 0.4.99 IMAP is supported. + + + + + + + Can Sylpheed handle local unix mailboxes? + + + + + Yes. + + + + + + + Can Sylpheed handle IPv6? + + + + + Yes, IPv6 is fully supported in Sylpheed. + + + + + + + Does Sylpheed support encryption like GPG? + + + + + Yes. GPG is implemented and works fine. For activating it in Sylpheed, + see the appropriate question in the Installation section. + + + + + + + How does Sylpheed check for MIME types? + + + + + Sylpheed uses the Mutt type of mime checking. + + + + + + Does Sylpheed allow me to write HTML styled messages? + + + + + No. A discussion has gone around over this topic, and + the outcome was that HTML mail is not wanted. If you + really need to send HTML, you can of course attach a + web page to an email. + + + + + Does Sylpheed have automatic name completion in the address fields? + + + + + Yes. When you search for a name that starts with "don", + type "don" (without the quotes) and it will show you the correct name (when only one "don" + exists in your address book. Otherwise a drop-down list + appears, which allows you to select the name you want. + E.g. Donald Duck, Don Johnson. But also email addresses + starting with "don" will appear in the list (like + "don.giovanni@maffia.org"). + Prior to Sylpheed 3.1, users needed to press the Tab key before the search would start. If you still prefer the previous behavior, you can enable it by checking + Configuration + Common preferences... + Details + Other + Address book + Address auto-completion: + Start with Tab + . + + + + + Fine, but when I hit the Tab key I either get an error message or nothing happens at all. + + + + + When you want to use name completion, make sure that + there are names in your address book. If there are no + names, even Sylpheed has a hard time completing + something. + 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: + Configuration + Common preferences... + Details + Other + Address book + Address auto-completion: + Disabled + . + + + + + Why is Sylpheed so fast? + + + + That's what it is designed for! + + + + + + Where can I get the current patches for Sylpheed? + + + + In most cases, current patches are being posted by Sylpheed users and contributors to the Sylpheed mailing list sylpheed@sraoss.jp. + (Also see the Installation section on how to install a patch.) + + + + + + How can I send in patches, report bugs, talk about Sylpheed with others? + + + + To talk to others, you should join the Sylpheed mailing + list at + http://www.sraoss.jp/mailman/listinfo/sylpheed + . Note that there is + a Japanese and an English list, so pick the right one! + If you have made a patch that you want the world to know + of, please post it either to the mailing list, or contact the Sylpheed author, Hiroyuki Yamamoto hiro-y@kcn.ne.jp. + Please supply the information of + Tools + Log window + , or the contents of +sylpheed.log, which is located under the configuration folder, when +reporting bugs. + + + + + When I send mail, the Content-Type header says the mail is in + US-ASCII, even when I specified ISO-8859-1? + + + + If ISO-8859-1 characters (>= 0x80) are not used in the + message body, Sylpheed will automatically set the + charset value in the Content-Type header as US-ASCII. + + + + + + Why does it look like word wrap is not working? + + + + Word wrapping is a bit peculiar perhaps. You can type + lines as long as you like. By the time you send or queue + a mail with long lines, Sylpheed will first wrap the + lines to the line length you set up, and then the mail + is queued. This is more convenient than you think. Once + a line is wrapped (hard line breaks are inserted in the + text) and you add something in a line there, the next + line will move to a separate new line, leaving one or + two words from the previous line "hanging there" alone. + E.g. + This is a long line that + is wrapped. Now you add one word in the first line: + This is a very long line + that + is wrapped This would cause you a lot of manual reformatting to get + a presentable mail again. + + + + As of Sylpheed 0.8.0., active word wrap has been + implemented. You can turn it on in + Common Preferences + Compose + Editor + Wrap on input + . + + + + + + + How do I copy my mail archive to another machine? + + + You need to copy the sylpheed-2.0 directory with your user profile, and your entire local mail archive. + Under UNIX, the user profile is stored in $HOME/.sylpheed-2.0 by default, and your local mail archive is by default located in $HOME/Mail. + While under Windows 2000/XP, the user profile is stored in C:\Documents and Settings\(user name)\Application Data\Sylpheed by default, and your local mail archive is by default located in C:\Documents and Settings\(user name)\Application Data\Sylpheed\Mailboxes\Mail. + Under Windows Vista/Seven, the directory paths are C:\Users\(user name)\AppData\Roaming\Sylpheed, and C:\Users\(user name)\AppData\Roaming\Sylpheed\Mailboxes\Mail, respectively. + + + + + Can I import a mbox into Sylpheed's MH mailfolders? + + + + + Yes, just create/select the folder you want your + mails in, and select Import mbox file... in the File + menu. + + + + + + Can I use procmail to sort my mails with the MH mail handling? + + + + + Yes. Just make sure that you add /. to the end of a rule so + procmail knows you are filtering into an MH mail folder. Example: + + 0: +* ^Subject:.*sylpheed +sylpheedmail/. + + Check man procmail for details. + + + + + + + When I upgrade Sylpheed, are there things I should be aware of? + + + + + Yes! + + + Upgrade to 0.4.50: you should reconfigure your newsgroup settings + + + Upgrade to 0.4.63: you should set the URL string colors from the Configuration menu + + + Upgrade to 0.4.65: some menu items have been moved + + + Upgrade to 0.7.3: many key bindings have changed + + + 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 + + + You should always read the NEWS document (and also NEWS-x.0 if you are upgrading from a very old version) that is included in the release tarballs. The NEWS can also be viewed on the appropriate Sylpheed website page. + + + + + How can I quickly update the views in Sylpheed? + + + + + Just press + Alt + U + or select Update summary from the View menu. + + + + + + Why can't I use gvim as external editor? + + + + + If one wishes to use gvim as an external editor it's + necessary to start it with the no-fork option -f, i.e. + in the configuration dialog box you need to enter + gvim -f %s. If not the editor forks and open up a + separate file and when one quits the editor the changes + are lost and don't show up in the composer window. + (Thanks, Ed Collins!) + + + + + + Can I quote just parts of the original message when replying? + + + + + Yes, select the part in the text view and choose Reply. + + + + + + Can I reply without quoting at all? + + + + You need to disable quoting by editing the reply format under + Configuration + Common preferences + Compose tab + Format tab + + (also works with + forward format which you can see below the reply format in the configuration dialog). + + + + + Does Sylpheed provide an anti-spam feature? + + + Yes. It has a bogofilter and a bsfilter support. Just go to + Configuration + Common preferences... + Junk mail + and check Enable Junk mail control. Then you can select a Learning command preset of your choice, or possibly use custom commands. + You can also use other spam filters thanks to the Actions functionality (available under + Configuration + Actions... + ). + + 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). + + + + + + Are there any plug-ins extending standard Sylpheed functionality? + + + As of Sylpheed 3.1, there is an Attachment Tool Plug-in distributed with the Sylpheed source code and available under plugin/attachment_tool/. Its only function is to remove attachments from +selected 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. + There is a page on the Sylpheed website dedicated to the plug-in interface. Additionally, the PLUGIN.txt file distributed directly with Sylpheed can provide you with some basic information on the topic. + + If you are a developer interested in creating plug-ins for Sylpheed, see the plug-in specification on the Sylpheed wiki. + + + + + + Where I can find the latest Sylpheed FAQ and manual? + + + + + Go to http://sylpheeddoc.sourceforge.net and check out + the FAQ and manual from the Sylpheed Documentation Project (sylpheeddoc). Both + documents are available in multiple languages there and + usually contain the latest updates. The direct links are as follows: + + + current version of the English FAQ + + + current version of the English manual + + + Also see the question about available language versions at the top of this section. + + + + + Where I can obtain source files for this document? + + + The source DocBook XML files in which this document is written can be obtained from a public CVS repository that is part of the Sylpheed Documentation Project. The source files with all the necessary build system, XSL stylesheets or snapshots are stored under the "doc" 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): + cvs -d:pserver:anonymous@sylpheeddoc.cvs.sourceforge.net:/cvsroot/sylpheeddoc login + cvs -z3 -d:pserver:anonymous@sylpheeddoc.cvs.sourceforge.net:/cvsroot/sylpheeddoc co -P doc + The source files are also included in .tar.gz and .zip archives made available with each documentation release, these can be downloaded from the appropriate project page. For more information on the used project infrastructure, please see the project website. + + + + + I have found an error and/or outdated information in this document! + + + Please report any errors, misleading and/or outdated information to the Sylpheed Documentation Project. You can see the list of Project members in the following question, so you can also contact them directly. + + + + + Who are the members of the Sylpheed Documentation Project? + + + The current members of the Sylpheed Documentation Project are: + Francois Barriere fbarriere at users.sourceforge.net +Petr Kovar pknbe at users.sourceforge.net + Below is the list of former members of the Sylpheed Documentation Project. Big thank you goes to all of them! + Martin Bretschneider furbour at users.sourceforge.net +Olivier Delhomme dup at users.sourceforge.net +Doruk Fisek dobidik at users.sourceforge.net +Melvin Hadasht mhadasht at users.sourceforge.net +Nicolas Kaiser nikai at users.sourceforge.net +Paul Kater pkater at users.sourceforge.net +Ricardo Mones Lastra mones at users.sourceforge.net +Jens Oberender jobi at users.sourceforge.net +Marcelo Ramos hackpando at users.sourceforge.net +Guido Rudolphi malatesta at users.sourceforge.net +Frank Weng fweng at users.sourceforge.net + + + + 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 @@ + + Sylpheed FAQ - Installation and Configuration + + + + What does it take to compile Sylpheed? + + + Any POSIX compliant UNIX or similar OS, e.g. Linux, +FreeBSD, Solaris. +GTK+ 2.4.0 or later (GTK+ 2.6.0 or later +is recommended). +A recent ANSI C compiler (gcc 2.7.2.3 should also +work). + + It is reported that Sun C will not compile +Sylpheed. + + Optionally: + + + compface (for X-Face) + + + GPGME (for GnuPG) + + + OpenSSL for SSL support + + + GtkSpell for a spell checking feature + + + cURL for allowing Sylpheed to check for updates + + + JPilot + + + LDAP + + + the equivalent of GTK+-devel and Xfree86-devel + + + you may also require flex (lex) and bison +(yacc). + + + Otherwise ./configure will fail. +See also the INSTALL file that is being distributed with the Sylpheed tarball. + Note that as Sylpheed now supports the Windows platform, you can also compile it using MinGW. + + + + + How do I set up Sylpheed? + + + When you run Sylpheed for the first time, it will +ask you where you want to store your mailboxes. The +default is $HOME/Mail (or %APPDATA%\Sylpheed\Mailboxes\Mail under Windows). You can change this to +anything you like as long as it is a valid directory +name. + + When Sylpheed is executed for the first time, it automatically creates the configuration files under $HOME/.sylpheed-2.0/ (or %APPDATA%\Sylpheed\ under Windows), and asks you the location of mailbox. As stated above, the default is $HOME/Mail, or %APPDATA%\Sylpheed\Mailboxes\Mail under Windows. If some files, which are non-MH format, already exist on the directory, you will have to specify another location. + + Furthermore, you need to create at least one account to be able to receive or send messages. + + + + + Why did the creation of the mailbox fail? + + + Sylpheed reports such an error if it can't create the default +mailboxes (inbox, outbox, etc.). This can be because $HOME/Mail +(or %APPDATA%\Sylpheed\Mailboxes\Mail under Windows) already contains files with the same names. This occurs when switching from +Kmail to Sylpheed, in this case backup and remove the existing Mail +directory or use another name for the Sylpheed mail directory. + + + + + How do I set up an account? + + + After loading Sylpheed for the first time, you can +add an email account by clicking the Configuration menu. Select the option Create new account and let the configuration assistant help you with the initial setup. +In a few easy steps, the assistant allows you to conveniently configure your POP3, IMAP4, or Gmail account. + + If you want later to change your account configuration, just select + Configuration + Preferences for current account... + , or + Configuration + Edit accounts... + + + + + + + How many accounts can I set up in Sylpheed? + + + The number is unlimited. The limit is reached when +your computer stops responding. + + + + + Can I set up an account for sending mail only? + + + Yes, add a new account using + Configuration + Edit accounts... + Add + and set the Protocol to None (local). + + + + + Why does Sylpheed not delete my mails when I press "Delete"? I set a filter, and Sylpheed does not filter. I moved a mail to a different mailbox and it did not move. + + + You have to click the Execute button. +The other solution: in the configuration settings +( + Common preferences... + Details + Interface + ), you have to +check the Execute immediately when moving or deleting messages box. + + + + + Can I set up special addresses/ports for my mailserver/newsserver? + + + Yes, you can. Under + Configuration + Preferences for current account... + Advanced + , you +can specify the exact port addresses you want to use. + + + + + Does Sylpheed have options for threading messages? + + + Yes. You can switch it on and off in the View + menu, just select Thread view or press + Ctrl + T + . + + + + + Can I create multiple levels of subfolders to store mail? + + + Absolutely. This is no problem. + + + + + Why isn't Sylpheed sending my mail out? + + + You need to create at least one account in order to + send. (This is a wonderful gotcha on LAN installs + with only a local mailbox feed). + + + + + How do I apply a patch after downloading it? + + + Copy patch to sylpheed directory. + Apply the patch as follows: + + % patch -p0 < some.patch + + Or, if it's gzipped: + + % gzip -dc some.patch.gz | patch -p0 + + Run ./autogen.sh, remove the generated /config.cache + file (unless you want to install in prefix + /usr/local). + Run ./configure with the appropriate options and + then make. + (Text as found on the former Sylpheed patches page.) + + + + + How do I compile in support for compface pictures? + + + You have to have a package called libcompface + installed, so this is available for compiling into + Sylpheed. Note that the exact name of the package depends on OS or distribution you use. + + + + + How do I make my own compface image? + + + The faces package contains a program called xbm2ikon script, + which converts a 48x48 xbm to the format suitable for + compface. Thanks to Jeff Dairiki, you can have a complete online course in this. Visit this page for the details. + + + + + How can I tell my browser/newsclient/other program to use Sylpheed as email program? + + + In the settings part of the program, write + sylpheed --compose + +Specific options for typical browsers: + + + Opera: sylpheed --compose [mailto:%t][?subject=%s] + + + Galeon: sylpheed --compose "mailto:%t?subject=%s" + + + + + + + How do I enable GPG support in Sylpheed? + + + When compiling Sylpheed, make sure you add --enable-gpgme in the ./configure command. +When that completes successfully, there is a Privacy section in the Common Preferences. + + + + + Mutt does not recognize Sylpheed's MH structure + + + For this to work you need to use the touch command in every MH folder. "touch" the file .xmhcache and Mutt should do just fine. + + + + + Viewing a GIF file within Sylpheed causes a segmentation fault. + + + In case this happens, you can easily fix that by adding the following to /etc/mime.types: + image/gif gif + + + + + How Sylpheed checks for new mail? + + + New mail can be retrieved either manually or automatically. + To check for new mail the manual way, you can: + + + Either press the Get button on the toolbar to incorporate new mail for the current account only, or use the Get all button to incorporate new mail for all configured accounts. + + + Or choose + File + Mailbox + Check for new messages + , or Check for new messages in all mailboxes. + + + Or select + Message + Receive + Get from current account + , or Get from all accounts. + + + + If you have a POP3 account and don't want to retrieve all the new messages stored on remote server to your computer, you can manage your account remotely (e.g. open or delete individual messages) by choosing + Message + Receive + Remote mailbox... + + + If you prefer autochecking for new mail instead, first of all, make sure that you have checked + Configuration + Common preferences... + Receive + Autocheck new mail every 10 minute(s) + . Optionally, you can adjust the interval value (in minutes) as well. + Also check your settings under + Configuration + Edit accounts... + You will find this +at the top: Check the boxes on the 'G' column to enable message retrieval by 'Get all'. The setting applies on both manual and automatic +mail checks. + + + + + How can I make Sylpheed notify me when new mail arrives? + + + Download Gkrellm or a similar program that is able to notify you of new incoming mail. Gkrellm is available at the Gkrellm page. + + + + + Can I use a spell checker with Sylpheed? + + + Yes. You need to have GtkSpell installed prior to Sylpheed compilation. The support for GtkSpell is enabled by default in configure. (If you want to disable it, make sure you add --disable-gtkspell in the ./configure command.) + The GtkSpell option is not supported in Sylpheed for Windows (yet), so you will have no spell checking under this OS. + + + + + How can I make Sylpheed send my compface image in the mails? + + + In the + Configuration + Preferences for current account... + Send + check Add user-defined header and press Edit button. A dialog appears, add a header named "X-Face" and fill the value field with your face data. Note that if you paste the data from a terminal into the field, some spurious newlines can be added, and these can mangle your face, be careful. + + + + + How can I get the newest source code from the Sylpheed Subversion (SVN) repository? + + + Move to an appropriate directory, and after you run the command specified below, a source tree named trunk will be created under that directory: + svn checkout svn://sylpheed.sraoss.jp/sylpheed/trunk + The subdirectories under the sylpheed directory are as follows: + + + trunk/ - main tree + + + branches/ - miscellaneous experimental branches + + + tags/ - release-tagged branches + + + To update to the newest source tree, run the following command in the target directory: + svn update + + + + + I checked out the sources using SVN and can't find any configure script. + + + The SVN versions are meant to be used by developers rather than "normal" + users, so the source (or binary) distributions are easier to use. +
+ Yeah, but the latest features from SVN really look sexy... +
+ You need to generate the configure script by running autogen.sh. + Be sure to have autoconf and automake packages installed for this. + + + + + Running "autogen.sh" gives error messages that "AM_PATH_GDK_PIXBUF" or + "AM_PATH_(whatever)" is not found. + + + There are some *.m4 files in the ac/missing directory. Try to copy + them into the ac directory and run autogen.sh again. + + If there are still some .m4 files not found (e.g. those from GTK+), try + to run % locate m4 | less or % locate aclocal | less to find additional directories containing those macros. If you find e.g. a + gtk.m4 in /opt/gnome/share/aclocal, change following line in + autogen.sh from + aclocal -I ac \ + to + aclocal -I ac -I /opt/gnome/share/aclocal \ + and run it again. + + + + + I don't want to compile in support for (...) any longer, but after running + "configure", those libraries are still used. + + + Remove the config.cache file and run ./configure again. You should + also use make clean to avoid undefined references. + + + + + How can I select different applications to open with specific MIME types? + + + The MIME-type to application associations are kept in /etc/mailcap. + + + + + How can I change the suggested mimetype for attachments? + + + The extension to MIME-type associations are kept in /etc/mime.types + + + + + The folder list is not updated after I manually moved/copied folders. + + + You need to update Sylpheed cache. Right click on the mailbox and choose + Rebuild folder tree. + + + + + How can I revert original settings, e.g. for fonts, key bindings, etc.? + + + Sylpheed keeps its configuration files in $HOME/.sylpheed-2.0/sylpheedrc (or %APPDATA%\Sylpheed\sylpheedrc under Windows) and creates default + entries, if none are found. So the easiest way is to quit Sylpheed, + temporarily renaming your $HOME/.sylpheed-2.0 (or %APPDATA%\Sylpheed\sylpheedrc) e.g. to *.bak and restarting + Sylpheed in order to get default entries. + + + + + What environment variables have effect on Sylpheed? + + + Here are the most common variables: + + + HOME + - location of .sylpheed-2.0 (config directory) and default folder for Mailboxes. + + + LANG, + + + LC_ALL, + + + LC_CTYPE, + + + LC_MESSAGES - locale settings, e.g. language and date format. + + + For more information on how to make Sylpheed display your language, see the relevant question. + + + + + Special characters (e.g. umlauts) are not displayed correctly. + + + In most cases, this is caused by fonts that use an unsuitable encoding on a not Unicode-based system. (On a Unicode-based system, fonts should support all thinkable characters for the vast majority of languages.) + Choose + Configuration + Common preferences... + Display + General + , and click the button right to Text font. Now, a special dialog appears that allows you to pick a desirable font family, style, and size. + You should also make sure that your environment variables regarding locale + settings have sensible values. + + + + + How can I convert my old mailbox/address book from (some mail client). + + + You can try to + export your old mailbox to MH, MBOX or EML format. + + Take a look at the Add sender to address book... item from the Tools + menu, it could be a useful alternative or addition, when importing your old + contacts. + + + + + + What config files are there, and what are they used for? + + + Sylpheed config files can be found in $HOME/.sylpheed-2.0 (under Windows, the path is %APPDATA%\Sylpheed). They are in plain + text format and quite easy to understand, so don't fear to take a look + into them using a text editor. + + + sylpheedrc - main configuration: nearly all options from the + settings window, e.g. mailbox location, font + entries, etc. + + + accountrc - settings for POP/IMAP/NNTP accounts + + + actionsrc - user-defined actions + + + addrbook-*.xml - contents of your address book + + + customheaderrc - contains user-defined header lines + + + dispheaderrc - headers to display above the mail body + + + filter.xml - filter settings + + + folderlist.xml - folder specific settings, e.g. hiding + read messages, sort order, etc. + + + menurc - key bindings + + + + + + + How do I change the location of user profile directory under Windows? + + + The configuration files and the mailboxes are saved under the following +location (%APPDATA%\Sylpheed) by default: + + + Windows 2000/XP: +C:\Documents and Settings\(user name)\Application Data\Sylpheed + + + Windows Vista/Seven: +C:\Users\(user name)\AppData\Roaming\Sylpheed + + + If you want to change the location of the configuration files, you can +specify it by the command line option --configdir "directory name". +Create a shortcut of sylpheed.exe, and append the option to the link target +like the following: + "C:\Program Files\Sylpheed\sylpheed.exe" --configdir "D:\Sylpheed" + If sylpheed.ini file exists at the same location as sylpheed.exe, it will be +loaded at startup. With this approach, you can make Sylpheed completely portable +independent of drive letters etc., and you can install it in removable media +such as USB memory. + + The installer version, and GnuPG and GPGME use registry. + + The sample INI file is included in the Sylpheed for Windows installation package as sample-sylpheed.ini. +Please copy or rename it to use. +ipcport specifies the port number of socket for IPC (default is 50215). +configdir specifies the location of configuration files as a relative +path from the folder in which sylpheed.exe is located, or an absolute path. + (The text above is a slightly modified excerpt from the README-win32.txt file, which you should find within the C:\Program Files\Sylpheed directory.) + + + + + Can I run multiple instances of Sylpheed? + + + Yes, Sylpheed 3.1 adds support for this often requested feature. The format of the multiple instances command is as follows: + sylpheed --instance-id ID --configdir path-to-alternative-configdir + Default ID is set to sylpheed, so you can specify any other instance +ID. The ID is used for the name of unix domain +socket (under UNIX), or mutex name (under Windows). configdir specifies the configuration directory, i.e. the location of configuration files you want to use with the given instance. + + Do not share same configuration directories or mailboxes across multiple instances as this may lead to an unexpected application behavior! + + + + + + What to do when printing an email prints off the paper? + + + You can use enscript for this. Use enscript %s to print everything on one page, or enscript -U2 %s for printing two logical pages on one physical page. + + + + 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 @@ + + Sylpheed FAQ - Interface + + + + How do I make Sylpheed display my language? + + + You have to set some environment variables, such as + LANG, LC_CTYPE, LC_MESSAGES to your local language. + Usually LANG (or LC_ALL) is sufficient. Note that modern distributions and operating systems do this for you automatically. + Under UNIX, if you need to set e.g. the LANG environment variable manually, execute the following command (using sh or related shell): + export LANG=value + Replace value with a valid ISO language code (e.g. en_GB for British English). + If you intend to set the displayed language manually under Windows, you can do so by creating the +LANG environment variable with a valid ISO language code value under + Control Panel + System + Advanced + Environment Variables + . + Also see the question regarding environment variables that have effect on Sylpheed. + + + + + I don't like the default font. Can I change that? + + + Yes. In + Configuration + Common preferences... + , under the + Display tab. + + + + + There are too many columns in the message list! + + + In + Configuration + Common preferences... + under the + Display tab, you can press the button Set display item of summary.... That pops up a screen with all the + options you can show or leave out of the message + list. + + + + + How do I disable or enable the alternating row colors in the message list? + + + Under UNIX, you can directly edit the appropriate hidden setting stored in the $HOME/.sylpheed-2.0/sylpheedrc configuration file by changing the setting value to 0, or 1, respectively (default is on, i.e. 1): + enable_rules_hint=0 + + There are various other hidden settings that can be adjusted in your sylpheedrc configuration file, see the README file for details. + + The above does not work under Windows, however, so you have to edit the C:\Program Files\Sylpheed\share\themes\MS-Windows\gtk-2.0\gtkrc file and set the following setting to 1, or 0, respectively (default is off under Windows, i.e. 0): + GtkTreeView::allow-rules = 1 + + 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 gtkrc file somewhere safe. + + + + + + Can I use a different editor to write my mails? + + + You can. In + Configuration + Common preferences + , under + the Details and External commands tabs, you can define your editor of choice. + Remember, if you want to use a command line editor + like vi or emacs, to write the name of the shell + (term, term, rxvt) with the -e parameter in front of + the editor. E.g.: rxvt -e vi %s. + Also, make sure that you have checked Automatically launch the external editor in + Common preferences + Compose + Editor + , if you want the editor of your choice to be launched every time you begin composing a message. + + + + + How to change the font size in the Sylpheed interface? + + + You can set the GTK+ font by $HOME/.gtkrc-2.0, or + $HOME/.gtkrc-2.0.mine, + (which is included by $HOME/.gtkrc-2.0). + For example: + style "default" { + font = "-adobe-helvetica-medium-r-normal--12-*-*-*-*-*-iso8859-1 " +} +widget_class "*" style "default" + + + + + + Sylpheed saves my outgoing mail (in Outbox). Can I make it stop doing that? + + + In + Configuration + Common preferences... + , there is a + checkbox Save sent message to outbox. Uncheck it, + and it's solved. + + + + + How can I change the key bindings (hotkeys) in Sylpheed? + + + Unlike Sylpheed 1.x, Sylpheed 2.x and 3.x doesn't allow direct modification of the menu shortcuts by default. Nevertheless, you can use the following methods to configure them: + + + Using GNOME 2.8 or later: run gconf-editor from + Applications + System Tools + Configuration Editor + . Select + desktop + gnome + interface + and check can-change-accels there. + + + Using GNOME before 2.8, or other environments: add the following line to the file ~/.gtkrc-2.0 (or create a new one, if it doesn't exist): + gtk-can-change-accels = 1 + + + When Sylpheed is not running, directly edit ~/.sylpheed-2.0/menurc with a text editor. + + + After that, the key binding change itself is very simple. Suppose you want to assign a + shortcut key to a function, e.g. sending all mail + out should start when you press + Ctrl + Y + . Click the + Message menu and move the mouse over Send all messages. Now you press + Ctrl + Y + . Immediately the menu + text is updated and the function is in place. Please + note that a previous function that + Ctrl + Y + was + assigned to, will no longer have a shortcut key. If + you want to remove the key binding, do the same + thing, but press the Delete key on the menu item. + Then the key binding is removed. + Also see + Configuration + Common preferences... + Details + Interface + Set key bindings... + where you are able to reset the Default key bindings, or use other predefined key bindings. + + + + + Can I close windows without the mouse? + + + Of course! Not all windows, but by pressing Escape, + you can close the address book, the window of viewing + a mail source ( + View + Message source + ), the window of + viewing the headers, and several others. Just give + it a try and you will find all of them. + + + + + Can I change the way the date is displayed in the message summary? + + + As of 0.4.65 you can. The options are: + %y = year in numbers %m = month in number + %d = day in numbers %c = date/time for locale + %A = full weekday name %a = short month name + %B = full month name %b = short month name + %H = hours in 24-clock %I = hours in 12-clock + For more information, go to the + Configuration + Common preferences + Display + General + and choose the ... labeled button. +For more options, see man 3 strftime. + + + + + Why can't I see the compface pictures? + + + You need to enable displaying of the header pane in the + general preferences. + + + + + I still can't see the pictures. Why not? + + + You may not have compiled in Compface support. See the appropriate question in the Installation and Configuration section. + + + + + Why does the URL launcher not launch my web browser? + + + You need to double click the URL. +Also, check that you have configured your web browser correctly in + Configuration + Common preferences... + Details + External commands + . + + + + + Attachments with spaces in the name won't open! + + + When you try to launch a helper application, like an image viewer, with an attachment that has spaces in the name, put quotes around the %s +parameter. Example: gedit '%s' + + + + + Execute command for my dynamic signature seems not to be working! + + + 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 + Account preferences + Compose + Signature + Command output + ) using either forward slashes or double +backslashes for paths, for example: + cmd /c 'c:\\signature.bat' + Note that it is also recommended to enclose paths with single quotes, as is illustrated above. + + + + + Where is the Bcc when I compose a mail? + + + Open + Configuration + Preferences for current account... + Compose + . There you can check the Bcc checkbox and optionally enter an email address. + + + + + How do I change the toolbar? + + + Go to + View + Customize toolbar... + and select items from the Available items list to be displayed on the toolbar. You can modify the order by using the Up or Down button. The customization dialog also offers you to revert your modifications to default. + + + + + Why isn't the next message displayed when I delete a message? + + + Go to + Configuration + Common preferences... + Details + Interface + , and select Always open messages in summary when selected. + + + + + How can I remove mailing list information from Subject headers? + + + 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 [sylpheed:33101]. 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. + To do that, right-click on a folder from the folder tree, and select Properties... In the Folder properties dialog, check Don't display [...] or (...) at the beginning of subject in summary, or Delete [...] or (...) at the beginning of subject on reply, respectively. + + + + 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 @@ + + + + GNU Free Documentation License + Version 1.2, November 2002 + + 2000,2001,2002 + Free Software Foundation, Inc. + + +
Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA02110-1301USA
 + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Version 1.2, November 2002 + + GNU Free Documentation License +
+ PREAMBLE + The purpose of this License is to make a manual, textbook, or +other functional and useful document "free" in the sense of freedom: to +assure everyone the effective freedom to copy and redistribute it, with +or without modifying it, either commercially or noncommercially. +Secondarily, this License preserves for the author and publisher a way +to get credit for their work, while not being considered responsible for +modifications made by others. + This License is a kind of "copyleft", which means that derivative +works of the document must themselves be free in the same sense. It +complements the GNU General Public License, which is a copyleft license +designed for free software. + We have designed this License in order to use it for manuals for +free software, because free software needs free documentation: a free +program should come with manuals providing the same freedoms that the +software does. But this License is not limited to software manuals; it +can be used for any textual work, regardless of subject matter or +whether it is published as a printed book. We recommend this License +principally for works whose purpose is instruction or reference. +
+
+ APPLICABILITY AND DEFINITIONS + This License applies to any manual or other work, in +any medium, that contains a notice placed by the copyright holder saying +it can be distributed under the terms of this License. Such a notice +grants a world-wide, royalty-free license, unlimited in duration, to use +that work under the conditions stated herein. The "Document", below, +refers to any such manual or work. Any member of the public is a +licensee, and is addressed as "you". You accept the license if you +copy, modify or distribute the work in a way requiring permission under +copyright law. + A "Modified Version" of the Document means any +work containing the Document or a portion of it, either copied verbatim, +or with modifications and/or translated into another language. + A "Secondary Section" is a named appendix or +a front-matter section of the Document that deals exclusively with the +relationship of the publishers or authors of the Document to the +Document's overall subject (or to related matters) and contains nothing +that could fall directly within that overall subject. (Thus, if the +Document is in part a textbook of mathematics, a Secondary Section may +not explain any mathematics.) The relationship could be a matter of +historical connection with the subject or with related matters, or of +legal, commercial, philosophical, ethical or political position +regarding them. + The "Invariant Sections" are certain Secondary +Sections whose titles are designated, as being those of Invariant +Sections, in the notice that says that the Document is released under +this License. If a section does not fit the above definition of +Secondary then it is not allowed to be designated as Invariant. The +Document may contain zero Invariant Sections. If the Document does not +identify any Invariant Sections then there are none. + The "Cover Texts" are certain short passages of +text that are listed, as Front-Cover Texts or Back-Cover Texts, in the +notice that says that the Document is released under this License. A +Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at +most 25 words. + A "Transparent" copy of the Document means a +machine-readable copy, represented in a format whose specification is +available to the general public, that is suitable for revising the +document straightforwardly with generic text editors or (for images +composed of pixels) generic paint programs or (for drawings) some widely +available drawing editor, and that is suitable for input to text +formatters or for automatic translation to a variety of formats suitable +for input to text formatters. A copy made in an otherwise Transparent +file format whose markup, or absence of markup, has been arranged to +thwart or discourage subsequent modification by readers is not +Transparent. An image format is not Transparent if used for any +substantial amount of text. A copy that is not "Transparent" is called +"Opaque". + Examples of suitable formats for Transparent copies include plain +ASCII without markup, Texinfo input format, LaTeX input format, SGML or +XML using a publicly available DTD, and standard-conforming simple HTML, +PostScript or PDF designed for human modification. Examples of +transparent image formats include PNG, XCF and JPG. Opaque formats +include proprietary formats that can be read and edited only by +proprietary word processors, SGML or XML for which the DTD and/or +processing tools are not generally available, and the machine-generated +HTML, PostScript or PDF produced by some word processors for output +purposes only. + The "Title Page" means, for a printed book, +the title page itself, plus such following pages as are needed to hold, +legibly, the material this License requires to appear in the title page. +For works in formats which do not have any title page as such, "Title +Page" means the text near the most prominent appearance of the work's +title, preceding the beginning of the body of the text. + A section "Entitled XYZ" means a named subunit +of the Document whose title either is precisely XYZ or contains XYZ in +parentheses following text that translates XYZ in another language. +(Here XYZ stands for a specific section name mentioned below, such as +"Acknowledgements", "Dedications", "Endorsements", or "History".) To +"Preserve the Title" of such a section when you modify the Document +means that it remains a section "Entitled XYZ" according to this +definition. + The Document may include Warranty Disclaimers next to the notice +which states that this License applies to the Document. These Warranty +Disclaimers are considered to be included by reference in this License, +but only as regards disclaiming warranties: any other implication that +these Warranty Disclaimers may have is void and has no effect on the +meaning of this License. +
+
+ VERBATIM COPYING + You may copy and distribute the Document in any medium, either +commercially or noncommercially, provided that this License, the +copyright notices, and the license notice saying this License applies to +the Document are reproduced in all copies, and that you add no other +conditions whatsoever to those of this License. You may not use +technical measures to obstruct or control the reading or further copying +of the copies you make or distribute. However, you may accept +compensation in exchange for copies. If you distribute a large enough +number of copies you must also follow the conditions in section 3. + + You may also lend copies, under the same conditions stated above, +and you may publicly display copies. +
+
+ COPYING IN QUANTITY + If you publish printed copies (or copies in media that commonly +have printed covers) of the Document, numbering more than 100, and the +Document's license notice requires Cover Texts, you must enclose the +copies in covers that carry, clearly and legibly, all these Cover Texts: +Front-Cover Texts on the front cover, and Back-Cover Texts on the back +cover. Both covers must also clearly and legibly identify you as the +publisher of these copies. The front cover must present the full title +with all words of the title equally prominent and visible. You may add +other material on the covers in addition. Copying with changes limited +to the covers, as long as they preserve the title of the Document and +satisfy these conditions, can be treated as verbatim copying in other +respects. + If the required texts for either cover are too voluminous to fit +legibly, you should put the first ones listed (as many as fit +reasonably) on the actual cover, and continue the rest onto adjacent +pages. + If you publish or distribute Opaque copies of the Document +numbering more than 100, you must either include a machine-readable +Transparent copy along with each Opaque copy, or state in or with each +Opaque copy a computer-network location from which the general +network-using public has access to download using public-standard +network protocols a complete Transparent copy of the Document, free of +added material. If you use the latter option, you must take reasonably +prudent steps, when you begin distribution of Opaque copies in quantity, +to ensure that this Transparent copy will remain thus accessible at the +stated location until at least one year after the last time you +distribute an Opaque copy (directly or through your agents or retailers) +of that edition to the public. + It is requested, but not required, that you contact the authors of +the Document well before redistributing any large number of copies, to +give them a chance to provide you with an updated version of the +Document. +
+
+ MODIFICATIONS + You may copy and distribute a Modified Version of the Document +under the conditions of sections 2 and 3 above, provided that you +release the Modified Version under precisely this License, with the +Modified Version filling the role of the Document, thus licensing +distribution and modification of the Modified Version to whoever +possesses a copy of it. In addition, you must do these things in the +Modified Version: + + GNU FDL Modification Conditions + + 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. + + + 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. + + + State on the Title page the name of the publisher of the Modified Version, as the publisher. + + + Preserve all the copyright notices of the Document. + + + Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. + + + Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. + + + Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice. + + + Include an unaltered copy of this License. + + + Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. + + + Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission. + + + For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. + + + 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. + + + Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. + + + Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section. + + + Preserve any Warranty Disclaimers. + + + If the Modified Version includes new front-matter sections or +appendices that qualify as Secondary Sections and contain no material +copied from the Document, you may at your option designate some or all +of these sections as invariant. To do this, add their titles to the +list of Invariant Sections in the Modified Version's license notice. +These titles must be distinct from any other section titles. + You may add a section Entitled "Endorsements", provided it +contains nothing but endorsements of your Modified Version by various +parties--for example, statements of peer review or that the text has +been approved by an organization as the authoritative definition of a +standard. + You may add a passage of up to five words as a Front-Cover Text, +and a passage of up to 25 words as a Back-Cover Text, to the end of the +list of Cover Texts in the Modified Version. Only one passage of +Front-Cover Text and one of Back-Cover Text may be added by (or through +arrangements made by) any one entity. If the Document already includes +a cover text for the same cover, previously added by you or by +arrangement made by the same entity you are acting on behalf of, you may +not add another; but you may replace the old one, on explicit permission +from the previous publisher that added the old one. + The author(s) and publisher(s) of the Document do not by this +License give permission to use their names for publicity for or to +assert or imply endorsement of any Modified Version. +
+
+ COMBINING DOCUMENTS + You may combine the Document with other documents released under +this License, under the terms defined in section 4 above for modified versions, provided that you include in the +combination all of the Invariant Sections of all of the original +documents, unmodified, and list them all as Invariant Sections of your +combined work in its license notice, and that you preserve all their +Warranty Disclaimers. + The combined work need only contain one copy of this License, and +multiple identical Invariant Sections may be replaced with a single +copy. If there are multiple Invariant Sections with the same name but +different contents, make the title of each such section unique by adding +at the end of it, in parentheses, the name of the original author or +publisher of that section if known, or else a unique number. Make the +same adjustment to the section titles in the list of Invariant Sections +in the license notice of the combined work. + In the combination, you must combine any sections Entitled +"History" in the various original documents, forming one section +Entitled "History"; likewise combine any sections Entitled +"Acknowledgements", and any sections Entitled "Dedications". You must +delete all sections Entitled "Endorsements". +
+
+ COLLECTIONS OF DOCUMENTS + You may make a collection consisting of the Document and other +documents released under this License, and replace the individual copies +of this License in the various documents with a single copy that is +included in the collection, provided that you follow the rules of this +License for verbatim copying of each of the documents in all other +respects. + You may extract a single document from such a collection, and +distribute it individually under this License, provided you insert a +copy of this License into the extracted document, and follow this +License in all other respects regarding verbatim copying of that +document. +
+
+ AGGREGATION WITH INDEPENDENT WORKS + A compilation of the Document or its derivatives with other +separate and independent documents or works, in or on a volume of a +storage or distribution medium, is called an "aggregate" if the +copyright resulting from the compilation is not used to limit the legal +rights of the compilation's users beyond what the individual works +permit. When the Document is included in an aggregate, this License does +not apply to the other works in the aggregate which are not themselves +derivative works of the Document. + If the Cover Text requirement of section 3 is applicable to these +copies of the Document, then if the Document is less than one half of +the entire aggregate, the Document's Cover Texts may be placed on covers +that bracket the Document within the aggregate, or the electronic +equivalent of covers if the Document is in electronic form. Otherwise +they must appear on printed covers that bracket the whole +aggregate. +
+
+ TRANSLATION + Translation is considered a kind of modification, so you may +distribute translations of the Document under the terms of section 4. +Replacing Invariant Sections with translations requires special +permission from their copyright holders, but you may include +translations of some or all Invariant Sections in addition to the +original versions of these Invariant Sections. You may include a +translation of this License, and all the license notices in the +Document, and any Warranty Disclaimers, provided that you also include +the original English version of this License and the original versions +of those notices and disclaimers. In case of a disagreement between the +translation and the original version of this License or a notice or +disclaimer, the original version will prevail. + If a section in the Document is Entitled "Acknowledgements", +"Dedications", or "History", the requirement (section 4) to Preserve its +Title (section 1) will typically require changing the actual +title. +
+
+ TERMINATION + You may not copy, modify, sublicense, or distribute the Document +except as expressly provided for under this License. Any other attempt +to copy, modify, sublicense or distribute the Document is void, and will +automatically terminate your rights under this License. However, +parties who have received copies, or rights, from you under this License +will not have their licenses terminated so long as such parties remain +in full compliance. +
+
+ FUTURE REVISIONS OF THIS LICENSE + The Free Software Foundation may publish new, revised versions of +the GNU Free Documentation License from time to time. Such new versions +will be similar in spirit to the present version, but may differ in +detail to address new problems or concerns. See +http://www.gnu.org/copyleft/. + Each version of the License is given a distinguishing version +number. If the Document specifies that a particular numbered version of +this License "or any later version" applies to it, you have the option +of following the terms and conditions either of that specified version +or of any later version that has been published (not as a draft) by the +Free Software Foundation. If the Document does not specify a version +number of this License, you may choose any version ever published (not +as a draft) by the Free Software Foundation. +
+
+ ADDENDUM: How to use this License for your documents + To use this License in a document you have written, include a copy +of the License in the document and put the following copyright and +license notices just after the title page: + + If you have Invariant Sections, Front-Cover Texts and Back-Cover +Texts, replace the "with...Texts." line with this: +
+ Sample Invariant Sections list + + with the Invariant Sections being LIST THEIR TITLES, with the + Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. + +
+ If you have Invariant Sections without Cover Texts, or some other +combination of the three, merge those two alternatives to suit the +situation. + If your document contains nontrivial examples of program code, we +recommend releasing these examples in parallel under your choice of free +software license, such as the GNU General Public License, to permit +their use in free software. +
+ 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 @@ + + + + + Chapter 1. Sylpheed FAQ - General Information + + + + + + + + + + +
+ + + + + + + + + +
Chapter 1. Sylpheed FAQ - General Information
Prev  +   Next
+
+
+
+
+
+
+

Chapter 1. Sylpheed FAQ - General Information +

+
+
+
+
+
+
1.1. + Are there FAQ's in other languages? +
+
1.2. + What is Sylpheed? +
+
1.3. + Where can I get Sylpheed? +
+
1.4. + Who writes Sylpheed? +
+
1.5. + What does the name Sylpheed mean? +
+
1.6. + How does Sylpheed store mails? +
+
1.7. + Why does the auto collection of mail not work? +
+
1.8. + Does Sylpheed have mail filtering? +
+
1.9. + Can Sylpheed handle IMAP mail? +
+
1.10. + Can Sylpheed handle local unix mailboxes? +
+
1.11. + Can Sylpheed handle IPv6? +
+
1.12. + Does Sylpheed support encryption like GPG? +
+
1.13. + How does Sylpheed check for MIME types? +
+
1.14. Does Sylpheed allow me to write HTML styled messages? +
+
1.15. Does Sylpheed have automatic name completion in the address fields? +
+
1.16. Fine, but when I hit the Tab key I either get an error message or nothing happens at all. +
+
1.17. Why is Sylpheed so fast? +
+
1.18. Where can I get the current patches for Sylpheed? +
+
1.19. How can I send in patches, report bugs, talk about Sylpheed with others? +
+
1.20. When I send mail, the Content-Type header says the mail is in + US-ASCII, even when I specified ISO-8859-1? +
+
1.21. Why does it look like word wrap is not working? +
+
1.22. How do I copy my mail archive to another machine?
+
1.23. Can I import a mbox into Sylpheed's MH mailfolders? +
+
1.24. + Can I use procmail to sort my mails with the MH mail handling? +
+
1.25. + When I upgrade Sylpheed, are there things I should be aware of? +
+
1.26. How can I quickly update the views in Sylpheed? +
+
1.27. Why can't I use gvim as external editor? +
+
1.28. Can I quote just parts of the original message when replying? +
+
1.29. Can I reply without quoting at all? +
+
1.30. Does Sylpheed provide an anti-spam feature?
+
1.31. Are there any plug-ins extending standard Sylpheed functionality?
+
1.32. Where I can find the latest Sylpheed FAQ and manual? +
+
1.33. Where I can obtain source files for this document?
+
1.34. I have found an error and/or outdated information in this document!
+
1.35. Who are the members of the Sylpheed Documentation Project?
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
1.1. +

+ Are there FAQ's in other languages? + +

+
+

+ Yes. Here are links to several translations: +

+
+ +
+

+ You can always download this FAQ from the Sylpheed Documentation Project website. +

+
+

Note

+

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 their website. Thanks in advance. +

+
+
1.2. +

+ What is Sylpheed? + +

+
+

+ Sylpheed is an email client (and news reader) based on GTK+, + running on the X Window System or Microsoft Windows, and aiming for: +

+
+
    +
  • +

    Quick response

    +
    • +
  • +

    Graceful, and sophisticated interface

    +
    • +
  • +

    Easy configuration, intuitive operation

    +
    • +
  • +

    High reliability

    +
    • +
  • +

    Internationalization and multilingualization support

    +
    • +
  • +

    Abundant features

    +
    • +
+
+

As the Sylpheed README file reads: The appearance and interface are similar to some popular e-mail clients for + Windows, such as Outlook Express or Becky!. Many commands are accessible with + the keyboard like the Emacs-based mailers such as Mew and Wanderlust. + So you will be able to migrate to Sylpheed without much discomfort, even if + you are accustomed to other mailers. +

+
1.3. +

+ Where can I get Sylpheed? + +

+
+

+ You can download it from the download page on Sylpheed website. There are links to download + tarball sources, patches to the previous version, and also links to the Sylpheed for Windows binaries, including + the installer, the ZIP archive, and the patch to the previous Sylpheed for Windows version. +

+

Depending on the state of the Sylpheed development cycle, you may be offered links to development versions such as beta and + RC releases. These might not be suitable for everyday use, however, so you may want to stick with the stable release, anyway. +

+

Also on the download page, you can download Sylph-Searcher (which is a program that enables fast full-text search of messages + stored in mailboxes of Sylpheed, or normal MH folders), and LibSylph (which is a library that provides Sylpheed core features + independent from the UI of Sylpheed). +

+
1.4. +

+ Who writes Sylpheed? + +

+
+

+ Hiroyuki Yamamoto . + +

+
1.5. +

+ What does the name Sylpheed mean? + +

+
+

+ It means light weight, like air. This comes from the + name of the wind spirits, the Sylphs. + +

+
1.6. +

+ How does Sylpheed store mails? + +

+
+

+ Mails are stored in the MH mailfile format as used by MH + and EMH. Maildir, mbox, and eml formats are not (yet) + supported, although it is possible to import an mbox + file or an eml file into a Sylpheed mailbox. +

+

You can manage your mails just with Sylpheed, or together with another mailer based on the MH format (e.g. Mew). The MH format + has less possibility + of losing mails on failures since one file corresponds to one mail. You can also utilize fetchmail + and/or procmail, and external programs on receiving (like inc or imget). +

+
1.7. +

+ Why does the auto collection of mail not work? + +

+
+

+ Auto collection works since version 0.5.1. If you need it + or want it, you should upgrade. + +

+
1.8. +

+ Does Sylpheed have mail filtering? + +

+
+

+ Yes. You can find it in Configuration -> Filter settings...

+

+ Please note that filtering is not yet implemented for IMAP accounts. + +

+
1.9. +

+ Can Sylpheed handle IMAP mail? + +

+
+

+ Yes. As of version 0.4.99 IMAP is supported. + +

+
1.10. +

+ Can Sylpheed handle local unix mailboxes? + +

+
+

+ Yes. + +

+
1.11. +

+ Can Sylpheed handle IPv6? + +

+
+

+ Yes, IPv6 is fully supported in Sylpheed. + +

+
1.12. +

+ Does Sylpheed support encryption like GPG? + +

+
+

+ Yes. GPG is implemented and works fine. For activating it in Sylpheed, + see the appropriate question in the Installation section. + +

+
1.13. +

+ How does Sylpheed check for MIME types? + +

+
+

+ Sylpheed uses the Mutt type of mime checking. + +

+
1.14. +

Does Sylpheed allow me to write HTML styled messages? + +

+
+

+ No. A discussion has gone around over this topic, and + the outcome was that HTML mail is not wanted. If you + really need to send HTML, you can of course attach a + web page to an email. +

+
1.15. +

Does Sylpheed have automatic name completion in the address fields? + +

+
+

+ Yes. When you search for a name that starts with "don", + type "don" (without the quotes) and it will show you the correct name (when only one "don" + exists in your address book. Otherwise a drop-down list + appears, which allows you to select the name you want. + E.g. Donald Duck, Don Johnson. But also email addresses + starting with "don" will appear in the list (like + "don.giovanni@maffia.org"). +

+

Prior to Sylpheed 3.1, users needed to press the Tab key before the search would start. If you still prefer the previous behavior, you can enable it by checking Configuration->Common preferences...->Details->Other->Address book+Address auto-completion:+Start with Tab. +

+
1.16. +

Fine, but when I hit the Tab key I either get an error message or nothing happens at all. + +

+
+

+ When you want to use name completion, make sure that + there are names in your address book. If there are no + names, even Sylpheed has a hard time completing + something. +

+

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: Configuration->Common preferences...->Details->Other->Address book+Address auto-completion:+Disabled. +

+
1.17. +

Why is Sylpheed so fast? + +

+
+

That's what it is designed for! + +

+
1.18. +

Where can I get the current patches for Sylpheed? + +

+
+

In most cases, current patches are being posted by Sylpheed users and contributors to the Sylpheed mailing list . + (Also see the Installation section on how to install a patch.) + +

+
1.19. +

How can I send in patches, report bugs, talk about Sylpheed with others? + +

+
+

To talk to others, you should join the Sylpheed mailing + list at + http://www.sraoss.jp/mailman/listinfo/sylpheed + . Note that there is + a Japanese and an English list, so pick the right one! + If you have made a patch that you want the world to know + of, please post it either to the mailing list, or contact the Sylpheed author, Hiroyuki Yamamoto . +

+

Please supply the information of Tools->Log window, or the contents of + sylpheed.log, which is located under the configuration folder, when + reporting bugs. +

+
1.20. +

When I send mail, the Content-Type header says the mail is in + US-ASCII, even when I specified ISO-8859-1? + +

+
+

If ISO-8859-1 characters (>= 0x80) are not used in the + message body, Sylpheed will automatically set the + charset value in the Content-Type header as US-ASCII. + +

+
1.21. +

Why does it look like word wrap is not working? + +

+
+

Word wrapping is a bit peculiar perhaps. You can type + lines as long as you like. By the time you send or queue + a mail with long lines, Sylpheed will first wrap the + lines to the line length you set up, and then the mail + is queued. This is more convenient than you think. Once + a line is wrapped (hard line breaks are inserted in the + text) and you add something in a line there, the next + line will move to a separate new line, leaving one or + two words from the previous line "hanging there" alone. + E.g. + +

+
+

           This is a long line that
+            is wrapped.         +

+
+

Now you add one word in the first line: + +

+
+

           This is a very long line
+            that
+            is wrapped         +

+
+

This would cause you a lot of manual reformatting to get + a presentable mail again. + + +

+
+

Note

+

As of Sylpheed 0.8.0., active word wrap has been + implemented. You can turn it on in Common Preferences->Compose->Editor+Wrap on input. + +

+
+
1.22. +

How do I copy my mail archive to another machine?

+
+

You need to copy the sylpheed-2.0 directory with your user profile, and your entire local mail archive. +

+

Under UNIX, the user profile is stored in $HOME/.sylpheed-2.0 by default, and your local mail archive is by default located in $HOME/Mail. +

+

While under Windows 2000/XP, the user profile is stored in C:\Documents and Settings\(user name)\Application Data\Sylpheed by default, and your local mail archive is by default located in C:\Documents and Settings\(user name)\Application Data\Sylpheed\Mailboxes\Mail. +

+

Under Windows Vista/Seven, the directory paths are C:\Users\(user name)\AppData\Roaming\Sylpheed, and C:\Users\(user name)\AppData\Roaming\Sylpheed\Mailboxes\Mail, respectively. +

+
1.23. +

Can I import a mbox into Sylpheed's MH mailfolders? + +

+
+

+ Yes, just create/select the folder you want your + mails in, and select Import mbox file... in the File + menu. +

+
1.24. +

+ Can I use procmail to sort my mails with the MH mail handling? + +

+
+

+ Yes. Just make sure that you add /. to the end of a rule so + procmail knows you are filtering into an MH mail folder. Example: + + 

0:
+* ^Subject:.*sylpheed
+sylpheedmail/.
+

Check man procmail for details. + +

+
1.25. +

+ When I upgrade Sylpheed, are there things I should be aware of? + +

+
+

+ Yes! +

+
+
    +
  • +

    Upgrade to 0.4.50: you should reconfigure your newsgroup settings

    +
    • +
  • +

    Upgrade to 0.4.63: you should set the URL string colors from the Configuration menu +

    +
    • +
  • +

    Upgrade to 0.4.65: some menu items have been moved

    +
    • +
  • +

    Upgrade to 0.7.3: many key bindings have changed

    +
    • +
  • +

    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 +

    +
    • +
+
+

You should always read the NEWS document (and also NEWS-x.0 if you are upgrading from a very old version) that is included in the release tarballs. The NEWS can also be viewed on the + appropriate Sylpheed website page. +

+
1.26. +

How can I quickly update the views in Sylpheed? + +

+
+

+ Just press Alt-U or select Update summary from the View menu. + +

+
1.27. +

Why can't I use gvim as external editor? + +

+
+

+ If one wishes to use gvim as an external editor it's + necessary to start it with the no-fork option -f, i.e. + in the configuration dialog box you need to enter + gvim -f %s. If not the editor forks and open up a + separate file and when one quits the editor the changes + are lost and don't show up in the composer window. + (Thanks, Ed Collins!) + +

+
1.28. +

Can I quote just parts of the original message when replying? + +

+
+

+ Yes, select the part in the text view and choose Reply. + +

+
1.29. +

Can I reply without quoting at all? + +

+
+

You need to disable quoting by editing the reply format under Configuration->Common preferences->Compose tab->Format tab + (also works with + forward format which you can see below the reply format in the configuration dialog). +

+
1.30. +

Does Sylpheed provide an anti-spam feature?

+
+

Yes. It has a bogofilter and a bsfilter support. Just go to Configuration->Common preferences...->Junk mail and check Enable Junk mail control. Then you can select a Learning command preset of your choice, or possibly use custom commands. +

+

You can also use other spam filters thanks to the Actions functionality (available under Configuration->Actions...). +

+
+

Note

+

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). +

+
+
1.31. +

Are there any plug-ins extending standard Sylpheed functionality?

+
+

As of Sylpheed 3.1, there is an Attachment Tool Plug-in distributed with the Sylpheed source code and available under plugin/attachment_tool/. Its only function is to remove attachments from + selected 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. +

+

There is a page on the Sylpheed website dedicated to the plug-in interface. Additionally, the PLUGIN.txt file distributed directly with Sylpheed can provide you with some basic information on the topic. +

+
+

Note

+

If you are a developer interested in creating plug-ins for Sylpheed, see the plug-in specification on the Sylpheed wiki. +

+
+
1.32. +

Where I can find the latest Sylpheed FAQ and manual? + +

+
+

+ Go to http://sylpheeddoc.sourceforge.net and check out + the FAQ and manual from the Sylpheed Documentation Project (sylpheeddoc). Both + documents are available in multiple languages there and + usually contain the latest updates. The direct links are as follows: +

+
+ +
+

Also see the question about available language versions at the top of this section.

+
1.33. +

Where I can obtain source files for this document?

+
+

The source DocBook XML files in which this document is written can be obtained from a public CVS repository that is part of the Sylpheed Documentation Project. The source files with all the necessary build system, XSL stylesheets or snapshots are stored under the "doc" 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): +

+

cvs -d:pserver:anonymous@sylpheeddoc.cvs.sourceforge.net:/cvsroot/sylpheeddoc login

+

cvs -z3 -d:pserver:anonymous@sylpheeddoc.cvs.sourceforge.net:/cvsroot/sylpheeddoc co -P doc

+

The source files are also included in .tar.gz and .zip archives made available with each documentation release, these can + be downloaded from the appropriate project page. For more information on the used project infrastructure, please see the project website. +

+
1.34. +

I have found an error and/or outdated information in this document!

+
+

Please report any errors, misleading and/or outdated information to the Sylpheed Documentation Project. You can see the list of Project members in the following question, so you can also contact them directly. +

+
1.35. +

Who are the members of the Sylpheed Documentation Project?

+
+

The current members of the Sylpheed Documentation Project are:

Francois Barriere      fbarriere at users.sourceforge.net
+Petr Kovar             pknbe at users.sourceforge.net

Below is the list of former members of the Sylpheed Documentation Project. Big thank you goes to all of them!

Martin   Bretschneider furbour at users.sourceforge.net
+Olivier  Delhomme      dup at users.sourceforge.net
+Doruk    Fisek         dobidik at users.sourceforge.net
+Melvin   Hadasht       mhadasht at users.sourceforge.net
+Nicolas  Kaiser        nikai at users.sourceforge.net
+Paul     Kater         pkater at users.sourceforge.net
+Ricardo  Mones Lastra  mones at users.sourceforge.net
+Jens     Oberender     jobi at users.sourceforge.net
+Marcelo  Ramos         hackpando at users.sourceforge.net
+Guido    Rudolphi      malatesta at users.sourceforge.net
+Frank    Weng          fweng at users.sourceforge.net
+
+
+
+
+ + + + + + + + + + + +
Prev  +   Next
Sylpheed FAQ Home Chapter 2. Sylpheed FAQ - Installation and Configuration
+
+ + \ 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 @@ + + + + + Chapter 2. Sylpheed FAQ - Installation and Configuration + + + + + + + + + + +
+ + + + + + + + + +
Chapter 2. Sylpheed FAQ - Installation and Configuration
Prev  +   Next
+
+
+
+
+
+
+

Chapter 2. Sylpheed FAQ - Installation and Configuration +

+
+
+
+
+
+
2.1. What does it take to compile Sylpheed?
+
2.2. How do I set up Sylpheed?
+
2.3. Why did the creation of the mailbox fail?
+
2.4. How do I set up an account?
+
2.5. How many accounts can I set up in Sylpheed?
+
2.6. Can I set up an account for sending mail only?
+
2.7. Why does Sylpheed not delete my mails when I press "Delete"? I set a filter, and Sylpheed does not filter. I moved a mail + to a different mailbox and it did not move.
+
2.8. Can I set up special addresses/ports for my mailserver/newsserver?
+
2.9. Does Sylpheed have options for threading messages?
+
2.10. Can I create multiple levels of subfolders to store mail?
+
2.11. Why isn't Sylpheed sending my mail out?
+
2.12. How do I apply a patch after downloading it?
+
2.13. How do I compile in support for compface pictures?
+
2.14. How do I make my own compface image?
+
2.15. How can I tell my browser/newsclient/other program to use Sylpheed as email program?
+
2.16. How do I enable GPG support in Sylpheed?
+
2.17. Mutt does not recognize Sylpheed's MH structure
+
2.18. Viewing a GIF file within Sylpheed causes a segmentation fault.
+
2.19. How Sylpheed checks for new mail?
+
2.20. How can I make Sylpheed notify me when new mail arrives?
+
2.21. Can I use a spell checker with Sylpheed?
+
2.22. How can I make Sylpheed send my compface image in the mails?
+
2.23. How can I get the newest source code from the Sylpheed Subversion (SVN) repository?
+
2.24. I checked out the sources using SVN and can't find any configure script.
+
2.25. Running "autogen.sh" gives error messages that "AM_PATH_GDK_PIXBUF" or + "AM_PATH_(whatever)" is not found.
+
2.26. I don't want to compile in support for (...) any longer, but after running + "configure", those libraries are still used.
+
2.27. How can I select different applications to open with specific MIME types?
+
2.28. How can I change the suggested mimetype for attachments?
+
2.29. The folder list is not updated after I manually moved/copied folders.
+
2.30. How can I revert original settings, e.g. for fonts, key bindings, etc.?
+
2.31. What environment variables have effect on Sylpheed?
+
2.32. Special characters (e.g. umlauts) are not displayed correctly.
+
2.33. How can I convert my old mailbox/address book from (some mail client).
+
2.34. What config files are there, and what are they used for?
+
2.35. How do I change the location of user profile directory under Windows?
+
2.36. Can I run multiple instances of Sylpheed?
+
2.37. What to do when printing an email prints off the paper?
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
2.1. +

What does it take to compile Sylpheed?

+
+

Any POSIX compliant UNIX or similar OS, e.g. Linux, + FreeBSD, Solaris. + GTK+ 2.4.0 or later (GTK+ 2.6.0 or later + is recommended). + A recent ANSI C compiler (gcc 2.7.2.3 should also + work). +

+
+

Note

+

It is reported that Sun C will not compile + Sylpheed. +

+
+

Optionally:

+
+
    +
  • +

    compface (for X-Face)

    +
    • +
  • +

    GPGME (for GnuPG)

    +
    • +
  • +

    OpenSSL for SSL support

    +
    • +
  • +

    GtkSpell for a spell checking feature

    +
    • +
  • +

    cURL for allowing Sylpheed to check for updates

    +
    • +
  • +

    JPilot

    +
    • +
  • +

    LDAP

    +
    • +
  • +

    the equivalent of GTK+-devel and Xfree86-devel

    +
    • +
  • +

    you may also require flex (lex) and bison + (yacc). +

    +
    • +
+
+

Otherwise ./configure will fail. + See also the INSTALL file that is being distributed with the Sylpheed tarball. +

+

Note that as Sylpheed now supports the Windows platform, you can also compile it using MinGW. +

+
2.2. +

How do I set up Sylpheed?

+
+

When you run Sylpheed for the first time, it will + ask you where you want to store your mailboxes. The + default is $HOME/Mail (or %APPDATA%\Sylpheed\Mailboxes\Mail under Windows). You can change this to + anything you like as long as it is a valid directory + name. +

+
+

Note

+

When Sylpheed is executed for the first time, it automatically creates the configuration files under $HOME/.sylpheed-2.0/ (or %APPDATA%\Sylpheed\ under Windows), and asks you the location of mailbox. As stated above, the default is $HOME/Mail, or %APPDATA%\Sylpheed\Mailboxes\Mail under Windows. If some files, which are non-MH format, already exist on the directory, you will have to specify another location. +

+
+

Furthermore, you need to create at least one account to be able to receive or send messages. +

+
2.3. +

Why did the creation of the mailbox fail?

+
+

Sylpheed reports such an error if it can't create the default + mailboxes (inbox, outbox, etc.). This can be because $HOME/Mail + (or %APPDATA%\Sylpheed\Mailboxes\Mail under Windows) already contains files with the same names. This occurs when switching from + Kmail to Sylpheed, in this case backup and remove the existing Mail + directory or use another name for the Sylpheed mail directory. +

+
2.4. +

How do I set up an account?

+
+

After loading Sylpheed for the first time, you can + add an email account by clicking the Configuration menu. Select the option Create new account and let the configuration assistant help you with the initial setup. + In a few easy steps, the assistant allows you to conveniently configure your POP3, IMAP4, or Gmail account. +

+
+

Tip

+

If you want later to change your account configuration, just select Configuration->Preferences for current account..., or Configuration->Edit accounts...

+
+
2.5. +

How many accounts can I set up in Sylpheed?

+
+

The number is unlimited. The limit is reached when + your computer stops responding. +

+
2.6. +

Can I set up an account for sending mail only?

+
+

Yes, add a new account using Configuration->Edit accounts...+Add and set the Protocol to None (local). +

+
2.7. +

Why does Sylpheed not delete my mails when I press "Delete"? I set a filter, and Sylpheed does not filter. I moved a mail + to a different mailbox and it did not move. +

+
+

You have to click the Execute button. + The other solution: in the configuration settings + (Common preferences...->Details->Interface), you have to + check the Execute immediately when moving or deleting messages box. +

+
2.8. +

Can I set up special addresses/ports for my mailserver/newsserver?

+
+

Yes, you can. Under Configuration->Preferences for current account...->Advanced, you + can specify the exact port addresses you want to use. +

+
2.9. +

Does Sylpheed have options for threading messages?

+
+

Yes. You can switch it on and off in the View + menu, just select Thread view or press Ctrl-T. +

+
2.10. +

Can I create multiple levels of subfolders to store mail?

+
+

Absolutely. This is no problem.

+
2.11. +

Why isn't Sylpheed sending my mail out?

+
+

You need to create at least one account in order to + send. (This is a wonderful gotcha on LAN installs + with only a local mailbox feed). +

+
2.12. +

How do I apply a patch after downloading it?

+
+

Copy patch to sylpheed directory. + Apply the patch as follows: +

+

+ % patch -p0 < some.patch

+

+ Or, if it's gzipped: +

+

+ % gzip -dc some.patch.gz | patch -p0

+

+ Run ./autogen.sh, remove the generated /config.cache + file (unless you want to install in prefix + /usr/local). + Run ./configure with the appropriate options and + then make. + (Text as found on the former Sylpheed patches page.) +

+
2.13. +

How do I compile in support for compface pictures?

+
+

You have to have a package called libcompface + installed, so this is available for compiling into + Sylpheed. Note that the exact name of the package depends on OS or distribution you use. +

+
2.14. +

How do I make my own compface image?

+
+

The faces package contains a program called xbm2ikon script, + which converts a 48x48 xbm to the format suitable for + compface. Thanks to Jeff Dairiki, you can have a complete online course in this. Visit this page for the details. +

+
2.15. +

How can I tell my browser/newsclient/other program to use Sylpheed as email program?

+
+

In the settings part of the program, write + sylpheed --compose

+

+ Specific options for typical browsers: +

+
+
    +
  • +

    Opera: sylpheed --compose [mailto:%t][?subject=%s]

    +
    • +
  • +

    Galeon: sylpheed --compose "mailto:%t?subject=%s"

    +
    • +
+
+
2.16. +

How do I enable GPG support in Sylpheed?

+
+

When compiling Sylpheed, make sure you add --enable-gpgme in the ./configure command. + When that completes successfully, there is a Privacy section in the Common Preferences. +

+
2.17. +

Mutt does not recognize Sylpheed's MH structure

+
+

For this to work you need to use the touch command in every MH folder. "touch" the file .xmhcache and Mutt should do just fine. +

+
2.18. +

Viewing a GIF file within Sylpheed causes a segmentation fault.

+
+

In case this happens, you can easily fix that by adding the following to /etc/mime.types: + 

image/gif gif
2.19. +

How Sylpheed checks for new mail?

+
+

New mail can be retrieved either manually or automatically.

+

To check for new mail the manual way, you can:

+
+
    +
  1. +

    Either press the Get button on the toolbar to incorporate new mail for the current account only, or use the Get all button to incorporate new mail for all configured accounts. +

    +
    2. +
  2. +

    Or choose File->Mailbox->Check for new messages, or Check for new messages in all mailboxes. +

    +
    3. +
  3. +

    Or select Message->Receive->Get from current account, or Get from all accounts. +

    +
    4. +
+
+
+

Tip

+

If you have a POP3 account and don't want to retrieve all the new messages stored on remote server to your computer, you + can manage your account remotely (e.g. open or delete individual messages) by choosing Message->Receive->Remote mailbox...

+
+

If you prefer autochecking for new mail instead, first of all, make sure that you have checked Configuration->Common preferences...->Receive+Autocheck new mail every 10 minute(s). Optionally, you can adjust the interval value (in minutes) as well. +

+

Also check your settings under Configuration->Edit accounts... You will find this + at the top: Check the boxes on the 'G' column to enable message retrieval by 'Get all'. The setting applies on both manual and automatic + mail checks. +

+
2.20. +

How can I make Sylpheed notify me when new mail arrives?

+
+

Download Gkrellm or a similar program that is able to notify you of new incoming mail. Gkrellm is available at the Gkrellm page. +

+
2.21. +

Can I use a spell checker with Sylpheed?

+
+

Yes. You need to have GtkSpell installed prior to Sylpheed compilation. The support for GtkSpell is enabled by default in + configure. (If you want to disable it, make sure you add --disable-gtkspell in the ./configure command.) +

+

The GtkSpell option is not supported in Sylpheed for Windows (yet), so you will have no spell checking under this OS.

+
2.22. +

How can I make Sylpheed send my compface image in the mails?

+
+

In the Configuration->Preferences for current account...->Send check Add user-defined header and press Edit button. A dialog appears, add a header named "X-Face" and fill the value field with your face data. Note that if you paste + the data from a terminal into the field, some spurious newlines can be added, and these can mangle your face, be careful. +

+
2.23. +

How can I get the newest source code from the Sylpheed Subversion (SVN) repository?

+
+

Move to an appropriate directory, and after you run the command specified below, a source tree named trunk will be created under that directory: +

+

svn checkout svn://sylpheed.sraoss.jp/sylpheed/trunk

+

The subdirectories under the sylpheed directory are as follows: +

+
+
    +
  • +

    trunk/ - main tree +

    +
    • +
  • +

    branches/ - miscellaneous experimental branches +

    +
    • +
  • +

    tags/ - release-tagged branches +

    +
    • +
+
+

To update to the newest source tree, run the following command in the target directory:

+

svn update

+
2.24. +

I checked out the sources using SVN and can't find any configure script.

+
+

The SVN versions are meant to be used by developers rather than "normal" + users, so the source (or binary) distributions are easier to use. +

+
+
+

Yeah, but the latest features from SVN really look sexy...

+
+
+

You need to generate the configure script by running autogen.sh. + Be sure to have autoconf and automake packages installed for this. +

+
2.25. +

Running "autogen.sh" gives error messages that "AM_PATH_GDK_PIXBUF" or + "AM_PATH_(whatever)" is not found. +

+
+

There are some *.m4 files in the ac/missing directory. Try to copy + them into the ac directory and run autogen.sh again. +

+

+ If there are still some .m4 files not found (e.g. those from GTK+), try + to run % locate m4 | less or % locate aclocal | less to find additional directories containing those macros. If you find e.g. a + gtk.m4 in /opt/gnome/share/aclocal, change following line in + autogen.sh from + 

aclocal -I ac \

to

aclocal -I ac -I /opt/gnome/share/aclocal \

and run it again.

+
2.26. +

I don't want to compile in support for (...) any longer, but after running + "configure", those libraries are still used. +

+
+

Remove the config.cache file and run ./configure again. You should + also use make clean to avoid undefined references. +

+
2.27. +

How can I select different applications to open with specific MIME types?

+
+

The MIME-type to application associations are kept in /etc/mailcap. +

+
2.28. +

How can I change the suggested mimetype for attachments?

+
+

The extension to MIME-type associations are kept in /etc/mime.types

+
2.29. +

The folder list is not updated after I manually moved/copied folders.

+
+

You need to update Sylpheed cache. Right click on the mailbox and choose + Rebuild folder tree. +

+
2.30. +

How can I revert original settings, e.g. for fonts, key bindings, etc.?

+
+

Sylpheed keeps its configuration files in $HOME/.sylpheed-2.0/sylpheedrc (or %APPDATA%\Sylpheed\sylpheedrc under Windows) and creates default + entries, if none are found. So the easiest way is to quit Sylpheed, + temporarily renaming your $HOME/.sylpheed-2.0 (or %APPDATA%\Sylpheed\sylpheedrc) e.g. to *.bak and restarting + Sylpheed in order to get default entries. +

+
2.31. +

What environment variables have effect on Sylpheed?

+
+

Here are the most common variables:

+
+
    +
  • +

    HOME + - location of .sylpheed-2.0 (config directory) and default folder for Mailboxes. +

    +
    • +
  • +

    LANG, +

    +
    • +
  • +

    LC_ALL, +

    +
    • +
  • +

    LC_CTYPE, +

    +
    • +
  • +

    LC_MESSAGES - locale settings, e.g. language and date format. +

    +
    • +
+
+

For more information on how to make Sylpheed display your language, see the relevant question. +

+
2.32. +

Special characters (e.g. umlauts) are not displayed correctly.

+
+

In most cases, this is caused by fonts that use an unsuitable encoding on a not Unicode-based system. (On a Unicode-based + system, fonts should support all thinkable characters for the vast majority of languages.) +

+

Choose Configuration->Common preferences...->Display->General, and click the button right to Text font. Now, a special dialog appears that allows you to pick a desirable font family, style, and size. +

+

You should also make sure that your environment variables regarding locale + settings have sensible values. +

+
2.33. +

How can I convert my old mailbox/address book from (some mail client).

+
+

You can try to + export your old mailbox to MH, MBOX or EML format. +

+
+

Tip

+

Take a look at the Add sender to address book... item from the Tools + menu, it could be a useful alternative or addition, when importing your old + contacts. +

+
+
2.34. +

What config files are there, and what are they used for?

+
+

Sylpheed config files can be found in $HOME/.sylpheed-2.0 (under Windows, the path is %APPDATA%\Sylpheed). They are in plain + text format and quite easy to understand, so don't fear to take a look + into them using a text editor. +

+
+
    +
  • +

    sylpheedrc - main configuration: nearly all options from the + settings window, e.g. mailbox location, font + entries, etc. +

    +
    • +
  • +

    accountrc - settings for POP/IMAP/NNTP accounts +

    +
    • +
  • +

    actionsrc - user-defined actions +

    +
    • +
  • +

    addrbook-*.xml - contents of your address book +

    +
    • +
  • +

    customheaderrc - contains user-defined header lines +

    +
    • +
  • +

    dispheaderrc - headers to display above the mail body +

    +
    • +
  • +

    filter.xml - filter settings +

    +
    • +
  • +

    folderlist.xml - folder specific settings, e.g. hiding + read messages, sort order, etc. +

    +
    • +
  • +

    menurc - key bindings +

    +
    • +
+
+
2.35. +

How do I change the location of user profile directory under Windows?

+
+

The configuration files and the mailboxes are saved under the following + location (%APPDATA%\Sylpheed) by default: +

+
+
    +
  • +

    Windows 2000/XP: + C:\Documents and Settings\(user name)\Application Data\Sylpheed

    +
    • +
  • +

    Windows Vista/Seven: + C:\Users\(user name)\AppData\Roaming\Sylpheed

    +
    • +
+
+

If you want to change the location of the configuration files, you can + specify it by the command line option --configdir "directory name". + Create a shortcut of sylpheed.exe, and append the option to the link target + like the following: + 

"C:\Program Files\Sylpheed\sylpheed.exe" --configdir "D:\Sylpheed"

If sylpheed.ini file exists at the same location as sylpheed.exe, it will be + loaded at startup. With this approach, you can make Sylpheed completely portable + independent of drive letters etc., and you can install it in removable media + such as USB memory. +

+
+

Note

+

The installer version, and GnuPG and GPGME use registry.

+
+

The sample INI file is included in the Sylpheed for Windows installation package as sample-sylpheed.ini. + Please copy or rename it to use. + ipcport specifies the port number of socket for IPC (default is 50215). + configdir specifies the location of configuration files as a relative + path from the folder in which sylpheed.exe is located, or an absolute path. +

+

(The text above is a slightly modified excerpt from the README-win32.txt file, which you should find within the C:\Program Files\Sylpheed directory.) +

+
2.36. +

Can I run multiple instances of Sylpheed?

+
+

Yes, Sylpheed 3.1 adds support for this often requested feature. The format of the multiple instances command is as follows:

+

sylpheed --instance-id ID --configdir path-to-alternative-configdir

+

Default ID is set to sylpheed, so you can specify any other instance + ID. The ID is used for the name of unix domain + socket (under UNIX), or mutex name (under Windows). configdir specifies the configuration directory, i.e. the location of configuration files you want to use with the given instance. +

+
+

Warning

+

Do not share same configuration directories or mailboxes across multiple instances as this may lead to an unexpected application + behavior! +

+
+
2.37. +

What to do when printing an email prints off the paper?

+
+

You can use enscript for this. Use enscript %s to print everything on one page, or enscript -U2 %s for printing two logical pages on one physical page. +

+
+
+
+
+
+ + + + + + + + + + + +
Prev  +   Next
Chapter 1. Sylpheed FAQ - General Information Home Chapter 3. Sylpheed FAQ - Interface
+
+ + \ 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 @@ + + + + + Chapter 3. Sylpheed FAQ - Interface + + + + + + + + + + +
+ + + + + + + + + +
Chapter 3. Sylpheed FAQ - Interface
Prev  +   Next
+
+
+
+
+
+
+

Chapter 3. Sylpheed FAQ - Interface +

+
+
+
+
+
+
3.1. How do I make Sylpheed display my language?
+
3.2. I don't like the default font. Can I change that?
+
3.3. There are too many columns in the message list!
+
3.4. How do I disable or enable the alternating row colors in the message list?
+
3.5. Can I use a different editor to write my mails?
+
3.6. How to change the font size in the Sylpheed interface?
+
3.7. Sylpheed saves my outgoing mail (in Outbox). Can I make it stop doing that?
+
3.8. How can I change the key bindings (hotkeys) in Sylpheed?
+
3.9. Can I close windows without the mouse?
+
3.10. Can I change the way the date is displayed in the message summary?
+
3.11. Why can't I see the compface pictures?
+
3.12. I still can't see the pictures. Why not?
+
3.13. Why does the URL launcher not launch my web browser?
+
3.14. Attachments with spaces in the name won't open!
+
3.15. Execute command for my dynamic signature seems not to be working!
+
3.16. Where is the Bcc when I compose a mail?
+
3.17. How do I change the toolbar?
+
3.18. Why isn't the next message displayed when I delete a message?
+
3.19. How can I remove mailing list information from Subject headers?
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
3.1. +

How do I make Sylpheed display my language?

+
+

You have to set some environment variables, such as + LANG, LC_CTYPE, LC_MESSAGES to your local language. + Usually LANG (or LC_ALL) is sufficient. Note that modern distributions and operating systems do this for you automatically. +

+

Under UNIX, if you need to set e.g. the LANG environment variable manually, execute the following command (using sh or related shell): +

+

export LANG=value

+

Replace value with a valid ISO language code (e.g. en_GB for British English). +

+

If you intend to set the displayed language manually under Windows, you can do so by creating the + LANG environment variable with a valid ISO language code value under Control Panel->System->Advanced+Environment Variables. +

+

Also see the question regarding environment variables that have effect on Sylpheed. +

+
3.2. +

I don't like the default font. Can I change that?

+
+

Yes. In Configuration->Common preferences..., under the + Display tab. +

+
3.3. +

There are too many columns in the message list!

+
+

In Configuration->Common preferences... under the + Display tab, you can press the button Set display item of summary.... That pops up a screen with all the + options you can show or leave out of the message + list. +

+
3.4. +

How do I disable or enable the alternating row colors in the message list?

+
+

Under UNIX, you can directly edit the appropriate hidden setting stored in the $HOME/.sylpheed-2.0/sylpheedrc configuration file by changing the setting value to 0, or 1, respectively (default is on, i.e. 1): + 

enable_rules_hint=0
+

Tip

+

There are various other hidden settings that can be adjusted in your sylpheedrc configuration file, see the README file for details. +

+
+

The above does not work under Windows, however, so you have to edit the C:\Program Files\Sylpheed\share\themes\MS-Windows\gtk-2.0\gtkrc file and set the following setting to 1, or 0, respectively (default is off under Windows, i.e. 0): + 

GtkTreeView::allow-rules = 1
+

Note

+

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 gtkrc file somewhere safe. +

+
+
3.5. +

Can I use a different editor to write my mails?

+
+

You can. In Configuration->Common preferences, under + the Details and External commands tabs, you can define your editor of choice. + Remember, if you want to use a command line editor + like vi or emacs, to write the name of the shell + (term, term, rxvt) with the -e parameter in front of + the editor. E.g.: rxvt -e vi %s. +

+

Also, make sure that you have checked Automatically launch the external editor in Common preferences->Compose->Editor, if you want the editor of your choice to be launched every time you begin composing a message. +

+
3.6. +

How to change the font size in the Sylpheed interface?

+
+

You can set the GTK+ font by $HOME/.gtkrc-2.0, or + $HOME/.gtkrc-2.0.mine, + (which is included by $HOME/.gtkrc-2.0). + For example: + 

style "default" {
+       font = "-adobe-helvetica-medium-r-normal--12-*-*-*-*-*-iso8859-1 "
+}
+widget_class "*" style "default"
+
3.7. +

Sylpheed saves my outgoing mail (in Outbox). Can I make it stop doing that?

+
+

In Configuration->Common preferences..., there is a + checkbox Save sent message to outbox. Uncheck it, + and it's solved. +

+
3.8. +

How can I change the key bindings (hotkeys) in Sylpheed?

+
+

Unlike Sylpheed 1.x, Sylpheed 2.x and 3.x doesn't allow direct modification of the menu shortcuts by default. Nevertheless, + you can use the following methods to configure them: +

+
+
    +
  1. +

    Using GNOME 2.8 or later: run gconf-editor from Applications->System Tools->Configuration Editor. Select desktop->gnome->interface and check can-change-accels there. +

    +
    2. +
  2. +

    Using GNOME before 2.8, or other environments: add the following line to the file ~/.gtkrc-2.0 (or create a new one, if it doesn't exist): + 

    gtk-can-change-accels = 1
    3. +
  3. +

    When Sylpheed is not running, directly edit ~/.sylpheed-2.0/menurc with a text editor. +

    +
    4. +
+
+

After that, the key binding change itself is very simple. Suppose you want to assign a + shortcut key to a function, e.g. sending all mail + out should start when you press Ctrl-Y. Click the + Message menu and move the mouse over Send all messages. Now you press Ctrl-Y. Immediately the menu + text is updated and the function is in place. Please + note that a previous function that Ctrl-Y was + assigned to, will no longer have a shortcut key. If + you want to remove the key binding, do the same + thing, but press the Delete key on the menu item. + Then the key binding is removed. +

+

Also see Configuration->Common preferences...->Details->Interface+Set key bindings... where you are able to reset the Default key bindings, or use other predefined key bindings. +

+
3.9. +

Can I close windows without the mouse?

+
+

Of course! Not all windows, but by pressing Escape, + you can close the address book, the window of viewing + a mail source (View->Message source), the window of + viewing the headers, and several others. Just give + it a try and you will find all of them. +

+
3.10. +

Can I change the way the date is displayed in the message summary?

+
+

As of 0.4.65 you can. The options are:

     %y = year in numbers     %m = month in number
+     %d = day in numbers      %c = date/time for locale
+     %A = full weekday name   %a = short month name
+     %B = full month name     %b = short month name
+     %H = hours in 24-clock   %I = hours in 12-clock

For more information, go to the Configuration->Common preferences->Display->General and choose the ... labeled button. + For more options, see man 3 strftime. +

+
3.11. +

Why can't I see the compface pictures?

+
+

You need to enable displaying of the header pane in the + general preferences. +

+
3.12. +

I still can't see the pictures. Why not?

+
+

You may not have compiled in Compface support. See the appropriate question in the Installation and Configuration section.

+
3.13. +

Why does the URL launcher not launch my web browser?

+
+

You need to double click the URL. + Also, check that you have configured your web browser correctly in Configuration->Common preferences...-> Details->External commands. +

+
3.14. +

Attachments with spaces in the name won't open!

+
+

When you try to launch a helper application, like an image viewer, with an attachment that has spaces in the name, put quotes + around the %s + parameter. Example: gedit '%s'

+
3.15. +

Execute command for my dynamic signature seems not to be working!

+
+

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 Account preferences->Compose->Signature+Command output) using either forward slashes or double + backslashes for paths, for example: +

+

cmd /c 'c:\\signature.bat'

+

Note that it is also recommended to enclose paths with single quotes, as is illustrated above.

+
3.16. +

Where is the Bcc when I compose a mail?

+
+

Open Configuration->Preferences for current account...->Compose. There you can check the Bcc checkbox and optionally enter an email address. +

+
3.17. +

How do I change the toolbar?

+
+

Go to View->Customize toolbar... and select items from the Available items list to be displayed on the toolbar. You can modify the order by using the Up or Down button. The customization dialog also offers you to revert your modifications to default. +

+
3.18. +

Why isn't the next message displayed when I delete a message?

+
+

Go to Configuration->Common preferences...->Details->Interface, and select Always open messages in summary when selected. +

+
3.19. +

How can I remove mailing list information from Subject headers?

+
+

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 [sylpheed:33101]. 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. +

+

To do that, right-click on a folder from the folder tree, and select Properties... In the Folder properties dialog, check Don't display [...] or (...) at the beginning of subject in summary, or Delete [...] or (...) at the beginning of subject on reply, respectively. +

+
+
+
+
+
+ + + + + + + + + + + +
Prev  +   Next
Chapter 2. Sylpheed FAQ - Installation and Configuration Home Appendix A. GNU Free Documentation License
+
+ + \ 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 @@ + + + + + Appendix A. GNU Free Documentation License + + + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + + +
Appendix A. GNU Free Documentation License
Prev  +   
+
+
+
+
+
+
+

GNU Free Documentation License +

+
+
+

Version 1.2, November 2002

+
+
+

Copyright © 2000,2001,2002 Free Software Foundation, Inc.

+
+
+
+

Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA02110-1301USA

+
+

Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. +

+
+
+
+

Version 1.2, November 2002

+
+
+
+
+
+
A.1. PREAMBLE
+
A.2. APPLICABILITY AND DEFINITIONS
+
A.3. VERBATIM COPYING
+
A.4. COPYING IN QUANTITY
+
A.5. MODIFICATIONS
+
A.6. COMBINING DOCUMENTS
+
A.7. COLLECTIONS OF DOCUMENTS
+
A.8. AGGREGATION WITH INDEPENDENT WORKS
+
A.9. TRANSLATION
+
A.10. TERMINATION
+
A.11. FUTURE REVISIONS OF THIS LICENSE
+
A.12. ADDENDUM: How to use this License for your documents
+
+
+
+
+
+
+

A.1. PREAMBLE +

+
+
+
+

The purpose of this License is to make a manual, textbook, or + other functional and useful document "free" in the sense of freedom: to + assure everyone the effective freedom to copy and redistribute it, with + or without modifying it, either commercially or noncommercially. + Secondarily, this License preserves for the author and publisher a way + to get credit for their work, while not being considered responsible for + modifications made by others. +

+

This License is a kind of "copyleft", which means that derivative + works of the document must themselves be free in the same sense. It + complements the GNU General Public License, which is a copyleft license + designed for free software. +

+

We have designed this License in order to use it for manuals for + free software, because free software needs free documentation: a free + program should come with manuals providing the same freedoms that the + software does. But this License is not limited to software manuals; it + can be used for any textual work, regardless of subject matter or + whether it is published as a printed book. We recommend this License + principally for works whose purpose is instruction or reference. +

+
+
+
+
+
+

A.2. APPLICABILITY AND DEFINITIONS +

+
+
+
+

This License applies to any manual or other work, in + any medium, that contains a notice placed by the copyright holder saying + it can be distributed under the terms of this License. Such a notice + grants a world-wide, royalty-free license, unlimited in duration, to use + that work under the conditions stated herein. The "Document", below, + refers to any such manual or work. Any member of the public is a + licensee, and is addressed as "you". You accept the license if you + copy, modify or distribute the work in a way requiring permission under + copyright law. +

+

A "Modified Version" of the Document means any + work containing the Document or a portion of it, either copied verbatim, + or with modifications and/or translated into another language. +

+

A "Secondary Section" is a named appendix or + a front-matter section of the Document that deals exclusively with the + relationship of the publishers or authors of the Document to the + Document's overall subject (or to related matters) and contains nothing + that could fall directly within that overall subject. (Thus, if the + Document is in part a textbook of mathematics, a Secondary Section may + not explain any mathematics.) The relationship could be a matter of + historical connection with the subject or with related matters, or of + legal, commercial, philosophical, ethical or political position + regarding them. +

+

The "Invariant Sections" are certain Secondary + Sections whose titles are designated, as being those of Invariant + Sections, in the notice that says that the Document is released under + this License. If a section does not fit the above definition of + Secondary then it is not allowed to be designated as Invariant. The + Document may contain zero Invariant Sections. If the Document does not + identify any Invariant Sections then there are none. +

+

The "Cover Texts" are certain short passages of + text that are listed, as Front-Cover Texts or Back-Cover Texts, in the + notice that says that the Document is released under this License. A + Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at + most 25 words. +

+

A "Transparent" copy of the Document means a + machine-readable copy, represented in a format whose specification is + available to the general public, that is suitable for revising the + document straightforwardly with generic text editors or (for images + composed of pixels) generic paint programs or (for drawings) some widely + available drawing editor, and that is suitable for input to text + formatters or for automatic translation to a variety of formats suitable + for input to text formatters. A copy made in an otherwise Transparent + file format whose markup, or absence of markup, has been arranged to + thwart or discourage subsequent modification by readers is not + Transparent. An image format is not Transparent if used for any + substantial amount of text. A copy that is not "Transparent" is called + "Opaque". +

+

Examples of suitable formats for Transparent copies include plain + ASCII without markup, Texinfo input format, LaTeX input format, SGML or + XML using a publicly available DTD, and standard-conforming simple HTML, + PostScript or PDF designed for human modification. Examples of + transparent image formats include PNG, XCF and JPG. Opaque formats + include proprietary formats that can be read and edited only by + proprietary word processors, SGML or XML for which the DTD and/or + processing tools are not generally available, and the machine-generated + HTML, PostScript or PDF produced by some word processors for output + purposes only. +

+

The "Title Page" means, for a printed book, + the title page itself, plus such following pages as are needed to hold, + legibly, the material this License requires to appear in the title page. + For works in formats which do not have any title page as such, "Title + Page" means the text near the most prominent appearance of the work's + title, preceding the beginning of the body of the text. +

+

A section "Entitled XYZ" means a named subunit + of the Document whose title either is precisely XYZ or contains XYZ in + parentheses following text that translates XYZ in another language. + (Here XYZ stands for a specific section name mentioned below, such as + "Acknowledgements", "Dedications", "Endorsements", or "History".) To + "Preserve the Title" of such a section when you modify the Document + means that it remains a section "Entitled XYZ" according to this + definition. +

+

The Document may include Warranty Disclaimers next to the notice + which states that this License applies to the Document. These Warranty + Disclaimers are considered to be included by reference in this License, + but only as regards disclaiming warranties: any other implication that + these Warranty Disclaimers may have is void and has no effect on the + meaning of this License. +

+
+
+
+
+
+

A.3. VERBATIM COPYING +

+
+
+
+

You may copy and distribute the Document in any medium, either + commercially or noncommercially, provided that this License, the + copyright notices, and the license notice saying this License applies to + the Document are reproduced in all copies, and that you add no other + conditions whatsoever to those of this License. You may not use + technical measures to obstruct or control the reading or further copying + of the copies you make or distribute. However, you may accept + compensation in exchange for copies. If you distribute a large enough + number of copies you must also follow the conditions in section 3. + +

+

You may also lend copies, under the same conditions stated above, + and you may publicly display copies. +

+
+
+
+
+
+

A.4. COPYING IN QUANTITY +

+
+
+
+

If you publish printed copies (or copies in media that commonly + have printed covers) of the Document, numbering more than 100, and the + Document's license notice requires Cover Texts, you must enclose the + copies in covers that carry, clearly and legibly, all these Cover Texts: + Front-Cover Texts on the front cover, and Back-Cover Texts on the back + cover. Both covers must also clearly and legibly identify you as the + publisher of these copies. The front cover must present the full title + with all words of the title equally prominent and visible. You may add + other material on the covers in addition. Copying with changes limited + to the covers, as long as they preserve the title of the Document and + satisfy these conditions, can be treated as verbatim copying in other + respects. +

+

If the required texts for either cover are too voluminous to fit + legibly, you should put the first ones listed (as many as fit + reasonably) on the actual cover, and continue the rest onto adjacent + pages. +

+

If you publish or distribute Opaque copies of the Document + numbering more than 100, you must either include a machine-readable + Transparent copy along with each Opaque copy, or state in or with each + Opaque copy a computer-network location from which the general + network-using public has access to download using public-standard + network protocols a complete Transparent copy of the Document, free of + added material. If you use the latter option, you must take reasonably + prudent steps, when you begin distribution of Opaque copies in quantity, + to ensure that this Transparent copy will remain thus accessible at the + stated location until at least one year after the last time you + distribute an Opaque copy (directly or through your agents or retailers) + of that edition to the public. +

+

It is requested, but not required, that you contact the authors of + the Document well before redistributing any large number of copies, to + give them a chance to provide you with an updated version of the + Document. +

+
+
+
+
+
+

A.5. MODIFICATIONS +

+
+
+
+

You may copy and distribute a Modified Version of the Document + under the conditions of sections 2 and 3 above, provided that you + release the Modified Version under precisely this License, with the + Modified Version filling the role of the Document, thus licensing + distribution and modification of the Modified Version to whoever + possesses a copy of it. In addition, you must do these things in the + Modified Version: +

+

GNU FDL Modification Conditions

+
    +
  1. 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. +
    2. +
  2. 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. +
    3. +
  3. State on the Title page the name of the publisher of the Modified Version, as the publisher.
    4. +
  4. Preserve all the copyright notices of the Document.
    5. +
  5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
    6. +
  6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version + under the terms of this License, in the form shown in the Addendum below. +
    7. +
  7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license + notice. +
    8. +
  8. Include an unaltered copy of this License.
    9. +
  9. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, + and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, + create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing + the Modified Version as stated in the previous sentence. +
    10. +
  10. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and + likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" + section. You may omit a network location for a work that was published at least four years before the Document itself, or + if the original publisher of the version it refers to gives permission. +
    11. +
  11. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section + all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. +
    12. +
  12. 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. +
    13. +
  13. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.
    14. +
  14. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.
    15. +
  15. Preserve any Warranty Disclaimers.
    16. +
+
+

If the Modified Version includes new front-matter sections or + appendices that qualify as Secondary Sections and contain no material + copied from the Document, you may at your option designate some or all + of these sections as invariant. To do this, add their titles to the + list of Invariant Sections in the Modified Version's license notice. + These titles must be distinct from any other section titles. +

+

You may add a section Entitled "Endorsements", provided it + contains nothing but endorsements of your Modified Version by various + parties--for example, statements of peer review or that the text has + been approved by an organization as the authoritative definition of a + standard. +

+

You may add a passage of up to five words as a Front-Cover Text, + and a passage of up to 25 words as a Back-Cover Text, to the end of the + list of Cover Texts in the Modified Version. Only one passage of + Front-Cover Text and one of Back-Cover Text may be added by (or through + arrangements made by) any one entity. If the Document already includes + a cover text for the same cover, previously added by you or by + arrangement made by the same entity you are acting on behalf of, you may + not add another; but you may replace the old one, on explicit permission + from the previous publisher that added the old one. +

+

The author(s) and publisher(s) of the Document do not by this + License give permission to use their names for publicity for or to + assert or imply endorsement of any Modified Version. +

+
+
+
+
+
+

A.6. COMBINING DOCUMENTS +

+
+
+
+

You may combine the Document with other documents released under + this License, under the terms defined in section 4 above for modified versions, provided that you include in the + combination all of the Invariant Sections of all of the original + documents, unmodified, and list them all as Invariant Sections of your + combined work in its license notice, and that you preserve all their + Warranty Disclaimers. +

+

The combined work need only contain one copy of this License, and + multiple identical Invariant Sections may be replaced with a single + copy. If there are multiple Invariant Sections with the same name but + different contents, make the title of each such section unique by adding + at the end of it, in parentheses, the name of the original author or + publisher of that section if known, or else a unique number. Make the + same adjustment to the section titles in the list of Invariant Sections + in the license notice of the combined work. +

+

In the combination, you must combine any sections Entitled + "History" in the various original documents, forming one section + Entitled "History"; likewise combine any sections Entitled + "Acknowledgements", and any sections Entitled "Dedications". You must + delete all sections Entitled "Endorsements". +

+
+
+
+
+
+

A.7. COLLECTIONS OF DOCUMENTS +

+
+
+
+

You may make a collection consisting of the Document and other + documents released under this License, and replace the individual copies + of this License in the various documents with a single copy that is + included in the collection, provided that you follow the rules of this + License for verbatim copying of each of the documents in all other + respects. +

+

You may extract a single document from such a collection, and + distribute it individually under this License, provided you insert a + copy of this License into the extracted document, and follow this + License in all other respects regarding verbatim copying of that + document. +

+
+
+
+
+
+

A.8. AGGREGATION WITH INDEPENDENT WORKS +

+
+
+
+

A compilation of the Document or its derivatives with other + separate and independent documents or works, in or on a volume of a + storage or distribution medium, is called an "aggregate" if the + copyright resulting from the compilation is not used to limit the legal + rights of the compilation's users beyond what the individual works + permit. When the Document is included in an aggregate, this License does + not apply to the other works in the aggregate which are not themselves + derivative works of the Document. +

+

If the Cover Text requirement of section 3 is applicable to these + copies of the Document, then if the Document is less than one half of + the entire aggregate, the Document's Cover Texts may be placed on covers + that bracket the Document within the aggregate, or the electronic + equivalent of covers if the Document is in electronic form. Otherwise + they must appear on printed covers that bracket the whole + aggregate. +

+
+
+
+
+
+

A.9. TRANSLATION +

+
+
+
+

Translation is considered a kind of modification, so you may + distribute translations of the Document under the terms of section 4. + Replacing Invariant Sections with translations requires special + permission from their copyright holders, but you may include + translations of some or all Invariant Sections in addition to the + original versions of these Invariant Sections. You may include a + translation of this License, and all the license notices in the + Document, and any Warranty Disclaimers, provided that you also include + the original English version of this License and the original versions + of those notices and disclaimers. In case of a disagreement between the + translation and the original version of this License or a notice or + disclaimer, the original version will prevail. +

+

If a section in the Document is Entitled "Acknowledgements", + "Dedications", or "History", the requirement (section 4) to Preserve its + Title (section 1) will typically require changing the actual + title. +

+
+
+
+
+
+

A.10. TERMINATION +

+
+
+
+

You may not copy, modify, sublicense, or distribute the Document + except as expressly provided for under this License. Any other attempt + to copy, modify, sublicense or distribute the Document is void, and will + automatically terminate your rights under this License. However, + parties who have received copies, or rights, from you under this License + will not have their licenses terminated so long as such parties remain + in full compliance. +

+
+
+
+
+
+

A.11. FUTURE REVISIONS OF THIS LICENSE +

+
+
+
+

The Free Software Foundation may publish new, revised versions of + the GNU Free Documentation License from time to time. Such new versions + will be similar in spirit to the present version, but may differ in + detail to address new problems or concerns. See + http://www.gnu.org/copyleft/. +

+

Each version of the License is given a distinguishing version + number. If the Document specifies that a particular numbered version of + this License "or any later version" applies to it, you have the option + of following the terms and conditions either of that specified version + or of any later version that has been published (not as a draft) by the + Free Software Foundation. If the Document does not specify a version + number of this License, you may choose any version ever published (not + as a draft) by the Free Software Foundation. +

+
+
+
+
+
+

A.12. ADDENDUM: How to use this License for your documents +

+
+
+
+

To use this License in a document you have written, include a copy + of the License in the document and put the following copyright and + license notices just after the title page: +

+
+
+

Sample Invariant Sections list

+
+

+ Copyright (c) YEAR YOUR NAME. + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.2 + or any later version published by the Free Software Foundation; + with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. + A copy of the license is included in the section entitled "GNU + Free Documentation License". + +

+
+
+

If you have Invariant Sections, Front-Cover Texts and Back-Cover + Texts, replace the "with...Texts." line with this: +

+
+
+

Sample Invariant Sections list

+
+

+ with the Invariant Sections being LIST THEIR TITLES, with the + Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. + +

+
+
+

If you have Invariant Sections without Cover Texts, or some other + combination of the three, merge those two alternatives to suit the + situation. +

+

If your document contains nontrivial examples of program code, we + recommend releasing these examples in parallel under your choice of free + software license, such as the GNU General Public License, to permit + their use in free software. +

+
+
+
+
+ + + + + + + + + + + +
Prev  +   
Chapter 3. Sylpheed FAQ - Interface Home 
+
+ + \ 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 @@ + + + + + Sylpheed FAQ + + + + + + + + + +
+ + + + + + + + + +
Sylpheed FAQ
   Next
+
+
+
+
+
+
+

Sylpheed FAQ +

+
+
+
+

Paul Kater

+
+
+
+
+

Jens Oberender

+
+
+
+
+

Francois Barriere

+
+
+
+
+

Olivier Delhomme

+
+
+
+
+

Petr Kovar

+
+
+
+

Copyright © 2010 The Sylpheed Documentation Project.

+
+
+

Permission is granted to copy, distribute and/or modify this + document under the terms of the GNU Free Documentation License, Version + 1.2 or any later version published by the Free Software Foundation; with + no Invariant Sections, with no Front-Cover Texts, and no Back-Cover + Texts. A copy of the license is included in the section entitled "GNU + Free Documentation License". + +

+
+
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Revision History
Revision 1.92005/07/08OD
Ported to DocBook XML.
Revision 2.02009/10/02PK
Finished porting to DocBook XML, updated many questions across the document to conform with Sylpheed 2.7.1.
Revision 2.12010/04/14PK
Updated with regard to Sylpheed 3.0.2.
Revision 2.22010/08/09PK
Updates for the upcoming Sylpheed 3.1.
+
+
+
+
+

Abstract

+

This document contains answers to various questions, which are frequently asked by Sylpheed users. It consists of three sections + providing general information, information on Sylpheed installation and configuration, and on Sylpheed interface. +

+
+
+
+
+
+
+

Table of Contents

+
+
1. Sylpheed FAQ - General Information
+
2. Sylpheed FAQ - Installation and Configuration
+
3. Sylpheed FAQ - Interface
+
A. GNU Free Documentation License
+
+
+
+
+
+ + + + + + + + + + + +
   Next
   Chapter 1. Sylpheed FAQ - General Information
+
+ + \ No newline at end of file diff --git a/faq/es/Makefile.am b/faq/es/Makefile.am new file mode 100644 index 0000000..a3e82c1 --- /dev/null +++ b/faq/es/Makefile.am @@ -0,0 +1,11 @@ +faqdatadir = $(faqdir)/es + +faqdata_DATA = \ + sylpheed-faq-1.html \ + sylpheed-faq-2.html \ + sylpheed-faq-3.html \ + sylpheed-faq.html + +# generated by `ls -1 | sed -e 's/\(.*\)/ \1 \'` + +EXTRA_DIST = $(faqdata_DATA) diff --git a/faq/es/Makefile.in b/faq/es/Makefile.in new file mode 100644 index 0000000..c083f2c --- /dev/null +++ b/faq/es/Makefile.in @@ -0,0 +1,552 @@ +# Makefile.in generated by automake 1.14.1 from Makefile.am. +# @configure_input@ + +# Copyright (C) 1994-2013 Free Software Foundation, Inc. + +# This Makefile.in is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY, to the extent permitted by law; without +# even the implied warranty of MERCHANTABILITY or FITNESS FOR A +# PARTICULAR PURPOSE. + +@SET_MAKE@ + +VPATH = @srcdir@ +am__is_gnu_make = test -n '$(MAKEFILE_LIST)' && test -n '$(MAKELEVEL)' +am__make_running_with_option = \ + case $${target_option-} in \ + ?) ;; \ + *) echo "am__make_running_with_option: internal error: invalid" \ + "target option '$${target_option-}' specified" >&2; \ + exit 1;; \ + esac; \ + has_opt=no; \ + sane_makeflags=$$MAKEFLAGS; \ + if $(am__is_gnu_make); then \ + sane_makeflags=$$MFLAGS; \ + else \ + case $$MAKEFLAGS in \ + *\\[\ \ ]*) \ + bs=\\; \ + sane_makeflags=`printf '%s\n' "$$MAKEFLAGS" \ + | sed "s/$$bs$$bs[$$bs $$bs ]*//g"`;; \ + esac; \ + fi; \ + skip_next=no; \ + strip_trailopt () \ + { \ + flg=`printf '%s\n' "$$flg" | sed "s/$$1.*$$//"`; \ + }; \ + for flg in $$sane_makeflags; do \ + test $$skip_next = yes && { skip_next=no; continue; }; \ + case $$flg in \ + *=*|--*) continue;; \ + -*I) strip_trailopt 'I'; skip_next=yes;; \ + -*I?*) strip_trailopt 'I';; \ + -*O) strip_trailopt 'O'; skip_next=yes;; \ + -*O?*) strip_trailopt 'O';; \ + -*l) strip_trailopt 'l'; skip_next=yes;; \ + -*l?*) strip_trailopt 'l';; \ + -[dEDm]) skip_next=yes;; \ + -[JT]) skip_next=yes;; \ + esac; \ + case $$flg in \ + *$$target_option*) has_opt=yes; break;; \ + esac; \ + done; \ + test $$has_opt = yes +am__make_dryrun = (target_option=n; $(am__make_running_with_option)) +am__make_keepgoing = (target_option=k; $(am__make_running_with_option)) +pkgdatadir = $(datadir)/@PACKAGE@ +pkgincludedir = $(includedir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkglibexecdir = $(libexecdir)/@PACKAGE@ +am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd +install_sh_DATA = $(install_sh) -c -m 644 +install_sh_PROGRAM = $(install_sh) -c +install_sh_SCRIPT = $(install_sh) -c +INSTALL_HEADER = $(INSTALL_DATA) +transform = $(program_transform_name) +NORMAL_INSTALL = : +PRE_INSTALL = : +POST_INSTALL = : +NORMAL_UNINSTALL = : +PRE_UNINSTALL = : +POST_UNINSTALL = : +build_triplet = @build@ +host_triplet = @host@ +target_triplet = @target@ +subdir = faq/es +DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/Makefile.am \ + $(top_srcdir)/mkinstalldirs +ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 +am__aclocal_m4_deps = $(top_srcdir)/ac/aclocal-include.m4 \ + $(top_srcdir)/ac/gnupg-check-typedef.m4 \ + $(top_srcdir)/configure.ac +am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ + $(ACLOCAL_M4) +mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs +CONFIG_HEADER = $(top_builddir)/config.h +CONFIG_CLEAN_FILES = +CONFIG_CLEAN_VPATH_FILES = +AM_V_P = $(am__v_P_@AM_V@) +am__v_P_ = $(am__v_P_@AM_DEFAULT_V@) +am__v_P_0 = false +am__v_P_1 = : +AM_V_GEN = $(am__v_GEN_@AM_V@) +am__v_GEN_ = $(am__v_GEN_@AM_DEFAULT_V@) +am__v_GEN_0 = @echo " GEN " $@; +am__v_GEN_1 = +AM_V_at = $(am__v_at_@AM_V@) +am__v_at_ = $(am__v_at_@AM_DEFAULT_V@) +am__v_at_0 = @ +am__v_at_1 = +SOURCES = +DIST_SOURCES = +am__can_run_installinfo = \ + case $$AM_UPDATE_INFO_DIR in \ + n|no|NO) false;; \ + *) (install-info --version) >/dev/null 2>&1;; \ + esac +am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`; +am__vpath_adj = case $$p in \ + $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \ + *) f=$$p;; \ + esac; +am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`; +am__install_max = 40 +am__nobase_strip_setup = \ + srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'` +am__nobase_strip = \ + for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||" +am__nobase_list = $(am__nobase_strip_setup); \ + for p in $$list; do echo "$$p $$p"; done | \ + sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \ + $(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \ + if (++n[$$2] == $(am__install_max)) \ + { print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \ + END { for (dir in files) print dir, files[dir] }' +am__base_list = \ + sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \ + sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g' +am__uninstall_files_from_dir = { \ + test -z "$$files" \ + || { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \ + || { echo " ( cd '$$dir' && rm -f" $$files ")"; \ + $(am__cd) "$$dir" && rm -f $$files; }; \ + } +am__installdirs = "$(DESTDIR)$(faqdatadir)" +DATA = $(faqdata_DATA) +am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) $(LISP) +DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) +ACLOCAL = @ACLOCAL@ +ALLOCA = @ALLOCA@ +AMTAR = @AMTAR@ +AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@ +AR = @AR@ +AUTOCONF = @AUTOCONF@ +AUTOHEADER = @AUTOHEADER@ +AUTOMAKE = @AUTOMAKE@ +AWK = @AWK@ +BUILD_REVISION = @BUILD_REVISION@ +CATALOGS = @CATALOGS@ +CATOBJEXT = @CATOBJEXT@ +CC = @CC@ +CCDEPMODE = @CCDEPMODE@ +CFLAGS = @CFLAGS@ +CPP = @CPP@ +CPPFLAGS = @CPPFLAGS@ +CYGPATH_W = @CYGPATH_W@ +DATADIRNAME = @DATADIRNAME@ +DEFS = @DEFS@ +DEPDIR = @DEPDIR@ +DEVEL_VERSION = @DEVEL_VERSION@ +DLLTOOL = @DLLTOOL@ +DSYMUTIL = @DSYMUTIL@ +DUMPBIN = @DUMPBIN@ +ECHO_C = @ECHO_C@ +ECHO_N = @ECHO_N@ +ECHO_T = @ECHO_T@ +EGREP = @EGREP@ +EXEEXT = @EXEEXT@ +EXTRA_VERSION = @EXTRA_VERSION@ +FGREP = @FGREP@ +GETTEXT_PACKAGE = @GETTEXT_PACKAGE@ +GLIB_CFLAGS = @GLIB_CFLAGS@ +GLIB_COMPILE_RESOURCES = @GLIB_COMPILE_RESOURCES@ +GLIB_GENMARSHAL = @GLIB_GENMARSHAL@ +GLIB_LIBS = @GLIB_LIBS@ +GLIB_MKENUMS = @GLIB_MKENUMS@ +GMOFILES = @GMOFILES@ +GMSGFMT = @GMSGFMT@ +GOBJECT_QUERY = @GOBJECT_QUERY@ +GPGME_CFLAGS = @GPGME_CFLAGS@ +GPGME_CONFIG = @GPGME_CONFIG@ +GPGME_LIBS = @GPGME_LIBS@ +GREP = @GREP@ +GTK_CFLAGS = @GTK_CFLAGS@ +GTK_LIBS = @GTK_LIBS@ +INSTALL = @INSTALL@ +INSTALL_DATA = @INSTALL_DATA@ +INSTALL_PROGRAM = @INSTALL_PROGRAM@ +INSTALL_SCRIPT = @INSTALL_SCRIPT@ +INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@ +INSTOBJEXT = @INSTOBJEXT@ +INTLLIBS = @INTLLIBS@ +LD = @LD@ +LDAP_LIBS = @LDAP_LIBS@ +LDFLAGS = @LDFLAGS@ +LEX = @LEX@ +LEXLIB = @LEXLIB@ +LEX_OUTPUT_ROOT = @LEX_OUTPUT_ROOT@ +LIBICONV = @LIBICONV@ +LIBOBJS = @LIBOBJS@ +LIBS = @LIBS@ +LIBSYLPH_CFLAGS = @LIBSYLPH_CFLAGS@ +LIBSYLPH_LIBS = @LIBSYLPH_LIBS@ +LIBTOOL = @LIBTOOL@ +LIPO = @LIPO@ +LN_S = @LN_S@ +LTLIBICONV = @LTLIBICONV@ +LTLIBOBJS = @LTLIBOBJS@ +LT_AGE = @LT_AGE@ +LT_CURRENT = @LT_CURRENT@ +LT_RELEASE = @LT_RELEASE@ +LT_REVISION = @LT_REVISION@ +MAINT = @MAINT@ +MAJOR_VERSION = @MAJOR_VERSION@ +MAKEINFO = @MAKEINFO@ +MANIFEST_TOOL = @MANIFEST_TOOL@ +MICRO_VERSION = @MICRO_VERSION@ +MINOR_VERSION = @MINOR_VERSION@ +MKDIR_P = @MKDIR_P@ +MKINSTALLDIRS = @MKINSTALLDIRS@ +MSGFMT = @MSGFMT@ +MSGFMT_OPTS = @MSGFMT_OPTS@ +NM = @NM@ +NMEDIT = @NMEDIT@ +OBJDUMP = @OBJDUMP@ +OBJEXT = @OBJEXT@ +OPENSSL_CFLAGS = @OPENSSL_CFLAGS@ +OPENSSL_LIBS = @OPENSSL_LIBS@ +OTOOL = @OTOOL@ +OTOOL64 = @OTOOL64@ +PACKAGE = @PACKAGE@ +PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@ +PACKAGE_NAME = @PACKAGE_NAME@ +PACKAGE_STRING = @PACKAGE_STRING@ +PACKAGE_TARNAME = @PACKAGE_TARNAME@ +PACKAGE_URL = @PACKAGE_URL@ +PACKAGE_VERSION = @PACKAGE_VERSION@ +PATH_SEPARATOR = @PATH_SEPARATOR@ +PKG_CONFIG = @PKG_CONFIG@ +PKG_CONFIG_LIBDIR = @PKG_CONFIG_LIBDIR@ +PKG_CONFIG_PATH = @PKG_CONFIG_PATH@ +POFILES = @POFILES@ +POSUB = @POSUB@ +PO_IN_DATADIR_FALSE = @PO_IN_DATADIR_FALSE@ +PO_IN_DATADIR_TRUE = @PO_IN_DATADIR_TRUE@ +RANLIB = @RANLIB@ +SED = @SED@ +SET_MAKE = @SET_MAKE@ +SHELL = @SHELL@ +STRIP = @STRIP@ +SYLPHEED_LIBS = @SYLPHEED_LIBS@ +USE_NLS = @USE_NLS@ +VERSION = @VERSION@ +WINDRES = @WINDRES@ +XGETTEXT = @XGETTEXT@ +YACC = @YACC@ +YFLAGS = @YFLAGS@ +abs_builddir = @abs_builddir@ +abs_srcdir = @abs_srcdir@ +abs_top_builddir = @abs_top_builddir@ +abs_top_srcdir = @abs_top_srcdir@ +ac_ct_AR = @ac_ct_AR@ +ac_ct_CC = @ac_ct_CC@ +ac_ct_DUMPBIN = @ac_ct_DUMPBIN@ +am__include = @am__include@ +am__leading_dot = @am__leading_dot@ +am__quote = @am__quote@ +am__tar = @am__tar@ +am__untar = @am__untar@ +bindir = @bindir@ +build = @build@ +build_alias = @build_alias@ +build_cpu = @build_cpu@ +build_os = @build_os@ +build_vendor = @build_vendor@ +builddir = @builddir@ +datadir = @datadir@ +datarootdir = @datarootdir@ +docdir = @docdir@ +dvidir = @dvidir@ +exec_prefix = @exec_prefix@ +faqdir = @faqdir@ +host = @host@ +host_alias = @host_alias@ +host_cpu = @host_cpu@ +host_os = @host_os@ +host_vendor = @host_vendor@ +htmldir = @htmldir@ +includedir = @includedir@ +infodir = @infodir@ +install_sh = @install_sh@ +libdir = @libdir@ +libexecdir = @libexecdir@ +localedir = @localedir@ +localstatedir = @localstatedir@ +mandir = @mandir@ +manualdir = @manualdir@ +mkdir_p = @mkdir_p@ +oldincludedir = @oldincludedir@ +pdfdir = @pdfdir@ +plugindir = @plugindir@ +prefix = @prefix@ +program_transform_name = @program_transform_name@ +psdir = @psdir@ +sbindir = @sbindir@ +sharedstatedir = @sharedstatedir@ +srcdir = @srcdir@ +sysconfdir = @sysconfdir@ +target = @target@ +target_alias = @target_alias@ +target_cpu = @target_cpu@ +target_os = @target_os@ +target_vendor = @target_vendor@ +themedir = @themedir@ +top_build_prefix = @top_build_prefix@ +top_builddir = @top_builddir@ +top_srcdir = @top_srcdir@ +faqdatadir = $(faqdir)/es +faqdata_DATA = \ + sylpheed-faq-1.html \ + sylpheed-faq-2.html \ + sylpheed-faq-3.html \ + sylpheed-faq.html + + +# generated by `ls -1 | sed -e 's/\(.*\)/ \1 \'` +EXTRA_DIST = $(faqdata_DATA) +all: all-am + +.SUFFIXES: +$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.am $(am__configure_deps) + @for dep in $?; do \ + case '$(am__configure_deps)' in \ + *$$dep*) \ + ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \ + && { if test -f $@; then exit 0; else break; fi; }; \ + exit 1;; \ + esac; \ + done; \ + echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign faq/es/Makefile'; \ + $(am__cd) $(top_srcdir) && \ + $(AUTOMAKE) --foreign faq/es/Makefile +.PRECIOUS: Makefile +Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status + @case '$?' in \ + *config.status*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \ + *) \ + echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \ + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \ + esac; + +$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh + +$(top_srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(am__configure_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ $(am__aclocal_m4_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(am__aclocal_m4_deps): + +mostlyclean-libtool: + -rm -f *.lo + +clean-libtool: + -rm -rf .libs _libs +install-faqdataDATA: $(faqdata_DATA) + @$(NORMAL_INSTALL) + @list='$(faqdata_DATA)'; test -n "$(faqdatadir)" || list=; \ + if test -n "$$list"; then \ + echo " $(MKDIR_P) '$(DESTDIR)$(faqdatadir)'"; \ + $(MKDIR_P) "$(DESTDIR)$(faqdatadir)" || exit 1; \ + fi; \ + for p in $$list; do \ + if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \ + echo "$$d$$p"; \ + done | $(am__base_list) | \ + while read files; do \ + echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(faqdatadir)'"; \ + $(INSTALL_DATA) $$files "$(DESTDIR)$(faqdatadir)" || exit $$?; \ + done + +uninstall-faqdataDATA: + @$(NORMAL_UNINSTALL) + @list='$(faqdata_DATA)'; test -n "$(faqdatadir)" || list=; \ + files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \ + dir='$(DESTDIR)$(faqdatadir)'; $(am__uninstall_files_from_dir) +tags TAGS: + +ctags CTAGS: + +cscope cscopelist: + + +distdir: $(DISTFILES) + @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + list='$(DISTFILES)'; \ + dist_files=`for file in $$list; do echo $$file; done | \ + sed -e "s|^$$srcdirstrip/||;t" \ + -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \ + case $$dist_files in \ + */*) $(MKDIR_P) `echo "$$dist_files" | \ + sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \ + sort -u` ;; \ + esac; \ + for file in $$dist_files; do \ + if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ + if test -d $$d/$$file; then \ + dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d "$(distdir)/$$file"; then \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ + if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ + cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ + cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \ + else \ + test -f "$(distdir)/$$file" \ + || cp -p $$d/$$file "$(distdir)/$$file" \ + || exit 1; \ + fi; \ + done +check-am: all-am +check: check-am +all-am: Makefile $(DATA) +installdirs: + for dir in "$(DESTDIR)$(faqdatadir)"; do \ + test -z "$$dir" || $(MKDIR_P) "$$dir"; \ + done +install: install-am +install-exec: install-exec-am +install-data: install-data-am +uninstall: uninstall-am + +install-am: all-am + @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am + +installcheck: installcheck-am +install-strip: + if test -z '$(STRIP)'; then \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + install; \ + else \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \ + fi +mostlyclean-generic: + +clean-generic: + +distclean-generic: + -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES) + +maintainer-clean-generic: + @echo "This command is intended for maintainers to use" + @echo "it deletes files that may require special tools to rebuild." +clean: clean-am + +clean-am: clean-generic clean-libtool mostlyclean-am + +distclean: distclean-am + -rm -f Makefile +distclean-am: clean-am distclean-generic + +dvi: dvi-am + +dvi-am: + +html: html-am + +html-am: + +info: info-am + +info-am: + +install-data-am: install-faqdataDATA + +install-dvi: install-dvi-am + +install-dvi-am: + +install-exec-am: + +install-html: install-html-am + +install-html-am: + +install-info: install-info-am + +install-info-am: + +install-man: + +install-pdf: install-pdf-am + +install-pdf-am: + +install-ps: install-ps-am + +install-ps-am: + +installcheck-am: + +maintainer-clean: maintainer-clean-am + -rm -f Makefile +maintainer-clean-am: distclean-am maintainer-clean-generic + +mostlyclean: mostlyclean-am + +mostlyclean-am: mostlyclean-generic mostlyclean-libtool + +pdf: pdf-am + +pdf-am: + +ps: ps-am + +ps-am: + +uninstall-am: uninstall-faqdataDATA + +.MAKE: install-am install-strip + +.PHONY: all all-am check check-am clean clean-generic clean-libtool \ + cscopelist-am ctags-am distclean distclean-generic \ + distclean-libtool distdir dvi dvi-am html html-am info info-am \ + install install-am install-data install-data-am install-dvi \ + install-dvi-am install-exec install-exec-am \ + install-faqdataDATA install-html install-html-am install-info \ + install-info-am install-man install-pdf install-pdf-am \ + install-ps install-ps-am install-strip installcheck \ + installcheck-am installdirs maintainer-clean \ + maintainer-clean-generic mostlyclean mostlyclean-generic \ + mostlyclean-libtool pdf pdf-am ps ps-am tags-am uninstall \ + uninstall-am uninstall-faqdataDATA + + +# Tell versions [3.59,3.63) of GNU make to not export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.NOEXPORT: diff --git a/faq/es/sylpheed-faq-1.html b/faq/es/sylpheed-faq-1.html new file mode 100644 index 0000000..e35255a --- /dev/null +++ b/faq/es/sylpheed-faq-1.html @@ -0,0 +1,241 @@ + + + + + Preguntas Más Frecuentes (FAQ) de Sylpheed: Información general + + + + + +Página siguiente +Página anterior +Índice general +
+

1. Información general

+ +

1.1 ¿Están disponibles los FAQs en otros idiomas? +

+ +

R.: Si, los siguientes enlaces corresponden a distintas traducciones +disponibles: +

+

También puedes encontrar la última versión en línea de este FAQ en +http://www.aic.uniovi.es/mones/sylpheed/sylpheed-faq-es/ (hay enlaces a diferentes formatos). +

1.2 ¿Qué es Sylpheed? +

+ +

R.: Sylpheed es un cliente de correo (y lector de noticias) +basado en GTK+, que corre bajo el X Window System, y +buscando: +

    +
  • Rápida respuesta
    • +
  • Interfaz sofisticado y agradable
    • +
  • Fácil configuración y manejo intuitivo
    • +
  • Múltiples características
    • +
+

1.3 ¿Dónde puedo obtener Sylpheed? +

+ +

R.: Se puede bajar de +http://sylpheed.good-day.net +Hay enlaces para descargar las fuentes completas y +también enlaces a sitios donde se pueden +descargar RPM's (para RedHat y Mandrake), paquetes +DEB para Debian, así como instalaciones para Solaris y +FreeBSD. +r +

1.4 ¿Quién ha realizado Sylpheed? +

+ +

R.: Hiroyuki Yamamoto <hiro-y@kcn.ne.jp> +

1.5 ¿Qué significa el nombre Sylpheed? +

+ +

R.: Significa de peso ligero, como el aire. Viene del nombre +de los espíritus del viento, las sílfides (Sylphs en inglés). +

1.6 ¿Cómo almacena Sylpheed los correos? +

+ +

R.: Los correos son almacenados en el formato MH, usado por +el propio MH y EMH. Los formatos maildir y mbox no +están (aún) soportados, aunque es posible +importar un fichero mbox en Sylpheed. +

1.7 ¿Por qué no funciona la recolección automática de correo? +

+ +

R.: La recolección automática funciona desde la versión 0.5.1. Si la +necesita o la quiere deberá actualizarse. +

1.8 ¿Tiene Sylpheed filtros para el correo? +

+ +

R.: Si. Los puedes encontar en la pestaña Configuración>Preferencias comunes>Filtrado +

NOTA: el filtrado aún no está implementado para cuentas IMAP +

1.9 ¿Puede Sylpheed manejar correo IMAP? +

+ +

R.: Si. Desde la versión 0.4.99 IMAP esta soportado. +

1.10 ¿Puede Sylpheed manejar buzones locales de UNIX? +

+ +

R.: Si. +

1.11 ¿Puede Sylpheed manejar IPv6? +

+ +

R.: Si, IPv6 está completamente soportado en Sylpheed. +

1.12 ¿Soporta Sylpheed encriptación como GPG? +

+ +

R.: Si. GPG está implementado y funciona correctamente. +Para activarlo en Sylpheed vea la pregunta 14 en la sección +de Instalación. +

1.13 ¿Cómo comprueba Sylpheed los tipos MIME? +

+ +

R.: Sylpheed usa la comprobación de tipos MIME equivalente a la realizada por Mutt. +

1.14 ¿Me permite Sylpheed escribir mensajes en HTML? +

+ +

R.: No. Se discutió ampliamente este tema y el resultado fue +que los mensajes HTML no son deseables. Si realmente necesita +enviar HTML siempre puede adjuntar una página web al +correo. Se han realizado varios parches para facilitar un mejor +manejo del HTML en Sylpheed. Los podrá encontrar en la +Página de Parches de Sylpheed (ver más adelante en este mismo documento). +

1.15 ¿Tiene Sylpheed autocompletado de nombres en los campos de dirección? +

+ +

R.: Si. Cuando busque un nombre que empieze por ``don'', teclee +``don'' (sin las comillas) y pulse el tabulador. Esto le +mostrará el nombre correcto si solamente existe un ``don'' +en su libro de direcciones, si no aparecerá una lista +desplegable que le permitirá seleccionar el nombre +deseado, p.ej. Donald Duck, Don Jonhson, pero también las +direcciones de correo que empiecen por ``don'' aparecerán en +la lista, como ``don.giovanni@maffia.org''. +

1.16 Bien, pero cuando pulso el tabulador aparece un mensaje de error. +

+ +

R.: Cuando quiera usar el autocompletado de nombres asegúrese +de que hay algún nombre en el libro de direcciones. Si no +hay nombres hasta Sylpheed tiene dificultades para completar algo. +

1.17 ¿Por qué es tan rápido Sylpheed? +

+ +

R.: ¡Es para lo que se ha diseñado! +

1.18 ¿Dónde puedo conseguir los parches actuales para Sylpheed? +

+ +

R.: En la Página de Parches de Sylpheed: +http://www.teledix.net/sylpheed/ +(Visite tambien la sección de instalación sobre como +instalar un parche) +

1.19 ¿Cómo puedo enviar parches, informar de errores, hablar con otros sobre Sylpheed? +

+ +

R.: Para hablar con otros debería unirse a la lista de +correo de Sylpheed en +http://sylpheed.good-day.net. Hay una +lista japonesa y otra en inglés, ¡elija la correcta! +Si tiene algún parche que quiera dar a conocer al +mundo póngase en contacto con el encargado de la página de +parches de Sylpheed en sylpheed@thewildbeast.co.uk. +

1.20 Cuando envio un correo la cabecera Content-Type dice que el +correo esta en US-ASCII, incluso si he especificado ISO-8859-1

+ +

R.: Si no se usan caracteres ISO-8859-1 (>= 0x80) en el cuerpo del +mensaje, Sylpheed automáticamente pondrá el valor +del conjunto de caracteres en la cabecera Content-Type como US-ASCII. +

1.21 ¿Por qué parece que el partido de líneas no funciona? +

+ +

R.: El partido de líneas es quizás algo peculiar. Se pueden teclear +las líneas tan largas como se deseen. Cuando se envía o se pone en cola +un correo con líneas largas, Sylpheed primero partirá las líneas +a la longitud que haya sido establecida, y luedo encolará el +mensaje. Esto es más conveniente de lo que se pueda pensar, ya +que una vez una línea es partida (se insertan saltos de línea +en el texto) y cuando añades algo a esa línea, la siguiente +se moverá a una nueva, dejando una o dos palabras de la anterior +``colgando'' solas. Por ejemplo: +

Esta es una línea larga + +

es partida. + +

Si ahora se añade una palabra en la primera línea: +

Esta es una línea muy larga + +

que + +

es partida. + +

Esto provocaría un monton de trabajo manual para reformatear +y dejar presentable el correo de nuevo. +

1.22 ¿Dónde puedo encontrar el último FAQ de Sylpheed? +

+ +

R.: Puedes encontrar el FAQ y el manual buscando en el proyecto sylpheeddoc en +http://sylpheeddoc.sf.net. También podrás encontrar enlaces a ambos documentos en otros idiomas, habitualmente con las últimas actualizaciones. +

1.23 ¿Se puede importar un mbox en las carpetas de correo MH de Sylpheed? +

+ +

R.: Si, simplemente selecciona o crea la carpeta donde quieras los +correos y selecciona ``Importar de fichero mbox`` en el menú +``Fichero``. +

1.24 ¿Se puede usar procmail para ordenar los correos con el manejo de correo MH? +

+ +

R.: Si. Asegúrate de añadir /. al final de las reglas para que procmail sepa que esta filtrando hacia una carpeta de correo estilo MH. Ejemplo: +

0: +

* ^Subject:.*sylpheed +

sylpheedmail/. +

Comprueba la página del manual de procmail para más detalles. +

1.25 ¿Hay cosas que debería tener en cuenta cuando actualize Sylpheed? +

+ +

R.: Si! Al actualizar a +

    +
  • 0.4.50: deberías reconfigurar las preferencias de los grupos de noticias.
    • +
  • 0.4.63: deberías establecer los colores para las URL en el menú de configuración.
    • +
  • 0.4.65: algunos elementos de menú han sido reubicados.
    • +
+

1.26 ¿Cómo puedo actualizar rápidamente las vistas en Sylpheed? +

+ +

R.: Simplemente pulse "Alt+U" o seleccione ``Actualizar`` del menú ``Resumen``. +

1.27 ¿Por qué no puedo usar gvim como editor externo? +

+ +

R.: Si desea utilizar gvim como editor externo es necesario +lanzarlo con la opción de no-fork -f, es decir, en el cuadro +de diálogo el comando deberá ser gvim -f %s. Si no se hace así +el editor realiza un fork, abriendo el fichero en el proceso hijo, y +cuando se sale del editor los cambios realizados se pierden, y no se +muestra nada en la ventana de composición. +(Cortesía de Ed Collins) +

+Página siguiente +Página anterior +Índice general + + diff --git a/faq/es/sylpheed-faq-2.html b/faq/es/sylpheed-faq-2.html new file mode 100644 index 0000000..f2e3a0b --- /dev/null +++ b/faq/es/sylpheed-faq-2.html @@ -0,0 +1,125 @@ + + + + + Preguntas Más Frecuentes (FAQ) de Sylpheed: Instalación y Configuración + + + + + +Página siguiente +Página anterior +Índice general +
+

2. Instalación y Configuración

+ +

2.1 ¿Qué es necesario para compilar Sylpheed? +

+ +

R.: Cualquier UNIX que siga el estandar POSIX o similar, +(por ejemplo: Linux, FreeBSD, Solaris), +GTK+ 1.2.6 o posterior y un compilador ANSI C reciente +(gcc 2.7.2.3 debería servir) +

+Nota: se sabe que Sun C no sirve para compilar Sylpheed. +

Opcionalmente: +

    +
  • Imlib o gdk-pixbuf (para el visor de imágenes interno)
    • +
  • libcompface (para X-Face)
    • +
  • libjconv (para I18N)
    • +
  • GPGME (para GnuPG)
    • +
  • el equivalente de GTK+-devel y Xfree86-devel si no ./configure fallará.
    • +
+

2.2 ¿Cómo configuro Sylpheed? +

+ +

R.: Cuando ejecute Sylpheed por primera vez le preguntará donde quiere almacenar +sus buzones de correo. El directorio por defecto es ~/Mail, pero puede cambiarlo +a cualquier otro que desee mientras sea un nombre de directorio válido. +

2.3 ¿Cómo configuro una cuenta? +

+ +

R.: Después de cargar Sylpheed la primera vez se puede añadir una cuenta de correo +pulsando en el menú de ``Configuración``, seleccionando la opción +``Crear nueva cuenta...`` +y rellenando los campos del cuadro de diálogo con los valores adecuados. +

2.4 ¿Cuántas cuentas puedo configurar en Sylpheed? +

+ +

R.: El número es ilimitado. El límite se alcanza cuando su ordenador deje de responder. +

2.5 ¿Por qué Sylpheed no borra mis correos cuando pulso ``Borrar``? ¿O cuando establezco +un filtro y Sylpheed no filtra? ¿O muevo correo a una carpeta diferente y no se mueve?

+ +

R.: Tienes que pulsar el botón ``Ejecutar``. Otra solución consiste en marcar la casilla +``Ejecutar comandos inmediatamente`` en las preferencias de configuración +(``Preferencias comunes > Interfaz``). +

2.6 ¿Puedo establecer direcciones o puertos especiales para mi servidor de correo/noticias? +

+ +

R.: Si, puede. En la configuración de cada cuenta se pueden especificar los puertos concretos +que desee utilizar. +

2.7 ¿Tiene Sylpheed opciones para separar en hilos los mensajes? +

+ +

R.: Si. Se puede activar o desactivar en el menú ``Resumen`` seleccionando +``Vista jerárquica`` o pulsando "Ctrl+T". +

2.8 ¿Puedo crear varios niveles de subcarpetas para almacenar el correo? +

+ +

R.: Si, no hay ningún problema. +

2.9 ¿Por qué no esta Sylpheed enviando mis correos? +

+ +

R.: Necesita crear al menos una cuenta para poder enviar correo. +

2.10 ¿Cómo aplico un parche después de haberlo descargado? +

+ +

R.: Copie el parche al directorio de Sylpheed. Aplíquelo con la orden: +

% patch -p0 < nombre-del-parche.patch +

O, si el parche esta comprimido con gzip: +

% gzip -dc nombre-del-parche.patch.gz | patch -p0 +

Después de esto deberá ejecutar ./autogen.sh y eliminar el fichero +./config.cache generado (a menos que quiera instalar el programa bajo +/usr/local). Ejecute ./configure con las opciones deseadas y +una vez finalizado, ejecute make. (Estas instrucciones son las que se +encuentran en la Página de Parches de Sylpheed). +

2.11 ¿Cómo puedo compilar el soporte para los dibujos compface? +

+ +

R.: Deberá tener instalado el paquete en el que esté incluido libcompface +(normalmente denominado faces), de manera que esté disponible para compilar con Sylpheed. +

2.12 ¿Cómo puedo crear mi propia imagen compface? +

+ +

R.: Dentro del paquete faces existe el programa xmb2icon (un guión de shell) +que convierte un fichero xbm de 48x48 pixels al formato adecuado para compface. Para conseguir una +imagen en formato xbm puede utilizar un programa gráfico como el Gimp. +Gracias a Jeff Daikiri está disponible un curso completo en línea sobre esto, visite +http://www.dairiki.org/xface/ para más detalles. +

2.13 ¿Cómo le puedo indicar a mi navegador, cliente de noticias u otro programa que +utilize Sylpheed como cliente de correo?

+ +

R.: En la sección de configuración del programa correspondiente escriba: + sylpheed --compose +

2.14 ¿Cómo puedo habilitar el soporte de GPG en Sylpheed? +

+ +

R.: Cuando compile Sylpheed asegúrese de añadir la opción --enable-gpgme al +comando ./configureCuando la compilación termine correctamente aparecerá en el diálogo de Preferencias comunes una sección de "Privacidad". +

2.15 Mutt no reconoce la estructura de carpetas MH de Sylpheed +

+ +

R.: Deberá hacer touch .xmhcache en todas y cada una de las cada carpetas MH, y Mutt funcionará correctamente. +

2.16 Sylpheed provoca una violación de segmento cuando veo un fichero GIF +

+ +

R.: Si sucede esto se puede solucionar fácilmente añadiendo lo siguiente al +fichero /etc/mime.types : +image/gif gif +

+Página siguiente +Página anterior +Índice general + + diff --git a/faq/es/sylpheed-faq-3.html b/faq/es/sylpheed-faq-3.html new file mode 100644 index 0000000..16cbe70 --- /dev/null +++ b/faq/es/sylpheed-faq-3.html @@ -0,0 +1,124 @@ + + + + + Preguntas Más Frecuentes (FAQ) de Sylpheed: Interface + + + + +Página siguiente +Página anterior +Índice general +
+

3. Interface

+ +

3.1 ¿Cómo puedo hacer que Sylpheed muestre mi idioma? +

+ +

R.: Deberá establecer el valor de algunas variables de entorno como +LANG, LC_CTYPE o LC_MESSAGES al idioma deseado. +Normalmente LANG (o LC_ALL) son suficientes. +

3.2 No me gusta la fuente por defecto, ¿puedo cambiarla? +

+ +

R.: Si. En el menú ``Configuración>Preferencias comunes`` bajo +la pestaña ``Visualización``. +

3.3 ¡Hay demasiadas columnas el la lista de mensajes! +

+ +

R.: En el menú ``Configuración>Preferencias comunes`` bajo +la pestaña ``Visualización`` puede pulsar el botón ``Cabeceras en +la vista resumen``. Aparecerá una ventana con todas las opciones +que puede mostrar o quitar de la lista de mensajes. +

3.4 ¿Puedo utilizar un editor diferente para escribir mis correos? +

+ +

R.: Puede. En el menú ``Configuración>Preferencias comunes`` bajo +la pestaña ``Otras`` se puede especificar el editor deseado. Recuerde que +si quiere usar un editor en linea de comandos, como vi o emacs, +deberá escribir el nombre del shell (term, xterm, rxvt) +con el parámetro -e delante del editor. Por ejemplo: rxvt -e vi %s +

3.5 ¿Cómo puedo cambiar el tamaño de la fuente en el interfaz de Sylpheed? +

+ +

R.: Puede establecer la fuente GTK+ en ~/.gtkrc o ~/.gtkrc.mine +(que es incluido por el primero). Por ejemplo: +

style "default" + +

{ +

font = "-adobe-helvetica-medium-r-normal--12-*-*-*-*-*-iso8859-1" + +

} + +

widget_class "*" style "default" + +

3.6 Sylpheed guarda mi correo saliente (en Salida). ¿Puedo evitar que haga esto? +

+ +

R.: En ``Configuración>Preferencias comunes`` hay una casilla denominada +``Guardar mensajes salientes en Salida``. Déjela en blanco y estará solucionado. +

3.7 ¿Cómo puedo cambiar las asociaciones de teclas (teclas calientes) en Sylpheed? +

+ +

R.: Esto es muy sencillo. Supongamos que quiere asignar una combinación +de teclas a una función, por ejemplo enviar todo el correo cuando se pulse ``Ctrl+Y''. +Pulse en el menú ``Mensajes`` y mueva el ratón sobre ``Enviar todo``. +Ahora pulse ``Ctrl+Y''. Inmediatamente verá que el texto del menú se actualiza para +reflejar la nueva combinación. Hay que hacer notar que la función a la que estaba asignada +previamente ``Ctrl+Y'' ya no tendrá ninguna combinación de teclas asociada. En caso de +que quiera eliminar la combinación asociada a alguna función el procedimiento es el mismo, +pero pulsando la tecla ``Supr'' sobre el elemento del menú. +

3.8 ¿Puedo cerrar las ventanas sin utilizar el ratón? +

+ +

R.: ¡Por supuesto! No todas las ventanas, pero pulsando la tecla de escape ("Esc") +puede cerrar la agenda, la ventana en la que se ve la fuente del correo +(``Mensaje>Ver fuente``), +la ventana de las cabeceras y varias más. Inténtelo y las encontrará todas. +

3.9 ¿Puedo cambiar la manera en la que aparece mostrada la fecha en la lista resumen de mensajes? +

+ +

R.: Desde la versión 0.4.65 se puede. Las opciones son las siguientes: +

+

    +
  • %y año en número
    • +
  • %m mes en número
    • +
  • %d día en número
    • +
  • %c fecha/hora local
    • +
  • %A día de la semana completo
    • +
  • %a nombre del día corto
    • +
  • %B día del mes completo
    • +
  • %b nombre del mes corto
    • +
  • %H hora (0-23)
    • +
  • %I hora (0-12)
    • +
+

Para más información vaya al menú de ``Configuración``, seleccione +``Preferencias comunes``, ``Visualizar``, +y mueva el puntero del ratón sobre el recuadro de ``Formato de fecha``. +

3.10 ¿Por qué no puedo ver las imágenes compface? +

+ +

R.: Necesita habilitar la visualización del panel de cabeceras en +las ``Preferencias generales``. +

3.11 Todavía no puedo ver las imágenes. ¿Por qué? +

+ +

R.: Quizás no haya compilado el soporte para Compface. Vea la pregunta +relativa a faces en la sección de Instalación/Configuración. +

3.12 ¿Por qué el lanzador de URLs no lanza mi navegador web? +

+ +

R.: Es necesario que haga doble-click con el ratón sobre la URL. +

3.13 Los ficheros adjuntos con espacios en el nombre no se abren! +

+ +

R.: Cuándo intente lanzar una aplicación auxiliar, como un visor de imágenes, con un adjunto que tenga +espacios en el nombre ponga comillas simples alrededor del parámetro %s. +Por ejemplo: gedit '%s' +

+Página siguiente +Página anterior +Índice general + + diff --git a/faq/es/sylpheed-faq.html b/faq/es/sylpheed-faq.html new file mode 100644 index 0000000..4c67206 --- /dev/null +++ b/faq/es/sylpheed-faq.html @@ -0,0 +1,98 @@ + + + + + Preguntas Más Frecuentes (FAQ) de Sylpheed + + + + + +Página siguiente +Página anterior +Índice general +
+

Preguntas Más Frecuentes (FAQ) de Sylpheed

+ +

Ricardo Mones Lastra <mones@aic.uniovi.es>

+

+ Preguntas más frecuentes (FAQ) de Sylpheed para la versión 0.7.4 - basado en el documento original en inglés de Paul Kater (paul@nlpagan.net) + y Jens Oberender (j.obi@troja.net) +
+

+

1. Información general

+ + +

+

2. Instalación y Configuración

+ + +

+

3. Interface

+ + +
+Página siguiente +Página anterior +Índice general + + diff --git a/faq/fr/Makefile.am b/faq/fr/Makefile.am new file mode 100644 index 0000000..2b26420 --- /dev/null +++ b/faq/fr/Makefile.am @@ -0,0 +1,11 @@ +faqdatadir = $(faqdir)/fr + +faqdata_DATA = \ + sylpheed-faq-1.html \ + sylpheed-faq-2.html \ + sylpheed-faq-3.html \ + sylpheed-faq.html + +# generated by `ls -1 | sed -e 's/\(.*\)/ \1 \'` + +EXTRA_DIST = $(faqdata_DATA) diff --git a/faq/fr/Makefile.in b/faq/fr/Makefile.in new file mode 100644 index 0000000..1f13b12 --- /dev/null +++ b/faq/fr/Makefile.in @@ -0,0 +1,552 @@ +# Makefile.in generated by automake 1.14.1 from Makefile.am. +# @configure_input@ + +# Copyright (C) 1994-2013 Free Software Foundation, Inc. + +# This Makefile.in is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY, to the extent permitted by law; without +# even the implied warranty of MERCHANTABILITY or FITNESS FOR A +# PARTICULAR PURPOSE. + +@SET_MAKE@ + +VPATH = @srcdir@ +am__is_gnu_make = test -n '$(MAKEFILE_LIST)' && test -n '$(MAKELEVEL)' +am__make_running_with_option = \ + case $${target_option-} in \ + ?) ;; \ + *) echo "am__make_running_with_option: internal error: invalid" \ + "target option '$${target_option-}' specified" >&2; \ + exit 1;; \ + esac; \ + has_opt=no; \ + sane_makeflags=$$MAKEFLAGS; \ + if $(am__is_gnu_make); then \ + sane_makeflags=$$MFLAGS; \ + else \ + case $$MAKEFLAGS in \ + *\\[\ \ ]*) \ + bs=\\; \ + sane_makeflags=`printf '%s\n' "$$MAKEFLAGS" \ + | sed "s/$$bs$$bs[$$bs $$bs ]*//g"`;; \ + esac; \ + fi; \ + skip_next=no; \ + strip_trailopt () \ + { \ + flg=`printf '%s\n' "$$flg" | sed "s/$$1.*$$//"`; \ + }; \ + for flg in $$sane_makeflags; do \ + test $$skip_next = yes && { skip_next=no; continue; }; \ + case $$flg in \ + *=*|--*) continue;; \ + -*I) strip_trailopt 'I'; skip_next=yes;; \ + -*I?*) strip_trailopt 'I';; \ + -*O) strip_trailopt 'O'; skip_next=yes;; \ + -*O?*) strip_trailopt 'O';; \ + -*l) strip_trailopt 'l'; skip_next=yes;; \ + -*l?*) strip_trailopt 'l';; \ + -[dEDm]) skip_next=yes;; \ + -[JT]) skip_next=yes;; \ + esac; \ + case $$flg in \ + *$$target_option*) has_opt=yes; break;; \ + esac; \ + done; \ + test $$has_opt = yes +am__make_dryrun = (target_option=n; $(am__make_running_with_option)) +am__make_keepgoing = (target_option=k; $(am__make_running_with_option)) +pkgdatadir = $(datadir)/@PACKAGE@ +pkgincludedir = $(includedir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkglibexecdir = $(libexecdir)/@PACKAGE@ +am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd +install_sh_DATA = $(install_sh) -c -m 644 +install_sh_PROGRAM = $(install_sh) -c +install_sh_SCRIPT = $(install_sh) -c +INSTALL_HEADER = $(INSTALL_DATA) +transform = $(program_transform_name) +NORMAL_INSTALL = : +PRE_INSTALL = : +POST_INSTALL = : +NORMAL_UNINSTALL = : +PRE_UNINSTALL = : +POST_UNINSTALL = : +build_triplet = @build@ +host_triplet = @host@ +target_triplet = @target@ +subdir = faq/fr +DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/Makefile.am \ + $(top_srcdir)/mkinstalldirs +ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 +am__aclocal_m4_deps = $(top_srcdir)/ac/aclocal-include.m4 \ + $(top_srcdir)/ac/gnupg-check-typedef.m4 \ + $(top_srcdir)/configure.ac +am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ + $(ACLOCAL_M4) +mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs +CONFIG_HEADER = $(top_builddir)/config.h +CONFIG_CLEAN_FILES = +CONFIG_CLEAN_VPATH_FILES = +AM_V_P = $(am__v_P_@AM_V@) +am__v_P_ = $(am__v_P_@AM_DEFAULT_V@) +am__v_P_0 = false +am__v_P_1 = : +AM_V_GEN = $(am__v_GEN_@AM_V@) +am__v_GEN_ = $(am__v_GEN_@AM_DEFAULT_V@) +am__v_GEN_0 = @echo " GEN " $@; +am__v_GEN_1 = +AM_V_at = $(am__v_at_@AM_V@) +am__v_at_ = $(am__v_at_@AM_DEFAULT_V@) +am__v_at_0 = @ +am__v_at_1 = +SOURCES = +DIST_SOURCES = +am__can_run_installinfo = \ + case $$AM_UPDATE_INFO_DIR in \ + n|no|NO) false;; \ + *) (install-info --version) >/dev/null 2>&1;; \ + esac +am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`; +am__vpath_adj = case $$p in \ + $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \ + *) f=$$p;; \ + esac; +am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`; +am__install_max = 40 +am__nobase_strip_setup = \ + srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'` +am__nobase_strip = \ + for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||" +am__nobase_list = $(am__nobase_strip_setup); \ + for p in $$list; do echo "$$p $$p"; done | \ + sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \ + $(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \ + if (++n[$$2] == $(am__install_max)) \ + { print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \ + END { for (dir in files) print dir, files[dir] }' +am__base_list = \ + sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \ + sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g' +am__uninstall_files_from_dir = { \ + test -z "$$files" \ + || { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \ + || { echo " ( cd '$$dir' && rm -f" $$files ")"; \ + $(am__cd) "$$dir" && rm -f $$files; }; \ + } +am__installdirs = "$(DESTDIR)$(faqdatadir)" +DATA = $(faqdata_DATA) +am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) $(LISP) +DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) +ACLOCAL = @ACLOCAL@ +ALLOCA = @ALLOCA@ +AMTAR = @AMTAR@ +AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@ +AR = @AR@ +AUTOCONF = @AUTOCONF@ +AUTOHEADER = @AUTOHEADER@ +AUTOMAKE = @AUTOMAKE@ +AWK = @AWK@ +BUILD_REVISION = @BUILD_REVISION@ +CATALOGS = @CATALOGS@ +CATOBJEXT = @CATOBJEXT@ +CC = @CC@ +CCDEPMODE = @CCDEPMODE@ +CFLAGS = @CFLAGS@ +CPP = @CPP@ +CPPFLAGS = @CPPFLAGS@ +CYGPATH_W = @CYGPATH_W@ +DATADIRNAME = @DATADIRNAME@ +DEFS = @DEFS@ +DEPDIR = @DEPDIR@ +DEVEL_VERSION = @DEVEL_VERSION@ +DLLTOOL = @DLLTOOL@ +DSYMUTIL = @DSYMUTIL@ +DUMPBIN = @DUMPBIN@ +ECHO_C = @ECHO_C@ +ECHO_N = @ECHO_N@ +ECHO_T = @ECHO_T@ +EGREP = @EGREP@ +EXEEXT = @EXEEXT@ +EXTRA_VERSION = @EXTRA_VERSION@ +FGREP = @FGREP@ +GETTEXT_PACKAGE = @GETTEXT_PACKAGE@ +GLIB_CFLAGS = @GLIB_CFLAGS@ +GLIB_COMPILE_RESOURCES = @GLIB_COMPILE_RESOURCES@ +GLIB_GENMARSHAL = @GLIB_GENMARSHAL@ +GLIB_LIBS = @GLIB_LIBS@ +GLIB_MKENUMS = @GLIB_MKENUMS@ +GMOFILES = @GMOFILES@ +GMSGFMT = @GMSGFMT@ +GOBJECT_QUERY = @GOBJECT_QUERY@ +GPGME_CFLAGS = @GPGME_CFLAGS@ +GPGME_CONFIG = @GPGME_CONFIG@ +GPGME_LIBS = @GPGME_LIBS@ +GREP = @GREP@ +GTK_CFLAGS = @GTK_CFLAGS@ +GTK_LIBS = @GTK_LIBS@ +INSTALL = @INSTALL@ +INSTALL_DATA = @INSTALL_DATA@ +INSTALL_PROGRAM = @INSTALL_PROGRAM@ +INSTALL_SCRIPT = @INSTALL_SCRIPT@ +INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@ +INSTOBJEXT = @INSTOBJEXT@ +INTLLIBS = @INTLLIBS@ +LD = @LD@ +LDAP_LIBS = @LDAP_LIBS@ +LDFLAGS = @LDFLAGS@ +LEX = @LEX@ +LEXLIB = @LEXLIB@ +LEX_OUTPUT_ROOT = @LEX_OUTPUT_ROOT@ +LIBICONV = @LIBICONV@ +LIBOBJS = @LIBOBJS@ +LIBS = @LIBS@ +LIBSYLPH_CFLAGS = @LIBSYLPH_CFLAGS@ +LIBSYLPH_LIBS = @LIBSYLPH_LIBS@ +LIBTOOL = @LIBTOOL@ +LIPO = @LIPO@ +LN_S = @LN_S@ +LTLIBICONV = @LTLIBICONV@ +LTLIBOBJS = @LTLIBOBJS@ +LT_AGE = @LT_AGE@ +LT_CURRENT = @LT_CURRENT@ +LT_RELEASE = @LT_RELEASE@ +LT_REVISION = @LT_REVISION@ +MAINT = @MAINT@ +MAJOR_VERSION = @MAJOR_VERSION@ +MAKEINFO = @MAKEINFO@ +MANIFEST_TOOL = @MANIFEST_TOOL@ +MICRO_VERSION = @MICRO_VERSION@ +MINOR_VERSION = @MINOR_VERSION@ +MKDIR_P = @MKDIR_P@ +MKINSTALLDIRS = @MKINSTALLDIRS@ +MSGFMT = @MSGFMT@ +MSGFMT_OPTS = @MSGFMT_OPTS@ +NM = @NM@ +NMEDIT = @NMEDIT@ +OBJDUMP = @OBJDUMP@ +OBJEXT = @OBJEXT@ +OPENSSL_CFLAGS = @OPENSSL_CFLAGS@ +OPENSSL_LIBS = @OPENSSL_LIBS@ +OTOOL = @OTOOL@ +OTOOL64 = @OTOOL64@ +PACKAGE = @PACKAGE@ +PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@ +PACKAGE_NAME = @PACKAGE_NAME@ +PACKAGE_STRING = @PACKAGE_STRING@ +PACKAGE_TARNAME = @PACKAGE_TARNAME@ +PACKAGE_URL = @PACKAGE_URL@ +PACKAGE_VERSION = @PACKAGE_VERSION@ +PATH_SEPARATOR = @PATH_SEPARATOR@ +PKG_CONFIG = @PKG_CONFIG@ +PKG_CONFIG_LIBDIR = @PKG_CONFIG_LIBDIR@ +PKG_CONFIG_PATH = @PKG_CONFIG_PATH@ +POFILES = @POFILES@ +POSUB = @POSUB@ +PO_IN_DATADIR_FALSE = @PO_IN_DATADIR_FALSE@ +PO_IN_DATADIR_TRUE = @PO_IN_DATADIR_TRUE@ +RANLIB = @RANLIB@ +SED = @SED@ +SET_MAKE = @SET_MAKE@ +SHELL = @SHELL@ +STRIP = @STRIP@ +SYLPHEED_LIBS = @SYLPHEED_LIBS@ +USE_NLS = @USE_NLS@ +VERSION = @VERSION@ +WINDRES = @WINDRES@ +XGETTEXT = @XGETTEXT@ +YACC = @YACC@ +YFLAGS = @YFLAGS@ +abs_builddir = @abs_builddir@ +abs_srcdir = @abs_srcdir@ +abs_top_builddir = @abs_top_builddir@ +abs_top_srcdir = @abs_top_srcdir@ +ac_ct_AR = @ac_ct_AR@ +ac_ct_CC = @ac_ct_CC@ +ac_ct_DUMPBIN = @ac_ct_DUMPBIN@ +am__include = @am__include@ +am__leading_dot = @am__leading_dot@ +am__quote = @am__quote@ +am__tar = @am__tar@ +am__untar = @am__untar@ +bindir = @bindir@ +build = @build@ +build_alias = @build_alias@ +build_cpu = @build_cpu@ +build_os = @build_os@ +build_vendor = @build_vendor@ +builddir = @builddir@ +datadir = @datadir@ +datarootdir = @datarootdir@ +docdir = @docdir@ +dvidir = @dvidir@ +exec_prefix = @exec_prefix@ +faqdir = @faqdir@ +host = @host@ +host_alias = @host_alias@ +host_cpu = @host_cpu@ +host_os = @host_os@ +host_vendor = @host_vendor@ +htmldir = @htmldir@ +includedir = @includedir@ +infodir = @infodir@ +install_sh = @install_sh@ +libdir = @libdir@ +libexecdir = @libexecdir@ +localedir = @localedir@ +localstatedir = @localstatedir@ +mandir = @mandir@ +manualdir = @manualdir@ +mkdir_p = @mkdir_p@ +oldincludedir = @oldincludedir@ +pdfdir = @pdfdir@ +plugindir = @plugindir@ +prefix = @prefix@ +program_transform_name = @program_transform_name@ +psdir = @psdir@ +sbindir = @sbindir@ +sharedstatedir = @sharedstatedir@ +srcdir = @srcdir@ +sysconfdir = @sysconfdir@ +target = @target@ +target_alias = @target_alias@ +target_cpu = @target_cpu@ +target_os = @target_os@ +target_vendor = @target_vendor@ +themedir = @themedir@ +top_build_prefix = @top_build_prefix@ +top_builddir = @top_builddir@ +top_srcdir = @top_srcdir@ +faqdatadir = $(faqdir)/fr +faqdata_DATA = \ + sylpheed-faq-1.html \ + sylpheed-faq-2.html \ + sylpheed-faq-3.html \ + sylpheed-faq.html + + +# generated by `ls -1 | sed -e 's/\(.*\)/ \1 \'` +EXTRA_DIST = $(faqdata_DATA) +all: all-am + +.SUFFIXES: +$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.am $(am__configure_deps) + @for dep in $?; do \ + case '$(am__configure_deps)' in \ + *$$dep*) \ + ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \ + && { if test -f $@; then exit 0; else break; fi; }; \ + exit 1;; \ + esac; \ + done; \ + echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign faq/fr/Makefile'; \ + $(am__cd) $(top_srcdir) && \ + $(AUTOMAKE) --foreign faq/fr/Makefile +.PRECIOUS: Makefile +Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status + @case '$?' in \ + *config.status*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \ + *) \ + echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \ + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \ + esac; + +$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh + +$(top_srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(am__configure_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ $(am__aclocal_m4_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(am__aclocal_m4_deps): + +mostlyclean-libtool: + -rm -f *.lo + +clean-libtool: + -rm -rf .libs _libs +install-faqdataDATA: $(faqdata_DATA) + @$(NORMAL_INSTALL) + @list='$(faqdata_DATA)'; test -n "$(faqdatadir)" || list=; \ + if test -n "$$list"; then \ + echo " $(MKDIR_P) '$(DESTDIR)$(faqdatadir)'"; \ + $(MKDIR_P) "$(DESTDIR)$(faqdatadir)" || exit 1; \ + fi; \ + for p in $$list; do \ + if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \ + echo "$$d$$p"; \ + done | $(am__base_list) | \ + while read files; do \ + echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(faqdatadir)'"; \ + $(INSTALL_DATA) $$files "$(DESTDIR)$(faqdatadir)" || exit $$?; \ + done + +uninstall-faqdataDATA: + @$(NORMAL_UNINSTALL) + @list='$(faqdata_DATA)'; test -n "$(faqdatadir)" || list=; \ + files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \ + dir='$(DESTDIR)$(faqdatadir)'; $(am__uninstall_files_from_dir) +tags TAGS: + +ctags CTAGS: + +cscope cscopelist: + + +distdir: $(DISTFILES) + @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + list='$(DISTFILES)'; \ + dist_files=`for file in $$list; do echo $$file; done | \ + sed -e "s|^$$srcdirstrip/||;t" \ + -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \ + case $$dist_files in \ + */*) $(MKDIR_P) `echo "$$dist_files" | \ + sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \ + sort -u` ;; \ + esac; \ + for file in $$dist_files; do \ + if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ + if test -d $$d/$$file; then \ + dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d "$(distdir)/$$file"; then \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ + if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ + cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ + cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \ + else \ + test -f "$(distdir)/$$file" \ + || cp -p $$d/$$file "$(distdir)/$$file" \ + || exit 1; \ + fi; \ + done +check-am: all-am +check: check-am +all-am: Makefile $(DATA) +installdirs: + for dir in "$(DESTDIR)$(faqdatadir)"; do \ + test -z "$$dir" || $(MKDIR_P) "$$dir"; \ + done +install: install-am +install-exec: install-exec-am +install-data: install-data-am +uninstall: uninstall-am + +install-am: all-am + @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am + +installcheck: installcheck-am +install-strip: + if test -z '$(STRIP)'; then \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + install; \ + else \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \ + fi +mostlyclean-generic: + +clean-generic: + +distclean-generic: + -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES) + +maintainer-clean-generic: + @echo "This command is intended for maintainers to use" + @echo "it deletes files that may require special tools to rebuild." +clean: clean-am + +clean-am: clean-generic clean-libtool mostlyclean-am + +distclean: distclean-am + -rm -f Makefile +distclean-am: clean-am distclean-generic + +dvi: dvi-am + +dvi-am: + +html: html-am + +html-am: + +info: info-am + +info-am: + +install-data-am: install-faqdataDATA + +install-dvi: install-dvi-am + +install-dvi-am: + +install-exec-am: + +install-html: install-html-am + +install-html-am: + +install-info: install-info-am + +install-info-am: + +install-man: + +install-pdf: install-pdf-am + +install-pdf-am: + +install-ps: install-ps-am + +install-ps-am: + +installcheck-am: + +maintainer-clean: maintainer-clean-am + -rm -f Makefile +maintainer-clean-am: distclean-am maintainer-clean-generic + +mostlyclean: mostlyclean-am + +mostlyclean-am: mostlyclean-generic mostlyclean-libtool + +pdf: pdf-am + +pdf-am: + +ps: ps-am + +ps-am: + +uninstall-am: uninstall-faqdataDATA + +.MAKE: install-am install-strip + +.PHONY: all all-am check check-am clean clean-generic clean-libtool \ + cscopelist-am ctags-am distclean distclean-generic \ + distclean-libtool distdir dvi dvi-am html html-am info info-am \ + install install-am install-data install-data-am install-dvi \ + install-dvi-am install-exec install-exec-am \ + install-faqdataDATA install-html install-html-am install-info \ + install-info-am install-man install-pdf install-pdf-am \ + install-ps install-ps-am install-strip installcheck \ + installcheck-am installdirs maintainer-clean \ + maintainer-clean-generic mostlyclean mostlyclean-generic \ + mostlyclean-libtool pdf pdf-am ps ps-am tags-am uninstall \ + uninstall-am uninstall-faqdataDATA + + +# Tell versions [3.59,3.63) of GNU make to not export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.NOEXPORT: diff --git a/faq/fr/sylpheed-faq-1.html b/faq/fr/sylpheed-faq-1.html new file mode 100644 index 0000000..c820141 --- /dev/null +++ b/faq/fr/sylpheed-faq-1.html @@ -0,0 +1,269 @@ + + + + + FAQ Sylpheed: FAQ Sylpheed - Informations générales + + + + + +Page suivante +Page précédente +Table des matières +
+

1. FAQ Sylpheed - Informations générales

+ +

1.1 Q01 Existent-ils des FAQ dans d'autres langues ? +

+ +

A. Oui, voici les liens vers les différentes traductions : +

+

1.2 Q02 Qu'est-ce que Sylpheed ? +

+ +

A. Sylpheed est un client de messagerie électronique (E-mail) +basé sur la bibliothèque Gtk+, fonctionnant sur X-window et +conçu pour être : +

    +
  • rapide ;
    • +
  • avec une interface agréable et simple à utiliser ;
    • +
  • de configuration simple et intuitive ;
    • +
  • avec de nombreuses fonctionnalités.
    • +
+

1.3 Q03 Où trouver Sylpheed ? +

+ +

A. Vous pouvez le télécharger à partir de +http://sylpheed.good-day.net +À partir de cette page, vous trouverez des liens pour télécharger +les sources, mais aussi les RPMs (pour les distributions Redhat et Mandrake) +les paquetages DEB pour la distribution Debian, et des installations pour +Solaris et FreeBSD. +

1.4 Q04 Qui écrit Sylpheed ? +

+ +

A. Hiroyuki Yamamoto (hiro-y@kcn.ne.jp) +

1.5 Q05 Que signifie le nom, Sylpheed ? +

+ +

A. Il signifie « léger », comme l'air et vient du nom de l'esprit des vents, +le Sylphe. +

1.6 Q06 Comment Sylpheed stocke-t-il les messages ? +

+ +

A. Les messages sont stockés dans des fichiers au format MH +(utilisé par MH et EMH). Les formats Maildir et mbox, ne sont pas +encore supportés, bien qu'il soit possible d'importer un fichier +mbox dans une boîte aux lettres Sylpheed. +

1.7 Q07 Pourquoi l'auto-collection des messages ne fonctionne-t-elle pas ? +

+ +

A. L'autocollection ne fonctionne que depuis cette version, si vous en avez besoin, +songez à mettre à jour votre installation de Sylpheed. +

1.8 Q08 Sylpheed peut-il filtrer les messages ? +

+ +

A. Oui. Vous trouverez cela dans le menu Configuration> Filtres. +Le filtrage n'est pas possible pour les comptes IMAP, pour le moment. +

1.9 Q09 Sylpheed peut-il gérer des comptes IMAP ? +

+ +

A. Oui. À partir de la version 0.4.99 IMAP est supporté. +

1.10 Q10 Sylpheed peut-il accéder à une boîte aux lettres locale Unix ? +

+ +

A. Oui. +

1.11 Q11 Est-ce que Sylpheed supporte IPv6 ? +

+ +

A. Oui, IPv6 est complètement supporté par Sylpheed. +

1.12 Q12 Est-ce que Sylpheed supporte le cryptage, comme le GPG ? +

+ +

A. Oui. GPG est supporté et fonctionne correctement. +Voir la question Q14 dans la section 'installation' pour +savoir comment activer cette fonction. +

1.13 Q13 Comment Sylpheed vérifie-t-il les types MIME ? +

+ +

A. Sylpheed utilise le meme type de vérification que Mutt. +

1.14 Q14 Puis-je écrire des messages au format HTML avec Sylpheed ? +

+ +

A. Non. Une discussion autour de ce sujet a eu lieu, et il en +est ressortit que cette fonctionnalité n'est pas désirée. +Si vous souhaitez quand meme envoyer de l'HTML, vous pouvez +joindre une page HTML a votre message. De nombreux patches ont été créé +pour améliorer la gestion du HTML par Sylpheed. Vous pouvez trouver +ces patches sur la page web des patches pour Sylpheed (voir plus loin +dans ce document). +

1.15 Q15 Sylpheed peut-il compléter les noms du champ « destinataire » ? +

+ +

A. Oui. Lorsque vous cherchez un nom qui commence par « don », +entrez « don » (sans les guiellemets) puis tapez la touche +TAB. Cela affichera le nom correct lorsqu'un seul « don » existe +dans votre carnet d'adresses. Sinon, une liste vous sera proposée +et vous pourrez sélectionner le nom que vous cherchez, par exemple +Donald Duck, ou Don Johnson. Les adresses de messagerie commençant +par « don » seront aussi incluses dans la liste (comme par exemple +« don.giovanni@maffia.org »). +

1.16 Q16 Bien, mais lorsque je tape la touche TAB, j'obtiens un message d'erreur. +

+ +

A. Lorsque vous utilisez la recherche de nom, vérifiez que votre carnet +d'adresses contient des noms. S'il est vide, ou qu'aucune correspondance +ne peut être trouvée, Sylpheed ne peut rien compléter. +

1.17 Q17 Pourquoi Sylpheed est-il si rapide ? +

+ +

A. Parce qu'il a été conçu pour cela ! +

1.18 Q18 Où puis-je trouver les derniers patches pour Sylpheed ? +

+ +

A. La page web des patches pour Sylpheed se trouve à l'adresse : +http://www.teledix.net/sylpheed/ +(Voir aussi la section concernant l'installation pour plus de +détails sur l'installation des patches) +

1.19 Q19 Comment puis-je envoyer un patch, signaler un bug, parler de Sylpheed avec d'autres personnes ? +

+ +

A. Pour parler à d'autres (fans de Sylpheed), rejoignez la liste de diffusion +de Sylpheed à : +http://sylpheed.good-day.net. +Notez qu'il existe une liste en japonais et une autre en anglais, +sélectionnez la bonne ! +Si vous avez créé un patch et que vous voulez que le monde +le sache, prenez contact avec le gestionnaire de la page des +patches pour Sylpheed à : sylpheed@thewildbeast.co.uk +

1.20 Q20 Quand j'envoie un message, l'en-tête définit le contenu comme étant en US-ASCII même lorsque je spécifie d'utiliser du ISO-8859-1 ? +

+ +

A. Si aucun caractère ISO-8859-1 (>= 0x80) n'est utilisé dans le corps du +message, Sylpheed définit automatiquement le type de contenu (dans +l'en-tête du message) comme utilisant le jeux de caractère US-ASCII. +

1.21 Q21 Pourquoi la mise en page (word wrap) semble ne pas fonctionner ? +

+ +

A. La mise en page est un peu bizarre, peut-être. En fait, +vous pouvez entrer des lignes aussi longues que vous voulez, au moment +d'envoyer le message, Sylpheed commence par mettre en page le message +au nombre de caractères (par ligne) maximum que vous avez défini. +C'est mieux pensé que vous ne le croyez. Une fois formatée (des retours +a la ligne sont insérés dans le texte), si vous ajoutez quelquechose +au début de votre phrase, le reste de la phrase passera à la ligne, +laissant quelques mots seuls entre deux lignes (provenant de la +première ligne). +

Par exemple : +

+     C'est une longue ligne
+     qui est formatée.
+
+

Maintenant, en ajoutant, un mot à la première ligne : +

+     C'est une très longue
+     ligne
+     qui est formatée.
+
+

Cela peut nécessiter un très grand nombre de remises en forme pour +finalement obtenir un message bien formaté. +

1.22 Q22 Où puis-je trouver la dernière version de la FAQ Sylpheed ? +

+ +

A. Sur +http://nlpagan.net/sylpheed-sylpheed-faq.html vous trouverez +la version anglaise (version de référence) dans laquelle vous trouverez +des liens vers les différentes traductions. +

Vous pouvez aussi obtenir les FAQ et manuels à partir de +http://www.sourceforge.net dans le projet sylpheeddoc. +Ce projet contient les versions les plus à jour des différentes +traductions de ces documents. +

1.23 Q23 Puis-je importer une bal mbox dans un dossier Sylpheed (MH) ? +

+ +

A. Oui. Vous devez juste créer ou sélectionner le dossier dans lequel +vous souhaitez insérer vos messages, puis sélectionner dans le menu +« Fichier », l'entrée « Importer un fichier mbox... ». +

1.24 Q24 Puis-je utiliser procmail pour trier mes messages ? +

+ +

A. Oui. Vous devez simplement vérifier que vous avez ajouté /. à la +fin de chaque règle, afin que procmail sache que vous filtrez dans +des dossiers MH. Par exemple : +

0: +

* ^Subject:.*sylpheed +

sylpheedmail/. +

Voir le manuel de procmail pour plus de détails. +

1.25 Q25 Lors des mises à jour de Sylpheed, dois-je faire attention à quelquechose ? +

+ +

A. Oui ! +

Mise à jour vers 0.4.50 : vous devez reconfigurer les newsgroups. +

Mise à jour vers 0.4.63 : vous devez définir la couleur des URLs dans le menu +de configuration. +

Mise à jour vers 0.4.65 : certaines entrées des menus ont été déplacées. +

1.26 Q26 Comment mettre à jour rapidement les différentes vues dans Sylpheed ? +

+ +

A. Utilisez Alt-U ou sélectionnez « mettre à jour » dans le menu « Résumé ». +

1.27 Q27 Pourquoi ne puis-je pas utiliser gvim comme éditeur ? +

+ +

+

A. Pour utiliser gvim comme éditeur il est nécessaire de le lancer avec +l'option -f (no-fork). Dans la fenêtre de configuration, vous devez saisir : +« gvim -f %s ». Sans cela, l'éditeur démarre un nouveau process, ouvre un +fichier et lorsque vous sortez de l'éditeur les changements sont perdus et +ne sont pas intégrés dans la fenêtre de composition. +

+

(Merci à Ed Collins !) +

+

+Page suivante +Page précédente +Table des matières + + diff --git a/faq/fr/sylpheed-faq-2.html b/faq/fr/sylpheed-faq-2.html new file mode 100644 index 0000000..3e99efd --- /dev/null +++ b/faq/fr/sylpheed-faq-2.html @@ -0,0 +1,140 @@ + + + + + FAQ Sylpheed: FAQ Sylpheed - Installation et configuration + + + + + +Page suivante +Page précédente +Table des matières +
+

2. FAQ Sylpheed - Installation et configuration

+ +

2.1 Q01 Que faut-il pour compiler Sylpheed ? +

+ +

A. Un système d'exploitation UNIX, respectant la norme POSIX +ou similaire, par exemple Linux, FreeBSD ou Solaris. +La bibliothèque GTK+ 1.2.6 ou plus récente. +Un compilateur ANSI C récent (gcc 2.7.2.3 devrait aussi fonctionner) +Note : le compilateur Sun C ne peut pas être utilisé pour compiler Sylpheed. +De façon optionnelle : +

    +
  • la bibliothèque Imlib ou gdk-pixbuf (pour la visualisation des images)
    • +
  • la bibliothèque libcompface (pour les icônes X-Face)
    • +
  • la bibliothèque libjconv (pour I18N)
    • +
  • la bibliothèque GPGME (pour le cryptage et la signature avec GnuPG)
    • +
  • les équivalents des paquetages GTK+-devel et Xfree86-devel.
    • +
+ +Sans cela la configuration avec ./configure échouera. +

2.2 Q02 Comment installer Sylpheed ? +

+ +

A. Lorsque vous démarrez Sylpheed pour la première fois, il vous sera +demandé l'emplacement (répertoire) ou vous souhaitez stocker vos dossiers. +Par défaut, il est défini comme <homedir>/Mail (homedir étant votre répertoire +de connexion). Vous pouvez changer cette valeur comme bon vous semble, +à condition qu'il s'agisse d'un répertoire valide (sur lequel vous avez +les droits d'écriture, entre autres). +

Lorsque Sylpheed est démarré pour la première fois, les fichiers +de configuration sont automatiquement créés dans le répertoire +$HOME/.sylpheed/ et il est demandé a l'utilisateur +de renseigner l'emplacement des boites aux lettres (la valeur +par défaut est: $HOME/Mail. Si ce répertoire contient +des fichiers qui ne sont pas au format MH, il vous faudra +spécifier un autre répertoire. +

2.3 Q03 Comment définir un compte de messagerie ? +

+ +

A. Après avoir démarré Sylpheed pour la première fois, vous pouvez +ajouter un compte de messagerie en utilisant le menu « Configuration ». +Sélectionnez l'option « Création d'un nouveau compte » et remplissez le +formulaire qui est affiché. +

2.4 Q04 Quel est le nombre maximum de comptes supportés par Sylpheed ? +

+ +

A. Le nombre n'est pas limité. La limite est atteinte lorsque votre +ordinateur ne répond plus. +

2.5 Q05 Pourquoi Sylpheed ne supprime-t-il pas mes messages lorsque je presse le bouton « Supprimer » ? J'ai défini un filtre et Sylpheed ne filtre rien. J'ai déplacé un message vers un autre dossier, et rien ne se passe. +

+ +

A. Vous devez cliquer sur le boutton « Exécuter ». Une autre solution +consiste à sélectionner l'option « Exécuter immédiatement... » dans la +section « Interface » des préférences générales. +

2.6 Q06 Comment définir une adresse ou un port pour le serveur de messagerie ou de news ? +

+ +

A. Dans la configuration du compte vous pouvez définir le port et l'adresse du +serveur pour ce compte. +

2.7 Q07 Sylpheed peut-il trier les messages par fil de discussion ? +

+ +

A. Oui. Vous pouvez le sélectionner par l'option « Vue par fil de conversation » du +menu « Sommaire », ou en utilisant le raccourci Ctrl-T. +

2.8 Q08 Puis-je créer plusieurs niveaux de dossiers pour ranger mes messages ? +

+ +

A. Sans problème. +

2.9 Q09 Pourquoi Sylpheed n'envoie-t-il pas mes messages ? +

+ +

A. Vous devez créer au moins un compte pour pouvoir envoyer des messages. +

2.10 Q10 Comment utiliser un patch après l'avoir téléchargé ? +

+ +

A. Copier le patch dans le répertoire Sylpheed, +puis l'appliquer : +

% patch -p0 < some.patch +

ou, s'il est gzipé : +

% gzip -dc some.patch.gz | patch -p0 +

Lancer ./autogen.sh, supprimer le fichier ./config.cache. +Lancer ./configure avec les options appropriées, puis make. +

2.11 Q11 Comment compiler avec le support des images 'compfaces' ? +

+ +

A. Vous devez obtenir le paquetage libcompface et l'installer pour +qu'il soit utilisable par Sylpheed. +

2.12 Q12 Comment créer ma propre image 'compface' ? +

+ +

A. Le paquetage faces contient un programme appelé xbm2ikon, qui +convertit une image xbm 48x48 au format nécessaire pour compface. +Grâce à Jeff Dairiki, vous pouvez avoir un cours complet sur cela à +l'adresse : +http://www.dairiki.org/xface/

+

2.13 Q13 Comment faire en sorte que mon navigateur internet (ou autre programme) utilise Sylpheed comme programme de messagerie ? +

+ +

A. Dans les préférences de ce programme, définir comme outil de messagerie : +sylpheed --compose +

2.14 Q14 Comment valider le support de GPG dans Sylpheed ? +

+ +

A. Lors de la compilation, vérifiez que vous avez ajouté l'option +--enable-gpgme lors de la configuration (avec ./configure). +

2.15 Q15 Mutt ne reconnaît pas la structure des dossiers de Sylpheed. +

+ +

A. Pour remédier à ce problème, vous devez créer un fichier .xmhcache +vide dans chaque dossier. Pour cela, utilisez la commande touch. +

2.16 Q17 Comment faire pour que Sylpheed signal l'arrivée de nouveaux messages? +

+ +

A. Pour cela vous pouvez faire: +

* Consulter la page des correctifs pour Sylpheed a +http://www.teledix.net/sylpheed/ +pour y trouver le correctif nécessaire. +

* Télécharger Gkrellm ou un programme similaire qui signalera l'arrivée +de tout nouveau message. Gkrellm se trouve a +http://www.gkrellm.net

+

+Page suivante +Page précédente +Table des matières + + diff --git a/faq/fr/sylpheed-faq-3.html b/faq/fr/sylpheed-faq-3.html new file mode 100644 index 0000000..75ac70a --- /dev/null +++ b/faq/fr/sylpheed-faq-3.html @@ -0,0 +1,120 @@ + + + + + FAQ Sylpheed: FAQ Sylpheed - L'interface + + + + +Page suivante +Page précédente +Table des matières +
+

3. FAQ Sylpheed - L'interface

+ +

3.1 Q01 Comment faire pour que Sylpheed parle ma langue ? +

+ +

A. Vous devez définir les variables d'environnement telles que +LANG,LC_CTYPE, LC_MESSAGES +pour votre langue (par exemple à « fr_FR » pour le français). +Normalement LANG (ou LC_ALL) est suffisant. +

3.2 Q02 Je n'aime pas la police par défaut, comment la changer ? +

+ +

A. Dans le menu « Configuration », sélectionnez « Préférences générales », puis allez dans la section +« Affichage ». +

3.3 Q03 Il y a trop de colonnes dans la liste des messages (fenêtre du sommaire) !! +

+ +

A. Dans la configuration, préférences générales, dans la section « Affichage », +cliquez sur le bouton « Éléments affichés dans le sommaire ». +Cela fera apparaître une fenêtre dans laquelle vous pourrez choisir les +éléments à afficher dans la fenêtre du sommaire. +

3.4 Q04 Comment utiliser mon éditeur préféré pour composer mes messages ? +

+ +

A. Dans le menu de configuration, dans les préférences générales, dans +la section « Autres », définissez l'éditeur de votre choix. +Attention, si vous sélectionnez un editeur en mode console, tel que vi ou emacs +vous devez le faire démarrer à partir d'un shell (term, xterm, rxvt,...) +avec le paramètre -e pour définir l'éditeur. Par exemple : +rxvt -e vi %s +

3.5 Q05 Comment changer la taille de la police dans Sylpheed ? +

+ +

A. Vous pouvez définir la police Gtk+ dans le fichier ~/.gtkrc, +ou ~/.gtkrc.mine, +(qui est appelé par ~/.gtkrc). +Par exemple : +style "default" +{ +font = +"-adobe-helvetica-medium-r-normal--12-*-*-*-*-*-iso8859-1 +" +} +widget_class "*" style "default" +

3.6 Q06 Sylpheed sauvegarde mes messages sortants (dans Outbox). Comment arrêter cela ? +

+ +

A. Dans le menu de configuration, sous les préférences générales, +dé-cocher la boite « Sauvegarder les messages envoyés dans la boîte d'envoi ». +

3.7 Q07 Comment changer les raccourcis de Sylpheed ? +

+ +

A. C'est très simple. Imaginons que vous souhaitez assigner +le raccourci Ctrl-Y à la fonction « Envoyer les messages en file d'attente ». +Cliquez sur le menu « Messages », déplacez le curseur sur la fonction +« Envoyer les messages en file d'attente », et maintenant appuyez sur Ctrl-Y. +Immédiatement, le texte du menu est mis à jour et contient le +raccourci que vous venez de définir. Notez que la fonction +dont le raccourci était Ctrl-Y (s'il y en avait une) n'a plus +de raccourci. +Pour supprimer un raccourci, appuyez sur la touche « Suppr » lorsque +le curseur est sur la fonction, cela supprimera le raccourci associé. +

3.8 Q08 Comment fermer les fenêtres sans utiliser la souris ? +

+ +

A. Vous ne pouvez pas fermer toutes les fenêtres de cette façon, +mais beaucoup se ferment en utilisant la touche « Echap » (Par exemple, la fenêtre du +carnet d'adresses, la fenêtre d'affichage du code source du message, la +fenêtre d'affichage des en-têtes, et d'autres). +Essayez, vous verrez. +

3.9 Q09 Comment puis-je changer le façon d'afficher la date dans la fenêtre du sommaire ? +

+ +

A. À partir de la version 0.4.65 vous le pouvez. Les options sont : +%y = année en chiffres %m = mois en chiffres +%d = jours en chiffres %c = format par défaut de la date et l'heure +%A = nom du jour %a = nom du jour (abrégé) +%B = nom du mois %b = nom du mois (abrégé) +%H = heure (24 heures) %I = heure (12 heures) +Pour plus d'informations, voir le menu de configuration, les préférences +générales, dans la section « Affichage », utiliser la fenêtre d'entrée +du format de la date. +

3.10 Q10 Pourquoi ne puis-je pas voir l'image 'compface' ? +

+ +

A. Vous devez autoriser l'affichage de cet élément d'en-tête dans les préférences. +

3.11 Q11 Je ne vois toujours pas l'image, pourquoi ? +

+ +

A. Vérifez que vous avez bien compilé Sylpheed avec le support +des images compfaces. Voir Q11 dans la section Installation/Configuration. +

3.12 Q12 Pourquoi aucun navigateur n'est lancé lorsque je clique sur un URL ? +

+ +

A. Il faut double-cliquer (deux fois rapidement). +

3.13 Q13 Les pièces jointes dont le nom contient un espace ne peuvent être ouvertes ! +

+ +

A. Lorsque vous lancez une application, telle que le visualiseur d'images, +avec une pièce jointe dont le nom contient des espaces, ajoutez des apostrophes +autour du paramètre %s. Par exemple : gedit '%s' +

+Page suivante +Page précédente +Table des matières + + diff --git a/faq/fr/sylpheed-faq.html b/faq/fr/sylpheed-faq.html new file mode 100644 index 0000000..5bca2d7 --- /dev/null +++ b/faq/fr/sylpheed-faq.html @@ -0,0 +1,104 @@ + + + + + FAQ Sylpheed + + + + + +Page suivante +Page précédente +Table des matières +
+

FAQ Sylpheed

+ + +

François Barriere (barriere.francois@libertysurf.fr) +

+

+ FAQ Sylpheed basée sur la version anglaise de + Paul Kater (paul@nlpagan.net) + et Jens Oberender (j.obi@troja.net). + Mise à jour pour la version 0.7.3. + +
+

Cette FAQ comprend les parties suivantes : +

+

1. FAQ Sylpheed - Informations générales

+ + +

+

2. FAQ Sylpheed - Installation et configuration

+ + +

+

3. FAQ Sylpheed - L'interface

+ + +
+Page suivante +Page précédente +Table des matières + + diff --git a/faq/it/Makefile.am b/faq/it/Makefile.am new file mode 100644 index 0000000..619228d --- /dev/null +++ b/faq/it/Makefile.am @@ -0,0 +1,11 @@ +faqdatadir = $(faqdir)/it + +faqdata_DATA = \ + sylpheed-faq-1.html \ + sylpheed-faq-2.html \ + sylpheed-faq-3.html \ + sylpheed-faq.html + +# generated by `ls -1 | sed -e 's/\(.*\)/ \1 \'` + +EXTRA_DIST = $(faqdata_DATA) diff --git a/faq/it/Makefile.in b/faq/it/Makefile.in new file mode 100644 index 0000000..49bd007 --- /dev/null +++ b/faq/it/Makefile.in @@ -0,0 +1,552 @@ +# Makefile.in generated by automake 1.14.1 from Makefile.am. +# @configure_input@ + +# Copyright (C) 1994-2013 Free Software Foundation, Inc. + +# This Makefile.in is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY, to the extent permitted by law; without +# even the implied warranty of MERCHANTABILITY or FITNESS FOR A +# PARTICULAR PURPOSE. + +@SET_MAKE@ + +VPATH = @srcdir@ +am__is_gnu_make = test -n '$(MAKEFILE_LIST)' && test -n '$(MAKELEVEL)' +am__make_running_with_option = \ + case $${target_option-} in \ + ?) ;; \ + *) echo "am__make_running_with_option: internal error: invalid" \ + "target option '$${target_option-}' specified" >&2; \ + exit 1;; \ + esac; \ + has_opt=no; \ + sane_makeflags=$$MAKEFLAGS; \ + if $(am__is_gnu_make); then \ + sane_makeflags=$$MFLAGS; \ + else \ + case $$MAKEFLAGS in \ + *\\[\ \ ]*) \ + bs=\\; \ + sane_makeflags=`printf '%s\n' "$$MAKEFLAGS" \ + | sed "s/$$bs$$bs[$$bs $$bs ]*//g"`;; \ + esac; \ + fi; \ + skip_next=no; \ + strip_trailopt () \ + { \ + flg=`printf '%s\n' "$$flg" | sed "s/$$1.*$$//"`; \ + }; \ + for flg in $$sane_makeflags; do \ + test $$skip_next = yes && { skip_next=no; continue; }; \ + case $$flg in \ + *=*|--*) continue;; \ + -*I) strip_trailopt 'I'; skip_next=yes;; \ + -*I?*) strip_trailopt 'I';; \ + -*O) strip_trailopt 'O'; skip_next=yes;; \ + -*O?*) strip_trailopt 'O';; \ + -*l) strip_trailopt 'l'; skip_next=yes;; \ + -*l?*) strip_trailopt 'l';; \ + -[dEDm]) skip_next=yes;; \ + -[JT]) skip_next=yes;; \ + esac; \ + case $$flg in \ + *$$target_option*) has_opt=yes; break;; \ + esac; \ + done; \ + test $$has_opt = yes +am__make_dryrun = (target_option=n; $(am__make_running_with_option)) +am__make_keepgoing = (target_option=k; $(am__make_running_with_option)) +pkgdatadir = $(datadir)/@PACKAGE@ +pkgincludedir = $(includedir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkglibexecdir = $(libexecdir)/@PACKAGE@ +am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd +install_sh_DATA = $(install_sh) -c -m 644 +install_sh_PROGRAM = $(install_sh) -c +install_sh_SCRIPT = $(install_sh) -c +INSTALL_HEADER = $(INSTALL_DATA) +transform = $(program_transform_name) +NORMAL_INSTALL = : +PRE_INSTALL = : +POST_INSTALL = : +NORMAL_UNINSTALL = : +PRE_UNINSTALL = : +POST_UNINSTALL = : +build_triplet = @build@ +host_triplet = @host@ +target_triplet = @target@ +subdir = faq/it +DIST_COMMON = $(srcdir)/Makefile.in $(srcdir)/Makefile.am \ + $(top_srcdir)/mkinstalldirs +ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 +am__aclocal_m4_deps = $(top_srcdir)/ac/aclocal-include.m4 \ + $(top_srcdir)/ac/gnupg-check-typedef.m4 \ + $(top_srcdir)/configure.ac +am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ + $(ACLOCAL_M4) +mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs +CONFIG_HEADER = $(top_builddir)/config.h +CONFIG_CLEAN_FILES = +CONFIG_CLEAN_VPATH_FILES = +AM_V_P = $(am__v_P_@AM_V@) +am__v_P_ = $(am__v_P_@AM_DEFAULT_V@) +am__v_P_0 = false +am__v_P_1 = : +AM_V_GEN = $(am__v_GEN_@AM_V@) +am__v_GEN_ = $(am__v_GEN_@AM_DEFAULT_V@) +am__v_GEN_0 = @echo " GEN " $@; +am__v_GEN_1 = +AM_V_at = $(am__v_at_@AM_V@) +am__v_at_ = $(am__v_at_@AM_DEFAULT_V@) +am__v_at_0 = @ +am__v_at_1 = +SOURCES = +DIST_SOURCES = +am__can_run_installinfo = \ + case $$AM_UPDATE_INFO_DIR in \ + n|no|NO) false;; \ + *) (install-info --version) >/dev/null 2>&1;; \ + esac +am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`; +am__vpath_adj = case $$p in \ + $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \ + *) f=$$p;; \ + esac; +am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`; +am__install_max = 40 +am__nobase_strip_setup = \ + srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'` +am__nobase_strip = \ + for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||" +am__nobase_list = $(am__nobase_strip_setup); \ + for p in $$list; do echo "$$p $$p"; done | \ + sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \ + $(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \ + if (++n[$$2] == $(am__install_max)) \ + { print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \ + END { for (dir in files) print dir, files[dir] }' +am__base_list = \ + sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \ + sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g' +am__uninstall_files_from_dir = { \ + test -z "$$files" \ + || { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \ + || { echo " ( cd '$$dir' && rm -f" $$files ")"; \ + $(am__cd) "$$dir" && rm -f $$files; }; \ + } +am__installdirs = "$(DESTDIR)$(faqdatadir)" +DATA = $(faqdata_DATA) +am__tagged_files = $(HEADERS) $(SOURCES) $(TAGS_FILES) $(LISP) +DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) +ACLOCAL = @ACLOCAL@ +ALLOCA = @ALLOCA@ +AMTAR = @AMTAR@ +AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@ +AR = @AR@ +AUTOCONF = @AUTOCONF@ +AUTOHEADER = @AUTOHEADER@ +AUTOMAKE = @AUTOMAKE@ +AWK = @AWK@ +BUILD_REVISION = @BUILD_REVISION@ +CATALOGS = @CATALOGS@ +CATOBJEXT = @CATOBJEXT@ +CC = @CC@ +CCDEPMODE = @CCDEPMODE@ +CFLAGS = @CFLAGS@ +CPP = @CPP@ +CPPFLAGS = @CPPFLAGS@ +CYGPATH_W = @CYGPATH_W@ +DATADIRNAME = @DATADIRNAME@ +DEFS = @DEFS@ +DEPDIR = @DEPDIR@ +DEVEL_VERSION = @DEVEL_VERSION@ +DLLTOOL = @DLLTOOL@ +DSYMUTIL = @DSYMUTIL@ +DUMPBIN = @DUMPBIN@ +ECHO_C = @ECHO_C@ +ECHO_N = @ECHO_N@ +ECHO_T = @ECHO_T@ +EGREP = @EGREP@ +EXEEXT = @EXEEXT@ +EXTRA_VERSION = @EXTRA_VERSION@ +FGREP = @FGREP@ +GETTEXT_PACKAGE = @GETTEXT_PACKAGE@ +GLIB_CFLAGS = @GLIB_CFLAGS@ +GLIB_COMPILE_RESOURCES = @GLIB_COMPILE_RESOURCES@ +GLIB_GENMARSHAL = @GLIB_GENMARSHAL@ +GLIB_LIBS = @GLIB_LIBS@ +GLIB_MKENUMS = @GLIB_MKENUMS@ +GMOFILES = @GMOFILES@ +GMSGFMT = @GMSGFMT@ +GOBJECT_QUERY = @GOBJECT_QUERY@ +GPGME_CFLAGS = @GPGME_CFLAGS@ +GPGME_CONFIG = @GPGME_CONFIG@ +GPGME_LIBS = @GPGME_LIBS@ +GREP = @GREP@ +GTK_CFLAGS = @GTK_CFLAGS@ +GTK_LIBS = @GTK_LIBS@ +INSTALL = @INSTALL@ +INSTALL_DATA = @INSTALL_DATA@ +INSTALL_PROGRAM = @INSTALL_PROGRAM@ +INSTALL_SCRIPT = @INSTALL_SCRIPT@ +INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@ +INSTOBJEXT = @INSTOBJEXT@ +INTLLIBS = @INTLLIBS@ +LD = @LD@ +LDAP_LIBS = @LDAP_LIBS@ +LDFLAGS = @LDFLAGS@ +LEX = @LEX@ +LEXLIB = @LEXLIB@ +LEX_OUTPUT_ROOT = @LEX_OUTPUT_ROOT@ +LIBICONV = @LIBICONV@ +LIBOBJS = @LIBOBJS@ +LIBS = @LIBS@ +LIBSYLPH_CFLAGS = @LIBSYLPH_CFLAGS@ +LIBSYLPH_LIBS = @LIBSYLPH_LIBS@ +LIBTOOL = @LIBTOOL@ +LIPO = @LIPO@ +LN_S = @LN_S@ +LTLIBICONV = @LTLIBICONV@ +LTLIBOBJS = @LTLIBOBJS@ +LT_AGE = @LT_AGE@ +LT_CURRENT = @LT_CURRENT@ +LT_RELEASE = @LT_RELEASE@ +LT_REVISION = @LT_REVISION@ +MAINT = @MAINT@ +MAJOR_VERSION = @MAJOR_VERSION@ +MAKEINFO = @MAKEINFO@ +MANIFEST_TOOL = @MANIFEST_TOOL@ +MICRO_VERSION = @MICRO_VERSION@ +MINOR_VERSION = @MINOR_VERSION@ +MKDIR_P = @MKDIR_P@ +MKINSTALLDIRS = @MKINSTALLDIRS@ +MSGFMT = @MSGFMT@ +MSGFMT_OPTS = @MSGFMT_OPTS@ +NM = @NM@ +NMEDIT = @NMEDIT@ +OBJDUMP = @OBJDUMP@ +OBJEXT = @OBJEXT@ +OPENSSL_CFLAGS = @OPENSSL_CFLAGS@ +OPENSSL_LIBS = @OPENSSL_LIBS@ +OTOOL = @OTOOL@ +OTOOL64 = @OTOOL64@ +PACKAGE = @PACKAGE@ +PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@ +PACKAGE_NAME = @PACKAGE_NAME@ +PACKAGE_STRING = @PACKAGE_STRING@ +PACKAGE_TARNAME = @PACKAGE_TARNAME@ +PACKAGE_URL = @PACKAGE_URL@ +PACKAGE_VERSION = @PACKAGE_VERSION@ +PATH_SEPARATOR = @PATH_SEPARATOR@ +PKG_CONFIG = @PKG_CONFIG@ +PKG_CONFIG_LIBDIR = @PKG_CONFIG_LIBDIR@ +PKG_CONFIG_PATH = @PKG_CONFIG_PATH@ +POFILES = @POFILES@ +POSUB = @POSUB@ +PO_IN_DATADIR_FALSE = @PO_IN_DATADIR_FALSE@ +PO_IN_DATADIR_TRUE = @PO_IN_DATADIR_TRUE@ +RANLIB = @RANLIB@ +SED = @SED@ +SET_MAKE = @SET_MAKE@ +SHELL = @SHELL@ +STRIP = @STRIP@ +SYLPHEED_LIBS = @SYLPHEED_LIBS@ +USE_NLS = @USE_NLS@ +VERSION = @VERSION@ +WINDRES = @WINDRES@ +XGETTEXT = @XGETTEXT@ +YACC = @YACC@ +YFLAGS = @YFLAGS@ +abs_builddir = @abs_builddir@ +abs_srcdir = @abs_srcdir@ +abs_top_builddir = @abs_top_builddir@ +abs_top_srcdir = @abs_top_srcdir@ +ac_ct_AR = @ac_ct_AR@ +ac_ct_CC = @ac_ct_CC@ +ac_ct_DUMPBIN = @ac_ct_DUMPBIN@ +am__include = @am__include@ +am__leading_dot = @am__leading_dot@ +am__quote = @am__quote@ +am__tar = @am__tar@ +am__untar = @am__untar@ +bindir = @bindir@ +build = @build@ +build_alias = @build_alias@ +build_cpu = @build_cpu@ +build_os = @build_os@ +build_vendor = @build_vendor@ +builddir = @builddir@ +datadir = @datadir@ +datarootdir = @datarootdir@ +docdir = @docdir@ +dvidir = @dvidir@ +exec_prefix = @exec_prefix@ +faqdir = @faqdir@ +host = @host@ +host_alias = @host_alias@ +host_cpu = @host_cpu@ +host_os = @host_os@ +host_vendor = @host_vendor@ +htmldir = @htmldir@ +includedir = @includedir@ +infodir = @infodir@ +install_sh = @install_sh@ +libdir = @libdir@ +libexecdir = @libexecdir@ +localedir = @localedir@ +localstatedir = @localstatedir@ +mandir = @mandir@ +manualdir = @manualdir@ +mkdir_p = @mkdir_p@ +oldincludedir = @oldincludedir@ +pdfdir = @pdfdir@ +plugindir = @plugindir@ +prefix = @prefix@ +program_transform_name = @program_transform_name@ +psdir = @psdir@ +sbindir = @sbindir@ +sharedstatedir = @sharedstatedir@ +srcdir = @srcdir@ +sysconfdir = @sysconfdir@ +target = @target@ +target_alias = @target_alias@ +target_cpu = @target_cpu@ +target_os = @target_os@ +target_vendor = @target_vendor@ +themedir = @themedir@ +top_build_prefix = @top_build_prefix@ +top_builddir = @top_builddir@ +top_srcdir = @top_srcdir@ +faqdatadir = $(faqdir)/it +faqdata_DATA = \ + sylpheed-faq-1.html \ + sylpheed-faq-2.html \ + sylpheed-faq-3.html \ + sylpheed-faq.html + + +# generated by `ls -1 | sed -e 's/\(.*\)/ \1 \'` +EXTRA_DIST = $(faqdata_DATA) +all: all-am + +.SUFFIXES: +$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.am $(am__configure_deps) + @for dep in $?; do \ + case '$(am__configure_deps)' in \ + *$$dep*) \ + ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \ + && { if test -f $@; then exit 0; else break; fi; }; \ + exit 1;; \ + esac; \ + done; \ + echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign faq/it/Makefile'; \ + $(am__cd) $(top_srcdir) && \ + $(AUTOMAKE) --foreign faq/it/Makefile +.PRECIOUS: Makefile +Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status + @case '$?' in \ + *config.status*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \ + *) \ + echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \ + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \ + esac; + +$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh + +$(top_srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(am__configure_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ $(am__aclocal_m4_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(am__aclocal_m4_deps): + +mostlyclean-libtool: + -rm -f *.lo + +clean-libtool: + -rm -rf .libs _libs +install-faqdataDATA: $(faqdata_DATA) + @$(NORMAL_INSTALL) + @list='$(faqdata_DATA)'; test -n "$(faqdatadir)" || list=; \ + if test -n "$$list"; then \ + echo " $(MKDIR_P) '$(DESTDIR)$(faqdatadir)'"; \ + $(MKDIR_P) "$(DESTDIR)$(faqdatadir)" || exit 1; \ + fi; \ + for p in $$list; do \ + if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \ + echo "$$d$$p"; \ + done | $(am__base_list) | \ + while read files; do \ + echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(faqdatadir)'"; \ + $(INSTALL_DATA) $$files "$(DESTDIR)$(faqdatadir)" || exit $$?; \ + done + +uninstall-faqdataDATA: + @$(NORMAL_UNINSTALL) + @list='$(faqdata_DATA)'; test -n "$(faqdatadir)" || list=; \ + files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \ + dir='$(DESTDIR)$(faqdatadir)'; $(am__uninstall_files_from_dir) +tags TAGS: + +ctags CTAGS: + +cscope cscopelist: + + +distdir: $(DISTFILES) + @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + list='$(DISTFILES)'; \ + dist_files=`for file in $$list; do echo $$file; done | \ + sed -e "s|^$$srcdirstrip/||;t" \ + -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \ + case $$dist_files in \ + */*) $(MKDIR_P) `echo "$$dist_files" | \ + sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \ + sort -u` ;; \ + esac; \ + for file in $$dist_files; do \ + if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ + if test -d $$d/$$file; then \ + dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d "$(distdir)/$$file"; then \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ + if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ + cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \ + find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \ + fi; \ + cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \ + else \ + test -f "$(distdir)/$$file" \ + || cp -p $$d/$$file "$(distdir)/$$file" \ + || exit 1; \ + fi; \ + done +check-am: all-am +check: check-am +all-am: Makefile $(DATA) +installdirs: + for dir in "$(DESTDIR)$(faqdatadir)"; do \ + test -z "$$dir" || $(MKDIR_P) "$$dir"; \ + done +install: install-am +install-exec: install-exec-am +install-data: install-data-am +uninstall: uninstall-am + +install-am: all-am + @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am + +installcheck: installcheck-am +install-strip: + if test -z '$(STRIP)'; then \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + install; \ + else \ + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \ + fi +mostlyclean-generic: + +clean-generic: + +distclean-generic: + -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES) + +maintainer-clean-generic: + @echo "This command is intended for maintainers to use" + @echo "it deletes files that may require special tools to rebuild." +clean: clean-am + +clean-am: clean-generic clean-libtool mostlyclean-am + +distclean: distclean-am + -rm -f Makefile +distclean-am: clean-am distclean-generic + +dvi: dvi-am + +dvi-am: + +html: html-am + +html-am: + +info: info-am + +info-am: + +install-data-am: install-faqdataDATA + +install-dvi: install-dvi-am + +install-dvi-am: + +install-exec-am: + +install-html: install-html-am + +install-html-am: + +install-info: install-info-am + +install-info-am: + +install-man: + +install-pdf: install-pdf-am + +install-pdf-am: + +install-ps: install-ps-am + +install-ps-am: + +installcheck-am: + +maintainer-clean: maintainer-clean-am + -rm -f Makefile +maintainer-clean-am: distclean-am maintainer-clean-generic + +mostlyclean: mostlyclean-am + +mostlyclean-am: mostlyclean-generic mostlyclean-libtool + +pdf: pdf-am + +pdf-am: + +ps: ps-am + +ps-am: + +uninstall-am: uninstall-faqdataDATA + +.MAKE: install-am install-strip + +.PHONY: all all-am check check-am clean clean-generic clean-libtool \ + cscopelist-am ctags-am distclean distclean-generic \ + distclean-libtool distdir dvi dvi-am html html-am info info-am \ + install install-am install-data install-data-am install-dvi \ + install-dvi-am install-exec install-exec-am \ + install-faqdataDATA install-html install-html-am install-info \ + install-info-am install-man install-pdf install-pdf-am \ + install-ps install-ps-am install-strip installcheck \ + installcheck-am installdirs maintainer-clean \ + maintainer-clean-generic mostlyclean mostlyclean-generic \ + mostlyclean-libtool pdf pdf-am ps ps-am tags-am uninstall \ + uninstall-am uninstall-faqdataDATA + + +# Tell versions [3.59,3.63) of GNU make to not export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.NOEXPORT: diff --git a/faq/it/sylpheed-faq-1.html b/faq/it/sylpheed-faq-1.html new file mode 100644 index 0000000..9b47503 --- /dev/null +++ b/faq/it/sylpheed-faq-1.html @@ -0,0 +1,227 @@ + + + + + Sylpheed FAQ: Sylpheed FAQ - Informazioni generali + + + + + +Precedente +Contenuti +Successivo +
+

1. Sylpheed FAQ - Informazioni generali

+ +

1.1 Q01 Ci sono FAQ in altre lingue? +

+ +

A. Sì. Qui ci sono i link per diverse traduzioni: +

    +
  • http://www.enseirb.fr/ dinh/sylpheed/sylpheed-FAQ-fr.html: SYLPHEED FAQ in francese grazie a DINH V. Hoa
    • +
  • http://silver.lacmhacarh.gr.jp/sylpheed/sylpheedfaq-ja.htm: SYLPHEED FAQ in giapponese grazie a WAKAI "SilverRain" Kazunao
    • +
  • http://beatles.cselt.it/ mau/sylpheed/sylpheedfaq.html: SYLPHEED FAQ in italiano grazie a Maurizio Codogno
    • +
  • http://www.synconet.de/privhome/rs/sylpheed_faq.html: SYLPHEED FAQ in tedesco (versione HTML)
    • +
  • http://www.synconet.de/privhome/rs/sylpheed_faq.txt: versione in tedesco solo testo, entrambe grazie a Ralf Schiffers.
    • +
  • http://www.cs.uoi.gr/ csst9910/el_sylfaq.html: SYLPHEED FAQ in greco grazie a Theofilos Intzoglou.
    • +
  • http://sylpheed.republika.pl: SYLPHEED FAQ in polacco grazie a Przemyslaw Sulek.
    • +
  • http://www.geocities.com/hackpando/sylpheedfaq.html: versione HTML di Marcelo Ramos, anche:
    • +
  • http://www.geocities.com/hackpando/sylpheedfaq.txt: versione solo testo
    • +
  • http://www.aic.uniovi.es/mones/sylpheed/faq-es/ : versione HTML, di Ricardo Mones Lastra, come pure
    • +
  • http://www.aic.uniovi.es/mones/sylpheed/faq-es.dvi: FAQ-es.dvi (Device independent)
    • +
  • http://www.aic.uniovi.es/mones/sylpheed/faq-es.ps: FAQ in spagnolo come Postscript file.
    • +
  • http://linux.fisek.com.tr/dfisek/sylpheed-sss.html: Una FAQ in turco per Sylpheed è disponibile grazie alla traduzione di Doruk Fisek.
    • +
  • http://hem.passagen.se/webplats/sylpheed-faq-se.html: FAQ svedese, grazie a Mattias Stergren
    • +
+ +Puoi scaricare questa FAQ in formato testo (in inglese) da http://nlpagan.net/sylpheedfaq.tar.gz +

1.2 Q02 Cos'è Sylpheed? +

+ +

A. Sylpheed è un client di mail (& lettore di news) basato su +GTK+, eseguito su un X Window System, e progettato per +

    +
  • Risposte rapide
    • +
  • Interfaccia sofisticata e accattivante
    • +
  • Facile configurazione, operazioni intuitive
    • +
  • Abbondanti caratteristiche
    • +
+

1.3 Q03 Dove posso prendere Sylpheed? +

+ +

A. Lo puoi scaricare da http://sylpheed.good-day.net . +Qui ci sono link per scaricare i sorgenti in formato .tar, e anche link +verso siti dove puoi trovare gli RPM (per Redhat and Mandrake), +pacchetti DEB per Debian, e installazioni per Solaris e FreeBSD. +

1.4 Q04 Chi scrive Sylpheed? +

+ +

A. Hiroyuki Yamamoto (hiro-y@kcn.ne.jp) +

1.5 Q05 Cosa significa il nome Sylpheed? +

+ +

A. Significa "peso leggero", come l'aria. Deriva dal nome +degli spiriti del vento, i Sylphs. +

1.6 Q06 In che modo Sylpheed memorizza le mail? +

+ +

A. Le mail sono memorizzate in file di formato MH per essere utilizzate +da MH e EMH. I formati MailDir e mbox non sono, per il momento, +supportati, tuttavia è possibile importare un file di tipo mbox +in una mailbox di Sylpheed. +

1.7 Q07 Perché la collezione automatica delle mail non funziona? +

+ +

A. La collezione automatica è stata implementata in Sylpheed a partire dalla +versione 0.5.1. Se hai bisogno di questa caratteristica o vuoi provarla, devi +aggiornare la tua versione di Sylpheed. +

1.8 Q08 Sylpheed può filtrare le mail? +

+ +

A. Sì. Puoi trovarlo nel menu Configurazione > Filtraggio. +

ATTENZIONE. Il filtraggio delle mail non è ancora implementato per account di +tipo IMAP. +

1.9 Q09 Sylpheed può prelevare mail da un server IMAP? +

+ +

A. Sì. IMAP è supportato dalla versione 0.4.99. +

1.10 Q10 Sylpheed può prelevare mail da una casella UNIX di posta locale? +

+ +

A. Sì. +

1.11 Q11 Sylpheed utilizza il protocollo IPv6? +

+ +

A. Sì, IPv6 è supportato appieno in Sylpheed. +

1.12 Q12 Sylpheed supporta protocolli di crittografia tipo GPG? +

+ +

A. Sì. GPG implementato e lavora egregiamente. Per attivarlo, +vedi Q14 nella sezione Installazione. +

1.13 Q13 Sylpheed come verifica i tipi MIME? +

+ +

A. Sylpheed utilizza un metodo di controllo per i tipi MIME come quello di MUTT. +

1.14 Q14 Sylpheed permette la scrittura di mail in stile HTML? +

+ +

A. No. Una discussione è andata avanti per parecchio tempo circa questo argomento, +e il risultato è stato che questa caratteristica era non richiesta. Se hai bisogno +di questa caratteristica, puoi allegare una pagina web ad una mail. +Diverse patch sono state create per facilitare questa operazione in Sylpheed. +Puoi trovare queste patch alla Sylpheed Patch Page (vedi più avanti in questo +documento). +

1.15 Q15 Sylpheed completa automaticamente i nomi nel campo indirizzo? +

+ +

A. Sì. Quando cerchi un nome che inizia per "don", +digita "don" (senza le virgolette) e premi il tasto TAB. +Questo mostrerà il nome corretto (solo quando un solo "don" +esiste nella rubrica. Negli altri casi compare una dropdown list, +che ti permette di selezionare il nome che preferisci. +E.g. Donald Duck, Don Johnson. Ma ricorda: appariranno nella lista solo gli +indirizzi che iniziano per "don" (tipo "don.giovanni@maffia.org"). +

1.16 Q16 OK, ma quando premo il tasto TAB ottengo un errore. +

+ +

A. Quando vuoi utilizzare il completamento automatico dei nome, assicurati che +ci siano dei nomi nella rubrica. Se non ce ne sono, sarà dura per Sylpheed capire +che nome vuoi e quindi completarlo. +

1.17 Q17 Perché Sylpheed è così veloce? +

+ +

A. E' stato progettato per esserlo! +

1.18 Q18 Dove posso prendere le ultime patch per Sylpheed? +

+ +

A. Alla Sylpheed Patch homepage: +http://www.teledix.net/sylpheed/ +(Leggi la sezione Installazione su come installare una patch) +

1.19 Q19 Come posso spedire patch, report di bug, discorrere circa Sylpheed con altri utenti? +

+ +

A. Per parlare con altri utenti, aderisci alla Sylpheed mailing +list su http://sylpheed.good-day.net. ATTENZIONE: c'è una versione +giapponese ed una inglese della lista, perciò scegli quella giusta! +Se hai fatto una patch che vuoi far conoscere anchbe agli altri, +contatto il manager della Sylpheed Patch homepage, all'indirizzo sylpheed@thewildbeast.co.uk +

1.20 Q20 Quando spedisco una mail, il campo Content-Type dell'intestazione dice che la mail è in US-ASCII, anche se io ho specificato ISO-8859-1? +

+ +

A. Se non ci sono caratteri nel corpo del messaggio di tipo +ISO-8859-1 (>= 0x80), Sylpheed modificherà automaticamente il valore del +charset nel campo Content-Type dell'intestazione a US-ASCII. +

1.21 Q21 Perché sembra che il word wrap non funzioni? +

+ +

A. Word wrapping è una piccola peculiarità. Puoi scrivere una linea di testo +lunga quanto vuoi. Nel momento in cui spedisci o metti in coda la mail +col la linea lunga, Sylpheed spezzerà la linea in tante linee non più lunghe +di quanto tu abbia configurato e poi la mail viene messa in coda. +Questo è più conveniente di quanto tu possa pensare. Una volta che la linea +è spezzettata (interruzioni di linea sono inseriti nel testo) +ed aggiungi qualcosa nella prima linea di queste, la linea successiva +si muoverà in una linea separata, lasciando una o due parole dalla linea +precedente da sole. +Esempio +

+     Questa è una linea lunga
+	 è stata spezzata.
+
+

Ora aggiungo una parola alla prima linea: +

+     Questa è una linea lunga
+	 che
+	 è stata spezzata.
+
+

Ciò causerebbe una gran quantità di riformattazione a mano per avere +di nuovo una mail presentabile e leggibile. +

1.22 Q22 Dove posso trovare l'ultima FAQ su Sylpheed? +

+ +

A. Vai a http://nlpagan.net/sylpheedfaq.htm dove le FAQ +sono disponibili in inglese. Puoi anche trovare link a FAQ in altre lingue. +

Puoi anche andare a http://www.sourceforge.net e prelevare le faq e il +manuale dal progretto sylpheeddoc. Entrambi i documenti sono disponibili +in diverse lingue e di solito contengono gli ultimi aggiornamenti. +

1.23 Q23 Posso importare una casella di tipo mbox nella struttura di tipo MH di Sylpheed? +

+ +

A. sì, basta creare/selezionare la cartella dove vuoi mettere le tue mail, +e selezionare "Importa mbox da file..." nel menu File. +

1.24 Q24 Posso utilizzare 'procmail' per ordinare le mail con una struttura di tipo MH? +

+ +

A. Sì. Assicurati solo di aggiungere /. alla fine dei ruoli così che +procmail riconosce che tu stai filtrando in una cartella di tipo MH. Esempio: +

0: +

* ^Subject:.*sylpheed +

sylpheedmail/. +

Leggi il man di procmail per maggiori dettagli. +

1.25 Q25 Quando effettuo un'upgrade di Sylpheed, c'è qualcosa a cui devo stare attento? +

+ +

A. Sì! +

Aggiornamento alla 0.4.50: devi riconfigurare i tuoi settaggi per i newsgroup +

Aggiornamento alla 0.4.63: devi configurare i colori per le stringhe URL dal menu Configurazione. +

Aggiornamento alla 0.4.65: alcune voci di menu sono state spostate +

1.26 Q26 Come posso aggiornare velocemente le viste in Sylpheed? +

+ +

A. Premi Alt-U o seleziona "update" dal menu Sommario. +

1.27 Q27 Perché non posso utilizzare 'gvim' come editor esterno? +

+ +

A. Se vuoi davvero utilizzare gvim come editor esterno, è necessario +lanciarlo con l'opzione no-fork (parametro -f), ad esempio nel dialog box di +configurazione devi inserire "gvim -f %s". Se non lo fai, l'editor forka e +apre un file separato; quando si esce dall'editor i cambiamenti vengono persi +e non vengono inseriti nella finestra di composizione. +

(Grazie, Ed Collins!) +

+Precedente +Contenuti +Successivo + + diff --git a/faq/it/sylpheed-faq-2.html b/faq/it/sylpheed-faq-2.html new file mode 100644 index 0000000..418c7a4 --- /dev/null +++ b/faq/it/sylpheed-faq-2.html @@ -0,0 +1,142 @@ + + + + + Sylpheed FAQ: Sylpheed FAQ - Installazione e Configurazione + + + + + +Precedente +Contenuti +Successivo +
+

2. Sylpheed FAQ - Installazione e Configurazione

+ +

2.1 Q01 Cosa devo avere per compilare Sylpheed? +

+ +

A. QUalsiasi UNIX POSIX compliant o sistema operativo simile tipo Linux, +FreeBSD, Solaris +GTK+ 1.2.6 o successivi +Un compilatore ANSI C recente (gcc 2.7.2.3 dovrebbe funzionare ancora) +ATTENZIONE: è documentato che il compilatore Sun C non compila Sylpheed. +Opzioni: +

    +
  • Imlib o gdk-pixbuf (per visualizzare le immagini dal client)
    • +
  • libcompface (per X-Face)
    • +
  • libjconv (per I18N)
    • +
  • GPGME (per GnuPG)
    • +
  • l'equivalente del GTK+-devel e Xfree86-devel.
    • +
+ +Senza tutto ciò ./configure fallirà. +

2.2 Q02 Come posso configurare Sylpheed? +

+ +

A. Quando esegui Sylpheed la prima volta, ti verrà chiesto dove vuoi +memorizzare le tue mail. Il default è <homedir>/Mail. Puoi cambiarlo in +qualsiasi cosa tu preferisci purché sia un nome di directory valido. +

ATTENZIONE: Quando esegui Sylpheed la prima volta, viene creato automaticamente +il file di configurazione sotto $HOME/.sylpheed/, e ti viene richiesto dove +posizionare la tua mailbox. Il default è $HOME/Mail. Se ci sono file preesistenti +che non sono in formato MH, dovrai specificare un'altra directory. +

2.3 Q03 Come posso configurare un account? +

+ +

A. Dopo aver eseguito la prima volta Sylpheed, puoi aggiungere un account +selezionando il menu "Configuratione". Seleziona l'opzione "Crea nuovo account..." +e riempi tutti i campi appropriati. +

2.4 Q04 Quanti accout posso configurare? +

+ +

A. Il numero è illimitato. Hai raggiunto il limite quando il tuo computer +finisce di risponderti. +

2.5 Q05 Perché Sylpheed non cancella le mie mail quando premo "delete"? Configuro un filtro, e Sylpheed non filtra. Sposto una mail in una cartella differente e questa non si muove. +

+ +

A. Devi premere il bottone "Esegui". +Altra soluzione: nei settaggi della configurazione +(Opzioni globali... > tab "Interfaccia") devi selezionare l'opzione +"Esegui immediatamente quando sposti o elimini dei messaggi". +

2.6 Q06 Posso configurare indirizzi speciali/porte per i miei server di mail/news? +

+ +

A. Certamente. Nella configurazione di ogni singolo account puoi +specificare la porta/indirizzo che vuoi usare. +

2.7 Q07 Sylpheed ha qualche opzione per le discussioni? +

+ +

A. Sì. Puoi abilitare o disabilitare dal menu Vista, +selezionando l'opzione "Vista discussione" o premendo Ctrl+T. +

2.8 Q08 Posso creare livelli multipli di sotto cartelle per memorizzare le mail? +

+ +

A. Certamente. Senza nessun problema. +

2.9 Q09 Perché Sylpheed non spedisce le mail in uscita? +

+ +

A. Devi creare almeno un account per poter spedire la posta. +

2.10 Q10 Come posso applicare una patch dopo che l'ho scaricata? +

+ +

A. Copia la patch nella directory dove risiedono i sorgenti di Sylpheed. +Applica la patch: +

% patch -p0 < some.patch +

Oppure, se è gzipped: +

% gzip -dc some.patch.gz | patch -p0 +

Esegui ./autogen.sh, rimuovi il file /config.cache +(sempre che tu non voglia installarlo nel prefix +/usr/local). +Esegui ./configure con le opzioni appropriate e +poi make. +(Queste istruzioni le trovi nella home page delle patch di Sylpheed.) +

2.11 Q11 Come posso compilare il supporto per le immagini di tipo compface? +

+ +

A. Devi avere installato sul tuo sistema un package di nome libcompface, +così è disponibile per la compialzione di Sylpheed. +

2.12 Q12 Come posso fare la mia immagine compface? +

+ +

A. Il package libcompface contiene un programma chiamato xbm2ikon, +che converte un'immagine xbm 48x48 al formato richiesto da compface. +Grazie a Jeff Dairiki, Puoi avere un corso completo online per questa caratteristica. +Visita http://www.dairiki.org/xface/ per i dettagli. +

2.13 Q13 Come posso specificare al mio browser/client di news/altro programma di usare Sylpheed come programma per le mail? +

+ +

A. Nella parte di configurazione del programma, scrivi +sylpheed --compose +

2.14 Q14 Come posso abilitare il supporto per GPG in Sylpheed? +

+ +

A. Quando compili Sylpheed, assicurati di aggiungere --enable-gpgme al ./configure. +Quando la procedura di compilazione termina, troverai una sezione "privacy" +nel menu Configurazione -> Opzioni globali... . +

2.15 Q15 Mutt non riconosce la struttura MH di Sylpheed +

+ +

A. Per farla riconoscere devi usare il comando "touch" in ogni cartella MH. +"touch" il file .xmhcache e Mutt funzionerà. +

2.16 Q16 Se visualizzo una GIF all'interno di Sylpheed ottengo un segmentation fault. +

+ +

A. Nel caso succedesse, puoi rimediare facilmente aggiungendo la seguente +riga nel file /etc/mime.types: +

image/gif gif +

2.17 Q17 Come posso fare che Sylpheed mi avverta quando arrivano nuove mail? +

+ +

A. Per questo hai diverse soluzioni: +

* Verifica se nella Sylpheed patch page (http://www.teledix.net/sylpheed/) c'è una patch per le nuove mail. +

* Scarica Gkrellm o un programma simile che può notificare l'arrivo di nuove +mail. Gkrellm è disponibile su http://www.gkrellm.net +

+

+Precedente +Contenuti +Successivo + + diff --git a/faq/it/sylpheed-faq-3.html b/faq/it/sylpheed-faq-3.html new file mode 100644 index 0000000..c95c8da --- /dev/null +++ b/faq/it/sylpheed-faq-3.html @@ -0,0 +1,111 @@ + + + + + Sylpheed FAQ: Sylpheed FAQ - Interfaccia + + + + +Precedenti +Contenuti +Successivo +
+

3. Sylpheed FAQ - Interfaccia

+ +

3.1 Q01 Come posso settare la mia lingua su Sylpheed? +

+ +

A. Devi settare alcuni parametri dell'environment come +LANG, LC_CTYPE, LC_MESSAGES nella tua lingua locale. +Di solito LANG (o LC_ALL) è sufficiente. +

3.2 Q02 Non mi piace il font di default. Posso cambiarlo? +

+ +

A. Sì. In Configurazione > Opzioni globali... sotto il tab "Visualizzazione". +

3.3 Q03 Ci sono troppe colonne nella lista dei messaggi!! +

+ +

A. In Configurazione > Opzioni globali... sotto il tab "Visualizzazione" +premi il bottone "Imposta le voci visibili nel sommario". +Questo mostra una finestra con tutte le opzioni che puoi vedere o non vedere nella +lista dei messaggi. +

3.4 Q04 Posso utilizzare un editor differente per scrivere le mie mail? +

+ +

A. Certamente. In Configurazione > Opzioni globali... sotto il tab "Altro" +puoi definire l'editor che preferisci. +Ricorda, se vuoi usare un editor a linea di comando (non grafico) tipo vi o emacs, +devi precedere il nome dell'editor con il terminale su cui eseguirlo +(term, term, rxvt) col parametro -e. Esempio: rxvt -e vi %s +

3.5 Q05 Come posso cambiare la dimensione del font nell'interfaccia di Sylpheed? +

+ +

A. Puoi settare il font del GTK+ con ~/.gtkrc, o +~/.gtkrc.mine, +(che è incluso in ~/.gtkrc). +Per esempio: +style "default" +{ +font = +"-adobe-helvetica-medium-r-normal--12-*-*-*-*-*-iso8859-1 +" +} +widget_class "*" style "default" +

3.6 Q06 Sylpheed salva le mie mail in uscita (in Outbox). Posso fermare questa opzione? +

+ +

A. In Configurazione > Opzioni globali... sotto il tab "Invia" c'è +l'opzione "Salva i messaggi inviati nella cartella 'In Uscita'". +Deseleziona l'opzione e risolvi il tuo quesito. +

3.7 Q07 Come posso cambiare la mappa dei tasti (tasti veloci) in Sylpheed? +

+ +

A. E' molto semplice. Supponi che vuoi assegnare una sequenza di tasti ad +una funzione, esempio spedire tutte i messaggi accodati premendo Ctrl-Y. +Seleziona il menu "Messaggio", posiziona il mouse sulla voce "Invia i messaggi +accodati". Ora premi Ctrl-Y. Immediatamente il menu viene aggiornato con +la modifica effettuata. ATTENZIONE: verifica che la sequenza di tasti non già +assegnata prima di fare ciò. Se vuoi rimuovere il settaggio, fai la stessa cosa, +ma premi il tasto "delete" sulla voce del menu. Questo rimuovera la sequenza di +tasti veloce assegnata a quella voce. +

3.8 Q08 Posso chiudere Sylpheed senza utilizzare il mouse? +

+ +

A. Certamente!! Non tutte le finestre, ma premendo il tasto ESCape, +puoi chiudere la rubrica, la finestra di visualizzazione del messaggio sorgente +(Vista>Vista sorgente), la finestra di visualizza delle intestazioni e molte +altre. Fai una prova e troverai quali delle finestre di Sylpheed funzionano allo +stesso modo. +

3.9 Q09 Posso cambiare il modo di visualizzazione della data nel sommario dei messaggi? +

+ +

A. Dalla versione 0.4.65 si può. Per avere una lista completa delle opzioni +vai al menu Configurazione, seleziona Opzioni globali, tab Visualizzazione e +il tasto vicino al box "Formato della Data". +

3.10 Q10 Perché non posso vedere l'immagine compface? +

+ +

A. Devi abilitare la visualizzzione del pannello intestazioni nelle opzioni +globali. +

3.11 Q11 Continuo a non vederla. Perché? +

+ +

A. Non hai compilato Sylpheed col support Compface. Leggi Q11 +nella sezione Installazione e Configurazione. +

3.12 Q12 Perché l'URL Launcher non apre il web browser che ho definito? +

+ +

A. Devi fare un doppio click sull'URL. +

3.13 Q13 Gli allegati con spazi nel nome non si aprono! +

+ +

A. Quando provi ad eseguire un'applicazione di supporto, tipo un visualizzatore +di immagini, con l'allegato che ha spazi nel nome del file, metti la virgoletta +singola attorno al parametro %s. Esempio: xv '%s' +

+Precedente +Contenuti +Successivo + + diff --git a/faq/it/sylpheed-faq.html b/faq/it/sylpheed-faq.html new file mode 100644 index 0000000..477821e --- /dev/null +++ b/faq/it/sylpheed-faq.html @@ -0,0 +1,103 @@ + + + + + Sylpheed FAQ + + + + + +Precedente +Contenuti +Successivo +
+

Sylpheed FAQ

+ + +

Paul Kater (paul@nlpagan.net) + e Jens Oberender (j.obi@troja.net) +

+

+ Sylpheed FAQ (per la versione 0.7.3) + +
+

Queste FAQ consistono delle seguenti sezioni: +

+

1. Sylpheed FAQ - Informazioni Generali

+ + +

+

2. Sylpheed FAQ - Installatione e Configurazione

+ + +

+

3. Sylpheed FAQ - Interfaccia

+ + +
+Precedente +Contenuti +Successivo + + -- cgit v1.3