in the mailer we have a similar problem, we basically do: - try the charset if supplied (dunno if you can specify charsets in ldap) - if the user has a viewing charset set, use that - fallback to the locale charset, if available.
the locale charset should do most of the time, but you proably need a manual override too. On Thu, 2004-02-05 at 16:33 -0500, 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 > <[EMAIL PROTECTED]> _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
