November 2020 - ntg-context - NTG Mailing Lists

Units of xpart and ypart of a pair in MetaFun
by Keith McKay 27 Nov '20

27 Nov '20

Hi, I have been using xpart and ypart to extract these values from pairs of points in a path but I wasn't getting the correct result. I was expecting: pair (2cm, 11cm) to give xpart 2 and ypart 11 However I was getting: pair (2cm, 11cm) -> xpart 56.6929 and ypart 311.8096 After much head scratching and reading the MetaPost and MetaFun manuals, I realised that the units of xpart or ypart are in Postcript points or Big Points (bp), and 1 bp is 1/72 of an inch, and thus to get the values of xpart or ypart in cm I would have to use a correction factor. I had made the assumption that since the x and ypart in the pair was in cm that the result would be in cm, but I see now that this is not the case. Will I have to continue doing this or is there some magic within MetaFun which takes account of the units in a pair and outputs the result of x and ypart in the same units? The MWE belows shows what I have been doing. Thanks Keith McKay %%% MWE %%% \setuppapersize [A5, landscape][A4, portrait] \usecolors[crayola] \starttext \startMPpage StartPage; width := PaperWidth ; height := PaperHeight ; unit := cm ; numeric squig; pair a[]; a0 = (2cm,11cm); a1 = (4cm,10cm); a2 = (6cm,9cm); a3 = (8cm,8cm); show xpart a[0], ypart a[0]; %Example of result from x and ypart before applying correction factor (cf) % cf := 72/2.54; %Converts points/in to points/cm% path pp; for i = 0 step 1 until 3: pp := ((xpart a[i])/cf*cm, (ypart a[i])/cf*cm); for squig = 1 step 1 until 15: xcoord := uniformdeviate(1) - 0.5 + (xpart a[i]/cf); ycoord := uniformdeviate(1) - 0.5+ (ypart a[i]/cf); pp := pp .. {curl 100}(xcoord*cm, ycoord*cm); endfor; pp := pp --- cycle; if i < 3 : pp := pp --- ((xpart a[i+1]/cf)*cm, (ypart a[i+1])/cf*cm); fi; f :=((1.4 - 0.6) * uniformdeviate(1)) + 0.8; % Factor to lighten/darken colour % draw pp withpen pencircle xscaled 0.5mm yscaled .1mm rotated 45 withcolor (f[white,\MPcolor{BurntSienna}]); endfor; StopPage; \stopMPpage \stoptext %%%%%%%%%%%%%%

4 9

Testing for LMTX
by Jean-Philippe Rey 27 Nov '20

27 Nov '20

Dear list, I would like to determine if LMTX is being used. Mimicking system modes I tried \startmode[*lmtx] . . . \stopmode however, LMTX doesn't define this mode but apparently defines *mkiv. Do you know a way to distinguish between LMTX and MkIV ? Thank you, -- Jean-Philippe Rey jean-philippe.rey(a)centralesupelec.fr 91192 Gif-sur-Yvette Cedex - France Empreinte PGP : 807A 5B2C 69E4 D4B5 783A 428A 1B5E E83E 261B BF51

3 3

question about frames
by Pablo Rodriguez 26 Nov '20

26 Nov '20

Dear list, here is a minimal sample of frames to make up labels: \setuplayout[page] \starttext \dorecurse{16}{\dontleavehmode\dorecurse{4} {\framed[width=52.5mm, height=18.5mm, align=right]{\null}}\\} \stoptext Which is the way to avoid any vertical space between frames? Sorry, this may be obvious, but I don’t know how to do it now. Many thanks for your help, Pablo -- http://www.ousia.tk

4 5

Orphan issue with \startitemize
by Bruce Horrocks 26 Nov '20

26 Nov '20

With the following MWE: \def\Lorem{Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. } \showframe \starttext %\dorecurse{32}{ ~ \par } %\dorecurse{33}{ ~ \par } \dorecurse{34}{ ~ \par } The following items are blah blah blsh: \startitemize \sym{-} \Lorem \sym{-} \Lorem \sym{-} \Lorem \sym{-} \Lorem \stopitemize \stoptext I find that \dorecurse{32} fits two items on the bottom of the first page and two at the top of the next. This is fine. With \dorecurse{33} I get one and three - which is also fine. With \dorecurse{34} all of the items move to the second page even though only one extra line has been added and there is now quite a large gap at the bottom of the first page. Is there a setting that controls this a bit more precisely, please? (So that \dorecurse{34} and possibly even 35 would still split one and three.) -- Bruce Horrocks Hampshire, UK

2 1

Re: [NTG-context] question about frames
by Andres Conrado Montoya 26 Nov '20

26 Nov '20

Disregard that... that is the default... it doesn't work as I thought initially. Sorry for the noise.

1 0

Re: [NTG-context] question about frames
by Andres Conrado Montoya 26 Nov '20

26 Nov '20

A bit late to the party but maybe this helps... try "frameoffset": \defineframed[caja][frameoffset=\zeropoint,width=5cm,height=2cm] \starttext \dorecurse{5}{\caja[frame=on]{Hello}} \stoptext -- Andrés Conrado Montoya

1 0

Re: [NTG-context] Vertical space when surrounding with textbackground
by Johann Birnick 26 Nov '20

26 Nov '20

On Thu, 2020-11-26 at 19:39 +0100, Johann Birnick wrote: > On Thu, 2020-11-26 at 19:35 +0100, Wolfgang Schuster wrote: > > Johann Birnick schrieb am 26.11.2020 um 19:26: > > > I didn't want to copy paste it :D Just add [option=XML] to \starttext like > > > this: > > > > Why do pass a option for the typing environment to \starttext? > > > > > \definetextbackground[code][background=color, backgroundcolor=lightgray, > > > frame=off, location=paragraph] > > > > > > \setuptyping[before={\startbackground[code]}, after={\stopbackground}] > > > > > > \starttext[option=XML] > > > \starttyping > > > This is some code > > > a second line > > > \stoptyping > > > \stoptext > > > > > > When I use \definetyping[Mytyping][option=XML] and then use \startMytyping > > > ... > > > \stopMytyping nothing changes. > > ??? > > > > \definetextbackground > > [Code] > > [ frame=off, > > background=color, > > backgroundcolor=lightgray, > > location=paragraph] > > > > \definetyping > > [Mytyping] > > [option=XML] > > > > \setuptyping > > %[Mytyping] > > [before={\blank\starttextbackground[Code]}, > > after={\stoptextbackground\blank}] > > > > \starttext > > > > \startMytyping > > <empty/> > > \stopMytyping > > > > \starttyping[option=XML] > > <empty/> > > \stoptyping > > > > \stoptext > > > > Wolfgang > > > > Sorry for confusing \starttext with \starttyping. > > @Wolfgang this is exactly what I mean. It doesn't work. There is an extra line > at the end. If you remove [option=XML] it works. So what is going wrong? > > Thank you, > Johann Ah, sorry again. I use \usemodule[Scite] at the begin of the document. Removing this helps. But I need it for the C and Cpp pretty printer. So do you know what's going on with Scite module? Thanks, Johann

2 4

new upload
by Hans Hagen 26 Nov '20

26 Nov '20

Hi, A new upload. Mojca upgraded the build manager and we also updated some machines so all binaries (platforms) should be in sync now. (No binaries for apples M1 and microsofts SQ2 as we don't have these machines, so just good old intel and arm it is.) On my rusty laptop the luametatex manual takes between 10 and 10.5 sec (depending on load). On the raspberry pi 64 bit it takes 32.5 sec (ubuntu, ssd on usb 3). The Windows Linux Subsystem (version 1) takes some 11.5 seconds and the domotica fitlet with a low power AMD A10 needs 27.5 sec.) The ratios match measurements of a while ago. In the meantime the format file got smaller, memory more dynamic and the mem footprint also smaller. I expect a modern intel laptop cpu to need some 5 seconds and a decent desktop less but who knows. It's not easy to squeeze out more (the bottleneck is in the lua code as the (con)tex(t) code is pretty efficient so we pay a price for flexibility). (In the process I saw that I bugged the xetex logo but that has to wait for a next upload. Hardly critital I suspect.) 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 -----------------------------------------------------------------

7 13

Vertical space when surrounding with textbackground
by Johann Birnick 26 Nov '20

26 Nov '20

Hi there, in my document(s) I have enumerations (created with \defineenumeration) and "typing"s (created with \definetyping) and I need to give a specific layout to them. In particular, I want to add textbackground (created with \definetextbackground) and sometimes a sidebar (created with \definesidebar) to them. However, when I surround for example my typing with a textbackground like this \starttextbackground[code] \startCpp ... \stopCpp \stoptextbackground or by putting the textbackground commands in "before=" and "after=" of my typing, then there will be an additional empty line at the end of the typing. Same with the enumerations and when I surround it with a sidebar instead of a textbackground. Often there is even an additional line / additional space before the typing/enumeration. How to surround such things properly? I just want a background to these and a sidebar. No addition spacing / empty lines. I would greatly appreciate your help. Thank you, Johann

3 10

Strange bug with obayspaces and tagging
by Christoph Reller 26 Nov '20

26 Nov '20

Hi, With the currently latest version of ConTeXt LMTX 2020.11.25 21:42, this MNWE fails with the following error message: ---- \setuptagging[state=start] \starttext \obeyspaces\obeylines patch \stoptext ---- tex error > tex error on line 4 in file ./scratch1.tex: Valid keyword expected, likely 'plus' <line 3.4> pa tch 1 \setuptagging[state=start] 2 \starttext 3 \obeyspaces\obeylines 4 >> patch 5 \stoptext ---- This may be a bug in the tagging feature. Cheers, Christoph

2 1