Re: non-ascii handling

[<mi...@st...>]

Jens,

Sorry for answering that late.

Jens Vagelpohl wrote:
> i have a product that uses python-ldap and i'm trying to make sure=20
> everything works when non-ascii characters are used in a DN. from what =
i=20
> have been reading about OpenLDAP it either wants pure ASCII passed to i=
t=20
> (for search terms, DNs etc) or UTF-8-encoded unicode strings.

Depends on the attribute. BTW: ASCII is a real subset of UTF-8. Or better=
=20
said: The character entities encoded in ASCII are mapped to the very same=
=20
encoding in UTF-8.

> my question is: does python-ldap do any automatic string conversions?

No! And I refused a patch which does. It cannot be done without applying =

knowledge about the schema (syntax of an attribute). Review the archives.=


> i=20
> get search results just fine using a non-ascii search term when i do no=
t=20
> convert the term myself and hand it to ldap.search_s, but i never get=20
> results if i convert the string by myself and then hand it to the=20
> search_s method.

If you have a Unicode object with a LDAP search filter than you have to=20
encode that before calling method search_s().

Example (valid on my Linux console with ISO-8859-1):

filter =3D unicode('cn=3D*Str=F6der*','iso-8859-1')
l.search_s(search_root,ldap.SCOPE_SUB,filter.encode('utf-8'))

Note that filter is a Unicode object created by passing a string and the =

known character set to the unicode() function.

Ciao, Michael.