On 27 Oct 2005, at 16:02, Peter Rolf wrote:

Gerben Wierda wrote:

...

I have a after={\textrule} in my \setupparagraphs but it takes too much space for my purpose. What can I do about that?

\setuptextrules[ before=, after=, % {\blank[small]} ]

I already had \setuptextrules [before=,after=,inbetween=] but that does not work. It seems that inside my paragraph environment, the settings made outside it are ignored. I also do not have my \setupinterlinespace[medium] there (see other thread). Looks like a startstopparagraph problem to me. G

On Oct 27, 2005, at 21:00, Peter Rolf wrote:

...

I already had

\setuptextrules [before=,after=,inbetween=]

but that does not work. It seems that inside my paragraph environment, the settings made outside it are ignored. I also do not have my \setupinterlinespace[medium] there (see other thread). Looks like a startstopparagraph problem to me.

I've tested it without an environment, so maybe you are right. Have you tried to add some setups (\setuptexrules,..) to

\setupparagraphs[...][...][before=??? or command=???]

I had tried about everything I could think of. That's the one big problem with ConTeXt, it's most of the tim ea matter of trial and error and a difficult process of trial and error even. Documentation often does only mentions the existence of something without an explanation (arguments to commands are seldomly adequately explained). I have been fighting with layout parameters yesterday for a document I needed to keep within one page.

I'm sure there is a (context-)way (but I have not used this command 'til today).

Someone should fund Hans for writing true documentation. G

Nicolas Grilly wrote:

I agree with the idea that documentation of ConTeXt's commands and parameters is rather incomplete.

I'm wondering if it's possible to have a documentation system like Java's Javadoc. We can put comments just before commands definitions and use a little preprocessor written in Perl or Python that parse TeX files in order to build a ConTeXt documentation like the manual titled "ConTeXt commands".

I'm looking forward your opinion about this.

one of the problems with a tex like system is that there is quite some interference, for instance, spacing is related to fonts and height/depth ations and such. This means that it's rather complex to describe some mechanisms independently, take: \framed {\startlines whatever \stoplines} - framed has its own spacing issues, either or not aligned, auto struts, offsets, auto width etc; these can be described (and are in several places) but it takes some playing around to get the picture - startlines in itself has vertical spacing set up - however, in this combination this before/after spacing interferes with auto-struts or take footnotes: due to limitations in tex, footnotes may not be burried too deep in boxes, (has to do with thw way inserts are implemented); so, context has some workarounds which work in most cases, but not always ... sometimes it's not even easy to predict when somethign will work out another example is splitting tables over pages: there are so many boundary conditions that it would take a manual on it sown that's not to say that we should not try to describe it ... you can add for instance comment to the command browser in the wiki Hans

Gerben Wierda wrote:

Someone should fund Hans for writing true documentation.

there will be a book by adam and steve Hans