Currently the supported PDF rendering tools are quite hardcoded inside the module. IMHO it would be a welcome enhancement to provide info on the available engines through hooks, and PDF engine support can be put into separate modules then as well.

This will make it a lot easier to integrate other PDF tools without having to patch the main print_pdf module.

Comments

drupalnesia’s picture

drupalnesia commented

+1

I am using wkhtmltopdf and I found this module not implemented all of wkhtmltopdf features/settings, currently I make my own patch to achieve my project requirements.

How about to make a separate module based on each PDF engine? Something like "wkhtmltopdf module"?

With specific PDF engine per module then we can:
- implemented all features of particular PDF engine
- ask and answer question more straight forward
- easy to maintain and extend module

jcnventura’s picture

jcnventura
Primary language English
commented
Status: Active » Postponed

This is in my TODO list. It's also one of the reasons why I stopped adding PDF libraries to the module.

jcnventura’s picture

jcnventura
Primary language English
commented
Version: 6.x-1.x-dev » 7.x-2.x-dev
Status: Postponed » Fixed

Just committed the new system to dev.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.