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
================================================================================
Keywords| |cjk, performance
--------------------------------------------------------------------------------
Target milestone|--- |not determined
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Mon Jun 22 10:00:08 +0000
2009 -------
IMHO an approach based on string iterators would work better as it would
isolate implementation
details (such as an internal UTF-16 representation) from its use. E.g. for
working on unicode
codepoints one would get an UTF-32 iterator, for encoding conversions (e.g. to
big5) one would get
other suitable iterators.
By splitting unicode string's implementation details (UTF-16) from its
interface (specialized string
iterators) this could also speed up such performance critical tasks as XML
parsing. XML text is usually
encoded as UTF-8 and AFAIK it currently has to be converted to UTF-16 for
further processing. By
keeping the inputs native encoding as an implementation detail the conversion
step which is costly
(from a processing, from a memory and from a spinlock contention perspective)
could be avoided
altogether.
---------------------------------------------------------------------
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]