tag:support.multimarkdown.com,2013-02-12:/discussions/questions/7024-use-of-meta-fieldsMultiMarkdown Software, LLC: Discussion 2022-12-09T13:48:48Ztag:support.multimarkdown.com,2013-02-12:Comment/570963722022-12-09T12:35:14Z2022-12-09T12:35:14Zuse of 'meta' fields<div><p>There are a couple of things going on here.</p>
<p>MultiMarkdown parses in a single pass, so you can't "nest" things that<br>
have to be resolved sequentially.</p>
<p>Metadata variables (the '[%foo]' construct) have to be a "top-level"<br>
element within a span of plain text in order to be converted into the<br>
value from the metadata.</p>
<p>Additionally, the URL construction (<code>[foo](URL)</code>) does not interpret<br>
Markdown inside the <code>(URL)</code> section -- that text is used as is.</p>
<p>In this case, you are saying that the URL is literally <code>[%domain]</code>.</p>
<p>You can test something similar with <code>[Foo **bar**](Foo **bar**)</code>. The<br>
strong attribute is applied to the link text, but not the URL.</p>
<p>The one exception to the "single pass" rule is that there is a<br>
pre-processing step that handles the <code>mmd header</code> and <code>mmd footer</code><br>
metadata, and performs file transclusion to create the final plain text<br>
source, and <em>then</em> the MultiMarkdown parser does it's thing.</p>
<p>Fletcher</p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/570963722022-12-09T13:48:48Z2022-12-09T13:48:48Zuse of 'meta' fields<div><p>No dice then. Thanks for explaining principles.</p></div>John Clements