Major conversion issue for doc to pdf using Aspose.Words 6.5.0.0 doc to pdf - header or image conversion problem

Aspose.Words Product Family
1

There is a major issue with converting doc files to pdf using Aspose.Words.6.5.0.0 Look at the attached DOC file generated with Aspose 6.5.0.0 and notice the table has a header line and two content lines. Everything is correct. Look at the conversion of this doc to the attached PDF and the content lines are hidden and the image covers them up or the header was reduced in the conversion.

2

Hi

Thanks for your request. I see the problem in your PDF, but this problem does not occur when I use the latest version of Aspose.Words (6.5.0) to convert your document to PDF. Please try using the latest version. You can download it from here:

http://www.aspose.com/community/files/51/file-format-components/aspose.words-for-.net-and-java/entry186045.aspx

Best regards.

3

Alexey, we are not converting a Word to document to a PDF. The issue is generating the PDF directly from the Aspose.Words object in memory. The attached documents were generated from the same object in memory. We called Save to generate the DOC file and SaveToPdf on the Aspose.Words.Document object to generate the PDF file.

4

Hi

Thank you for additional information. In this case, could you please provide me sample code, which will allow me to reproduce the problem on my side or maybe, create sample application? I will check the issue and provide you more information.

Best regards.

5

The attached program generates a PDF file using Aspose.Words. Several tables are placed in the header of the doc. In Aspose Words 6.4, the tables are created correctly in the pdf file. In 6.5 they are not.

Thanks.

6

Hello!

Thank you for reporting this.

I have reproduced the issue and registered it under reference number #9801. We’ll notify you when it’s fixed.

Regards,

7

The issues you have found earlier (filed as 9801) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
8

This issue was not fixed in this update. I took the program and compiled it using the DLL from the Aspose 6.6 project. Attached are the DOC and PDF files that resulted. Notice the PDF is not fixed.

9

Hi

Thanks for your request. I cannot reproduce the problem on my side using the latest version of Aspose.Words. I attached PDF document produced on my side.

Do you do any preprocessing of your document before saving it as PDF?

Best regards.

10

We do not do any preprocessing. I still can’t get the program originally attached to work with version 6.6 that we downloaded from the website. The program I compiled was on XP SP3. The Aspose.Words.dll I have been using has a size of 3,155,584. Explorer reports the file is version 6.6.0.0, Product version 2009.08.05. I can zip up the entire directory if you like and send it to you.

11

Hi Jeff,

Thank you for additional information. I ran conversion on Win XP SP3 too and no problems occur on my side (you have seen the document produced on my side.). IT would be great if you attach simple application, which will allow me to reproduce the problem. I will further investigate the issue and provide you more information.

Best regards.

12

Attached is our sample program, slightly edited so the version of the Aspose.words.dll file is printed in the reports, along with the dll. A doc and pdf are created in the same directory as the executable. I don’t think a license file is necessary.

13

Hi Jeff,

Thank you for additional information. The example, you have attached, allows me to reproduce the problem, but could you also provide me source code of this example. This will help us to understand where the problem occurs.

Best regards.

14

I’m attaching the code. It is largely the same code used before.

15

Hi Jeff,

Thank you for additional information. I managed to reproduce the problem and linked your request to the appropriate issue. You will be notified as soon as it is resolved.

The problem occurs because your headers is built from few tables one after another. As a workaround, you can try building your header as a single table, this should resolve the problem.

Best regards.

16

Alexey, just checking to see if there is an update on this issue. Thanks.

17

Hi Jeff,

Thanks for your inquiry. The problem is still unresolved. Have you tried to work the problem around by building your header as a single table instead of inserting several tables?

Also as a workaround you can insert an empty paragraph between tables. For example, see the following code:

// Open document.

Document doc = new Document(@“Test001\in.html”);

// Get collection of tables

NodeCollection tables = doc.GetChildNodes(NodeType.Table, true);

Paragraph spliter = new Paragraph(doc);

spliter.ParagraphBreakFont.Size = 1;

// loop through all tables

foreach (Table table in tables)

{

// Check if the next node after the tabel is another table.

// If so, insert an empty paragraph between tables.

if (table.NextSibling != null && table.NextSibling.NodeType == NodeType.Table)

table.ParentNode.InsertAfter(spliter.Clone(true), table);

}

// Save output document

doc.SaveToPdf(@“Test001\out.pdf”);

Best regards.

18

The one table approach runs into problems with spacing in the PDF. In the word document it works fine. In the PDF the various columns try to align when I don’t want them to, and I’m betting that’s a PDF issue and not an Aspose issue.

I will investigate the paragraph. That may work for us. Thanks for your help.

19

This seems to work. I’ll update if we run into bugs in the future but for now this seems to be working. Thanks.

20

The issues you have found earlier (filed as 9902) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by aspose.notifier.
(45)