<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">All,<div class=""><br class=""></div><div class="">I have updated the documentation build configuration to build a LaTeX-generated PDF in addition to the website every time it refreshes. This can be found at <a href="https://raw.githubusercontent.com/OSGeo/proj.4/gh-pages/proj4.pdf" class="">https://raw.githubusercontent.com/OSGeo/proj.4/gh-pages/proj4.pdf</a> and it is linked on the front page of the HTML website. It would be useful to steal LaTeX builder configuration from the MapServer or PDAL projects, which both have quite nice PDFs being generated from Sphinx in a similar approach. </div><div class=""><br class=""></div><div class="">The Sphinx+LaTeX combo can be a little bit finicky. First, SVG isn't supported, so we need to be feeding PNGs or JPEGs to it. If we switch to SVG for the example renderings, we will have to workflow the conversion to PNG as part of the documentation build process for the LaTeX builder. Second, unicode, math expressions, and heading levels can all cause it to blow up in unexpected ways. The documentation builder should error with a marginally helpful error message that you might have to try/catch for a while to figure out how to make happy. You can build the PDF using Docker yourself. See the build_docs.sh script in the ./travis directory for instructions.</div><div class=""><br class=""></div><div class="">Howard</div></body></html>