Skip to content

docs: say which richdoc-to-PDF paths already existed - #8

Merged
tannevaled merged 1 commit into
mainfrom
fix/say-which-paths-exist
Nov 5, 2026
Merged

tannevaled merged 1 commit into
mainfrom
fix/say-which-paths-exist

Conversation

@tannevaled

Copy link
Copy Markdown
Contributor

The doc comment claimed to be "the direction that did not exist". It was not.

go-richdoc/rst/pdf     richdoc → reST → docutils → LaTeX → go-tex/engine
go-richdoc/latex/pdf   richdoc → LaTeX → go-tex/engine

⛔ The claim was wrong because the search was. I looked for functions named ToPDF; these are named Write. A capability is not found by guessing what its function is called — the fifth time in one day this inventory was wrong for consulting the wrong thing, and the first time it put a false claim in shipped documentation.

This one is still worth having, and the comment now says when to reach for which: this for a pure-Go, CGO-free page that also builds for GOOS=js and keeps emphasis, links and tables; rst/pdf or latex/pdf when TeX's typesetting is the point and a six-megabyte engine — and today's loss of emphasis to go-tex/engine#590 — are acceptable.

🤖 Generated with Claude Code

The doc comment claimed to be "the direction that did not exist". It
was not: go-richdoc/rst/pdf and go-richdoc/latex/pdf were already there,
both taking a richdoc to a typeset PDF through a real TeX compile.

The claim was wrong because the SEARCH was. I looked for functions named
ToPDF; these are named Write. A capability is not found by guessing what
its function is called -- the fifth time in one day that this inventory
was wrong for consulting the wrong thing.

What the comment says now is when to reach for which: this one for a
pure-Go, CGO-free page that also builds for GOOS=js and keeps emphasis,
links and tables; rst/pdf or latex/pdf when TeX typesetting is the point
and six megabytes of engine and the loss of emphasis to
go-tex/engine#590 are acceptable.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@tannevaled
tannevaled merged commit 5e69ced into main Nov 5, 2026
1 check passed
@tannevaled
tannevaled deleted the fix/say-which-paths-exist branch November 5, 2026 21:28
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

Successfully merging this pull request may close these issues.

1 participant