ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: structure levels
Date: Wed, 29 Sep 2010 15:12:43 +0200	[thread overview]
Message-ID: <4CA33B4B.9040603@wxs.nl> (raw)

Hi Alan,

I added a default set

\starttext

\startstructurelevel [title=first top level]

     \startstructurelevel [title=first lower level]
         \startstructurelevel [title=second lower level]
             \startstructurelevel [title=third lower level]
                 test
             \stopstructurelevel
         \stopstructurelevel
     \stopstructurelevel

     \startstructurelevel [title=first lower level]
         \startstructurelevel [title=second lower level]
             \startstructurelevel [title=third lower level]
                 test
             \stopstructurelevel
         \stopstructurelevel
     \stopstructurelevel

\stopstructurelevel

\stoptext

this uses

\definestructurelevels
   [default]
   [chapter,
    section,
    subsection,
    subsubsection,
    subsubsubsection,
    subsubsubsubsection]

The more verbose variant is still there:

\definehead[xxxxxxsection][subsubsection]
\setuphead [xxxxxxsection][color=red]

\definestructurelevels[main][chapter,section,subsection,subsubsection]
\definestructurelevels[next][chapter,section,subsection,xxxxxxsection]

\starttext

\startstructurelevel [main] [title=first top level]

     \startstructurelevel [main] [title=first lower level]
         \startstructurelevel [main] [title=second lower level]
             \startstructurelevel [main] [title=third lower level]
                 test
             \stopstructurelevel
         \stopstructurelevel
     \stopstructurelevel

     \startstructurelevel [main] [title=first lower level]
         \startstructurelevel [main] [title=second lower level]
             \startstructurelevel [next] [title=third lower level]
                 test
             \stopstructurelevel
         \stopstructurelevel
     \stopstructurelevel

\stopstructurelevel

\stoptext


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
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


                 reply	other threads:[~2010-09-29 13:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CA33B4B.9040603@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).