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

Document how this is kept in sync with Pandoc Template #4

Open
mfhepp opened this issue Jul 23, 2022 · 1 comment
Open

Document how this is kept in sync with Pandoc Template #4

mfhepp opened this issue Jul 23, 2022 · 1 comment

Comments

@mfhepp
Copy link

mfhepp commented Jul 23, 2022

It would be good to explain how you are keeping this the partials and the entire template in sync with the official Pandoc template.

This would make it easier for contributors of journal styles to maintain their partials or their template.

Here is a link to the official LaTeX template in Pandoc.

@cderv
Copy link
Collaborator

cderv commented Jul 25, 2022

The Pandoc LaTeX template will be kept updated with the Pandoc version bunlded within Quarto. The partials system for the template file is there so that a format maintainer won't have to keep the full template up to date. The partial will keep being inserted in the right place.

This template contains as example the default template / partials file as a copy of the files used in quarto, and this will be keep updated with any quarto update on those default. A format developper using this repo to start its format extension would only modify the templates that needs to be tweaked and delete the other one as the default are fine.

So usually, a format author will only provide partials for the template and won't have to maintain anything on new Pandoc version. However, if a developer replace a whole pandoc template, then indeed a sync with new pandoc version will be needed.

Are you suggesting the later part should be documented ?

Does it clarify ? Or am I missing something here ?

Happy to take any suggestion to improve this repo or the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants