Commit 0774406d authored by Patrick Brunschwig's avatar Patrick Brunschwig

added Scottish Gaelic (gd) locale

parent 1fdc3ad3
......@@ -7,6 +7,7 @@ el
es-ES
fi
fr
gd
gl
hu
it
......
# used in the AccountManager
prefPanel-enigprefs=Tèarainteachd OpenPGP
This diff is collapsed.
This diff is collapsed.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Enigmail Help: Message Composition</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
<style type="text/css">
/*<![CDATA[*/
dt { font-weight: bold; }
/*]]>*/
</style>
</head>
<body>
<h1>Enigmail Help</h1>
<h3>Using Enigmail when composing messages</h3>
<dl>
<dt>Enigmail menu in Mail/Compose window</dt>
<dd>
<dl>
<dt>Sign message</dt>
<dd>Enable/Disable sending signed mail. User is notified, if signing fails.</dd>
<dt>Encrypt message</dt>
<dd>
<p>Enable/Disable encryption to all recipient(s) before sending. User is notified, if encryption fails.</p>
<p>If <em>Display selection when necessary</em> is set in <strong>Preferences -&gt; Key Selection tab</strong>, a list of keys will pop up if there are addresses in the list of recipients for the message for whom you have no public key.</p>
<p>If <em>Never display OpenPGP key selection dialog</em> is set in <strong>Preferences -&gt; Key Selection tab</strong>, and there are addresses in the list of recipients for the message for whom you have no public key, the message will be sent unencrypted.</p>
</dd>
<dt>Use PGP/MIME for this message</dt>
<dd>
Enable/Disable the use of <a href="http://www.ietf.org/rfc/rfc3156.txt">PGP/MIME</a> for this message.
<p>If you know the recipient(s) can read mail using the PGP/MIME format, you should use it.</p>
<p>This feature is dependent on the settings in <strong>Preferences -&gt; PGP/MIME tab</strong> being set to <em>Allow to use PGP/MIME</em> or <em>Always use PGP/MIME</em>.</p>
</dd>
<dt>Default composition options</dt>
<dd>
<ul>
<li><strong>Signing/Encryption Options...</strong>: shortcut to <strong>Account Settings -&gt; OpenPGP Options.</strong></li>
<li><strong>Send options...</strong>: shortcut to <strong>Preferences -&gt; Send</strong> tab.</li>
<li><strong>Key selection options...</strong>: shortcut to <strong>Preferences -&gt; Key Selection</strong> tab.</li>
<li><strong>PGP/MIME options...</strong>: shortcut to <strong>Preferences -&gt; PGP/MIME</strong> tab.</li>
</ul>
</dd>
<dt>Undo encryption</dt>
<dd>
<p>If there is a failure when actually sending mail, such as the POP server not accepting the request, Enigmail will not know about it, and the encrypted message will continue to be displayed in the Compose window. Choosing this menu item will undo the encryption/signing, reverting the Compose window back to its original text.</p>
<p><em>As a temporary fix, this option may also be used to decrypt the quoted text when replying to encrypted messages. Enigmail should automatically decrypt the quoted message, but if that fails for some reason, you can use this menu item to force it.</em></p>
</dd>
<dt>Insert public key</dt>
<dd>insert ASCII-armored public key block at the current cursor location in the Compose window. You will be prompted for the email addresses of the key(s) to be inserted. Keys inserted in this manner will automatically be recognized at the receiving end by Enigmail. After key insertion, you may still choose to sign/encrypt the mail as needed. Also, do not insert more than one key block in a message; just specify multiple email addresses, separated by commas or spaces, when prompted.</dd>
<dt>Clear save passphrase</dt>
<dd>Clears cached passphrase. Useful if you have multiple passphrases.</dd>
<dt>Help</dt>
<dd>Displays Help information from the website (this page).</dd>
</dl>
</dd>
</dl>
<hr />
<p>Further help is available on the <a href="http://www.enigmail.net/support/">Enigmail Help web page</a></p>
</body>
</html>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Enigmail Help: Edit Per-Recipient Rule</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
<style type="text/css">
/*<![CDATA[*/
dt { font-weight: bold; }
/*]]>*/
</style>
</head>
<body>
<h1>Enigmail Help</h1>
<h3>Using the Enigmail Rules Editor: Edit Per-Recipient Rule</h3>
<p>In the Rules Editor, you can specify defaults per recipient for enabling encryption, signing and PGP/MIME, and to define what OpenPGP key(s) to use. In this dialog, you can specify the rules for a single recipient, and for a group of recipients with very similar attributes.</p>
<dl>
<dt>Set Enigmail Rules for</dt>
<dd>Contains the email addresses of the recipients (without names, i.e. just an address like <tt>somebody@email.domain</tt>). You can specify several email addresses, separated by spaces. The address specified here can consist of only the domain section so that mail to any address at that domain will be matched, e.g. <tt>@email.domain will</tt> allow matching to <tt>body@email.domain</tt>, <tt>somebody@email.domain</tt>, <tt>anybody@email.domain</tt>, etc.</dd>
<dt>Apply rule if recipient ...</dt>
<dd>
This modifies the matching of the email addresses. If multiple addresses are entered, the setting will apply to all. The examples below are based on <tt>body@email.domain</tt> entered in the <em>Enigmail Rules</em> field above.
<ul>
<li><em>Is exactly</em>: with this setting, the rule will only trigger on emails to <tt>body@email.domain</tt> (exact, case insensitive matching).</li>
<li><em>Contains</em>: with this setting, any email address containing the string is matched, e.g. <tt>anybody@email.domain</tt> or <tt>body@email.domain.net</tt></li>
<li><em>Begins with</em>: with this setting, any email address starting with the string is matched, e.g. <tt>body@email.domain.net</tt>, <tt>body@email.domain-name.com</tt>.</li>
<li><em>Ends with</em>: with this setting, any email address ending with the string is matched, e.g. <tt>anybody@email.domain</tt> , <tt>somebody@email.domain</tt>.</li>
</ul>
</dd>
<dt>Continue with the next rule for the matching address</dt>
<dd>Enabling this function will allow you to define a rule but not have to specify a KeyID in the <em>Use the following OpenPGP keys:</em> field, so that the email address is used to check for a key at the time of sending. Also, further rules for the same address(es) will be processed as well.</dd>
<dt>Do not check further rules for the matching address</dt>
<dd>Enabling this function stops processing any other rules for the matching address(es) if this rule is matched; i.e. rule processing continues with the next recipient.</dd>
<dt>Use the following OpenPGP keys:</dt>
<dd>Use the <em>Select Key(s)..</em> button to select the recipient keys to be used for encryption. As in the action above, no further rules for the matching address(es) are processed.</dd>
<dt>Default for Signing</dt>
<dd>
Enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
<ul>
<li><em>Never</em>: disable signing, even if it was enabled in the message composition window (overrules the other values)</li>
<li><em>Yes, if selected from in Message Composition</em>: leave signing as specified in the message composition window</li>
<li><em>Always</em>: enable signing, even if it was <span style="font-style: italic;">not</span> enabled in the message composition window</li>
</ul>These signing settings are applied for all rules that match. If one of the rules disables signing, the message will not be signed, regardless of other rules that specify <em>Always</em>.
</dd>
<dt>Encryption</dt>
<dd>Enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.</dd>
<dt>PGP/MIME</dt>
<dd>Enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning are the same as for message signing.</dd>
</dl>
<p>The rules are processed in the order displayed in the list in the <em>Per-Recipient Rules Editor</em>. Whenever a rule matches a recipient and contains a OpenPGP Key ID, in addition to using the specified Key ID, the recipient is not considered anymore when processing further rules.</p>
<hr />
<p>Further help is available on the <a href="http://www.enigmail.net/documentation/pgprules_file.php" target="_blank">Enigmail Per-Recipient Settings page</a></p>
</body>
</html>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
<title>Enigmail Help</title>
</head>
<body>
<h1>Enigmail Help</h1>
<h3>Using Enigmail when reading messages</h3>
<ul>
<li><b>Decrypt button in main Mail window</b><br />
This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command. </li>
<li><b>Pen and Key icons in Message Header display</b><br />
The <em>Pen</em> and <em>Key</em> icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the <em>Pen</em> icon will change to a <em>Broken Pen</em> to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
<ul>
<li><em>Enigmail Security info</em>: allows you to view the output status from GnuPG for the message.</li>
<li><em>Copy Enigmail Security info</em>: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.</li>
<li><em>View OpenPGP Photo ID</em>: allows you to view the <em>Photo ID</em> of the person who sent the message, if they have a photo embedded in their Public Key. (<em>This option will only be enabled if a Photo ID exists in their key.)</em></li>
<li><em>S/MIME Security info</em>: allows you to view the S/MIME Security Info for the message.</li>
</ul>
<p>If you do not have <em>keyserver-options auto-key-retrieve</em> set in your <tt>gpg.conf</tt> file and you read a message which is signed or encrypted, you will see a <em>Pen</em> icon in the headers display area with a <em>Question mark</em> on it, the Enigmail status line in the headers area will say <em>Part of the message signed; click pen icon for details</em> and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.</p>
<p>You may also see this if you have <em>keyserver-options auto-key-retrieve</em> set in your <tt>gpg.conf</tt> file and the OpenPGP key is not available on the default keyserver.</p>
<p>Clicking on the <em>Pen and Question mark</em> icon will bring up a window advising that the key is unavailable in your keyring. Clicking on OK will bring up another window with a list of keyservers from which you can select to download the sender's public key from.</p>
<p>To configure the list of keyservers you wish to use, go to <b>Enigmail -&gt; Preferences -&gt; Basic</b> tab and enter the keyserver addresses in the <em>Keyserver(s):</em> box, separated by a comma. <em>The first keyserver in the list will be used as the default.</em></p>
</li>
<li><b>Opening encrypted attachments / importing attached OpenPGP keys</b><br />
Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: <em>Decrypt and Open</em> and <em>Decrypt and Save</em>. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings. </li>
</ul>
<hr />
<p> Further help is available on the <a href="http://www.enigmail.net/support/" target="_blank">Enigmail Help web page</a> <br />
If you have questions or comments about enigmail, please send a message to the <a href="http://www.enigmail.net/support/list.php" target="_blank">Enigmail mailing list</a></p>
<p>Enigmail is open source and licensed under the <a href="http://www.mozilla.org/MPL/" target="_blank">Mozilla Public License</a> and the <a href="http://www.gnu.org/copyleft/gpl.html" target="_blank">GNU General Public License</a></p>
</body>
</html>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Enigmail Help: How to Resolve Problems with Initializing Enigmail</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
<style type="text/css">
/*<![CDATA[*/
dt { font-weight: bold; }
/*]]>*/
</style>
</head>
<body>
<h1>Enigmail Help</h1>
<h3>How to Resolve Problems with Initializing Enigmail</h3>
<p>There are several reasons why initializing Enigmail does not succeed. The most common ones are described below;
for more information please visit the <a href="http://www.enigmail.net/support/" target="_blank">Enigmail Support page.</a></p>
<dl>
<dt>GnuPG could not be found</dt>
<dd>
<p>
In order for Enigmail to work, the tool <a href="http://www.gnupg.org/" target="_blank">GnuPG</a> needs to be installed.
If GnuPG cannot be found, then first make sure that the executable <tt>gpg.exe</tt> (on Windows; <tt>gpg</tt> on other platforms) is installed on your computer.
If GnuPG is installed, and Enigmail cannot find it, then you need to manually set the path to GnuPG in the Enigmail Preferences (menu <i>Enigmail</i> &gt; <i>Preferences</i>)
</p>
<dt>Enigmime failed to initialize</dt>
<dd>
<p>
Enigmail works only if it is built using the same build environment as Thunderbird or SeaMonkey was built. This means that you can use the official Enigmail releases only if you use the official releases of Thunderbird or SeaMonkey provided by <a href="www.mozilla.org">mozilla.org</a>.
</p>
<p>
If you use a Thunderbird or SeaMonkey version coming from some other source (e.g. the provider of your Linux distribution), or if you built the application yourself, you should either use an Enigmail version built by the same source, or build Enigmail yourself. For building Enigmail, refer to the <a href="http://www.enigmail.net/download/source.php">Source Code section</a> on the Enigmail home page. Please don't file any bug report concerning this problem, it is not solvable.
</p>
</dd>
</dl>
<p>Further help is available on the <a href="http://www.enigmail.net/support/troubles.php" target="_blank">Enigmail Support Web Site</a>.</p>
</body>
</html>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Enigmail Help: Message Reading</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
<style type="text/css">
/*<![CDATA[*/
dt { font-weight: bold; }
/*]]>*/
</style>
</head>
<body>
<h1>Enigmail Help</h1>
<h3>Using Enigmail when reading messages</h3>
<dl>
<dt>Decrypt button in main Mail window</dt>
<dd>This button can be used for several purposes: decrypt, verify, or import public keys. Normally decryption/verification happens automatically, although this can be disabled through a preference. However, if this fails, usually a short error message will appear in the Enigmail status line. If you click the Decrypt button, you will be able to see a more detailed error message, including the output from the GnuPG command.</dd>
<dt>Pen and Key icons in Message Header display</dt>
<dd>
The <em>Pen</em> and <em>Key</em> icons in the Message Header display indicate if the message you are reading was signed and/or encrypted and if the signature is good, i.e. the message has not been changed since it was signed. If the message has been changed, the <em>Pen</em> icon will change to a <em>Broken Pen</em> to indicate that the signature is bad. Right clicking on either the Pen or Key icons will bring up a menu with the following options:
<ul>
<li><em>Enigmail Security info</em>: allows you to view the output status from GnuPG for the message.</li>
<li><em>Copy Enigmail Security info</em>: copies the output status from GnuPG to the clipboard; to paste into a reply message, etc.</li>
<li><em>View OpenPGP Photo ID</em>: allows you to view the <em>Photo ID</em> of the person who sent the message, if they have a photo embedded in their Public Key. (<em>This option will only be enabled if a Photo ID exists in their key.)</em></li>
<li><em>S/MIME Security info</em>: allows you to view the S/MIME Security Info for the message.</li>
</ul>
<p>If you do not have <em>keyserver-options auto-key-retrieve</em> set in your <tt>gpg.conf</tt> file and you read a message which is signed or encrypted, you will see a <em>Pen</em> icon in the headers display area with a <em>Question mark</em> on it, the Enigmail status line in the headers area will say <em>Part of the message signed; click pen icon for details</em> and the message in the Message Pane will show all the OpenPGP message block indicators and the signature block.</p>
<p>You may also see this if you have <em>keyserver-options auto-key-retrieve</em> set in your <tt>gpg.conf</tt> file and the OpenPGP key is not available on the default keyserver.</p>
<p>Clicking on the <em>Pen and Question mark</em> icon will bring up a window advising that the key is unavailable in your keyring. Clicking on OK will bring up another window with a list of keyservers from which you can select to download the sender's public key from.</p>
<p>To configure the list of keyservers you wish to use, go to <strong>Enigmail -&gt; Preferences -&gt; Basic</strong> tab and enter the keyserver addresses in the <em>Keyserver(s):</em> box, separated by a comma. <em>The first keyserver in the list will be used as the default.</em></p>
</dd>
<dt>Opening encrypted attachments / importing attached OpenPGP keys</dt>
<dd>Attachments named *.pgp, *.asc and *.gpg are recognized as attachments that can be handled specially by Enigmail. Right clicking on such an attachment enables two special menu items in the context menu: <em>Decrypt and Open</em> and <em>Decrypt and Save</em>. Use these two menu items if you want Enigmail to decrypt an attachment before opening or saving it. If an attachment is recognized as an OpenPGP key file, you are offered to import the keys it into your keyrings.</dd>
</dl>
<hr />
<p>Further help is available on the <a href="http://www.enigmail.net/support/" target="_new">Enigmail Help web page</a></p>
</body>
</html>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Enigmail Help: Rules Editor</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
<style type="text/css" xml:space="preserve">
/*<![CDATA[*/
dt { font-weight: bold; }
/*]]>*/
</style>
</head>
<body>
<h1>Enigmail Help</h1>
<h3>Using the Enigmail Rules Editor</h3>
<p>In the Rules Editor, you can specify defaults per recipient for enabling encryption, signing and PGP/MIME, and to define what OpenPGP key(s) to use. Each rule consists of 5 fields and is represented on a single line:</p>
<dl>
<dt>Email</dt>
<dd>The e-mail(s) from the To:, Cc: and Bcc: fields to match. The matching works on <span style="font-style: italic;">substrings</span> (Further details can be found in the Edit Rule dialog)</dd>
<dt>OpenPGP Key(s)</dt>
<dd>a list of OpenPGP Key ID's to use for the recipient</dd>
<dt>Sign</dt>
<dd>
enable or disable message signing. This either uses or overrides what you have specified in the message composition window. The values are:
<ul>
<li><em>Never</em>: disable signing, even if it was enabled in the message composition window (overrules the other values)</li>
<li><em>Possible</em>: leave signing as specified in the message composition window</li>
<li><em>Always</em>: enable signing, even if it was <span style="font-style: italic;">not</span> enabled in the message composition window</li>
</ul>
<p>These signing settings are applied for all rules that match. If one of the rules disables signing, the message will not be signed, regardless of other rules that specify <em>Always</em>.</p>
</dd>
<dt>Encrypt</dt>
<dd>enable or disable message encryption. The allowed settings and their meaning are the same as for message signing.</dd>
<dt>PGP/MIME</dt>
<dd>enable or disable the use of the PGP/MIME (RFC 3156) message encoding. If PGP/MIME is disabled, the messages are encoded using "inline PGP". The allowed values and their meaning a re the same as for message signing.</dd>
</dl>
<p>The rules are processed in the order displayed in the list. Whenever a rule matches a recipient and contains a OpenPGP Key ID, in addition to using the specified Key ID, the recipient is not considered anymore when processing further rules.</p>
<p><em>Note:</em> The rule editor is not yet complete. It is possible to write some more advanced rules by directly editing the rules file (these rules should then not be edited anymore in the rule editor). <a href="http://www.enigmail.net/documentation/pgprules_file.php" target="_blank">Further information</a> for directly editing the file is available on the Enigmail Homepage</p>
<hr />
<p>Further help is available on the <a href="http://www.enigmail.net/support/" target="_blank">Enigmail Help web page</a></p>
</body>
</html>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Enigmail Help: Edit OpenPGP Rule</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
<style type="text/css">
/*<![CDATA[*/
dt { font-weight: bold; }
/*]]>*/
</style>
</head>
<body>
<h1>Enigmail Help</h1>
<h3>Defining Preferences to Send Encrypted</h3>
<p>In the Sending Preferences you can choose the general model and preferences for encryption.</p>
<dl>
<dt>Convenient Encryption</dt>
<dd>With these settings, emails are encrypted without confirmation whenever possible.
<p>This setup is appropriate, if you just want to improve your privacy by sending emails encyrpted instead of unencrypted if that's possible.
<p>The effect is like sending emails as letters instead of postcards. Unlike postcards, letters usually hide their contents while in transit.
<p>Note however that as with letters you can't be sure that nobody is opening the letter while it is in transit (although, some technical effort is necessary for that).
<p>A concrete risk is that you accidentally use &quot;faked keys&quot; you got from somewhere or somebody claiming that the key belongs to the person you want to send emails to. To avoid this risk, you can either use the trust model of PGP (see below) or you should always verify, whether the fingerprint of a public key is correct.</dd>
<dt>Manual Encryption</dt>
<dd>This option allows you to specify the different preferences for encryption according to your needs. You can specify
<ul>
<li>whether replies to encrypted/signed emails should automatically also be encrypted/signed-</li>
<li>whether to use the trust model of Enigmail to accept keys (this means that to use a key you either have to sign the key or have enough other people you trust having signed the key).</li>
<li>whether you want to automatically send emails encrypted if all keys are accepted.</li>
<li>whether and when you want to finally confirm sending an email.</li>
</ul>
</dd>
If it is important for you that content you send encrypted can't be read by other people or organizations, you should use the manual preferences at least choose the option to accept keys only if you or other people signed them. While this model reduces the risk of using faked keys, it requires that you actively sign keys and declare owner trust using the key managament dialog.
</body>
</html>
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment