GpgFrontend/gpgme
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

2003-05-27 Marcus Brinkmann <marcus@g10code.de>

Browse Source 
* gpgme.texi (Protocol Selection): Do not use @acronym in @node
	because that breaks texi2dvi.
This commit is contained in:
Marcus Brinkmann 2003-05-27 05:41:43 +00:00
parent 0be6fec1e2
commit 569509758a
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/ChangeLog
View File

@ -1,5 +1,8 @@
2003-05-27 Marcus Brinkmann <marcus@g10code.de>
* gpgme.texi (Protocol Selection): Do not use @acronym in @node
because that breaks texi2dvi.
* gpgme.texi (Passphrase Callback): Document new prototype.
2003-05-18 Marcus Brinkmann <marcus@g10code.de>

5
doc/gpgme.texi
View File

@ -1538,7 +1538,8 @@ The function @code{gpgme_get_protocol} retrieves the protocol currently
use with the context @var{ctx}.
@end deftypefun
@node @acronym{ASCII} Armor
@c FIXME: Unfortunately, using @acronym here breaks texi2dvi.
@node ASCII Armor
@subsection @acronym{ASCII} Armor
@cindex context, armor mode
@cindex @acronym{ASCII} armor
@ -2681,7 +2682,7 @@ data buffer.
@deftypefun gpgme_error_t gpgme_op_import (@w{gpgme_ctx_t @var{ctx}}, @w{gpgme_data_t @var{keydata}})
The function @code{gpgme_op_import} adds the keys in the data buffer
@var{keydata} to the key ring of the crypto engine used by @var{ctx}.
The format of @var{keydata} can be @var{ASCII} armored, for example,
The format of @var{keydata} can be @acronym{ASCII} armored, for example,
but the details are specific to the crypto engine.
After the operation completed successfully, the result can be