Benoît Bryon

Original RST indentation rules are here : http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#indentation

See also [PEP 12](http://www.python.org/dev/peps/pep-0012/), which tells 4 spaces-indentation for literal blocks.

Hi @ardalis :) Thanks for the report. Feel free to pull-request some changes, I'll be glad to review them ;) So Github now renders `code-block` correctly, cool! The `code-block` example...

Tagged as "bug" because there is something wrong in the documentation.

Some conventions seen in PEP 12: - 4 spaces indentation for literal blocks - "references" section at the end of the document - "copyright" section at the end of the...

Implementation may be a RST docutils writer: takes a docutils tree and renders it as "standardized" RST. I don't know if there are RST constructs that we can't reproduce: -...

Started implementation at https://github.com/benoitbryon/rst2rst

A question is: where should we plug RST syntax verification? - At http://sphinx.pocoo.org/ext/appapi.html#events, we see that candidate would be `doctree-resolved` event, because at this stage, we know that documents are...

See http://www.linuxbyexamples.net/2012/08/Nginx-post-action-to-trigger-successfully-download-file.html and http://wiki.nginx.org/HttpCoreModule#post_action

> This is my first time using both xsendfile and downloadview so I might be doing something wrong. I apologize if that is the case. And I am not an...