-
-
Notifications
You must be signed in to change notification settings - Fork 974
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
Wrong post processing pipeline for pdf_document() conversion #2282
Comments
I think this makes the logic very clear. I had an idea to apply |
Thanks for the feedback !
Which format are you thinking off ? I am curious about post processing of PDF files (instead of tex file before PDF conversion) |
Not on a public repository, but I used to apply post processing on PDF to outline fonts to ensure it prints safely by a command like
|
Thanks for sharing. Good to know this could be useful. Probably for PDF conversion we need to consider current pre_processor / post_processor as hooks for Pandoc conversion ( Seems like a piece is missing here. |
#2320 fixed the issue with the warnings due to wrong post processing. I'll leave this issue open to deal in a later version to fix the way post processing is happening for PDF. |
Found while working #2264,
A recent fix introduced a post processor in the
pdf_document()
output. 5a3e941This creates some issues I believe but it does not show in CI oddly.
output_format$post_processor()
is supposed to run on the output of the Pandoc conversion. While looking into the other issue #2264 (comment), it happens that the conversion step (before post processing) will generate a PDF file usinglatexmk()
. when output file is pdf for example.rmarkdown/R/render.R
Lines 974 to 981 in 0af6b35
In that case the
post_processor()
will try to post process the PDF filermarkdown/R/pdf_document.R
Lines 191 to 200 in 5a3e941
This does not work obviously. Reprex:
The post processing step should happen before
latexmk()
after Pandoc conversion from.md
to.tex
. I don't think it is working right now.Or maybe the
latexmk()
rendering should happen in thepdf_document()
post processing 🤔 But that would mean for user creating custom output that they need to usepdf_document()
as base format or do the conversion themself. Maybe room for apdf_document_base()
format that does essential processing ?I get all those warning message when running tests locally, I am not sure why we don't see them in CI. 🤔
The text was updated successfully, but these errors were encountered: