From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: (critical edition) nesting linenotes
Date: Mon, 18 Nov 2013 20:55:06 +0100 [thread overview]
Message-ID: <528A709A.3020902@gmx.es> (raw)
Dear Thomas, Luigi and Hans,
my second sample might be related to the first one. But I’m not sure it
is a bug.
Here is the code:
\setuppapersize[A8]
\newcounter\MyCounter
\def\CritApp#1#2{\increment\MyCounter%
\startlinenote[Varia:\MyCounter]{#1] #2}#1%
\prewordbreak\stoplinenote[Varia:\MyCounter]}
\starttext
\startlinenumbering
\startlinenote[one]{hyphenated}this is a test on
\startlinenote[two]{with nested
linenote}hyphenation\prewordbreak\stoplinenote[two]\stoplinenote[one]
\CritApp{this is a test on \CritApp{hyphenation}{nested linenote: bad
line number}}{not hyphenated}
\stoplinenumbering
\stoptext
A command such as \CritApp above is intended to generate all linenote
references automagically.
It works fine, but I cannot nest \CritApp linenotes. The problem is in
within this line:
\startlinenote[Varia:\MyCounter]{#1] #2}#1%
If I replace "{#1] #2}#1" with {#2}#1, nesting \CritApp linenotes,
everything works as expected.
Is this a bug?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2013-11-18 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 19:55 Pablo Rodriguez [this message]
2013-11-18 22:25 ` Hans Hagen
2013-11-19 16:48 ` Pablo Rodriguez
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=528A709A.3020902@gmx.es \
--to=oinos@gmx.es \
--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).