up

What happens is that Eclipse sends the commit encoded as UTF-8; the server running mantis is using a different encoding (probably latin1).
You can re-encode the commit log using iconv in the post-commit hook.
I don't think that mantis can handle this, it has no control over the external input and cannot reliably infer the encoding.

IMHO, UTF8 should be the only supported encoding from our side so we would break only when dealing with stuff not UTF aware...

IOW, we should see if and how checkin.php can be forced to use UTF.

On the other hand, mantis 1.2 is going to have a revamped source control integration based on plugins, so I recommend:

1. use UTF by default in checkin.php
2. do nothing if 1 is next to trivial to do

oh, and

3. check the new implementation as soon as possible in the development phase, so we can ensure it will work with UTF chars...

I think that (1) is nop, modulo changing the encoding on the DB. The problem is that you have to convert UTF-8 strings to whatever encoding the web server is using to display then properly, and the extension (mbstring) might not be available. And of course you'd have to convert all the HTTP input (which you cannot control) to UTF-8.
IOW it may a PITA if you do not control the whole stack (svn repositoty, database, web server).

Right now integrating SVN and Mantis is a mess for non US country.
I don't understand how a software like Mantis can support 38 foreign languages without be UTF-8 compliant.

The problem describe in this issue has 2 steps :

1. the command "svnlook log" has a bad encoding when it's call from an apache httpd svn hook. (see this post : http://svn.haxx.se/dev/archive-2004-09/0996.shtml)

2. Mantis don't accept UTF-8 encoding chars but at least ISO-8856-1 (latin1)

The workaround is :

1. Use binding svn API instead of an external call to svnlook
2. convert the valid UTF-8 string to latin1 and give it to checkin.php

I gonna attach a sample in ruby that work for me that anybody can convert into his favorite language.

I have made a mistake.
With the lastest and greatest version of Mantis and SVN only the step 1 is useful

Won't fix as this old source code integration support is being dropped in favour of using a more modern plugin approach with the SourceIntegration plugin.

Refer to 0011732 for more details and feedback.