The goal is to solve the issue in both directions by writing the links using a more portable cross-reference association instead of a hard coded link and the renderer will just do the right thing. I'll be sure to use the Groovy docs as an example scenario.
This improvement promises to be a big step forward for writing portable docs.
-Dan
Hi!
I don't think it's exactly the same, mine looks a bit more complicated, since it's about replacing a link to an external (yet asciidoc) file into an internal link as soon as asciidoc "discovers" that the file that contains the link also has included the document (using the include macro).
It doesn't seem to be covered by https://github.com/asciidoctor/asciidoctor/issues/417, is it?
If you reply to this email, your message will be added to the discussion below:http://discuss.asciidoctor.org/Links-and-one-page-HTML-tp429p436.htmlTo start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML
| Free forum by Nabble | Edit this page |