ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: More levels of subsubsection?
Date: Sat, 16 Aug 2014 15:08:00 +0200	[thread overview]
Message-ID: <C37E2743-7429-4895-A91A-9404DCF7CD92@gmail.com> (raw)
In-Reply-To: <44BBCEE4-5EA8-4856-8C5A-897A1A2CDEB3@rna.nl>


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


Am 16.08.2014 um 14:48 schrieb Gerben Wierda <gerben.wierda@rna.nl>:

> On 15 Aug 2014, at 18:11, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
> 
>> 
>> Am 15.08.2014 um 17:33 schrieb Gerben Wierda <gerben.wierda@rna.nl>:
>> 
>>> I am reproducing another document in an appendix. This document has a numbered structure and an appendix.
>>> 
>>> A. My Appendix
>>> 
>>> My appendix text introduction
>>> 
>>> 1. Foo
>>> foo text
>>> 
>>> 1.1 Foo
>>> foo text
>>> 
>>> 2. Foo Appendix
>>> 
>>> 1. FooBar
>>> FooBar text
>>> 
>>> 1.1 FooBar
>>> FooBar text
>>> 
>>> 1.1.1 FooBar
>>> FooBar text
>>> 
>>> When I use \chapter for My and \subsection and \subsubsection for Foo, how do I solve the FooBar appendix? I have now
>>> 
>>> \chapter My Appendix
>>> 
>>> My appendix text introduction
>>> 
>>> \subsection Foo
>>> foo text
>>> 
>>> \subsubsection Foo
>>> foo text
>>> 
>>> \subsection Foo Appendix
>>> 
>>> But then, how do I solve:
>>> 
>>> 1. FooBar
>>> FooBar text
>>> 
>>> 1.1 FooBar
>>> FooBar text
>>> 
>>> 1.1.1 FooBar
>>> FooBar text
>>> 
>>> And to matters more complixated, Id like to reproduce the original's indentation, that is 1.1 is a bit more indented than 1 and 1.1.1 is a bit more than 1.1.
>> 
>> Can you make a *working* minimal example with the code you’re currently using?
> 
> I have tried but a separate test file behaves differently. Probably I'll have to rebuild the whole producs/chapters/evironment setup.
> 
> I've been studying the (2001) manual a bit more and I might need to define my own headers. If I do a \definhead between \start\stop pairs, can I isolate these definitions from what comes after? 

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.

Wolfgang


[-- Attachment #1.2: Type: text/html, Size: 3191 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-16 13: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 [this message]
2014-08-17 16:08       ` Gerben Wierda
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=C37E2743-7429-4895-A91A-9404DCF7CD92@gmail.com \
    --to=schuster.wolfgang@gmail.com \
    --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).