Hallo,
I'v searched for an answer but did not found one yet.
I do have a openldap-2.3.43 server (centos 5.5.) in test and tried to add a ldif-file with my data using the apache directory studio (on mac os x).
As my name contains a german umlaut I do get an error adding 'Götz Reinicke' for the gecko.
Also for 'displayName', 'cn' and 'givenName' the 'ö' is automatically replaced by 'oe'.
If I change the entry in the ldap by hand in the apache DS, the 'ö' is accepted accept for the geckos. An 'ü' in 'o' is manually accepted to.
Any hints, explanations, suggestions?
Thanks and best regards,
Götz
Hi,
As my name contains a german umlaut I do get an error adding 'Götz Reinicke' for the gecko.
Do you mean 'gecos' with that? The 'gecos' attribute from the NIS-schema is an IA5 string [1], which is equal to ASCII. You won't be able to use special characters with that one.
Also for 'displayName', 'cn' and 'givenName' the 'ö' is automatically replaced by 'oe'.
If I change the entry in the ldap by hand in the apache DS, the 'ö' is accepted accept for the geckos. An 'ü' in 'o' is manually accepted to.
How is your ldif file encoded? 'cn', 'givenName' and so on are defined as SUB to 'name', which is defined with "Directory Sting" syntax [2] aka UTF-8.
Regards, Christian Manal
[1] http://www.alvestrand.no/objectid/1.3.6.1.4.1.1466.115.121.1.26.html
[2] http://www.alvestrand.no/objectid/1.3.6.1.4.1.1466.115.121.1.15.html
On Wed, 10 Nov 2010, Christian Manal wrote:
Hi,
As my name contains a german umlaut I do get an error adding 'Götz Reinicke' for the gecko.
Do you mean 'gecos' with that? The 'gecos' attribute from the NIS-schema is an IA5 string [1], which is equal to ASCII. You won't be able to use special characters with that one.
Also for 'displayName', 'cn' and 'givenName' the 'ö' is automatically replaced by 'oe'.
If I change the entry in the ldap by hand in the apache DS, the 'ö' is accepted accept for the geckos. An 'ü' in 'o' is manually accepted to.
How is your ldif file encoded? 'cn', 'givenName' and so on are defined as SUB to 'name', which is defined with "Directory Sting" syntax [2] aka UTF-8.
Regards, Christian Manal
When you decide which attribute is to store utf-8 string, look into libnss-ldap manual page to find out how to map other attribute to be used as filling for "gecos" NSS field.
Regards, DT
Hallo,
Am 10.11.10 15:47, schrieb Christian Manal:
Hi,
As my name contains a german umlaut I do get an error adding 'Götz Reinicke' for the gecko.
Do you mean 'gecos' with that? The 'gecos' attribute from the NIS-schema is an IA5 string [1], which is equal to ASCII. You won't be able to use special characters with that one.
jep 'gecos', typo on my side. I was thinking of something like that. Thanks for making that clear to me :-)
Also for 'displayName', 'cn' and 'givenName' the 'ö' is automatically replaced by 'oe'.
If I change the entry in the ldap by hand in the apache DS, the 'ö' is accepted accept for the geckos. An 'ü' in 'o' is manually accepted to.
How is your ldif file encoded? 'cn', 'givenName' and so on are defined as SUB to 'name', which is defined with "Directory Sting" syntax [2] aka UTF-8.
It's from what my text editor says UTF-8.
But now I do have also the phenomenon, that in the ldap the umlaut is replaced with a wired character and not replaced with 'oe' ....
I think, that the AD Studio makes something 'funny'. May be.
cheers . Götz
openldap-technical@openldap.org
-
Christian Manal -
DT Piotr Wadas -
Götz Reinicke - IT-Koordinator