RE: [LDAPsh-users] unicode

[Rafael C. <Raf...@li...>]

Hi Frederic,
This is the normal behaviour. "vi" work in LDIF format and LDIF must =
encode in base64 values with special characters. Just imagine an entry =
with the attribute "comment" having the following value:

"During holidays, please contact me at:
Home in California: +1 111111111
Home in Italy: +39 1111111"

If this value would not be base64 encoded, there would be a confusion =
because the carriage returns would be interpreted as the end of the =
value and nest lines as new attributes assignment!

So, if you want to enter/edit accented fields, I recommend you using =
directly the LDAPsh functions "add" or "replace".
To view the encoded characters, using dump will show UTF-8 encoded =
strings, you can decode them with perl native Unicode functions or using =
a module like Unicode::MapUTF8.

Finally, I'm curious to know what happens if in an LDIF file I use =
accented characters. Will they be correctly set in the attribute value?

Rafael

-----Original Message-----
From: Frederic Gobry [mailto:fre...@sm...]=20
Sent: jeudi, 15. janvier 2004 11:17
To: lda...@li...
Subject: [LDAPsh-users] unicode

Hi,

Sorry if this is a FAQ, but the ml archives are unavailable :-)

I would like to enter/edit accented fields in LDAP via
ldapsh. However, when I run=20

	vi 'cn=3DSome CN'

...accented fields are displayed in base64 form.

Am I missing sth ?

Fr=E9d=E9ric

--=20
 Fr=E9d=E9ric Gobry       SMARTDATA    	 =20
                      http://www.smartdata.ch/
 PGP: 5B44F4A5        Lausanne - Switzerland
                      +41 21 693 84 98