From: "Stephens, Kenny" <kstephens@hsutx.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: sectionconversionset not working for table of contents
Date: Tue, 19 Sep 2017 00:19:00 +0000 [thread overview]
Message-ID: <24ABE1070A5A4041884908141E95A66B024B07AC9F@HSUEX14MBX1.hsutx.edu> (raw)
In-Reply-To: <f4da2822-5a49-8f04-82cc-6586ab953ae5@gmx.es>
Pablo,
Excellent. Works like a charm. Many thanks.
From Pablo's suggestion, I replaced my original two 'sectionblockenvironment' blocks with:
\definestructureconversionset
[sectionnumbers]
[I,N,KR,a,m]
[N]
\definestructureconversionset
[appendix:sectionnumbers]
[O,A,R,r,KA]
[R]
\setupheads
[chapter,section,subsection]
[sectionconversionset=sectionnumbers]
\startsectionblockenvironment [bodypart]
\setuphead [chapter] [style={\rm\bf}, sectionsegments=chapter]
\setuphead [section] [style={\ss\bf}, sectionsegments=section]
\setuphead [subsection] [style={\sl}, sectionsegments=subsection]
\stopsectionblockenvironment
\startsectionblockenvironment [appendix]
\setuphead [chapter] [style={\rm\bf}]
\setuphead [section] [style={\sans}]
\setuphead [subsection] [style={\sl}]
\stopsectionblockenvironment
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2017-09-19 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 12:40 Stephens, Kenny
2017-09-18 17:22 ` Pablo Rodriguez
2017-09-19 0:19 ` Stephens, Kenny [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=24ABE1070A5A4041884908141E95A66B024B07AC9F@HSUEX14MBX1.hsutx.edu \
--to=kstephens@hsutx.edu \
--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).