ntg-context March 2023

ntg-context@ntg.nl

42 participants
65 discussions

Nested itemize
by Alexandre Christe 22 Aug '23

22 Aug '23

Dear all, I'm struggling to setup a nested itemize with no blank line and several columns. What I mean is something like 1. a) bla c) bla b) bla d) bla The following MWE is my starting point \starttext \startitemize[n] \item \blank[-line] \startitemize[a,horizontal,two] [margin=2cm] \item First \item Second \item Third \item Fourth \stopitemize \item \blank[-line] \startitemize[a,horizontal,columns,two] \item First \item Second \item Third \item Fourth \stopitemize \stopitemize \stoptext Thanks in advance

3 7

Luatex 1.12.0 announcement.
by luigi scarso 27 May '23

27 May '23

============================================================== LuaTeX 1.12.0 2020-03-15 ============================================================== This is the release for TeX live 2020. --shell-restricted now forbids loading of dso (dll/so object) Scaled virtual font Aadditional primitives \eTeXglue[stretch|shrink]order for querying order the etex way. Extra features runtoks tex.getmodenames() (as these can differ per engine/version) Permit nested runtoks in more complex situations of nesting (HH) More accurate and correct test for tex.[set|get]math Minor clean-up and bugs fixed -- luigi

1 4

Non-standard font alternatives
by Matthew McCabe 20 Apr '23

20 Apr '23

Hi list, I'm looking to import a font with medium and light weights (in this case Roboto) and define font alternatives so one can quickly switch to light text just as one would switch to bold text. There is a stackexchange answer from Wolfgang (https://tex.stackexchange.com/questions/303648/context-font-weights) which details a solution to this problem for ConTeXt MkIV but despite my best efforts I haven't been able to get things to work for me. There is the Roboto typescript example on ConTeXt garden but it isn't exactly what I'm looking for as for the document I'm making I would prefer to be able to treat the font weights as alternatives rather than separate families since I will be switching often. One can download the exact set of fonts I am using from https://fonts.google.com/specimen/Roboto Here is my code: \definefontalternative[lf] % light \definefontalternative[li] % lightitalic \definefontalternative[md] % medium \definefontalternative[mi] % mediumitalic \starttypescript [sans] [roboto] \definefontsynonym [SansLight] [file:Roboto-Light] [features=default] \definefontsynonym [SansLightItalic] [file:Roboto-LightItalic] [features=default] \definefontsynonym [Sans] [file:Roboto-Regular] [features=default] \definefontsynonym [SansItalic] [file:Roboto-Italic] [features=default] \definefontsynonym [SansMedium] [file:Roboto-Medium] [features=default] \definefontsynonym [SansMediumItalic] [file:Roboto-MediumItalic] [features=default] \definefontsynonym [SansBold] [file:Roboto-Bold] [features=default] \definefontsynonym [SansBoldItalic] [file:Roboto-BoldItalic] [features=default] \definefontsynonym [SansCaps] [file:Roboto-Sans] [features=smallcaps] \stoptypescript \starttypescript [sans] [roboto] \definebodyfont [default] [rm] [lf=SansLight sa 1, li=SansLightItalic sa 1, tf=Sans sa 1, it=SansItalic sa 1, md=SansMedium sa 1, mi=SansMediumItalic sa 1, bf=SansBold sa 1, bi=SansBoldItalic sa 1, sc=SansCaps sa 1] \stoptypescript \definetypeface[roboto][rm][sans][roboto][default] \setupbodyfont[roboto] \starttext \lf Light \li LightItalic \tf Regular \it Italic \md Medium \mi MediumItalic \bf Bold \bi BoldItalic \sc SmallCaps \stoptext - The result is entirely in the regular weight default font: What I've tried: 1. I've tried a great deal of alternative \definefontsynonym arguments such as specifying by name, including the full path to each ttf file 2. I played around with different two character \definefontalternative arguments to ensure there was no overlap with existing commands (as far as I am aware the existing set are otherwise undefined) A few things to note: 1. My current version of ConTeXt is 2022.12.09 16:34 2. For portability I have included the ttf files for Roboto in a directory within my project directory and while setting things up I set OSFONTDIR to include this directory and run `mtxrun --script fonts --reload --force` 3. `mtxrun --script fonts --list --all --pattern=Robo` yields: identifier familyname fontname filename subfont instances roboto roboto robotoregular ./fonts/Roboto/Roboto-Regular.ttf robotoblack roboto robotoblack ./fonts/Roboto/Roboto-Black.ttf robotoblackitalic roboto robotoblackitalic ./fonts/Roboto/Roboto-BlackItalic.ttf robotobold roboto robotobold ./fonts/Roboto/Roboto-Bold.ttf robotobolditalic roboto robotobolditalic ./fonts/Roboto/Roboto-BoldItalic.ttf robotoitalic roboto robotoitalic ./fonts/Roboto/Roboto-Italic.ttf robotolight roboto robotolight ./fonts/Roboto/Roboto-Light.ttf robotolightitalic roboto robotolightitalic ./fonts/Roboto/Roboto-LightItalic.ttf robotomedium roboto robotomedium ./fonts/Roboto/Roboto-Medium.ttf robotomediumitalic roboto robotomediumitalic ./fonts/Roboto/Roboto-MediumItalic.ttf robotonormal roboto robotoregular ./fonts/Roboto/Roboto-Regular.ttf robotoregular roboto robotoregular ./fonts/Roboto/Roboto-Regular.ttf robotothin roboto robotothin ./fonts/Roboto/Roboto-Thin.ttf robotothinitalic roboto robotothinitalic ./fonts/Roboto/Roboto-ThinItalic.ttf 4. Using `\definedfont[name:robotomedium*default] hello` and `\definedfont[file:Roboto-Thin*default] hello` (for example) work exactly as expected I hope this isn't a silly question, I'm very new to ConTeXt and have been struggling for a while so thought I may as well ask in case there's something I'm missing, would appreciate any guidance :) Regards, Matt

5 10

new uplaod
by Hans Hagen 17 Apr '23

17 Apr '23

Hi, I uploaded a new lmtx. Again some updated math of which details will be revealed later. Apart from some details we added suport for fourier notations. There are no high level definitions yet as we have to invent names but this is how it works (private unicode slots might change): \setupbodyfont[pagella] \starttext \setupmathdelimited [topoffset=.2\exheight] \definemathdelimited [fourier] [rule=no, left=\zerocount, right="FE944] \definemathdelimited [courier] [rule=no, left=\zerocount, right="FE946] \definemathdelimited [xourier] [rule=no, left=\zerocount, right="FE948] $ \fourier{(z+1)} $ $ \fourier{(z+1)} + \sqrt[2]{1}$ $ \fourier{(z+1)} + \courier{(z+1)} + \xourier{(z+1)} $ $ \fourier{\left(z+\frac12\right)} + \courier{\left(z+\frac12\right)} + \xourier{\left(z+\frac12\right)} $ $ \autofences \fourier{(z+\frac12)} + \courier{(z+\frac12)} + \xourier{(z+\frac12)} $ $ \widehat{x^2 + 2x + 2} $ \stoptext This example also shows a new \autofences feature and widehats (widetilde and widecheck also work that way) that overcome limitations in fonts, so \def\CrappyHack#1{\im{#1{a} + #1{a+b} + #1{a+b+c} + #1{a+b+c+d} + #1{a+b+c+d+e} + #1{a+b+c+d+e+f}}\par} \CrappyHack\widehat \CrappyHack\widetilde \CrappyHack\wideacute \CrappyHack\widecheck will work. For thise in finance we now have $ \annuity{x + 1} + \lannuity{x + 1} + \rannuity{x + 1} + \lrannuity{x + 1} $ these are basically radicals (like sqrt) with two sided symbols. 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 -----------------------------------------------------------------

3 5

registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
by Carlos 05 Apr '23

05 Apr '23

Hello list: This is under a fresh TeXLive installation. Sort as to put aside any texlive prepackaged issues. And the followign lines is the output of the error I've been having with the call of context on a recent texlive installation by both mtxrun --generate and luatools --generate right after. mtxrun --script cache --erase has also been called out to no avail registered function call [1160]: ...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied stack traceback: [C]: in upvalue 'func' ...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: in function 'lfs.dir' .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:139: in upvalue 'glob_pattern_table' .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in upvalue 'glob_pattern_table' .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in upvalue 'glob_pattern_table' .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in upvalue 'glob_pattern_table' .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:163: in upvalue 'glob_pattern_table' .../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:180: in function <.../texlive/2023/texmf-dist/tex/context/base/mkiv/l-dir.lua:169> (...tail calls...) ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: in upvalue 'walk_tree' ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1190: in local 'method' ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1152: in local 'traverse' ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1200: in upvalue 'analyzefiles' ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1286: in field 'identify' ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1311: in field 'load' ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1322: in field 'load' ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1588: in field 'getfilename' ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-otl.lmt:835: in function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-otl.lmt:828> (...tail calls...) ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:378: in function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:366> (...tail calls...) ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:485: in field 'read' ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-ctx.lmt:1377: in function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-ctx.lmt:1234> (...tail calls...) 51 ;definetypeface[MyLucida][rm][serif][lucida][default][encoding=texnansi] 52 \definetypeface[MyLucida][ss][sans][lucida][default][encoding=texnansi] 53 \definetypeface[MyLucida][tt][mono][lucida][default][encoding=texnansi] 54 \stoptypescript 55 56 57 \starttext 58 59 \usetypescriptfile[type-lucida] 60 \usetypescript[Lucida][texnansi] 61 >> \setupbodyfont[MyLucida, 10pt] 62 63 \input zapf 64 65 \input tufte 66 67 68 \stoptext 69 mtx-context | fatal error: return code: 1 it doesn't matter either whatever the typescript name goes and whether is type-lucida from texnansi-lucida-map file as it has been previously advised to change the name from . makes no difference. Is LuaLaTeX behaving the same way? Answer: no. The permission denied message happened first with folders whose permeissions were not owned by the user, but the root, so I moved the files out of harm's way to another folder . Anothr folder, NOT a subfolder. Then the problem persisted to read folders and even subfolders (directories, subdirectories) with cache filenames and headers that follow So let's not get to apprehensive, It's understandable that say, not reasonable, but understandable maybe? that mtxrun or lua for that matter will stop right before. So the folders were moved right after. Gone out of the binaries. But what I can't understand is why would it try to access cache folders unrelated with anything TeX or header folders for that matter???? This is perhaps more serious than I thought at first. And Let's not blame the TeXLive pre-packaged running under Alpine Linux. To put it in laymans' terms and If anything is clear to me, is that Alpine ir not letting Lua running beserk on the system and its folders, owned by whatever/whoever else, and with pesmissions set elsewhere. It's out of the question. Or it rather be. This is all writh a fresh TeX Live Installation. I mentioned the problem that may arise by questioning the Alpine installation because there were some problems with some binaries from the prepackaged TeX Live put out by Alpine devs. But this is not prepackaged. Nope. -- "We are on the verge: Today our program proved Fermat's next-to-last theorem." -- Epigrams in Programming, ACM SIGPLAN Sept. 1982

4 23

tikz error upgrading to texlive version (artix)
by Xavier B. 02 Apr '23

02 Apr '23

Hi, I use artix linux (a fork of arch with systemd alternative init systems). During the texlive package, I get this error: return { ["filename"]="/usr/share/texmf-dist/tex/generic/pgf/basiclayer/pgfcorepoints.code.tex", ["lastcontext"]="\n<inserted text> \n \\inaccessible \n<to be read again> \n \"\n\\pgfmath@catcodes ->\\catcode `\\==12 \\catcode `\\,=12 \\catcode `\\|=12 \\catcode `\\&=12 \\let \"\n \\pgfmath@char@quote \n\\pgfmathparse ->\\begingroup \\pgfmath@catcodes \n \\pgfmath@quickparsefalse \\ifpgfmathfloat \\let \\pgfmath@parse@next =\\pgfmathfloatparsenumber \\else \\let \\pgfmath@parse@next =\\pgfmathparse@ \\fi \\pgfmath@parse@next \n<argument> \\pgfmathparse \n {1cm}\\ifpgfmathmathunitsdeclared \\pgf@x \\pgfmathresult mu\\relax \\else \\pgf@x \\pgfmathresult pt\\relax \\fi \n\\pgfmath@next #1#2->#2\n \n...\nl.926 \\pgfsetxvec{\\pgfpoint{1cm}{0cm}}\n ", ["lastluaerror"]="?", ["lasttexerror"]="! Missing control sequence inserted", ["linenumber"]=926, ["offset"]=10, } I simply run context to this file: \usemodule[tikz] \starttext {\bf a} \tikz (0,0) -- (1,0); \stoptext My version of context is: [xan@coronari ~]$ context --version mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: /usr/share/texmf-dist/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2023.03.10 12:15 mtx-context | main context file: /usr/share/texmf-dist/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2023.03.10 12:15 My packages are: $ pacman -Qs texlive local/texlive-bibtexextra 2023.66579-1 (texlive-most) TeX Live - Additional BibTeX styles and bibliography databases local/texlive-bin 2023.66539-1 TeX Live binaries local/texlive-core 2023.66587-1 (texlive-most) TeX Live core distribution local/texlive-pictures 2023.66549-1 (texlive-most) TeX Live - Packages for drawings graphics local/texlive-publishers 2023.66550-1 (texlive-most) TeX Live - LaTeX classes and packages for specific publishers local/texlive-science 2023.66461-1 (texlive-most) TeX Live - Typesetting for mathematics, natural and computer sciences I also posted the message in Artix mailing list [https://lists.artixlinux.org/archives/artix-general/2023-March/000977.html] Thanks in advance, Xavier PS: In arch there are many AUR packages for installing minimal latest version: https://aur.archlinux.org/packages/context-minimals-git https://aur.archlinux.org/packages/context https://aur.archlinux.org/packages/context-modules Which one do you recomend to?

7 15

Re: [NTG-context] natural table oddities
by Henning Hraban Ramm 01 Apr '23

01 Apr '23

I would be happy about some answers/comments. Hraban Am 13.03.23 um 23:26 schrieb Henning Hraban Ramm: > Working on the documentation for “natural tables” in my book I stumbled > upon a few oddities/problems: > > ## Addressing cells: > > * There’s \setupTABLE[header], but not "footer" (or "section"); since we > have TABLEhead and TABLEfoot, IMO "head" and "foot" would make sense. > > * Row 1 is the first row of TABLEbody. I couldn’t find how to address > the first line of TABLEbody. > > * If I format a column, e.g. \setupTABLE[c][-1][color=red], body and > foot are formatted, but not the same column in header. I couldn’t find > how to format columns in header. > > * I don’t understand the addressing options "start" and "one". > > > ## Formatting > > * maxwidth doesn’t seem to have an effect, neither on the whole table > nor on a column. > * textwidth works only for the whole table. > * width gets stretched if option=stretch; i.e. I can’t fix the width of > single cells or columns. > > > ## Page breaking > > * What’s the difference between split=repeat and header=repeat ? > > > > I’d like to know if there are misunderstandings / if the behavior is > intentional.

2 2

Stack overflow when using Neo Euler for math
by Rory Molinari 31 Mar '23

31 Mar '23

Hi, I'm in the process of updating to TeXlive 2023 after a long time of light use with 2018. One issue I'm now having is an error when I try to use Neo Euler as my math font. \definefontfamily[mypalatinoeuler][rm][TeX Gyre Pagella] \definefontfamily[mypalatinoeuler][mm][Neo Euler] \setupbodyfont[mypalatinoeuler] \starttext $x=1$ \stoptext Result: mathematics > tweak > 'Neo-Euler', size 7, math size 3, version 'Version 000.002' found, version 'Version 000.002 ' expected tex error > tex error on line 5 in file ./euler_problem.tex: lua error: registered function call [1160]: ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3254: stack overflow stack traceback: ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3254: in upvalue 'add' ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3254: in upvalue 'add' ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3254: in upvalue 'add' ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3254: in upvalue 'add' ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3254: in upvalue 'add' ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3254: in upvalue 'add' ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3254: in upvalue 'add' ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3254: in upvalue 'add' ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3254: in upvalue 'add' ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3254: in upvalue 'add' ... (skipping 99970 levels) ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3267: in local 'action' ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3617: in upvalue 'tweaklist' ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3653: in upvalue 'applytweaks' ...xlive/2023/texmf-dist/tex/context/base/mkxl/math-act.lmt:3682: in upvalue 'mathematics_tweakaftercopyingfont' [string "local mathematics_tweakaftercopyingfont = mat..."]:5: in local 'runner' ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-ctx.lmt:510: in field 'aftercopyingcharacters' ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-con.lmt:859: in field 'scale' ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-otl.lmt:659: in function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-otl.lmt:651> (...tail calls...) ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:378: in function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:366> (...tail calls...) ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-def.lmt:485: in field 'read' ...xlive/2023/texmf-dist/tex/context/base/mkxl/font-ctx.lmt:1377: in function <...xlive/2023/texmf-dist/tex/context/base/mkxl/font-ctx.lmt:1234> (...tail calls...) It works if I use, say, [TeX Gyre Pagella Math] in place of [Neo Euler]. 15:49:15 $ context --version mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: /usr/local/texlive/2023/texmf-dist/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2023.03.10 12:15 mtx-context | main context file: /usr/local/texlive/2023/texmf-dist/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2023.03.10 12:15 I don't know how to diagnose any further. Cheers, Rory Molinari

2 2

meta-imp-fen in mkxl?
by Thomas A. Schmitz 31 Mar '23

31 Mar '23

Hi all, I wanted to use a rightbrace as background for a table, as defined in meta-imp-fen.mkiv. Unfortunately, I can't get it to work, for 2 reasons: 1. meta-imp-fen doesn't appear to be ported to mkxl. 2. When I try to compile with the --luatex switch, I get this error message: tex error > tex error on line 101 in file /mnt/shared/lmtx/tex/texmf-context/tex/context/base/mkiv/meta-imp-dum.mkiv: ! Undefined control sequence l.101 \newinteger \c_grph_replacement_n So, I'm a bit stymied right now. What can be done? All best Thomas

2 1

Numbering of figures after defining a new float
by Willi Egger 31 Mar '23

31 Mar '23

Hello everybody, I am still working on the previously mentioned project, consisting out of different parts. There are about 25 chapters in each part and most of the chapters contain figures. When using the predefined figure environment, then all figures in the figure-list are placed correctly though at each part the numbering restarts. Now I tried to implement for each part its own float environment, which enables me to produce a figure-list per part with subtitels. How ever in the newly defined floats there is no continuous numbering i.e. chapternumber.serialnumber. Instead each float get the chapter number only. How to get the numbering right? Kind regards Willi The following example shows what happens: \useMPlibrary[dum] \definefloat[Afigure][Afigures][figures] \definefloat[Bfigure][Bfigures][figures] \setuphead [part] [placehead=yes, page=yes] \setuphead [chapter] [page=no] \starttext \starttitle[title=List of figures] \startsubject[title=Figures (predefined figureenvironment)] \placelistoffigures \stopsubject \startsubject[title=Figures A] \placelistofAfigures \stopsubject \startsubject[title=Figures B] \placelistofBfigures \stopsubject \stoptitle \startpart[title=Part ONE] \startchapter[title={Chapter one in part one}] %les21 \startplaceAfigure [location=left, reference=fig:dumA, title={Dummy A}] {\externalfigure[dummy][width=0.6\textwidth]} \stopplaceAfigure \startplacefigure [location=left, reference=fig:dumB, title={Dummy B}] {\externalfigure[dummy][width=0.6\textwidth]} \stopplacefigure \startsection[title=Section A] \startplaceAfigure [location=left, reference=fig:dumC, title={Dummy C}] {\externalfigure[dummy][width=0.6\textwidth]} \stopplaceAfigure \stopsection \stopchapter \stoppart \startpart[title=Part TWO] \startchapter[title=Chapter one in part two] \startplaceBfigure [location=left, reference=fig:dumD, title={Dummy D}] {\externalfigure[dummy][width=0.6\textwidth]} \stopplaceBfigure \stopchapter \stoppart \stoptext

4 5

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context March 2023