Bad tooltip generated in HTML

Aspose.Diagram Product Family
1

Hi,

When saving a vsdm ou vsdx file in HTML, the tooltip are not rendered as they should be.

When saving the file “Direction.vsdm” with Aspose.Diagram in HTML the result is :

  • direction.html
  • Screenshot_TooltipWithAsposeDiagram.png

When saving it with Ms Visio (Microsoft) in HTML the result is :

  • Direction_With_Microsoft_Visio.htm
  • Screenshot_TooltipWithMsVisio.png

As you can see in the screenshots, the correct tooltip should be IQ822.

Done with Aspose.Diagram version : 19.10.0.0
All the files in the zip

files.zip (2.2 MB)

Thanks,

2

@julien.mevel.isilog

Thank you for contacting support.

Would you please also share SSCCE code that you are using for this conversion, so that we may try to reproduce and investigate it in our environment.

3

Hi,
You can reproduce with that simply code :

            // The path to the documents directory.
            string dataDir = dataDir = @"D:\Temp\";  
            
            // Load diagram
            Diagram diagram = new Diagram(dataDir + "DIRECTION.vsdx");
            // Save diagram
            diagram.Save(dataDir + "outputVSDXtoHTML.html", SaveFileFormat.HTML);
            // ExEnd:ExportToHTML

In the newfile.zip :

  • DIRECTION.vsdx is the input file
  • outputVSDXtoHTML.html is the output done with the previous code
  • Screenshot_with_aspose_Diagram.png is the result you can see

And in the “html_area_tag.png” the content of the HTML generated for the area tag, where you can see that the property “Title” is not correct.

newfiles.zip (1.4 MB)

Thanks.

4

@julien.mevel.isilog

We were able to replicate the issue in our environment and have logged it as DIAGRAMNET-51730 in our issue tracking system. We will further investigate the issue in details and keep you posted with the status of its correction. Please be patient and spare us little time.

We are sorry for the inconvenience.

5

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

6

Hi,

I confirm that this issue is solved with Version 19.12.
Thanks.