Wolfram Language Paclet Repository
Community-contributed installable additions to the Wolfram Language
Wolfram`Parser`
MarkdownInlineParse  |
|
| | ||||
▪
The result is a flat of s. Prose runs are ; emphasis is / / ; code is / / ; math is / ; the paired references are and ; and / / cover the remaining spans.
"Type""Text","Text"str
"Bold"
"Italic"
"BoldItalic"
"Code"
"LiteralCode"
"HtmlCode"
"MathInline"
"MathDisplay"
"Link"
"Image"
"Sub"
"Sup"
"Strike"
▪
A span's body — the of an emphasis / sub / sup / strike atom, or the of a link — is itself a of inline atoms, because the captured body is re-parsed recursively. So nests a atom inside the .
"Children"
"Label"
**bold$x$**
"MathInline"
"Bold"
▪
Adjacent atoms are merged, so a contiguous prose run is one atom, not one atom per character.
"Text"
▪
Overlapping openers resolve by PEG order, longest first: before before , double backtick before single, before , and the HTML / before their single-character Pandoc twins.
***
**
*
$$
$
<sub>
<sup>
▪
Underscore emphasis follows CommonMark word-boundary rules: opens emphasis at a word boundary, but an underscore between word characters () stays literal.
_em_
snake_case
▪
A literal inside a run becomes the Unicode ellipsis character; inside a code span or math span is left verbatim.
...
"Text"
...
▪
A backslash before ASCII punctuation (, ) yields that punctuation as literal text rather than opening a span.
\*
\$
▪
An unclosed delimiter is not an error — the opener and its trailing text stay as literal .
"Text"
▪
handles inline constructs only. Whole-document structure (frontmatter, headings, code fences, thematic breaks, paragraph splitting) is 's job; feed a document's block text through this function to resolve its spans.
"Prose"
▪
is the wrapper around the combinator: it runs and then merges text runs, applies the ellipsis and underscore-emphasis passes, and re-parses span children. On a parse failure it returns the object unchanged.
▪
The grammar and its post-processing passes are walked through in the .
Examples
(15)
Basic Examples
(1)
Plain prose is a single atom:
"Text"
In[1]:=
 | MarkdownInlineParse |
Out[1]=
{TypeText,Textplain text}
Emphasis and code spans become their own atoms, with the surrounding prose in runs:
"Text"
In[2]:=
| MarkdownInlineParse |
Out[2]=
{TypeBold,Children{TypeText,Textbold},TypeText,Text and ,TypeCode,Codecode}
A link's label is parsed recursively — here it is a code span, not plain text:
In[3]:=
| MarkdownInlineParse |
Out[3]=
{TypeLink,Urlpaclet:ref/Range,Label{TypeCode,CodeRange}}
Scope
(8)
Properties & Relations
(3)
Possible Issues
(2)
Neat Examples
(1)
 |
|
 |
|
""