On Fri, Sep 12, 2014 at 7:24 PM, Lex Trotman <[email protected]> wrote:
> Perhaps not understanding the Gradle plugin is my problem, but if the > Asciidoc(tor) spec says documents are included relative to the document > including them, isn't that well defined within any tree. The problem is that the base_dir isn't just used for resolving include files, it's also used for other things. When that value got changed, then the includes stopped working correctly. So the effort here is to untangle all the references so that each path resolution is handled in the proper way. Because path resolution was never really clearly defined in AsciiDoc, some inconsistencies cropped up in Asciidoctor as it grew...which we could classify as bugs. What I'm planned to do to help clarify things is create a matrix of all the path resolutions in Asciidoctor so that we can see how they are resolved and what settings they depend on. Then we can map that back to AsciiDoc Python and see where the discrepancies are. This is definitely one of the major tasks to take on in the current development iteration. -Dan -- Dan Allen | http://google.com/profiles/dan.j.allen -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
