4 ms·

Was it implemented before the generic CSV import was implemented? It seems like if parsing fails it should throw an exception and fallback to regular csv parsi

• mark-r 10y ago
  I suspect the parsing for CSV and the parsing for SYLK are completely different pieces of code, and the appropriate one gets called once a determination of the file format is made. This would be in an upper level where you wouldn't want to put format-specific behavior. The problem then is that the code determining the format doesn't dig far enough into the file to make sure it's valid before sending it to the parser.
• ygra 10y ago
  That's probably how it has been fixed. I cannot test right now, but since the article doesn't apply to newer versions of Office, I guess they are no longer susceptible to that.
  • Piskvorrr 10y ago
    Nope - just no longer admitting to it. Had to redo a bunch of exports because of this recently.
  • moobs 10y ago
    This is so funny, I was literally fixing this bug last night. Still applies to office 2013
    • cm2187 10y ago
      Another bug with CSV files is that opening a CSV file triggers a full recalculation, even if the calculations are set to manual. This is clearly a wrong behaviour.
  • deleted 10y ago
    [deleted]