On Thu, 2004-08-05 at 16:06, David Turner wrote:
I'm rewriting some of the marker code, because it doesn't conform in any way, shape, or form to the spec. Along the way, I've found some deficiencies in the internals of Inkscape (as well as some in the SVG spec).
NArtBPath does not properly handle closed subpaths.
It also doesn't do cubic (or is it quadratic? ... the kind with three points) beziers or elliptical arcs either.
We inherited NArtBPath from libart, actually; it's not really well-adapted for SVG's path model.
We really need a new standard path type, I think, though for the moment the changes you describe are maybe sufficient.
<whine> Note that Inkscape currently incorrectly renders marker-start on the start of any subpath, rather than only on the start of the path as a whole. This is entirely logical, but does not match the spec. It's my opinion that the spec is dead wrong here, and evidently somebody else agrees with me -- I just saw a message on www-svg@...157... proposing new markers for the beginning and ends of subpaths. I'll "fix" this too, to match the spec, even though the spec is wrong. I may also add custom subpath-start and subpath-end markers. </whine>
Hmm, I'm not sure how to add our own subpath markers without violating the should-render-identically-in-standard-user-agents ground rule.
(I agree with your assessment of the spec in this regard though)
-mental