You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to the latest version, I'm noticing that some SVG files are no longer rendering and instead I get an error message of "File "<FILE_NAME>", error: Parameter is not valid."
However, it doesn't tell me what it doesn't like or needs to change. Inkscape loads the files fine.
I've included 2 examples.
The text was updated successfully, but these errors were encountered:
Version 0.5.0.1715 has been released, which makes the FIRST file render without error (although it does not render correctly). To achieve this, I downgraded the version of the SVG.NET library from 3.4.6 to 3.4.4. Because there is a known bug in versions 3.4.5 and 3.4.6, although it will probably be fixed in the next version of the library.
However, I did not find any version of the SVG.NET library that could show the SECOND file. Looks like it is perfectly valid (I even checked it with an SVG validator), and it opens perfectly in browsers and editors. But the SVG.NET library cannot open it because it contains an unknown URL #DotM-4. I don't know what it is, but looks like it can be deleted without harming the picture. You can fix this file yourself — just open this SVG file in Notepad, and delete 2 occurrences of the following:
;marker-start:url(#DotM-4)
After this, it will be displayed without error (although it does not render correctly too). Because there are a lot of bugs in SVG.NET library. That's why I'm looking for a better replacement for this lib.
After upgrading to the latest version, I'm noticing that some SVG files are no longer rendering and instead I get an error message of "File "<FILE_NAME>", error: Parameter is not valid."
However, it doesn't tell me what it doesn't like or needs to change. Inkscape loads the files fine.
I've included 2 examples.


The text was updated successfully, but these errors were encountered: