From: Hans Hagen <pragma@wxs.nl>
Subject: Re: \setuphead question (long section lines not wrapping)
Date: Thu, 11 Dec 2003 19:10:14 +0100 [thread overview]
Message-ID: <6.0.1.1.2.20031211190749.02049b70@server-1> (raw)
In-Reply-To: <Pine.LNX.4.56.0312111200210.13473@phoebe.cs.unm.edu>
At 20:19 11/12/2003, you wrote:
>On Thu, 11 Dec 2003, Hans Hagen wrote:
>
> > \startstandardmakeup
> > \startlocalfootnotes
> > Thanks \footnote{test}
> > \stoplocalfootnotes
> > \vfill \placelocalfootnotes
> > \stopstandardmakeup
>
>This works fine for separate titlepages, is there a similar technique for
>doing this when the title is on the first page of the text (see the
>attached dvi from my last message for an example)? I had tried using
>local footnotes during my experimentation the other day, but they always
>appeared between the title and the text, rather than below the first
>column of text, as is the norm. Again, this is a minor issue, as a
>combination of \high, \footnotetext, and \resetnumber work just fine as a
>quick hack...
\title{test \footnote{test}}
\section{test \footnote{test}}
tets \footnote{test}
\framed{\postponefootnotes test \footnote{test}}
should work, but somehow the latest greatest multi note version messes up
the postponed notes (they end up in a separate class)
> > \setuplabeltext[en][section={{},{.}},subsection={{},{.}}]
> >
> > should do that; i don't know why it does not break in your case
>
>Ah...thank you; this does work. Although I must say, I would *never* have
>gotten this from the documentation which treats \setuphead and it's
>command parameter as the way to control the appearance of sectioning
>titles, and never provides a backreference to \setuplabeltext, which is
>tucked away in the chapter on language specific issues. And even there,
>the documentation never comes close to describing the behavior shown
it started as an experiment -)
>above. Thank goodness for the living breating documentation that this
>list provides then, eh?
hm, this double label thing is needed for chinese (which introduced a few
more interesting non documented features)
anyhow, those few hours playing learned you read context source code -)
Hans
prev parent reply other threads:[~2003-12-11 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 17:10 William D. Neumann
2003-12-10 18:03 ` Hans Hagen
2003-12-10 21:58 ` William D. Neumann
2003-12-10 22:10 ` Thomas A.Schmitz
2003-12-11 8:41 ` Hans Hagen
2003-12-11 19:19 ` William D. Neumann
2003-12-11 18:10 ` Hans Hagen [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=6.0.1.1.2.20031211190749.02049b70@server-1 \
--to=pragma@wxs.nl \
--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).