Thanks Krzysztof,
Of course my comment about XLink namespace was wrong. I was thinking at keeping "href" empty inside the filter like that : xlink:href="" which is the result of removing the image reference from inside the Filters editor. If that's not correct SVG which alternative do you propose or what is the right way ?
About the "," problem, this mistake was only caused by my distraction while entering manually Component transfer values into the XML editor (that's because this primitive works perfectly and gives fantastic results but has no UI at the moment in the Filters editor).
ivan
________________________________ De : Krzysztof Kosiński <tweenk.pl@...400...> À : ~suv <suv-sf@...58...> Cc : Ivan Louette <ivan_louette@...48...>; Inkscape-devel@...1239....net Envoyé le : Dim 12 décembre 2010, 14h 36min 53s Objet : Re: [Inkscape-devel] Re : Firefox corrupts svg files !
2010/12/11 ~suv <suv-sf@...58...>:
On 11/12/10 12:49, Ivan Louette wrote: AFAIU all it would require is adding xmlns:xlink="http://www.w3.org/1999/xlink" to the top-level <svg> element of the enhanced or experimental 'filters.svg', along with the other already existing attributes. But maybe some SVG experts can confirm this?
Yes, this should fix it. The XLink namespace is always the same. Ivan's comment about the user of the filter changing the XLink namespace is a bit nonsensical to be honest. The namespace is just a formal requirement of the XML parser, not some user-definable value like the target of a link.
Seems related to Bug #586059 “Period not accepted in filter matrices UI (FR locale and maybe others)”: https://bugs.launchpad.net/inkscape/+bug/586059
For shared filters.svg files it might be better to not use a localized Inkscape version (to be save) or verify that the decimal separators within the file are consistent.
This is a different bug. 586059 is about the period not being accepted in the UI, while here the bug is about localized values being written to the SVG - a much more severe thing, because it results in non-conformant documents. I have a fix, but it appears that the recent GSoC merge broke the open dialog, so I can't verify it.
Regards, Krzysztof