February 2021 - ntg-context - NTG Mailing Lists

Questions for eTABLE
by Alain Delmotte 23 Feb '21

23 Feb '21

2 2

Using Gill Sans on macOS
by Gerben Wierda 22 Feb '21

22 Feb '21

I’m normall using Optima Nova on my system, e.g. by defining a font like this: \definefontfamily [archimate] [ss] [Optima nova LT Pro] [tf=style:Medium, bf=style:Bold, it=style:Medium Italic, bi=style:Bold Italic] \setupbodyfont[archimate] I would like to experiment with Gill Sans, but that fails with fonts > defining > unable to define 'GillSans.ttc' as 'archimate-14pt-ss-tf-0--0' It is here: /System/Library/Fonts/Supplemental/GillSans.ttc What should I do to be able to use that font? Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>) R&A Enterprise Architecture <https://ea.rna.nl/> (main site) Book: Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/> Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>

2 2

path in LuaMetaFun
by Pablo Rodriguez 21 Feb '21

21 Feb '21

Dear list, I have the fowllowing sample: \starttext \startmakeup[page][align=middle] \startMPcode{doublefun} draw lmt_followtext [ text = "\feature[+][smallcaps]\bf\samplefile{zapf} ", path = ((0,0)..(3,3.25)..(9,-3.25)..(12,0)..(9,3.25)..(3,-3.25)..(0,0)), autoscaleup = "max", reverse=true, ] xsized .75TextWidth ; \stopMPcode \startMPcode{doublefun} draw lmt_followtext [ text = "\feature[+][smallcaps]\bf\samplefile{zapf} ", path = ((0,0)..(3,3.25)..(9,-3.25)..(12,0)..(9,3.25)..(3,-3.25)..cycle), autoscaleup = "max", reverse=true, ] xsized .75TextWidth ; \stopMPcode \stopmakeup \stoptext I’m afraid I don’t understand how to close the path. Cycle has problems with part of the text and returning to the start seems to distort the path itself. Which is the right way to close the path or what am I missing? Many thanks for your help, Pablo -- http://www.ousia.tk

2 4

metafun
by Hans Hagen 20 Feb '21

20 Feb '21

Hi, When making sure that the metafun manual processes with lmtx (where we have sometimes different implementations of macros) I also checked performance. When we started with this manual, it was still MKII time so we either had direct calls or inbetween calls. Especially multiple runs could take a while (many minutes, iir some 15 depending on how it was run). That was no fun. In mkiv with luatex and the built in mp library this dramatically went down to 18.1 seconds for one run and 14.2 seconds for luajittex, for 428 pages. This not bad considering that a lots of features are used: thousands of mp images, a bunch of external images, many fonts, plenty of buffers, positioning, color, hyperlinks, backgrounds etc. This document uses plenty of lua so that is why we gain a lot with luajittex. In lmtx where we dropped jit and have a less performing backend we expect to need more runtime but in the meantime we're quite okay. Not only the engine is faster, but also some low level macros benefit a bit from new features. I don't know how much lua speedup plays a role but probably not that much. For 448 pages (some 20 more than we had before) we now need 16.5 seconds and 15.7 when we use the compact font mode. So we're halfway between luatex and luajittex now. More than 3 seconds of the runtime is for metapost. (I use the machine as before.) Hans PS. If all the stories are true is should be 1 second on a modern apple at which point differences in measurements become noise but I cannot check that. Some day I might check it on a rpi 4. ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

2 2

Lua code and table
by Fabrice Couvreur 20 Feb '21

20 Feb '21

Hi, The code works, but is it possible to make it shorter ? Thank you Fabrice \startuseMPgraphic{DiagonalRule} rulethickness := \frameddimension{rulethickness}; drawoptions( withpen pencircle scaled rulethickness withcolor \MPcolor{\framedparameter{framecolor}}); pair leftcorner, rightcorner, Leftcorner, Rightcorner; leftcorner := (rulethickness, \overlayheight-rulethickness); rightcorner := (\overlaywidth-rulethickness, rulethickness); Leftcorner := ( rulethickness, rulethickness); Rightcorner := (\overlaywidth-rulethickness,\overlayheight-rulethickness); draw leftcorner -- rightcorner; draw Leftcorner -- Rightcorner; \stopuseMPgraphic \defineoverlay [DiagonalRule] [\useMPgraphic{DiagonalRule}] \define[2]\DiagonalLabel{% \setuptabulate [after={\blank[\frameddimension{offset}]}] \starttabulate [|p|r|] \NC \NC \bf #2 \NC\NR \NC \bf #1 \NC \NC\NR \stoptabulate } \starttext \startluacode local background_one = { align = "middle", style = "type", background = "DiagonalRule", } local letters_1 = { "A", "B", "C", "D", "E", "F", "G", "H" } context.startxtable({"align={middle,lohi}, width=0.8cm,offset=0.8ex,bodyfont=9pt,framecolor=cyan"}) context.startxrow() context.startxcell({"frame=off"}) context() context.stopxcell() for _, letter in ipairs(letters_1) do context.startxcell() context(letter) context.stopxcell() end context.stopxrow() for _, letter in ipairs(letters_1) do context.startxrow() context.startxcell() context(letter) context.stopxcell() for j = 0, 7 do context.startxcell( j == 0 and letter == "B" and background_one or j == 0 and letter == "C" and background_one or j == 0 and letter == "D" and background_one or j == 0 and letter == "G" and background_one or j == 0 and letter == "H" and background_one or j == 1 and letter == "A" and background_one or j == 1 and letter == "E" and background_one or j == 1 and letter == "F" and background_one or j == 1 and letter == "G" and background_one or j == 2 and letter == "A" and background_one or j == 2 and letter == "D" and background_one or j == 2 and letter == "F" and background_one or j == 2 and letter == "G" and background_one or j == 2 and letter == "H" and background_one or j == 3 and letter == "A" and background_one or j == 3 and letter == "C" and background_one or j == 3 and letter == "E" and background_one or j == 3 and letter == "H" and background_one or j == 4 and letter == "B" and background_one or j == 4 and letter == "D" and background_one or j == 4 and letter == "F" and background_one or j == 4 and letter == "G" and background_one or j == 5 and letter == "B" and background_one or j == 5 and letter == "C" and background_one or j == 5 and letter == "E" and background_one or j == 6 and letter == "A" and background_one or j == 6 and letter == "B" and background_one or j == 6 and letter == "C" and background_one or j == 6 and letter == "E" and background_one or j == 7 and letter == "A" and background_one or j == 7 and letter == "C" and background_one or j == 7 and letter == "D" and background_one ) context() context.stopxcell() end context.stopxrow() end context.stopxtable() \stopluacode \stoptext

6 13

issue with references
by Pablo Rodriguez 19 Feb '21

19 Feb '21

Hans, I have the following sample: \setuphead[chapter][sectionsegments=chapter] \setuphead[section][sectionsegments=section] \setupreferencestructureprefix [default] [prefixsegments=*:*] \starttext \startTEXpage[offset=1em] \chapter{Chapter} \section[sec]{Section} As told in \getreference[number][sec]. \getreference[title][sec].\\ As told in \in[sec]. \about[sec]. \stopTEXpage \stoptext \getreference[number] doesn’t follow \setupreferencestructureprefix. I don’t know whether this is intended, but I think it might be a bug. Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

lmtx
by Hans Hagen 19 Feb '21

19 Feb '21

Hi, In the last couple of lmtx uploads \startTEXpage should work a bit better. These uploads also introduced a new option for alignments, which can be checked in: \def\DemoA#1{\vbox{\red \hsize#1\input tufte }} \def\DemoB#1{\vbox{\green \setupalign[always]\hsize#1\input tufte }} \def\DemoC#1{\startTEXpage[offset=10pt]\DemoA{#1pt}\blank\DemoB{#1pt}\blank#1pt\stopTEXpage} \starttext \dostepwiserecurse{300}{600}{10}{ \startTEXpage[offset=10pt] \startoverlay {\DemoA{#1pt}} {\DemoB{#1pt}} \stopoverlay \blank \the\dimexpr#1pt\relax \stopTEXpage } \DemoC{370} \DemoC{390} \DemoC{490} \DemoC{540} \DemoC{580} \stoptext I leave it to users to determine if the few cases where the results differ are better or worse but one can for instance use it to influence (as side effect) the last line. In general, tweaking the machinery can give different results and i guess that hardly any user can make consistent claims about what is better. It all depends on what one deals with. (The keyword is suboptimal, it kind of tells what happens but on the other obscurew what really goes on: always forcing a first hyphenation pass when breaking lines.) 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 -----------------------------------------------------------------

1 0

MKIV format generation error with latest 2021-02-17 13:33
by Adam Reviczky 17 Feb '21

17 Feb '21

Hi, I am getting the following error with luatex/mkiv with today's latest: context --make loading : ConTeXt Token Support / Initialization /usr/share/texmf/tex/context/base/mkxl/toks-ini.lmt:21: attempt to call a nil value (field 'getcommandvalues') stack traceback: /usr/share/texmf/tex/context/base/mkxl/toks-ini.lmt:21: in local 'code' /usr/share/texmf/tex/context/base/mkiv/util-lua.lua:96: in field 'loadedluacode' /usr/share/texmf/tex/context/base/mkiv/luat-env.lua:108: in field 'luafilechunk' /usr/share/texmf/tex/context/base/mkiv/luat-cod.lua:75: in function 'lua.registercode' [\directlua]:1: in main chunk. \registerctxluafile #1#2->\ctxlua {lua.registercode("#1","#2")} l.18 \registerctxluafile{toks-ini}{autosuffix} ? --- mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: /usr/share/texmf/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2021.02.17 13:30 mtx-context | main context file: /usr/share/texmf/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2021.02.17 13:30 --- Compiled with libpng 1.6.37; using 1.6.37 Compiled with lua version 5.3.6 Compiled with mplib version 2.00 Compiled with zlib 1.2.11; using 1.2.11 Development id: 7405 --- Adam

2 1

Are positional graphics still working?
by Jairo A. del Rio 17 Feb '21

17 Feb '21

I've copied the following example from the ConTeXt archive: \defineoverlay[frames][\positionoverlay{frames}] \setupbackgrounds[text][background=frames] \startMPpositiongraphic{frame} if unknown context_apos : input mp-apos.mpiv ; fi ; \MPgetposboxes{\MPvar{self}}{\MPanchorid} if nofposboxes = 1 : draw posboxes[1] ; fi ; \stopMPpositiongraphic \startpositionoverlay{frames} \setMPpositiongraphic{one}{frame} \setMPpositiongraphic{two}{frame} \stoppositionoverlay \starttext This \hpos{one}{word} should be \hpos{two}{framed}. \stoptext Frames are misplaced, so I don't know if that's a bug or something else has been updated/changed/deprecated. Thank you in advance. Jairo

2 3

infinite number of runs
by Pablo Rodriguez 17 Feb '21

17 Feb '21

Hans, I have some documents that trigger infinite runs. I want to provide a minimal sample that shows this. But is there some code in the .tuc file (or in the .log file with \tracingall) that shows the need of another run? Many thanks for your help, Pablo -- http://www.ousia.tk

2 1