We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Convert DOTX Word Document with Table having Solid Borders to PDF File using C# .NET | Support Cell Spacing

AsposeSampleApp.zip (181.9 KB)


We have found out an issue where .dotx document having borders around tables will loose the borders when saved to pdf (everything is fine when we save to docx)
attached is a sample app (with input file already included inside InputFiles directory) - please compile and run it (you will need to add Aspose.Words library). in OutputFiles folder should be two files in docx and pdf formats - if you check pdf file - there are no borders around the tables (they are present in docx file).

Could you please take a look and let us know if this can be fixed somehow?



We tested the scenario and have managed to reproduce the same problem on our end. For the sake of correction, we have logged this problem in our issue tracking system. The ID of this issue is WORDSNET-18532. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.

Is there any workaround that we could use to make it work for us for now? code or dotx template update



The issue occurs because cell spacing is currently not supported by Aspose.Words Layout engine.

The problematic table has a solid border specified at the table level. Nil border is specified at the cell level. The table has cell spacing, so both cell and table borders are visible in MS Word. As Aspose.Words layout currently does not support cell spacing, nil cell border supersedes table-level border and Aspose.Words renders the table without borders.

You may remove cell spacing from the problematic table as a workaround.

We will inform you via this thread as soon as this issue is resolved. We apologize for your inconvenience.

it’s been more than a year that this feature has been with aspose. Any progress?


We have completed the analysis of WORDSNET-18532; but I am afraid, the implementation of the fix of this issue has been postponed till a later date. There are no estimates (ETA) available at the moment. We will inform you here as soon as this issue will get resolved in future. We apologize for your inconvenience.