Closed seahindeniz closed 9 years ago
There is no problem with encoding of utf8mb4 characters.
Since v1.5, you need to add the extension to the filename, so if you want to compress with bz2, you will need to to:
$dump->start('ydk/'.time().'sql.bz2');
My point is not the utf8mb4, is text file encoding.
Sorry, I misunderstood you. Since mysqldump-php doesn't write any header to the output file, may I suggest you to try another text editor, one with an option to select utf8 encoding? Looks like your editor is wrongly guessing the file encoding and that some utf8 bytes are confusing it. El 06/02/2015 20:32, "traBolic" notifications@github.com escribió:
My point is not the utf8mb4, is text file encoding. [image: ekran alintisi] https://cloud.githubusercontent.com/assets/5789670/6086065/9b002f7c-ae47-11e4-9a93-4c5483ab300b.PNG
Reply to this email directly or view it on GitHub https://github.com/ifsnop/mysqldump-php/issues/76#issuecomment-73298156.
Hi, earlier I told u about the utf8mb4 character set problem and you solved. This time, when I run the codes using this
And the file saved fine.
But somethings not right.
If I run the codes and db>table>field has '🐈', file saved as ANSI encoding and the cat looked like 🈠If field has not the '🐈' file saved as UTF8 without BOM
Thank you for solving the problems