To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=101169
User aw changed the following:
What |Old value |New value
================================================================================
Status|NEW |STARTED
--------------------------------------------------------------------------------
------- Additional comments from a...@openoffice.org Tue Apr 21 10:39:13 +0000
2009 -------
AW: Okay, taking a look. Comparing DEV300 m29 (last version before primitives)
with OOO310 m7. This shows that the preparation is pretty identical, but the
decision for pTextDecoratedCandidate has to be removed (as already stated).
The 2nd issue with the too many generated breaks is quickly found: The code in
drawinglayer/source/processor2d/vclmetafileprocessor2d.cxx uses rTxt =
rTextCandidate.getText() and rTxt.getLength() for the BreakIterator looping and
processing. This is generally wrong, since the TextSimplePortionPrimitive2D
works with String, Position and Length parameters; thus currently e.g. for a
text portion with start at 50 and length of 30, the whole string was tagged
again and again for each single portion. Corrected, that, works as expected.
Tesing a little more...
---------------------------------------------------------------------
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: issues-unsubscr...@graphics.openoffice.org
For additional commands, e-mail: issues-h...@graphics.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
