I noticed is I backup my content tables and reimport all characters like quotes, apostrophes etc. become ascii ’

One workaround to this was to download the import file, convert to utf8 in notepad and import. However, apparently, you need only add the following command to the dump function:

--default-character-set=utf8

Thoughts? Is there something I'm missing?

Comments

joncianciullo’s picture

joncianciullo commented
Status: Active » Closed (fixed)

Actually I just realized that this only happens when I download the backup/restore .sql file and run in manually.

josepvalls’s picture

josepvalls commented
Priority: Critical » Normal
Status: Closed (fixed) » Active

I ran into the same situation.
Although the bug does not seem critical to me, the header in the SQL files created by BAM defaults to a UTF8 encoding but the file IS NOT UTF8.

ronan’s picture

ronan commented
Status: Active » Postponed (maintainer needs more info)

Are you sure the data is UTF-8 in the db? I'm not doing any character conversion so whatever encoding is int he db should be what's in the dump file.

ronan’s picture

ronan commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Is this still an issue? If so please reopen.