This could be the same issue as PDFNET-17143 but the method I’m using to get to the issue is different, so I’m posting.
Thanks for using our products.
I am pleased to inform you that the issue has been resolved and we are currently busy with the testing of HotFix. Please spare us little time and we will get back to you with the status of correction, shortly.
Your cooperation and comprehension is greatly appreciated in this regard. We apologize for your inconvenience.
PS, As you have shared that the contents are coming from the database and you cannot update the contents. So I would request you to be patient and wait for the hotfix.
I need a timeline for when a fix or workaround will be available, so I can determine if I need to do a rollback.
I have contacted the development team to share the ETA regarding the resolution of this problem and once I have some updates, I would be pleased to update you with the status of correction.
Aspose.Words and Aspose.Pdf work independently and as per my understanding, the usage of different versions of two products might not cause any problem except for the case when we are using the legacy/conventional method of converting Word documents into PDF format using Aspose.Words and Aspose.Pdf. Nevertheless, I am still not certain about your exact requirement.
If you have so much urgency, then you may revert back to the older version and try using it. In case you encounter any issues, please feel free to contact. We apologize for your inconvenience.
I have discussed this matter with the development team and we expect to release the HotFix containing the resolution of this problem by the mid of this month (June-2010). Please be patient and spare us little time. We are sorry for your inconvenience.
The issues you have found earlier (filed as 17143) have been fixed in this update.