WeasyPrint for PDF generation? #3906
Comments
|
I am open to supporting it.
One possibility would be to have a general
…--pdf-engine
or
--pdf-via
option which could be used for pdflatex, xelatex, context,
html2pdf, etc. We could make --latex-engine a deprecated
synonym of this.
|
|
There is also PrinceXML which offers very professional publishing output (and free for non-commercial use), so having a general |
|
+++ Ian [Sep 09 17 23:59 ]:
There is also [1]PrinceXML which offers very professional publishing
output (and free for non-commercial use), so having a general --pdf-via
that could accommodate this in addition to the other tools would be
nice. I'm not sure how best to configure the general command-line for
each tool, it is currently hard-coded right?
There's a --latex-engine-opt flag, but otherwise, yes, it's
hard coded. Moreover, each kind of engine has to be
specially handled (e.g. they have different needs for
where they expect to find image files, and so on).
But it should be possible to add support for both these
tools.
|
mb21
added a commit
to mb21/pandoc
that referenced
this issue
Sep 10, 2017
and add support for `weasyprint` and `prince`, in addition to `wkhtmltopdf` closes jgm#3906
mb21
added a commit
to mb21/pandoc
that referenced
this issue
Sep 10, 2017
and add support for `weasyprint` and `prince`, in addition to `wkhtmltopdf` closes jgm#3906
mb21
added a commit
to mb21/pandoc
that referenced
this issue
Sep 11, 2017
and add support for `weasyprint` and `prince`, in addition to `wkhtmltopdf` closes jgm#3906
jgm
pushed a commit
that referenced
this issue
Sep 12, 2017
* Rename --latex-engine to --pdf-engine * In `Text.Pandoc.Options.WriterOptions`, rename `writerLaTeXEngine` to `writerPdfEngine` and `writerLaTeXArgs` to `writerPdfArgs`. * Add support for `weasyprint` and `prince`, in addition to `wkhtmltopdf`, for PDF generation via HTML (closes #3906). * `Text.Pandoc.PDF.html2pdf`: use stdin instead of intermediate HTML file
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Should we support WeasyPrint in addition to
wkhtmltopdf?This would require a
--html-engineoption. More correctly, it would have to be called--html-to-pdf-engine, but that's quite long and--latex-engineset some kind of precedent. Other options include--html2pdf-engineand--html-pdf-engine.The text was updated successfully, but these errors were encountered: