To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=102943
User hdu changed the following:
What |Old value |New value
================================================================================
Summary|meta-issue for tracking no|meta-issue for tracking no
|n-unicode baseplane proble|n-baseplane unicode proble
|ms |ms
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Mon Jun 22 11:03:54 +0000
2009 -------
Yes, msgNo=18462 is a good start as it identified problems in the UNO API.
Finding the remaining
problems (individual sal_Unicodes) is the other important task.
OUString::iterateCodePoints() was a good start too, as it was the first method
in the string area which
didn't require its users to handle surrogate pairs themselves. The iterator
approach I outlined above is
IMHO better though because it could allow zero-conversion and zero-copy access
to raw data, such as
the performance critical XML files. The current approach to convert them first
to UTF-16 and then use
iterateCodePoints() to convert them to UTF-32 does not have that benefit.
---------------------------------------------------------------------
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]
