Accents get messed up when using the Export function

[Francois Lavigne]

When I export my database in SQL format, the accents get replaced by incorrect characters. Here are some examples:

• ç becomes √ß
• é becomes √©
• à becomes √†

I tried to open the .sql file using different encodings but none gives me the correct accents. 

This is the headers of my file:

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;

Everything should be in utf8.

[Rowan Beentje]

Hi Francois,

We believe encodings in exports and imports are handled correctly - although there's always edge cases...

Looking at the example you gave, the character mappings look like the characters are being translated to a Western (Mac OS Roman) character set at some point. This could be due to a mishandled export, due to a program opening it using that encoding, or due to the display layer (eg a Terminal application) being set to a different display encoding.

What program are you using to open the file?

Rowan

> --
> You received this message because you are subscribed to the Google Groups "Sequel Pro" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sequel-pro+...@googlegroups.com.
> To post to this group, send email to seque...@googlegroups.com.
> Visit this group at http://groups.google.com/group/sequel-pro?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[François Lavigne]

I'm using:
OS X 10.8.2
Sequel Pro 10.0.1 for exporting
TextMate 1.5.11 and I then try the "Re-Open with Encoding"  function with all the available encodings, none give me the correct options.

I tried with and without the "Add UTF-8 BOM to output"

I attached the outputted file (without the sensitive information). You can find all mistranslated characters by searching for √

Thank you very much for the support!