Hi all, I am working on some testsuite fails, and am now stuck on painting-marker-02-f.svg. Apparently, the stroke thickness of the markers should be inherited from the path they are on. This does not work in Inkscape. How should this inheritence be done? (is there an example of how this is usually done in inkscape?)
Thanks, Johan
-----Original Message----- From: J.B.C.Engelen@...1578... [mailto:J.B.C.Engelen@...1578...] Sent: vrijdag 2 januari 2009 16:50 To: inkscape-devel@lists.sourceforge.net Subject: [Inkscape-devel] testsuite painting-marker-02-f.svg
Hi all, I am working on some testsuite fails, and am now stuck on painting-marker-02-f.svg. Apparently, the stroke thickness of the markers should be inherited from the path they are on. This does not work in Inkscape. How should this inheritence be done? (is there an example of how this is usually done in inkscape?)
Hmm, according to SVG spec: "Properties inherit into the 'marker' element from its ancestors; properties do not inherit from the element referencing the 'marker' element." So something else is the problem...
J.B.C.Engelen@...1578... wrote:
Hi all, I am working on some testsuite fails, and am now stuck on painting-marker-02-f.svg. Apparently, the stroke thickness of the markers should be inherited from the path they are on. This does not work in Inkscape.
Sounds good! However, I don't know what you're using for reference, the standard or the test suite reference images, but if you're using the latter you may want to double-check the standard. I'm currently in the process of generating new references for the filter-related tests, as I found that some of the W3C references are likely incorrect (there is still a chance that there are some color space issues with the Inkscape output, but so far it seems that there are at least some problems with the W3C images).
Hmm, according to SVG spec: "Properties inherit into the 'marker' element from its ancestors; properties do not inherit from the element referencing the 'marker' element." So something else is the problem...
yes, markers should be clipped by their viewBox, but inkscape does not do that.
Thomas Holder wrote, On 01/02/09 17:24:
Hmm, according to SVG spec: "Properties inherit into the 'marker' element from its ancestors; properties do not inherit from the element referencing the 'marker' element." So something else is the problem...
yes, markers should be clipped by their viewBox, but inkscape does not do that.
this test file reveals another issue with markers: The bounding box is to big, it looks like it gets calculated for orient="auto" even though these examples all use the default orient="0".
-----Original Message----- From: Thomas Holder [mailto:speleo3@...58...] Sent: zaterdag 3 januari 2009 12:25 To: inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] testsuite painting-marker-02-f.svg
Thomas Holder wrote, On 01/02/09 17:24:
Hmm, according to SVG spec: "Properties inherit into the 'marker' element from its ancestors; properties do not inherit from the element referencing the 'marker' element." So something
else is the
problem...
yes, markers should be clipped by their viewBox, but
inkscape does not
do that.
this test file reveals another issue with markers: The bounding box is to big, it looks like it gets calculated for orient="auto" even though these examples all use the default orient="0".
Could you tell me exactly what the problem is? Perhaps create a test file for me? I've worked on markers before so I might be able to fix it, but I forgot what the orient attribute exactly means.
Cheers, Johan
J.B.C.Engelen wrote, On 01/03/09 19:56:
yes, markers should be clipped by their viewBox, but inkscape does not do that.
this test file reveals another issue with markers: The bounding box is to big, it looks like it gets calculated for orient="auto" even though these examples all use the default orient="0".
Could you tell me exactly what the problem is? Perhaps create a test file for me? I've worked on markers before so I might be able to fix it, but I forgot what the orient attribute exactly means.
from http://www.w3.org/TR/SVG/painting.html#MarkerElement
orient = "auto | <angle>" Indicates how the marker is rotated.
The default value is an angle of 0 degrees, this means no rotation. A value of "auto" rotates the marker so that it's x-axis matches the bisecting line between incoming and outgoing path segment. I attached a test file, the guidelines match the bounding box of the two paths. For the path with the blue marker this is correct, for the path with the red marker this is not correct as you can see. However, it's only the boundig box, rendering is fine.
The other issue is a rendering problem. The marker must be clipped by its viewBox, unless overflow="visible" is given.
"... the default behavior of SVG user agents is to establish a clipping path to the bounds of the initial viewport and to establish a new clipping path for each element which establishes a new viewport and each 'pattern' and 'marker' element."
"The initial value for 'overflow' as defined in [CSS2-overflow] is 'visible'; however, SVG's user agent style sheet overrides this initial value and set the 'overflow' property on elements that establish new viewports (e.g., 'svg' elements), 'pattern' elements and 'marker' elements to the value 'hidden'."
from http://www.w3.org/TR/SVG/masking.html#InitialClippingPath
Thomas
-----Original Message----- From: Thomas Holder [mailto:admin@...2024...] On Behalf Of Thomas Holder Sent: zaterdag 3 januari 2009 21:34 To: Engelen, J.B.C. (Johan) Cc: inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] testsuite painting-marker-02-f.svg
J.B.C.Engelen wrote, On 01/03/09 19:56:
yes, markers should be clipped by their viewBox, but
inkscape does
not do that.
this test file reveals another issue with markers: The
bounding box
is to big, it looks like it gets calculated for orient="auto" even though these examples all use the default orient="0".
Could you tell me exactly what the problem is? Perhaps
create a test
file for me? I've worked on markers before so I might be
able to fix
it, but I forgot what the orient attribute exactly means.
from http://www.w3.org/TR/SVG/painting.html#MarkerElement
orient = "auto | <angle>" Indicates how the marker is rotated.
The default value is an angle of 0 degrees, this means no rotation. A value of "auto" rotates the marker so that it's x-axis matches the bisecting line between incoming and outgoing path segment. I attached a test file, the guidelines match the bounding box of the two paths. For the path with the blue marker this is correct, for the path with the red marker this is not correct as you can see. However, it's only the boundig box, rendering is fine.
Thank you very much for the bug report and especially the test file. I think I've fixed the bbox calculation in trunk now.
The viewbox problem, I do not know how to approach so can't fix it now.
Johan
participants (3)
-
unknown＠example.com -
Jasper van de Gronde -
Thomas Holder