-

Wed, 23 Dec 2020 23:22:58 +0100

adminsforum@hubzilla.org

elmussol wrote the following post Wed, 23 Dec 2020 23:22:55 +0100

4.6>5.0 UTF-8 scramble
Since updating from 4.6 to 5.0 I (and other elsmussols.net members) are getting UTF-8 problems. Random example from a post by @lotfi:

Si Ã§a tâ€™intÃ©resse, "I'm Your Man" c'est aussi un superbe film documentaire sur LÃ©onard Cohen. C'est lÃ  que j'ai dÃ©couvert pour la premiÃ¨re fois Martha Wainwright

It there a possibility that one of the db tables lost its encoding somehow? If so, where should I be checking? I have checked dbsync was successful on the major version update and on the subsequent point ones.

If more info is need, please ask.

Fri, 01 Jan 2021 17:30:04 +0100

Beni Grind ~HB9HNT

navigium@grindcore.ch

@elmussol Today I had the same problem when trying to migrate to #postgres. I couldn't get the encoding right, no matter what collation or encoding I set. Astonishingly what solved it in the end: I dumped the DB to disk using mysqldump, then deleted the database and recreated it from the dump.

Sun, 03 Jan 2021 16:32:01 +0100

Beni Grind ~HB9HNT

navigium@grindcore.ch

@elmussol

Re 1. I don't think so, you just have to make sure you have a backup. Of course it's saver to stop Hubzilla because you loose data if you have to go back to the backup.

Re 2. If I understood what I read correctly, these values are mainly defaults. You also have to update the encoding of the string fields in each table. I followed something similar to this article: https://techbriefers.com/how-to-choose-your-mysql-encoding-and-collation/