Open
Conversation
The `preprint` target outputs a very plain file, missing any
journal-specific styling. It's nice when the arxiv version of a paper
has similar formatting to the published version. There have been
requests and discussions concerning a smooth way to do this.
Some issues were raised, the biggest one being possible confusion about
the publication status of a preprint.
Configure pandoc to output a LaTeX file somewhat closer to that which
would generate the official PDFs. In order to distinguish it from a
published article, this style:
- Removes the journal logo from the header.
- Replaces the DOI and review details in the sidebar with "Preprint:
Prepared for submission to $journal.title$". This is borrowed from
JCAP's LaTeX style.
- Removes the self-citation in the footer.
There are other minor differences in fonts and PDF tags because
arxiv.org only supports `pdflatex`, not `lualatex`:
- remove `\pdfvariable omitcidset=*
- remove `\setmonofont{Hack}`
- remove `\usepackage{fontsetup}`
Contributor
|
I really like this idea since it means that the regular publication and preprint can be managed in the same template I would go even further and say that this should replace the preprint template completely |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
preprinttarget outputs a very plain file without any styling. It is nice when the preprint version of a paper has similar formatting to the published version.There have been requests and discussions concerning a smooth way to do this:
Some issues were raised, the biggest one being possible confusion about the publication status of a preprint. (See for example openjournals/joss#132 (comment) and openjournals/joss#132 (comment).)
In this PR I have configured pandoc to output a LaTeX file somewhat closer to that which would generate the official PDFs. In order to distinguish it from a published article, this style:
Preprint: Prepared for submission to $journal.title$.This is borrowed from JCAP's LaTeX style.
There are other minor differences in fonts and PDF tags because arxiv.org only supports
pdflatex, notlualatex:\pdfvariable omitcidset=*\setmonofont{Hack}\usepackage{fontsetup}Possible issues/room for improvement:
main(possibly due to Cannot apk add - temporary error alpinelinux/docker-alpine#59).Here is the PDF preview generated by arxiv:

This PR may not be merged here, but I figured I would put the changes out there in case they are useful to someone.