ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Tomas Hala <tomas.hala@mendelu.cz>
To: Mailing list ConTeXt <ntg-context@ntg.nl>
Subject: typing+framedtext: different behaviour between TL2017 and 2019
Date: Fri, 17 Jan 2020 15:18:55 +0100	[thread overview]
Message-ID: <20200117141855.GB18700@akela.mendelu.cz> (raw)

Hi all,

if I compile the following (minimised) code with ConTeXt from TL2017,
I receive expected result -- one framed gray box with correct width.

\starttext\showframe
\defineframedtext[MPT][background=color,backgroundcolor=gray,width=\makeupwidth,frame=on,offset=1cc,]
\setuptyping[MP][before={\startMPT},after={\stopMPT},]
\startMP bla \stopMP
\stoptext

Now I tried it with ConTeXt from TL2019 (TL2018 produces the same result as TL2019)
and I have got _two_ boxes -- the outer one is correct and frames the typing environment
as in the past whereas the new box frames the text inside the typing.

Unfortunately, both boxes seems to be controlled by the \defineframedtext[MPT]
which caused that the inner box runs outside the typesetting area, i.e. the
left offset value is applied twice.

I found out that it is related with the given name MP.
Therefore, I renamed it to another name (it was ok) but after adding
"option=mp" I came across the same problem.

Is there any way how to define behaviour of both boxes in the existing \startMP
environment apart? Or is it not possible?

Best wishes,

Tomáš
___________________________________________________________________________________
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
___________________________________________________________________________________

             reply	other threads:[~2020-01-17 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 14:18 Tomas Hala [this message]
2020-01-17 18:40 ` Wolfgang Schuster
2020-01-17 19:02   ` Otared Kavian
2020-01-17 19:32   ` Tomas Hala
2020-01-17 19:48     ` Wolfgang Schuster
2020-01-17 20:15       ` Tomas Hala
2020-01-17 22:04         ` Tomas Hala

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=20200117141855.GB18700@akela.mendelu.cz \
    --to=tomas.hala@mendelu.cz \
    --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).