Menu
Active2 months ago
- Itextsharp Html To Pdf Img Lost
- Itextsharp Html To Pdf Arabic C#
- Itextsharp Html To Pdf Multiple Pages
I am posting this question because many developers ask more or less the same question in different forms. I will answer this question myself (I am the Founder/CTO of iText Group), so that it can be a 'Wiki-answer.' If the Stack Overflow 'documentation' feature still existed, this would have been a good candidate for a documentation topic.
IText is a PDF library that allows you to CREATE, ADAPT, INSPECT and MAINTAIN documents in the Portable Document Format (PDF), allowing you to add PDF functionality to your software projects with ease. We even have documentation to help you get coding. GetUrl (string imagepath) function. Now we will create an instance of Document class obtained from ITEXTSHARP DLL.In order to create the PDF Document on the FLY. Now we create instance of HTMLWorker class ITEXTSHARP DLL from the namespace iTextSharp.text.html.simpleparser so that the rendered HTML can be worked upon and pass it to PDF Document.
I am trying to convert the following HTML file to PDF:
In a browser, this HTML looks like this:
HTMLWorker doesn't take CSS into account at all
When I used
HTMLWorker
, I need to create an ImageProvider
to avoid an error that informs me that the image can't be found. I also need to create a StyleSheet
instance to change some of the styles:The result looks like this:
For some reason,
HTMLWorker
also shows the content of the <title>
tag. I don't know how to avoid this. The CSS in the header isn't parsed at all, I have to define all the styles in my code, using the StyleSheet
object.When I look at my code, I see that plenty of objects and methods I'm using are deprecated:
So I decided to upgrade to using XML Worker.
Upstream b2 pdf. Images aren't found when using XML Worker
I tried the following code:
This resulted in the following PDF:
Instead of Times-Roman, the default font Helvetica is used; this is typical for iText (I should have defined a font explicitly in my HTML). Otherwise, the CSS seems to be respected, but the image is missing, and I didn't get an error message.
With
HTMLWorker
, an exception was thrown, and I was able to fix the problem by introducing an ImageProvider
. Let's see if this works for XML Worker.Itextsharp Html To Pdf Img Lost
Not all CSS styles are supported in XML Worker
I adapted my code like this:
My code is much longer, but now the image is rendered:
The image is larger than when I rendered it using
HTMLWorker
which tells me that the CSS attribute width
for the poster
class is taken into account, but the float
attribute is ignored. How do I fix this?Itextsharp Html To Pdf Arabic C#
So the question boils down to this: I have a specific HTML file that I try to convert to PDF. I have gone through a lot of work, fixing one problem after the other, but there is one specific problem that I can't solve: how do I make iText respect CSS that defines the position of an element, such as
float: right
?When my HTML contains form elements (such as
<input>
), those form elements are ignored.Bruno Lowagie
Bruno LowagieBruno Lowagie64.9k1010 gold badges8282 silver badges122122 bronze badges
2 Answers
As explained in the introduction of the HTML to PDF tutorial,
HTMLWorker
has been deprecated many years ago. It wasn't intended to convert complete HTML pages. It doesn't know that an HTML page has a <head>
and a <body>
section; it just parses all the content. It was meant to parse small HTML snippets, and you could define styles using the StyleSheet
class; real CSS wasn't supported.Then came XML Worker. XML Worker was meant as a generic framework to parse XML. As a proof of concept, we decided to write some XHTML to PDF functionality, but we didn't support all of the HTML tags. For instance: forms weren't supported at all, and it was very hard to support CSS that is used to position content. Forms in HTML are very different from forms in PDF. There was also a mismatch between the iText architecture and the architecture of HTML + CSS. Gradually, we extended XML Worker, mostly based on requests from customers, but XML Worker became a monster with many tentacles.
Eventually, we decided to rewrite iText from scratch, with the requirements for HTML + CSS conversion in mind. The hindu newspaper pdf download today free. This resulted in iText 7. On top of iText 7, we created several add-ons, the most important one in this context being pdfHTML.
Using the latest version of iText (iText 7.1.0 + pdfHTML 2.0.0) the code to convert the HTML from the question to PDF is reduced to this snippet:
The result looks like this:
As you can see, this is pretty much the result you'd expect. Since iText 7.1.0 / pdfHTML 2.0.0, the default font is Times-Roman. The CSS is being respected: the image is now floating on the right.
Itextsharp Html To Pdf Multiple Pages
Developers often feel opposed to upgrade to a newer iText version when I give the advice to upgrade to iText 7 / pdfHTML 2. Allow me to answer to the top 3 of arguments I hear:
I need to use the free iText, and iText 7 isn't free / the pdfHTML add-on is closed source.
iText 7 is released using the AGPL, just like iText 5 and XML Worker. The AGPL allows free use in the sense of free of charge in the context of open source projects. If you are distributing a closed source / proprietary product (e.g. you use iText in a SaaS context), you can't use iText for free; in that case, you have to purchase a commercial license. This was already true for iText 5; this is still true for iText 7. As for versions prior to iText 5: you shouldn't use these at all. Regarding pdfHTML: the first versions were indeed only available as closed source software. We have had heavy discussion within iText Group: on the one hand, there were the people who wanted to avoid the massive abuse by companies who don't listen to their developers when those developers tell the powers that be that open source isn't the same as free. Developers were telling us that their boss forced them to do the wrong thing, and that they couldn't convince their boss to purchase a commercial license. On the other hand, there were the people who argued that we shouldn't punish developers for the wrong behavior of their bosses. Eventually, the people in favor of open sourcing pdfHTML, that is: the developers at iText, won the argument. Please prove that they weren't wrong, and use iText correctly: respect the AGPL if you're using iText for free; make sure that your boss purchases a commercial license if you're using iText in a closed source context.
I need to maintain a legacy system, and I have to use an old iText version.
Seriously? Maintenance also involves applying upgrades and migrating to new versions of the software you're using. As you can see, the code needed when using iText 7 and pdfHTML is very simple, and less error-prone than the code needed before. A migration project shouldn't take too long.
I've only just started and I didn't know about iText 7; I only found out after I finished my project.
That's why I'm posting this question and answer. Think of yourself as an eXtreme Programmer. Throw away all of your code, and start anew. You'll notice that it's not as much work as you imagined, and you'll sleep better knowing that you've made your project future-proof because iText 5 is being phased out. We still offer support to paying customers, but eventually, we'll stop supporting iText 5 altogether.
Bruno LowagieBruno Lowagie64.9k1010 gold badges8282 silver badges122122 bronze badges
Abhishek SenguptaAbhishek Sengupta61711 gold badge44 silver badges1414 bronze badges
protected by Bruno LowagieJun 29 '18 at 8:30
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead? Zend studio 13.6.1 crack key.
Would you like to answer one of these unanswered questions instead? Zend studio 13.6.1 crack key.