We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Visio guidelines present in SVG


We are using guidelines in Visio to align objects, and those guidelines appear to be present in the output SVG.

When exporting from Visio, those guidelines are removed in the SVG.

You create the guidelines as a path element, with the d attribute values of ‘Z’, this may be valid SVG, but that element has 0 (zero) width and height, and doesn’t add value to the output.

guideline.zip (278.0 KB)
source.vsd (source diagram with guidelines)
apose.svg (apose output containing guides lines (id=101 and 113)
visio.svg (visio output with no guide lines)




Thanks for contacting support.

Could you please share a screenshot displaying the issue which you have mentioned above. It would help us addressing the issue accordingly.

The issue isn’t visible when viewing the SVG, but when parsing the SVG with an XML parse, honoring the schemas. It gives an warning, because the element doesn’t have any dimensions.

I’m just thinking that whenever an element in the Visio file is an guideline, it should be disregarded and omitted from the SVG.


Thanks for writing back and further elaboration.

Would you kindly share which SVG:Parser you are using in your environment and what type of warning it uses to show (a screenshot would be helpful). We will further investigate the feasibility of your requirements.

The xml parser used is Tiny XML version 1 for C++.

And Aspose.Diagrams doesn’t give error, we are validating the SVG xml, and an Path=‘Z’ is not valid according to SVG Spec, hence our own program, throws an warning.
I am guessing you want your SVGs to follow the standards? :slight_smile:


Thanks for sharing requested information.

We have created an investigation ticket as DIAGRAMNET-51580 in our issue tracking system. We will further investigate the scenario while considering your concerns and as soon as we have some additional updates to share, we will inform you. Please be patient and spare us little time.

The issues you have found earlier (filed as DIAGRAMNET-51580) have been fixed in Aspose.Diagram for .NET 18.11.