ntg-context May 2023

ntg-context@ntg.nl

45 participants
76 discussions

OBSD 7.3 binary locally compiled… what next?
by damien＠thiriet.web4me.fr 04 May '23

04 May '23

Hi, I upgraded today my OBSD to 7.3 and… realized too late that texlive binaries were on the compile farm, but not the lmtx ones. That was the opportunity to learn self-install, though. I compiled the binary, but I am stuck with the next step What I did: - rm -rf /usr/local/context/* (now I suspect I should have first updated my 7.2 installation and then, after upgrading to 7.3, compiled the binaries…) - download https://www.pragma-ade.nl/context/latest/cont-tmf.zip - unpacked it into /usr/local/context (unzip cont-tmf.zip -d /usr/local/context/) - cd /usr/local/context/source/luametatex - ./build.sh --native Compilation succeeded, looks like the binary lies in /usr/local/context/source/luametatex/build/native/luametatex What's the next step? There was this message: ============== tex trees resources like public fonts : tex/texmf/.... the context macro package : tex/texmf-context/.... the luametatex binary : tex/texmf-native/bin/... optional third party modules : tex/texmf-context/.... fonts installed by the user : tex/texmf-fonts/fonts/data/.... styles made by the user : tex/texmf-projects/tex/context/user/.... binaries: tex/texmf-<your platform>/bin/luametatex : the compiled binary (some 2-3MB) tex/texmf-<your platform>/bin/mtxrun : copy of or link to luametatex tex/texmf-<your platform>/bin/context : copy of or link to luametatex tex/texmf-<your platform>/bin/mtxrun.lua : copy of tex/texmf-context/scripts/context/lua/mtxrun.lua tex/texmf-<your platform>/bin/context.lua : copy of tex/texmf-context/scripts/context/lua/context.lua commands: mtxrun --generate : create file database mtxrun --script fonts --reload : create font database mtxrun --autogenerate context ... : run tex file (e.g. from editor) https://www.pragma-ade.nl/context/latest/cont-tmf.zip The tex/texmf/ folder does not exist yet. Does this mean I have to create that part of the tree by hand (which means should I have unpacked the zip at /usr/local/context/tex/texmf rather than /usr/local/context)?I’d bet copying anything(copying mtxrun from /usr/local/context/scripts/context/stubs/unix/mtxrun ? Should I run install.sh – which I not did, assuming maybe wrongly that it would fail, and if so, which options? Thank you for your time, Damien

2 1

Units for volts and Ohms
by Aditya Mahajan 04 May '23

04 May '23

Hi, As I was testing circuitikz, I realized that the following don't work: \unit{1V} \unit{100 kΩ} In phys-dim.lmt, we need to change line 467: v = "volt", to V = "volt", and perhaps add (not sure if lua allows utf variable names) Ω = "ohm", Aditya

2 1

define math function with \, inside
by Stefan Haller 01 May '23

01 May '23

Hi all, I wanted to define a custom math function (similar to log etc.) for argmax. However, I wanted to have a small space between "arg" and "max" and limits should work properly. I am using a up-to-date LMTX installation. Without the first constraint it's easy: > % old way: > \definemathcommand[argmax][limop]{\mfunction[argmax]} > % new way, discoverd by looking into math-def.mkxl > \definemathfunction[argmax] However, both methods do not work if I want to have "arg\,max" printed (error about \endcsname missing). With mkiv the first method works and can also be found in the wiki[1]. What's the current way to define such a custom math function? Thanks! Stefan [1]: https://wiki.contextgarden.net/Math/functions

2 2

Linebreaking in Japanese in ConTeXt
by Gerben Wierda 01 May '23

01 May '23

I am currently testing with a Japanese translation of something I originally created in English using the ConTeXt engine (LMTX). I run into the fact that Japanese has no use for whitespace, so most of the time TeX has no idea where to break. Is there something I can tell ConTeXt to solve this for me or do I have to alk with the translator to put whitespace in the correct places (kind of breaks the automatic linebreaking of TeX, though)? Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>, Mastodon <https://newsie.social/@gctwnl>) R&A IT Strategy <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/>

3 5

no recent message listed in the web interface
by Pablo Rodriguez 01 May '23

01 May '23

Dear list, I‘m afraid that https://mailman.ntg.nl/pipermail/ntg-context/2023/108157.html is the most recent message displayed for 2023 in the web interface (https://mailman.ntg.nl/pipermail/ntg-context/2023/date.html#108157). Although the list has been distributing messages to subscribers and I received them, I guess that the server software update might have something to do with this. Just for the record, I contacted Taco privately two weeks ago. No reply, but I understand that obviously he is busy with other things. Before sending him another message on the issue, I would like to ask whether anyone could confirm that recent messages (from this week) aren’nt being listed at https://mailman.ntg.nl/pipermail/ntg-context/2023/date.html. Many thanks for your help, Pablo

2 2

cannot generate format file with current latest
by Pablo Rodriguez 01 May '23

01 May '23

Dear list, I have just updated to current latest (2023.04.27 17:04). I always delete cache with "mtxrun --generate" after an update. When I try to create the format file with "context --make --all", I get the following error message: lua error > lua error on line 645 in file context.mkxl: token call, execute: ...ext/base/mkxl/cldf-pos.lmt:18: attempt to index a nil value (global 'posit') stack traceback: ...ext/base/mkxl/cldf-pos.lmt:18: in local 'code' ...ext/base/mkiv/util-lua.lua:96: in field 'loadedluacode' ...ext/base/mkiv/luat-env.lua:108: in field 'luafilechunk' ...ext/base/mkxl/luat-cod.lmt:82: in function 'lua.registercode' [ctxlua]:1: in main chunk <empty file> A number should have been here; I inserted '0'. (If you can't figure out why I needed to see a number, look up 'weird error' in the index to The TeXbook.) Could anyone confirm the issue? Many thanks for your help, Pablo

3 4

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context May 2023