To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=102548





------- Additional comments from [email protected] Thu Jul  2 17:12:09 +0000 
2009 -------
AW: Found. Problem is that all the decomposition stuff is layouted for unified
geometry data and an object transformation holding the whole transformation
stack. For historical reasons (the old polygon had only integer, so it colud not
be in unified coordinates, this would have resetted all data to 0 and 1) it's
different for path objects.
Normally the combination of object transformation and unified geometry describes
everything, whereby the scale is in the transformation. For the path object, the
scale is applied to the polygon (geometric data) and is extracted (set to 1.0,
1.0) in the transformation. In the assumed combination, all leads to equal
results (e.g. for getting the real poygon, it gets transformed with the
transformation; it makes no difference where the scale is loacted).
But (of course :-)) there is an exception: The polygon setup for contour text
decomposition in combination with the (old) outliner stuff needs the scale
separated (since it still operates on old integers). Guess where the scale is
taken from...? From the object transformation where it's (1.0, 1.0) for the
polygon case...

There are two solutions:
(a) Change SdrPathPrimitive2D constructor calls (only one) to get the correct
data representations
(b) check if the scale is 1.0/the polygon has some size in
impDecomposeContourTextPrimitive and get the scale from the polygon

While (a) is technically cleaner, (b) is less dangerous. Evaluating...

---------------------------------------------------------------------
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]

Reply via email to