security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2024-11-11 21:48:50 +01:00
Code Activity

* TRANSLATE: New, note to translators about the yes|yes multiple match

Browse Source 
syntax.

* gpg.sgml: Document --compress-level.  Some minor tweaks to other
entries.
This commit is contained in:
David Shaw 2003-11-20 13:02:42 +00:00
parent 31ea8b4b08
commit de199636e9
3 changed files with 34 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/ChangeLog
View File

@ -1,3 +1,11 @@
2003-11-20 David Shaw <dshaw@jabberwocky.com>
* TRANSLATE: New, note to translators about the yes|yes multiple
match syntax.
* gpg.sgml: Document --compress-level. Some minor tweaks to other
entries.
2003-10-01 David Shaw <dshaw@jabberwocky.com>
* samplekeys.asc: Update 99242560.

18
doc/TRANSLATE Normal file
View File

@ -0,0 +1,18 @@
$Id$
Note for translators
--------------------
Some strings in GnuPG are for matching user input against. These
strings can accept multiple values that mean essentially the same
thing.
For example, the string "yes" in English is "sí" in Spanish. However,
some users will type "si" (without the accent). To accomodate both
users, you can translate the string "yes" as "sí|si". You can have
any number of alternate matches seperated by the | character like
"sí|si|seguro".
The strings that can be handled in this way are of the form "yes|yes",
(or "no|no", etc.) There should also be a comment in the .po file
directing you to this file.

24
doc/gpg.sgml
View File

@ -573,14 +573,6 @@ or changed by you.
</para></listitem></varlistentry>
<varlistentry>
<term>--export-all &OptParmNames;</term>
<listitem><para>
Same as --export, but also exports keys which
are not compatible with OpenPGP.
</para></listitem></varlistentry>
<varlistentry>
<term>--export-secret-keys &OptParmNames;</term>
<term>--export-secret-subkeys &OptParmNames;</term>
@ -874,7 +866,7 @@ Try to be as quiet as possible.
<varlistentry>
<term>-z &ParmN;, --compress &ParmN;</term>
<term>-z &ParmN;, --compress-level &ParmN;</term>
<listitem><para>
Set compression level to &ParmN;. A value of 0 for &ParmN;
disables compression. Default is to use the default
@ -1008,7 +1000,7 @@ ID is bound to the key.
<varlistentry>
<term>--always-trust</term>
<listitem><para>
Identical to `--trust-model always'
Identical to `--trust-model always'. This option is deprecated.
</para></listitem></varlistentry>
@ -1019,11 +1011,11 @@ Use &ParmName as your keyserver. This is the server that --recv-keys,
--send-keys, and --search-keys will communicate with to receive keys
from, send keys to, and search for keys on. The format of the
&ParmName is a URI: `scheme:[//]keyservername[:port]' The scheme is
the type of keyserver: "hkp" for the Horowitz (or compatible)
keyservers, "ldap" for the NAI LDAP keyserver, or "mailto" for the
Horowitz email keyserver. Note that your particular installation of
GnuPG may have other keyserver types available as well. Keyserver
schemes are case-insensitive.
the type of keyserver: "hkp" for the HTTP (or compatible) keyservers,
"ldap" for the NAI LDAP keyserver, or "mailto" for the Graff email
keyserver. Note that your particular installation of GnuPG may have
other keyserver types available as well. Keyserver schemes are
case-insensitive.
</para><para>
Most keyservers synchronize with each other, so there is generally no
need to send keys to more than one server. Using the command "host -l
@ -1864,7 +1856,7 @@ the SHA-256 digest algorithm.
<term>--no-force-v3-sigs</term>
<listitem><para>
OpenPGP states that an implementation should generate v4 signatures
but PGP versions 5 and higher only recognize v4 signatures on key
but PGP versions 5 through 7 only recognize v4 signatures on key
material. This option forces v3 signatures for signatures on data.
Note that this option overrides --ask-sig-expire, as v3 signatures
cannot have expiration dates. --no-force-v3-sigs disables this