From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: line numbering within frame
Date: Fri, 24 Jan 2020 18:45:06 +0100 [thread overview]
Message-ID: <489CBBC7-2352-4C0F-9126-7FA0D480A235@uni-bonn.de> (raw)
In-Reply-To: <20200123114522.GA13455@akela.mendelu.cz>
> On 23. Jan 2020, at 12:45, Tomas Hala <tomas.hala@mendelu.cz> wrote:
>
> Hi Thomas,
>
> move definitions and setups for Three and Four before the use of \framed.
> (With TL2019 works.)
>
> Wishes,
>
> Tomáš
Thank you for the hint - we’re still waiting for an answer to Wolfgang’s bonus question. But I have continued testing and discovered what is certainly a bug. Here’s a new example:
\setbreakpoints [compound]
\definelinenumbering
[original]
[style=\tx\ss,distance=-1ex,step=5,location=inleft,start=10,color=darkred]
\definelinenumbering
[translation]
[style=\tx\ss,distance=-1ex,step=5,location=inleft,start=50,color=darkblue]
\starttext
\framed
[background=color,
backgroundcolor=gray,
align={normal},
frame=off,
loffset=6ex,
width=\textwidth,
foregroundstyle=\ss]
{\startlinenumbering[original]
\input knuth
\stoplinenumbering
\blank [line]
\startlinenumbering[translation]
\input klein
\stoplinenumbering}
\stoptext
If you compile it, you will see that the “color” key of the two defined linenumbering environments is not followed. If you comment out the first line \setbreakpoints [compound], you will get two colors, as expected. I leave it as an exercise for Hans and Wolfgang to explain what’s going on here :-)
Thomas
___________________________________________________________________________________
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:[~2020-01-24 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 10:54 Thomas A. Schmitz
2020-01-23 11:45 ` Tomas Hala
2020-01-23 21:32 ` Wolfgang Schuster
2020-01-23 21:53 ` Thomas A. Schmitz
2020-01-25 18:17 ` Wolfgang Schuster
2020-01-26 12:49 ` Thomas A. Schmitz
2020-01-24 17:45 ` Thomas A. Schmitz [this message]
2020-01-24 17:57 ` Tomas Hala
2020-01-24 19:06 ` Wolfgang Schuster
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=489CBBC7-2352-4C0F-9126-7FA0D480A235@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).