From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: (critical edition) nesting linenotes
Date: Mon, 18 Nov 2013 23:25:54 +0100 [thread overview]
Message-ID: <528A93F2.8060803@wxs.nl> (raw)
In-Reply-To: <528A709A.3020902@gmx.es>
On 11/18/2013 8:55 PM, Pablo Rodriguez wrote:
> 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?
you need to separate cases:
(1) some macro that uses grouping with nested notes
(2) hyphenation
here is an example of the first case
\setuppapersize
[A8][A7]
\setuplayout
[location=middle]
\unexpanded\def\doCritApp#1#2#3%
{\startlinenote[#1]{#2 #3}(#2)\stoplinenote[#1]}
\newcounter\MyCounter
\unexpanded\def\CritApp
{\doglobal\increment\MyCounter
\normalexpanded{\doCritApp{Varia:\MyCounter}}}
% \setupnotes[linenote][split=verystrict,scope=page]
\starttext
\startlinenumbering
\startlinenote[one]{note one}
one one one one one one one one one one one one one one one
\startlinenote[two]{note two}
two two two two two two two
\stoplinenote[two]
one one one one one one one one one one one one one one one
\stoplinenote[one]
\par
\CritApp
{(one one one one one one)
\CritApp
{(two two)}
{two two two two two two}
(one one one one one one)}
{one one one one one one}
\stoplinenumbering
\stoptext
so, in your macro you need to make sure that the counter (1) gets
incremented global and (2) gets expanded in time.
Hans
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-11-18 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 19:55 Pablo Rodriguez
2013-11-18 22:25 ` Hans Hagen [this message]
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=528A93F2.8060803@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).