When I use IE8, I see that problem on sogo-demo.inverse.ca too.
The reason is bad interpretation/setting of encoding in IE8.
When I look to Page->Encoding, I see "Windows-1250". It is wrong, it must be UTF-8. Firefox uses UTF-8 and has no problem.

On my own server I solved it by setting:
AddDefaultCharset UTF-8
into
apache2/conf.d/charset file

This forces IE8 to use UTF-8 charset ;-)

The display glitch is fixed in revision 86a177d4a05deda193edc7d9e0fedca89758cadd.

I think I can close the ticket since the other encoding errors could be solved by fixing your Apache configuration.

Hello,

Thank you for information.

I'm not sure that forcing users to reconfigure their servers is the best solution. I my opinion SOGo should rather set charset meta properly.

Does SOGo use encoding other than UTF-8? If only UTF-8 is used - please verify and consider appling atteched patch (SOGo-1.3.0-utf8-fix.patch) - it should add

<meta http-equiv="content-type" content="text/html; charset=UTF-8" />

to every SOGo html page output (works well in our system).

Thank you,
Pawel

Please reopen an other bug for this.

What you propose is a quick hack but if things are to be handled by SOGo/SOPE instead of Apache, it should be handled by SOPE since it's SOPE that already handle the WOMessageUTF8 preference.