To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113421
------- Additional comments from e...@openoffice.org Mon Jul 26 13:46:48 +0000 2010 ------- @guidogam: > But your implementation non only does not follow RFC 793 [8], How should this be related to RFC 793 TCP? > but violates also RFC4180 [5]: "If fields are not enclosed with double > quotes, then double quotes may not appear inside the fields." It means > that the program should have taken everythig between the quotes and > treated it as a single field. No. It means that this is a file content that is not defined by the standard, as the field is not enclosed with double quotes. Field content starts right after the comma and there is a space. At first hand the generator didn't follow standards, not our import implementation. Now as we take the entire content between commas as one field and do not detect a quoted content in this case we take all characters up to the next delimiter, including any quotes encountered. We do so because there are too many implementations that write broken files that have quotes in non-quoted field content, and even unescaped quotes in quoted content. This is a long ongoing discussion and I won't repeat it here. See issue 78926 for details. --------------------------------------------------------------------- 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
