October 2021 - ntg-context - NTG Mailing Lists

MkIV missing?
by Henning Hraban Ramm 19 Oct '21

19 Oct '21

Hi, since a while, I can’t run MkIV any more, even after several runs of install.sh (and mtxrun --generate, of course). It’s the same on my Mac and my Linux laptop (of course the bin dir is different on the latter): $ context --version mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: /Users/hraban/lmtx/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2021.09.26 17:00 mtx-context | main context file: /Users/hraban/lmtx/tex/texmf-context/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2021.09.26 17:00 $ context --version --luatex mtx-context | redirect luametatex -> luatex: luatex --luaonly "/Users/hraban/lmtx/tex/texmf-osx-64/bin/mtxrun.lua" --script mtx-context --version --luatex --redirected mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua' $ which context /Users/hraban/lmtx/tex/texmf-osx-64/bin/context $ which luatex /Users/hraban/lmtx/tex/texmf-osx-64/bin/luatex $ luatex --version This is LuaTeX, Version 1.13.0 (TeX Live 2021) ... $ mtxrun --version mtxrun | ConTeXt TDS Runner Tool 1.32 mtxrun | source path I thought that was related to the server/provider move, but I guess it isn’t. It’s a bit annoying that install.sh leaves ~/lmtx/bin in the PATH, so that a call to mtxrun can’t find any configuration. Hraban

5 11

SVG not rendering correctly with LMTX and conversion=mp
by Jason Ross 18 Oct '21

18 Oct '21

The following MWE fails to render the text in the attached SVG properly: \starttext \externalfigure[test.svg][conversion=mp] \stoptext The axis labels, tick labels, and title are all incorrect. This file was generated with Matplotlib.

4 10

Compilation error with the new version of lmtx
by Fabrice Couvreur 17 Oct '21

17 Oct '21

Hi, The latest version of lmtx does not allow me to compile the following file although there was no problem before. Thank you Fabrice \startproduct[expertes-manual] \startfrontmatter \setuppagenumbering [location=] \definefont [ChapterTextStyle] [SansBold*default sa 2.2] \setuphead [title] [style=ChapterTextStyle, align=flushright] \setuplist [chapter] [style=bold, alternative=b, width=1em] \setuplist [section] [margin=1em, width=1.75em] \setuplist [subsection] [margin=2.75em, width=2em, distance=\spaceamount] \starttitle[title=Table des matières] \placelist [chapter,section,subsection] [criterium=all, interaction=all, alternative=c] \stoptitle \stopfrontmatter \startbodymatter \component[chapter_1] \component[chapter_2] \stopbodymatter \stopproduct ########################################################################## tex error > tex error on line 1 in file ./expertes.tex: Undefined control sequence \undefined <lua output> <to be read again> \relax <macro> \p_maxwidth \dostarttagged \t!listcontent \empty \clf_listtitle {\currentlist }\currentlistindex \relax \dostoptagged <macro> \strc_lists_limitated_text #1->\edef \p_maxwidth {\listparameter \c!maxwidth }\ifempty \p_maxwidth \listparameter \c!textcommand {#1} \else \listparameter \c!textcommand {\limitatetext {#1}\p_maxwidth {\splitsymbol {\listparameter \c!limittext }}}\fi <macro> \22>:140>:abc ...rence_attribute \v!text \strc_lists_set_style_color \c!textstyle \c!textcolor \v!text \the \t_lists_every_renderingtext \the \t_lists_every_renderingsynchronize \setstrut \begstrut \strc_lists_limitated_text \currentlistentrytitle \endstrut \en ... <macro> \currentlistextra ...\begingroup \ifempty \m_strc_list_alternative \edef \currentlistalternative {\listparameter \c!alternative }\else \let \currentlistalternative \m_strc_list_alternative \fi \directsetup {\listalternativeparameter \c!renderingsetup } \relax \endgr ... ... <line 3.41> alternative=c] 1 >> \startproduct[expertes-manual] 2 3 \startfrontmatter 4 5 \setuppagenumbering 6 [location=] 7 8 \definefont 9 [ChapterTextStyle] 10 [SansBold*default sa 2.2] 11 The control sequence at the end of the top line of your error message was never \def'ed. You can just continue as I'll forget about whatever was undefined. mtx-context | fatal error: return code: 256 TeX Output exited abnormally with code 1 at Sat Oct 16 19:28:21

2 1

Reading ConTeXt metadata values into Lua
by Ramkumar KB 17 Oct '21

17 Oct '21

Hello All, I was trying to read the value of '\totalnumberofpages' into lua to do something with it. As an example, see below. Now, as I understand it, my example would not work as TeX gets the first go at this and therefore the variable 'pages' is the string '\totalnumberofpages' and not the actual value itself. And Lua cannot process this "calculation". I tried to go thru the manual - *cld-mkiv.pdf *- in the distro but could not catch on how to read a metadata value (not print). I am sure that I am missing a small trick somewhere (or is it something more involved?). \startluacode function myFancyCalculations(pages) -- some fancy stuff but as an example local myCal = tonumber(pages) + 1 return myCal \stopluacode \starttext \blah \ctxlua{context(myFancyCalculations("\\totalnumberofpages"))} \stoptext Thank you in advance for any tips. best regards, Ramkumar

3 3

Update error on Raspberry Pi
by Luis Montgomery 16 Oct '21

16 Oct '21

Hi, I try to update LMTX and the script sends me this error: resolvers > lua > loading file '/home/monty/context/tex/texmf-context/tex/context/base/mkxl/spac-par.lmt' succeeded tex error > tex error on line 41 in file spac-par.mkxl: Undefined control sequence \undefined <line 3.41> + \shapingpenaltiesfrozenparcode <empty file> The control sequence at the end of the top line of your error message was never \def'ed. You can just continue as I'll forget about whatever was undefined. What has changed here? L. Montgomery

3 3

Memo module not working with lmtx
by Jason Ross 16 Oct '21

16 Oct '21

Hello, The Letter module seems to also include a module for memos. The following MWE fails with version 2021.10.10 23:43: \usemodule[memo] \setupmemo[ opening={People of Earth}, closing={Thanks for all the Fish,}, signature={The Dolphins}] \startmemo \startletter We are writing to let you know that we are all leaving \stopmemo \stoptext The following error is thrown by ConTeXt: tex error > tex error on line 197 in file /home/jason/.local/context/tex/texmf-modules/tex/context/third/letter/base/s-cor-02.mkvi: Undefined control sequence \???memosectionrenderings <argument> \???memosectionrenderings \v!head :\v!memo <macro> \syst_setups_start_tex_two #1#2#+\stopsetups ->\endgroup \dodoglobal \instance \defcsname \??setup #1:#2 \endcsname #1{#3} <line 5.197> \stopsetups 187 \stopsetups 188 189 \startsetups[\???memosectionrenderings\v!head:\v!memo] 190 \def\\{\correspondencesectionparameter\c!separator} 191 \startpacked 192 \doifsomething{\correspondenceparameter\c!fromname}{\memotext\c!fromname \correspondenceparameter\c!fromname \par} 193 \doifsomething{\correspondenceparameter\c!date }{\memotext\c!date \correspondenceparameter\c!date \par} 194 \doifsomething{\correspondenceparameter\c!toname }{\memotext\c!toname \correspondenceparameter\c!toname \par} 195 \doifsomething{\correspondenceparameter\c!subject }{\memotext\c!subject \correspondenceparameter\c!subject \par} 196 \stoppacked 197 >> \stopsetups 198 199 \unexpanded\def\correspondence_memo_head_table#element% 200 {\doifsomething{\correspondenceparameter#element} 201 {\NC % label 202 \def\currentcorrespondencestyle{\v!memo:#element}% 203 \usecorrespondencestylestyleandcolor\c!titlestyle\c!titlecolor 204 \memotext#element 205 \EQ % text 206 \def\currentcorrespondencestyle{\v!memo:#element}% 207 \usecorrespondencestylestyleandcolor\c!textstyle\c!textcolor The control sequence at the end of the top line of your error message was never \def'ed. You can just continue as I'll forget about whatever was undefined. mtx-context | fatal error: return code: 256

3 3

new upload
by Hans Hagen 14 Oct '21

14 Oct '21

Hi, This midweek upload has something new. There has been some discussion about footnotes and one thing I noticed when playing with some new possibilities is that the stretch in topskip (we use a default amount that long ago was derived from plain tex and is relative to the body font size) influences the pagebreaks in relation to inserts (footnotes) in a more significant way than one would expect. I also noticed that this stretch component is one of the reasons why sometimes a side float shape will carry over to a next page in spite of there being room. This relates to \brokenpenalty. At the end of this mail are some tests that demonstrate this. As a consequence we now have a "ntop" parameter as well as a shaping related penalty primitives (parameters): \shapingpenaltiesmode"FF % set all (future) bits (currently 4) \shapingpenalty\plushundred % don't go too high which is currently not enabled by default but might be in upcoming versions; this also depends on user feedback. It's a non intrusive extension the LuaMetaTeX engine. I have this setting in my local preferences file. Hans % test code (for Massimiliano and Hraban to play with) \starttext \showframe % this is the current default behaviour; we have a topskip with % quite some stretch and that stretch is taken into account % when tex calculates the badness; watch the next page \dorecurse{4}{ \bgroup \shapingpenaltiesmode\zerocount \showmakeup[penalty] \placefigure[left]{}{} \input tufte \par \egroup } \page EMPTY \page % the ntop is new and when >= 0 it is a multiplier for the number % of lines stretch, here we have one line; watch the next page \dorecurse{4}{ \bgroup \shapingpenaltiesmode\zerocount \setupinterlinespace[ntop=1] \showmakeup[penalty] \placefigure[left]{}{} \input tufte \par \egroup } \page EMPTY \page % these shaping parameters will discourage a linebreak within a % shape; the placement macro checked available space but that % doesn't mean that there can be no linebreak \dorecurse{4}{ \bgroup \showmakeup[penalty] \shapingpenaltiesmode"FF\relax \shapingpenalty\plushundred \placefigure[left]{}{} \input tufte \par \egroup } \page EMPTY \page % the next pages show the effect of changed topskip on page breaks % with footnotes \dorecurse{10}{ [#1] \input tufte \footnote{\input{tufte}} \par } \page EMPTY \page \setupinterlinespace[ntop=2] \dorecurse{10}{ [#1] \input tufte \footnote{\input{tufte}} \par } \page EMPTY \page \setupinterlinespace[ntop=0] \dorecurse{10}{ [#1] \input tufte \footnote{\input{tufte}} \par } \stoptext ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

3 2

Error: attempt to index a nil value
by Hans Åberg 13 Oct '21

13 Oct '21

I was suggested a long ago to hack the file /usr/local/texlive/2021/texmf-dist/tex/generic/context/luatex/luatex-math.tex and use LuaTeX directly, now using Version 1.13.2 (TeX Live 2021), but I get this error: (./luaotfload.sty (/usr/local/texlive/2021/texmf-dist/tex/latex/base/ltluatex.tex)) (./luatex-math-modified.tex[\directlua]:1: attempt to index a nil value (global 'arguments') stack traceback: [\directlua]:1: in main chunk. l.132 } ? … It is from this segment in the modified luatex-math.tex: \ifdefined\directlua \directlua { if arguments["mtx:lucidabright"] then tex.print("\string\\lucidabright") else tex.print("\string\\latinmodern") end } \fi Is there a workaround? —I may ditch this setup in favour of using 'context' directly, so it is not so important if there is no fix.

3 9

setuplocalinterlinespace not affecting the whole group?
by denis.maier＠unibe.ch 13 Oct '21

13 Oct '21

Hi, I have this MWE: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \definebodyfontenvironment [9bp] [ normal=9bp, b=24bp, ] \setupbodyfont[9bp] \startTEXpage { \setuplocalinterlinespace[line=25.5bp] %\setupinterlinespace[line=25.5bp] \tfb One\crlf Two Three } \stopTEXpage %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% For some reason \setuplocalinterlinespace[line=25.5bp] seems to affect only the first paragraph in the group, but not the distance between the two paragraphs. Using \setupinterlinespace instead of \setuplocalinterlinespace gives the same result. (Adding a \crlf between Two and Three gives the correct visual appearance. But that's an ugly hack of course...) Any hints? Best, Denis

2 2

undefined command in current latest
by Alexandre Christe 13 Oct '21

13 Oct '21

Indeed I can report similar issues with \getmarking after updating to the latest version of Context. Did something change regarding its definition / use recently? context -version mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: /Users/aleks/context-osx-64/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2021.10.08 20:18 mtx-context | main context file: /Users/aleks/context-osx-64/tex/texmf-context/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2021.10.08 20:18 Alex

4 3