Has svg export changed ?

[Turan Mirza]

Just done that - thanks. I don't want anyone to go out of their way. If you don't know Resolve it would take a bit of getting used to - but it is Free to download.

[Acorn]

Turan, when I check the SVG in Notepad++, it complains that Line 2: <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> fails with "XML Parsing error line 2 pos 11; // DTD is prohibited.

Until Xara sorts it out, change svg to html
OR
Delete Line 2 (and Line 3 if you don't want to know Xara generated it)
OR
Drop into SVGOMG and optimise the file: remove doctype; XML instructions; comments.

Try hand (1).svg

Acorn

[Turan Mirza]

Humm that did not do it either. But I'll check out SVGOMG - it's been a few years since I tinkered, time to get hands dirty. Thanks.

[RKissane]

Turan,

I imported your hand file into the following programs without issue: Inkscape, Scribus, Gimp, Krita, and my Xara V18 new update. No problems on any of these. I don't have Affinity so maybe somebody else can check.

Ray

[Turan Mirza]

You can take the engineer out of engineering, but you can't take engineering out of the man - you know what I mean.

I opened a simple svg that had one item in it in Notepad (Installed SVGOMG plugin for chrome form google store, but AVG say's there is malware [could be a false positive - thoughts?]) for comparison.

I'm not up on XML but C, C#, C++ and html are not too bad for me. So I intelligently (if you can call it that) removed lines I felt were not needed. There are 'id equals background' and also id equals 'background 2's' in there plus 'page background' tags. Plus multiple scales etc so removed one line tested it, etc.

Turns out when I remove the defs section out - which holds a url for a css - it works and loads fine.

Anyone know the need/importance of that line? After all the playing about I kept everything but that line (and the upper and lower 'open def' close def' lines.

I imported this file in the past and it worked fine. (to be clear after importing it successfully into Resolve I deleted the svg file but kept the .xar file, so I'm now importing a fresh export of the svg)

Also - both XaraDesPro+ AND resolve have had updates.

So either Xara has now added/altered this line OR Resolve now has issue with this line (where before it overlooked/ignored or handled the line).

I'm an older and bigger fan of xara than Resolve, but as said above having had issues with Xara's .ai export before, kinda points me to think it is Xara.

None of the other test .svg's I download had a line like this, maybe it is useful but not for their context.

If this is a possible bug in Xara export I can raise it to them - so let me know if you know what this line does.

Thanks for all your (everyone above) help.

[Acorn]

Turan, sorry you have having such grief.

A <defs> block is coding something for later and repeated use.
It would be accessed with a <use> block.

I can see Xara is including the <defs> to add in a Google Font, in my case, Opens Sans.
boxy-svg.com can define complex filters with and id and then reference the id in a url.
If no <use> block or url reference then you can probably remove the <defs>.

I use the svgomg website directly.

For the Xara SVG generator 6.6.0.1, I get no faults.
I sometimes get the DTD complaint in 6.6.0.6 but the designs still render.
I have exported Adobe, Inkscape and non-repeating and frankly here is no difference in the SVG code.

AI uses a Comment:
<!-- Generator: Adobe Illustrator 25.0.0, SVG Export Plug-In . SVG Version: 6.00 Build 0) -->
Xara does the same:
<!--Generator: Xara Designer (www.xara.com), SVG filter version: 6.6.0.6-->
zint.org.uk doesn't have one.

I doubt then that here is a Xara SVG Export fault as I cannot get any load issues in any of the tools I have.

Acorn

[Turan Mirza]

Don't worry - no big grief - I was trying to be purist by using vectors, but solved the problem by using .png's during the week there. So I was just now mopping up for a better understanding and for future use.

So really appreciate the testing you dig - thanks. I'll reach out on some Resolve forums and see if this is a known issue with defs in svg's.

Cheers.