Hello,
while reading the manual of libgcrypt, I noticed some writing errors:
Index: cvs/libgcrypt/doc/gcrypt.texi
===================================================================
--- cvs/libgcrypt/doc/gcrypt.texi (revision 1142)
+++ cvs/libgcrypt/doc/gcrypt.texi (working copy)
@@ -1137,7 +1137,7 @@
AES (Rijndael) with a 128 bit key.
@item GCRY_CIPHER_AES192
-@itemx GCRY_CIPHER_RIJNDAEL128
+@itemx GCRY_CIPHER_RIJNDAEL192
AES (Rijndael) with a 192 bit key.
@item GCRY_CIPHER_AES256
@@ -1418,7 +1418,7 @@
@var{inlen} is @code{0}, in-place encryption of the data in @var{out} or
length @var{outsize} takes place. With @var{in} being not @code{NULL},
@var{inlen} bytes are encrypted to the buffer @var{out} which must have
-at least a size of @var{inlen}. @var{outlen} must be set to the
+at least a size of @var{inlen}. @var{outsize} must be set to the
allocated size of @var{out}, so that the function can check that there
is sufficient space. Note, that overlapping buffers are not allowed.
@@ -1438,7 +1438,7 @@
@var{inlen} is @code{0}, in-place decryption of the data in @var{out} or
length @var{outsize} takes place. With @var{in} being not @code{NULL},
@var{inlen} bytes are decrypted to the buffer @var{out} which must have
-at least a size of @var{inlen}. @var{outlen} must be set to the
+at least a size of @var{inlen}. @var{outsize} must be set to the
allocated size of @var{out}, so that the function can check that there
is sufficient space. Note, that overlapping buffers are not allowed.
@@ -1886,7 +1886,7 @@
Because it is often necessary to get the message digest of one block of
memory, a fast convenience function is available for this task:
-@deftypefun void gcry_md_hash_buffer (int @var{algo}, void *@var{digest}, const cvoid *@var{buffer}, size_t @var{length});
+@deftypefun void gcry_md_hash_buffer (int @var{algo}, void *@var{digest}, const void *@var{buffer}, size_t @var{length});
@code{gcry_md_hash_buffer} is a shortcut function to calculate a message
digest of a buffer. This function does not require a context and
@@ -3022,7 +3022,7 @@
@example
@{
gcry_ac_key_pair_t key_pair;
- gcry_ac_key_spec_rsa rsa_spec;
+ gcry_ac_key_spec_rsa_t rsa_spec;
rsa_spec.e = gcry_mpi_new (0);
gcry_mpi_set_ui (rsa_spec.e, 1)
@@ -3091,7 +3091,7 @@
are then forwared to the cryptographic primitives. Since schemes are
to be used for a special purpose in order to achieve a particular
security goal, there exist ``encryption schemes'' and ``signature
-schemes''. Encoding methods can be used seperately or implicitely
+schemes''. Encoding methods can be used separately or implicitly
through schemes.
What follows is a description of the cryptographic primitives.
@@ -3391,7 +3391,7 @@
string is inserted into the resulting S-expression.
@item %d
The next argument is expected to be of type @code{int} and its
-value ist inserted into the resulting S-expression.
+value is inserted into the resulting S-expression.
@item %b
The next argument is expected to be of type @code{int} directly
followed by an argument of type @code{char *}. This represents a
--
Tommi Vainikainen
_______________________________________________
Gcrypt-devel mailing list
Gcrypt-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gcrypt-devel
while reading the manual of libgcrypt, I noticed some writing errors:
Index: cvs/libgcrypt/doc/gcrypt.texi
===================================================================
--- cvs/libgcrypt/doc/gcrypt.texi (revision 1142)
+++ cvs/libgcrypt/doc/gcrypt.texi (working copy)
@@ -1137,7 +1137,7 @@
AES (Rijndael) with a 128 bit key.
@item GCRY_CIPHER_AES192
-@itemx GCRY_CIPHER_RIJNDAEL128
+@itemx GCRY_CIPHER_RIJNDAEL192
AES (Rijndael) with a 192 bit key.
@item GCRY_CIPHER_AES256
@@ -1418,7 +1418,7 @@
@var{inlen} is @code{0}, in-place encryption of the data in @var{out} or
length @var{outsize} takes place. With @var{in} being not @code{NULL},
@var{inlen} bytes are encrypted to the buffer @var{out} which must have
-at least a size of @var{inlen}. @var{outlen} must be set to the
+at least a size of @var{inlen}. @var{outsize} must be set to the
allocated size of @var{out}, so that the function can check that there
is sufficient space. Note, that overlapping buffers are not allowed.
@@ -1438,7 +1438,7 @@
@var{inlen} is @code{0}, in-place decryption of the data in @var{out} or
length @var{outsize} takes place. With @var{in} being not @code{NULL},
@var{inlen} bytes are decrypted to the buffer @var{out} which must have
-at least a size of @var{inlen}. @var{outlen} must be set to the
+at least a size of @var{inlen}. @var{outsize} must be set to the
allocated size of @var{out}, so that the function can check that there
is sufficient space. Note, that overlapping buffers are not allowed.
@@ -1886,7 +1886,7 @@
Because it is often necessary to get the message digest of one block of
memory, a fast convenience function is available for this task:
-@deftypefun void gcry_md_hash_buffer (int @var{algo}, void *@var{digest}, const cvoid *@var{buffer}, size_t @var{length});
+@deftypefun void gcry_md_hash_buffer (int @var{algo}, void *@var{digest}, const void *@var{buffer}, size_t @var{length});
@code{gcry_md_hash_buffer} is a shortcut function to calculate a message
digest of a buffer. This function does not require a context and
@@ -3022,7 +3022,7 @@
@example
@{
gcry_ac_key_pair_t key_pair;
- gcry_ac_key_spec_rsa rsa_spec;
+ gcry_ac_key_spec_rsa_t rsa_spec;
rsa_spec.e = gcry_mpi_new (0);
gcry_mpi_set_ui (rsa_spec.e, 1)
@@ -3091,7 +3091,7 @@
are then forwared to the cryptographic primitives. Since schemes are
to be used for a special purpose in order to achieve a particular
security goal, there exist ``encryption schemes'' and ``signature
-schemes''. Encoding methods can be used seperately or implicitely
+schemes''. Encoding methods can be used separately or implicitly
through schemes.
What follows is a description of the cryptographic primitives.
@@ -3391,7 +3391,7 @@
string is inserted into the resulting S-expression.
@item %d
The next argument is expected to be of type @code{int} and its
-value ist inserted into the resulting S-expression.
+value is inserted into the resulting S-expression.
@item %b
The next argument is expected to be of type @code{int} directly
followed by an argument of type @code{char *}. This represents a
--
Tommi Vainikainen
_______________________________________________
Gcrypt-devel mailing list
Gcrypt-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gcrypt-devel