- ntg-context - Mailing Lists

Luatex format error
by Hans Åberg 28 May '21

28 May '21

Using TexLive 2021, I got the error below. How to fix it? What input file should one give? % context math_style.tex resolvers | formats | executing runner 'run luatex format': /usr/local/texlive/2021/bin/universal-darwin/luatex --jobname="math_style" --fmt=/Users/<name>/Library/texlive/2021/texmf-var/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luatex/cont-en.fmt --lua=/Users/<name>/Library/texlive/2021/texmf-var/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luatex/cont-en.lui --c:currentrun=1 --c:fulljobname="./math_style.tex" --c:input="./math_style.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:texmfbinpath="/usr/local/texlive/2021/bin/universal-darwin" This is LuaTeX, Version 1.13.2 (TeX Live 2021) system commands enabled. ** Please type the name of your input file. **

2 4

setupindentations
by Hans van der Meer 28 May '21

28 May '21

This macro \setupindentations is mentioned in my ConText the manual from november 12, 2001. It seems to have disappeared. Is that so? Then why? What replacement? dr. Hans van der Meer

2 1

t-vim module: no highlighting for custom filetypes
by Nicola 28 May '21

28 May '21

For some reason, the vim module has stopped highlighting code associated to custom filetypes (it still works for built-in filetypes). For instance, typeset this: \usemodule[vim] \startvimrc[name=foo] set nocompatible set runtimepath+=~/foo/ \stopvimrc \definevimtyping[foo][ style={\switchtobodyfont[16pt,tt]}, directory=code/, syntax=foo, alternative=pscolor, vimrc=foo, ] \starttext \startfoo let while endwhile \stopfoo \stoptext The ~/foo/ directory contains ftdetect/foo.vim: au BufRead,BufNewFile *.foo setfiletype foo and syntax/foo.vim: if exists("b:current_syntax") finish endif syn case match syn iskeyword @,48-57,192-255,_ syn keyword fooKeyword let while endwhile hi def link fooKeyword Keyword let b:current_syntax = "foo" If I change `syntax=foo` to, say, `syntax=vim` in \definevimtyping then the code is highlighted. So, I suspect that I am not configuring the runtimepath correctly. Any idea how to fix this? I am using the latest LMTX to which I have added modules as explained here: https://wiki.contextgarden.net/Modules#ConTeXt_LMTX t-vim VERSION reads 2021.03.01. Nicola

3 13

no leavevmode
by Hans van der Meer 28 May '21

28 May '21

Why is there not implemented in \subsection a \leavevmode at the end of it? Here a minimal example showing that starting with the first word in an \hbox encounters vertical mode. Thus requiring a \leavevmode to put it on line with the following text. Whereas not starting with an \hbox does an implicite switch to horizontal mode. I can imagine that this behaviour could be confusing for users not well versed in the different behaviour of the horizontal and vertical modes. Therefore my question: Wouldn't it be wise to implement that \leavevmode? \startsubsection[title=TEST] \hbox{abc} def\crlf ghi jkl xyz \stopsubsection dr. Hans van der Meer

2 1

mathcolor attribute in MathML (mkiv)
by Duncan Hothersall 27 May '21

27 May '21

Hello list. I'm trying to use colour in some MathML formulae using the mathcolor attribute. It seems to have no effect on the output. I can see \applymmlmathcolor in the x-mathml.mkiv source but I can't see how to make it work. Does anyone have any pointers? (Does lmtx support this?) Thanks. Duncan

2 4

Advisable setupitaliccorrection in LuaMetaTeXT?
by Eduardo Bohoyo 27 May '21

27 May '21

Hi. Is it still necessary to use setupitaliccorrection if we have switched to LMTX?

1 0

new upload
by Hans Hagen 27 May '21

27 May '21

Hi, I uploaded a new version of lmtx. Apart from some small fixes, the configuration file is hopefully okay too. I'm sure MF will check it. However, the biggest change is hidden. In traditional tex, inserts (used for footnotes) are implemented using a quadruple of registers. In context these come from the range 132-254 which is not used by normal allocations. The number is basically a sort of index. However, this box/dimen/count/skip memory model doesn't work well for (possible) extensions nor does the wrapped final (per page) box fit into the more extended regular box model (not that anyone will notice or abuse that, it's just that some features of boxes don't make sense in the perspective of inserts). Inserts are somewhat complex (and interwoven) and are also somewhat fuzzy when one wants to do checking when making progress on a page. We already deal with that in context in a reasonable way but I get the feeling that we can do better. This and the above are reasons to come up with a variant memory model that permits playing with additional features more easily. The existing storage model is stil there (after all it's tex) but for those willing to check the alternative, in page-ins.mkxl one can uncomment % \insertmode\plustwo and remake the format. I rejected a mixed mode model because it makes the code ugly. Related mem grows on demand as with other mechanisms so there is no extra overhead involved. As a consequence I had to abstract some of the insert interface in context a bit more (because we use accessors instead of boxes) and hopefully I didn't forget one. We'll see. Once I'm confident with the new approach we'll switch to that (low level) interface model and can progress. Because users don't use inserts directly themselves not much harm can be done. 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 4

Unnecessary loading of lm-mono
by Rik Kabel 26 May '21

26 May '21

For a few revisions now, I have seen the following as the very first line of log files. It is not coming from my document. Is anybody else seeing it? fonts > beware: no fonts are loaded yet, using 'lm mono' in box Here is an example document that generates it: \setupbodyfont[libertinus,10pt] \starttext Hello world! \stoptext It seems harmless, but it does result in loading an un-needed font. mkiv lua stats > loaded fonts: 4 files: lmmono10-regular.otf, libertinusmath-bold.otf, libertinusmath-regular.otf, libertinusserif-regular.otf -- Rik

2 1

Re: [NTG-context] Unwanted upright math in MkIV
by Gavin 26 May '21

26 May '21

Aditya, > On Sun, 23 May 2021, Gavin wrote: > >> Hello, >> >> I’m using ConTeXt with MacOS. The current version of MkIV produces upright math rather than italic. MWE: >> >> \starttext >> \m{f = \beta} >> \stoptext > > Works correctly here. What does context --version say? My log file has this near the beginning: ... This is LuaTeX, Version 1.13.0 (TeX Live 2021) … system > ConTeXt ver: 2021.05.21 15:07 MKIV fmt: 2021.5.23 int: english/english … I am putting the entire log file below, since it isn’t terribly long. I hope that’s not bad etiquette. (I’m fairly new here.) Thanks! Gavin > mtx-context | redirect luametatex -> luatex: luatex --luaonly "/Users/Gavin/context-osx-64/tex/texmf-osx-64/bin/mtxrun.lua" --script mtx-context --luatex --autopdf GlyphExp.tex --redirected > > resolvers | formats | executing runner 'run luatex format': /Users/Gavin/context-osx-64/tex/texmf-osx-64/bin/luatex --jobname="GlyphExp" --fmt=/Users/Gavin/context-osx-64/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.fmt --lua=/Users/Gavin/context-osx-64/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.lui cont-yes.mkiv --c:autopdf --c:currentrun=1 --c:engine="luatex" --c:fulljobname="./GlyphExp.tex" --c:input="./GlyphExp.tex" --c:kindofrun=1 --c:luatex --c:maxnofruns=9 --c:redirected --c:texmfbinpath="/Users/Gavin/context-osx-64/tex/texmf-osx-64/bin" > This is LuaTeX, Version 1.13.0 (TeX Live 2021) > system commands enabled. > open source > level 1, order 1, name '/Users/Gavin/context-osx-64/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv' > system > > system > ConTeXt ver: 2021.05.21 15:07 MKIV fmt: 2021.5.23 int: english/english > system > > system > 'cont-new.mkiv' loaded > open source > level 2, order 2, name '/Users/Gavin/context-osx-64/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv' > system > beware: some patches loaded from cont-new.mkiv > close source > level 2, order 2, name '/Users/Gavin/context-osx-64/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv' > system > files > jobname 'GlyphExp', input './GlyphExp', result 'GlyphExp' > fonts > latin modern fonts are not preloaded > languages > language 'en' is active > open source > level 2, order 3, name '/Users/Gavin/Desktop/GlyphExp/GlyphExp.tex' > fonts > preloading latin modern fonts (second stage) > fonts > 'fallback modern-designsize rm 12pt' is loaded > backend > xmp > using file '/Users/Gavin/context-osx-64/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml' > pages > flushing realpage 1, userpage 1, subpage 1 > close source > level 2, order 3, name '/Users/Gavin/Desktop/GlyphExp/GlyphExp.tex' > close source > level 1, order 3, name '/Users/Gavin/context-osx-64/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv' > > mkiv lua stats > used config file: selfautoparent:/texmf/web2c/texmfcnf.lua > mkiv lua stats > used cache path: /Users/Gavin/context-osx-64/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e > mkiv lua stats > resource resolver: loadtime 0.006 seconds, 0 scans with scantime 0.000 seconds, 0 shared scans, 11 found files, scanned paths: <none> > mkiv lua stats > stored bytecode data: 457 modules (0.242 sec), 96 tables (0.015 sec), 553 chunks (0.257 sec) > mkiv lua stats > traced context: maxstack: 1424, freed: 0, unreachable: 1424 > mkiv lua stats > cleaned up reserved nodes: 57 nodes, 9 lists of 442 > mkiv lua stats > node memory usage: 11 attribute, 4 attribute_list, 1 glue, 51 glue_spec, 3 kern, 2 penalty, 2 temp, 2 user_defined > mkiv lua stats > node list callback tasks: 8 unique task lists, 7 instances (re)created, 38 calls > mkiv lua stats > used backend: pdf (backend for directly generating pdf output) > mkiv lua stats > jobdata time: 0.001 seconds saving, 0.000 seconds loading > mkiv lua stats > callbacks: internal: 132, file: 64, direct: 2, late: 0, function 507, total: 705 (705 per page) > mkiv lua stats > randomizer: resumed with value 0.58778292965144 > mkiv lua stats > result saved in file: GlyphExp.pdf, compresslevel 3, objectcompresslevel 1 > mkiv lua stats > loaded patterns: en::1, load time: 0.000 > mkiv lua stats > loaded fonts: 2 files: latinmodern-math.otf, lmroman12-regular.otf > mkiv lua stats > font engine: otf 3.116, afm 1.513, tfm 1.000, 7 instances, 3 shared in backend, 3 common vectors, 0 common hashes, load time 0.200 seconds > mkiv lua stats > used platform: osx-64, type: unix, binary subtree: texmf-osx-64 > mkiv lua stats > used engine: luatex version: 1.13, functionality level: 7420, banner: this is luatex, version 1.13.0 (tex live 2021) > mkiv lua stats > used hash slots: 46714 of 65536 + 250000 > mkiv lua stats > lua properties: engine: lua 5.3, used memory: 106 MB, ctx: 106 MB, max: unknown MB, hash chars: min(64,40), symbol mask: utf (τεχ) > mkiv lua stats > runtime: 0.545 seconds, 1 processed pages, 1 shipped pages, 1.835 pages/second > mtx-context | pdfview methods: auto default okular pdfxcview sumatra, current method: sumatra (directives_pdfview_method) > pdfview | command: wine "sumatrapdf.exe" -reuse-instance -bg-color 0xCCCCCC "GlyphExp.pdf" 1>/dev/null 2>/dev/null & > mtx-context | pdfview overhead: 0.004 seconds > system | total runtime: 0.865 seconds

2 5

Re: [NTG-context] lmtx and defined placeinitial color
by Eduardo Bohoyo 26 May '21

26 May '21

I have just seen that I also experience the same problem. I didn't realise it. I have provisionally "solved" it with an unfancy workaround. For instance, in your case it could be something like this: \definecolor[dropcapitals][t=0.40,a=1] This is not ideal. I know. But for the moment I can't think of anything better than to include the transparency trick. Eduardo Bohoyo

2 2