0006148: Upgrading from 1.0.0a2 to 1.0.0rc1 is mixing up some characters in the database

ID	Project	Category	View Status	Date Submitted	Last Update
0006148	mantisbt	upgrade	public	2005-08-17 03:47	2009-06-26 12:01

Reporter	TomR	Assigned To	grangeway
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	no change required
Product Version	1.0.0rc1

Summary	0006148: Upgrading from 1.0.0a2 to 1.0.0rc1 is mixing up some characters in the database
Description	When upgrading database to 1.0.0rc1 some of my characters are so shows € as â‚¬ under 1.0.0rc1 and show ë as Ã« However I only upgrade database and programs.
Tags	No tags attached.

TomR 2005-08-25 14:45 reporter ~0011294	Can anyone verify this. I want to upgrade to 1.0.0rc1.

TomR 2005-09-07 05:12 reporter ~0011348	When I look in both databases, the data is identical, so there must be something different in the programs between 1.0.0a2 and 1.0.0rc1 which cause data to display different. Can anybody please give some advice.

TomR 2005-09-07 06:36 reporter ~0011350 Last edited: 2005-09-12 03:24	After some testing my problem was solved by putting $s_charset = 'UTF-8'; in lang/dutch_strings.txt See also 0004195

jlatour 2005-12-07 09:26 reporter ~0011718	Any idea how you ended up with UTF data in your database? As far as I know, only Chinese, Japanese and Slovene have UTF codepages.

Martin Fuchs 2007-09-03 06:06 reporter ~0015563	The relevant change is that of entry 0006782: Now the database connection is correctly using UTF-8 as character encoding. Mantis 1.1.x versions before 1.1.0a4 stored incorrectly encoded data into the database, which was corrected with this patch. However the incorrect data is not automatically fixed. You have to do this manually if there are any problems.

TomR 2008-11-29 06:21 reporter ~0020105	Can be closed.

grangeway 2008-11-29 08:33 reporter ~0020108	Thanks Tom - marking resolved as requested. Paul