Well, don't know if this was the best solution or not but I made a custom ant task that creates that "procedure wrapper" document on the fly. Doesn't seem like the best approach but it's working.
- Andy On Jul 6, 1:50 pm, Andy68 <[email protected]> wrote: > Hi! I have a guide that is composed of a top level document that > includes chapter documents from each of the child subfolders. This > works well because the chapters don't change much so I just hard-code > the include: macros for these. I generate one big docbook output then > chunk it up.. done, works nice. > > Now my issue. I have one folder where I have all sorts of stand-alone > procedures and I'd like to just include them all in one fell swoop > into a "Procedures" chapter so I tried doing this: > > sys::[for /f %f in ('dir /b procedures\procedure_*.asc') do echo > include::%f[] ] > > But, alas, I realize that it's only the output from the final call in > this loop that is getting brought into my document. > > My compilation process uses nant so I could conceivably rig something > up using that but I'd really like to keep this simple using some sort > of intrinsic asciidoc functionality. > > Does anyone have a suggestion on a good way to go about it? > > - Andy -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
