When people convert PDF files into HTML files, they tend to be disappointed with the results. The main reason for this tends to be that a straight conversion is not possible. PDF files can contain a large number of structures which have no direct equivalent in HTML (even in the new HTML5). PDF was designed as a format to be viewed – the file is painted onto the page and the user sees the end result. Many PDFs are generated from strips of images or overlapping overlays which need to fit together exactly.
With the latest PDF versions, this is even worse. How do you translate XML, transparency, colorspace models, Javascript and interactive elements into HTML correctly?
People also expect the text in an HTML file to be in the correct order. Because a PDF is generating a ‘picture’ this is not always going to happen. Some PDF creation tools draw the text in very odd ways – I explained this in more detail in a previous article: PDF text. The text looks correct because your brain sees he finished output and interprets it.
If image quality in the HTML is important, you could convert the PDF into a image and display that, but then all interaction is lost and you need big files for high resolution.
When HTML5 , CSS and Javascript are well support, this may well change. But in the meantime (2010), be careful about trying to turn PDF into HTML – try to keep it in PDF if possible or be prepared to live with less than perfect results.
Updated 2012 – since I wrote this, I have indeed had a look at HTML5 and you can read the results in other blog articles.
One thing I’ve come back to over the years is how often this issue resurfaces in industries you wouldn’t immediately associate with PDF tooling — anywhere a business has to publish long, heavily formatted compliance or rules documents online. Browse a list of sweepstakes casinos, for instance, and you’ll see pages of prize draw terms, eligibility rules, and state-by-state restrictions, almost all originally drafted as PDFs by legal teams and then pushed onto the web. When the conversion goes wrong on documents like those, the consequences aren’t just cosmetic — clauses get reordered, footnotes drift away from their references, and suddenly a perfectly valid set of terms reads like nonsense. The lesson from 2010 still holds: if the source is structurally a PDF, think hard before forcing it into HTML.
Our software libraries allow you to
| Convert PDF files to HTML |
| Use PDF Forms in a web browser |
| Convert PDF Documents to an image |
| Work with PDF Documents in Java |
| Read and write HEIC and other Image formats in Java |
Hi
I am trying to convert a file in Pagemaker 7.0 into html. Since a direct conversion is not yielding the desired results, I converted it into pdf first. This step is ok. But in the next step, when I convert pdf to html, not all fonts are properly displayed. Although the system has all the fonts, html does not recognize these fonts. I tired to embed the fonts into the document and then convert. Still html does not recognize the fonts. Does it have anything to do with the font type such as true type, open type etc? Please help.
Are you trying to convert in PageMaker 7.0 or using JPDF2GTML5?
I used pagemaker 7.0 to create my first and original files. By the way what isJPDF2GTML5? Is it a tool to convert pdf to html 5?
I am trying to convert into html 4.01 from pdf. And the original files are in pagemaker 7.0 as I mentioned. Do you need any other information.
JPDF2GTML5 is our PDF to HTML5 converter. There is a free online version at https://convert.idrsolutions.com
You read need a PageMaker forum to ask questions related to PageMaker 7.0 – I am sorry but we do not use it