News for hackers. Stuff that matters.
Re:I was wrong about spreadsheets (2017) by phonon on Friday July 12, 2019 @09:05AM (#20420379)
> it does not support native UTF8 csv files

It does though? You can export as a UTF-8 csv file...check the export options.

Re:I was wrong about spreadsheets (2017) by ekianjo on Friday July 12, 2019 @09:54AM (#20420729)
I am talking about importing CSV files in UTF8. If I use Japanese characters for example it fails utterly to display properly unless I import it as "Text" first.
Re:I was wrong about spreadsheets (2017) by jchb on Friday July 12, 2019 @10:48AM (#20421114)
The secret trick for importing data into Excel (without actually writing a file in the Excel file format): don't try CSV - as you have already noticed that will fail in all kind of fragile ways depending on your character encoding and operating system locale. Instead, convert your data into an html table and then paste or import that into Excel.

But not any html table, you need to have the appropriate proprietary css properties in there, such as the mso-data-placement:same-cell. Those are actually documented ...in the Office HTML and XML Reference published in 1999.

Re:I was wrong about spreadsheets (2017) by chaseha on Friday July 12, 2019 @11:09AM (#20421245)
I frequently go from SQL query results to HTML table to excel in a similar manner, but I haven't had issues w/ any proprietary CSS properties. Using Paste Special -> Match Destination Formatting it always comes out without any issues
Re:I was wrong about spreadsheets (2017) by phonon on Friday July 12, 2019 @03:02PM (#20423402)
No, you should use the Data import tools--that's what they're there for!
Re:I was wrong about spreadsheets (2017) by phonon on Friday July 12, 2019 @03:00PM (#20423394)
Yes, it takes a little longer, but you should use Data > From Text/CSV for more complex text/delimited imports.