From: Christoph N. <en...@ap...> - 2001-06-05 17:06:15
|
On Tue, 5 Jun 2001, Knut Sander wrote: > > I chose the directoryString (UTF-8 format) type since it should allow t= he > > international characters. However, when I try to insert the string 'im > > k=3DE4ppele 8' I get the error: > >=20 > > apuhomestreet: value #0 contains invalid data >=20 > Hi Christoph, >=20 > did you encode your data as UTF8-string? The 0xe4 above (=E4 =3D ae) look= s > like you try to add a latin1 string, but this is not a legal UTF8 byte > sequence. Hm...that seems to be correct. I checked the output from the "debug". =20 This is the string I am sending to the server: 0040 04 13: STRING =3D 'apuhomestreet' 004F 31 14: SET { 0051 04 12: STRING 0053 : 69 6D 20 6B E4 70 70 65 6C 65 20 38 __ __ __ __ im k.ppele= 8 005F : } Any recommendation on which encoding I should user in LDAP to support international characters? Is UTF8 really the way to go? If UTF8 is the way to go, how should I go about converting data that is=20 in iso-8859-1 to UTF8? A quick search on CPAN turned up "Unicode::MapUTF8" and "use utf8" pragma in perl 5.7. Anyone have experience with either of these? Also, where might I find good documentation on how these character sets are defined? Thanks for all the help and insight. - Christoph |