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
pandoc 2.9.2.1
Compiled with pandoc-types 1.20, texmath 0.12.0.1, skylighting 0.8.3.2
Here's some ReStructuredText (file ma.rst) input that has a code block
in it:
Missing Ampersand in Code Block -ms output
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Here's a code block containing ReStructuredText:
.. code::
.. container:: for-format ms .. figure:: davesmapper-2017-04-10-caves-4-numbered.eps :alt: Map of Bandit's Cave Map of Bandit's Cave .. container:: for-format html latex context epub .. figure:: davesmapper-2017-04-10-caves-4-numbered.png :alt: Map of Bandit's Cave Map of Bandit's Cave
How's that look?
Using the command line pandoc -r rst -w ms -o ma-rst.ms ma.rst, here's
the ms output from it:
.SH 1
Missing Ampersand in Code Block -ms output
.pdfhrefO1"Missing Ampersand in Code Block -ms output"
.pdfhrefM"missing-ampersand-in-code-block--ms-output"
.LP
Here\[aq]s a code block containing ReStructuredText:
.IP
.nf\f[C]
..container::for-formatms
.. figure:: davesmapper-2017-04-10-caves-4-numbered.eps
:alt: Map of Bandit\[aq]s Cave
Map of Bandit\[aq]s Cave
\&.. container:: for-format html latex context epub
.. figure:: davesmapper-2017-04-10-caves-4-numbered.png
:alt: Map of Bandit\[aq]s Cave
Map of Bandit\[aq]s Cave
\f[]
.fi
.LP
How\[aq]s that look?
See the first line that starts with .. container::? That line should
start with \& so it isn't interpreted as an roff command. As it
is, when you build the PDF output from output that line disappears
entirely with no warning to the user. (The default for roff
processors like groff is to ignore unknown commands.)
See the second line that starts with .. container::? That line does start with \&. It makes it through fine. The other lines
whose first non-whitespace character is . make it through fine because
to make it a roff command the first character on the line has to be
a period.
Oddly enough, it doesn't happen with man output. Using the command pandoc -r rst -w man -o ma-rst.man ma.rst here's the man output from
it:
.SH Missing Ampersand in Code Block -ms output
.PP
Here\[aq]s a code block containing ReStructuredText:
.IP
.nf\f[C]\&.. container:: for-format ms
.. figure:: davesmapper-2017-04-10-caves-4-numbered.eps
:alt: Map of Bandit\[aq]s Cave
Map of Bandit\[aq]s Cave
\&.. container:: for-format html latex context epub
.. figure:: davesmapper-2017-04-10-caves-4-numbered.png
:alt: Map of Bandit\[aq]s Cave
Map of Bandit\[aq]s Cave
\f[R]
.fi
.PP
How\[aq]s that look?
The first line that starts with .. container:: has a \& at the
beginning.
The text was updated successfully, but these errors were encountered:
If a line of ms code block output starts with a period (.), it should
be prepended by '\&' so that it is not interpreted as a roff command.
Fixesjgm#6505
If a line of ms code block output starts with a period (.), it should
be prepended by '\&' so that it is not interpreted as a roff command.
Fixesjgm#6505
Missing Ampersand in Code Blocks in
ms
OutputUsing pandoc version
Here's some ReStructuredText (file
ma.rst
) input that has a code blockin it:
Using the command line
pandoc -r rst -w ms -o ma-rst.ms ma.rst
, here'sthe
ms
output from it:See the first line that starts with
.. container::
? That line shouldstart with
\&
so it isn't interpreted as an roff command. As itis, when you build the PDF output from output that line disappears
entirely with no warning to the user. (The default for roff
processors like groff is to ignore unknown commands.)
See the second line that starts with
.. container::
? That linedoes start with
\&
. It makes it through fine. The other lineswhose first non-whitespace character is
.
make it through fine becauseto make it a roff command the first character on the line has to be
a period.
Oddly enough, it doesn't happen with
man
output. Using the commandpandoc -r rst -w man -o ma-rst.man ma.rst
here's theman
output fromit:
The first line that starts with
.. container::
has a\&
at thebeginning.
The text was updated successfully, but these errors were encountered: