Skip to content
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

Closed
shouze opened this issue Jul 30, 2012 · 7 comments
Closed

Other backends than wkhtmltopdf #37

shouze opened this issue Jul 30, 2012 · 7 comments
Projects
Milestone

Comments

@shouze
Copy link

shouze commented Jul 30, 2012

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.

@pilot
Copy link
Contributor

pilot commented Sep 19, 2014

@shouze this is good idea, what kind of help you need to make PR with support of prnicexml?

@pilot pilot added the RFC label Sep 19, 2014
@akovalyov
Copy link
Contributor

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 akovalyov removed the RFC label Aug 4, 2015
@shouze
Copy link
Author

shouze commented Aug 5, 2015

@akovalyov ok in fact we've already done such a thing that extends Pdf implements GeneratorInterface from Snappy since about 3 years from now and it just work but will never be open sourced even if some guys like @pilot is 👍 and you are 👎 ;)

@shouze
Copy link
Author

shouze commented Aug 5, 2015

ha... and @akovalyov as Snappy is MIT licence there's no reason that we couldn't add a PrinceXML btw...

@pilot pilot reopened this Aug 5, 2015
@pilot
Copy link
Contributor

pilot commented Aug 5, 2015

@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

@akovalyov
Copy link
Contributor

I agree about other backends, but I don't agree with PrinceXML. We could add support of weasyprint i.e. But I am -1 for PrinceXML since it is close-sourced. And again, there are already wrappers for this tool.
What I am completely +1 for is to check other good pdf generation processors.
And also in this case we should refactor our API first, I am not sure it is rather flexible ATM.

@akerouanton akerouanton added this to the 2.x milestone Oct 1, 2017
@akerouanton akerouanton added this to Backlog in Snappy Oct 1, 2017
@akerouanton akerouanton moved this from Backlog to TODO 2.x in Snappy Oct 21, 2017
@stale
Copy link

stale bot commented Nov 12, 2019

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.

@stale stale bot added the stale label Nov 12, 2019
@stale stale bot closed this as completed Nov 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Snappy
TODO 2.x
Development

No branches or pull requests

4 participants