![](https://secure.gravatar.com/avatar/e5aa6984b53b8925e405ebbdbc051ad9.jpg?s=120&d=mm&r=g)
Hi, I won’t reply to single points, thus I don’t quote previous mails. I’m one of the few who work a lot on the wiki. But that means: if I find the time and if I find issues that I’m able to address. Often it needs an hour of research to just explain one parameter properly. Don’t ask about all of them. I’m fading out MkII documentation in the Wiki (I guess we somehow agreed on that). I won’t delete it, but move it to the bottom, mark it as MkII/obsolete and never test it. Indian scripts are the one thing that you can do with MkII but not with MkIV. And I know nothing about them and will probably never use them... I’m also writing a (beginners) book on ConTeXt in German, and I find it really hard to decide what I should include. It can’t become a reference, a complete one is impossible anyway. You can’t do serious work with ConTeXt without using manuals, wiki, mailing list and the sources. There are just too many possibilities and different needs. E.g. I wanted margin notes. Like footnotes, but in the margin. No problem if you want them at the bottom. Very hard if you want them like marginals, starting in the line of the marker... Is this common enough to include it in my book? As a media designer, wo’s also working with InDesign, my focus is of course different from a scientist who just wants her thesis readable... XML processing is an important "USP" for ConTeXt, but I never used it – I write my own XML-to-ConTeXt conversions in Python, since I’ll refine the ConTeXt code anyway. etc. etc. yadda yadda Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD