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 Links containing an URI get parsed twice #4581
Comments
hi, i don't understand why the solution i proposed three months ago, which follows rST specifications, has been ignored after a discussion while this issue has been closed with a different approach which:
the solution i proposed also fixes #4561, which has been closed as unsolvable. this is a confirmation that the problem of nested inlines is better solved in the general case |
i created #4792 in order to better discuss the topic of parsing nested inlines |
@danse I'm sorry, I lost track of your solution here. Anyway, the fix committed above can be reverted and replaced with something better. We'll continue discussion on #4792. |
No worries, with all the activity going on about pandoc i reckon keeping track of conversation isn't easy! |
nested inlines are not allowed in RST but pandoc parses these inlines
recursively. in the case of a link this can lead to a double parsing
due to implicit links. this can garble an RST document going through a
round-trip workflow
The text was updated successfully, but these errors were encountered: