aboutsummaryrefslogtreecommitdiffstats
path: root/dirmngr/cdblib.c
diff options
context:
space:
mode:
authorDaniel Kahn Gillmor <[email protected]>2016-09-15 17:34:10 +0000
committerNIIBE Yutaka <[email protected]>2016-09-17 06:57:31 +0000
commit215180d1ce6c93e2b4969d746c83ac4c055d25ef (patch)
treed9cf00cd41a0f729b2028814b574905a79ba8dae /dirmngr/cdblib.c
parentg10: On failure, propagate the return code. (diff)
downloadgnupg-215180d1ce6c93e2b4969d746c83ac4c055d25ef.tar.gz
gnupg-215180d1ce6c93e2b4969d746c83ac4c055d25ef.zip
move some file encodings to UTF-8
* dirmgnr/cdblib.c: comment used unnecesary hyphenation * dirmngr/crlcache.h: comment was iso-8859-1 * doc/contrib.text: list contributors using UTF-8 (now we can acknowledge many more people using their preferred orthography) At least one other files remains in a non-UTF-8 encoding, which i'm not sure what to do with: - build-aux/speedo/w32/inst.nsi is ISO-8859-1, but maybe Windows needs it that way? Signed-off-by: Daniel Kahn Gillmor <[email protected]>
Diffstat (limited to 'dirmngr/cdblib.c')
-rw-r--r--dirmngr/cdblib.c13
1 files changed, 6 insertions, 7 deletions
diff --git a/dirmngr/cdblib.c b/dirmngr/cdblib.c
index 52c17c98d..c04690ff8 100644
--- a/dirmngr/cdblib.c
+++ b/dirmngr/cdblib.c
@@ -298,16 +298,15 @@ cdb_find(struct cdb *cdbp, const void *key, cdbi_t klen)
possible to have many than one record with the same key in a
database, and these routines allow enumeration of all of them.
cdb_findinit() initializes search structure pointed to by cdbfp.
- It will return negative value on error or 0 on success. cdb_find�
- next() attempts to find next matching key, setting value position
- and length in cdbfp structure. It will return positive value if
- given key was found, 0 if there is no more such key(s), or negative
- value on error. To access value position and length after
+ It will return negative value on error or 0 on success.
+ cdb_findnext() attempts to find next matching key, setting value
+ position and length in cdbfp structure. It will return positive
+ value if given key was found, 0 if there is no more such key(s), or
+ negative value on error. To access value position and length after
successeful call to cdb_findnext() (when it returned positive
result), use cdb_datapos() and cdb_datalen() macros with cdbp
pointer. It is error to use cdb_findnext() after it returned 0 or
- error condition. These routines is a bit slower than
- cdb_find().
+ error condition. These routines is a bit slower than cdb_find().
Setting KEY to NULL will start a sequential search through the
entire DB.