Inkscape 0.48 Drawing disappears in .091

Good Morning,
I reported this bug about a month ago. What is the status of this request please?

confirmed on Windows 10, Inkscape 0.92.2 (5c3e80d, 2017-08-06)

Hi.

The SVG is malformed, the elements "path8130-15-4-6-7-3-5", "path8130-15-4-6-3-9", "path8130-15-4-6-7-3", "path8130-15-4-6-3", "path8130-15-4-6-7-5", "path8130-15-4-6-6", "path8130-15-4-6-7"... has a wrong "d" attribute. If you remove or fix the value on all wrong elements the draw show.

Hi Jabiertxof,

Thanks for the update. I am working with Mike Gallagher on this issue. Are we talking about these d="m 5.77 ..." in the second line from the file that was created in 0.48?

      <path
         id="path5174"
         d="m 5.77,0 -8.65,5 0,-10 8.65,5 z"
         style="fill:#ffffff;fill-rule:evenodd;stroke:#ffffff;stroke-width:1pt;marker-start:none"
         transform="scale(0.8,0.8)"
         inkscape:connector-curvature="0" />

As suggested, I removed all "d" attributes, meaning I deleted the entire line. However, when I open the new file in Inkscape 0.92, all I get is the same file as when the "d" were all still in there.

So could you please elaborate on the correct removal or fixing on the "d" attribute?

Also, our associates have a lot of files (100's or 1000's) created with 0.48, and just this current file I am working has about 100 "d" attributes. Rather than touching about 100,000 lines in files manually, a patch to 0.92 would be much appreciated.

Best regards,

Berno

Hi the problem is the lines with id="what id I say" and something more has a d="with wrong data not a path"

Puting in real live:
The path with id="path8130-15-4-6-3-9" has a d="m 562.10383,1.9527134e218 v 0"
1.9527134e218 is not a valid coordinate
There is a lot of ocurrences of this on the file with diferent numbers.
As is a particular issue the best way to fix is if all desirables values of 1.93....e218 are one or are egual to 1.93... do a regex expression on the files to remove the e218 ot substitute the entry 1.93....e218 for one fixed number, ot remove full tag. If there is diferent numbers the data is lost in the SVG, anyway I dont think it because seems dead lines.

You can do it running script once in a folder copy of all the SVG.

Anyway, I think but not sure, is not a thing that can be included in core base because can data loose or need some parameters and seems a particular case.

If you code the script please add to this bug report if this problem happends to more people.

Best, Jabier.

To test the wrong path open a new file, add a line and substitute the d="...." with "m 562.10383,1.9527134e218 v 0" by this way you have a less sice scope to work. The first thing I try is remove "e228" text and see if is the desirable result, or maybe need to be 0, or one or a totaly loosed value....

You can do this things with the XML inspector

Inside Inkscape

Hi Javier,

Thank you for the additional information. To keep this in context, the file that is now considered malformed with regard to Inkscape 0.92 has been created in Inkscape 0.48 where it shows absolutely correctly, see attached. How can Inkscape 0.48 save coordinates to an svg file (and render the same svg file correctly after closing and reopening it) that are considered malformed by Inkscape 0.91 or 0.92?

Best regards,

Berno

¿Can you try to remove all wrong elements to see if the file is full draw correctly or missing some parts?

Replace all ocurrences in a text editor of "e218" by "" and it show.
Anyway is a malformed path maybe a bug on 0.48.

Not sure if auto remove it from Inkscape 0.93 is a good idea.