When reading your my way i noticed a few things:
(1) sometimes too wide verbatim xml lines can better be handled as follows:
\starttext
\showXMLwrd[oeps]
\startbuffer
<text>
<example>
test <oeps/> test
</example>
</text>
\stopbuffer\showXMLbuffer
\stoptext
There is also an inline variant:
test test test test test \showXMLtext {<text> <example> test <oeps/> test
</example> </text>} test test test testand of course a \showXMLfile{name.xml}
The advantage of this method is that too wide lines are handled better i.e. they are properly indented
(2) When formatting an ascii text (i.e. the input source), instead of
test \test{test[test] test{test}} test
one can say:
test \test {test [test] test {test}} test
which wraps nicer. So, one may have a space after a \command, and between {one} {two} arguments (few
exceptions) etc.
(3) instead of \input symb-uni you can use \usesymbols[uni]
(4) I've just added \startxtyping and \startxxtyping to the style
\definetyping[xtyping] [style=\ttx] \definetyping[xxtyping][style=\ttxx]
Hans
Hans
_______________________________________________ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
