PDF generation #22
Open
PDF generation #22
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
Open
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.
There were two problems preventing PDF generation:
#:style "strike"was included, instead of the TeX equivalentトランスフォーマ. LaTeX can be set-up in principle to handle these characters, but as a quick solution, I simply added asedcommand to themakefilewhich removes this word and saves that aspdf-index.rkt. The sentence is still readable, so not much is lost.I also included a few Makefile idiosyncrasies, like marking "virtual" targets as such using the very-well-named (ahem)
.PHONYtarget. I also made the dependencies for a few targets a bit more precise.The PDF file builds fine on my Linux system with
texlive-fullinstalled.I'll send a second pull request for the gh-pages branch which includes the generated PDF.