xlink:href deprecated in svg2.0

[muffintop]

Hi,

I noticed Inkscape still uses "xlink:href" which has been deprecated in svg2.0.

Does anyone know when Inkscape will support plain "href"? (The slated replacement of xlink:href.) I'm using Inkscape v0.92 and it doesn't seem to support plain "href".

Also, is there a developers forum where these kinds of questions can be asked?

Thnaks!

[Lazur]

Hi.

That doesn't sound so good.

There are a few ways to connect with developers directly:
-entering hackfests (maybe next year)
-in a live chat at irc #inkscape-devel channel @freenode
which is where they will probably direct you to the
-bug tracker.
-the core of the project has moved to gitlab, where you could also draw some attention to the problem (after consulting on the irc), also there is
-joining the developer mailing list.

My guessing is probably there are developers avare of the problem since at least Tavmjong Bah is part of the svg working group.
Maybe there is also an existing bug report of it at the bug tracker.
I would also check for the mile stones as there are still some very basic flaws that long waiting a solution -customizable coordinate system origo, multipage and cmyk support. Latter two were discussed at the hackfest as far as I know while the first one doesn't have an easy backwards compatible solution.

[brynn]

The devel mailing list (https://inkscape.org/en/community/mailing-lists/) is the most dependable way to contact developers.  (I know, maling lists make me crazy - I dont' know why in the world Inkscape developers can't come into the future with internet communication.)  On IRC, you can't be sure if the person who knows the answer will be logged on when you visit.

My best guess is that Inkscape will not use SVG2 until it is officially....released or approved or adopted, or whatever the correct language is for that.

I found this, for more info:  http://wiki.inkscape.org/wiki/index.php/SVG2

And this, which explains what level of development SVG2 is at right now:  https://www.w3.org/TR/SVG2/

Roughly a year ago, or maybe closer to 2, there was a mailing list discussion about this, from one of the developers of SVG2.  You could search the archives (http://sourceforge.net/mailarchive/forum.php?forum_name=inkscape-devel) for a message from Amelia Bellamy-Royds.  As far as I could understand, she was the only active developer, and not feeling good about being in it alone, and not knowing whether should could continue alone.

I also seem to recall there was some talk about browsers not wanting to adopt SVG2, which would make it  pretty much a dead endeavor.  So as far as I know, Inkscape will be using SVG1 for the foreseeable future.  (The threat of browsers not wanting to adopt SVG2 is the main reason Inkscape's Gradient Mesh tool was rushed into version 0.92, so users could show the world how awesome it could be.) (edit - or was it version 0.91?)

Edit
Or if you're more comfortable asking the question as a user, you can use the User mailing list, which most developers also watch and answer.  Same link as above, to subscribe.

[Lazur]

 

(The threat of browsers not wanting to adopt SVG2 is the main reason Inkscape's Gradient Mesh tool was rushed into version 0.92, so users could show the world how awesome it could be.) (edit - or was it version 0.91?)

0.91 could render and edit a current version of gradient meshes at the time if the part of the gui was unhidden -however the code changed later on, and rendering is no more backwards compatible. As a result openclipart can't render gradient meshes drawn with an up to date version as a thumbnail because they are using 0.91 r13725.