- ntg-context - NTG Mailing Lists

Issue with interactive checkboxes
by Jan-Erik Hägglöf 25 May '22

25 May '22

HI! Tried to make a checklist in an interactive document. The problem seems to be that all checks/uncecks in same click, not each individually. Is there something wrong with my code? See attached below \setupinteraction[state=start] \setupexternalfigures[location=global] \usemodule[fields] \definesymbol [yes] [{\externalfigure[check-mark-svgrepo-com.svg][conversion=mp]}] \definesymbol [no] [] \setupfield [setup 3] [width=0.5cm, height=0.5cm, rulethickness=1pt, corner=round, framecolor=red] \definefield [check-me] [check] [setup 3] [yes,no] [no] \define\chk{\field[check-me]} \starttext \chk \blank[3cm] \chk \stoptext

3 8

Help needed with Custodia typescript
by Stefan Nedeljkovic 25 May '22

25 May '22

Dear list, I'm trying to set up Custodia in LMTX, but the custodiasemibolditalic won't show up. It shows up regularly when I run mtxrun --script fonts --list --all --pattern=Custodia I'm attaching the output for reference. Any help would be appreciated. Sincerely, Stefan \definefontalternative[md] \definefontalternative[mi] \starttypescript [serif] [custodia] \definefontsynonym[Serif] [name:custodianormal][features=default] \definefontsynonym[SerifItalic] [name:custodianormalitalic][features=default] \definefontsynonym[SerifMedium] [name:custodiasemibold][features=default] \definefontsynonym[SerifMediumItalic] [name:custodiasemibolditalic][features=default] \definefontsynonym[SerifBold] [name:custodiabold][features=default] \definefontsynonym[SerifBoldItalic] [name:custodiabolditalic][features=default] \stoptypescript \starttypescript [serif] [custodia] \definebodyfont [default] [rm] [ tf=Serif sa 1, it=SerifItalic sa 1, md=SerifMedium sa 1, mi=SerifMediumItalic sa 1, bf=SerifBold sa 1, bi=SerifBoldItalic sa 1] \stoptypescript \definetypeface [custodia] [rm] [serif] [custodia] [default] \usetypescript[custodia][uc] \setupbodyfont[custodia,rm,10pt] \starttext Regular Hamburgerfons, {\it Italic Hamburgerfons}, {\md Medium Hamburgerfons}, {\mi Medium Italic Hamburgerfons}, {\bf Bold Hamburgerfons}, {\bi Bold Italic Hamburgerfons},\\ \setff{smallcaps}{Small Caps Hamburgerfons}, \setff{smallcaps}{\it Small Caps Italic Hamburgerfons}, \setff{smallcaps}{\md Small Caps Medium Hamburgerfons}, \setff{smallcaps}{\mi Small Caps Medium Italic Hamburgerfons}, \setff{smallcaps}{\bf Small Caps Bold Hamburgerfons}, \setff{smallcaps}{\bi Small Caps Bold Italic Hamburgerfons} \stoptext

2 6

Help needed with slide grid layout
by Stefan Nedeljkovic 25 May '22

25 May '22

Dear list, This is a follow-up question on my previous question about Jean-Luc Doumont and his grid layouts. This time I have concrete questions. I reverse engineered his slide (slide_grid_overlay.pdf). All his units are based on inches, because the inch is an integer multiple (72) of the TeX point. His base unit is 0.1in. I tried implementing the layout first, but the pdf dimensions do not match the ones I set up. For example the width should be 8 inches, but the pdf is over 11 inches wide. I wish to shut off all margins and similar things and only have a text area with an offset of 0.2in all around the page (see slide_grid_overlay.pdf). Here is my current attempt: %\input fonts \definemeasure[base][0.1in] \definemeasure[zero][0in] \definepapersize[slide][width=80\measure{base},height=60\measure{base}] \setuppapersize[slide] \setuplayout[ leftedge=\measure{zero}, rightedge=\measure{zero}, leftedgedistance=\measure{zero}, rightedgedistance=\measure{zero}, leftmargin=\measure{zero}, rightmargin=\measure{zero}, leftmargindistance=\measure{zero}, rightmargindistance=\measure{zero}, width=middle, cutspace=2\measure{base}, backspace=2\measure{base}, topspace=2\measure{base}, header=\measure{zero}, height=middle, bottomspace=2\measure{base}, footer=\measure{zero}] %\usetypescript[ibmplex][uc] %\setupbodyfont[ibmplex,rm,9pt] \starttext \showlayout \stoptext Link to files: https://drive.google.com/drive/folders/1KpYbDlukvSCirKkFvJICOX3wABl_83bW?us… Kind regards, Stefan

2 3

spooky jumping headerline
by Steffen Wolfrum 25 May '22

25 May '22

Hi, the \blackrule (in my real project this is the running title) on page 1 is about 1mm higher than on page 2. Why? Best, Steffen \setupbodyfont[palatino,9.5pt]\setupinterlinespace[13pt] \setuppagenumbering [alternative=doublesided,location=] \setupheader[strut=yes] \setupheadertexts[text][][\blackrule] \definepapersize[stw][width=17cm,height=24cm] \setuppapersize[stw][stw] \setuplayout [width=122mm, backspace=18mm,topspace=10mm, header=7mm,headerdistance=5.969mm, footer=5mm,footerdistance=5mm,height=214.031mm, location=middle] \definedelimitedtext [narrowtext] [leftmargin=6mm,rightmargin=0mm]%, \starttext %%Test 1: \dorecurse{6}{\input linden} %%Test 2: %\dorecurse{5}{\input tufte} \start \startdelimitedtext[narrowtext] \switchtobodyfont[8pt]\setuplocalinterlinespace[line=11pt] \input linden\par \stopdelimitedtext \stop \stoptext

1 0

Problems with column sets?
by T. Kurt Bond 25 May '22

25 May '22

Given the following file that uses definecolumnset and startcolumnset/stopcolumnset (largely from the wiki <https://wiki.contextgarden.net/Command/definecolumnset>) for input: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \setuppapersize[letter] \definecolumnset[TwoColumns][n=2] \startcolumnset [TwoColumns] \title{Test page} \framed [frame=off, bottomframe=on, width=\textwidth, frameoffset=1mm, foregroundstyle=small, ]{\copyright\ \date[][year] Donald E. Knuth} \input knuth \stopcolumnset %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Why does context fail, producing an empty .log and .pdf, with the following information to the terminal: resolvers | formats | executing runner 'run luametatex format': /usr/local/sw/versions/context-osx-64/tex/texmf-osx-64/bin/luametatex --jobname="./x.ctx" --fmt=/usr/local/sw/versions/context-osx-64/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt --lua=/usr/local/sw/versions/context-osx-64/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui --c:currentrun=1 --c:fulljobname="./x.ctx" --c:input="./x.ctx" --c:kindofrun=1 --c:maxnofruns=9 --c:texmfbinpath="/usr/local/sw/versions/context-osx-64/tex/texmf-osx-64/bin" system > system > ConTeXt ver: 2022.05.11 11:36 LMTX fmt: 2022.5.24 int: english/english system > system > 'cont-new.mkxl' loaded open source > level 1, order 1, name '/usr/local/sw/versions/context-osx-64/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > beware: some patches loaded from cont-new.mkiv close source > level 1, order 1, name '/usr/local/sw/versions/context-osx-64/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > files > jobname './x', input './x.ctx', result './x' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 1, order 2, name './x.ctx' mtx-context | fatal error: return code: 1 -- T. Kurt Bond, tkurtbond(a)gmail.com, https://tkurtbond.github.io

3 4

item enumeration
by Jorge Manuel 25 May '22

25 May '22

Hi to All A have this piece of code that works in old ConText versions but with new versions (current version: 2022.04.19 19:53) don’t. \def\legalconversion#1{ \dorecurse{\numexpr\currentitemlevel-1}{% \rawcounter[itemgroup:\currentparentitemgroup][\recurselevel].}% #1% } \defineconversion[legal][\legalconversion] How can fix this? Thanks for you support Jorge Magalhães

2 1

Callbacks in LuaMetaTeX
by Max Chernoff 25 May '22

25 May '22

Hi list, I've been playing around with some of the Lua callbacks in LuaMetaTeX, and I have a few questions/comments. Context: I'm writing a Plain/LaTeX/ConTeXt module called "lua-widow-control" that uses Lua callbacks to automatically remove widows and orphans from documents. The relevant Lua code is at: https://github.com/gucci-on-fleek/lua-widow-control/blob/master/source/lua-… in case you're curious about how I'm using these callbacks, but you shouldn't need to look there since this email is self-contained. 1. In LMTX, calling "tex.linebreak" produces a luatex warning > tex: left parfill skip is gone warning. I don't get this warning in Plain LuaTeX, LuaLaTeX, or MkIV, so I think that it's specific to LuaMetaTeX. The LuaMetaTeX manual hardly mentions "left parfill skip"/"parfillleftskip", so I'm not too sure what to do to avoid this warning. You can reproduce the warning with this code (but any call to "tex.linebreak" also works): \startluacode function test(head) tex.linebreak(node.copylist(head)) return head end nodes.tasks.appendaction("processors", "after", "test") \stopluacode \starttext Hello! \stoptext 2. The LuaMetaTeX manual says that "pre_linebreak_filter" is called after the parfillskip glue has been added, but this doesn't seem to be the case. With LuaLaTeX/Plain LuaTeX, this is true, but the node list passed to the callback in MkXL is missing the parfillskip. (I don't have an MkIV installation to test here.) This MkXL code: \startluacode function test(head) local last = node.slide(head) print "START" for i=1,3 do print(last) print( node.type(last.id), node.subtypes(last.id)[last.subtype], last.width, last.stretchorder, last.stretch ) last = last.prev end print "STOP" return head end nodes.tasks.appendaction("processors", "after", "test") \stopluacode \starttext Hello! \stoptext produces: START <node : 2521 <= 2258 => nil : glue spaceskip> glue spaceskip 341648 0 384354 <node : 2509 <= 2521 => 2258 : glyph unset> glyph nil 213792 nil nil <node : 2497 <= 2509 => 2521 : glyph unset> glyph nil 385140 nil nil STOP START <node : 2611 <= 2357 => nil : glue userskip> glue userskip 0 2 65536 <node : 2274 <= 2611 => 2357 : glyph unset> glyph nil 385140 nil nil <node : 2239 <= 2274 => 2611 : rule strut> rule strut 0 nil nil STOP while this (presumably) equivalent Plain LuaTeX code: \directlua{ function test(head) local last = node.slide(head) print "START" for i=1,3 do print(last) print( node.type(last.id), node.subtypes(last.id)[last.subtype], last.width, last.stretch_order, last.stretch ) last = last.prev end print "STOP" return head end callback.register("pre_linebreak_filter", test) } Hello! \bye produces: START <node 82 < 298 > nil : glue 15> glue parfillskip 0 2 65536 <node 291 < 82 > 298 : penalty 2> penalty linepenalty nil nil nil <node 284 < 291 > 82 : glyph 0> glyph unset 182045 nil nil STOP I'm not sure if this is a doc bug, an engine bug, or if I'm just doing something wrong. 3. The LuaTeX/LuaMetaTeX engine manuals say that for node callbacks, you can return "true" if you don't need to replace the passed node list. This works fine with raw LuaTeX callbacks and the luatexbase wrappers, but it doesn't work with the ConTeXt "nodes.tasks" wrapper functions. This Plain example works: \directlua{ callback.register("pre_linebreak_filter", function () return true end) } Hello! \bye But this MkXL example doesn't: \startluacode function test(head) return true end nodes.tasks.appendaction("processors", "after", "test") \stopluacode \starttext Hello! \stoptext I'm not sure if this behaviour is expected or not. Saving the node passed to the callback then returning it at the end works just fine, but being able to just return "true" would be slightly more convenient sometimes. 4. Would it be possible to add a ConTeXt-level interface ("nodes.tasks") to the "pre_output_filter" callback? Right now I'm using the low-level engine interface ("callback.register"), but this is pretty fragile since any format update could block this. Plus, it would be more convenient for me if I could register all of the callbacks the same way. The way I'm doing it right now seems to work well enough though, so this doesn't matter too much. 5. Off-topic, but is there a good way to trace node memory leaks? Documents larger than ~1600 pages run out of node memory when I load lua-widow-control, so I know that I'm leaking nodes somewhere, but it's pretty tricky to trace. Are there any "tricks" to find leaked nodes, or do I just need to watch my allocations very carefully? Sorry if any of these points don't make much sense or have already been answered elsewhere. Thanks in advance. -- Max Versions used for test documents: ConTeXt ver: 2022.04.20 19:18 LMTX fmt: 2022.5.1 int: english/english This is LuaTeX, Version 1.13.2 (TeX Live 2021/W32TeX)

1 1

Fwd: ConTeXt meeting registration
by Taco Hoekwater 25 May '22

25 May '22

Hi all, I just registered myself to attend the ConTeXt meeting in 2022. This is a good moment to remind you all of the meeting (September 12-18, in Dreifelden DE) and —especially— of the need to register if you plan to attend, either in person or online! There is no finished programme yet, so I can repeat the call for papers also. The theme for this meeting is digging deep But, as in previous years, anything at all related to ConTeXt that you would like to share is an acceptable subject for a presentation, tutorial, discussion, Q&A session, demonstration, workshop, recital, sketch, or sermon. More details are on the website: https://meeting.contextgarden.net/ Hoping to see many of you in Dreifelden, Taco > Begin forwarded message: > > From: 16th ConTeXt Meeting Registration <taco(a)contextgarden.net> > Subject: taco(a)bittext.nl ConTeXt meeting registration > Date: 25 May 2022 at 09:08:47 CEST > To: cg-treasurer(a)contextgarden.net > Reply-To: taco(a)bittext.nl > > Hi Taco, > > Taco Hoekwater has registered at 2022-05-25 09:08:47. — Taco Hoekwater E: taco(a)bittext.nl genderfluid (all pronouns) — Taco Hoekwater E: taco(a)bittext.nl genderfluid (all pronouns)

1 0

Numbering in mathalignment not working
by śrīrāma 25 May '22

25 May '22

Hi, [I am on version 2022.05.11 11:36] I think either a bug might have crept into one of the recent uploads or there is some change in behaviour – numbering of statements inside mathalignment blocks is not working: only one statement is numbered even if multiple are requested. The following example does not produce the expected result (sample attached): both the equations should be numbered when only the first one is – \starttext \placeformula \startformula \startmathalignment \NC a \NC = b \NR[eq:one] \NC c \NC = d \NR[eq:two] \stopmathalignment \stopformula \stoptext Also the [+] options and the second optional argument of \NR does not work as expected. Has its behaviour changed? I ran into this when I compiled a large maths-heavy document and while proof- reading noticed numerous missing references to statements inside mathalignment. Please advise me on how I might fix/workaround this. Thank you, Sreeram

3 4

font question re U+00336
by jbf 25 May '22

25 May '22

I wonder if someone can help me interpret this message in the log file fonts > start missing characters: /home/jbf/bin/context/tex/texmf/fonts/opentype/public/tex-gyre/texgyrepagella-regular.otf fonts > 88 U+00336 ̶ COMBINING LONG STROKE OVERLAY fonts > stop missing characters My questions are as follows: 1. What does 88 mean here? 88 instances of this missing glyph? Page 88? Or something else? or in other words, how might I discover where something is missing from the original text? 2. Tex Gyre Pagella is normally a pretty handy typeface to use for me because it has pretty much all the glyphs I normally need... except this one obviously! Isn't it really just an en rule (or very similar to such)? Or in other words, how do I best overcome the problem of this missing character? 3. And perhaps connected with the above question: is there good fallback solution one can use? Do I need to \definefontfallback something or is there an automatic one already happening? I've started to examine the log files a bit more carefully for various items and it is showing up my ignorance!! Julian

2 2