There is another problem with converting vsdx to SVG format. The Vsdx file contains simple balloons with embedded text labels. After conversion, the text labels become gigantic in size and extend beyond the balloon areas. I do a simple transformation via the method Diagram.Save according to documentation (Diagram.Save method).
I attached the original Visio diagram (InputFile1.vsdx) and SVG file (OutputFile1.svg) obtained after transformation.
Could you review my files from the attached archive and fix the problem in the next release?
Summary
When a VSDX file that contains balloon shapes with embedded text is saved to SVG using Diagram.Save, the text in the resulting SVG can appear much larger than it does in Visio, causing it to overflow the balloon boundaries.
Why it happens
The SVG exporter may handle DPI and text‑fit information differently from Visio. This can lead to a mismatch in the way font sizes are interpreted, resulting in oversized text in the SVG output. The behavior is specific to the SVG serializer; other export formats (PDF, PNG, etc.) usually render the text correctly.
What to do next
Verify the Aspose.Diagram version – Make sure you are using the latest released version of Aspose.Diagram for .NET. If you are on an older build, upgrade and test again, as the issue may have been addressed in a newer release.
Try using SVG export options – If the SDK provides SvgSaveOptions (or a similar class), experiment with its properties that control DPI or text rendering. Adjusting these settings can sometimes align the SVG output with Visio’s appearance.
Provide diagnostic information – If the problem persists, gather the following details for the Aspose support team:
Exact Aspose.Diagram for .NET version you are using.
A minimal code snippet that reproduces the oversized‑text behavior.
Whether the issue occurs only with balloon shapes or with any shape that contains text.
Samples of the input VSDX and the generated SVG (you can share them via a support ticket).
Compare with other export formats – Export the same VSDX to PDF or PNG using the same SDK version. Correct rendering in those formats confirms that the issue is isolated to the SVG exporter.
If after these steps the text size is still incorrect, please open a support ticket with the collected information so the development team can investigate the issue for a future fix.
I could not fully verify this explanation against the retrieved sources. Please double-check the behaviour in your environment and confirm the exact SDK/version.
@krserg
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): DIAGRAMNET-53856
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
The issues you have found earlier (filed as DIAGRAMNET-53856) have been fixed in this update. This message was posted using Bugs notification tool by philip.zhou
I could not fully verify this explanation against the retrieved sources. Please double-check the behaviour in your environment and confirm the exact SDK/version.