View Issue Details

IDProjectCategoryView StatusLast Update
0008230mantisbtlocalizationpublic2009-06-26 12:06
ReporterMartin Fuchs Assigned Tosiebrand  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.1.0a4 
Summary0008230: Character encoding in Mantis 1.1.0a4 on the Bugtracker site
Description

The database content of the Mantis Bugtracker (http://bugs.mantisbt.org) should be converted into correct utf-8 encoding. It seams the preceding versions 1.1.0x before 1.1.0a4 wrote utf-8 encoded strings using an database connection in latin1 mode into the utf-8 database. This lead to double encoded strings.

If you look for example at this page
http://bugs.mantisbt.org/view.php?id=7647
you see various scrambled characters, e.g. "Einträge" instead of "Einträge" or the cyrillic words in the atteched comments.

Additional Information

It may be possible to solve the problem with the following steps:

1.) Export the MySQL database content while converting from utf-8 to latin1:
mysql -uUSER -pPASSWORD INSTANCE --default-character-set=latin1 > mantis-db.sql

2.) create a new database with utf-8 as default character set.

3.) Connect to the database with the MySQL client and import the dump file in utf8 mode:
mysql -uUSER -pPASSWORD INSTANCE --default-character-set=utf8
source mantis-db.sql;

TagsNo tags attached.

Relationships

child of 0004084 closedsiebrand [all lang] Use UTF-8 codepage 

Activities

Martin Fuchs

Martin Fuchs

2007-08-03 19:28

reporter   ~0015341

To make things a bit more clearer: This is just about fixing the strings included in all issue texts, which were entered with Mantis 1.1.0x before 1.1.0a4 (all versions which used utf-8 als encoding for the HTML code). In the current version 1.1.0a4 of Mantis there is no problem. Also there is no problem with issued entered with Mantis before 1.1.0 (using nun-unicode encodings)

siebrand

siebrand

2008-09-10 17:36

developer   ~0019369

Solved in current version (Mantis 1.2.0a2)