3 files changed, 36 insertions, 4 deletions
diff --git a/doc/ChangeLog b/doc/ChangeLog
index 33e0c41bc..a481732d2 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,12 @@
+2001-10-31  Werner Koch  <[email protected]>
+
+	* gpg.sgml: Add a remark on how to get the long key ID.  Suggested
+	by Sebastian Klemke.
+
+2001-10-23  Werner Koch  <[email protected]>
+
+	* gpg.sgml: Add missing tag.
+
 2001-09-28  Werner Koch  <[email protected]>
 
 	* gpg.sgml: Add a note on option parsing.
diff --git a/doc/gpg.sgml b/doc/gpg.sgml
index 2c07e7c8b..0eec90bad 100644
--- a/doc/gpg.sgml
+++ b/doc/gpg.sgml
@@ -81,6 +81,7 @@ You will find a list of HOWTO documents at http://www.gnupg.org/docs.html .
 Please remember that option parsing stops as soon as a non option is
 encountered, you can explicitly stop option parsing by using the
 special option "--".
+</para>
 </refsect1>
 
 <refsect1>
@@ -1299,6 +1300,19 @@ signatures on data.
 Reset the --force-v3-sigs option.
 </para></listitem></varlistentry>
 
+<varlistentry>
+<term>--force-v4-certs</term>
+<listitem><para>
+Always use v4 key signatures even on v3 version keys.  This make the
+signature unusable for PGP 2.
+</para></listitem></varlistentry>
+
+<varlistentry>
+<term>--no-force-v3-certs</term>
+<listitem><para>
+Reset the --force-v4-certs option.
+</para></listitem></varlistentry>
+
 
 <varlistentry>
 <term>--force-mdc</term>
@@ -1453,7 +1467,7 @@ encoded in UTF-8 regardless of any --charset setting.
 <varlistentry>
 <term>--with-key-data</term>
 <listitem><para>
-Print key listings delimited by colons and print the public key data.
+Print key listings delimited by colons (like --with-colons) and print the public key data.
 </para></listitem></varlistentry>
 
 <varlistentry>
@@ -1617,7 +1631,8 @@ Here the key ID is given in the usual short form.
 <term>01AB3FED1347A5612</term>
 <term>0x234AABBCC34567C4</term>
 <listitem><para>
-Here the key ID is given in the long form as used by OpenPGP.
+Here the key ID is given in the long form as used by OpenPGP
+(you can get the long key ID using the option --with-colons).
 </para></listitem>
 </varlistentry>
 
diff --git a/doc/gpg.texi b/doc/gpg.texi
index 1a83b0906..9b8a90ddd 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -791,6 +791,13 @@ signatures on data.
 @item ---no-force-v3-sigs
 Reset the ---force-v3-sigs option.
 
+@item ---force-v4-certs
+Always use v4 key signatures even on v3 version keys. This make the
+signature unusable for PGP 2.
+
+@item ---no-force-v3-certs
+Reset the ---force-v4-certs option.
+
 @item ---force-mdc
 Force the use of encryption with appended manipulation
 code. This is always used with the newer ciphers (those
@@ -881,7 +888,7 @@ Print key listings delimited by colons. Note, that the output will be
 encoded in UTF-8 regardless of any ---charset setting.
 
 @item ---with-key-data
-Print key listings delimited by colons and print the public key data.
+Print key listings delimited by colons (like ---with-colons) and print the public key data.
 
 @item ---with-fingerprint
 Same as the command ---fingerprint but changes only the format of the output
@@ -979,7 +986,8 @@ Here the key ID is given in the usual short form.
 @itemx 0F323456784E56EAB
 @itemx 01AB3FED1347A5612
 @itemx 0x234AABBCC34567C4
-Here the key ID is given in the long form as used by OpenPGP.
+Here the key ID is given in the long form as used by OpenPGP
+(you can get the long key ID using the option ---with-colons).
 
 @item 1234343434343434C434343434343434
 @itemx 123434343434343C3434343434343734349A3434