Update : We had been using the Ruport gem in our time-tracking system Tempo to provide the CSV exports when I first posted this question. I work in a few different environments myself and this is definitely an issue that will becoming up again. Net-ers and folks on any frameworks handle this. I'm doing this on a Rails stack, but curious how the. What's the simplest way of generating that Just-For-Excel file that will correctly support UTF8, my dear Stack Overflowers? If that simplest option only supports the latest version of Excel, that's still of interest.
It looks like no matter what, I'm probably going to want to continue offering a plain-old CSV file for the folks who aren't using it for Excel anyway, and a separate download option for Excel. SpreadsheetML, using custom XSLT, or generating the new Excel XML format via templating. there are some three or four ways to get XML data into the various recent versions of excel, and those would support UTF8, in theory.supplying the data in an HTML table with an Excel mime-type or file extension (not sure if this option supports UTF8).supplying a UTF-16 Little Endian TSV file which Excel will interpret correctly, but which won't support multi-line data.
So I've done a bit of digging (the Intervals folks have a interesting post about it here), and there are some limited if ridiculously annoying options out there. The problem is when you open a typical UTF8 CSV up in Excel, it reads it as ANSII encoded text, and accordingly tries to read two-byte chars like ø and ü as two separate characters and you end up with fail. And we can export the user-supplied data into CSV no problem - it's still in UTF8 at that point. So we have this web app where we support UTF8 data.
0 kommentar(er)
