How to convert these strange characters? (ë, Ã, ì, ù, Ã)

How to convert these strange characters? (ë, Ã, ì, ù, Ã)

  1. Blog
  2. 15 November 2026
  3. 3 min read

Stefan Bogdanescu

Founder & Senior Architect

The "Mojibake" Trap: Diagnosing and Fixing UTF-8 Corruption

When your page displays ë, ì, or ù instead of expected characters like «, ï, or ú, it is almost always a classic encoding mismatch. You mentioned setting both the HTTP header to utf-8 and the MySQL connection charset to utf8. While these settings are correct in isolation, they do not guarantee that the data actually stored in the database matches the encoding your application expects to read. The most common culprit here is a legacy character set lurking deep within the database schema or the specific table/column definitions.

The visual corruption occurs because of how bytes are misinterpreted. If you have data originally saved in ISO-8859-1 (Latin-1) but your application reads it as UTF-8, the browser receives the raw byte sequence of a character like « (which is byte 0xC2 0xAB in UTF-8). However, if that same two-byte sequence is interpreted as ISO-8859-1, those bytes map to the characters à and «. The result on your screen is ë. This specific pattern—where a high-bit character splits into two printable ASCII characters—is the definitive fingerprint of Latin-1 data being read as UTF-8.

Simply adding <?php header('Content-Type: text/html; charset=utf-8'); ?> or executing SET NAMES utf8mb4 in your application code won't fix the data itself if the rows were inserted into a column defined as CHAR(50) CHARACTER SET latin1. The bytes are already there; the metadata just tells you how to interpret them incorrectly.

To resolve this, you must inspect and correct the character set definitions at every layer of your stack:

  1. Database Configuration: Run SHOW VARIABLES LIKE 'character_set_database'; to ensure the default database is not stuck in an old encoding. More importantly, check your specific tables. Execute SHOW CREATE TABLE your_table_name; and look for CHARACTER SET latin1. If found, you must alter the table:
    ALTER TABLE your_table_name CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
    
  2. Column Specifics: Sometimes the connection is set correctly, but individual columns retain their old settings. Ensure all text columns use utf8mb4. Do not settle for utf8 (the MySQL alias for 3-byte UTF-8) if you plan to store emojis or specific accented characters later; use utf8mb4 explicitly.
  3. Application Connection: In your database connection configuration (e.g., in Laravel's .env file), ensure you are using the full utf8mb4 string:
    DB_CONNECTION=mysql
    DB_CHARSET=utf8mb4
    

If the data was inserted via a legacy script that blindly assumed Latin-1, converting the table might result in garbled text if the original bytes were invalid UTF-8 sequences. In such cases, you may need to identify the problematic rows and manually reconstruct them or use a dedicated migration tool to handle the byte-level conversion safely.

Once the schema is corrected, you must ensure the application driver matches. If you are using Laravel, verify that your config/database.php file specifies charset: 'utf8mb4' and collation: 'utf8mb4_unicode_ci'. This ensures that when PDO sends a query, it explicitly tells MySQL to treat the incoming stream as UTF-8, preventing the driver from falling back to the old default.

After altering the table structure, you must run migrations or flush caches if your framework relies on compiled schema information. In Laravel, for instance, you might need to clear config caches:

php artisan config:clear
php artisan cache:clear

Finally, test with a direct insert of known UTF-8 characters using an escape sequence (like \u00E2\u00AE) or by copying from a verified UTF-8 source. If the output matches the input exactly, the encoding chain is finally synchronized. The key takeaway is that setting headers and connection strings only defines the expectation of the encoding; the actual data integrity depends on how those bytes were physically stored in the disk files backing your database.

Our network