Used charset in ldap tree

[Frank Matthieß]

Dieter Kluenter [2005-07-20 16:13 CEST]:
> Frank Matthieß <frankm at lug-owl.de> writes:
[...]
> 
> > I saw that the webinterface converts all values with special characters
> > to base64. This seems to be base64 encode iso-8859-15. Is it right?
> 
> It has to be UTF-8, and distinguish between data presented by a client
> and data stored in the directory.
> If a client receives say iso8859-15 encoded data, this data have to be
> converted to UTF-8 prior to presenting the data to the directory
> server. The other way round, the directory server, in most cases,
> presents UTF-8 encoded data to the client and the client may convert
> UTF-8 to the given locale. In some cases the data exchanged between
> client and server is enclosed in LDIF (LDAP Data Interchange
> Format). This format accepts unicode character strings that contain
> characters above U+007F (byte 0x7F) as base64 encoded string.

Thanks for explaning this in detail.

Ok. So i translate an iso-8859-15 ldif file to an utf-8 encoded file and
should encode the values with special characters with base64 too.

Frank.
-- 
Frank Matthieß

A: Because it messes up the order in which people normally read text.                                                                                     
Q: Why is top-posting such a bad thing?                                                                                                                   
A: Top-posting.                                                                                                                                           
Q: What is the most annoying thing on usenet and in e-mail?
 -- Antony Stone auf netfilter at lists.netfilter.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.kolab.org/pipermail/users/attachments/20050720/c490ed7b/attachment.sig>