On 10-5-2010 11:23, Peter Münster wrote:
On Sun, May 09 2010, Hans Hagen wrote:
So, how about more extensive info. As each command has a unique reference, the best approach is to have a separate file for each such entry. I suppose that this can be generated from the wiki.
Hello Hans,
Yes, I also like one file per command, it's easier to manage.
From that it's possible to generate something big (although big pdf's are not that much fun) or generate command specific files that are crosslinked to the main setup file.
For looking up something, I often open big pdf-files (> 1000 pages), and the size doesn't matter. But for printing it, I agree. If someone really wants to print it on A4, the font size must be small and it must be 2-column layout.
printing, distribution and generation also, i expect it to be more that 1000 pages at some point
I imagine the following steps: 1. decision how to structure the commands (lua or xml or ...)
the xml is handy for manipulations but documentation about tex can best be done in tex (verbatim can get quite messy in xml)
Thanks for the advice. This is good, because I don't have any experience with xml.
3. implementation of \showsetup (currently broken anyway)
hm, in what sense broken?
No output:
\usemodule[set-11] \loadsetups % from contextref-env.tex (context-manual) \starttext \showsetup{startproject} % from co-documents.tex (context-manual) \stoptext
\usemodule[set-11] \loadsetups \starttext \showsetup{framed} \stoptext works -)
So what about: - a new directory "http://foundry.supelec.fr/svn/contextman/context-commands" - one tex-file per command
If you agree, I just start.
let me think about it for a while (naming and such) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------