Svenn Are Bjerkem <[email protected]> writes: > I am currently also thinking about having the data external and just > do like this: > ---- > include::protocol_tc_llc_bv_01.log[] > ---- > for the text part as the protocol test will spit out a lot of data for > different test cases. > then I could have done something like this: > > [myfilter] > include::protocol_tc_llc_bv_01.log[] > > to get the log and picture included and generated in one run.
This might not do what you expect; include is relative to the file it's in, not the file that's being compiled. So, if you put this in a .conf file in your .asciidoc, it will try and load protocol_tc_llc_bv_01.log from there. I understand why this was done, but it makes life hard at times. For instance, I wanted to do something similar where I include some code (javascript) through source-highlight, and then include the *same* code raw (with the additional HTML), so you can view the syntax highlighted code and run it. At the moment, I have to do this in two steps, rather than one. 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. Phil -- 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.
