ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: \setupsection ... works how?
Date: Fri, 20 Feb 2004 11:55:02 +0100	[thread overview]
Message-ID: <6.0.1.1.2.20040220115356.03201ec0@server-1> (raw)
In-Reply-To: <1701729933.20040218162204@iol.it>

At 16:22 18/02/2004, you wrote:
>Hi there,
>
>while replying to a post on comp.text.tex I made the
>interesting discovery that
>
>\setupsection[section-2][conversion=Romannumerals]
>
>cannot be replaced by
>
>\setupsection[chapter][conversion=Romannumerals]
>
>even though chapter is section-2 ... why is it? Shouldn't it be
>possible to use those names?

sections are at  ahigher level that chapters

   \setuphead[chapter][...] should work

of course i can cook up something that would make \setupsectionp[chapter] 
work; remind me in a few weeks

Hans  

      reply	other threads:[~2004-02-20 10:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18 15:22 Giuseppe Bilotta
2004-02-20 10:55 ` Hans Hagen [this message]

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=6.0.1.1.2.20040220115356.03201ec0@server-1 \
    --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).