Re: International Characters

[Chris R. <chr...@me...>]

Knut Sander <knu...@se...> wrote:
>> Date: Fri, 1 Jun 2001 19:21:40 -0700 (PDT)
>> From: Christoph Neumann <en...@ap...>
>> To: LDAP Mailing List <per...@li...>
>> Subject: International Characters
>  =
>> I chose the directoryString (UTF-8 format) type since it should allow =
the
>> international characters.  However, when I try to insert the string 'im
>> k=3DE4ppele 8' I get the error:
>> =
>> apuhomestreet: value #0 contains invalid data
> =
> Hi Christoph,
> =
> did you encode your data as UTF8-string? The 0xe4 above (=E4 =3D ae) =
looks
> like you try to add a latin1 string, but this is not a legal UTF8 byte
> sequence.
> =
> I also had this problem with OpenLDAP 2.x but not with Netscape or
> ControlData. It looks to me, that it depends on the schema, ControlData
> (real X.500) defines attributes with more then on legal encoding (T.61,
> latin1, UTF8) and prefixes it with '{<encoding>}' like passwords. The
> server tries to determine the right encoding if it is not supplied, and
> falls back to T.61 if it is not clear. I don't know if this is conform
> to any LDAP-spec.

That isn't legal for the standard syntaxes in LDAPv3 - everything *must* be
UTF-8. It would be OK for LDAPv2, except that UTF-8 is not a valid encoding
of a character set for LDAPv2.

Netscape will typically accept any illegal garbage values and return them
verbatim, so it isn't a good test of what is correct or not :-(

Cheers,

Chris