tag:support.markedapp.com,2011-09-11:/discussions/questions/8756-multi-multi-file-documentsMarked: Discussion 2016-05-30T01:53:19Ztag:support.markedapp.com,2011-09-11:Comment/396233312016-04-12T14:22:56Z2016-04-12T14:22:56ZMulti-Multi-file Documents <div><p>You can nest includes, but note that all paths are relative to
the base<br>
document, not the included document. If the base document
includes<br>
"sections/section1.md" and then section1.md wants to include a
subfolder "subsections/subsection1.md", it would have to use:</p>
<p><<[sections/subsections/subsection1.md]</p>
<p>Because all of the included documents have to be collated
before<br>
rendering in order to process things like footnotes, referenced
links,<br>
etc., by the time the include statement is processed, nested
includes<br>
don't know always know where they came from in a folder
hierarchy.</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/396233312016-04-15T09:53:23Z2016-04-15T09:53:24ZMulti-Multi-file Documents <div><p>Hi Brett,</p>
<p>Thank you for the quick reply. I totally forgot about this. You
are right. It works perfectly.</p>
<p>Thanks again.</p>
<p>Best regards,<br>
Otto Smittenaar</p></div>Otto Smittenaartag:support.markedapp.com,2011-09-11:Comment/396233312016-05-30T01:53:18Z2016-05-30T01:53:18ZMulti-Multi-file Documents <div><p>For what's its worth, I have not found this to be the case in my
own "multi-multi-file" documents. My MMD file transclusions with
{{file.md}} are always relative to the file that has the
transclusion. I actually can't do it the way Brett is suggesting
because I need to generate HTML/PDF of some parts separately from
HTML/PDF of wholes.</p></div>davidjohnmacdonald