[Date Prev][Date Next]
Re: UTF8 vs T61
I have used the "Octet String" type as a transitional measure from latin1
to UTF8. Essentially you will be treating your strings as a a series of
bytes instead of characters. Since it is raw data, there is no
type-checking that is performed on the server side.
>From the OpenLDAP admin guide:
> Octet String 220.127.116.11.4.1.1418.104.22.168.40 arbitary octets
Azusa Pacific University
On Thu, 29 Nov 2001, Jan Stevens wrote:
> I am using Openldap 2.0.15 right now, which only accepts UTF8. I recently
> upgraded to this version , introducing some problems because characters like
> EUR and ö were accepted in the previous version (2.0.1) of openldap we used
> and not in the newer version.
> I read a lot about it on openldap.org and other newsgroups and I know I
> should enable UTF8 support in my userinterfaces. But, is there a way to
> (temporarely) support the mentioned characters in OpenLdap 2.0.15, without
> Has it something to do with LDAPv2 and LDAPv3, if so, how do I dow so?
> Regards, Jan Stevens