This is the default behaviour of the original Markdown specification. From pandoc(1):
Original Markdown allows you to include HTML “blocks”: blocks of HTML
between balanced tags that are separated from the surrounding text with
blank lines, and start and end at the left margin. Within these blocks,
everything is interpreted as HTML, not Markdown; so (for example), * does
not signify emphasis.
However, some renderers (including pandoc), extend this:
Pandoc behaves this way when the markdown_strict format is used; but by
default, pandoc interprets material between HTML block tags as Markdown.
Implementing something like this isn't easy, but it's not impossible: it would require breaking apart the text in a LOWDOWN_BLOCKHTML into a series of LOWDOWN_RAW_HTML separated by parsed markdown. If you'd like to take a look at this, it would require tokenising the interval of the block and calling the parser for non-HTML subintervals. See document.c where LOWDOWN_BLOCKHTML is pushed onto the parse stack.
I understand, thank you. I may be able to do some CSS tricks with the "p" element to get a two-column layout on wider display ports in the interim. I'll close this issue.
Kristaps, I'm don't understand the difference between node types LOWDOWN_BLOCKHTML and LOWDOWN_RAW_HTML. Would it make sense to parse my case into a few LOWDOWN_BLOCKHTML nodes with other markdown nodes in between? I see that <hr /> and <br /> are parsed as LOWDOWN_BLOCKHTML. When would I expect to see LOWDOWN_RAW_HTML?
from lowdown.
Comments (4)
This is the default behaviour of the original Markdown specification. From pandoc(1):
However, some renderers (including pandoc), extend this:
Implementing something like this isn't easy, but it's not impossible: it would require breaking apart the text in a
LOWDOWN_BLOCKHTML
into a series ofLOWDOWN_RAW_HTML
separated by parsed markdown. If you'd like to take a look at this, it would require tokenising the interval of the block and calling the parser for non-HTML subintervals. See document.c whereLOWDOWN_BLOCKHTML
is pushed onto the parse stack.from lowdown.
I understand, thank you. I may be able to do some CSS tricks with the "p" element to get a two-column layout on wider display ports in the interim. I'll close this issue.
from lowdown.
Kristaps, I'm don't understand the difference between node types
LOWDOWN_BLOCKHTML
andLOWDOWN_RAW_HTML
. Would it make sense to parse my case into a fewLOWDOWN_BLOCKHTML
nodes with other markdown nodes in between? I see that<hr />
and<br />
are parsed asLOWDOWN_BLOCKHTML
. When would I expect to seeLOWDOWN_RAW_HTML
?Thank you,
Ron
from lowdown.
Addressed in #128
from lowdown.
Related Issues (20)
Recommend Projects
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
Recommend Topics
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web
Some thing interesting about web. New door for the world.
server
A server is a program made to process requests and deliver data to clients.
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization
Some thing interesting about visualization, use data art
Game
Some thing interesting about game, make everyone happy.
Recommend Org
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.
Jobs
Jooble