Jan Schneider wrote:
I have this problem with Horde-3.3.2 and IMP-4.3.2:
[...]
With "English (American)" locale:
Ügyfél

With "Magyar" locale:
&ANw-gyf&AOk-l

The latter is the same displaying as with the folder's name on the filesystem:
# ls -1 user/Maildir/
[...]
.&ANw-gyf&AOk-l/
[...]
It has to be an issue with your mail server then, because non-ascii characters in regular folders work perfectly fine in the latest (and any older) release.

But if it is working with one locale (English (american)), and it doesn't with another (Magyar), how could this be a bug in my mailserver?

No idea. But changing the language also changes the system locale, and this might have any side-effects. And of course, you have the iconv/mbstring extensions installed, don't you?
My system is OpenBSD. I have iconv installed and mbstring configured with php.
$ php -i |fgrep mbstring
mbstring.detect_order => no value => no value
mbstring.encoding_translation => Off => Off
mbstring.func_overload => 0 => 0
mbstring.http_input => pass => pass
mbstring.http_output => pass => pass
mbstring.internal_encoding => no value => no value
mbstring.language => neutral => neutral
mbstring.strict_detection => Off => Off
mbstring.substitute_character => no value => no value
$ php -i |fgrep iconv
Registered Stream Filters => string.rot13, string.toupper, string.tolower, string.strip_tags, convert.*, consumed,convert.iconv.*, zlib.*
iconv
iconv support => enabled
iconv implementation => libiconv
iconv library version => 1.11
iconv.input_encoding => ISO-8859-1 => ISO-8859-1
iconv.internal_encoding => ISO-8859-1 => ISO-8859-1
iconv.output_encoding => ISO-8859-1 => ISO-8859-1

It seems that IMP doesn't even try to convert the folder names, because it is displayed in the "native" way, exactly the same as on the filesystem, no?

Daniel

--
LEVAI Daniel
PGP key ID = 0x4AC0A4B1
Key fingerprint = D037 03B9 C12D D338 4412  2D83 1373 917A 4AC0 A4B1
--
IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]

Reply via email to