Re: [Evolution-hackers] Non-UTF8 encodings in LDAP data

[Chris Toshok <toshok ximian com>]

There's actually a bug about this (49808).  The fix will most likely
have to be a per-server setting that allows the user to set the
character set of the data on the server.

Chris=

On Thu, 2004-02-05 at 13:33, Scott MacLean wrote:
> I've recently found a problem with the Evolution address book's 
> handling of LDAP data that is not UTF8-encoded: any LDAP attribute
> string containing non-UTF8 characters is truncated at the first such
> character.
> 
> To see this in action, create an LDAP entry with a name containing
> non-UTF8, non-ASCII characters. Pointing Evolution to this directory
> server will result in the name being truncated - this affects both the
> book and autocomplete views.
> 
> I have built (and attached) a patch against Evolution 1.4.5 that works
> (read 'kludges') around this by assuming that an invalid UTF8 string is
> ISO8859-1-encoded and converting it to UTF8, but I am unsure how to go
> about determining a string's encoding and converting it appropriately in
> the general case.
> 
> Any advice or pointers would be much appreciated.
> 
> Thanks,
> 
> Scott MacLean
> <scott nit ca>