February 2014 - Inkscape Devel

Future plans for XML namespaces in Inkscape and SVG 2
by Jarek Foksa 03 Feb '14

03 Feb '14

Are there any plans for Inkscape to move away from XML namespaces when SVG 2, HTML 5 and Web Components will become widely supported and XML namespaces will get deprecated? If this is the case, I think it would be great opportunity to clean up the current namespace mess. Ideally, I would like to see all vendors of SVG editors to agree on a common “editor” namespace that would be implemented with HTML 5 data- attributes and custom elements. My proposal: 1. Drop “dc:", "cc:" and "rdf:" namespaces and remove any elements and attributes using them as this is just useless noise. 2. Drop "xlink:" namespace prefix (as defined by the SVG 2 spec). 3. Convert all elements in “inkscape:" and "sodipodi:" namespace to custom elements with "editor-" prefix (as defined by Web Components spec) 4. Convert all attributes in “inkscape:” and "sodipodi:" namespace to data- attributes (as defined by HTML 5 spec). For example following SVG 1.1 document generated by current stable version of Inkscape: <svg xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" version="1.0" width="1000" height="2000" viewBox="0 0 1000 2000"> <sodipodi:namedview pagecolor="#ffffff" bordercolor="#666666" borderopacity="1" objecttolerance="10" gridtolerance="10" guidetolerance="10" inkscape:pageopacity="0" inkscape:pageshadow="2" inkscape:window-width="1366" inkscape:window-height="689" id="namedview1530" showgrid="false" inkscape:zoom="0.57" inkscape:cx="542.23281" inkscape:cy="1495.4813" inkscape:window-x="0" inkscape:window-y="27" inkscape:window-maximized="1" inkscape:current-layer="svg2"/> <image sodipodi:absref="/image.png" xlink:href="image.png" width="950" height="632"/> <path inkscape:connector-curvature="0" d="M 60,10 L -40,-45"/> </svg> ... could become this in future when saved as SVG 2 document: <graphics width="1000" height="2000" viewbox="0 0 1000 2000"> <defs> <editor-namedview pagecolor="#ffffff" bordercolor="#666666" borderopacity="1" objecttolerance="10" gridtolerance="10" guidetolerance="10" pageopacity="0" pageshadow="2" windowwidth="1366" windowheight="689" id="namedview1530" showgrid="false" zoom="0.57" cx="542.23281" cy="1495.4813" windowx="0" windowy="27" windowmaximized="1" currentlayer="svg2"> </editor-namedview> </defs> <image data-editor-absref="/image.png" href="image.png" width="950" height="632"/> <path data-editor-connector-curvature="0" d="M 60,10 L -40,-45"/> </graphics> Some related documents: - Custom elements: http://w3c.github.io/webcomponents/spec/custom/ - Proposal for improving SVG DOM: http://dev.w3.org/SVG/proposals/improving-svg-dom/ - Data attributes: http://www.whatwg.org/specs/web-apps/current-work/#embedding-custom-non-vis… Do you think this has any chance to get adopted by Inkscape? If not, do you have any alternative plan to improve the way how Inkscape stores non-standard data in SVG documents in the upcoming post-XML future?

5 8

wiki account
by Masanori Kanazu 03 Feb '14

03 Feb '14

Hi, I would like to contribute to the translation of Inkscape wiki into Japanese. I already finished translating these two articles. http://wiki.inkscape.org/wiki/index.php/Inkscape_for_Adobe_Illustrator_users http://wiki.inkscape.org/wiki/index.php/AdobeToolMap Could you please create a wiki account with username "mkanazu" for me? regards, Masanori Kanazu

2 1

Future plans for XML namespaces in Inkscape and SVG 2
by Jelle Mulder 03 Feb '14

03 Feb '14

Hi all, If anything I think the namespaces et al should be optional by using export switches. That would allow every user to create his own specified exports. Currently the is the Inkscape SVG file and plain SVG and optimised SVG, but I think it would be way more useful if there were just two kinds of SVG files. Inkscape native and export, the latter of which could be optimised with switches. If you'd then have a list of templates for optimisation (with a description on what it is used for)that would set these switches for the users, it would facilitate the user to find the right flavor of SVG. Currently you'll have to handcode a lot to create the right flavor and using such export facilities would simplify the process. In any case removing the XML namespaces doesn't feel like a good option as long as many people are using legacy software to get their SVG to parse right. Blink of all parsers imho is NOT the default to go with when it comes to parsing SVG and there are more things done with SVG than just produce content for the Android platform. SVG 2 seems still very much in flux and I would suggest not doing anything drastic until the recommendation level is reached, regardless of what a juggernaut like Google is doing. I guess they're flexible enough when it comes to exploiting standards for their own benefit as do all the others to try and push things their way, but that is basically what standards are for. To force the monopolists to adhere to standards. Not the other way around. Google in that respect can have a look at what happened to MS the past decade. And it may very well be the opening that MS would like to see if Google would divert. There are several products Google tried and dropped as well, without a blink. Please stick to the standard with tenacity. Any decent developer can handle the bloat. Oh,.. and... Happy Chinese New Year! Jelle Mulder

1 0

Waf build system, second try
by Krzysztof Kosiński 01 Feb '14

01 Feb '14

Hello everyone, I conducted an experiment in building Inkscape with Waf, redoing the work I did a long time ago with a newer version (1.7.15) and using more of its features. A correct build of Inkscape, with internal libraries built separately, "inklib" built as a shared library, Bazaar revision fetching and .po file compilation, requires less than 250 lines of Python script (!!!). I read on some mailing lists that Debian refused to package some software using Waf, because Debian considers shipping the "Waf binary" to be incompatible with the DFSG. I circumvented this problem by adding the Waf source distribution to the tree, which is a little bigger, but DFSG-compliant and works exactly the same. The code will be up shortly at lp:~tweenk/inkscape/waf-build, if anyone wants to check it out. Regards, Krzysztof

10 28