We wanted to have a piece of text with a different font, Wingdings, that has ID=3 in the Fonts list of the document. So we changed one line in the sample code.
// Just a little modification. We would like to have another font here (the “Wingdings” font → ID = 3).
shape.Chars[1].Font.Value = 3;
The result is that output saved by the code shows three problems:
The font of the text belonging to the given formatting shows in Calibri, and not in Wingdings.
When we edit the respective shape, the dorpdown on the ribbon of Visio, that should show the font of the text is blank.
All the text that comes after the one with the problematic font is squashed, the letters are on top of each other. When the shape is edited, then they show as one-pixel smudge.
We managed to replicate the said issues in our environment. An investigation has been logged under the ticket ID DIAGRAMNET-51469 in our issue tracking system. We have linked your post to this ticket and will keep you informed regarding any available updates.
The issues you have found earlier (filed as DIAGRAMNET-51469) have been fixed in Aspose.Diagram for .NET 18.6. This message was posted using BugNotificationTool from Downloads module by imran.rafique
What the sample code does is to crate a document with formatting, save it, then reload it into a diagram object.
What you can see on the first page of the pdf is that before saving the diagram has 4 character styles, however reloading the resulting document results in 7 styles.
If we save a document with four styles we expect the same number after reloading it as well.
We managed to replicate the problem of the font count in our environment. An investigation has been logged under the ticket ID DIAGRAMNET-51494 in our bug tracking system. We have linked your post to this ticket and will keep you informed regarding any available updates.