Thanks for your patience. The development team got busy resolving other high priority issues and I am afraid this issue is not yet resolved. Nevertheless, I have again intimated the team to further look into this matter and share the latest status regarding its resolution. As soon as we have some further updates, we will let you know.
Well this shall I say is disappointing to hear. I am really questioning the benefit of a subscription if it takes more than 6 months for you to even look at an issue.
I can understand that this isn’t a critical issue, but it does involve a rendering issue which makes PDF output pretty much useless to put in front of end users. From my prospective it is serious enough to log the issue and keep chasing it up.
Really looking forward to some positive news and outcomes from you soon.
As shared earlier, we estimated that we will be able to get this problem fixed in July-2014 release, however due to the complexity of this problem and high priority of other issues, it has not been fixed. However, I am in coordination with development team to get some further updates regarding the resolution of this problem.
The development team has started investigating this issue and I have requested them to share the possible ETA. As soon as we have some further updates, we will let you know.
Thanks for your feedback. I am afraid the issue is quite complex and we have planned to fix it in our new DOM approach. It needs a lot of changes and improvements in our API structure. Our development team has revisited the issue and set ETA to Q1/2015. However we raised your issue priority to high, escalated issue to the management and requested to fix it ASAP.
Thanks for letting me know. I am not sure what to say except I am very, very disappointed that it has taken over 6 months to tell me this and that I have to wait at least another 6 months to be fixed which puts it out of our subscription.
I would be interested to know what you can do around this to make me less disappointed…
Keeping your urgency in mind, the development team has worked really hard and we are pleased to share that the issue reported earlier as PDFNEWNET-36461 is resolved and its fix will be included in upcoming release of Aspose.Pdf for .NET 9.6.0 which is planned to release in current week or early next week.
In order to generate correct output, please try using the new Document Object Model (DOM) of Aspose.Pdf namespace. Please try using the attached code snippet.
For your reference, I have also attached the resultant PDF generated at our end.