From: David Arnold <dwarnold45@cox.net>
Subject: section prefix=+
Date: Wed, 21 Dec 2005 23:21:00 -0800 [thread overview]
Message-ID: <FB3E69E9-FE12-476D-9757-C414BE84FC76@cox.net> (raw)
Hans et al,
We'll have different teachers writing different sections of a multi-
chapter, multi-section document. The following use of prefix=+, as
far as I can see, will keep them from stumbling over each other's
references while they are working independently. I wonder how this
will work in the project-product-component structure?
% output=pdf
\environment bookenv
\setuphead[section]
[prefix=+]
\starttext
\startuseMPgraphic{david}
draw unitsquare scaled 2cm withpen pencircle scaled 5mm withcolor red;
\stopuseMPgraphic
\startbuffer[table]
\starttable[|c|c|]
\HL
\VL This \VL is \VL\FR
\VL a \VL table \VL\LR
\HL
\stoptable
\stopbuffer
\startbuffer[figure]
\startcombination[2*1]
{\useMPgraphic{david}}{First caption}
{\useMPgraphic{david}}{Second caption}
\stopcombination
\stopbuffer
\completecontent
\chapter[quadratic]{Quadratic Functions}
\input tufte
\section[parabola]{The Parabola}
\input tufte
\placefigure[][fig:1]
{This is the caption of the figure.}
{\getbuffer[figure]}
\input tufte
\placetable[][tab:1]
{A very simple example of a table.}
{\getbuffer[table]}
\input tufte
\placefigure[][fig:2]
{This is the caption of the figure.}
{\getbuffer[figure]}
\input tufte
In \in{Figure}[fig:1] on \at{page}[fig:1], we see \ldots.
\section[vertex]{Vertex Form}
\input tufte
\placefigure[][fig:1]
{This is the caption of the figure.}
{\getbuffer[figure]}
\input tufte
\placetable[][tab:1]
{A very simple example of a table.}
{\getbuffer[table]}
\input tufte
\placefigure[][fig:2]
{This is the caption of the figure.}
{\getbuffer[figure]}
\input tufte
In \in{Figure}[fig:1] on \at{page}[fig:1], we see \ldots.
\chapter[poly]{Polynomial Functions}
\input tufte
\section[end]{End Behavior}
\input tufte
\placefigure[][fig:1]
{This is the caption of the figure.}
{\getbuffer[figure]}
\input tufte
\placetable[][tab:1]
{A very simple example of a table.}
{\getbuffer[table]}
\input tufte
\placefigure[][fig:2]
{This is the caption of the figure.}
{\getbuffer[figure]}
\input tufte
In \in{Figure}[fig:1] on \at{page}[fig:1], we see \ldots.
\section[zeros]{Zeros}
\input tufte
\placefigure[][fig:1]
{This is the caption of the figure.}
{\getbuffer[figure]}
\input tufte
\placetable[][tab:1]
{A very simple example of a table.}
{\getbuffer[table]}
\input tufte
\placefigure[][fig:2]
{This is the caption of the figure.}
{\getbuffer[figure]}
\input tufte
In \in{Figure}[parabola:fig:1] on \at{page}[parabola:fig:1], we see
\ldots.
\stoptext
next reply other threads:[~2005-12-22 7:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 7:21 David Arnold [this message]
2005-12-22 7:25 ` section prefix=+ (oops) David Arnold
2005-12-22 10:31 ` Red framed text Jilani Khaldi
2005-12-22 10:42 ` Taco Hoekwater
2005-12-22 17:07 ` Jilani Khaldi
2005-12-22 21:15 ` Hans Hagen
2005-12-22 22:36 ` Jilani Khaldi
2005-12-23 7:59 ` Jilani Khaldi
2005-12-23 8:25 ` Peter Münster
2005-12-22 23:22 ` David Arnold
2005-12-23 9:28 ` Hans Hagen
2005-12-23 17:44 ` setbounds question David Arnold
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=FB3E69E9-FE12-476D-9757-C414BE84FC76@cox.net \
--to=dwarnold45@cox.net \
--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).