RE: [Inkscape-devel] SPOffset standards considerations
- use our own inkscape:href (or something like that) attribute instead
of xlink:href for linked offsets -- SVG does not define xlink:href to have meaning for <path> elements.
Yes
- populate the d= attribute of the SPOffset <path> with the offset
path, so the SVG requirements are satisfied, and normal SVG UAs have something to render.
Doesn't it do that already?
[ a ground rule here is that an Inkscape document should look no different in a pure SVG UA than in Inkscape -- at minimum, when in doubt, check how it looks in Batik ]
Yes
- All of the SPOffset extension attributes need to be in the inkscape
namespace, not the sodipodi namespace (e.g. inkscape:original, not sodipodi:original). The sodipodi namespace is reserved for Sodipodi's use. This holds true for all new functionality we add.
Yes, I wrote about that
As interoperability and standards-compliance are core goals for us, I can't sign off on an 0.37 release until these are fixed.
But I think they are really easy to fix :)
_________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=dept/features&pgmarket=en-ca&RU=http%3a%2f...
On Thu, 2004-01-15 at 04:03, bulia byak wrote:
- populate the d= attribute of the SPOffset <path> with the offset
path, so the SVG requirements are satisfied, and normal SVG UAs have something to render.
Doesn't it do that already?
It did at one point; CVS HEAD does not appear to do it anymore, though.
As interoperability and standards-compliance are core goals for us, I can't sign off on an 0.37 release until these are fixed.
But I think they are really easy to fix :)
Then please do so? ^_^
(I've been preparing for a job interview today, or I'd have done it myself...)
-mental
participants (2)
-
bulia byak
-
MenTaLguY