No feedback.

And that's how it is supposed to be. If the client and the server 
understand UTF-8, we will use it. Do the screen elements that contain 
foreign characters render correctly on your device?

What happens if send messages with latin2 characters, is the sent 
message encoded properly.
No, and it doesn't make any sense because it only hides the real problem.

The workaround works.

But I have a screenshot of the compose page's source. Here you can 
see, that the form posts the actionID in UTF8.

Is it possible to set the MIMP pages to latin2 (8859-2)? Since our 
users will send mails in hungarian. I think this would solve the 
problem as well.

I doubt that. Do you have any information to back up this opinion with?

Ok, that's the problem. compose.php expects

"A címrészlet teljessé egészítése" (in 8859-2)

but gets

"A c?­mr??szlet teljess?? eg??sz?­t??se" (in UTF8)

When I try to expand names.

Might be something related to codepages. The form posts the actionID 
in UTF8. Maybe compose.php waits for an ISO-8859-2 (latin2) coded value?

This means that compose.php isn't properly translating the string on 
the second load, though - any idea why that might be?

I'm using Horde framework with hungarian localization.

In MIMP's compose page I could neither send the mail nor expand the 
recipient address with the corresponding links.

Figured out that the form in templates/compose/compose.inc sets the 
actionID to the localized name instead of the original english action 
names while the compose.php checks for the english names. Therefore 
nothing happens when I click any of the links.



A quick workaround was replacing

case _("Expand Names"):

to

case _("A c?­mr??szlet teljess?? eg??sz?­t??se"):

... and so on

in the switch($actionID) of compose.php



regards,

Richard