Re: [NTG-context] typing+framedtext: different behaviour between TL2017 and 2019

2020-01-17 Thread Tomas Hala 

# # 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
___

Re: [NTG-context] typing+framedtext: different behaviour between TL2017 and 2019

2020-01-17 Thread Tomas Hala 

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
___

Re: [NTG-context] typing+framedtext: different behaviour between TL2017 and 2019

2020-01-17 Thread Wolfgang Schuster 

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
___

Re: [NTG-context] typing+framedtext: different behaviour between TL2017 and 2019

2020-01-17 Thread Tomas Hala 
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


typing-tl17.pdf
Description: Adobe PDF document


typing-tl19.pdf
Description: Adobe PDF document
___
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
___

Re: [NTG-context] typing+framedtext: different behaviour between TL2017 and 2019

2020-01-17 Thread Otared Kavian 
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

typing-and-framedtext.pdf
Description: Adobe PDF document
On 17 Jan 2020, at 19:40, Wolfgang Schuster  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="" class="">\setuptyping[MP][before={\startMPT},after={\stopMPT},]\startMP bla \stopMP\stoptextNow 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 environmentas 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-contextwebpage  : http://www.pragma-ade.nl / http://context.aanhet.netarchive  : https://bitbucket.org/phg/context-mirror/commits/wiki : http://contextgarden.net__
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
___

Re: [NTG-context] typing+framedtext: different behaviour between TL2017 and 2019

2020-01-17 Thread Wolfgang Schuster 

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
___

[NTG-context] typing+framedtext: different behaviour between TL2017 and 2019

2020-01-17 Thread Tomas Hala 
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
___