CSV encoding

I’m not sure of the exact problem here – we deal with content which includes foreign characters without problem, so perhaps this is an issue related to your database encoding.

Can you try to run an export with some Brazilian text on a completely different install to check?

Also, please report which plugin and WP version you are using

Hi I exported my wp tables users and usermeta from this instalation to a new one with no plugins except yours but i still have characters problems when export.
Im using wordpress 4.5.2 and Coursepress pro 1.3 plugin
Im reporting the problem but already solved with another plugin that could export the same database without giving me those characters problemns.
If you need any other information to solve the problem you can ask me.

Same problem here

change the export-user-data.php line 2254 to:

return $string;

now csv works with pt-br utf-8

This topic is a little older, but I couldn’t find anything newer. I have the same problem, exporting German characters such as ?, ?, ?, ü doesn’t work. I tried utf-8, Latin1 etc. when opening the csv in LibeOffice, but in all cases the charcters were broken.
I just saw that it is not an encoding error. ? for example is displayed html style as ö
Still not pretty and I have to search and replace every of those special characters. I wonder if that is a problem of the Exporter Plugin or from WordPress itself?

• This reply was modified 7 years, 7 months ago by Tilman.
• This reply was modified 7 years, 7 months ago by Tilman.

Same problem. I found the semicomma ; is missing in the file for example, ? is å but showing &aring instead. It’s due to that excel splited the line whenever there is a “;”, so I opened the csv file in a text editor and paste back to Excel/Openoffice, everything works fine now.

• This reply was modified 7 years, 7 months ago by clarezoe.

The solution of @andremacola works. All special characters are replaced with the special_characters function (called in export-user-data.php on line 1126 and 1131) into their html equivalents. Changing line 2254:
return htmlentities( $string, ENT_COMPAT, 'UTF-8' );
into simply
return $string;
stops that. I have no idea why this replacement is made anyways, but I believe there was some good idea behind it. In any case, it works now and all German characters are displayed correctly.