mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-03 22:56:33 +02:00
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 <dkg@fifthhorseman.net>
This commit is contained in:
parent
6e930f0e40
commit
215180d1ce
3 changed files with 17 additions and 18 deletions
|
@ -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.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue