this issue can be fixed by setting right collation for tables and columns - to utf8_unicode

kinguru,

MySql manual says that collation is about comparing strings and so... Are you sure it can affect on how Mantis shows strings from database?

VYu, did you get the issue resolved on your bug tracker?

vboctor,

no, sorry, I have found finally that my problem is other than reported here by kinguru. My problem was that after upgrading from 1.0.6 (but with utf-8 database already) to 1.1.2 Mantis shows russian content with strange chars (2 strange symbols per 1 russian original), and I have solved it according to recipe from http://www.mantisbt.org/forums/viewtopic.php?f=3&t=4467&p=11426 by exporting database to sql-file, replacing SET NAMES latin1 to SET NAMES utf8 and importing data back.

Marked as confirmed, since we seem to have a similar issue with our bug tracker.

Why issue 8763 was closed? 8763 is not duplicate.
Here - string from MySql. There - string from string_russian.txt.
*.txt has no relation to MySQL and can not be fixed by MySQL collation.

I'm agree with klimrmad. 0008763 is not duplicate of this issue.

I don't know about this issue, but i know what i have not problem with see russian letters on anywhere in my mantis. I start use mantis before 1.1.1 version ...
If some additional information about my configuration required - i can get it.

P.S. ????

P.P.S I saw that my mantis databases use cp1251 collation - may be it will be better use utf8. But i have not problem cause i use only english and russian language.

hm... - on my P.S. i wrote word "test" in russian language ;)

Speakus, ? ????????? Mantis ? ?????? 1.0.1, ????? ???? ?????? ???? latin ? ????????? ????? ???? win1251. ?????? ????? ?????, ? ???????? ???? ????? ;)

Speakus, I'm use Mantis from version 1.0.1, when db's charset latin and russian language - win1251. But now I use 1.1.6 with db utf8-general_ci and language utf-8 - problems new ;)

Please test with Mantis 1.2.0a2 or later with a UTF-8 database and a UTF-8 localisation. This issue should be resolved.

Who made russian translation?
Can I translate too?

Of course. Please use the translation interface at http://translatewiki.net. Russian currently has 6[1] untranslated messages. Just register/create an account, follow instructions on how to get translator rights, and use [1] to update your translations.

[1] http://translatewiki.net/w/i.php?title=Special:Translate&group=out-mantis&language=ru

In order to solve this issue for my mantis I've exported it's database, replaced latin1 with utf8 and imported it back. I think mantis should have mysql/postgres charset selection in installation script

I have changed line 592 to:

$sqlarray = $dict->CreateDatabase( $f_database_name,array("MYSQL"=>"CHARACTER SET utf8 COLLATE utf8_general_ci") );

Since then any installation on a NONE UTF default database is correct...

There is no need to specify COLLATE utf8_general_ci because that is the default setting MySQL uses anyway. See http://dev.mysql.com/doc/refman/5.0/en/charset-unicode-sets.html

What version of MySQL are you using?

Can you please type from the command line (ssh):

mysql -h your.database.server -u adminuser -p

show create database bugtracker;

Where your.database.server is the hostname of your MySQL server. adminuser is a MySQL user that has permission to create/show databases. It'll ask for the password for adminuser as well. bugtracker is the name of your Mantis database on the MySQL server.

Let me know what the result is. It should tell you what the character set on the Mantis database is.

I will explane why it is needed.

For the past month I have made a few installation of VANILA Zend Core + MySQL.

I am talking about a standart installations of without setting's changed.

What I have seen is that, on PC's that have Windows installed in a local settings (in my cases in Hebrew, dont thy that at home... it's sucks), the default database collation is hebrew_general_ci, and not UTF8 (as you would expect).

That is teh reasone I think the COLLATE MAST be set (at least for MySQL, I have not tested on other's).

I will post the -h info when I get to a PC that I can perform this installation.

OK thanks for the explanation, I'll fix it. I was just going on what I had read from the documentation. It doesn't hurt to specify the collation :)

On Hebrew language support, did you read the comment at the bottom of http://dev.mysql.com/doc/refman/5.0/en/charset-unicode-sets.html

Yes I did... :)

But I would really like to see the user who would use Nikkud in typings ;)