This is a list of Frequently Asked Questions about Sphinx. Feel free to suggest new entries!
How do I...
- ... create PDF files without LaTeX?
- You can use rst2pdf version 0.12 or greater which comes with built-in Sphinx integration. See the :ref:`builders` section for details.
- ... get section numbers?
- They are automatic in LaTeX output; for HTML, give a :numbered: option to the :rst:dir:`toctree` directive where you want to start numbering.
- ... customize the look of the built HTML files?
- Use themes, see :doc:`theming`.
- ... add global substitutions or includes?
- Add them in the :confval:`rst_epilog` config value.
- ... display the whole TOC tree in the sidebar?
- Use the :data:`toctree` callable in a custom layout template, probably in the sidebartoc block.
- ... write my own extension?
- See the :ref:`extension tutorial <exttut>`.
- ... convert from my existing docs using MoinMoin markup?
- The easiest way is to convert to xhtml, then convert xhtml to reST. You'll still need to mark up classes and such, but the headings and code examples come through cleanly.
Using Sphinx with...
- There's a third-party extension providing an api role which refers to Epydoc's API docs for a given identifier.
- Michael Jones is developing a reST/Sphinx bridge to doxygen called breathe.
- Glenn Hutchings has written a SCons build script to build Sphinx documentation; it is hosted here: http://bitbucket.org/zondo/sphinx-scons
- Jannis Leidel wrote a setuptools command that automatically uploads Sphinx documentation to the PyPI package documentation area at http://packages.python.org/.
- github pages
- You can use Michael Jones' sphinx-to-github tool to prepare Sphinx HTML output.
- Google Analytics
You can use a custom layout.html template, like this:
The epub builder is currently in an experimental stage. It has only been tested with the Sphinx documentation itself. If you want to create epubs, here are some notes:
Split the text into several files. The longer the individual HTML files are, the longer it takes the ebook reader to render them. In extreme cases, the rendering can take up to one minute.
Try to minimize the markup. This also pays in rendering time.
For some readers you can use embedded or external fonts using the CSS @font-face directive. This is extremely useful for code listings which are often cut at the right margin. The default Courier font (or variant) is quite wide and you can only display up to 60 characters on a line. If you replace it with a narrower font, you can get more characters on a line. You may even use FontForge and create narrow variants of some free font. In my case I get up to 70 characters on a line.
You may have to experiment a little until you get reasonable results.
Test the created epubs. You can use several alternatives. The ones I am aware of are Epubcheck, Calibre, FBreader (although it does not render the CSS), and Bookworm. For bookworm you can download the source from http://code.google.com/p/threepress/ and run your own local server.
Large floating divs are not displayed properly. If they cover more than one page, the div is only shown on the first page. In that case you can copy the :file:`epub.css` from the sphinx/themes/epub/static/ directory to your local _static/ directory and remove the float settings.
Files that are inserted outside of the toctree directive must be manually included. This sometimes applies to appendixes, e.g. the glossary or the indices. You can add them with the :confval:`epub_post_files` option.