HTML conversion to PDF

Aspose.PDF Product Family
1

We have to convert HTML to PDF. Attached is the HTML and the PDF we are generating with aspose.pdf. We are using the latest version.

The text within tables is not flowing correctly. What needs to be done to convert the HTML as close as possible to a PDF?

J

2

Hi John,

Sorry for the delayed response. I’ve managed to reproduce the issue at my end and logged it as PDFNEWNET-35295 in our bug tracking system for further investigation and resolution. You will be notified via this thread as soon as it is resolved.

Sorry for the inconvenience faced.

Best Regards.

3

Has there been a fix to this issue?

Thanks,

John

4

Hi John,


Thanks for your inquiry. I’m afraid your reported issue is still not resolved. Its pending for the analysis in queue with other priority tasks. However, I’ve requested our development team to share some ETA. I’ll update you as soon as I get a feedback.

Thanks for your patience and cooperation.

Best Regards,
5

The issues you have found earlier (filed as PDFNEWNET-35295) have been fixed in Aspose.Pdf for .NET 9.2.0.

The blog post for this release is created over this link

This message was posted using Notification2Forum from Downloads module by Aspose Notifier.
6

Hi John,

As mentioned above, we are pleased to inform you that your reported issue has been fixed. You may use the new DOM-based approach to render HTML to PDF. It will fix your above-reported issue.

Please use the following code snippet, based on the new Document Object Model (DOM), with the latest release of Aspose.Pdf for .NET. It will help you to accomplish the task.

HtmlLoadOptions htmloptions = new HtmlLoadOptions();
// use the new conversion engine
htmloptions.UseNewConversionEngine = true;

Document doc = new Document(myDir + "input.htm", htmloptions);
doc.Save(myDir + "Output.pdf");

Please feel free to contact us for any further assistance.

Best Regards,

7

We are still having issues. We are not writing to a directory. we are passing the bytes.



Attached is the input HTML and the output PDF.



We also noticed a great reduction in speed with the latest code.

8

jbourds:
We are still having issues. We are not writing to a directory. we are passing the bytes.

Attached is the input HTML and the output PDF.


Hi John,

Thanks for your feedback. We have noticed that Property and Value columns are misaligned and logged an investigate ticket as PDFNEWNET-36945 for further investigation and resolution. Please confirm you are facing the only issue in formatting. So we will look into further.

Moreover in reference to reading/writing files, you may use Document constructor and Save method with stream parameter. It will help you to accomplish the task.

Best Regards,
9
jbourds:
We also noticed a great reduction in speed with the latest code.

Hi John,

We are sorry for the inconvenience caused. We will appreciate if you please share some more details about the issue. We will look into it and will provide you information accordingly.

Best Regards,
10

We are still waiting on a fix for converting HTML to PDF. Please see the attached.

11

Hi John,


Thanks for your patience.

We are pleased to share that the issue PDFNEWNET-36945 is resolved and it should not appear with latest release. Please try using the latest release and in case you still face the same issue, please feel free to contact.

Besides this, I have tested the conversion of above shared HTML (ClaimFile.html) to PDF format and have managed to reproduce that table formatting in resultant file is not correct. For
the sake of correction, I have separately logged it in our issue tracking system as PDFNEWNET-38104. We will
investigate this issue in details and will keep you updated on the status of a
correction.

We apologize for your inconvenience.

12

Do you have an estimated time frame for resolving this issue?

Is there anything I can do on my end to get this resolved?

13

Hi John,

As we have recently been able to notice the issue PDFNEWNET-38104, the development team requires a little time to investigate and figure out the reasons for this problem. Nevertheless, I have also intimated the development team to investigate this issue on a priority basis. As soon as we have made some definite progress towards its resolution, we would be more than happy to update you with the status of the correction.

Our humble request is to please be patient and spare us a little time.

14

any status on this? Would it help my cause if I went priority support?

15

Hi John,

Thank for your inquiry. As stated above we have recently noticed the issue, so issue investigation is still not planned. As soon as its investigation is completed then we will be in good position to share and ETA.

Moreover regarding to your priority support query, please note purchasing the Priority Support does not guarantee any immediate resolution of the issue but it increases its precedence over normal support and development team start investigating the issue on priority basis. Until or unless we encounter any technical limitation or the resolution is dependent upon any missing feature in product, the issue is resolved in timely manner.

Aspose offers three different types of enhanced support. Please check following links for the details/prices and enhanced support [FAQs](http://www.aspose.com/corporate/services/support-FAQs.aspx).

Furthermore, If you have any query related the enhanced support please post here. We will be more than happy to help you.

Best Regards,

16

The issue logged under the ticket ID PDFNET-38104 has been resolved in Aspose.PDF for .NET 25.12.

You can please download the latest release from:

If you have any further questions, please let us know.