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] Sun May 21 23:44:21 -0700 2006 ------- > The D/B construction allows the 'system' charset - which in my case (and in ~all Unix cases) > is UTF-8 to be used. On the first system I tried (our Linux build machines), osl_getThreadTextEncoding (which is what "System" evaluates to) gave me RTL_TEXTENCODING_ISO_8859_1 ... Cutting 8-byte-characters respecting UTF-8 boundaries would probably be possible. The problem then is that terms like "field length" then lose their meaning: If a column is declared to have a length of n characters, this translates to m or i or k or whatever UTF-8-encoded characters, depending on the concrete string to be encoded.This will most probably lead to bug reports of the kind "I entered 20 characters and the last 5 silently disappeared". How to solve this? --------------------------------------------------------------------- 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]
