I don't know how to judge between adherence and non-adherence to standards.
It's not me. It's my software. Various apps, from GIMP to Paintshop Pro, take in SVG's made with sodipodi, for example, but choke or make bad images with Inkscape SVG's. I quit outputting SVG's and simply have Inkscape export PNG's to work on in bitmapped image editors now.
After all, Inkscape itself differentiates between Inkscape SVG and "plain" SVG. If there is no difference, why the output option?
I perhaps wrote in error when I distinguished between Inkscape and "standard" SVG's I should have said "plain" SVG's instead. I'm not sure there is a standard SVG yet.
Finally, do recall that I was suggesting a way to make an SVG file that would be accepted by another app. In the past, I have had better success with the plain option than with the Inkscape option.
On 4/14/06, Bryce Harrington <bryce@...983...> wrote:
On Thu, Apr 13, 2006 at 10:46:29PM -0400, Edward Hume wrote:
One problem with importing Inkscape SVG's into OO is that Inkscape SVG's are not standard SVG's.
In what way have you found Inkscape's default SVG to not adhere to the SVG standard?
Bryce
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&da... _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user