On 9/17/15 8:12 AM, Maik Nergert wrote:
Hexcode from ü → c3 bc is encoded again to → c3 83 (Ã) and c2 bc (¼) (http://www.utf8-zeichentabelle.de/)First I've upgraded RT from 3.8 to 4.2 with mysql db (utf8) and everything went smoothly.
Can you confirm that the umlaut can be sucessfully added to the database after the upgrade but before the postgres migration?
I'm trying to determine if the issue happened during the upgrade or because of rt-serializer.
