"If you simply have to produce tabular data for use in Excel, consider CSV." That's what most of us have been doing for years, simply to avoid the mess discussed in this article. After reading the article, I, for one, will keep on doing it.
I ran into a nasty bug(?) recently in the way Excel processes CSVs. I create a well formed CSV from a Java Web app which the user downloads. They open the CSV up in Excel and modify the data for an eventual upload. However, during the save process, Excel truncates trailing commas. Which causes my well formed CSV to be a poorly formed CSV during upload and parsing. Not fun.
A,B,,,,,,,," " C,D,,,,,,,," "
That's newline there between " and "
I guess Excel loads that internally through a convertor, trims the rightmost unused columns, and then saves it that way.