Font size of text is changed after joining documents using .NET

We just moved from AsposeWords .Net 17.9.0 to 20.2.0. During our testing we found a situation where after appending a document via “primaryDoc.AppendDocument(secondaryDoc, ImportFormatMode.KeepSourceFormatting)” the font size of the appended document is incorrect. We see the same unwanted result when exporting to both PDF or Docx files.

For a clear example of this situation, please refer to the uploaded Zip file, “AsposeFontSizeTest.zip” which contains the following:

  • InputPrimaryTestDocument.docx and InputSecondaryTestDocument.docx simplified source Word documents

  • OutputTestDocument_AsposeVer17-9-0.pdf and OutputTestDocument_AsposeVer17-9-0.docx output files showing desired results generated with ver 17.9.0

  • OutputTestDocument_AsposeVer20-2-0.pdf and OutputTestDocument_AsposeVer20-2-0.docx output files showing unwanted results generated with ver 20.2.0

  • ScreenCapturePDFGoodVsBad.PNG and ScreenCaptureDocxGoodVsBad.PNG comparison screenshots highlighting the problematic font size issue

  • Simple “AsposeFontSizeTest” VS2019/VB.Net/WinForm solution that we built to demonstrate the issue. The solution contains 2 projects (FontSizeTest _AsposeVer17-9-0 & FontSizeTes_AsposeVer20-2-0). Note to run an Aspose license file is needed, Nuget pakages for Aspose ver 17-9-0 & ver 20-2-0 need to be added to corresponding projects & adjustment to the “TestPath” variable for your environment.

Can you please let us know what the latest version of Aspose.Words .Net WITHOUT this issue is?

Can we get any idea of when this situation might be addressed?

Could you suggest a viable work-around for the time being.

Thanks in advance for your help with this issue,

Jeff
AsposeFontSizeTest.zip (1.0 MB)

@JDiamond

We have tested the scenario using the latest version of Aspose.Words for .NET 20.3 and have not found the shared issue. So, please use Aspose.Words for .NET 20.3.

Tahir,

Thanks very much for your prompt attention to this issue!

I can confirm that Aspose.Words for .NET 20.3 resolves this issue.

Jeff

@JDiamond

Thanks for your feedback. Please feel free to ask if you have any question about Aspose.Words, we will be happy to help you.