From de199636e995f4b88b9eb1f7b51b839e6a0acacf Mon Sep 17 00:00:00 2001 From: David Shaw Date: Thu, 20 Nov 2003 13:02:42 +0000 Subject: [PATCH] * TRANSLATE: New, note to translators about the yes|yes multiple match syntax. * gpg.sgml: Document --compress-level. Some minor tweaks to other entries. --- doc/ChangeLog | 8 ++++++++ doc/TRANSLATE | 18 ++++++++++++++++++ doc/gpg.sgml | 24 ++++++++---------------- 3 files changed, 34 insertions(+), 16 deletions(-) create mode 100644 doc/TRANSLATE diff --git a/doc/ChangeLog b/doc/ChangeLog index 2ff5e2202..a27095dca 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,11 @@ +2003-11-20 David Shaw + + * 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 * samplekeys.asc: Update 99242560. diff --git a/doc/TRANSLATE b/doc/TRANSLATE new file mode 100644 index 000000000..6ddc93fc0 --- /dev/null +++ b/doc/TRANSLATE @@ -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. diff --git a/doc/gpg.sgml b/doc/gpg.sgml index 1e3ca36a9..627a3adc3 100644 --- a/doc/gpg.sgml +++ b/doc/gpg.sgml @@ -573,14 +573,6 @@ or changed by you. - ---export-all &OptParmNames; - -Same as --export, but also exports keys which -are not compatible with OpenPGP. - - - --export-secret-keys &OptParmNames; --export-secret-subkeys &OptParmNames; @@ -874,7 +866,7 @@ Try to be as quiet as possible. --z &ParmN;, --compress &ParmN; +-z &ParmN;, --compress-level &ParmN; 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. --always-trust -Identical to `--trust-model always' +Identical to `--trust-model always'. This option is deprecated. @@ -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. 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. --no-force-v3-sigs 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