Comment 3 for bug 567014

Revision history for this message
Mikhail Ryazanov (michael-ryazanov) wrote :

Still not fixed...
It is even more interesting that the specification read further: "If a valid ‘clip-path’ reference is placed on one of the children of a ‘clipPath’ element, then the given child element is clipped by the referenced clipping path before OR'ing the silhouette of the child element with the silhouettes of the other child elements.", and that situation works differently in Inkscape (0.48.2 r9819). Namely, clip-path attribute of <clipPath> is ignored completely, but clip-path attribute of a child adds clipping to the bounding box instead of the actual path.
See the attached file (based on http://apike.ca/prog_svg_clip.html):
"Intersection" was made by nesting clip paths (one for <g>, another for <rect>) — it looks correct.
"Intersection1" uses clip-path attribute of <clipPath> — no effect in Inkscape.
"Intersection2" uses clip-path attribute of a child path — Inkscape clips to the clip-path's bounding box (warning: would produce a correctly looking result for unrotated rectangles).

P.S. Is there any standard-compliant tool to convert SVG to EPS/PDF?