2

I see one solution so far:

http://www.htmldoc.org/

Are there any more out there which are suggested?

4
  • HTMLDOC is the standard – any reason for not wanting to use it?
    – slhck
    Commented Sep 21, 2011 at 19:30
  • I just didn't know it was "The" standard - so I asked. But from your answer, I understand that I should not bother with alternatives :)
    – Tal Galili
    Commented Sep 21, 2011 at 20:27
  • I've searched for similar things but – at least on *nix systems, I've always got back to HTMLDOC :)
    – slhck
    Commented Sep 21, 2011 at 20:32
  • @slhck Two reasons - lack of support for unicode and css in the stable 1.8.27 release. However, they are apparently supported in v1.9b1 (the notes mention "basic support"). Commented Oct 30, 2013 at 16:28

2 Answers 2

4

by using http://wkhtmltopdf.org/ you can do it like this:

$> wkhtmltopdf http://superuser.com su.pdf
0
0

One alternative to HTMLDOC is Prince.

PROs: Prince can handle most of CSS (which HTMLDOC can't) and use almost all fonts (where HTMLDOC PDFs contain only Helvetica, Times and Courier) and translate HTML/XML input into really well looking pages.

CONs: Unlike HTMLDOC, Prince isn't OpenSource software (though free as in beer for private use, putting a rather unobtrusive logo on PDF pages created with it).

PrinceXML is made by a small Australian company and seems to be also driving Google Docs' PDF output.

HTMLDOC is 'good enough' for most people's needs (and also provides quite a few features which Prince doesn't).

Not the answer you're looking for? Browse other questions tagged .