tag:support.markedapp.com,2011-09-11:/discussions/questions/8973-opml-title-node-from-markdownMarked: Discussion 2017-06-22T21:43:40Ztag:support.markedapp.com,2011-09-11:Comment/428203432017-06-22T15:06:30Z2017-06-22T15:06:30Zopml title node from markdown?<div><p>There does seem to be some inconsistency in this, and I'll look into it.<br>
Right now, the title node is taken from MultiMarkdown metadata (title:<br>
key), so if you're document looks like:</p>
<pre>
<code>title: Main Node Title
# Header 1
## Subsection 1.1</code>
</pre>
<p>then a round trip from Marked->OPML->MindNode->Markdown (or<br>
Marked->OPML->Marked->Markdown) will result in:</p>
<pre>
<code> # Main Node Title
## Header 1
- Subsection 1.1
## Metadata
- title
Main Node Title</code>
</pre>
<p>Some of this is unavoidable as every OPML-capable app can interpret the<br>
hierarchy differently. OPML is just an outline, so a poorly structured<br>
document (that has multiple h1s, or skips from h1-h3, h2-h5, etc.) will<br>
be interpreted differently. However, I do think that Marked should<br>
interpret the first h1 as a main node, especially if there's no title:<br>
metadata. I'll look into this.</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/428203432017-06-22T21:43:40Z2017-06-22T21:43:40Zopml title node from markdown?<div><p>Thank you! <br>
It is certainly not a deal-breaker.<br>
I have adopted a sort of iterative writing workflow, cycling between MultiMarkdown and OPML (mind map), to more effectively integrate the brainstorm and the outline. I would just like to predict what I expect to see with each conversion.<br>
Best regards<br>
Otini</p>
<pre>
<code> From: Brett <tender2+d1ff809608@tenderapp.com></code>
</pre>
<p>To: <a href="mailto:otinikroukamp@yahoo.ca">otinikroukamp@yahoo.ca</a> Sent: Thursday, June 22, 2017 11:06 AM Subject: opml title node from markdown? [Questions]</p></div>Otini Kroukamp