[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: [ldapext] UTF-8 full support in LDIF / LDIF v2




Hi Yves,

Yves Dorfsman wrote:
Kurt Zeilenga wrote:


Extending LDIF to support XML values.

Really ?

See http://www.xmled.info/drafts/draft-sciberras-xed-eldif-05.txt


Interesting, I think this is a valid issue, although I think XML is the wrong solution.

We created a solution for presenting directory attribute values that are arbitrary UTF-8 character strings including line breaks. That accommodates UTF-8 encoded XML documents, but would also be useful for GSER encodings if the whitespace separator is extended to include line breaks.

Any reason why the draft never made it to an RFC ?

It may yet. We've just been busy with other things and there hasn't been external pressure to move it along.


What other solutions could be used to make multi-line entries ?

Escaping the line break characters in the value and using the existing LDIF line folding method would work. The output function can optionally fold lines immediately after an escaped line break so that the number of lines in the value matches the number of lines in the LDIF output.

Another solution is to drop into a literal mode until a special character
sequence is encountered (e.g., END-OF-VALUE). One must then take care to
escape the special sequence if it happens to occur in the attribute value.

Both of the above solutions require messing about with escape sequences,
whereas the simple prefix method we settled on doesn't need to.

Would quoting a la python work, or would that add too much complexity, too much of a change from the current LDIF ?

Can you present an example of what you mean ?

Regards,
Steven




I think the ASCII I-D/RFC needs to have examples that use some sort of escaping mechanism (for the purposes of the example)

    value: \C3\BC

where C3 BC is the 2 octet UTF-8 encoding of the Unicode LATIN SMALL LETTER U WITH DIAERESIS (U+00FC) codepoint.

    value: \75\CC\88


Thanks, I'll look at that. Anybody knows of an RFC that use something like this in their example, from the top of your head ?


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext