To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=80385
------- Additional comments from [EMAIL PROTECTED] Wed Aug 8 17:50:15 +0000 2007 ------- Friend er, > Isn't that somewhat contradicting? You have broken data in your file and > want it reflected reasonably accurately? Yes, we can add some more magic > to try to guess broken data correctly. Yes, we will do eventually, this > is what issue 78926 is about, so this issue here in fact is a duplicate. I do not ask for any magic or guessing of data. All I ask is for the treatment of data to be consistent. I thought I knew what Calc was doing, and that it would do the same or similar thing as Excel, but it looks like I was wrong there. To be honest with you, I was writing a C routine to read in CSV files, and I wanted to find out how they were handled in production applications, hence my creation of the "broken" CSV files. Excel appears to handle "broken" data rather gracefully. Calc... rather less gracefully, losing some data in the process. Surely it is important not to lose data? Surely it is important to apply rules consistently? I guess I might as well give up. At the very least, could you put something in the documentation somewhere that specifies exactly how Calc reads in CSV files? At least then, people like me wouldn't be unpleasantly surprised. --------------------------------------------------------------------- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
