From: Idris Samawi Hamid <ishamid@lamar.colostate.edu>
Subject: \placecontent problems
Date: Mon, 25 Jul 2005 10:12:20 -0600 [thread overview]
Message-ID: <42F33AC2@webmail.colostate.edu> (raw)
[Dear syndicate: I sent this Saturday with no response yet. Sorry 4 being a
pest, but I've got to get this (much-delayed) book to the publisher this week;
hope someone can help...:-)]
Dear gang:
I have a \placecontent-type problem. I want to collect all the subsections and
subsubsections of the main bodymatter of a book into a list, then place that
list into an appendix (conversion=Characters):
\definecombinedlist[synopsis][subsection,subsubsection][textstyle=\tf]
\setupcombinedlist [synopsis][alternative=c,textstyle=\tf]
There are two problems:
1. If I place the content list within a chapter, the list disappears. It works
if I place it before the chapter heading. Thus, I need a way to do
\placesynopsis beneath a chapter heading;
2. \start-\stopappendices begins a new sectionblock, therefore \placesynopsis
does nothing, even if I do not place it within a chapter/appendix.
Thus (assuming we can solve problem 1) I need a way to change the conversion
to Characters on the fly within the bodymatter sectionblock. I need, e.g.
1. A Chapter
2. Another Chapter
A. An Appendix
within the same sectionblock.
Is this possible? I notice that conversion=Characters appears to be defined
for the global sectionblock, but not for local headings. It would be nice if I
could do something like
\definehead[appendix][chapter]
\setuphead[appendix][conversion=Characters]
with the first instance of \appendix starting with `A' (i.e., decoupled from
the chapter numbers).
See the attached file for some experiments.
Best
Idris
========================================================
\setupoutput[pdftex]%
\definecombinedlist[summary][chapter][textstyle=\tf]
\setupcombinedlist [summary][alternative=c,textstyle=\tf]
\definecombinedlist[synopsis][subsection,subsubsection][textstyle=\tf]
\setupcombinedlist [synopsis][alternative=c,textstyle=\tf]
\starttext
\startbodymatter
\placesummary
\page
\placesynopsis
\chapter{This is a test.}
\subsection{This is a subtest.}
\subsubsection{This is a subsubtest.}
\chapter{This is another test.}
\subsection{This is another subtest.}
\subsubsection{This is another subsubtest.}
\chapter{Synopsis}
\placesynopsis
\stopbodymatter
\startappendices
\placesynopsis
\chapter{Synopsis}
\placesynopsis
\stopappendices
\stoptext
============================
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
============================
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next reply other threads:[~2005-07-25 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 16:12 Idris Samawi Hamid [this message]
2005-07-25 19:12 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2005-07-25 21:48 Idris Samawi Hamid
2005-07-23 18:04 Idris Samawi Hamid
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=42F33AC2@webmail.colostate.edu \
--to=ishamid@lamar.colostate.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).