On 25 April 2011 03:44, Alexandre Hamez <[email protected]> wrote:
> Hello,
> I'm writing a tutorial for a DSL we have at my lab. I like to be certain
> that the examples given compile correctly. Thus, I've made a filter which
> finds AsciiDoc blocks, nested in the DSL comments. I thus can maintain a
> single source file for both the documentation and the code. For example:
> input file:
> /*{
> An explanation about a *shiny feature*.
> }*/
> Some_Code;
> /*{
> _Another_ *nify feature*.
> }*/
> Another_Code;
> Output for AsciiDoc :
> An explanation about a *shiny feature*.
> ----
> The shiny feature in the DSL
> ----
> _Another_ *nify feature*.
> ----
> Another_Code;
> ----
>
> As you see, my filter can output several blocks. The problem is that it
> seems that AsciiDoc does not provide a substitution in postsubs that can
> process this type of output.
Asciidoc does not process the output of filters, they are intended to
write backend not asciiidoc, otherwise you wouldn't be able to use
filters like Pygments that write HTML.
You could try calling your extractor from a system attribute, the
stdout is then processed by Asciidoc eg
{sys:extractor_command infile selection_parameters}
Otherwise if it works keep doing it the way you are, even Asciidoc has
to use a nested Asciidoc for table nesting.
Cheers
Lex
--
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.
