ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
* typing+framedtext: different behaviour between TL2017 and 2019
@ 2020-01-17 14:18 Tomas Hala
  2020-01-17 18:40 ` Wolfgang Schuster
  0 siblings, 1 reply; 7+ messages in thread
From: Tomas Hala @ 2020-01-17 14:18 UTC (permalink / raw)
  To: Mailing list ConTeXt

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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: typing+framedtext: different behaviour between TL2017 and 2019
  2020-01-17 14:18 typing+framedtext: different behaviour between TL2017 and 2019 Tomas Hala
@ 2020-01-17 18:40 ` Wolfgang Schuster
  2020-01-17 19:02   ` Otared Kavian
  2020-01-17 19:32   ` Tomas Hala
  0 siblings, 2 replies; 7+ messages in thread
From: Wolfgang Schuster @ 2020-01-17 18:40 UTC (permalink / raw)
  To: mailing list for ConTeXt users

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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: typing+framedtext: different behaviour between TL2017 and 2019
  2020-01-17 18:40 ` Wolfgang Schuster
@ 2020-01-17 19:02   ` Otared Kavian
  2020-01-17 19:32   ` Tomas Hala
  1 sibling, 0 replies; 7+ messages in thread
From: Otared Kavian @ 2020-01-17 19:02 UTC (permalink / raw)
  To: mailing list for ConTeXt users


[-- 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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: typing+framedtext: different behaviour between TL2017 and 2019
  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
  1 sibling, 1 reply; 7+ messages in thread
From: Tomas Hala @ 2020-01-17 19:32 UTC (permalink / raw)
  To: Wolfgang Schuster; +Cc: mailing list for ConTeXt users

[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

Hi Wolfgang, 

two files with the difference are attached.

I thought about the current beta -- it could be good way for me but 
unfortunately it does not suit for my students.

Tomáš

Fri, Jan 17, 2020 ve 07:40:57PM +0100 Wolfgang Schuster napsal(a):
# 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

[-- Attachment #2: typing-tl17.pdf --]
[-- Type: application/pdf, Size: 6580 bytes --]

[-- Attachment #3: typing-tl19.pdf --]
[-- Type: application/pdf, Size: 7303 bytes --]

[-- Attachment #4: 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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: typing+framedtext: different behaviour between TL2017 and 2019
  2020-01-17 19:32   ` Tomas Hala
@ 2020-01-17 19:48     ` Wolfgang Schuster
  2020-01-17 20:15       ` Tomas Hala
  0 siblings, 1 reply; 7+ messages in thread
From: Wolfgang Schuster @ 2020-01-17 19:48 UTC (permalink / raw)
  To: Tomas Hala; +Cc: mailing list for ConTeXt users

Tomas Hala schrieb am 17.01.2020 um 20:32:
> Hi Wolfgang,
>
> two files with the difference are attached.
>
> I thought about the current beta -- it could be good way for me but
> unfortunately it does not suit for my students.

This should fix it:

\setupstartstop
   [DefaultSnippet]
   [before=,
    after=,
    style=]

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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: typing+framedtext: different behaviour between TL2017 and 2019
  2020-01-17 19:48     ` Wolfgang Schuster
@ 2020-01-17 20:15       ` Tomas Hala
  2020-01-17 22:04         ` Tomas Hala
  0 siblings, 1 reply; 7+ messages in thread
From: Tomas Hala @ 2020-01-17 20:15 UTC (permalink / raw)
  To: Wolfgang Schuster; +Cc: mailing list for ConTeXt users


Fri, Jan 17, 2020 ve 08:48:47PM +0100 Wolfgang Schuster napsal(a):
# This should fix it:
# 
# \setupstartstop
#   [DefaultSnippet]
#   [before=,
#    after=,
#    style=]
# Wolfgang

Unfortunately not, I tried it in preamble (with no effect)
as well as after the \starttext (with no effect + text of parameters were pushed to the document).

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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: typing+framedtext: different behaviour between TL2017 and 2019
  2020-01-17 20:15       ` Tomas Hala
@ 2020-01-17 22:04         ` Tomas Hala
  0 siblings, 0 replies; 7+ messages in thread
From: Tomas Hala @ 2020-01-17 22:04 UTC (permalink / raw)
  To: Wolfgang Schuster; +Cc: mailing list for ConTeXt users


# # This should fix it:
# # \setupstartstop
# #   [DefaultSnippet]
# #   [before=,
# #    after=,
# #    style=]
# # Wolfgang
# 
# Unfortunately not, I tried it in preamble (with no effect)
# as well as after the \starttext (with no effect + text of parameters were pushed to the document).

Your code works, thank you for the help.

The no-effect-problem was caused by some invisible characters (0xc2a0)
inside, they disrupted the token processing.
 
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
___________________________________________________________________________________

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2020-01-17 22:04 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-17 14:18 typing+framedtext: different behaviour between TL2017 and 2019 Tomas Hala
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

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).