-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature suggest: best practices with .pdf export #198
Comments
Sphinx can export to LaTeX and subsequently to PDF, most of the styling features, like bootstrap CSS, however won't be available there, but we are not using many fancy directives in the learn section. Also, I believe it would export the whole page as one PDF by default, so we would have to exclude everything but the learn section if we are using the PDF backend (similar in idea in #173 to append to the exclude list based on the builder). |
I just recognize pandoc and (g)roff might be used to generate .pdf out of .md (an example). The syntax highlighting ( #!/usr/bin/bash
for file in *.md;
do
base=$(basename "$file");
output=${base//\.md/};
echo 'work on file' "$file";
pandoc -Tpdf -t ms "$file" -o "$output".pdf;
done To build a .pdf as e.g., the .zip below about the .md of section «best_practices». True, there however are at least two points already seen which would require improvement:
|
Though the content likely is equally available via GitHub, I would like to suggest that the compilation of «Fortran Best Practices» equally becomes available as export to .pdf. This is an option seen e.g., with «normal» entries in the Wikipedia, as well as for their wikibooks:
(screenphoto of https://en.wikibooks.org/wiki/Fortran/Printable_version)
The example of wikipedia demonstrates that the already present discern between the documentation per sé and snippets of code -- including syntax highlighting -- may be preserved.
The text was updated successfully, but these errors were encountered: