To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=74754
------- Additional comments from [EMAIL PROTECTED] Mon Jun 2 14:58:06 +0000 2008 ------- A UNO string is a sequence of Unicode scalar values, even though most/all language bindings implement it as a sequence of UTF-16 code units; a UNO char (probably by mistake) is a UTF-16 code unit (not a Unicode scalar value). This is already confusing enough. API that combines string or sequence<char> with numeric indices into such sequences potentially adds further confusion (are the indices based on code points, or scalar values? in case of sequence<char>, what to do with unmatched surrogate halfs in the input? etc.). Hence my suggestion (IIRC) to make the API as simple as possible. --------------------------------------------------------------------- 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]
