From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: Labels and Enumerations
Date: Sun, 14 Jan 2018 20:59:53 -0500 [thread overview]
Message-ID: <75e88f11-b24d-0b42-caf6-0fe49cee45b0@rik.users.panix.com> (raw)
In-Reply-To: <ad1195fa-eded-e3a0-1659-685ab0292ff2@rik.users.panix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1589 bytes --]
Further experimentation suggests that the problem is in the interaction
between footnotes and margin placement. Endnotes work fine.
\defineconstructionalternative
[mylabel]
[renderingsetup=constructionrenderings:mylabel,
width=]
\startsetups[constructionrenderings:mylabel]
\dontleavehmode
\inright{\flushconstructionheadbox}
\stopsetups
\defineenumeration
[one]
[alternative=mylabel,
display=no,
before=,
after=]
\definenote
[endnote]
\setupnotation
[endnote]
[way=bytext,
location=none,
conversion=numbers]
\starttext
\startchapter[title=bar]
this works \startone[reference=aa]\input jojomayer \stopone
\quotation{\startone[reference=bb]\input ward \stopone}
this fails\footnote{\startone[reference=cc]\input jojomayer
\stopone
\quotation{\startone[reference=dd]\input ward \stopone}}
while this works\endnote{\startone[reference=ee]\input
jojomayer \stopone
\quotation{\startone[reference=ff]\input ward \stopone}}
whatever \in{one}[aa] whatever \in{one}[bb]
whatever \in{one}[cc] whatever \in{one}[dd]
whatever \in{one}[ee] whatever \in{one}[ff]
\stopchapter
\startchapter[title=notes]
\placenotes[endnote]
\stopchapter
\stoptext
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 2333 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-01-15 1:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 21:17 Rik Kabel
2018-01-13 22:14 ` Alan Braslau
2018-01-14 14:46 ` Hans Hagen
2018-01-14 20:37 ` Rik Kabel
2018-01-15 1:59 ` Rik Kabel [this message]
2018-01-15 8:09 ` Hans Hagen
2018-01-15 21:15 ` Rik Kabel
2018-01-16 8:21 ` Hans Hagen
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=75e88f11-b24d-0b42-caf6-0fe49cee45b0@rik.users.panix.com \
--to=context@rik.users.panix.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).