To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=62664
------- Additional comments from [EMAIL PROTECTED] Tue Jul 25 05:44:41 -0700 2006 ------- no, sorry, it doesn't. It doesn't matter whether you switch on the problem via UI, or in the code by default. The problem remains: If for a UTF-8 dBase data source, the user enters a too-long string in the UI, then this string is silently truncated. I continue to think that this is not the best way to handle user input, and so far nobody commented on this or tried to convince me of the opposite :) This should be easy to fix: Instead of silently ignoring the problem in convertUnicodeStringToLength, throw an error - that's it. Other than this: - "if ( 0 )" is valid for a proof of concept, but not as a patch which is intended to be checked in - please remove the dead code in this branch. - fprintf is never a good idea, please use OSL_TRACE which has the same signature, and is removed in product builds --------------------------------------------------------------------- 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]
