It turns out that the version of Pygments on the system where this behavior
was occurring was not the minimum required for Sphinx 1.1.3 (had pygments
1.1.1 and 1.2 or greater is required).
Mystery solved...
On Thursday, January 2, 2014 11:24:00 AM UTC-5, Tom Baker wrote:
>
> Hi all.
>
> I've just started trying to use Latex to generate a PDF for some Sphinx
> documentation. I've been using it to generate HTML output for quite a
> while.
>
> I notice that in a literal block that includes things like
> double-underscores, or the '#' sign, the output in the PDF is trying to
> escape it.
>
> For example, if I had a comment in code that was included in a literal
> block like:
>
> ## some comment
>
> The output in the PDF would show as:
>
> \#\# some comment
>
> Same with underscores being prefixed by backslash, and also '<' and '>'
> showing as \textless{} and \textgreater{} in the PDF output when they are
> being used in a literal block of code.
>
> Any ideas what I've misconfigured, or what might cause this?
>
> Thanks!
>
>
>
--
You received this message because you are subscribed to the Google Groups
"sphinx-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sphinx-users.
For more options, visit https://groups.google.com/groups/opt_out.
