documentation update

git-svn-id: http://svn.code.sf.net/p/docutils/code/trunk@5458 929543f6-e4f2-0310-98a6-ba3bd3dd1d04

6 files changed, 227 insertions, 165 deletions

diff --git a/sandbox/code-block-directive/docs/syntax-highlight.txt b/sandbox/code-block-directive/docs/syntax-highlight.txt
index d4fe431fa..7aac07bab 100644
--- a/sandbox/code-block-directive/docs/syntax-highlight.txt
+++ b/sandbox/code-block-directive/docs/syntax-highlight.txt
@@ -1,19 +1,19 @@
 .. -*- rst-mode -*-
 
 Syntax Highlight
-----------------
+================
 
 .. contents::
 .. sectnum::
 
-Syntax highlighting significantly enhances the readability of code.
-So it is almost a must for pretty-printing a literate program.
+Syntax highlighting significantly enhances the readability of code. However,
+in the current version, docutils does not highlight literal blocks. 
 
-PyLit_ uses docutils_ as pretty-printing back end. However, in the current
-version, docutils does not highlight literal blocks. This may change in the
-future, as in a mail on
-`Questions about writing programming manuals and scientific documents`__,
-docutils main developer David Goodger wrote:
+This sandbox project aims to add syntax highlight of code blocks to the
+capabilities of docutils. To find its way into the docutils core, it should
+meet the requirements laid out in a mail on `Questions about writing
+programming manuals and scientific documents`__, by docutils main developer
+David Goodger:
 
    I'd be happy to include Python source colouring support, and other
    languages would be welcome too. A multi-language solution would be
@@ -25,38 +25,41 @@ docutils main developer David Goodger wrote:
 __ http://sourceforge.net/mailarchive/message.php?msg_id=12921194
 
 
-Existing highlighting additions to docutils
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+State of the art
+----------------
 
 There are already docutils extensions providing syntax colouring, e.g:
 
-* SilverCity_ is a C++ library and Python extension that can provide lexical
-  analysis for over 20 different programming languages. A recipe__
-  for a "code-block" directive provides syntax highlight by SilverCity.
+SilverCity_, 
+  a C++ library and Python extension that can provide lexical
+  analysis for over 20 different programming languages. A recipe__ for a
+  "code-block" directive provides syntax highlight by SilverCity.
   
 __ http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/252170
 
-* The `listings`_ LaTeX package provides highly customisable and advanced
+`listings`_,
+  a LaTeX package providing highly customisable and advanced
   syntax highlight, though only for LaTeX (and LaTeX derived PS|PDF). 
-  A patch__ mailed by Gael Varoquaux uses the listings package for a
-  "code-block" directive with syntax highlight.
+  See also section `listings.sty`_ and a proposal__ Gael Varoquaux.
   
 __ http://article.gmane.org/gmane.text.docutils.devel/3914
 
-* Trac_ has `reStructuredText support`__ and offers syntax highlighting with
+Trac_ 
+  has `reStructuredText support`__ and offers syntax highlighting with
   a "code-block" directive using GNU Enscript_, SilverCity_, or Pygments_.
   
 __ http://trac.edgewall.org/wiki/WikiRestructuredText
 
-* The rest2web_ site builder provides the `colorize`__ macro (using the
+rest2web_,
+  the "site builder" provides the `colorize`__ macro (using the
   `Moin-Moin Python colorizer`_) 
 
 __ http://www.voidspace.org.uk/python/rest2web/macros.html#colorize
 
-* `Pygments`_ a generic syntax highlighter for general use. 
+Pygments_ 
+  is a generic syntax highlighter written completely in Python. 
 
-  * Written completely in Python, usable as a command-line tool and as a
-    Python package.
+  * Usable as a command-line tool and as a Python package.
   * A wide range of common `languages and markup formats`_ is supported.
   * Additionally, OpenOffice's ``*.odt`` is supported by the odtwriter_.
   * The layout is configurable by style sheets.
@@ -68,114 +71,40 @@ __ http://www.voidspace.org.uk/python/rest2web/macros.html#colorize
   * The web site provides a recipe for `using Pygments in ReST documents`_.
     It is used in the `Pygments enhanced docutils front-ends`_ below.
 
-* The experimental Odtwriter_ for Docutils OpenOffice export supports syntax
-  colours using Pygments.
+Odtwriter_, experimental writer for Docutils OpenOffice export supports syntax
+  colours using Pygments. (See section `Odtwriter syntax`_.)
 
 Pygments_ seems to be the most promising docutils highlighter. For printed
 output, the listings_ package has its advantages too.
 
 
 Pygments enhanced docutils front-ends
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Here comes a working example for syntax highlighting in HTML and LaTeX
-output with pygments_.
+-------------------------------------
 
-The example code in "`Using Pygments in ReST documents`_" defines a new
-"sourcecode" directive. The directive takes one argument `language` and uses
-the `Pygments`_ source highlighter to parse and render its content as a
-colourful source code block. 
-
-Combining the pygments_ example code with the standard docutils_ front-ends,
-results in front-end scripts generating output documents with syntax colour.
-For consistency with the majority of existing add-ons, the directive is
-renamed to "code-block".
-
-`rst2html-pygments`_ 
-  enhances the standard docutils ``rst2html`` front-end to
-  generate a HTML rendering with syntax highlight. 
-  
-`rst2latex-pygments`_ 
-  enhances docutils' ``rst2latex`` to generate LaTeX with syntax highlight.
+Syntax highlight can be achieved by `front-end scripts`_ combining docutils and
+pygments.
 
 Advantages:
   + Easy implementation with no changes to the stock docutils_. 
   + Separation of code blocks and ordinary literal blocks.
 
 Disadvantages:
-  - "code-block" content is formatted by `pygments`_ and inserted in the
-    document tree as a "raw" node making the approach writer-dependant.
-  - documents are incompatible with the standard docutils because of the
-    locally defined directive.
-  - more "invasive" markup distracting from content
-  - no "minimal" code block marker -- three additional lines per code block
-
-The later disadvantages become an issue in literate programming where a code
-block is the most used block markup (see the proposal for a `configurable
-literal block directive`_ below).
-
-To support the ``.. code-block::`` directive, the PyLit converter would need
-a configurable "code block marker" instead of the hard coded ``::``
-presently in use. (See also the `code-block directive`__ section in
-pylit.py.)
-
-__ ../examples/pylit.py.html#code-block-directive
-
-
-Example
-"""""""
-
-Python script:
-  :text source: `for-else-test.py.txt`_
-  :HTML:   `for-else-test.py.htm`_
-  :LaTeX:  `for-else-test.py.tex`_
-  :PDF:    `for-else-test.py.pdf`_
-
-Stylesheets:
-  :CSS stylesheet:  `pygments-default.css`_
-  :LaTeX style:     `pygments-default.sty`_
-
-
-
-Proposal for a code-block directive in docutils
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
+  1. "code-block" content is formatted by `pygments`_ and inserted in the
+     document tree as a "raw" node making the approach writer-dependant.
+  2. documents are incompatible with the standard docutils because of the
+     locally defined directive.
+  3. more "invasive" markup distracting from content
+     (no "minimal" code block marker -- three additional lines per code block)
 
-In a `post to the docutils users list`__, David Goodger wrote (after an all
-too long discussion):
 
-  Here are my pronouncements:
-  
-  * If reST is to grow a code-block (or sourcecode or syntax-highlight
-    or whatever) directive, it must be independent of the output format.
-  
-  * The result will be stored in a literal_block node in the document
-    tree.  There will be no new element.
-  
-  * There will be no "unparsed" code-block.  It would make no sense.
-  
-  * There will be no special pass-through support for LaTeX to do its
-    own syntax highlighting.
-  
-__ http://article.gmane.org/gmane.text.docutils.user/3923
-
-On  7.06.07, David Goodger wrote:
-
- On 6/7/07, G. Milde suggested:
-
- 3. Docutils will support optional features that are only available if
-    a recommended package or module is installed.
-
-    -> code-block directive content would be
+Point 1 and 2 lead to the `code-block directive proposal`_. Point 3
+becomes an issue in literate programming where a code block is the most used
+block markup. It is addressed in the proposal for a `configurable literal
+block directive`_).
 
-      - rendered with syntax highlight if ``import pygments`` works,
 
-      - output as "ordinary" literal-block (preserve space, mono-coloured
-        fixed-width font) if ``import pygments`` fails.
-
- +1 on number 3.
- 
-Implemented 2007-06-08.
+`code-block` directive proposal
+-------------------------------
 
 
 Reading
@@ -185,22 +114,21 @@ Felix Wiemann provided a `proof of concept`_ script that utilizes the
 pygments_ parser to parse a source code string and store the result in
 the document tree.
 
-This concept is used in `pygments_code_block_directive.py`_, (HTML rendering
-of the literate code: `pygments_code_block_directive`_), to define
-and register a "code-block" directive.
+This concept is used in a `pygments_code_block_directive`_ (Source:
+`pygments_code_block_directive.py`_), to define and register a "code-block"
+directive.
 
-* The `DocutilsInterface` class uses pygments_ to parse the content of the
+* The ``DocutilsInterface`` class uses pygments to parse the content of the
   directive and classify the tokens using short CSS class names identical to
   pygments HTML output. If pygments is not available, the unparsed code is
   returned.
 
-* The `code_block_directive` function inserts the tokens in a "rich"
+* The ``code_block_directive`` function inserts the tokens in a "rich"
   <literal_block> element with "classified" <inline> nodes.
 
 The XML rendering of the small example file `myfunction.py.txt`_ looks like
 `myfunction.py.xml`_.
 
-
 Writing
 """""""
 
@@ -216,7 +144,7 @@ HTML
   * Styling is done with the adapted CSS style sheet `pygments-default.css`_
     based on docutils' default stylesheet and the output of 
     ``pygmentize -S default -f html``.
-  * The result looks like `myfunction.py.html`_.
+  * The result looks like `myfunction.py.htm`_.
   
   The "s5" and "pep" writers are not tested yet.
   
@@ -247,7 +175,7 @@ OpenOffice
 TODO
 """"
 
-* fix the "latex" writer.
+* fix the "latex" writers.
 
 * think about an interface for pygments' options (like "encoding" or
   "linenumbers").
@@ -257,31 +185,30 @@ TODO
 .. _proof of concept:
      http://article.gmane.org/gmane.text.docutils.user/3689
 .. _pygments_code_block_directive.py: ../pygments_code_block_directive.py
-.. _pygments_code_block_directive: pygments_code_block_directive-bunt.py.html
+.. _pygments_code_block_directive: pygments_code_block_directive-bunt.py.htm
 .. _pygments_docutils_interface.py: pygments_docutils_interface.py
 .. _myfunction.py.txt: myfunction.py.txt
 .. _myfunction.py.xml: myfunction.py.xml
+.. _myfunction.py.htm: myfunction.py.htm
 .. _myfunction.py.pseudoxml: myfunction.py.pseudoxml
-.. _myfunction.py.html: myfunction.py.html
 .. _myfunction.py.tex: myfunction.py.tex
 .. _myfunction.py.newlatex2e.tex: myfunction.py.newlatex2e.tex
 .. _myfunction.py.newlatex2e.pdf: myfunction.py.newlatex2e.pdf
-.. _rst2html-highlight: ../tools/rst2html-highlight
+.. _rst2html-highlight: ../rst2html-highlight
 .. _pygments-long.css: ../data/pygments-long.css
 
 
 
-
 Configurable literal block directive
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+------------------------------------
 
 Goal
 """"
 
 A clean and simple syntax for highlighted code blocks -- preserving the
 space saving feature of the "minimised" literal block marker (``::`` at the
-end of a text paragraph). This is especially desirable in literate programs
-with many code blocks.
+end of a text paragraph). This is especially desirable in documents with 
+many code blocks like tutorials or literate programs.
 
 Inline analogon
 """""""""""""""
@@ -293,12 +220,18 @@ use::
 
   .. default-role:: subscript
   
-  The triple point of H`2`O is at 0°C.
+  The triple point of H\ `2`\O is at 0°C.
+
+.. default-role:: subscript
+
+to produce 
+  
+  The triple point of H\ `2`\O is at 0°C.
 
 This customisation is currently not possible for block markup.
 
-Proposal: make the default "literal block" role configurable.
-"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+Proposal
+""""""""
 
 * Define a new "literal" directive for an ordinary literal block.
   This would insert the block content into the document tree as
@@ -313,8 +246,8 @@ Proposal: make the default "literal block" role configurable.
 * From a syntax view, this would be analog to the behaviour of the odtwriter_.
   (I am not sure about the representation in the document tree, though.)
 
-Motivation
-''''''''''
+Motive
+""""""
 
 Analogue to customising the default role of "interpreted text" with the
 "default-role" directive, the concise ``::`` literal-block markup could be
@@ -345,8 +278,8 @@ Example (using the upcoming "settings" directive)::
 In the same line, a "default-block-quote" setting or directive could be
 considered to configure the role of a block quote.
 
-Odtwriter
-~~~~~~~~~
+Odtwriter syntax
+----------------
 
 Dave Kuhlman's odtwriter_ extension can add syntax highlighting
 to ordinary literal blocks.
@@ -394,49 +327,48 @@ I.e. the odtwriter implements a `configurable literal block directive`_
 (but with a slightly different syntax than my proposal below).
 
 
-Syntax highlight with the ``listings.sty`` LaTeX package
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+``listings.sty``
+----------------
 
 Using the listings_ LaTeX package for syntax highlight is currently not
 possible with the standard latex writer output. 
 
 Support for the use of listings_ with docutils is an issue that must be
-settled separate from the `proposal for a code-block directive in
-docutils`_. It would need 
+settled separate from the `code-block directive proposal`_. It needs
 
 * a new, specialized docutils latex writer, or
 * a new option (and behaviour) to the existing latex writer.
 
+Ideas and experimental code is in the Sandbox under `latex-variants`_.
+
 
-.. External links
+.. External links 
 .. _pylit: http://pylit.berlios.de
-.. _docutils: http://docutils.sourceforge.net/ 
+.. _docutils: http://docutils.sourceforge.net/
 .. _rest2web: http://www.voidspace.org.uk/python/rest2web/
 .. _Enscript: http://www.gnu.org/software/enscript/enscript.html
-.. _SilverCity: http://silvercity.sourceforge.net/ 
-.. _Trac: http://trac.edgewall.org/ 
-.. _Moin-Moin Python colorizer:
-    http://www.standards-schmandards.com/2005/fangs-093/ 
-.. _odtwriter: http://www.rexx.com/~dkuhlman/odtwriter.html 
-.. _pygments: http://pygments.org/ 
-.. _listings: http://www.ctan.org/tex-archive/help/Catalogue/entries/listings.html
-.. _fancyvrb: http://www.ctan.org/tex-archive/help/Catalogue/entries/fancyvrb.html
+.. _SilverCity: http://silvercity.sourceforge.net/
+.. _Trac: http://trac.edgewall.org/
+.. _Moin-Moin Python colorizer: 
+    http://www.standards-schmandards.com/2005/fangs-093/
+.. _odtwriter: http://www.rexx.com/~dkuhlman/odtwriter.html
+.. _pygments: http://pygments.org/
+.. _listings: 
+    http://www.ctan.org/tex-archive/help/Catalogue/entries/listings.html
+.. _fancyvrb: 
+    http://www.ctan.org/tex-archive/help/Catalogue/entries/fancyvrb.html
 .. _alltt: http://www.ctan.org/tex-archive/help/Catalogue/entries/alltt.html
-.. _moreverb: http://www.ctan.org/tex-archive/help/Catalogue/entries/moreverb.html
-.. _verbatim: http://www.ctan.org/tex-archive/help/Catalogue/entries/verbatim.html
-.. _languages and markup formats: http://pygments.org/languages 
+.. _moreverb:
+    http://www.ctan.org/tex-archive/help/Catalogue/entries/moreverb.html
+.. _verbatim: 
+    http://www.ctan.org/tex-archive/help/Catalogue/entries/verbatim.html
+.. _languages and markup formats: http://pygments.org/languages
 .. _Using Pygments in ReST documents: http://pygments.org/docs/rstdirective/
-.. _`Docutils Document Tree`: 
-       http://docutils.sf.net/docs/ref/doctree.html#classes
+.. _Docutils Document Tree: 
+    http://docutils.sf.net/docs/ref/doctree.html#classes
+.. _latex-variants: http://docutils.sourceforge.net/sandbox/latex-variants/
 
 .. Internal links
-.. _rst2html-pygments: ../tools/rst2html-pygments
-.. _rst2latex-pygments: ../tools/rst2latex-pygments
-.. _for-else-test:
-.. _for-else-test.py.htm: for-else-test.py.htm
-.. _for-else-test.py.txt: for-else-test.py.txt
-.. _for-else-test.py.tex: for-else-test.py.tex
-.. _for-else-test.py.pdf: for-else-test.py.pdf
+.. _front-end scripts: ../tools/pygments-enhanced-front-ends
 .. _pygments-default.css: ../data/pygments-default.css
-.. _pygments-default.sty: ../data/pygments-default.sty
 
diff --git a/sandbox/code-block-directive/rst2html-highlight b/sandbox/code-block-directive/rst2html-highlight
index 737a8c802..0203c857e 100755
--- a/sandbox/code-block-directive/rst2html-highlight
+++ b/sandbox/code-block-directive/rst2html-highlight
@@ -1,11 +1,18 @@
 #!/usr/bin/python
 
+# rst2html-highlight
+# ==================
+# 
+# Docutils front-end with syntax highlight.
+#   
 # :Author: David Goodger, a Pygments author|contributor, Guenter Milde
 # :Date: $Date: $
 # :Copyright: This module has been placed in the public domain.
-
+# 
 # This is a merge of the docutils_ `rst2html` front end with an extension
 # suggestion taken from the pygments_ documentation.
+# 
+# ::
 
 """
 A front end to docutils, producing HTML with syntax colouring using pygments
@@ -15,6 +22,10 @@ Generates (X)HTML documents from standalone reStructuredText sources. Uses
 Needs an adapted stylesheet  
 """
 
+# Requirements
+# ------------
+# ::  
+
 try:
     import locale
     locale.setlocale(locale.LC_ALL, '')
@@ -23,14 +34,18 @@ except:
 
 from docutils.core import publish_cmdline, default_description
 
-# Define and register a new directive `code-block` that uses the `pygments`_
-# source highlighter to render code in color. 
+# The `pygments_code_block_directive`_ module defines and registers a new
+# directive `code-block` that uses the `pygments`_ source highlighter to
+# render code in color::
+
 import pygments_code_block_directive
 
 # Call the docutils publisher to render the input as html::
+
 description = __doc__ + default_description
 publish_cmdline(writer_name='html', description=description)
 
-# .. _doctutile: http://docutils.sf.net/
+# .. _docutils: http://docutils.sf.net/
+# .. _pygments_code_block_directive.py: pygments_code_block_directive.py
 # .. _pygments: http://pygments.org/
 # .. _Using Pygments in ReST documents: http://pygments.org/docs/rstdirective/
diff --git a/sandbox/code-block-directive/rst2html-highlight.txt b/sandbox/code-block-directive/rst2html-highlight.txt
new file mode 100644
index 000000000..2640765c8
--- /dev/null
+++ b/sandbox/code-block-directive/rst2html-highlight.txt
@@ -0,0 +1,52 @@
+..  #!/usr/bin/python
+
+rst2html-highlight
+==================
+
+Docutils front-end with syntax highlight.
+  
+:Author: David Goodger, a Pygments author|contributor, Guenter Milde
+:Date: $Date$
+:Copyright: This module has been placed in the public domain.
+
+This is a merge of the docutils_ `rst2html` front end with an extension
+suggestion taken from the pygments_ documentation.
+
+::
+
+  """
+  A front end to docutils, producing HTML with syntax colouring using pygments
+  
+  Generates (X)HTML documents from standalone reStructuredText sources. Uses
+  `pygments` to parse and mark up the content of ``.. code-block::` directives.
+  Needs an adapted stylesheet  
+  """
+
+Requirements
+------------
+
+::  
+
+  try:
+      import locale
+      locale.setlocale(locale.LC_ALL, '')
+  except:
+      pass
+  
+  from docutils.core import publish_cmdline, default_description
+  
+The `pygments_code_block_directive`_ module defines and registers a new
+directive `code-block` that uses the `pygments`_ source highlighter to
+render code in color::
+
+  import pygments_code_block_directive
+  
+Call the docutils publisher to render the input as html::
+
+  description = __doc__ + default_description
+  publish_cmdline(writer_name='html', description=description)
+  
+.. _docutils: http://docutils.sf.net/
+.. _pygments_code_block_directive.py: pygments_code_block_directive.py
+.. _pygments: http://pygments.org/
+.. _Using Pygments in ReST documents: http://pygments.org/docs/rstdirective/
diff --git a/sandbox/code-block-directive/tools/pygments-enhanced-front-ends/README.txt b/sandbox/code-block-directive/tools/pygments-enhanced-front-ends/README.txt
new file mode 100644
index 000000000..5f5e77557
--- /dev/null
+++ b/sandbox/code-block-directive/tools/pygments-enhanced-front-ends/README.txt
@@ -0,0 +1,63 @@
+.. -*- rst-mode -*-
+
+Pygments enhanced docutils front-ends
+-------------------------------------
+
+The example code in "`Using Pygments in ReST documents`_" defines a new
+"sourcecode" directive. The directive takes one argument `language` and uses
+the `Pygments`_ source highlighter to parse and render its content as a
+colourful source code block. 
+
+Combining the pygments_ example code with the standard docutils_ front-ends,
+results in front-end scripts generating output documents with syntax colour.
+For consistency with the majority of existing add-ons, the directive is
+renamed to "code-block".
+
+`rst2html-pygments`_ 
+  enhances the standard docutils ``rst2html`` front-end to
+  generate a HTML rendering with syntax highlight. 
+  
+`rst2latex-pygments`_ 
+  enhances docutils' ``rst2latex`` to generate LaTeX with syntax highlight.
+
+Advantages:
+  + Easy implementation with no changes to the stock docutils_. 
+  + Separation of code blocks and ordinary literal blocks.
+
+Disadvantages:
+  - "code-block" content is formatted by `pygments`_ and inserted in the
+    document tree as a "raw" node making the approach writer-dependant.
+  - documents are incompatible with the standard docutils because of the
+    locally defined directive.
+  - more "invasive" markup distracting from content
+  - no "minimal" code block marker -- three additional lines per code block
+
+
+Example
+"""""""
+
+Python script:
+  :text source: `for-else-test.py.txt`_
+  :HTML:   `for-else-test.py.htm`_
+  :LaTeX:  `for-else-test.py.tex`_
+  :PDF:    `for-else-test.py.pdf`_
+
+Stylesheets:
+  :CSS stylesheet:  `pygments-default.css`_
+  :LaTeX style:     `pygments-default.sty`_
+
+.. References
+
+.. _pygments: http://pygments.org/
+.. _docutils: http://docutils.sourceforge.net/
+.. _Using Pygments in ReST documents: http://pygments.org/docs/rstdirective/
+
+.. _rst2html-pygments:    rst2html-pygments
+.. _rst2latex-pygments:   rst2latex-pygments
+.. _for-else-test:
+.. _for-else-test.py.htm: for-else-test.py.htm
+.. _for-else-test.py.txt: for-else-test.py.txt
+.. _for-else-test.py.tex: for-else-test.py.tex
+.. _for-else-test.py.pdf: for-else-test.py.pdf
+.. _pygments-default.css: ../data/pygments-default.css
+.. _pygments-default.sty: ../data/pygments-default.sty
diff --git a/sandbox/code-block-directive/tools/rst2html-pygments b/sandbox/code-block-directive/tools/pygments-enhanced-front-ends/rst2html-pygments
index c227bbf2e..c227bbf2e 100755
--- a/sandbox/code-block-directive/tools/rst2html-pygments
+++ b/sandbox/code-block-directive/tools/pygments-enhanced-front-ends/rst2html-pygments
diff --git a/sandbox/code-block-directive/tools/rst2latex-pygments b/sandbox/code-block-directive/tools/pygments-enhanced-front-ends/rst2latex-pygments
index f52fc167f..f52fc167f 100755
--- a/sandbox/code-block-directive/tools/rst2latex-pygments
+++ b/sandbox/code-block-directive/tools/pygments-enhanced-front-ends/rst2latex-pygments