Re: [NTG-context] XML processing instructions

2022-05-03 Thread Duncan Hothersall via ntg-context
e learned that you can just use arbitrary context code in xml: >> >> >> >> \def\xmltexdirective#1#2{\doif{#1}{command}{#2}} >> >> >> >> \xmlinstalldirective{tex}{xmltexdirective} >> >> >> >> >> >>

Re: [NTG-context] XML processing instructions

2022-05-02 Thread Duncan Hothersall via ntg-context
tive} > > > > > > > > > > > > Best, > > Denis > > > > *Von:* Maier, Denis Christian (UB) > *Gesendet:* Montag, 2. Mai 2022 09:45 > *An:* 'mailing list for ConTeXt users' > *Cc:* Duncan Hothersa

Re: [NTG-context] XML processing instructions

2022-05-02 Thread Denis Maier via ntg-context
users' Cc: Duncan Hothersall Betreff: AW: [NTG-context] XML processing instructions Von: ntg-context mailto:ntg-context-boun...@ntg.nl>> Im Auftrag von Duncan Hothersall via ntg-context Gesendet: Montag, 2. Mai 2022 09:20 An: mailing list for ConTeXt users mailto:ntg-context@ntg

Re: [NTG-context] XML processing instructions

2022-05-02 Thread Denis Maier via ntg-context
: mailing list for ConTeXt users Cc: Duncan Hothersall Betreff: [NTG-context] XML processing instructions I have a big set of existing XML books (held in a derivative of DocBook) which I'm looking to start processing directly with ConTeXt. (Up to now I have a system which converts the XML into Co

Re: [NTG-context] XML processing instructions

2022-05-02 Thread Duncan Hothersall via ntg-context
Apologies, there are two rogue * in the lxml.preprocessor code, but even when they are removed it doesn't work. On Mon, 2 May 2022 at 08:19, Duncan Hothersall wrote: > I have a big set of existing XML books (held in a derivative of DocBook) > which I'm looking to start processing directly with C

[NTG-context] XML processing instructions

2022-05-02 Thread Duncan Hothersall via ntg-context
I have a big set of existing XML books (held in a derivative of DocBook) which I'm looking to start processing directly with ConTeXt. (Up to now I have a system which converts the XML into ConTeXt code which is then processed, but this is inefficient and lots of the code is now unsupported.) I've