Cheap solution; Since all I'm doing is simple searches and playing with the data directly, downgrading to LDAP v2 solves the problem by returning the data in a Windows codepage that doesn't require any conversion. Since this is a Wintel only project this a 'good enough' work around.
Sigh...Windows. and here I am on another windows box that has mangled the acented chars in this email. On Friday, August 22, 2003, at 09:07AM, Chris Ridd <[EMAIL PROTECTED]> wrote: >On 22/8/03 2:50 pm, Erik Ableson <[EMAIL PROTECTED]> wrote: > >> I'm trying to search in an ou that contains accented characters in the >name. >> >> OU=Groupes S�curit?DC... >> >> and it returns zero objects with the filter of (objectclass=group). Since >I >> was recently arguing with character sets on this box, I've tried a few >> encode:decode operations on the OU string, but that just causes the script >to >> stall indefinitely. >> >> Setup: >> >> Windows XP >> ActiveState perl 5.8 >> Net::LDAP > >If you're using LDAP then you need to have a string containing UTF-8. > >If you set $ldap->debug(12) before your search (and set $ldap->debug(0) >afterwards) then you can see what bytes are being sent. Can you confirm that >UTF-8 is being sent correctly?
