About reference to other files

[Ducasse]

While <!inputFile=file.md!> is actually parsing the file and producing a tree that replaces the inputfile node, hyperlinks do not work the same way.

Traditionnally in pillar we could write

 *more...>article.pillar*

which is

 [more...](article.pillar) 

and the link would point to the rendered version of the referenced files. In HTML article.html.
In LaTeX it should be probably '\ref{labelDefinedInTheFile}

We should offer the same because right now we have to write

 [more...](article.html) 

[kasperosterbye]

As I see it, my proposal is non-trivial as it has to be added to Microdown, the LaTeX renderer, the HTML renderer, etc. But here is the idea:

The notation [foo desc](bar.?) signals that this is a cross-reference to another Microdown source file, where the output format is left open.

The renderer is then responsible for handling both sides of the reference:
In HTML:

[foo desc](bar.?) becomes <a href="bar.html">foo desc</a>
bar.md gets an id anchor inserted at its top-level heading

In LaTeX:

[foo desc](bar.?) becomes \ref{bar}
bar.md gets a \label{bar} inserted at its top-level heading when included via <!inputFile=bar.md!>

This keeps the source format-agnostic. The author writes the reference once, and the renderer coordinates both the link and the anchor/label on the target side — without needing to know the output format.

[Ducasse]

Tx kasper I have to think :) but yes having input is nice.
Now I want to release a new version of Foliage.