Howard Chu wrote:
Yeah, the utf8 API is in kind of a weird place. Some stuff is provided by the OS, like utf8 <-> charset conversion (iconv), some stuff is provided by third party libraries we already use (ICU). It's really odd that an LDAP library should provide a utf8 API - it just seems as though there should be a more widespread utf8 API library (ICU is very heavyweight if that's all you're going to use it for - a sledgehammer for a thumbtack). However, since utf8 is so integral to LDAP, having LDAP expose a useful API would be a good thing.Message: 1 Date: Mon, 06 Jul 2009 13:20:22 -0600 From: Rich Megginson<rmeggins@xxxxxxxxxx>Note - the patch does not contain the diffs for configure nor Makefile.inhttp://rmeggins.fedorapeople.org/0001-OpenLDAP-support.patchWe probably should talk about exposing the UTF8 APIs. The only reason they were kept private is because they weren't part of the RFC1823 or the expired C API draft, but they've been present for at least the past 9 years.
Ok. We will have to track that and be prepared when the change occurs. Thanks for the heads-up.re: ldif_read_record() and the public LDIF API, note our ITS#5892; some of the function signatures here will change soon so that error can be distinguished from EOF. (But since 2.4's APIs are supposed to be frozen it may wait until 2.5.)
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-- 389-devel mailing list 389-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-devel
