To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=5658
------- Additional comments from philhi...@openoffice.org Mon Jun 14 14:48:01 +0000 2010 ------- jtienhaara: This is a bigger issue than someone deciding "his medical spreadsheets were important than all the existing OOo spreadsheets out there". This is an Excel compatibility issue, and I understand that some people don't care about the 25 year legacy of the most widely-used piece of business software ever written, but OOo can't afford to ignore it. There's a hard choice to make here - do you silently treat a badly-formed number (e.g. "l2345") as a zero, or do you highlight it as an error to the user? I'm currently on the fence. My instincts are to go with the patch for this issue, and highlight it to the user (that's what Excel also does). That it breaks your spreadsheet is highly unfortunate, but I'm unsure whether it's a serious enough backwards-compatibility bug to revert this aspect of the behaviour (and treat non-numeric strings as zero rather than raising #VALUE!). In any case, I think it needs to be raised as a new issue for consideration, as this one is closed. --------------------------------------------------------------------- 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
