You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The LaTeX version of this template supports these options:
theme_color (choice) - Choose between `blue` and `red` color scheme. Defaults to `blue`.
line_spacing (choice) - Use the onehalfspacing or doublespacing option for 1.5/2.0 line spacing.
venue_footer (choice) - Show a label of the venue, like "arXiv" in the footer of each page.
number_sections (boolean) - Number sections of the article
line_numbers (boolean) - Turn line numbers on in the PDF
Ideally we'd support the same and with the same syntax, so that it's as easy as possible for users to switch between lapreprint and lapreprint-typst. I think the typst workflow is the future, but today there's still a lot of edge cases where things break. Supporting the same overall config syntax will make it easier for users to test the typst version and gradually transition (helping us find and fix the remaining bugs).
For reference, as of Jan 16, 2025, the only options supported by lapreprint-typst are:
Options:
logo (file) - An image path that is shown in the top right of the page
kind (string) - The "kind" of the content, e.g. "Original Research" - shown as the title of the margin content on the first page
The text was updated successfully, but these errors were encountered:
The LaTeX version of this template supports these options:
Ideally we'd support the same and with the same syntax, so that it's as easy as possible for users to switch between
lapreprint
andlapreprint-typst
. I think the typst workflow is the future, but today there's still a lot of edge cases where things break. Supporting the same overall config syntax will make it easier for users to test the typst version and gradually transition (helping us find and fix the remaining bugs).For reference, as of Jan 16, 2025, the only options supported by
lapreprint-typst
are:The text was updated successfully, but these errors were encountered: