From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Footnotes into a single paragraph (mkiv)
Date: Sat, 31 Jul 2010 00:28:46 +0200 [thread overview]
Message-ID: <4C53521E.3060807@wxs.nl> (raw)
In-Reply-To: <4C52E9F1.9050601@gmx.at>
On 30-7-2010 5:04, Markus Finke wrote:
> Can anybody help me? I don’t want to fall back on LaTeX because I would
> miss a lot of features for fonts and I prefer the smoother usability
> writing in ConTEXt.
>
> Is there any hope for this (not to rare) design in footnotes?
I uploaded an alpha release. You need to take the alpha zip from the
website and unpack it in texmf-context.
This is just a test.
% \enabletrackers[structure.notes]
\setupnote
[footnote][paragraph=yes,numbercommand=,inbetween=\hskip.5em\vl\hskip.5em]
\setupdescriptions[footnote][paragraph=no,location=serried,distance=.5em] %
before=,after=
\starttext
\startlocalfootnotes
local 1a\footnote{local note 1a}
local 1b\footnote{local note 1b}
\placelocalfootnotes
\stoplocalfootnotes
\blank
global 1a\footnote{global note 1a}
global 1b\footnote{global note 1b}
\blank
\startlocalfootnotes
local 2a\footnote{local note 2a}
local 2b\footnote{local note 2b}
\placelocalfootnotes
\stoplocalfootnotes
\blank
global 2a\footnote{global note 2a}
global 2b\footnote{global note 2b}
\blank
\startlocalfootnotes
local 3a\footnote{local note 3a}
local 3b\footnote{local note 3b}
\placelocalfootnotes
\stoplocalfootnotes
\blank
global 2a\footnote{\input tufte }
global 2b\footnote{global note 2b}
\blank
\stoptext
You need to be a bit tolerant with this mechanism. It uses the same
trick as in mkii, and you can find more about the trick used on pages
398 and 399 of the texbook.
The inbetween material cannot be too large. Also, the distance between
the text and footnotes should be large enough to catch a potential
overflow, although normally there is enough stretch in a paragraph.
(I can support ragged right if needed, but it would involve another trick.)
ps for Wolfgang: we need to discuss this at the context meeting. Maybe
we should have some predefined variants. As you're looking into
parameters (the cont-en.xml thing) ... we need to check those related to
notes and descriptions, as there are some subtle differences with mkii.
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2010-07-30 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 6:19 Markus Finke
2010-07-30 15:04 ` Markus Finke
2010-07-30 17:02 ` Hans Hagen
2010-07-30 21:59 ` Markus Finke
2010-07-30 22:28 ` 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=4C53521E.3060807@wxs.nl \
--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).