To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=87999
------- Additional comments from tuhar...@openoffice.org Fri Sep 4 10:06:54 +0000 2009 ------- The behaviour is illogical more than that. The way the data are parsed is applied BY CELL! So that it ends up like a useless mess of (bogus) dates and numbers. CSV is usually used as simple data transfer format, not intended for any formatting or so. We can quite reliably assume, that the format of any column, excepting the first line, should be of same type. So, if the program dosen't know for sure, how to eat the values, it should at least keep up with the same resolution for the whole column (excepting the first line). The most secure way to do is simply interpret them as text and let the user decide later, how to deal with them (he can always select them and say "they are all numbers"). That seems for me quite reasonable approach: "Hmm, there are some strange values in the column C, that don't hold together with other values in that column.. I will better mark them as text and let the user decide". At least, there is no dataloss using this approach. This is much more favorable than generating dates from everything that remotely resembles a date, thus destroying original values. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@sc.openoffice.org For additional commands, e-mail: issues-h...@sc.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
