You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ReStructuredText has a form called "Quoted Literal Block". I've quoted the spec below.
pandoc doesn't recognize this form, and converts into an ordinary paragraph.
From spec:
Quoted Literal Blocks
Quoted literal blocks are unindented contiguous blocks of text where each line begins with the same non-alphanumeric printable 7-bit ASCII character [5]. A blank line ends a quoted literal block. The quoting characters are preserved in the processed document.
[5]
The following are all valid quoting characters:
! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~
Note that these are the same characters as are valid for title adornment of sections.
Google Code Info:
Issue #: 306
Author: [email protected]
Created On: 2011-06-06T22:11:37.000Z
Closed On:
The text was updated successfully, but these errors were encountered:
Pandoc's rst parser handles quoted literal blocks using the '|' character. I didn't know you could also use these other characters -- perhaps that is a recent addition? In any case, I don't see how a rst parser is supposed to know whether
one
two
is a quoted literal block or a list! Also, I tried with rst2html (from Docutils 0.7), and while '>' and '|' worked, '}' did not.
Google Code Info:
Author: [email protected]
Created On: 2011-06-07T22:14:14.000Z
That's interesting. It isn't working for me. Can you post the rst you used
where it worked, so I can see if there's something wrong with my source?
(I'm not producing the rst, just trying to convert it.)
Google Code Info:
Author: [email protected]
Created On: 2011-06-08T20:19:16.000Z
Oops, I was confusing "line blocks" (using |) with quoted literal blocks. Only the former are supported in pandoc.
Though I wonder how the rst parser is supposed to know whether
| hi
| there
is a line block or a quoted literal block?
It seems to match the specification for both.
Google Code Info:
Author: [email protected]
Created On: 2011-06-09T00:50:42.000Z
The text was updated successfully, but these errors were encountered: