1
0
mirror of git://git.gnupg.org/gnupg.git synced 2025-02-01 16:33:02 +01:00

* gpg.sgml: Note that --display-charset is just for display and

doesn't recode data.  Note that --search-keys can use the standard
search syntax now (<, =, *, @).  Document the @-address mode.
This commit is contained in:
David Shaw 2005-09-22 03:09:38 +00:00
parent d0b9ff171d
commit 8db0dc2f08
2 changed files with 26 additions and 6 deletions

View File

@ -1,3 +1,9 @@
2005-09-21 David Shaw <dshaw@jabberwocky.com>
* gpg.sgml: Note that --display-charset is just for display and
doesn't recode data. Note that --search-keys can use the standard
search syntax now (<, =, *, @). Document the @-address mode.
2005-08-23 David Shaw <dshaw@jabberwocky.com> 2005-08-23 David Shaw <dshaw@jabberwocky.com>
* gpg.sgml: Fix documentation for setpref/updpref, document * gpg.sgml: Fix documentation for setpref/updpref, document

View File

@ -749,6 +749,10 @@ keyservers set (see --keyserver-option honor-keyserver-url).
Search the keyserver for the given names. Multiple names given here Search the keyserver for the given names. Multiple names given here
will be joined together to create the search string for the keyserver. will be joined together to create the search string for the keyserver.
Option --keyserver must be used to give the name of this keyserver. Option --keyserver must be used to give the name of this keyserver.
Keyservers that support different search methods allow using the
syntax specified in "How to specify a user ID" below. Note that
different keyserver types support different search methods. Currently
only LDAP supports them all.
</para></listitem></varlistentry> </para></listitem></varlistentry>
<varlistentry> <varlistentry>
@ -1470,8 +1474,8 @@ the --edit-key command "clean uids" before export. Defaults to no.
<listitem><para> <listitem><para>
When using the "--export-secret-subkeys" command, this option resets When using the "--export-secret-subkeys" command, this option resets
the passphrases for all exported subkeys to empty. This is useful the passphrases for all exported subkeys to empty. This is useful
when the exported subkey is to be used on an unattended amchine where when the exported subkey is to be used on an unattended machine where
a passphrase won't make sense. Defaults to no. a passphrase doesn't necessarily make sense. Defaults to no.
</para></listitem></varlistentry> </para></listitem></varlistentry>
</variablelist> </variablelist>
@ -1756,10 +1760,12 @@ found.
<term>--display-charset &ParmName;</term> <term>--display-charset &ParmName;</term>
<listitem><para> <listitem><para>
Set the name of the native character set. This is used to convert Set the name of the native character set. This is used to convert
some informational strings like user IDs to the proper UTF-8 some informational strings like user IDs to the proper UTF-8 encoding.
encoding. If this option is not used, the default character set is Note that this has nothing to do with the character set of data to be
determined from the current locale. A verbosity level of 3 shows the encrypted or signed; GnuPG does not recode user supplied data. If
chosen set. Valid values for &ParmName; are:</para> this option is not used, the default character set is determined from
the current locale. A verbosity level of 3 shows the chosen set.
Valid values for &ParmName; are:</para>
<variablelist> <variablelist>
<varlistentry> <varlistentry>
<term>iso-8859-1</term><listitem><para>This is the Latin 1 set.</para></listitem> <term>iso-8859-1</term><listitem><para>This is the Latin 1 set.</para></listitem>
@ -2943,6 +2949,14 @@ indicates this email address mode.
</para></listitem> </para></listitem>
</varlistentry> </varlistentry>
<varlistentry>
<term>@heinrichh</term>
<listitem><para>
Match within the &#60;email.address&#62; part of a user ID. The at sign
indicates this email address mode.
</para></listitem>
</varlistentry>
<!-- we don't do this <!-- we don't do this
<varlistentry> <varlistentry>
<term>+Heinrich Heine duesseldorf</term> <term>+Heinrich Heine duesseldorf</term>