Re: [NTG-context] mwe (font proble) SOLVED

2021-11-14 Thread Henning Hraban Ramm via ntg-context

> Am 15.11.2021 um 04:34 schrieb Aditya Mahajan via ntg-context 
> :
> 
> On Sun, 14 Nov 2021, skyhorse--- via ntg-context wrote:
> 
>> 
>> Solved.  Well almost.  I do know that it's an access problem of some sort.
>> I used 'font-manager' to look at fonts and it showed  'DejaVu Math Tex Gyre' 
>> as "disabled"
>> For su is shows the font as usable.
>> When context is run su, it compiles successfully.
>> So the fonts are there.  The example does work, but, not for me as user.
>> I for some reason have the some fonts disabled.
>> I'll figure out how to enable them.
> 
> Most likely, you installed context using `su` or `sudo`. It is possible that 
> the directory where the fonts are installed are not readable by the user. 
> 
> The simple work-around is to install context as a regular user so that you 
> have the permissions to read the font files.

... or at least open permissions.

I could imagine the real culprit is the cache tree (i.e. its permissions).

Hraban
___
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] Paragraph break over pages with hanging float

2021-11-14 Thread Adam Reviczky via ntg-context
Hi,

Is there a way to allow a paragraph to break over two pages (between the
paragraph start and the placement of the float) with a hanging float
further down the paragraph?

MWE:

\starttext
\input lorem
\blank[20*line]

% commenting out the hanging float allows paragraph break
\startplacefigure[location={right,15*hang}]
\framed[width=3cm,height=2cm]{graphic}
\stopplacefigure

\dorecurse{10}{\input lorem}
\stoptext

When I remove the hanging float, the paragraph is broken down at the first
pagebreak.
With the float, the paragraph starts always on the next page, regardless of
the space left on the previous page.

Adam
___
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] directsetup vs setups

2021-11-14 Thread Rik Kabel via ntg-context

Hello list,

Can anyone provide a description of, or a point to a description of, the 
differences between setups= and directsetup= for including setups? I 
searched the list archive and the documents and found nothing. (That may 
indicate my level of search foo, but nonetheless I am in need of help 
with this.)


--
Rik

___
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] mwe (font proble) SOLVED

2021-11-14 Thread Aditya Mahajan via ntg-context
On Sun, 14 Nov 2021, skyhorse--- via ntg-context wrote:

> 
> Solved.  Well almost.  I do know that it's an access problem of some sort.
> I used 'font-manager' to look at fonts and it showed  'DejaVu Math Tex Gyre' 
> as "disabled"
> For su is shows the font as usable.
> When context is run su, it compiles successfully.
> So the fonts are there.  The example does work, but, not for me as user.
> I for some reason have the some fonts disabled.
> I'll figure out how to enable them.

Most likely, you installed context using `su` or `sudo`. It is possible that 
the directory where the fonts are installed are not readable by the user. 

The simple work-around is to install context as a regular user so that you have 
the permissions to read the font files.

Aditya
___
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] Bug in lmt_arrow

2021-11-14 Thread Aditya Mahajan via ntg-context
On Sun, 14 Nov 2021, Aditya Mahajan via ntg-context wrote:

> On Sun, 14 Nov 2021, Hans Hagen wrote:
> 
> > On 11/14/2021 4:33 AM, Aditya Mahajan via ntg-context wrote:
> > > Hi,
> > > 
> > > There is a bug in lmt_arrow. If given a "non-cycle" path, lmt_arrow
> > > completes the cycle.
> > > 
> > >  \starttext
> > > 
> > >  \startMPcode
> > >newpath p;
> > >ahfactor := 5;
> > >p := origin .. (1cm, 1cm) .. (2cm, 0);
> > >draw lmt_arrow
> > > [
> > >   path = p,
> > >   location = "percentage",
> > >   percentage = 50,
> > >   alternative = "curved",
> > > ]
> > > withpen pencircle scaled 1bp;
> > >  \stopMPcode
> > >  \stoptext
> > > 
> > > With 2021.11.11, I get the attached file. Note that lmt_arrow has drawn 
> > > the
> > > "cycle" version of the path, even though p does not have a cycle.
> > > 
> > > I have looked at the code and cannot figure out why this is happening.
> > 
> > it happens in the 'direct' variant (metapost.registerdirect) where a boolean
> > is passed as signal and that boolean then is also picked up by the (shared)
> > path injector as (old school) signal that a path is closed while it should
> > instead consutl the closed field in a path table (sounds more complex than 
> > it
> > is)
> > 
> > so in the end it is a nasty side effect of the fast inject code path (shared
> > function with different stack values; i'll probably have to ditch a "low 
> > level
> > backward compatibility feature no one uses anyway" some day)
> > 
> > i uploaded a fix that you can test when the bins are compiled at
> > 
> > https://build.contextgarden.net/#/waterfall?tags=c.luametatex
> > 
> > new bins then in:
> > 
> > https://dl.contextgarden.net/build/luametatex/
> > 
> > (fyi: in the mp code you see that the path p is 'get' from the lua end where
> > it got passed to by parameter)
> 
> Thanks! Works perfectly here.

Spoke too soon. Now straight lines don't work:

\starttext

\startMPcode
  newpath p;
  ahfactor := 5;
  p := origin .. (3cm,0);
  draw lmt_arrow
   [
 path = p, 
 location = "percentage",
 percentage = 50,
 alternative = "curved", 
   ]
   withpen pencircle scaled 1bp;
\stopMPcode
\stoptext


gives

metapost> trace > This is MPLIB for LuaMetaTeX, version 3.11, running 
in scaled mode.
metapost> trace > 
metapost> trace > loading metafun for lmtx, including the plain 1.004 
base definitions
metapost> trace > 
metafun > log >
metafun > log > error: This can't happen (division by zero)
metafun > log >
metapost> trace >  arrowhead ->  -> 
begingroup.save.q,e,r;pair.e;e=point.length(EXPR2)of(EXPR2);path.q;q=gobble((EXPR2)shifted-e.cutafter.makepath(pencircle.scaled(2ahlength)))cuttings;if.ahvariant>0:path.r;r=gobble((EXPR2)shifted-e.cutafter.makepath(pencircle.scaled((1-ahdimple)*2ahlength)))cuttings;fi(q.rotated(ahangle/2)(ahangle/2)if.ahvariant=1:--point0of.r--elseif.ahvariant=2:...point0of.r...else:--fi.cycle)shifted.e.endgroup
metapost> trace >  endgroup
metapost> trace >  pushparameters "arrow" ; save a ; string a 
; a := getparameter "alternative" ; save l ; string l ; l := getparameter 
"location" ; save k ; string k ; k := getparameter "kind" ; save p ; path p ; p 
:= getparameter "path" ; interim ahvariant := if a = "dimpled" : 1 elseif a = 
"curved" : 2 else : 0 fi ; interim ahdimple := getparameter "dimple" ; interim 
ahscale := getparameter "scale" ; interim ahangle := getparameter "angle" ; 
interim ahlength := getparameter "length" ; if not getparameter "headonly" : 
draw p ; fi ; if hasparameter "pen" : if hasoption "pen" "auto" : ahlength := ( 
getparameter "penscale" ) * boundingradius ( currentpen ) ; else : ahlength := 
( getparameter "penscale" ) * boundingradius ( getparameterpen "pen" ) ; fi ; 
fi ; if k = "draw" : draw elseif k = "both" : filldraw else : fill fi if l = 
"middle" : midarrowhead p ; elseif l = "percentage" : arrowheadonpath ( p , ( 
getparameter "percentage" ) / 100 ) ; elseif l = "both" : arrowhead p ; if k = 
"draw" : draw elseif k = "both" : filldraw else : fill fi arrowhead reverse p ; 
else : arrowhead p ; fi ; popparameters ;
metapost> trace >  image -> (TEXT3)-> 
begingroup.save.currentpicture;picture.currentpicture;currentpicture:=nullpicture;(TEXT3);currentpicture.if.str(SUFFIX2)<>"":shifted(mfun_labxf(SUFFIX2)*lrcorner.p+mfun_labyf(SUFFIX2)*ulcorner.p+(1-mfun_labxf(SUFFIX2)-mfun_labyf(SUFFIX2))*llcorner.p)fi.endgroup
metapost> trace >  lmt_do_arrow -> -> 

Re: [NTG-context] Bug in lmt_arrow

2021-11-14 Thread Aditya Mahajan via ntg-context
On Sun, 14 Nov 2021, Hans Hagen wrote:

> On 11/14/2021 4:33 AM, Aditya Mahajan via ntg-context wrote:
> > Hi,
> > 
> > There is a bug in lmt_arrow. If given a "non-cycle" path, lmt_arrow
> > completes the cycle.
> > 
> >  \starttext
> > 
> >  \startMPcode
> >newpath p;
> >ahfactor := 5;
> >p := origin .. (1cm, 1cm) .. (2cm, 0);
> >draw lmt_arrow
> > [
> >   path = p,
> >   location = "percentage",
> >   percentage = 50,
> >   alternative = "curved",
> > ]
> > withpen pencircle scaled 1bp;
> >  \stopMPcode
> >  \stoptext
> > 
> > With 2021.11.11, I get the attached file. Note that lmt_arrow has drawn the
> > "cycle" version of the path, even though p does not have a cycle.
> > 
> > I have looked at the code and cannot figure out why this is happening.
> 
> it happens in the 'direct' variant (metapost.registerdirect) where a boolean
> is passed as signal and that boolean then is also picked up by the (shared)
> path injector as (old school) signal that a path is closed while it should
> instead consutl the closed field in a path table (sounds more complex than it
> is)
> 
> so in the end it is a nasty side effect of the fast inject code path (shared
> function with different stack values; i'll probably have to ditch a "low level
> backward compatibility feature no one uses anyway" some day)
> 
> i uploaded a fix that you can test when the bins are compiled at
> 
>   https://build.contextgarden.net/#/waterfall?tags=c.luametatex
> 
> new bins then in:
> 
>   https://dl.contextgarden.net/build/luametatex/
> 
> (fyi: in the mp code you see that the path p is 'get' from the lua end where
> it got passed to by parameter)

Thanks! Works perfectly here.

> (interesting that it didn't show up sooner, maybe most users have closed paths
> and/or most lmt_ features used closed paths)

I was reusing two year old code and took me a while to figure out why the 
output was suddenly wrong. 

Aditya
___
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] mwe (font proble) SOLVED

2021-11-14 Thread skyhorse--- via ntg-context

Solved.  Well almost.  I do know that it's an access problem of some sort.
I used 'font-manager' to look at fonts and it showed  'DejaVu Math Tex Gyre' as 
"disabled"
For su is shows the font as usable.
When context is run su, it compiles successfully.
So the fonts are there.  The example does work, but, not for me as user.
I for some reason have the some fonts disabled.
I'll figure out how to enable them.

Thank you all for your time.  I'll post back when I know what to do in case any 
future user has this problem.

Thank you

Hans Hagen via ntg-context  wrote:

> On 11/14/2021 12:26 AM, skyhorse--- via ntg-context wrote:
> > Here is the minium not-working example which I took from the
> > Wikigarden a few minutes ago.
> >
> > \def\T#1{%
> >\startitemize[#1,joinedup]
> >  \item This is a bullet of type #1.
> >\stopitemize
> > }
> > \starttext
> >\dorecurse{9}{\T\recurselevel}
> > \stoptext
> >
> > Compiling this into a pdf file with context produces an error.
> > I've pasted the complete context typesetting run to show the error, in 
> > hopes that it will shed some light on what's wrong with my setup.   I have 
> > a feeling that the stand along install is missing some vital part of the 
> > installation regarding fonts, and that it's not noticed by the majority of 
> > you since those items are still on your system from legacy versions.
> nornally it means that you have no math font loaded (i.e. you do
> something before \starttext
>
> Hans
>
>
>
> -
>   Hans Hagen | PRAGMA ADE
>   Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -
> ___
> 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
> ___
___
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] minimum working example plus (output)

2021-11-14 Thread Wolfgang Schuster via ntg-context

skyhorse--- via ntg-context schrieb am 14.11.2021 um 21:13:

Hans Hagen via ntg-context  wrote:


On 11/14/2021 12:26 AM, skyhorse--- via ntg-context wrote:

Here is the minium example which I took from the
Wikigarden a few minutes ago.

\def\T#1{%
\startitemize[#1,joinedup]
  \item This is a bullet of type #1.
\stopitemize
}
\starttext
\dorecurse{9}{\T\recurselevel}
\stoptext

Compiling this into a pdf file with context produces an error.
I've pasted the complete context typesetting run to show the error, in hopes 
that it will shed some light on what's wrong with my setup.   I have a feeling 
that the stand along install is missing some vital part of the installation 
regarding fonts, and that it's not noticed by the majority of you since those 
items are still on your system from legacy versions.

nornally it means that you have no math font loaded (i.e. you do
something before \starttext

Hans

Nothing is done before the sample shown above.That is all that is in the 
.lmtx source file.

 From looking at the errors, I agree, it looks like there are no math fonts or, 
they are not visiable to context.

I need advice on how I can remedy that.
What do I need and what do I need to do to install them if I don't have them 
already on disk.
I assume that they are not distributed with the   shelll script.


Can you delete the tex folder in your installation and try to download 
the files again.


When the script runs take a look at the terminal if you can see the 
following lines where the two zip files texmf.zip and texmf-context.zip 
are loaded. The first zip files contains all font files which are needed 
for your document.


sh install.sh
[...]
mtx-install | server   : lmtx.pragma-ade.com
mtx-install | instance : install-lmtx
mtx-install | platform : linux-64
mtx-install | system   : unix
mtx-install | fetching 
'http://lmtx.pragma-ade.com/install-lmtx//texmf.zip'

mtx-install | unzipping 'texmf.zip'
[...]
mtx-install | fetching 
'http://lmtx.pragma-ade.com/install-lmtx//texmf-context.zip'

mtx-install | unzipping 'texmf-context.zip'

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] minimum working example plus (output)

2021-11-14 Thread skyhorse--- via ntg-context
Hans Hagen via ntg-context  wrote:

> On 11/14/2021 12:26 AM, skyhorse--- via ntg-context wrote:
> > Here is the minium example which I took from the
> > Wikigarden a few minutes ago.
> >
> > \def\T#1{%
> >\startitemize[#1,joinedup]
> >  \item This is a bullet of type #1.
> >\stopitemize
> > }
> > \starttext
> >\dorecurse{9}{\T\recurselevel}
> > \stoptext
> >
> > Compiling this into a pdf file with context produces an error.
> > I've pasted the complete context typesetting run to show the error, in 
> > hopes that it will shed some light on what's wrong with my setup.   I have 
> > a feeling that the stand along install is missing some vital part of the 
> > installation regarding fonts, and that it's not noticed by the majority of 
> > you since those items are still on your system from legacy versions.
>
> nornally it means that you have no math font loaded (i.e. you do
> something before \starttext
>
> Hans

Nothing is done before the sample shown above.That is all that is in the 
.lmtx source file.

From looking at the errors, I agree, it looks like there are no math fonts or, 
they are not visiable to context.

I need advice on how I can remedy that.
What do I need and what do I need to do to install them if I don't have them 
already on disk.
I assume that they are not distributed with the   shelll script.


Thanks
___
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] minimum working example plus (output)

2021-11-14 Thread Hans Hagen via ntg-context

On 11/14/2021 12:26 AM, skyhorse--- via ntg-context wrote:


Here is the minium not-working example which I took from the Wikigarden a few 
minutes ago.


\def\T#1{%
   \startitemize[#1,joinedup]
 \item This is a bullet of type #1.
   \stopitemize
}

\starttext
   \dorecurse{9}{\T\recurselevel}
\stoptext



Compiling this into a pdf file with context produces an error.
I've pasted the complete context typesetting run to show the error, in hopes 
that it will shed some light on what's wrong with my setup.   I have a feeling 
that the stand along install is missing some vital part of the installation 
regarding fonts, and that it's not noticed by the majority of you since those 
items are still on your system from legacy versions.
nornally it means that you have no math font loaded (i.e. you do 
something before \starttext


Hans



-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
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] Bug in lmt_arrow

2021-11-14 Thread Hans Hagen via ntg-context

On 11/14/2021 4:33 AM, Aditya Mahajan via ntg-context wrote:

Hi,

There is a bug in lmt_arrow. If given a "non-cycle" path, lmt_arrow completes 
the cycle.

 \starttext

 \startMPcode
   newpath p;
   ahfactor := 5;
   p := origin .. (1cm, 1cm) .. (2cm, 0);
   draw lmt_arrow
[
  path = p,
  location = "percentage",
  percentage = 50,
  alternative = "curved",
]
withpen pencircle scaled 1bp;
 \stopMPcode
 \stoptext

With 2021.11.11, I get the attached file. Note that lmt_arrow has drawn the 
"cycle" version of the path, even though p does not have a cycle.

I have looked at the code and cannot figure out why this is happening.


it happens in the 'direct' variant (metapost.registerdirect) where a 
boolean is passed as signal and that boolean then is also picked up by 
the (shared) path injector as (old school) signal that a path is closed 
while it should instead consutl the closed field in a path table (sounds 
more complex than it is)


so in the end it is a nasty side effect of the fast inject code path 
(shared function with different stack values; i'll probably have to 
ditch a "low level backward compatibility feature no one uses anyway" 
some day)


i uploaded a fix that you can test when the bins are compiled at

https://build.contextgarden.net/#/waterfall?tags=c.luametatex

new bins then in:

https://dl.contextgarden.net/build/luametatex/

(fyi: in the mp code you see that the path p is 'get' from the lua end 
where it got passed to by parameter)


(interesting that it didn't show up sooner, maybe most users have closed 
paths and/or most lmt_ features used closed paths)


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
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
___