[NTG-context] Some gardening

Mojca Miklavec mojca.miklavec.lists at gmail.com
Mon Jul 4 21:14:00 CEST 2005

Hans Hagen wrote:
> Mojca Miklavec wrote:
> > Here's some more work for you Patrick, in case you get bored.
> > (I guess I'll soon be removed from the list as a spammer/abuser if I
> > continue writing mails such as this one :)
> > What do the others think about it?
> some day others will start expecting you to help patrick gardening -)

I'm not a reliable person, I don't have as much time and I'm much
slower than "an average ConTeXt developer", but if I know how to do
something and if I have a possibility to do so (access to the
source,...), than I'm willing to contribute - step by step.

> > Take \setuplayout for example. Describing such huge collection of
> > parameters in plain text is not clear, synoptic any more. It would be
> > great if there would be a possibility to add descriptions for:
> > - the command as such (already there)
> > - every pair of braces (only one for \setuplayout), has to be visible
> > if it is optional or not
> > - every parameter inside a single brace
> > - every single option for that parameter (for example: width=middle
> > means that ...), default has to be marked
> default maring is a bit tricky (since it can be \SomeCommand which will they
> blow up context visualizer; in principle, now that we've moved to xml for the
> descriptor, it's easier to add features.
> can you give a more verbose example

Most options are already self explaining, but some are not. A nice
example are serried, broad, packed, ... in \setupitemize. Here it is
necessary to be able to specify what which option does.

An example:
- '\setupitemgroup' - we need place to describe a command and probably
give an example
- there are 4 groups of arguments for this command
    - for each of these groups we would like to specify if the group
is optional or not, what this group does, defaults (if any) and
probably an example
- the third and fourth group have lots of possible arguments (broad,
serried, packed, columns, ... width=...,stopper=..., ...)
    - we have to specify possible combinations of them (broad |
serried | n*broad | n*serried), (packed | unpacked) - broad and
serried may not occur at the same time, while broad and packed may
    - we have to specify if the parameters are "swithches" (they are
present or they are not, like broad, packed) or if they have
parameters, like "headstyle=...".
- In case we have parameters like "headstyle=...", we have to specify
all the alternatives (normal | bold | slanted | boldslanted | ...),
probably note the default value as well. We also have to be able do
describe these alternatives. For example "caps - will typeset the head
of itemization in small caps". And possibility to add an example as

Once again:

% perhaps some "pseudo commands" as this one could be added as well
... equal to/see \setupitemgroup[itemize]


Classification (?): setups, different forms of paragraph typesetting
Description: The command is used to control the layout of itemization

[.1.] {\sl name} - the name of item group for which this setup holds
    {\sl name}
        example: itemize - equal to writing \setupitemize

(optional ?)
[.2.] {\sl number} | each - to which level of itemization the setup should apply
    {\sl number} 
        example: 2 - the second level of itemization
    each - the setup will hold for all the levels

(optional ?)
[.3.] standard [default], (n*broad | n*serried), (packed | unpacked),
stopper, (joinedup | paragraph), (atmargin | inmargin | intext),
autointro, loose, section, columns, (one | two | three | four)
    broad | n*broad - extra horizontal space after symbol
    serried | n*serried - little horizontal space after symbol
        example: someone would probably like to give an example of an
itemization environment with 2*serried option turned on (Wiki-like)
    packed - no white space between items
    unpacked - white space between items
    stopper - use a character like '.' or ':' after the symbol
    joinedup - no white space before and after itemization
    paragraph - no white space before itemization
    atmargin - symbol between margin and text
    inmargin - symbol in margin
    intext - symbol 
    intro - no pagebreak
    loose - ?
    section - ?
    columns - typeset in one, two, three or four columns (two is the default)
    one - will make itemize in one column (where no 'columns' option
is set, this is the default)
    two - will make itemize in two columns (default where 'colums'
option is set)
    three - if columns option is set, it will make the itemize in three columns
    four - if columns option is set, it will make the itemize in four columns
% I have a feeling that the user manual is not very consistent here


The schema should (I think it does already) support nested commands as
well (like most commands that accept the same parameters as
\setupframed). In this case no change in XML specification is needed,
but it would be nice if texshow would show that parameters as well.

It's difficult to express this in plain text. I'm sorry, my
description is confusing, I know. Also, don't bother about the
mistakes I've made in the description - I don't know what exactly all
of the options do, so I probably gave some wrong descriptions. The
example is just to get the feeling of what I mean with a "description
of parameters on all the levels".

Most of the options DO NOT need additional description as the name is
descriptive enough, but for some of the options an individual
description would be of great help.

> > The ability to add commands is already there I think (I have never
> > tried it out yet). What about adding commands for (official and
> > third-party) modules? It should be separated from the main page, but
> > still offering the same functionality.
> in principle each module should have an associated spec file

Do authors of the modules know that?


More information about the ntg-context mailing list