May 2020 - ntg-context - NTG Mailing Lists

Strangely placed dot
by Mikael P. Sundqvist 04 May '20

04 May '20

Hi, what is going on with the placement of the dot in this example, and how can I avoid it? \starttext \startTEXpage[offset=3bp] $E_tE_s=E_{\min(t,s)}$. \switchtobodyfont[stixtwo]$E_tE_s=E_{\min(t,s)}$. \switchtobodyfont[lucidaot]$E_tE_s=E_{\min(t,s)}$. \stopTEXpage \stoptext Output attached. /Mikael

1 1

lmt_followtext crashes while standard followtext itself works
by Gerben Wierda 04 May '20

04 May '20

The following example has been extracted from my automatically generated MP code. \starttext \startMPpage string texstring; texstring := "{\colored [r=0.00, g=0.00, b=0.00]{\definebodyfont [9.0pt][rm][default=Regular at 9.0pt]\switchtobodyfont [9.0pt]\setupinterlinespace [9.9pt]\tf E.g. publish/ subscribe}}"; path parpath; parpath := (238,-167.00010681152344)..controls (238,-167.00010681152344) and (238,-167.00010681152344) ..(238,-167.00010681152344)..controls (238,-166.60010673470143) and (238,-166.20010665787942) ..(238,-165.80010658105741)..controls (238,-165.40010643392299) and (238,-165.00010628678857) ..(238,-164.60010613965414)..controls (238,-164.2001060472048) and (238,-163.80010595475545) ..(238,-163.40010586230611)..controls (238,-155.56353466513065) and (231.9683162849897,-149) ..(224.2552179837387,-149)..controls (223.85521783436539,-149) and (223.45521768499208,-149) ..(223.05521753561877,-149)..controls (222.65521740514737,-149) and (222.255217274676,-149) ..(221.8552171442046,-149)..controls (221.45521705001735,-149) and (221.0552169558301,-149) ..(220.65521686164286,-149)..controls (220.25521665589685,-149) and (219.85521645015083,-149) ..(219.45521624440482,-149)..controls (219.05521631807508,-149) and (218.65521639174534,-149) ..(218.2552164654156,-149)..controls (217.85521724037432,-149) and (217.45521801533303,-149) ..(217.05521879029175,-149)..controls (216.6552203077878,-149) and (216.25522182528385,-149) ..(215.85522334277991,-149)..controls (215.45522405083273,-149) and (215.05522475888554,-149) ..(214.65522546693836,-149)..controls (214.25522550518758,-149) and (213.8552255434368,-149) ..(213.45522558168602,-149)..controls (213.0552253720042,-149) and (212.65522516232238,-149) ..(212.25522495264056,-149)..controls (211.8552248680295,-149) and (211.45522478341843,-149) ..(211.05522469880736,-149)..controls (210.65522456100436,-149) and (210.25522442320135,-149) ..(209.85522428539835,-149)..controls (209.45522414149036,-149) and (209.05522399758237,-149) ..(208.65522385367439,-149)..controls (200.95716230583835,-149) and (195,-155.63452868682958) ..(195,-163.48966401016395)..controls (195,-163.88966411101083) and (195,-164.28966421185771) ..(195,-164.68966431270459)..controls (195,-165.08966445890775) and (195,-165.4896646051109) ..(195,-165.88966475131406)..controls (195,-166.25981210471718) and (195,-166.62995945812031) ..(195,-167.00010681152344); picture pic; pic := lmt_followtext [ text = texstring, path = parpath, spread = false, ]; \stopMPpage \stoptext lmt_followtext crashes on this code with: metapost log > ! angle(0,0) is taken as zero. metapost log > <for(1)> ...0)]shifted(-wid/2,0)rotated(angle(ad)) metapost log > shifted.ap;draw.pic[(EXPR0... metapost log > <argument> ...caled0.5pt.withcolor.green;fi;endfor metapost log > ;if((autoscaleupfollowtext... metapost log > metapost log > image->...ture;currentpicture:=nullpicture;(TEXT3) metapost log > ;currentpicture.if.str(SUF... metapost log > metapost log > followtext->...b_n;setbounds.currentpicture.to.b;) metapost log > endgroup metapost log > <argument> ...parameter"path"),getparameter"text") metapost log > ;popparameters; metapost log > image->...ture;currentpicture:=nullpicture;(TEXT3) metapost log > ;currentpicture.if.str(SUF... metapost log > metapost log > lmt_do_followtext->...meter"text");popparameters;) metapost log > endgroup metapost log > <scantokens> lmt_do_followtext metapost log > metapost log > <*> ...exstring, path = parpath, spread = false, ] metapost log > ; ; When I adapt the parameters that create parpath in my code, other uses of lmt_followtext crash. The same combinations of text and path so far haven’t crashed basic followtext(). I’ve run into comparable situations in my own code where I had to add code to handle the existence of a (0,0) direction (e.g. when I had two identical points on a path, but that is not the case here). The above minimal example triggers the failure. G

2 2

Vertical lines in matrices
by Weber, Matthias 03 May '20

03 May '20

Dear List, I am trying to get vertical (separating) lines into matrices, as is possible in tables: \starttext \startformula \left( \starttable[|c|c|c|] \NC 0 \NC 0\VL 0 \FR \NC 1 \NC 0\VL 1 \FR \stoptable \right) \stopformula \stoptext But my parentheses don’t fit, and I am not sure whether using tables in math mode is the proper way of doing things. \startmatrix seems to ignore a \VL. Any. suggestions? Thanks, Matthias

1 0

[ibmplex setup script]
by Floris van Manen 03 May '20

03 May '20

At present the ibmplexmonothin font is seen by the mtxrun script mtxrun --script fonts --list --all --pattern=ibmplexmonothin* identifier familyname fontname filename subfont instances ibmplexmonothin ibmplexmono ibmplexmonothin /home/vm/.local/share/fonts/Unknown Vendor/OpenType/IBM Plex Mono/IBM_Plex_Mono_Thin.otf ibmplexmonothinitalic ibmplexmono ibmplexmonothinitalic /home/vm/.local/share/fonts/Unknown Vendor/OpenType/IBM Plex Mono/IBM_Plex_Mono_Thin_Italic.otf But I don't manage to get the monothin variants loaded. Any hints available? Thanks .Floris

3 6

followtext, lmt_followtext and an offset of the glyphs typeset along the path
by Gerben Wierda 03 May '20

03 May '20

I have been looking at lmt_followtext and followtext to get typesetting done along a path. That works fine, except that in my case, I need the text to not be exactly on that path, I need it to hover slightly above tor below he path. Given that the path may have an unpredictable form, that means that all the glyphs need to be shifted a bit, there is no generic transfrom of the entire text string that will work, It should look a bit like this: Could I for instance change a TeX snippet to shift all the glyphs (individually) up a bit before handing it to followtext(), that would be a non-intelligent way of going about it (as it would of course also stretch/shrink the space between the glyphs when a bend is rounded, but I can live with that for now) G

3 5

\definehead behaving differently when in an environment file versus \input'ed
by ntg＠scorecrow.com 02 May '20

02 May '20

I'm having trouble with \definehead behaving differently depending upon whether I process a file that includes it via a \input statement versus a project structure that calls it via an environment file referenced from a component file. Overall aim: I currently produce a small circulation journal in Word that I'm hoping to switch to ConTeXt. Each article is written by a different author and I currently provide a Word template so they can see how their article will eventually look and how long it is, etc. I want to do the same for the ConTeXt version so I have created a template tex file they can simply \input at the top of their article. Processing the single article gives the desired output. So far so good. When I receive the articles, I want to use the project/product/component structure to allow me to produce an entire issue of the journal in one go. (I would simply comment out the \input line and add \startproject \startcomponent etc lines as necessary from each received article.) Problem: I've created a custom chapter heading, but the font size changes depending on whether I'm processing the \input version of the article or the \component version and I don't know why. Obviously, I would like the heading to be the same in each case so that authors see what I see and vice versa. I've attached a small zip file with a directory structure containing a minimal example. There are two directories: "input_version" and "project" version and the article.pdf files in each show the difference in the heading. I'm using TeX Live 2020 on a Mac. The console reports: ConTeXt ver: 2020.03.10 14:44 MKIV beta fmt: 2020.4.18 int: english/english -- Bruce Horrocks Hampshire, UK

2 3

unwanted vertical spaces after sectionhead in column layout
by Damien Thiriet 02 May '20

02 May '20

Hello list, Looks like lmtx adds extra vertical space after heads. Compare those two MWE: \setuppapersize [S4] \setuphead [subject] [after={}] \starttext \startsubject[title={blabla}] \input knuth \stopsubject \stoptext \setuppapersize [S4] \setuphead [subject] [after={}] \starttext \startcolumns [n=3] \startsubject[title={blabla}] \input knuth \stopsubject \stopcolumns \stoptext Greetings, Damien Thiriet (missing BachoTeX)

1 0

supp-ran.lua makes code unable to work in ConTeXt
by Jairo A. del Rio 01 May '20

01 May '20

I've adapted the following code to make mazes in LuaLaTeX and ConTeXt: https://www.rosettacode.org/wiki/Maze_generation#Lua I defined a modified version to make content visible to TeX and I saved in a file named maze.lua: function make_maze_tex(w, h, m) w = w or 16 h = h or 8 local map = initialize_grid(w*2+1, h*2+1) function walk(x, y) map[y][x] = false local d = { 1, 2, 3, 4 } shuffle(d) for i, dirnum in ipairs(d) do local xx = x + dirs[dirnum].x local yy = y + dirs[dirnum].y if map[yy] and map[yy][xx] then map[avg(y, yy)][avg(x, xx)] = false walk(xx, yy) end end end walk(math.random(1, w)*2, math.random(1, h)*2) tex.print([[\bgroup]]) tex.print([[\baselineskip ]]..m) local s = {} for i = 1, h*2+1 do --table.insert(s, [[\hbox{]]) tex.print([[\hbox{]]) for j = 1, w*2+1 do -- table.insert(s, [[\hbox{]]) if (j == 1 and i == 2) or (j == 2*w + 1 and i == 2*h) then tex.print([[\hskip ]]..m) elseif map[i][j] then --table.insert(s, [[\vrule width ]]..m..[[ height ]]..m) tex.print([[\vrule width ]]..m..[[ height ]]..m) else --table.insert(s, [[\hskip ]]..m) tex.print([[\hskip ]]..m) end -- table.insert(s, [[}]].."\n") end --table.insert(s, [[}]]) tex.print([[}]]) end --tex.print(table.concat(s)) tex.print([[\egroup]]) end And I executed the folowing in LuaLaTeX and ConTeXt: %\documentclass{article} %\usepackage{luacode} %\begin{document} \starttext %\begin{luacode*} \startluacode mz = dofile("maze.lua") local count = 0 for i=10,109 do count = count + 1 tex.print([[\subject{Laberinto ]]..count..[[}]]) mz.make_maze_tex(i, i, [[\dimexpr\textwidth/]]..(2*i+1)..[[\relax]]) tex.print([[\pagebreak]]) end %\end{luacode*} \stopluacode %\end{document} \stoptext Whereas it works very fast in LuaLaTeX it crashes on ConTeXt and outputs the following: token call, execute: ...ext/tex/texmf-context/tex/context/base/mkiv/supp-ran.lua:30: C stack overflow Why does it happen? I guess it has something to do with math.randomseed, but I don't know how to avoid this error message.

3 5

.so libraries not working with LMTX
by Jairo A. del Rio 01 May '20

01 May '20

I've tried using some C libraries for Lua in LuaTeX: http://webserver2.tecgraf.puc-rio.br/~lhf/ftp/lua/ They work (both LuaLaTeX and ConTeXt), but when LMTX is used, the following message appears (an example with MAPM): token call, execute: ...xt/tex/texmf-context/tex/context/base/mkiv/l-package.lua:325: error loading module 'mapm' from file './mapm.so': ./mapm.so: undefined symbol: lua_settop I've compiled both with Lua 5.3.5 and Lua 5.4.0 (rc1 and rc2) and both work successfully for test.lua (command line). However, they just don't work with LMTX. Is this a bug or feature of LMTX? Thank you in advance.

2 1

[rotate question]
by Floris van Manen 01 May '20

01 May '20

I try to introduce a per character rotation using lua. But a negative rotation angle seems to introduce a vertical offset to the base line. It might be intended, but how to get it gone? Any hints? .Floris \def\streepA{% \rotate[rotation=\ctxlua{context(math.random(1,15))}]{\|}% } \def\streepB{% \rotate[rotation=\ctxlua{context(math.random(-15,-1))}]{\|}% } \def\stapA#1{\dorecurse{#1}{\streepA}} \def\stapB#1{\dorecurse{#1}{\streepB}} \starttext \startTEXpage[offset=20mm, width=297mm] \startalignment[width]~ \dorecurse{50}{\stapA{10}\stapB{10}} \stopalignment \stopTEXpage \stoptext

1 0