-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Other backends than wkhtmltopdf #37
Comments
@shouze this is good idea, what kind of help you need to make PR with support of prnicexml? |
Since here is no activity and PrinceXML is non-free, it can not be applied to snappy itself because snappy is wkhtmltopdf wrapper. Then, it is better to develop another wrapper for that or check Packagist. |
@akovalyov ok in fact we've already done such a thing that |
ha... and @akovalyov as Snappy is MIT licence there's no reason that we couldn't add a PrinceXML btw... |
@akovalyov this is really good idea, snappy should be enclosed only with the wk, which are not cover lost of things what alredy done with others processors. It should be next level of evolution for snappy |
I agree about other backends, but I don't agree with PrinceXML. We could add support of |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
What do you think of supporting other pdf generators than wkhtmltopdf ?
I'm thinking about prince xml for example : http://www.princexml.com/
I can manage this if you give me the entry points for a multiple pdf generator backends code modifications.
The text was updated successfully, but these errors were encountered: