[svn] GnuPG - r3897 - trunk/doc

svn author dshaw cvs at cvs.gnupg.org
Thu Sep 22 05:09:44 CEST 2005


Author: dshaw
Date: 2005-09-22 05:09:38 +0200 (Thu, 22 Sep 2005)
New Revision: 3897

Modified:
   trunk/doc/ChangeLog
   trunk/doc/gpg.sgml
Log:
* 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.


Modified: trunk/doc/ChangeLog
===================================================================
--- trunk/doc/ChangeLog	2005-09-20 08:19:50 UTC (rev 3896)
+++ trunk/doc/ChangeLog	2005-09-22 03:09:38 UTC (rev 3897)
@@ -1,3 +1,9 @@
+2005-09-21  David Shaw  <dshaw at 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 at jabberwocky.com>
 
 	* gpg.sgml: Fix documentation for setpref/updpref, document

Modified: trunk/doc/gpg.sgml
===================================================================
--- trunk/doc/gpg.sgml	2005-09-20 08:19:50 UTC (rev 3896)
+++ trunk/doc/gpg.sgml	2005-09-22 03:09:38 UTC (rev 3897)
@@ -749,6 +749,10 @@
 Search the keyserver for the given names.  Multiple names given here
 will be joined together to create the search string for the 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>
 
 <varlistentry>
@@ -1470,8 +1474,8 @@
 <listitem><para>
 When using the "--export-secret-subkeys" command, this option resets
 the passphrases for all exported subkeys to empty.  This is useful
-when the exported subkey is to be used on an unattended amchine where
-a passphrase won't make sense. Defaults to no.
+when the exported subkey is to be used on an unattended machine where
+a passphrase doesn't necessarily make sense.  Defaults to no.
 </para></listitem></varlistentry>
 
 </variablelist>
@@ -1756,10 +1760,12 @@
 <term>--display-charset &ParmName;</term>
 <listitem><para>
 Set the name of the native character set.  This is used to convert
-some informational strings like user IDs to the proper UTF-8
-encoding. If 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>
+some informational strings like user IDs to the proper UTF-8 encoding.
+Note that this has nothing to do with the character set of data to be
+encrypted or signed; GnuPG does not recode user supplied data.  If
+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>
 <varlistentry>
 <term>iso-8859-1</term><listitem><para>This is the Latin 1 set.</para></listitem>
@@ -2943,6 +2949,14 @@
 </para></listitem>
 </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
 <varlistentry>
 <term>+Heinrich Heine duesseldorf</term>




More information about the Gnupg-commits mailing list