![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
On 2/26/2016 8:52 AM, Pablo Rodriguez wrote:
On 02/25/2016 10:48 AM, Hans Hagen wrote:
[...] i'm still puzzled what you want
Hans,
I’m only guessing (after testing the XML analyzing ability that you discovered us with a single XML file).
The analysis is important, but after that I have to write the actual environment.
I think that the basic structure that I sent in https://mailman.ntg.nl/pipermail/ntg-context/2016/084582.html is useful to avoid writing myself the environment.
You want to autogenerate that? That could become quite huge (And probably most would be discarded later anyway of you want all permutations of elements and attributes)
I mean, of course I have to add the relevant commands to handle in ConTeXt each element. But with the basic scheme, I know which elements (in the broadest sense) I have to setup.
I want to avoid writing the whole element list in the environment by hand. But I may be doing wrong (this is totally new to me).
Or do you write (type) each environment from scratch after using the report generated by ConTeXt?
We just start with the trivial things and then look at the specific structures. We get either relative simple html like xml or we get quite complex educational markup, with quite demanding rendering and multiple products. The good news is that the number of elements is always limited (analyzing would not really work well because it can be that thousands of files need to be loaded and merged which itself is not a problem, but one then always need to interpret what needs to get loaded). Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------