Mantis migration - encoding mismatches

Added by Leszek Ciesielski over 9 years ago

I am using the svn-head version of Redmine. When I try to migrate an existing Mantis setup (databases use LATIN2 encoding AFAIK), I can either:
- migrate with encoding[UTF-8] (I just leave the default) - this botches the user names and ticket text quite a log
- try to change the encoding used by rake - this breakes with
"encoding [UTF-8]: LATIN2

rake aborted!
Validation failed: Lastname activerecord_error_invalid"

Any ideas what encoding could work? And BTW, could the script just detect it, like phpmyadmin does? Or is this somehow not feasible?

Replies (2)

RE: Mantis migration - encoding mismatches - Added by Leszek Ciesielski over 9 years ago

bump. Could anyone provide some help? Should I file a bug report? I can attach a trimmed-down version of mantis DB snapshot (original is 40MB compressed), but before I start working on it I'd like some confirmation that it will be used :-)

RE: Mantis migration - encoding mismatches - Added by Thomas Lecavelier over 9 years ago

Please, open a defect issue with the same details as provided here. Encoding/charsets is quite a mess with Ruby...

(1-2/2)