![]() ![]() This does not solve the problem! You still got a miss-match. Some people do not understand this problem, and so they simply recommend to use HTML entities like: If you do use UTF-8, and you still got problems with characters not displaying correctly, keep in mind, if there is a miss-match between the encoding of the data in your database, database-connection or static file and the specified encoding in the HTTP Content-Type header, certain letters will be replaced with gibberish characters (Aka Mojibake). It also avoids problems with user input on HTML forms, as well as browsers different ways of handling characters that fall outside of whatever "limited" character encoding you might otherwise use – could be Latin-1 - ISO-8859-1). UTF-8 is recommended for the web because it has support for all unicode characters, and thereby allow you to use language-specific characters without having to use HTML entity replacements. CREATE DATABASE name_of_new_database CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci Why using UTF-8 is recommended
0 Comments
Leave a Reply. |