Somewhat related to a post that I made the other day (<a href="https://forum.aspose.com/t/103782), I would be quite pleased to see OTF font support across the board. It seems that Aspose.Words already supports saving a word document as PDF and the OTF font gets embedded in the PDF, but with Aspose.Cells and Aspose.Slides, neither of them will embed the OTF font when saved as a PDF. This has been a little problematic for my company as we have been working to switch to Aspose products for converting many of our document formats to PDF, but the lack of support for OTF fonts in Aspose.Cells and Aspose.Slides has been a bit of an issue for us as the component that we are trying to replace with Aspose already supports OTF fonts.
Thanks for your posting and using Aspose.
I am representative of Aspose.Cells team.
We have already logged your issue with ticket id: CELLSNET-41130. We have now linked your current thread with this issue id and logged your comments in our database.
We will look into your requirements and once there is some update for you, we will let you know asap.
Aspose.Slides support team will also respond to your thread as soon as possible.
Thanks Shakeel! Just to clarify, the reason I created this post separately from my other one is that this is more specifically a feature request, whereas the other issue I posted about was a bug that just happened to be related to the OTF font type. I just didn’t want to combine the bug and the feature request into one post.
Thanks for your clarification.
Actually, to my knowledge, this feature is not available, so I have not logged it as a bug but I have logged it as an investigation ticket.
Once, there is some update relating to it from developers, then we will edit it as a New Feature Request or create a separate new ticket for it.
Your both issues are related in a sense that both depends on the same feature.
Thanks for using Aspose.Cells.
For your issue logged as CELLSNET-41130, the exception problem has been fixed in Aspose.Cells for .NET 8.4.2. We do not support OTF and we find the font to replace it.
The issues you have found earlier (filed as SLIDESNET-33764) have been fixed in this update.