Free Support Forum - aspose.com

Out of position and character orientation when rendering

Hello Team,



I have converted 0_20.vsd to 0_20.pdf with Aspose.Diagram. Please find error points with attached file.



1) Characters position (Page 3)

2) Characteres orientation (Page 3)



This is my code.

---------------------

public static MemoryStream ConvertDocumentToPdfStream(string docName, MemoryStream docStream)

{

MemoryStream pdfStream = new MemoryStream();



try

{

// Instantiate the License class

Aspose.Diagram.License license = new Aspose.Diagram.License();

license.SetLicense(“Aspose.Total.lic”);



// Convert .ppt and .pptx file to PDF.

Diagram diagram = new Diagram(docStream);

diagram.Save(pdfStream, Aspose.Diagram.Saving.SaveOptions.CreateSaveOptions(SaveFileFormat.PDF));

return pdfStream;

}

finally

{

}

}

------

Thank you,

PFU DSOL2

Hi,


Thank you for contacting support. We managed to replicate the highlighted issues in our working environment and have logged in our bug tracking system as below:

DIAGRAMNET-51240: Displaced text on converting a VSD to PDF
DIAGRAMNET-51241: Rotated characters of the text when converting a VSD to PDF

We have linked your post to these tickets and will keep you informed regarding any available updates. We are sorry for the inconvenience caused.

Hi,


Thank you for being patient. We have resolved the ticket ID DIAGRAMNET-51240. If there is no issue in the quality assurance phase, then this fix will be included in the next version 17.5 of Aspose.Diagram for .NET API. We will notify you in this forum thread as soon as the new release is published.

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


This message was posted using Notification2Forum from Downloads module by Aspose Notifier.

Do you have any updates about DIAGRAMNET-51241?

@PFU.DSOL2,

The analysis phase of the linked ticket ID DIAGRAMNET-51241 is not completed yet. We have logged an ETA request under the same ticket ID DIAGRAMNET-51241. We will let you know once a significant progress has been made in this regard.

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