Open aaronkaplan opened 9 years ago
The manman-fetcher now has a new option 'utf8' which can be added to the call. This option adds the following to the call to mysqldump --default-character-set=utf8
The resulting export has different size and yields a different sha1 hash. However a quick check didn't fix the issues with names like 'Jürgen'....
On Mar 16, 2015, at 9:57 PM, equinox0815 notifications@github.com wrote:
The manman-fetcher now has a new option 'utf8' which can be added to the call. This option adds the following to the call to mysqldump --default-character-set=utf8
The resulting export has different size and yields a different sha1 hash. However a quick check didn't fix the issues with names like 'Jürgen'....
Thanks!
@schlatterbeck : can you try if this fixes some of the import encoding issues we are seeing?
— Reply to this email directly or view it on GitHub.
Make sure that the encoding of the mysql manman DB export match what we need. Also make sure that the encodings inside the mysql DB are uniform (no double encodings)