https://bugs.documentfoundation.org/show_bug.cgi?id=152336
--- Comment #10 from Mike Kaganski <[email protected]> --- (In reply to Eyal Rozenberg from comment #9) > I would assume that if I save a file in a certain format, the specifics > would be independent of the input filtering, and only respect the format's > spec (and whatever defaults I have chosen the app to abide by if the spec is > flexible). Thus I would expect a TSV to be saved with tabs and a CSV with > commas even if, say, the input was parsed so as to separate fields by spaces. This may be a preference of some; but I claim, that at least for CSV, this would be a minority's preference; and the majority-to-minority ratio here will be HUGE. Most people who use Calc to edit CSVs will need Calc to retain the original file's structure; especially taking into account, that all "specs" in CSV are application-specific (and there is a *informational memo* RFC, reflecting some suggestions, but not binding). "Application-specific" here relates to the workflow (generation/consuming applications), not to the editing application in the middle. And a workflow of "normalization" of heterogenously-generated CSVs will be a minority of use cases. -- You are receiving this mail because: You are the assignee for the bug.
