With the Client 1.0.5 version, content export in CSV file is using "encode in UTF-8 without BOM" and user must use some other code programe to change it into "encode in UTF-8" in order to view the right content in Excel.
It will be thanks a lot for export using the "encode in UTF-8" option, in order to let the user use the CSV file directly in Excel.
Thanks a lot.
When you open the CSV file using the Get External Data > From Text in Excel, it asks you for various options, including encoding. You can force it to use UTF-8 encoding.
Regards,
Michał
but in default, every normal user alway use "double click" for opening it, and Excel open it with UTF-8 with no BOM v_v ...
for us, the "clever" users, we can use Get External Data or use some Text Editor else for this problem, but the question here is for normal users.
If could in the 1.0.6 will be very good for me and lot other using unicode project managers.
You're right. I will fix this in the next version.
Regards,
Michał