3 ms·
Agreed for arbitrary HTML, but there a lot of webapps (including one I've written) where it's useful to be able to produce PDF output. When you control the HTM
by epe 17y ago
Agreed for arbitrary HTML, but there a lot of webapps (including one I've written) where it's useful to be able to produce PDF output. When you control the HTML and can test that it converts to PDF the way you want, this can be much faster than trying to generate PDFs from raw Postscript or whatever.
- teilo 17y agoExactly. This has countless applications. Vastly simpler to create an HTML report, and convert to PDF, than to program said report in some sort of PDF library. You can use your framework's template library, and leverage existing skills. Your designers can design reports as easily as pages. On my Mac, the kerning was wacked on Arial. Probably something that can be done about that. But all in all - highly impressive.
- danp 17y agoI found that the font rendering with this was a little weird in general. Arial was pretty horrible, other fonts were a bit better but letter spacing was still always a bit off (this was on a PC btw, so it's not just Mac). I was never able to figure out what was going on, so we ended up going with a for-pay html-to-pdf library because it didn't have the same font rendering issues.