[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: [ldapext] UTF-8 full support in LDIF / LDIF v2
Howard Chu wrote:
> Kurt Zeilenga wrote:
>> By raising these points, I hope to show that simply removing the ASCII
>> restrictions will lead to problems, and even though some of them (such
>> as invalid UTF-8) can be address by installing various restrictions,
>> the simple fact that LDIF represents LDAP data not text will lead to
>> various problems (such as unintended text file conversions, inability
>> to use text processing programs, etc.).
>> -- Kurt
>
> Agreed. Not to mention that to implement this properly will require
> complete schema knowledge at the time the LDIF is generated. (Otherwise,
> how do you distinguish a genuine octetString value, which cannot be
> safely represented in UTF-8, from a directoryString value...)
Well, in the real world applications are already applying schema
knowledge to the LDAP/LDIF data produced or parsed. But not in the
formal way of a DSA or DUA using information from the subschema
subentry. Rather it's more hard-coded a-priori schema knowledge.
A LDIF writer/reader module could be called with data passed in as
Unicode strings vs. binary buffers to let the application decide which
attribute values to treat as textual string (to be encoded as UTF-8) and
which to treat as blob which needs base64-encoding.
Ciao, Michael.
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext