On Thu, May 06 2010, Idris Samawi Hamid ادريس سماوي حامد wrote:
> I'm interested in an audit of all current mid-to-high-level mkiv commands, > including experimental or undocumented ones. I'm trying to come up with, as > much as possible, a set of context commands which is > > mutually exclusive > > jointly exhaustive. Hello, I would like to contribute to a very similar project: a new version of setup-en.pdf, more verbose (detailed description of all options), complete (even for low-level commands, but like you no obsolete commands), and with some additional features (categories, index, cross-references). There is also the new command reference on the wiki, but it's not enough tagged. Here my questions: - How could all these efforts be shared in the most efficient way? - Are others already working for the above project? - Is the structure of cont-en.xml already the good choice and it only needs some extensions for additional features, or would it be as good to use lua-tables (one lua-file per command for example)? I imagine the following steps: 1. decision how to structure the commands (lua or xml or ...) 2. script for producing setup-en.pdf (perhaps Hans can provide his current converter?) 3. implementation of \showsetup (currently broken anyway) 4. filling in the structure with all available information at the moment (last cont-en.xml, wiki) 5. putting nightly built setup-en.pdf on-line 6. filling the structure with all command descriptions Then continuously: 7. updating command descriptions at each update on the wiki 8. updating command descriptions at each new context release 9. updating command descriptions whenever something seems not clear enough (questions on mailing list) Please send me your comments! Cheers, Peter -- Contact information: http://pmrb.free.fr/contact/ _______________________________________________ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
