This content has been marked as final. Show 4 replies
Hi Dirk,1 person found this helpful
Most likely, the Automatic CSV encoding attribute is set to 'Yes' for your application. If you're running your application in German, then the CSV file will be encoded in WE8MSWIN1252.
Can you try setting Automatic CSV Encoding to "No" (in the Globalization attributes of your application)? The CSV file will then be encoded in UTF-8 - which means that your Windows users may not open it directly but, instead, have to do a data import and specify utf-8 character set.
thanks for your answer.
Yes, the automatic csv encoding attribute is set to 'Yes'.
Setting it to 'No' does help, the csv is now opened correctly in Numbers on a mac, but as you said on windows the users will not be able to open it directly.
So fixing the issue for mac users will kind of break it for windows users.
Is there a way to set that csv encoding parameter dynamically based on what os the user uses?
Is your CSV export emanating from an Interactive Report?
P.S. I'm curious - do you have Excel for Mac? I've tried opening a utf-8 encoded CSV file on Mac, and it always becomes corrupted.
I just had the same Problem and could fix it by setting the automatic CSV encoding to YES (language is set to German "de" ).
I'm using Excel for Mac.
Don't know if that helps, just wanted to contribute.