On Sep 22, 5:34 pm, Phillip Lord <[email protected]> wrote: > If you case, you could have the filter generate the final output, which > would be both an SVG image, and all the stuff that it was given in the > first place. So, given "x y z", your filter would print... > > <svg> > x y z > </svg> > <pre> > x y z > </pre> > > This should do the trick, but, of course, it means that the filter is > backend aware.
I am targeting the docbook backend for dblatex as I want to have pdf, but eventually there is supposed to be a wordml file. (shrug) When having a look at the examples in asciidoc, it hits me that most of the filter coding examples are included twice: .... [whatever-filter] ---- code for whatever-filter ---- .... [whatever-filter] ---- code for whatever-filter ---- The first section to show the ascii code that the user is supposed to type into his ascii editor, and the second to render the example. I guess this is also the twopass solution to your javascript code? .The output of protocol_tc_llc_bv_01 test: ---- protocol_tc_llc_bv_01 input data goes here ---- [protocol-filter] ---- protocol_tc_llc_bv_01 input data goes here ---- I understand that a user do not want to literally print graphviz source code as it is uninteresting in an automata documentation. I have problem understanding why it is difficult to do this in one pass for those cases where the filter input code _and_ the result is of importance to the reader. -- Svenn -- 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.
