At first glance (or perhaps even after several glances) it seems logical that the include directive could handle subdocuments. However, after close examination of the processor logic and existing uses of the include macro, it becomes clear to me that include is not appropriate to handle both cases.
I know it seems like a document with a starting line that looks like a document title should be treated as a subdocument, but that misses too many scenarios: - the document has to be parsed, which is not appropriate at this point in the processor (we have to consider comment lines, attribute entries, etc) both above & below - the document may not have level 0 as its starting section title, but could still be a subdocument - we might be in a literal context, for which the preprocessor is not aware - we break compatibility with AsciiDoc Python severely, with no way to emulate the behavior there - ... I definitely agree there is a need for the subdocuments feature. I also believe that it should be implemented as a block macro. As for the name, includedocument is far too verbose. I think subdocument or just subdoc is sufficient. I want to emphasize that it's possible to start prototyping this feature today using a block macro extension. I'd like it to live as an extension while we flesh it out and bring it into core once we've got an implementation we like. -- 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/groups/opt_out.
