-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rst code blocks with language tag not converting correctly to gfm #5204
Comments
You can also use But basically it seems to boil down to whether the RST reader should add the |
Plus Or is it that the markdown (gfm) writer should be ignoring the class? That would fix 2 of the 4 sample cases as well. The other 2 are coming through as embedded html, to they have more problems. Assuming they are valid rst of course. |
Looks like |
As for
Note that skylighting adds the |
Fedora 27 4.18.19-100.fc27.x86_64
pandoc 2.5 «installed from tarbell»
Compiled with pandoc-types 1.17.5.4, texmath 0.11.1.2, skylighting 0.7.4
Searching through existing issues #721, #4523 look to be related. Sorry about the length of this, but the variation details could important.
Are there multiple flavours of rst, as there for markdown? This is a simplified extract from an rst document from a bitbucket wiki page.
passing that through
pandoc -s --to=gfm --from=rst -o test.md test.rst
give test.md asI would expect
rst is not a format I have worked with, but doing some research, I could not find an rst structure that pandoc would convert to the expected markdown. Here is a bit of an extended case in
sourcecode.rst
and
pandoc -s --to=gfm --from=rst -o sourcecode.md sourcecode.rst
give sourcecode.md asnone of which looks like the expected markdown block. In fact, round trip does not work. Starting from block.md
converting with
pandoc -s --to=rst --from=gfm -o block.rst block.md
gives block.rst asand
pandoc -s --to=gfm --from=rst -o block1.md block.rst
gives block1.md asAm I missing something obvious? rst is new to me, but gfm I have done a lot of work with.
The text was updated successfully, but these errors were encountered: