Re: ldap_explode_dn corrupts UTF-8 encoding (ITS#1890)

[ps@psncc.at]

On Mon, 17 Jun 2002, Pierangelo Masarati wrote:

> > OpenLDAP 2.1.2 seems to currupt non-ASCII UTF-8 encoded characters.
> > It actually turns unprintable chars (in the ASCII sense) into \<hexcode>.
>
> I think this is a leftover of when we decided to use UTF8 instead
> of the '\' + HEXPAIR representation of non-ascii chars, and initially
> it was intended; of course, when parsing a DN, one wants the correct
> UTF8 encoding.

Note that the problem does not exist in 2.0.23...

To further elaborate the problem: before passing the DN to the
ldap_explode_dn function it is properly (UTF-8) encoded. Afterwards the DN
parts aren't...

> It's only a matter of passing a LDAP_DN_PRETTY flag to the conversion
> routines.

Is exploding a dn a conversion wrt to codesets? (I would not think it is)
Where would one need to specify extra flags? Or is this a purely internal
matter?

ps