SVG file imported incorrectly

[Lukas.]

Hi,

I have this svg file (attatched) which is not correctly imported by Affinity Designer. I don't think it's particulary a problem with v2 (as I tested it with v1 as well - same result) but that's the one I'm using now - so I'm posting it in this forum.

As you can see in the screenshot above all the outlines of the flowers are messed up. The stroke is too thin and the shape is filled with black color.

Inkscape for example and my browser seem to import / render the file correctly however.

Any help would be appreciated, thanks in advance!

Tested on:
Windows 10.0.19045 Build 19045
Affinity Designer v2.0.4 (hardware accelaration on/off)
Affinity Designer v1.10.6.1665
Inkscape 1.2.2 (732a01da63, 2022-12-09)

Flowers.svg

Edited May 13, 2023 by Lukas.
fixed formatting

[v_kyr]

1 hour ago, Lukas. said:

As you can see in the screenshot above all the outlines of the flowers are messed up. The stroke is too thin and the shape is filled with black color.

Inkscape for example and my browser seem to import / render the file correctly however.

Any help would be appreciated, thanks in advance!

Well, if you open that file inside a text editor and review/inspect the SVG XML code there, you will determine that certain of the numbered SVG style settings are split-up into multiple settings (.cls-10,  .cls-12,  .cls-14) ...

... and the Affinity SVG parser get's probably puzzled by those!

If one instead defines and edits the styles (.cls-10,  .cls-12,  .cls-14) in a none split-up manner like here ...

... then the Affinity SVG parser doesn't get puzzled and can shows up the right SVG output instead ...

Here's the slightly modified SVG file in terms of it's styles definitions ...

• test_svg.svg

So all in all, as can be seen above, it's in this case overall a matter of how the SVG XML styles are defined and that the Affinity SVG parser isn't as flexible and foolprove here in parsing those in, in contrast to the SVG parsers used/included in webbrowsers and Inkscape!

 

[Dan C]

Hi @Lukas.,

Thanks for your report & file provided!

Using the great information from @v_kyr above, I will be logging this with our development team in order to help improve Affinitys SVG importer in a future update. Hopefully the fixed file provided in the above post should help workaround this issue in the meantime.

I hope this helps, and many thanks to v_kyr for your work here  

[Lukas.]

Thanks v_kyr for the technical insight provided and thanks to Dan C as well for passing it along to the devs! 👍