Currently, I have this solved -- I process my buffers first using XSLT (as I cannot decompose <... etc. in verbatim buffers into <... and then process the buffer using processXMLbuffer) to generate \startbuffer..\stopbuffer containing <>, and I assure that all buffers will contain <math> and </math> to avoid problems with expanding for \XMLremapdata.
i must have a script somewhere that prepares verbatim (simply because i want to have more structure and so); maybe it makes sense to cook up a sort of standard for buffers so that we can preprocess in an uniform way (some regexp substitution is normally much faster that xslt or full blown parsing).
something:
<bc:buffer label="whatever">....</bc:buffer>
<bc:buffer label="whatever"/>
although formally this equals an empty buffer, so maybe:
<bc:getbuffer label="whatever"/>
makes more sense
does this sound ok?
Hans
------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | [EMAIL PROTECTED] Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------
_______________________________________________ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
