wish of those help If you're seeing multiple bytes for what should be single characters, chances are it's already in UTF-8. Bear in mind that ISO-8859-1 is a single-byte-per-character encoding, whereas UTF-8 can take multiple bytes - and any non-ASCII character does take multiple bytes. I suggest you open the file in a UTF-8-aware text editor, and check it there.
Character Encoding utf8 to latin1, explain these 2 characters
this will help The encoding is important is so far as it determines what characters you can store. You cannot save "日本語" or other similar "exotic" characters in a latin1 encoded column. If you may be required to do that, you'll have to choose an encoding for that column that can store those characters. Note that there's also the connection encoding. Any client that connects to the database (e.g. phpmyadmin, your own PHP scripts, a database admin utility, any application etc.) implicitly or explicitly specifies a connection encoding, which denotes what encoding that client would like to receive. You can have a latin1 encoded column and query data from it via a connection set to utf8 and MySQL will convert the data on the fly and give you utf8 encoded data nonetheless.
character encoding issues when migrating gyroscope app from mysql (latin1) to mariadb (utf8)
this one helps. If you cannot use latin1 as the default system encoding for whatever reason, here's a quick solution: Leave the data dump as-is. Even though it's latin1 encoded, it can be imported as utf8.
mysql> create database ezine character set utf8 collate utf8_general_ci;
mysql -uwebuser -p --default-character-set=utf8 ezine < dump.sql
like below fixes the issue You are trying to import an UTF-8 file that contains the character … (“horizontal ellipsis”, Unicode code point 2026). This character cannot be encoded in LATIN1, so you will not be able to do that.