Hi, we'd like to be able to export views as Unicode text to avoid CSV character corruption issues.
That is set in configuration.
Look for System Defaults and Default Encoding of CSV Files (Export). Go for UTF-8.
Thanks. The only thing I'm missing is an UTF-8 BOM option.
Without a BOM header, Excel doesn't recognize the encoding automatically.
Can you shed more light on the Excel connection here?
Are the CSV files not readable?
How would that relate to https://xtrf.userecho.com/forums/6-xtrf-knowledge-base/topics/469-how-to-import-csv-into-an-office-excel-sheet/ ?
Yes, we can use the text import wizard, but it would be nice to be able to open the file directly.
I found an interesting article on the subject. The author says two things:
So the question is should we adjust to Excel, or to general recommendations? :)
I'm guessing that a lot of people will open the CSV files in Excel directly.
If the encoding is UTF-8 BOM the content will be displayed correctly and you can save it as an Excel workbook (Excel cannot save to Unicode CSV).
My vote would be to adjust to Excel, since I would think that the majority of users will open CSV files in Excel.
I would vote for adapting it to Excel as well. Is this perhaps already being implemented?
Would it be feasible to have both UTF-8 and UTF-8 with BOM as export options?
Customer support service by UserEcho