To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=37213
------- Additional comments from [EMAIL PROTECTED] Tue Mar 1 08:05:09 -0800 2005 ------- AW: OASIS specification: OASIS Open Office XML Format Technical Committee (http://www.oasis-open.org/committees/office/). Should be well-known now. AW: From Your last answer: >But I think once we define a user coordinate system, we should respect to it. >For example, if we set svg:viewBox="0 0 100 100" then svg:points="40 40 60 40 >60 >60 40 60 40 40" should draw a square inside the draw element no matter what are >the values of :x, :y, :width, :height. That's exactly the question. Does 'embedded' mean: (a) the values of :x, :y, :width, :height may be overridden from polygon specification (b) the values of :x, :y, :width, :height always define the shape In my opinion, 'embedded' means (b), so at the moment there would be no way to change object definition from 'embedded' user coordinate system. I think users would write bugs if the polygon definition would overwrite their :x, :y, :width, :height value definitions. You also wrote: >As you also said, the logic of viewBox should be: >xOut = ObjectPos.x + (((xIn - viewBox:x) * ObjectSize.width)/viewBox.width) >yOut = ObjectPos.y + (((yIn - viewBox:y) * ObjectSize.height)/viewBox.height) No, i did not say it 'should be', this is an analysis of the existing code. So it looks like it was intended to do it this way, but it's not completely implemented at the moment. The implementation handles the polygon that way, but does not change :x, :y, :width and :height when the polygon definition is different from that. At the moment it does neither correct the polygon to (0,0) alignment inside the shape. So, for correcting this there is solution (a) change :x, :y, :width, :height (b) align polygon to (0,0) and object size corresponding to (a,b) from above. I think to do (a) the OASIS specification would NEED TO DOCUMENTATE that the embedded polygon data may change object width and height definitions. That's not the case, so i think the fix needs to be (b) as long as that is not mentioned/documented. --------------------------------------------------------------------- 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]
