summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorpknbe <pknbe>2010-08-08 22:35:32 +0000
committerpknbe <pknbe>2010-08-08 22:35:32 +0000
commit7051e387fca1d4b6b871ee69c5172f3d916e73b4 (patch)
tree933ddb5771135a095580a58857586895854fe35d
parente0f0562dfad7ed517ca074e5beea97972e8a4990 (diff)
downloadsylpheeddoc-doc-7051e387fca1d4b6b871ee69c5172f3d916e73b4.zip
sylpheeddoc-doc-7051e387fca1d4b6b871ee69c5172f3d916e73b4.tar.gz
sylpheeddoc-doc-7051e387fca1d4b6b871ee69c5172f3d916e73b4.tar.xz
Second round of updates with regard to Sylpheed 3.1.
-rw-r--r--faq/en/ChangeLog7
-rw-r--r--faq/en/faq.xml6
-rw-r--r--faq/en/faq_001.xml36
-rw-r--r--faq/en/faq_002.xml4
-rw-r--r--faq/en/faq_003.xml16
5 files changed, 57 insertions, 12 deletions
diff --git a/faq/en/ChangeLog b/faq/en/ChangeLog
index 9baac8a..a54b662 100644
--- a/faq/en/ChangeLog
+++ b/faq/en/ChangeLog
@@ -1,3 +1,10 @@
+2010-08-09 Petr Kovar <pknbe@volny.cz>
+
+ * 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 <pknbe@volny.cz>
* faq_001.xml: Some fixes to the recent updates.
diff --git a/faq/en/faq.xml b/faq/en/faq.xml
index f9dbc6d..5fa63f0 100644
--- a/faq/en/faq.xml
+++ b/faq/en/faq.xml
@@ -83,6 +83,12 @@
<authorinitials>PK</authorinitials>
<revremark>Updated with regard to Sylpheed 3.0.2.</revremark>
</revision>
+ <revision>
+ <revnumber>2.2</revnumber>
+ <date>2010/08/09</date>
+ <authorinitials>PK</authorinitials>
+ <revremark>Updates for the upcoming Sylpheed 3.1.</revremark>
+ </revision>
<!-- ******************************************************************************** --> </revhistory>
</bookinfo>
&__faq__001;&__faq__002;&__faq__003;&__license;</book>
diff --git a/faq/en/faq_001.xml b/faq/en/faq_001.xml
index 154ed34..2b2880f 100644
--- a/faq/en/faq_001.xml
+++ b/faq/en/faq_001.xml
@@ -227,25 +227,32 @@ and/or procmail, and external programs on receiving (like inc or imget).</para>
</qandaentry>
<qandaentry>
<question id="faq-completion-adress-sylpheed">
- <para>Does Sylpheed have name completion in the address fields?
+ <para>Does Sylpheed have automatic name completion in the address fields?
</para>
</question>
<answer>
<para>
Yes. When you search for a name that starts with &quot;<literal>don</literal>&quot;,
- type &quot;<literal>don</literal>&quot; (without the quotes) and press the <keycap>Tab</keycap> key.
- This will show you the correct name (when only one &quot;don&quot;
+ type &quot;<literal>don</literal>&quot; (without the quotes) and it will show you the correct name (when only one &quot;don&quot;
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 &quot;<literal>don</literal>&quot; will appear in the list (like
- &quot;<literal>don.giovanni@maffia.org</literal>&quot;).
- </para>
+ &quot;<literal>don.giovanni@maffia.org</literal>&quot;).</para>
+ <para>Prior to Sylpheed 3.1, user needed to press the <keycap>Tab</keycap> key before the search would start. If you still prefer the previous behavior instead, you can enable it by checking <menuchoice>
+ <guimenu>Configuration</guimenu>
+ <guimenuitem>Common preferences...</guimenuitem>
+ <guimenuitem>Details</guimenuitem>
+ <guimenuitem>Other</guimenuitem>
+ <guisubmenu>Address book</guisubmenu>
+ <guilabel>Address auto-completion:</guilabel>
+ <guilabel>Start with Tab</guilabel>
+ </menuchoice>.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="faq-tab-error-sylpheed">
- <para>Fine, but when I hit the Tab key I get an error message.
+ <para>Fine, but when I hit the Tab key I get an error message or nothing happens at all.
</para>
</question>
<answer>
@@ -253,8 +260,16 @@ and/or procmail, and external programs on receiving (like inc or imget).</para>
When you want to use name completion, make sure that
there are names in your address book. If there are no
names, even Sylpheed has a hard time completing
- something.
- </para>
+ something.</para>
+ <para>If nothing happens at all when typing text in the address fields, make sure that you have the address auto-completion enabled by checking that the following preference is not selected: <menuchoice>
+ <guimenu>Configuration</guimenu>
+ <guimenuitem>Common preferences...</guimenuitem>
+ <guimenuitem>Details</guimenuitem>
+ <guimenuitem>Other</guimenuitem>
+ <guisubmenu>Address book</guisubmenu>
+ <guilabel>Address auto-completion:</guilabel>
+ <guilabel>Disabled</guilabel>
+ </menuchoice>.</para>
</answer>
</qandaentry>
<qandaentry>
@@ -501,7 +516,8 @@ sylpheedmail/.
<para>Are there any plug-ins extending standard Sylpheed functionality?</para>
</question>
<answer>
- <para>Not yet, but they are planned, since Sylpheed 3.0, released in early 2010, and later supports a plug-in interface. In the future, some of the Sylpheed features will be re-implemented as plug-ins, and, moreover, various other plug-ins will be released.</para>
+ <para>As of Sylpheed 3.1, there is an Attachment Tool Plug-in distributed with the Sylpheed source code and available under <filename>plugin/attachment_tool/</filename>. Its only function is to remove attachments from
+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.</para>
<para>There is a page on the Sylpheed website dedicated to the <ulink url="http://sylpheed.sraoss.jp/en/plugin.html">plug-in interface</ulink>. Additionally, the <filename>PLUGIN.txt</filename> file distributed directly with Sylpheed can provide you with some basic information on the topic.</para>
<note>
<para>If you are a developer interested in creating plug-ins for Sylpheed, see the <ulink url="http://sylpheed.sraoss.jp/wiki/index.php?PluginSpec">plug-in specification</ulink> on the Sylpheed wiki.</para>
@@ -538,7 +554,7 @@ sylpheedmail/.
<para>The source DocBook XML files in which this document is written can be obtained from a <ulink url="http://sylpheeddoc.cvs.sourceforge.net/sylpheeddoc/">public CVS repository</ulink> that is part of the <ulink url="http://sylpheeddoc.sourceforge.net/">Sylpheed Documentation Project</ulink>. The source files with all the necessary build system, XSL stylesheets or snapshots are stored under the &quot;<ulink url="http://sylpheeddoc.cvs.sourceforge.net/viewvc/sylpheeddoc/doc/">doc</ulink>&quot; module in the CVS repository and can be checked out through anonymous CVS with the following commands (simply press Enter when prompted for a password):</para>
<para><command>cvs -d:pserver:anonymous@sylpheeddoc.cvs.sourceforge.net:/cvsroot/sylpheeddoc login</command></para>
<para><command>cvs -z3 -d:pserver:anonymous@sylpheeddoc.cvs.sourceforge.net:/cvsroot/sylpheeddoc co -P doc</command></para>
- <para>The source files are also included in .tar.gz and .zip archives made available with each documentation release, these can be downloaded from the <ulink url="http://sourceforge.net/projects/sylpheeddoc/files/">appropriate project page</ulink>. For more information on the used project infrastructure, please the <ulink url="http://sylpheeddoc.sourceforge.net/en/tools.html">project website</ulink>.</para>
+ <para>The source files are also included in .tar.gz and .zip archives made available with each documentation release, these can be downloaded from the <ulink url="http://sourceforge.net/projects/sylpheeddoc/files/">appropriate project page</ulink>. For more information on the used project infrastructure, please see the <ulink url="http://sylpheeddoc.sourceforge.net/en/tools.html">project website</ulink>.</para>
</answer>
</qandaentry>
<qandaentry>
diff --git a/faq/en/faq_002.xml b/faq/en/faq_002.xml
index 381dc26..58da0f3 100644
--- a/faq/en/faq_002.xml
+++ b/faq/en/faq_002.xml
@@ -467,7 +467,7 @@ mail checks.</para>
<para><envar>LC_MESSAGES</envar> - locale settings, e.g. language and date format.</para>
</listitem>
</itemizedlist>
- <para>For more information on how to make Sylpheed display your language, see the <link linkend="faq-display-language">relevant question</link>. </para>
+ <para>For more information on how to make Sylpheed display your language, see the <link linkend="faq-display-language">relevant question</link>.</para>
</answer>
</qandaentry>
<qandaentry>
@@ -603,4 +603,4 @@ socket (under UNIX), or mutex name (under Windows). <parameter>configdir</parame
</answer>
</qandaentry>
</qandaset>
-</chapter> \ No newline at end of file
+</chapter>
diff --git a/faq/en/faq_003.xml b/faq/en/faq_003.xml
index e86596c..8410a2a 100644
--- a/faq/en/faq_003.xml
+++ b/faq/en/faq_003.xml
@@ -246,6 +246,22 @@ parameter. Example: <command>gedit &apos;%s&apos;</command></para>
</qandaentry>
<qandaentry>
<question>
+ <para>Execute command for my dynamic signature seems not to be working!</para>
+ </question>
+ <answer>
+ <para>Under Windows, if you have created e.g. a simple batch file to echo a line to be included in your dynamic signature, you need to execute the command (specified under <menuchoice>
+ <guimenu>Account preferences</guimenu>
+ <guisubmenu>Compose</guisubmenu>
+ <guimenuitem>Signature</guimenuitem>
+ <guilabel>Command output</guilabel>
+ </menuchoice>) using either forward slashes or double
+backslashes for paths, for example:</para>
+ <para><command>cmd /c &apos;c:\\signature.bat&apos;</command></para>
+ <para>Note that it is also recommended to enclose paths with single quotes, as is illustrated above.</para>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
<para>Where is the Bcc when I compose a mail?</para>
</question>
<answer>