Encoding problem

Commit messages are shown wrong, when they are not English. For example, we use Russian for commit messages, and as result:    [ATTACH=CONFIG]113[/ATTACH]    It is UTF-8, if remove "?".

Last updated 9 years ago

Hi ufna,  That does look like an encoding issue. Can you tell us how you're adding the commit messages? Are you doing it via a terminal, or an app like Tortoise?   Also, which OS is this on and do you have language support installed on there?   Cheers  Wayne

Hi Wayne,  Commit messages are added with both SmartSVN and Tourtoise. Client OS is Windows, server - Ubuntu, both have Russian language support. In SmartSVN revision history are shown correct, problem is only on uberSVN portal.  Regards, Vladimir

Just to let you know, I haven't forgotten about this. I'm currently working with QA to go through this usage scenario for the next release, due shortly. Multi-byte testing is performed for releases but this issue hasn't been seen internally or externally, until now.  It wouldn't surprise me to learn that this is a browser issue of some kind, though. Can you confirm that you've tried multiple web-browsers with the same result?

It works the same way on Chrome, Firefox and IE, bug still here.  If you want, I can create test repository with this problem and give you access to it.

Thanks ufna but we really need to be reproducing this in-house, under controlled conditions.  If for some reason we're not able to do this in the next few days then I'll be back in touch. Appreciate the offer :)

There is a solution to this case? It is happening to me with Portuguese language.  In the dashboard is not showing correctly the UTF8 character with accentuation when the post came from Subversion commit. I am using the latest uberSVN core (13.02.3153-2) in a Debian Linux and committing through TortoiseSVN. Debian language locale is configured to pt_BR.UTF-8.  The problem occurs only with the commit comment. If I do the comment directly in the dashboard interface there isn't problem. And browsing in the repository log there isn't error too.  [ATTACH]357[/ATTACH]  [ATTACH]358[/ATTACH]