January 2021 - ntg-context - NTG Mailing Lists

About baseline alignment in metapost
by Garulfo 29 Jan '21

29 Jan '21

To align with the baseline : thetextext.drt("Hello, World!", (1cm, 5cm)) ; Also existing : thetextext.d (center) thetextext.dlft (left)

3 3

code 139
by Thomas A. Schmitz 29 Jan '21

29 Jan '21

Hi all, a complex file with a metafun background does not compile anymore with lmtx. It compiles fine with mkiv. Compilation breaks off after 10 pages (maybe that's significant) with this message: pages > flushing realpage 10, userpage 10, subpage 10 mtx-context | fatal error: return code: 139 What is code: 139? Where should I start looking for the culprit? All best Thomas

3 7

About baseline alignment in metapost
by Stefan Nedeljkovic 28 Jan '21

28 Jan '21

Dear list, Consider the following example: \definepapersize [custom] [width=20cm, height=15cm] \setuppapersize [custom] \setuplayout [ width=fit, rightmargin=0cm, leftmargin=0cm, leftmargindistance=0pt, rightmargindistance=0pt, height=fit, header=0pt, footer=0pt, topspace=0cm, backspace=0cm, bottomspace=0cm, bottom=0pt, location=singlesided] \setuppagenumbering[location=] \startMPpage StartPage ; width := PaperWidth ; height := PaperHeight ; unit := cm ; drawoptions(withpen pencircle scaled .2pt withcolor .8white) ; draw vlingrid(0, width /unit, 1/10, width, height) ; draw hlingrid(0, height/unit, 1/10, height, width ) ; drawoptions(withpen pencircle scaled .5pt withcolor .4white) ; draw vlingrid(0, width /unit, 1, width, height) ; draw hlingrid(0, height/unit, 1, height, width ) ; draw thetextext.origin("Hello, World!", (1cm, 5cm)) ; StopPage ; \stopMPpage I want to position the text "Hello, World!" such that the vertical coordinate of the text origin is at the baseline, but the output seems to be the same even if I use "thetextext.raw" (note how the output changes if I remove the comma from the text). Also, how would I go about setting the origin on the right side? Kind regards, Stefan

1 0

Re: [NTG-context] possible problem with MPinstance or MPinclusions? works in 20200920 but not in the current 20210124 ...
by Hans Hagen 28 Jan '21

28 Jan '21

On 1/27/2021 3:08 PM, Rudd, Kevin wrote: > thanks, Hans--- > > with the only change being the lmtx release, I get: > > in 2020.09.20: > > resolvers > tex > 'file' closer: > '/local/Software/lmtx/tex/texmf-context/metapost/context/base/mpiv/metafun.mpxl' > closed > metapost > log > > resolvers > methods > resolving, method 'finders', how 'uri', > handler 'file', argument 'boxrow.mp' > > in 2021.01.24: > > resolvers > tex > 'file' closer: > '/local/Software/lmtx/tex/texmf-context/metapost/context/base/mpxl/metafun.mpxl' > closed > metafun > log > > metafun > log > error: Not implemented: (unknown > numeric)=(string) > > thus the MPincludes block doesn't seem to be processed in the latest > release so the option block doesn't get grokked properly. the log files > are attached with all of the gory details; if they don't make it, I can > send separately. but how does the tex/.mp file look ... in the log you can see that there is no attempt to read boxrow.mp at all ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

1 0

understanding \startTEXpage
by Peter Münster 28 Jan '21

28 Jan '21

Hi, According to https://wiki.contextgarden.net/Command/startTEXpage it "starts a page that fits its contents exactly". But it seems, that part of the content is cropped here: \startTEXpage X \hskip20cm X \stopTEXpage No problem with 10cm instead of 20cm... Is this a bug or expected behaviour? TIA, -- Peter

2 1

--extra=combine no more working
by Peter Münster 27 Jan '21

27 Jan '21

Hi, The command "context --extra=combine file-1.pdf file-2.pdf" doesn't work any more with the latest version. Here is the output: --8<---------------cut here---------------start------------->8--- mtx-context | processing extra: /opt/context/tex/texmf-context/tex/context/base/mkiv/mtx-context-combine.tex resolvers | formats | executing runner 'run luametatex format': /opt/context/tex/texmf-linux-64/bin/luametatex --jobname="mtx-context-combine" --fmt=/opt/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt --lua=/opt/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui /opt/context/tex/texmf-context/tex/context/base/mkiv/mtx-context-combine.tex --c:currentrun=1 --c:extra="combine" --c:files="file-1.pdf,file-2.pdf" --c:fulljobname="/opt/context/tex/texmf-context/tex/context/base/mkiv/mtx-context-combine.tex" --c:input="/opt/context/tex/texmf-context/tex/context/base/mkiv/mtx-context-combine.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:purgeall --c:result="context-extra" --c:texmfbinpath="/opt/context/tex/texmf-linux-64/bin" open source > level 1, order 1, name '/opt/context/tex/texmf-context/tex/context/base/mkiv/mtx-context-combine.tex' system > system > ConTeXt ver: 2021.01.24 16:07 LMTX fmt: 2021.1.26 int: english/english system > system > 'cont-new.mkxl' loaded open source > level 2, order 2, name '/opt/context/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > beware: some patches loaded from cont-new.mkiv close source > level 2, order 2, name '/opt/context/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > files > jobname 'mtx-context-combine', input '/opt/context/tex/texmf-context/tex/context/base/mkiv/mtx-context-combine', result 'context-extra' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 2, order 3, name 'mtx-context-common.tex' close source > level 2, order 3, name 'mtx-context-common.tex' fonts > preloading latin modern fonts (second stage) fonts > 'fallback modern-designsize rm 12pt' is loaded mtx-context | fatal error: return code: 139 --8<---------------cut here---------------end--------------->8--- How could that be fixed please? TIA, -- Peter

2 4

possible problem with MPinstance or MPinclusions? works in 20200920 but not in the current 20210124 ...
by Rudd, Kevin 26 Jan '21

26 Jan '21

Hi--- I have a number of included figures that work in 20200920 but not in the current 20210124 version. There's a project structure that sets everything up but after that they are input as a figure: \startplacefigure[title={NS Hierarchy}, reference={f:ns-hierarchy}] \input ns_hierarchy \stopplacefigure and generate the error: metafun > log > error: Not implemented: (unknown numeric)=(string) metafun > log > metapost > log > metapost > log > <to be read again> metapost > log > , metapost > log > <*> make_BoxRow [ name = "Parent", metafun > log > metafun > log > I'm afraid I don't know how to apply that operation to that combination of types. Continue, and I'll return the second argument (see above) as the result of theoperation. metafun > log > metapost > log > label = "Parent Root Namespace", ]; ; >From triaging, it looks like the "boxrow.mp" file isn't being input by the current version from within the MPinclusions block associated with the MPinstance; the error appears to be spurious as a result of make_BoxRow not being defined and doesn't occur in the old version where the file is input. "boxrow.mp" is not in the same directory as the document but is in the configured through the usepath/usesubpath interface from an environment file. I can put together and share a runnable MWE set of files if this information is not complete enough to identify the problem. Here is the MWE that I used for the input figure file that demonstrates the problem. \defineMPinstance[ns_hier] [ format=metafun, extensions=yes, initializations=yes, method=double, ] \startMPinclusions{ns_hier} input boxrow \stopMPinclusions \startMPdefinitions{ns_hier} % nothing to see here.... \stopMPdefinitions \startMPcode{ns_hier} make_BoxRow [ name = "Parent", label = "Parent Root Namespace", ]; \stopMPcode Thanks for any feedback, ---K Kevin W. Rudd, Ph.D. CAPT, USN (Ret) Computer Architecture & Computer Engineering Advanced Computing Systems (ACS) Research Program Laboratory for Physical Sciences (LPS) 443-654-7878 kevin(a)lps.umd.edu<mailto:kevin@lps.umd.edu> Visiting Research Professor United States Naval Academy rudd(a)usna.edu<mailto:rudd@usna.edu>

2 4

Re: [NTG-context] fancybreak module
by Clyde Johnston 25 Jan '21

25 Jan '21

I just realized that \starbreak was one of my own macros (defined ages ago) so the MWE should be: \usemodule[fancybreak] \define\starbreak{ \fancybreak{ \strut\hfill\hfill\symbol[star]\hfill\symbol[star]\hfill\symbol[star]\hfill\ hfill\strut }} \starttext \input ward \starbreak \input ward \stoptext Sorry for the confusion. Clyde From: Clyde Johnston [mailto:clyde@johnston.name] Sent: Monday, January 25, 2021 6:46 PM To: mailing list for ConTeXt users (ntg-context(a)ntg.nl) Subject: fancybreak module I have finally gotten around to upgrading my ConTeXt installation to LTMX and found that the \starbreak command in the "fancybreak" module no longer works. \usemodule[fancybreak] \starttext \input ward \starbreak \input ward \stoptext Have I missed something about the LTMX changes? I was working in version 2018.07.02 14:39 but not in 2021.01.24 16:07. Regards, Clyde

2 7

Inline Fractions
by Johann Birnick 25 Jan '21

25 Jan '21

Recently inline fractions stopped working correctly. For example symbol spacing, sub-/superscripts, the line is too short,... You can see the 3 named problems and how they sometimes appear and sometimes not in this two fractions: \starttext $\frac{\sin(x)}{16 \pi \epsilon_0 c^2 m_e^2} \frac{\sin(x)}{\epsilon_0}$ \stoptext Compare the output between the current LMTX version with some old version. (I compared with mk4, because I had nothing else available. I don't know when bugs were introduced.) Best regards, Johann

2 1

fancybreak module
by Clyde Johnston 25 Jan '21

25 Jan '21

I have finally gotten around to upgrading my ConTeXt installation to LTMX and found that the \starbreak command in the "fancybreak" module no longer works. \usemodule[fancybreak] \starttext \input ward \starbreak \input ward \stoptext Have I missed something about the LTMX changes? I was working in version 2018.07.02 14:39 but not in 2021.01.24 16:07. Regards, Clyde

1 0