Repository navigation
feat: render the PDF and EPUB as well as the site - #22
Merged
Merged
Conversation
_output.yml has always declared all three; build.R rendered bs4_book only because the LaTeX toolchain was unproven on modern R. Smoke-tested first on a compute node with this repo's own assets: krantz.cls plus the full preamble compiles under xelatex, biblatex with refsegment=chapter and the \printbibliography line prepManualRmds() injects compiles, biber is present and cairo is available for dev = "cairo_pdf". Download links stay commented out until the files exist. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
One line:
build.Rrendersoutput_format = "all"instead ofbs4_bookalone._output.ymlhas always declaredbs4_book,pdf_bookandepub_book. Thebuild was restricted to HTML because the LaTeX toolchain was unproven on modern
R, and a missing package would have failed the whole build while the manual was
being brought back to life.
This is the prerequisite for the release scheme: a released manual archives a
PDF, and there is no PDF today.
The toolchain was smoke-tested first
On a compute node, with this repository's own assets rather than a guess at them:
krantz.cls+ fulllatex/preamble.tex(15 packages, incl.Alegreya,sourcecodepro,tabu) under xelatexbiblatexwithrefsegment=chapterand\printbibliography[segment=\therefsegment,heading=none]prepManualRmds()appends to every chapterbibercapabilities("cairo")fordev: "cairo_pdf"So the remaining risk is content-level, not toolchain. CI already has
setup-tinytexand the full module dependency stack, which is the expensive partto reproduce locally, so this is the cheapest place to find what is left.
Opened as a PR deliberately: a
pull_requestbuild renders without deploying, sonothing reaches the site until this is known good.
Expect iteration
EPUB needs no LaTeX. If it fails too, the problem is content rather than TeX,
which makes the first run diagnostic either way. Likely suspects if something
does break: kableExtra tables in a LaTeX context (
_common.Rswitchesknitr.table.formatfor this), figures referenced asmodules/<M>/figures/...,and unicode in author names.
Follow-ups, not in this PR
download: ["pdf", "epub"]in_output.ymlonce the files exist, orthe site advertises links that 404
archiveManualPDF()writesarchive/pdf/LandR-manual-v<version>.pdf, the workflow's bot step commits it,and
publishManualArchive()republishes the set🤖 Generated with Claude Code