/usr/share/help/cs/evolution/mail-composer-message-templates-variables.page is in evolution-common 3.12.9~git20141130.241663-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 | <?xml version="1.0" encoding="utf-8"?>
<page xmlns="http://projectmallard.org/1.0/" xmlns:its="http://www.w3.org/2005/11/its" type="topic" id="mail-composer-message-templates-variables" xml:lang="cs">
<info>
<desc>Configure variables in templates and reuse items from the message you reply to</desc>
<link type="guide" xref="mail-composer-message-templates#options"/>
<revision pkgversion="3.5.90" version="0.3" date="2012-08-17" status="draft"/>
<credit type="author">
<name its:translate="no">Andre Klapper</name>
<email its:translate="no">ak-47@gmx.net</email>
</credit>
<credit type="author">
<name its:translate="no">Novell, Inc</name> <!-- Content partially from http://library.gnome.org/users/evolution/2.32/b1dlaazl.html.en -->
</credit>
<include xmlns="http://www.w3.org/2001/XInclude" href="legal.xml"/>
</info>
<title>Using Variables in Templates</title>
<section id="configure">
<title>Configuring Variables for Message Templates</title>
<steps>
<item><p>Select <guiseq><gui>Edit</gui><gui>Plugins</gui></guiseq>.</p></item>
<item><p>Click <gui>Templates</gui>.</p></item>
<item><p>Click the <gui>Configuration</gui> tab.</p></item>
<item><p>You can add, edit or remove the key-value pairs. You can specify any number of key-value pairs.</p></item>
</steps>
<p>V kterékoliv šabloně je výskyt $klíč nahrazen hodnotou, kterou má v nastavení. Například nastavíte klíčové slovo na manažer a hodnotu na Jindra, jakýkoliv výskyt $manažer je nahrazen ve zprávě výrazem Jindra. </p>
<p>Assume that you have 1000 message templates with your current manager's name in them. When the current manager is replaced by a new one, it is not easy for you to manually replace the manager's name in all the 1000 messages. If the messages have a $Manager key value, you can reset the value in the Configuration tab of this plugin.</p>
<p>Ve výchozím stavu jsou proměnné celého prostředí použity jako páry klíčových hodnot. Výskyt $env_variable je nahrazen hodnotou, kterou nese. Například výskyt $PATH ve vaší šabloně je nahrazen hodnotou, když je šablona použita.</p>
<p>Proces nahrazování používá následující pořadí priorit:</p>
<steps>
<item>
<p>$klíč je nahrazen hodnotou mu přiřazenou na kartě Nastavení zásuvného modulu Šablona.</p>
</item>
<item>
<p>Pokud není klíč nalezen, je nahrazen hodnotou proměnné z prostředí.</p>
</item>
<item>
<p>Pokud není klíč ani volbou v nastavení, ani proměnnou v prostředí, žádné změny neproběhnou.</p>
</item>
</steps>
</section>
<!-- as per https://bugzilla.gnome.org/show_bug.cgi?id=641845 - available since 3.2-->
<section id="reply-variables">
<title>Using Elements From a Message in a Template When Replying</title>
<p>Templates can contain more than just the predefined set of <link xref="#configure">key-value pairs</link>. You can also get any message header values from the email that you are applying the template on, plus the complete message body.</p>
<!-- TRANSLATORS: Do NOT translate "$ORIG[subject]" and "$ORIG[body]" in this sentence. -->
<p its:locNote="TO TRANSLATORS: Do NOT translate $ORIG[subject] and $ORIG[body] in this sentence!">In order to do this, use the format <code>$ORIG[header_name]</code> and replace the variable <code>header_name</code> by the actual header. For example, if you would like to insert the subject line of the message that you reply to, use <code>$ORIG[subject]</code>. To insert the complete body, use <code>$ORIG[body]</code>.</p>
<!-- TRANSLATORS: Do NOT translate "$ORIG[body]" and "$ORIG[reply-to]" in this sentence. -->
<p its:locNote="TO TRANSLATORS: Do NOT translate $ORIG[body] and $ORIG[reply-to] in this sentence!">If no replacement for a variable is found, the variable is not removed (except for <code>$ORIG[body]</code>) but left in place so that you see that something went wrong. This could happen when trying to use headers that are not necessarily always available in the original message (for example <code>$ORIG[reply-to]</code>).</p>
</section>
</page>
|