ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Gerben Wierda <gerben.wierda@rna.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: More levels of subsubsection?
Date: Sun, 17 Aug 2014 18:08:39 +0200	[thread overview]
Message-ID: <56F8EEC6-34C9-43E9-A272-69DC570FEA9F@rna.nl> (raw)
In-Reply-To: <C37E2743-7429-4895-A91A-9404DCF7CD92@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1713 bytes --]

On 16 Aug 2014, at 15:08, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:

> Can you first explain what you try to achieve, you’re talking about indenting something but I don’t know what you want to indent, only the header or the complete content of the section/subsection.

I've been able to create a lot of what I want by using \definehead and \setuphead. I am using ownnumber.

\definehead[PSAappsection][subsection]
\definehead[PSAappsubsection][subsubsection]
\definehead[PSAappsubsubsection][subsubsubsection]
\setuphead[PSAappsection][continue=no,ownnumber=yes,after=]
\setuphead[PSAappsubsection][continue=no,ownnumber=yes,before=,after=]
\setuphead[PSAappsubsubsection][continue=no,ownnumber=yes,before=,after=]

What is left is to figure out the style where each sub (sub sub) section is indented more including teh paragraphs that belong to that setion. I robably need to do something with after (to set the indenting) and before (to end the indenting). In fixed width font like this:

1. SECTION
   text text text

   1.1 Sub Section
       text text text
 
       text text text

   1.1.1 Sub Sub Section
         text text text

G

> 
> Wolfgang
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 9488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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:[~2014-08-17 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 15:33 Gerben Wierda
2014-08-15 16:11 ` Wolfgang Schuster
2014-08-16 12:48   ` Gerben Wierda
2014-08-16 13:08     ` Wolfgang Schuster
2014-08-17 16:08       ` Gerben Wierda [this message]
2014-08-17 19:22         ` Wolfgang Schuster

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=56F8EEC6-34C9-43E9-A272-69DC570FEA9F@rna.nl \
    --to=gerben.wierda@rna.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).