October 2022 - ntg-context - NTG Mailing Lists

context --autopdf and --showdirectives
by Henning Hraban Ramm 02 Nov '22

02 Nov '22

I’d like to configure the default behaviour of "context --autopdf"; since on my Mac I must always write "--autopdf=auto", otherwise context tries to call wine "sumatrapdf.exe" -reuse-instance -bg-color 0xCCCCCC instead of e.g. "open". There’s a hint about "directives_pdfview_method", so I wanted to find out more about directives: "context --showdirectives" looks promising; it tells me "result saved in file: .../texmf-context/tex/context/base/mkiv/mtx-context-setters.pdf", but that file isn’t there; it is actually in the current directory, but broken. * How can I configure the command for --autopdf ? (Something in texmfcnf.lua?) * Can we add additional options ("pdfview methods: auto default okular pdfxcview sumatra"), e.g. open (should be default on Mac), xdg-open (could be default on Linux)... * What’s wrong with --showdirectives? Hraban

2 2

Create the values of a sequence with Lua
by Fabrice Couvreur 31 Oct '22

31 Oct '22

Hi, The idea is to fill the array with the sequence defined by p(0) = 0.3 and p(n + 1) = 0.3 + 0.7*p(n) The problem is that I don't really master Lua but I will learn when I have some time! Thanks for your help. Fabrice \starttext \startluacode context.startxtable({"align={middle,lohi},width=2cm,bodyfont=9pt"}) p = {} p[0] = 0.3 for i=0,19 do p[i+1] = 0.3+0.7*p[i]^2 end context.startxrow() for i=0,19 do context.startxcell() context(i) context.stopxcell() context.startxcell() context(i+1) context.stopxcell() context.startxcell() context("%0.8f",p[i] ) context.stopxcell() context.stopxrow() end context.stopxtable() \stopluacode \stoptext

2 1

Suboptimal German hyphenation
by Leah Neukirchen 31 Oct '22

31 Oct '22

Hi, I was typesetting some German text on a narrow page when I discovered the justification wasn't as good as expected. I think I tracked this down to differences in hyphenation points, namely, ConTeXt has fewer: \starttext \language[de] \showhyphens{Zusammenhang} \showhyphens{anderswo} \showhyphens{anderswoher} \stoptext This shows languages > hyphenation > show: Zusam[-||]men[-||]hang languages > hyphenation > show: anderswo languages > hyphenation > show: anders[-||]wo[-||]her Now with LaTeX and Babel: \documentclass{article} \usepackage[ngerman]{babel} \begin{document} \showhyphens{Zusammenhang} \showhyphens{anderswo} \showhyphens{anderswoher} \end{document} This shows [] \TU/lmr/m/n/10 Zu-sam-men-hang [] \TU/lmr/m/n/10 an-ders-wo [] \TU/lmr/m/n/10 an-ders-wo-her The LaTeX hyphenation points agree with the German Duden dictionary. As none of the words use more than 7-bit ASCII, I think newer pattern changes are not related. Curiously, the same effect already appears with MKII and MKIV from TeXLive 2014, the oldest I had around. I'm also surprised 'anders-wo-her' gets hyphenated but 'anderswo' is not hyphenated at all. I could not reproduce a difference with English words so far. Any ideas? As far as I understand, MKIV/LMTX should use the de-hyph-1996 patterns which LuaLaTeX uses these days too, via hyph-utf8. Thanks, -- Leah Neukirchen <leah(a)vuxu.org> https://leahneukirchen.org/

7 9

What to do when ConTeXt not revealing the error details?
by Joel 31 Oct '22

31 Oct '22

I have a very large document that, when compiled, produces a PDF, but reports the error "mtx-context | fatal error: return code: 1". The PDF can open, but after about 100 pages in, the content starts appearing all in the wrong place. Usually when I compile, it says there is an error, and I just scroll up until I find the details. I've scrolled through the output, and *.log file, but cannot see anything that looks like an error. It could be that just because the document is so long (about 1200 pages), I can't find the error among the huge logs, but I looked through them all carefully. How can I isolate the error when ConTeXt isn't showing it? Is there some setting for showing only errors, or revealing more details about an error? --Joel

3 3

is something wrong with the mailing list?
by Henning Hraban Ramm 30 Oct '22

30 Oct '22

Hi again, I didn’t get any mails from ntg-context between 2022-10-26, 01:52 and my mails now. Was there no activity? (Maybe I was switched off due to bounced mails, because my provider had left outdate the ssl certificate of the mail server...) Hraban

2 2

something’s wrong with \definefontfallback
by Henning Hraban Ramm 30 Oct '22

30 Oct '22

This used to work: \definefontfallback[seguiFB] [file:seguisym.ttf] [0x00000-0xFFFFF] [check=yes,force=no] \definetypeface [contextstart] [ss] [sans] [segoe] [default][fallbacks=seguiFB] (Intention is to take all missing characters from this symbol font.) But with current LMTX, I get: tex error > tex error on line 48 in file env_contextstart.tex: lua error: registered function call [1145]: ...-14/tex/texmf-context/tex/context/base/mkxl/math-act.lmt:2339: attempt to perform arithmetic on a nil value (field 'depth') stack traceback: ...-14/tex/texmf-context/tex/context/base/mkxl/math-act.lmt:2339: in local 'action' ...-14/tex/texmf-context/tex/context/base/mkxl/math-act.lmt:3166: in upvalue 'applytweaks' ...-14/tex/texmf-context/tex/context/base/mkxl/math-act.lmt:3200: in upvalue 'mathematics_tweakaftercopyingfont' [string "local mathematics_tweakaftercopyingfont = mat..."]:5: in local 'runner' ...-14/tex/texmf-context/tex/context/base/mkxl/font-ctx.lmt:504: in field 'aftercopyingcharacters' ...-14/tex/texmf-context/tex/context/base/mkxl/font-con.lmt:859: in field 'scale' ...-14/tex/texmf-context/tex/context/base/mkxl/font-otl.lmt:672: in function <...-14/tex/texmf-context/tex/context/base/mkxl/font-otl.lmt:664> (...tail calls...) ...-14/tex/texmf-context/tex/context/base/mkxl/font-def.lmt:378: in function <...-14/tex/texmf-context/tex/context/base/mkxl/font-def.lmt:366> (...tail calls...) ...-14/tex/texmf-context/tex/context/base/mkxl/font-def.lmt:484: in field 'read' ...-14/tex/texmf-context/tex/context/base/mkxl/font-ctx.lmt:1371: in function <...-14/tex/texmf-context/tex/context/base/mkxl/font-ctx.lmt:1228> (...tail calls...) 43 \usetypescriptfile[contextstart] 44 \usebodyfont[modern] 45 \usebodyfont[cambria] 46 \usebodyfont[segoe] 47 48 >> \setupbodyfont[contextstart,10pt] Hraban

2 2

Undefined control sequence \bodyfontsizevariable
by Henning Hraban Ramm 30 Oct '22

30 Oct '22

Latest LMTX, probably an error in mkxl/s-fonts-show.mkxl: \starttext \showbodyfont \showbodyfontenvironment % error! As you can see, the font class is called \quotation{\fontclass} and the bodyfont is typeset from \quotation{\fontname\font} in \the\globalbodyfontsize. \stoptext Hraban

1 0

"true" units in LuaMetaTeX
by Max Chernoff 27 Oct '22

27 Oct '22

Hi Hans, The unit scanner in LuaMetaTeX fails for any of the "true" dimensions. With this test file: \starttext \vrule width 1truein height 1pt depth 0pt\relax \vrule width 1in height 1pt depth 0pt\relax \stoptext I get this output: tex error > tex error on line 2 in file ./lmtx-true.tex: Valid keyword expected, likely 'true' <line 3.2> \vrule width 1truei n height 1pt depth 0pt\relax 1 \starttext 2 >> \vrule width 1truein height 1pt depth 0pt\relax 3 4 \vrule width 1in height 1pt depth 0pt\relax 5 \stoptext 6 I was able to fix this with the patch at the end of the email. (Also, how do you want patches sent? Via email to the mailing list, emailed directly to you, as a pull request on GitHub, or something else?) Thanks, -- Max -- >8 -- >From 69f186daa9b3bf53697e6edf1bd9b066d64b35fe Mon Sep 17 00:00:00 2001 From: Max Chernoff <49086429+gucci-on-fleek(a)users.noreply.github.com> Date: Wed, 26 Oct 2022 23:45:19 -0600 Subject: [PATCH] Fix scanning of "true" units --- source/tex/texscanning.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/tex/texscanning.c b/source/tex/texscanning.c index 7f78d80..98a9c41 100644 --- a/source/tex/texscanning.c +++ b/source/tex/texscanning.c @@ -2304,6 +2304,7 @@ typedef enum scanned_unit { static int tex_aux_scan_unit(halfword *num, halfword *denom, halfword *value, halfword *order) { + AGAIN: do { tex_get_x_token(); } while (cur_cmd == spacer_cmd); @@ -2327,7 +2328,6 @@ static int tex_aux_scan_unit(halfword *num, halfword *denom, halfword *value, ha goto BACK_TWO; } cur_cs = save_cur_cs; - AGAIN: switch (chrone) { case 'p': case 'P': switch (chrtwo) { -- 2.37.3

2 3

\autoinsertnextspace regression / discrepancy, mkiv to lmtx
by Rik Kabel 27 Oct '22

27 Oct '22

The following example produces different results when processed by LMTX and MkIV. In particular, a space between the X and Y is not auto-inserted by LMTX, while it is by MkIV. \starttexdefinition TEST #1 #1\autoinsertnextspace \stoptexdefinition \tt \starttext \TEST{X} \emph{Y} \stoptext The MkIV result is the correct result (in my opinion). -- Rik

3 3

Missing parinitskips in \normalizelinemode=0
by Max Chernoff 27 Oct '22

27 Oct '22

Hi Hans, When running in \normalizelinemode=0, the \parinitleftskip and \parinitrightskip nodes are either nonexistant or invisible from Lua, causing tex.linebreak to not work correctly. This sample file: \enabledirectives[system.callbacks.permitoverloads] \normalizelinemode=0 \directlua{ callback.register("pre_linebreak_filter", function(head) tex.preparelinebreak(head) local list, info = tex.linebreak(head) print(info) return head end) } \starttext \input knuth \stoptext Produces this output: luatex warning > linebreak: list seems already prepared luatex warning > linebreak: [ leftinit | rightinit | leftfill | rigthfill ] expected nil Thanks, -- Max

2 2