From 8c7605b0271308459bdbbcdb45d52a94ee1d0589 Mon Sep 17 00:00:00 2001 From: pknbe Date: Sun, 8 Aug 2010 23:58:55 +0000 Subject: NEWS: Prepare for the FAQ_EN_2_2 release. faq_001.xml: Minor fixes. faq_003.xml: Ditto. --- faq/en/ChangeLog | 6 ++++++ faq/en/NEWS | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ faq/en/faq_001.xml | 10 +++++----- faq/en/faq_003.xml | 6 +++--- 4 files changed, 65 insertions(+), 8 deletions(-) (limited to 'faq') diff --git a/faq/en/ChangeLog b/faq/en/ChangeLog index a54b662..b7bb11a 100644 --- a/faq/en/ChangeLog +++ b/faq/en/ChangeLog @@ -1,3 +1,9 @@ +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. diff --git a/faq/en/NEWS b/faq/en/NEWS index 0f12680..63b3d86 100644 --- a/faq/en/NEWS +++ b/faq/en/NEWS @@ -1,3 +1,54 @@ +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 ================================================ diff --git a/faq/en/faq_001.xml b/faq/en/faq_001.xml index 2b2880f..802b6cd 100644 --- a/faq/en/faq_001.xml +++ b/faq/en/faq_001.xml @@ -239,7 +239,7 @@ and/or procmail, and external programs on receiving (like inc or imget). 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, user needed to press the Tab key before the search would start. If you still prefer the previous behavior instead, you can enable it by checking + 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 @@ -252,7 +252,7 @@ and/or procmail, and external programs on receiving (like inc or imget). - Fine, but when I hit the Tab key I get an error message or nothing happens at all. + Fine, but when I hit the Tab key I either get an error message or nothing happens at all. @@ -516,9 +516,9 @@ sylpheedmail/. 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 + 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. + 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. @@ -588,4 +588,4 @@ Frank Weng fweng at users.sourceforge.net - \ No newline at end of file + diff --git a/faq/en/faq_003.xml b/faq/en/faq_003.xml index 8410a2a..7fded96 100644 --- a/faq/en/faq_003.xml +++ b/faq/en/faq_003.xml @@ -249,7 +249,7 @@ 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 + 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 @@ -257,7 +257,7 @@ parameter. Example: gedit '%s' ) 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. + Note that it is also recommended to enclose paths with single quotes, as is illustrated above. @@ -306,4 +306,4 @@ backslashes for paths, for example: - \ No newline at end of file + -- cgit