Print Fixed layout HTML after conversion from DOCX does not work correctly using .NET

When converting a multi-page A4 Word document to HTML using a fixed layout using Aspose, the resulting HTML looks good, and very close to how the document looked in Word.

However, when printing this HTML, it doesn’t line up quite right with A4 pages. It appears that the “pages” rendered are slightly taller than A4 so by the time you are several pages into the document, the page breaks are mid way down the physical pages in the printout.

Is there a setting I can change to improve this?


Could you please ZIP and attach your input Word document along with problematic output HTML here for testing? Please also share steps that you are using to print the HTML. We will investigate the issue and provide you more information on it.

See attached. File > Print from Chrome or Firefox will exhibit the issue. (40.2 KB)


Thanks for sharing the documents. Could you please share the screenshots of problematic printed document? We will then log this issue in our issue tracking system.

“Print to PDF” produces exactly the same issue so I’ve attached the PDF - I hope that makes sense. Thanks.

page-break-test.pdf (1.6 MB)


We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-21371. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

Thanks for the update. Are you able to give me a rough idea of when this is likely to be addressed? I’m aware I could chose to pay for a higher level of support, but it would be helpful to have at least an approximate idea of when this might get fixed ordinarily.


We try our best to deal with every customer request in a timely fashion, we unfortunately cannot guarantee a delivery date to every customer issue. We work on issues on a first come, first served basis. We feel this is the fairest and most appropriate way to satisfy the needs of the majority of our customers.

Unfortunately, there is no ETA available for this issue at the moment. We will inform you via this forum thread once there is an update available on it.

The issues you have found earlier have been fixed in this Aspose.Words for .NET 20.12 update and this Aspose.Words for Java 20.12 update.