a63e03e301
It was too hard to tell what was embedded sample code and what was true cell input/output. |
||
---|---|---|
.. | ||
__init__.py | ||
6x9build_book.bat | ||
book6x9.tplx | ||
book_old.tplx | ||
book_to_pdf.bat | ||
book.tplx | ||
build_book | ||
build_book6x9.bat | ||
build_book_html.sh | ||
build_book.bat | ||
build_html_ipynb.py | ||
clean_book | ||
clean_book.bat | ||
formatting.py | ||
html_book | ||
html_build_book | ||
html_build_book.bat | ||
index.ipynb | ||
make_chapter.bat | ||
merge_book.py | ||
nbmerge.py | ||
readme.txt | ||
report_old.tplx | ||
rm_notebook.py | ||
run_notebooks.bat | ||
short_build_book | ||
short_merge_book.py | ||
to_pdf.py | ||
update_pdf.bat | ||
update_pdf.sh |
This directory contains code to convert the book into the PDF file. The normal build process is to cd into this directory, and run build_book from the command line. If the build is successful (no errors printed), then run clean_book from the command line. clean_book is not run automatically because if there is an error you probably need to look at the intermediate output to debug the issue. I build the PDF my merging all of the notebooks into one huge one. I strip out the initial cells for the book formatting and table of contents, and do a few other things so it renders well in PDF. I used to do this in Unix, but switched to Windows. The Unix scripts have not been kept up to date. There is also some experimental code to convert to html. The files with short in the name combine only a couple of notebooks together. I use this to test the production without having to wait the relatively long time required to produce the entire book. Mostly this is for testing the scripts. No one but me should need to run this stuff, but if you fork the project and want to generate a PDF, this is how you do it.