@bhanu410 Unfortunately, I cannot reproduce the problem on my side using the latest 22.12 version of Aspose.Words for .NET. Please try using the latest version:
@bhanu410 It looks like content is pushed down by the evaluation message at the beginning of the document. You can request a temporary 30-days license to test Aspose.Words without evaluation version limitations.
@alexey.noskov we already have a license, 22.05 is working fine. do we need to get new license if we upgrade to latest version?
@bhanu410 Every Aspose license provides a 1-year subscription for free upgrades to any new Aspose.Words version that comes out. You can update to any Aspose.Words version released before the subscription expiry date.
You can check when your subscription expires, just open the license file in Notepad (but take care not to modify and save the license file or it will no longer work) and see the SubscriptionExpiry field.
It means that you can free upgrade to version of Aspose.Words published before 02/18/2022.
@bhanu410 It looks like the problem on your side occurs because lack of the fonts required to render the document:
Aspose.Words needs the fonts used in the document to build document layout upon conversion to PDF. If Aspose.Words cannot find the font used in the document, the font is substituted. This might lead into fonts mismatch and document layout differences. You can implement IWarningCallback to get notifications when font substitution is performed.