From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: typing+framedtext: different behaviour between TL2017 and 2019
Date: Fri, 17 Jan 2020 20:02:43 +0100 [thread overview]
Message-ID: <8BBD06C1-4BD3-4B0F-B999-895DE029F1AE@gmail.com> (raw)
In-Reply-To: <e7cf616f-d074-e4be-7361-c6a96f2029d0@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1759 bytes --]
Hi Wolfgang,
Indeed the sample sent by Tomas works fine with recent lmtx and mkiv, but with the mkiv version in TeXLive2019 one gets the result attached.
This means that Tomas has to update to a newer version of ConTeXt…
Best regards: OK
> On 17 Jan 2020, at 19:40, Wolfgang Schuster <wolfgang.schuster.lists@gmail.com> wrote:
>
> Tomas Hala schrieb am 17.01.2020 um 15:18:
>> 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.
>
> Your example works fine with the current beta and since you don't show the differences between the different installations there is nothing which can be done.
>
> Wolfgang
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
[-- Attachment #1.2.1: Type: text/html, Size: 651 bytes --]
[-- Attachment #1.2.2: typing-and-framedtext.pdf --]
[-- Type: application/pdf, Size: 7251 bytes --]
[-- Attachment #1.2.3: Type: text/html, Size: 2634 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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:[~2020-01-17 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 14:18 Tomas Hala
2020-01-17 18:40 ` Wolfgang Schuster
2020-01-17 19:02 ` Otared Kavian [this message]
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=8BBD06C1-4BD3-4B0F-B999-895DE029F1AE@gmail.com \
--to=otared@gmail.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).