luk , Thanks. I use that workaround and it works fine. However, our bloggers are not technical and find it very difficult to even open a single report using this workaround. And to be able to do it for 12 other languages by different teams everytime they need a report is not practical. It is surely a coding issue that needs to be modified from Khoros 's end.
It is surely a coding issue that needs to be modified from Khoros 's end.
Well, I don't think it's that easy, afaik Excel by default opens csv files with ISO-8859-1 encoding, but the world has moved on for many years and UTF-8 is de-facto standard. Imagine you want to use your csv data in let's say python or whatever language to do programmatic analysis but Khoros gives you ISO-8859-1 encoded data, it would be a nightmare. So it's not that Khoros couldn't encode the exported csv that way, the question is more: Would it be better?
PS: As I mentioned above, I'm not using excel at all for several years, so take the above with a grain of salt.
EDIT: A quick google points me to this https://answers.microsoft.com/en-us/msoffice/forum/all/excel-read-csv-set-utf-8-as-default-for-all-csv/62eb4068-fc70-4f9b-9bd7-c904713beaf0 so I would assume something like changing a registry value to switch the default encoding to UTF-8 when opening csv files would still work (also not using windows 😉) and might solve your problem (if you can then change your registry, might be a problem on a managed device)?
