> * Ralf Hildebrandt <[EMAIL PROTECTED]>:
>
>
>> Which details do you want :)
>>
>
> Tomas sent me a patch that fixed the problem immediately. Dunno if it
> made it to CVS or not.
Fixed in 1.5.1cvs.
http://cvs.sf.net/viewcvs.py/squirrelmail/squirrelmail/functions/i18n.php?r1=1.202&r2=1.203
Shoul
* Ralf Hildebrandt <[EMAIL PROTECTED]>:
> Which details do you want :)
Tomas sent me a patch that fixed the problem immediately. Dunno if it
made it to CVS or not.
--
Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED]
Charite - Universitätsmedizin BerlinTel. +49 (0)3
* Tomas Kuliavas <[EMAIL PROTECTED]>:
> You forgot to mention your squirrelmail version.
I suck. It's CVS HEAD.
> In some cases name of used SquirrelMail translation can help too.
de_DE, but it doesn't work with English, either.
> LDAP entries are usually stored in utf-8 charset.
Indeed!
>
> When I use "Compose" and then click on "Addresses" to query the LDAP
> Server
> for
>
> FrÃmmel
>
> I get no results at all, although the LDAP server contains 3 entries. It
> seems that the query string is not being UTF-8 encoded.
>
> Likewise, with the result when the result set contains Umlauts
When I use "Compose" and then click on "Addresses" to query the LDAP Server
for
Frömmel
I get no results at all, although the LDAP server contains 3 entries. It
seems that the query string is not being UTF-8 encoded.
Likewise, with the result when the result set contains Umlauts, I get in the
"N
