From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: combinedlist: different behaviour in mkiv
Date: Fri, 21 Sep 2012 20:03:41 +0200 [thread overview]
Message-ID: <4EAE3123-EC60-496B-B8E2-A619DF45F289@gmail.com> (raw)
In-Reply-To: <20120921092419.GA19290@phlegethon.router_intern>
Am 21.09.2012 um 11:24 schrieb Philipp Gesang <gesang@stud.uni-heidelberg.de>:
> Hi Stefan,
>
> ···<date: 2012-09-20, Thursday>···<from: Stefan Rothe>···
>
>> % Top level head
>> \definehead [AgendaPart] [section]
>> \setuphead [AgendaPart] [ownnumber=yes, number=yes,
>> numbercommand={Part }, style=\bf\tfb]
>>
>> \newcounter\AgendaPartNumber
>>
>> \define [1] \agendapart {
>> \doglobal\increment\AgendaPartNumber
>> \AgendaPart{\Character{\AgendaPartNumber}}{#1}
>> }
>>
>> % Second level head, idependently numbered
>> \definehead [AgendaItem] [subsubsection]
>> \setuphead [AgendaItem] [ownnumber=yes, number=yes, style=\bf]
>
> %% Adjust the “sectionsegments” parameter to include only the
> %% head’s own structure level. (Multiple levels need to be
> %% separated by cola (“:”)).
> \definehead [AgendaItem] [subsubsection] [
> ownnumber=yes,
> number=yes,
> style=\bf,
> sectionsegments=subsubsection,
> ]
>
> Btw why does your structure go section->subsubsection? Afair
> these have depth 3 and 5 respectively, so it would look more
> consistent to use section->subsection (3->4).
+1
I wonder also why he uses such a complicated method for his headings when there is a better way.
\defineresetset [none][][0]
\definehead [agendapart] [section] [sectionresetset=none,sectionsegments=agendapart,style=\bfb,conversion=A,bodypartlabel=part]
\definehead [agendaitem] [subsection] [sectionresetset=none,sectionsegments=agendaitem,style=\bf]
\setuplist [agendapart] [width=1.5cm,pagenumber=no,style=bold,label=yes]
\setuplist [agendaitem] [width=1.5cm,pagenumber=no]
\definecombinedlist [agenda] [agendapart,agendaitem]
\starttext
\placeagenda
\agendapart{First}
\agendaitem{One}
\agendaitem{Two}
\agendapart{Second}
\agendaitem{Three}
\agendaitem{Four}
\stoptext
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
___________________________________________________________________________________
prev parent reply other threads:[~2012-09-21 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 8:04 Stefan Rothe
2012-09-21 9:24 ` Philipp Gesang
2012-09-21 18:03 ` Wolfgang Schuster [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=4EAE3123-EC60-496B-B8E2-A619DF45F289@gmail.com \
--to=wolfgang.schuster@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).