Experimenting with rendering the manual to PDF using rinohtype #270
Conversation
This file contains 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
…he Docs theme colour scheme.
…n the Read the Docs theme <#166 (comment)>
…ick up corrections to the manual.
… in response to review <#166 (comment)>.
rptb1
changed the title
|
We don't really need a pdf manual. It would be nice to have |
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 rinohtype package is mentioned in the Sphinx FAQ as a way of rendering docs into PDF without using LaTeX. This is just a quick attempt at doing that. It doesn't work (yet). See brechtm/rinohtype#421 .