-<?xml version="1.0" encoding="utf-8" standalone="no"?>
+<?xml version="1.0" encoding="utf-8"?>
<section id="ch_advanced">
<title>Advanced features</title>
<section id="adv_actions">
<para>
Actions allow you to use all the power of the Unix command-line with your emails. You can define various commands, taking parameters such as the current email file, a list of emails, the currently selected text, and so on. In this way, you'll be able to perform various tasks such as editing a raw mail in your text editor, "hide" what you mean using ROT-13, apply patches contained in emails directly, and so on. The only limit is your imagination. You can configure Actions via the Tools menu.
</para>
+ <blockquote>
+ <example><title>Simple <quote>Open With...</quote></title>
+ <variablelist>
+ <varlistentry><term>Menu name: <emphasis>Open with/kate</emphasis> Command Line: <emphasis>kate %p</emphasis></term>
+ <listitem><para>Opens the file of the selected decoded MIME part (<emphasis>%p</emphasis>) with the <emphasis>kate</emphasis> text editor.
+ </para></listitem>
+ </varlistentry>
+ </variablelist>
+ </example>
+ <example><title>Spam management using <ulink url="http://bogofilter.sourceforge.net/">Bogofilter</ulink></title>
+ <variablelist>
+ <varlistentry><term>Menu name: <emphasis>Bogofilter/Mark as Ham</emphasis> Command Line: <emphasis>bogofilter -n -v -B "%f"</emphasis></term>
+ <listitem><para>Marks the currently selected mails (<emphasis>%f</emphasis>) as 'not spam' using <emphasis>Bogofilter</emphasis>.
+ </para></listitem>
+ </varlistentry>
+ <varlistentry><term>Menu name: <emphasis>Bogofilter/Mark as Spam</emphasis> Command Line: <emphasis>bogofilter -s -v -B "%f"</emphasis></term>
+ <listitem><para>Marks the currently selected mails (<emphasis>%f</emphasis>) as 'spam' using <emphasis>Bogofilter</emphasis>.
+ </para></listitem>
+ </varlistentry>
+ </variablelist>
+ </example>
+ <example><title>Search Google using an external script</title>
+ <variablelist>
+ <varlistentry><term>Menu name: <emphasis>Search/Google</emphasis> Command Line: <emphasis>|/path/to/google_search.pl</emphasis></term>
+ <listitem><para>Searches Google for the currently selected text (<emphasis>|</emphasis>) using the external script <emphasis><ulink url="http://claws.sylpheed.org/tools.php">google_search.pl</ulink></emphasis>.
+ </para></listitem>
+ </varlistentry>
+ </variablelist>
+ </example>
+ </blockquote>
</section>
<section id="adv_templates">
<title>Templates</title>
<para>
- Templates are used in Composition windows, and are a sort of "model" letters. Templates can be filled with static text and dynamic parts, such as the original sender's name ("Dear %N, ..."), the date, ... When applying a template, the dynamic fields will be replaced with the relevant values. You can configure templates via the Tools menu.
+ Templates are used in composition windows, and act as a model for emails. Templates can be filled with static text and dynamic parts, such as the original sender's name ("Dear %N, ..."), the date, etc. When applying a template, the dynamic fields will be replaced with the relevant values. You can configure templates via the Tools menu.
</para>
- </section>
+ <para>
+ When applying a template, you will be asked to <quote>Insert</quote> or <quote>Replace</quote>, the difference between replacing and inserting is only concerned with the message body. <quote>Replace</quote> will replace the current composition window message body with the body defined in the template, clearing it if the template body is empty. <quote>Insert</quote> will insert the template's body, if set, at the current cursor position.
+ </para>
+ <para>
+ Whether you choose to Insert or Replace, any To, Cc or Bcc field that is defined in the template will be appended to the compose window's recipients list. If it is defined, the template's Subject will always replace the compose window's Subject.
+ </para>
+ <para>
+ Symbols can be used in all parts of the templates and will be substituted with their respective dynamic value if possible, otherwise no value will be used. This often makes more sense if you apply a template when a replying or forwarding. There is no restriction on which symbols can be used in template parts, even if inserting the body (%M or %Q) may make no sense in common situations.
+ </para>
+ <para>
+ When applying a template, the body is processed first, then the To, Cc, Bcc and Subject fields follow.
+ </para>
+ <para>
+ Further information and examples of usage can be found in the user-contributed FAQ on the Sylpheed-Claws website <ulink url="http://claws.sylpheed.org/faq.php">http://claws.sylpheed.org/faq.php</ulink>
+ </para>
+ </section>
<section id="adv_processing">
<title>Processing</title>
<para>
- Processing rules are the same as Filtering rules, except that they are applied when entering a folder and apply only to this folder. You can use them to automatically move old mails into an archive folder, or for further dispatching of emails. You can set each folder's Processing rules by right-clicking on it.
+ Processing rules are the same as Filtering rules, except that they are applied when entering a folder and apply only to this folder. You can use them to automatically move old mails into an archive folder, or for further dispatching of emails, and more. You can set each folder's Processing rules by right-clicking on it.
</para>
<para>
- Processing rules are accompanied by Preprocessing and Postprocessing rules. Like Processing rules, they apply only when opening a folder, but like Filtering rules, they are shared accross all folders. You can configure them from the Tools menu.
+ Processing rules are accompanied by Pre-processing and Post-processing rules. Like Processing rules, they apply only when opening a folder, but like Filtering rules, they are shared accross all folders. You can configure them from the Tools menu. Pre-processing rules are executed before the folder's specific Processing rules, while Post-processing rules are executed afterwards.
</para>
</section>
+ <section id="adv_colour_labels">
+ <title>Colour Labels</title>
+ <para>
+ Colour labels can be used to denote a message as having a particular significance. To set a colour label simply right-click a message in the Message List and use the <quote>Colour label</quote> submenu.
+ </para>
+ <para>
+ Colour labels are user-configurable. Both the colour and the label can be set by the user. Preferences can be found on the <quote>Configuration/Preferences/Display/Colours</quote> page.
+ </para>
+ </section>
<section id="adv_plugins">
<title>Plugins</title>
<para>
- Plugins are the mechanism of extending Sylpheed-Claws capabilities. Imagine you want to store your mails in a remote <acronym>SQL</acronym> database. In most mailers out there this is simply impossible without reworking the internals of it. With Sylpheed-Claws you can simply write a plugin to achieve the task.
+ Plugins are the mechanism for extending Sylpheed-Claws' capabilities. For example, imagine that you want to store your mails in a remote <acronym>SQL</acronym> database. In most mailers out there this is simply impossible without reworking the internals of the mailer. With Sylpheed-Claws you can simply write a plugin to achieve the task.
</para>
<para>
- This is only an example of the possibilities. Already exist a good number of plugins developed for Sylpheed-Claws, and more are to come. The <link linkend="ch_plugins">Extending Sylpheed-Claws section</link> is devoted to all of them.
+ This is just an example of the possibilities. A good number of plugins developed for Sylpheed-Claws already exist, and more are to come. The <link linkend="ch_plugins">Extending Sylpheed-Claws section</link> gives details of them.
</para>
</section>
<section id="adv_hidden">
<title>Hidden preferences</title>
<para>
- There are a number of hidden preferences in Sylpheed-Claws, preferences that some users we wanted to please couldn't live without, but which did not had a place in the GUI in our opinions. You can find the following, and change them while Sylpheed-Claws is not running in ~/.sylpheed-claws/sylpheedrc.
+ There are a number of hidden preferences in Sylpheed-Claws, preferences that some users who we wanted to please couldn't live without, but which did not have a place in the GUI in our opinion. You can find the following, and change them while Sylpheed-Claws is not running in ~/.sylpheed-claws/sylpheedrc.
</para>
<variablelist>
<varlistentry><term>bold_unread</term>
<listitem><para>show unread messages using bold font in summary view</para></listitem>
</varlistentry>
- <varlistentry><term>color_new</term>
- <listitem><para>color (as hex triplet) of folder name when indicating new messages</para></listitem>
- </varlistentry>
<varlistentry><term>cache_max_mem_usage</term>
<listitem><para>the maximum amount of memory to use to cache messages, in kB.</para></listitem>
</varlistentry>
<listitem><para>specify the policy of vertical scroll bar of folder view</para></listitem>
</varlistentry>
<varlistentry><term>hover_timeout</term>
- <listitem><para>time in milliseconds that will cause a folder tree to expand during drag n drop when the mouse cover is held over it</para></listitem>
+ <listitem><para>time in milliseconds that will cause a folder tree to expand during drag 'n' drop when the mouse cover is held over it</para></listitem>
</varlistentry>
<varlistentry><term>statusbar_update_step</term>
<listitem><para>update stepping in progress bars</para></listitem>
<listitem><para>use UTF-8 encoding for broken mails instead of current locale</para></listitem>
</varlistentry>
<varlistentry><term>warn_dnd</term>
- <listitem><para>display a confirmation dialog on drag n drop of folders</para></listitem>
+ <listitem><para>display a confirmation dialog on drag 'n' drop of folders</para></listitem>
</varlistentry>
</variablelist>
</section>
projects / claws.git / blobdiff