Please take a look at the documents i attached. The test.doc is built using the file named AlertPrintTemplate.doc and is two documents appended together. The Toc merge field of the second document is overlaying merge field of the first. The Toc fields are Headings that will be used to build the TOC for a PDF using Aspose Pdf.
The two documents are appended using this method:
Please let me know, do you mean (24) 900HC405 (24) 030924 through 030925 row in the table that is overlaying the text of the page footer in the resulting PDF? Is it the problem that you are referring to?
Hello!
Aspose.Words doesn’t split document contents to pages. Table row with text “(24) 900HC405 (24) 030924 through 030925” should probably go to the text page in Aspose.Pdf. And also after this row there is one empty row with smaller height renders unexpectedly. I’ll notify Aspose.Pdf team to take appropriate action.
Regards,
sorry, i got my bugs mixed up. I attached a project that will create a word doc from 2 xml files. The project opens at template doc (AlertPrintTemplate.doc) and creates a file called overlap.doc (which is also included). The problem is the first merge field for the appended doc overlaps the first merge field of the first doc. The fields are heading fields and are used to create a custom string to be used in the TOC of a pdf made with Aspose pdf. It does not show in the pdf because we set the font color to white on white and make the font size 1 pt during the pdf processing. That was the workaround the Aspose Pdf team came up with for us to be able to have custom headings in the TOC. We may want to publish the Word document in the future so I need to get the overlap corrected in the actual document output. I modified a project that i sent to the pdf team for an issue on the pdf side.
Calling it is disastrous for the document layout. If you comment it out you will get a good result without any overlapping. It is not an Aspose.Words problem. Applying this style to a good resulting file made like described above produces the same disastrous layout. So please consider getting rid of this line in your code.
Hope this helps,