Correct key-gen example.

diff --git a/doc/ChangeLog b/doc/ChangeLog
index d1ea9439bc2b506ffaceb7d62faa4457bf963b51..638df329e3017875cf0a4294430733b754c13dad 100644 (file)
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,8 @@
+2011-05-12  Marcus Brinkmann  <marcus@g10code.com>
+
+       * gpgme.texi (Generating Keys): Fix OpenPGP parameters and reference
+       GPG and GPGSM manual.
+
 2010-01-05  Werner Koch  <wk@g10code.com>
 
        * gpgme.texi (Changing Passphrases): New.

diff --git a/doc/gpgme.texi b/doc/gpgme.texi
index c9bb708f7875c7eb6731043076b450cd9ba9c441..c2bb3092ce167f18178549fbcf3c45c2d7086123 100644 (file)
--- a/doc/gpgme.texi
+++ b/doc/gpgme.texi
@@ -3294,14 +3294,13 @@ used.  GpgSM does not make the fingerprint available.
 The argument @var{parms} specifies parameters for the key in an XML
 string.  The details about the format of @var{parms} are specific to
 the crypto engine used by @var{ctx}.  Here is an example for GnuPG as
-the crypto engine:
+the crypto engine (all parameters of OpenPGP key generation are
+documented in the GPG manual):
 
 @example
 <GnupgKeyParms format="internal">
-Key-Type: DSA
-Key-Length: 1024
-Subkey-Type: ELG-E
-Subkey-Length: 1024
+Key-Type: default
+Subkey-Type: default
 Name-Real: Joe Tester
 Name-Comment: with stupid passphrase
 Name-Email: joe@@foo.bar
@@ -3310,7 +3309,8 @@ Passphrase: abc
 </GnupgKeyParms>
 @end example
 
-Here is an example for GpgSM as the crypto engine:
+Here is an example for GpgSM as the crypto engine (all parameters of
+OpenPGP key generation are documented in the GPGSM manual):
 
 @example
 <GnupgKeyParms format="internal">