From 6c7ce7551dbcee46d4b69ea6e71934d36a006bd9 Mon Sep 17 00:00:00 2001 From: Werner Koch Date: Tue, 28 Aug 2001 11:11:10 +0000 Subject: Typo fixes and new gpgme_get_op_info --- complus/README | 2 +- complus/vbtest.vbs | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'complus') diff --git a/complus/README b/complus/README index 30fc30d9..7dc3bb1d 100644 --- a/complus/README +++ b/complus/README @@ -63,7 +63,7 @@ Using Gpgcom Gpgcom currently support only encryption but will be extended to the full range of operations GnuPG provides. The 2 examples should goive yopu a hint on how to use it. We suggest that you always set armor to -true, so that the returned text is a string. IF you don't use armor, +true, so that the returned text is a string. If you don't use armor, the "ciphertext" property will return an array with the binary message. diff --git a/complus/vbtest.vbs b/complus/vbtest.vbs index 7ea346da..8246b456 100644 --- a/complus/vbtest.vbs +++ b/complus/vbtest.vbs @@ -13,7 +13,7 @@ gpg.textmode = true gpg.plaintext = "This is the secret message." 'or: InputBox('Enter message:") ' Set the Recipient. You may also use a keyID or an fingerprint -gpg.addrecipient "alice" +gpg.AddRecipient "alice" ' And encrypt the stuff gpg.encrypt -- cgit v1.2.3