pdf2htmlEX

If you are like me who was a fan of pdf2htmlEX, you would be almost as heart-breaking as me when it's archived about 8 years ago. Another attempt to release and RC was 6 years ago. At some point, one cannot even compile it anymore. This is why I decided to give it a go with Ox-Alpha. After running 40 workflows, I finally did it, and validated it on macOS and Ubuntu. I made three design decisions: 1. upgrade the dependencies (obviously) to make it compilable; 2. the resulting binary should be statically linked so anyone can download it and run; 3. Drop windows support. Feel free to have fun with it. I will find some time to curate a list of PDFs for testing purposes, and I'm open to bug and improvements through issues. But since this is agent-assisted, I disabled PR. If you want your own flavor of pdf2htmlEX, please don't hesitate and fork

"Free" book. Actually a really annoying (to the point of unusable) dynamic-loading paginated html page. Surely nobody'd ever want to learn anything (much less RISC-V assembly) like this. <!-- Created by pdf2htmlEX (https://github.com/coolwanglu/pdf2htmlex) --> The PDF itself nowhere to be found, although I expect one will be generated by hackish means and uploaded somewhere soon. (edit: z-library and Anna's both have it as PDF) The simulator is similarly locked behind the webbrowser, but seems to be at least based on an open source one[0]. Whether it has been modified is unclear. 0. https://github.com/antoniocgj/RISC-V-ALE

I don’t think it’s a question of standards. It’s more that HTML and PDF are different things that solve different problems. PDF is supposed to be a static document that looks exactly the same in every compliant PDF reader. A correctly built PDF with have every glyph that it uses embedded, for example. It’s archival, in the sense that it will always look the same, in all future versions of PDF readers. HTML is markup that describes the author’s intentions to the browser. The reader can use his or her own fonts and have other preferences. The text might reflow to fit screens of various sizes. I can read it on my terminal with lynx. You can embed all kinds of resources from the network. One can take heroic measures¹ to force an exact rendering, but, in my opinion, that’s a dead end that hacks a markup system to do what it’s not intended to d

For non-reflow conversion there is pdf2htmlEX: https://github.com/coolwanglu/pdf2htmlEX is discontinued but there is development under https://github.com/pdf2htmlEX/pdf2htmlEX Demo: https://pdf2htmlex.github.io/pdf2htmlEX/doc/tb108wang.html

The pdf2htmlEX program does this. It creates exact renditions of PDFs in HTML, using embedded fonts and positioning each character. Personally, although it’s an amazing demonstration, I don’t really understand the purpose, when you can just distribute the PDF. https://github.com/coolwanglu/pdf2htmlEX

I'm parsing PDFs and extracting tabular data - I am using this library https://github.com/coolwanglu/pdf2htmlEX to convert the PDF into HTML and then parsing thereafter. It works reasonably well for my use-case but there are all kinds of hacks that I've had to put in place. The system is about 5-6 years old and has been running since. The use-case is basically one where there is a tabular PDF uploaded every week and the script parses it to extract the data. Thereafter a human interacts with the data. In such a scenario, every ~100 parses it fails and I'll have to patch the parser. Sometimes text gets split up, but as long as the parent DOM node is consistent I can pull the text of the entire node and it seems to work fine.

Looking at the HTML source, it appears they've used pdf2htmlEX: https://github.com/coolwanglu/pdf2htmlEX / http://coolwanglu.github.io/pdf2htmlEX/ -- the first demo there (which is also from a scan) also seems to have the same property you mentioned.

Best one I have found. https://github.com/coolwanglu/pdf2htmlEX

Great work. I've also been working on a similar open-source project "Sharead". https://github.com/strin/sharead It has a chrome extension that uploads Arxiv papers, and you can manage papers with tags. It also automatically converts pdf to HTML using a library called pdf2html: https://github.com/coolwanglu/pdf2htmlEX

The HTML source contains this: <!-- Created by pdf2htmlEX (https://github.com/coolwanglu/pdf2htmlex) -->

pdf2htmlEX (https://github.com/coolwanglu/pdf2htmlEX) would be another route if you aren't concerned about preserving the semantics of the markup. Obviously you would to go LaTeX -> PDF -> HTML5. It maintains the paginated style and looks good for scientific papers (example: http://coolwanglu.github.io/pdf2htmlEX/demo/demo.html)

Congrats to the PDF.js team for the adoption. I'm curious as to how the pdf2htmlEX project [0] compares to PDF.js. Instead of client-side conversion this is a server-side one-time conversion from PDF to HTML5. [0] https://github.com/coolwanglu/pdf2htmlEX

Looks like they used pdf2htmlEX (https://github.com/coolwanglu/pdf2htmlEX)

Many of the world's most important documents are locked away in PDFs - perhaps the world's worst file format. Let's work to right that wrong. I am assembling a team of sharp individuals to design and develop an application that can be used to render PDFs in a browser with zero loss of fidelity (this is important as many of my use cases deal with TeX) and functions to annotate and markup the document. Markup could be collaborative.<p>The tools available in the marketplace are subpar at best - let's raise the bar and give people tools they're actually excited to use :-)<p>Some potential components: https://github.com/coolwanglu/pdf2htmlEX https://github.com/kermitt2/grobid https://github.com/openannotation/annotator https://github.com/hyperstudio/Annotation-Studio https://developers.google.com/drive/realtime/overview http://quilljs.com/<p>F