Preserve Widow Orphan Control Option during Word to PDF Conversion C# .NET & Manage Unwanted Line Breaks in PDF

Aspose.Words Product Family
1

Hi,
We have a document that is breaking a line during PDF rendering and looks different from it’s Word equivalent. Since this is an official document where we don’t want any difference between those two we consider this to be a defect.
Please look at the bottom line in the first page where it breaks after the word "Insurance"
I attached both the word and the pdf file.
We use WORDS 9.1.0.0
Any help is appriciated.
Regards,
Ron

2

Hi Ron,

Thanks for your request. I managed to reproduce the problem on my side. Your request has been linked to the appropriate issue. You will be notified as soon as it is fixed. If it is acceptable for you, you can try using the following code to work this problem around:

// Open document
Document doc = new Document("yourDoc.doc");
// Loop through all Sections
foreach(Section sect in doc.Sections)
    // Set PageSetup.PageWidth + 10
    sect.PageSetup.PageWidth = sect.PageSetup.PageWidth + 10;
doc.Save("out.pdf");

Best regards,

3

Hi,
I did try your suggestion but strange enough the page with in my PDF did not changed. It was 8.5" before in the Word template and after the transaction it was still 8.5" in the PDF. The saved word document however had a changed width (8.64")
I also tried to change the left and right margin but like with the width it was only changed in the word version of the Document.
Am I doning something wrong here or did we ran into a new defect?
Thanks,
Ron

4

Hi

Thanks for your request. I just tested with your document one more time, and it works.
I use the following code:

// Open document
Document doc = new Document(@"Test\634129104120317761Welcome+Letter1.Doc");
// Loop through all Sections
foreach(Section sect in doc.Sections)
    // Set PageSetup.PageWidth + 10
    sect.PageSetup.PageWidth = sect.PageSetup.PageWidth + 10;
doc.Save(@"Test\out.pdf");

I send the PDF document produced on my side to your e-mail.
Best regards,

5

Hi,
The suggested workaround only works when I save my doc object first than load it again and then change the page width. So far so good.
However the line I mentioned is not the only one that is different from the template documents after rendering the pdf. This workaround will not be accepted by my customer because of the following.
We are dealing here with insurance policies containing text blocks that are approved by the legal department and some provided by the us goverment such as HIPPA. Based on the customers needs we build policies dynamically. The layout of the end result MUST look 100% the same as the layout of the used text blocks (from a legal point of view). The created policy in WORD format looks ok even as the printout that will be send to the customer. The PDF version that is used for Archiving and internet publishing (to the customer) looks different on many pages and that is not acceptable.
If I save the document to PDF in WORD itself it keeps the Layout as it is in WORD.
I hope you get my point and give this the appropriate attention. This is really the second issue I have with PDF rendering that cost me a lot of dissatisfaction from my customers.
Thanks,|
Ron

6

Hi

Thank you for additional information. Currently I cannot suggest you any other way to work this problem around. You should just wait for the fix of the original issue.

In additional, please follow the link to see the table which provides implementation details about how Aspose.Words saves a document in the PDF format.

Best regards,

7

Hi,
My customer is getting very frustrated and is running out of patience because I can’t give them a time estimate when this issue will be resolved. Basically I can’t blame them and I feel the same.
I already upgraded my support to priority support in the hope things are moving a little faster. How can we do Business when we don’t get an SLA from Aspose regarding software bugs.
Please provide me with an e-mail address or channel to someone higher up in the support organization so I can escalate my open issues.
Thanks in advance,
Ron van Leeuwen

8

Hi Ron,

Thanks for your request. I raised priority of the issue. We will keep you informed on any developments regarding this issue.
Best regards,

9

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

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