Hi
I’ve managed to recreate a number of errors when saving various Visio files as SVG. I’ve described the errors below and have attached the source Visio files and SVG output files.
OP1.vdx
- Black border on map shapes is grey on SVG version
- Strapline Phrase One Phrase Two Phrase Three (bottom of screen) is not spaced correctly on SVG
- Text Touchpoint appears on the SVG content at the bottom of the screen
BA1.vdx
- Hyperlink in top right hand corner not displayed properly
- Responsibility box at bottom of shape is partially shaded when it should be white
FG1.vdx
- Shading on hyperlink button with up arrow in bottom left corner not displaying correctly
- Envelope icon in bottom right of screen is not displaying correctly
- Text alignment in Key box at top right is not correct, i.e. certain text is not centered correctly (both horizontally or vertically)
WS1.vsdm
- Warning triangle is not rendered correctly (exclamation is too high)
- Shading on hyperlink button with up arrow in bottom left corner not displaying correctly
- The text at the bottom of the screen (Map Title) is aligned too far to the left
- The text at the bottom of the screen on the right is not displayed properly
- The overlapping connectors on the left of the screen, leads to different shadings
Hi Andrew,
Thank you for contacting support. We have logged tickets in our bug tracking system as below:
File Name: BA1.vdx
DIAGRAMNET-51190: Incorrect display of hyperlinked shape on saving a VDX to SVG
DIAGRAMNET-51191: Responsibility box at bottom of the shape is partially shaded on saving a VDX to SVG
File Name: OP1.vdx
DIAGRAMNET-51192: The text phrases are not being spaced correctly on saving a VDX to SVG
DIAGRAMNET-51193: An additional text appeared on saving a VDX to SVG
File Name: FG1.vdx
DIAGRAMNET-51194: Incorrect rendering of an icon on saving a VDX to SVG
DIAGRAMNET-51195: Incorrect rendering of an envelope icon on saving a VDX to SVG
DIAGRAMNET-51196: Incorrect text alignment on saving a VDX to SVG
File Name: GS1.vsdm
DIAGRAMNET-51197: Warning triangle shapes are not rendered correctly while saving a VSDM to SVG
DIAGRAMNET-51198: Shade on hyperlink button is not rendered correctly while saving a VSDM to SVG
DIAGRAMNET-51199: Title text is not aligned on saving a VSDM to SVG
DIAGRAMNET-51200: The text items are overlapping on saving a VSDM to SVG
Your post has also been linked to these tickets. We shall keep you informed regarding any available updates.
:
OP1.vdx
- Black border on map shapes is grey on SVG version
WS1.vsdm
- The overlapping connectors on the left of the screen, leads to different shadings
Please highlight both these issues with the help of screenshots. It will help us to identify them as well.
Thanks for your response.
OP1.vdx
- Black border on map shapes is grey on SVG version
I’ve re-examined this and have realised that the borders are actually black - they just seemed grey when zoomed out. Please disregard this issue report.
WS1.vsdm
- The overlapping connectors on the left of the screen, leads to different shadings
On closer examination I can see that this effect is present within the Visio diagram as well as the SVG output so please disregard this issue report.
Hi Andrew,
Thank you for being patient. We have a good news for you that the ticket IDs DIAGRAMNET-51191 and DIAGRAMNET-51192 have now been resolved. If there is no issue in the QA phase, then their fixes will be included in the next version 17.4.0 of Aspose.Diagram for .NET API. We’ll inform you via this forum thread as soon as the new release is published.
Hi Andrew,
Thank you for being patient. We have a good news for you that the ticket IDs DIAGRAMNET-51197 and DIAGRAMNET-51200 have now been resolved. If there is no issue in the QA phase, then their fixes will be included in the next version 17.4.0 of Aspose.Diagram for .NET API. We’ll inform you via this forum thread as soon as the new release is published.
The issues you have found earlier (filed as DIAGRAMNET-51191;DIAGRAMNET-51192;DIAGRAMNET-51193;DIAGRAMNET-51200) have been fixed in Aspose.Diagram for .NET 17.4.0.
This message was posted using Notification2Forum from Downloads module by Aspose Notifier.
I have tested the issues which have been addressed in 17.4.0 and listed the results below.
issue 51191 = confirmed as fixed
issue 51192 = NOT FIXED (the issue is still present)
issue 51193 = confirmed as fixed
issue 51200 = confirmed as fixed
Regards,
Andrew
Hi Andrew,
Thank you for the confirmation. In reference to the ticket ID DIAGRAMNET-51192, when you will save VDX in the SVG format using Microsoft Visio, there would be no spaces in Chrome display. However, Firefox shows spaces as you can see in source VDX using Microsoft Visio application. The latest version 17.4.0 of Aspose.Diagram API mimics the same behavior. Please let us know in case of any confusion or questions.
Hi Andrew,
Thank you for being patient. We have a good news for you that the ticket IDs DIAGRAMNET-51195 and DIAGRAMNET-51196 have now been resolved. If there is no issue in the QA phase, then their fixes will be included in the next version 17.5.0 of Aspose.Diagram for .NET API. We shall inform you via this forum thread as soon as the new release is published.
I can confirm that both these issues are now fixed.
Many thanks,
Andrew
Hi Andrew,
Thank you for the confirmation. It is nice to hear from you that the problem has been resolved. Please let us know in case of any further assistance or questions.
The issues you have found earlier (filed as DIAGRAMNET-51195;DIAGRAMNET-51196) have been fixed in Aspose.Diagram for .NET 17.5.
This message was posted using Notification2Forum from Downloads module by Aspose Notifier.
@andrew.ridgeley,
The linked ticket ID DIAGRAMNET-51199 has been resolved and will be included in the next version 18.1 of Aspose.Diagram for .NET API. We will notify you once the new version is published.
@andrew.ridgeley,
The linked ticket ID DIAGRAMNET-51199 has been fixed. Please download and try the latest version 18.1 of Aspose.Diagram for .NET API.
The issues you have found earlier (filed as DIAGRAMNET-51190,DIAGRAMNET-51194) have been fixed in Aspose.Diagram for .NET 19.5.
The issues you have found earlier (filed as DIAGRAMNET-51198) have been fixed in Aspose.Diagram for .NET 20.1.