July 2020 - ntg-context - NTG Mailing Lists

lmtx update
by Hans Hagen 03 Aug '20

03 Aug '20

Hi, Sorry for the long mail ... One of the changes in lmtx is that we freeze the properties that determine the paragraph shape as well as breaking into lines in such a way that we have predictable behaviour. As a side effect it can be that existing code (lmtx only) will behave differently (will be fixed when we notice) but also that some low level user tweaking can not work, i.e. they are just ignored, but only when they happen mid paragraph which actually is always debatable anyway. Now, if for some reasom you get unexpected results and can't wait for a fix, you can do this: \forgetparagraphfreezing : disables \setparagraphfreezing : enables (default) Of course it might have other side effects once in lmtx we everywhere expect freezing to be enabled. You can take a snapshot with: \freezeparagraphproperties : snapshot relevant parameters \defrostparagraphproperties : resets snapshot More efficient is snapshotting a subcategory: \updateparagraphproperties : all \updateparagraphpenalties : only penalties \updateparagraphdemerits : other than penalties \updateparagraphshapes : hangindent etc Don't use the low level commands that they use because we take plenty of time to experiment at that level and interfaces might evolve, for instance: \frozen\hangindent 30pt \frozen\hangafter 2 is valid and will likely stay. We're talking of a conceptually rather different approach. Internally the engine is still doing the same things but we can control it a bit differently. Due to the way ConTeXt is set up, we can make such a paradigm shift without too much troubles. I'll wrap up more details in an article later. Other work in progress is: better columns in itemize, esp proper footnote support (not that I ever need that but I know users do so ...), experiments work ok, but I need to check spacing. In general, footnotes (will) behave a bit better, especially those used nested in other mechanisms. A side effect of more control is that we can do other tricks too and we're playing with it (kind of fun). More work in progress concerns paragraph wrappers and that will result in a rewrite of some existing mechanism (generic subsystems with instances), but that might as well go unnoticed. To give an idea of possibilities, here is an example: \definedescription[whatever][alternative=right:bottom] \startwhatever{just a small\\example} \input ward \stopwhatever No one ever requested it so see it an a quick and dirty example but don't hesitate to ask for more anyway (we like an occasional challenge). Anyway, it might take some weeks / iterations before all this settles down and now you can't say that we didn't warn you. So far, 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 -----------------------------------------------------------------

6 13

handle_error_hook in LuaMetaTeX
by Marcel Fabian Krüger 01 Aug '20

01 Aug '20

Hi, thanks for handling f file consition in LuaMetaTeX. While playing with that, I encountered a potential bug in the latest LuaMetaTeX version: If handle_error_hook is executed and returns any number, LuaMetaTeX segfaults. (I'm pretty sure that this still worked with the previous version) Minimal ConTeXt example: \enabledirectives[system.quitonerror=false] \directlua{ print(callbacks.register('handle_error_hook', function(...) return 3 end)) } \undefined % Trigger an error \starttext \stoptext This triggers [...] system > ConTeXt ver: 2020.07.31 10:20 LMTX fmt: 2020.7.31 int: english/english [...] tex error > tex error on line 7 in file ./test_empty_input.tex: ! Undefined control sequence l.7 \undefined [...] 9 \stoptext segmentation fault (core dumped) /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex cont-yes.mkiv valgrind suggests that this is caused by an attempt to access a null pointer: ==382632== Invalid write of size 4 ==382632== at 0x1A581F: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x1A662F: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x14BAA8: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x1DA50E: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x1DA802: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x15F956: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x156E2E: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x121E97: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x4A16001: (below main) (in /usr/lib/libc-2.31.so) ==382632== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==382632== ==382632== ==382632== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==382632== Access not within mapped region at address 0x0 ==382632== at 0x1A581F: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x1A662F: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x14BAA8: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x1DA50E: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x1DA802: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x15F956: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x156E2E: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x121E97: ??? (in /home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatex) ==382632== by 0x4A16001: (below main) (in /usr/lib/libc-2.31.so) That me know if you are interested in the coredump. Best regards, Marcel

2 1

Alphabet & color
by Marcus Vinicius Mesquita 01 Aug '20

01 Aug '20

Dear list I need to typeset a book for kids wich contains texts where each letter is assigned a fixed color, for example: A - - > red; B - - > blue; ... Z - - > green. What would be the best way to do this? TIA. Marcus Vinicius

2 9

About testing rest of space on a page
by Willi Egger 30 Jul '20

30 Jul '20

Good evening! I have a bookproject in which sections are ended with a small graphical element. Now as usual this graphic might be moved to a new page which is of course unwanted. At this moment I have: \startsetups endsection \vfil \placefigure[middle,none][]{}{\externalfigure[ornament2][height=2\lineheight]} \stopsection \stopsetups \def\stopmysection{\setups{endsection}} I use then instead of \stopsection the \stopmysection. This works except that the ornament is in some cases placed on the next page. — My question is whether it is possible to do a \testpage and evaluate the result hereof and then using either the placement of the ornament and stop the section or just end the section without ornament? Kind regards Willi

3 3

Re: [NTG-context] ntg-context Digest, Vol 193, Issue 65
by Jan Hansen 30 Jul '20

30 Jul '20

Help > On 31 Jul 2020, at 5:26 am, ntg-context-request(a)ntg.nl wrote: > > Send ntg-context mailing list submissions to > ntg-context(a)ntg.nl > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.ntg.nl/mailman/listinfo/ntg-context > or, via email, send a message with subject or body 'help' to > ntg-context-request(a)ntg.nl > > You can reach the person managing the list at > ntg-context-owner(a)ntg.nl > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of ntg-context digest..." > > > Today's Topics: > > 1. Re: Installing VSCode extension? (Henning Hraban Ramm) > 2. Re: Installing VSCode extension? (Henning Hraban Ramm) > 3. Unknown script 'fonts.lua' or 'mtx-fonts.lua' > (Marcus Vinicius Mesquita) > 4. Re: Unknown script 'fonts.lua' or 'mtx-fonts.lua' (Hans Hagen) > 5. Re: Unknown script 'fonts.lua' or 'mtx-fonts.lua' > (Marcus Vinicius Mesquita) > 6. Re: Unknown script 'fonts.lua' or 'mtx-fonts.lua' (Aditya Mahajan) > 7. Re: About testing rest of space on a page (Wolfgang Schuster) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 30 Jul 2020 12:25:34 +0200 > From: Henning Hraban Ramm <texml(a)fiee.net> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Subject: Re: [NTG-context] Installing VSCode extension? > Message-ID: <4ECE59FD-6C48-4B38-BEA3-68EE3D0441B6(a)fiee.net> > Content-Type: text/plain; charset=utf-8 > > >> Am 30.07.2020 um 07:52 schrieb Jeong Dal <haksan(a)me.com>: >> >> Dear Alasdair McAndrew, >> >> I am using vscode in iMac, so my setting may not work for you. >> >> >> >> 1. First, find files for vscode in your TeX folder. >> >> In my case, >> >> /ConTeXt-homefolder/tex/texmf-context/context/data/vacode/extensions/context/*.* >> >> 2. In a homefolder, there is a hidden folder “.vacode”. >> >> Copy context/*.* to ./vscode/extensions/context/*.* >> >> 3. Open vscode and enable context-extension. >> >> Since it was long time ago, my memory may not be correct. >> However, I hope that it may give you an idea. > > It might make sense to not copy the files but symlink the folder (then it automatically receives updates). > i.e. > ln -s $TEXROOT/texmf-context/context/data/vacode/extensions/context ~/.vscode/extensions/ > > Don’t know how symlinking in Windows works, though. > > HR > > ------------------------------ > > Message: 2 > Date: Thu, 30 Jul 2020 12:33:29 +0200 > From: Henning Hraban Ramm <texml(a)fiee.net> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Subject: Re: [NTG-context] Installing VSCode extension? > Message-ID: <A395BFDC-5328-4065-A57F-3684189713AF(a)fiee.net> > Content-Type: text/plain; charset=utf-8 > > > >> Am 30.07.2020 um 03:57 schrieb Alasdair McAndrew <amca01(a)gmail.com>: >> >> Thanks again, I've fiddled with SciTE, but when I attempted to compile a context file, I was told that "texexec" wasn't in my path, so somehow, somewhere, I must have picked up an old version of the compile command. Also, there doesn't seem to be an easy way of getting SciTE to use a monospaced font. > > Did you read $TEXROOT/texmf-context/context/data/scite/context/documents/scite-context-readme.pdf ? > > I don’t know if that answers your questions and if it’s still current. > > HR > > ------------------------------ > > Message: 3 > Date: Thu, 30 Jul 2020 12:03:48 -0300 > From: Marcus Vinicius Mesquita <marcusvinicius.mesquita(a)gmail.com> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Subject: [NTG-context] Unknown script 'fonts.lua' or 'mtx-fonts.lua' > Message-ID: > <CAK9ODgRtyKRd+TsAhv5fbaz6+53CDZG=wwh5tNAcoVeDk2zAJw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Dear List, > > After updating ConTeXt to the last version, the command: > > mtxrun --script fonts > > replies: > mtxrun | unknown script 'fonts.lua' or 'mtx-fonts.lua' > > mtxrun --version gives: > > mtxrun | ConTeXt TDS Runner Tool 1.32 > > Greetings > > Marcus Vinicius > -- > Todas as coisas fatigam o corpo, salvo a música, que não fatiga nem o corpo > nem seus membros, por ser descanso da alma, primavera do coração, distração > do aflito, entretenimento do solitário, e viático do viajante. > > Kunnâsh al-Hâ'ik (Cancioneiro de al-Hâ'ik) >

2 1

Unknown script 'fonts.lua' or 'mtx-fonts.lua'
by Marcus Vinicius Mesquita 30 Jul '20

30 Jul '20

Dear List, After updating ConTeXt to the last version, the command: mtxrun --script fonts replies: mtxrun | unknown script 'fonts.lua' or 'mtx-fonts.lua' mtxrun --version gives: mtxrun | ConTeXt TDS Runner Tool 1.32 Greetings Marcus Vinicius -- Todas as coisas fatigam o corpo, salvo a música, que não fatiga nem o corpo nem seus membros, por ser descanso da alma, primavera do coração, distração do aflito, entretenimento do solitário, e viático do viajante. Kunnâsh al-Hâ'ik (Cancioneiro de al-Hâ'ik)

3 3

Installing VSCode extension?
by Alasdair McAndrew 30 Jul '20

30 Jul '20

I am installing the Windows version of ConTeXt, which comes with a VSCode extension, in <ConTeXt>\tex\texmf-context\context\data\vscode\extensions with instructions to run (from within the VSCode terminal): code -- extensions-dir <above directory> -- install-extension context The trouble is that the current ConTeXt installation (as of 65 minutes ago), doesn't seem to contain an extension in the format that VSCode understands. Running that command produces the errors: Installing extensions... Extension 'context' not found. Make sure you use the full extension ID, including the publisher, e.g.: ms-dotnettools.csharp Failed Installing Extensions: context: For what it's worth, I'm running VSCode 1.46.0. How can I install the VSCode ConTeXt extension? Thank you, Alasdair -- https://numbersandshapes.net

4 6

Pagenumbering with \setupcounter[userpagenumber]
by Willi Egger 29 Jul '20

29 Jul '20

Good evening! I am trying to make use of the userpagenumber counter. I have a book at hand, where I need to adjust the start of the pagenumbering. It appears to me, that the \setupcounter[userpagenumber[state=stop] and later the \setupcounter[userpagenumber][state=start,start=7] is not giving the expected result. MWE: % Context file \mainlanguage[en] \usetypescript[termes] \setupbodyfont[termes,9pt] \setuppapersize [A5][A5] \setuppagenumbering[location=,alternative=doublesided] \setupheadertexts [text] [] [\userpagenumber] [\userpagenumber] [{\getmarking[chapter]}] \setupfootertexts [] [\pagenumber] [\pagenumber] [] \setupmakeup[standard][top=,bottom=,doublesided=yes] \setupcounter[userpagenumber][state=stop] \starttext \startstandardmakeup[page=yes,doublesided=yes] \strut \godown[.2\textheight] \rightaligned{Bramble-Bees} \stopstandardmakeup \startstandardmakeup[doublesided=yes,page=yes] \strut \godown[.1\textheight] \startalignment[middle] {\bfb BRAMBLE-BEES AND OTHER} \blank[line] {\bfa by J. HENRI FABRE} \stopalignment \vfill \startalignment[middle] {TRANSLATED BY ALEXANDER TEIXEIRA DE MATTOS, F.Z.S.} \stopalignment \stopstandardmakeup \starttitle[title={TRANSLATOR'S NOTE.}] \input ward \stoptitle \setupcounter[userpagenumber][state=start,number=7] \starttitle[title=Contents] \placelist[chapter] \stoptitle \startchapter[title=Ward] \input ward \stopchapter \startchapter[title=Knuth] \input knuth \stopchapter \stoptext Is this a bug or do I miss something? Kind regards Willi

2 1

Is there a bug in lmt_shade[...=...,...=...]
by Keith McKay 29 Jul '20

29 Jul '20

Hi Has a bug appeared in the command lmt_shade[ ]? This used to work before I upgraded. \setuppapersize [A5, portrait][A4, landscape] \setuparranging[2UP] \starttext \startMPpage StartPage; width := PaperWidth ; height := PaperHeight ; unit := cm ; definecolor [ name = "MyColor1", r = 0.781, g = 0.5, b = 0.5 ] ; definecolor [ name = "MyColor3", r = 1, g = 1, b = 0.7983 ] ; draw lmt_shade [ path = unitsquare xscaled width yscaled height, direction = "up", alternative = "linear", colors = { "MyColor1", "MyColor3" }, ] ; StopPage; \stopMPpage \stoptext The console output gives this: system > system > ConTeXt ver: 2020.07.29 14:08 LMTX fmt: 2020.7.29 int: english/english system > metapost > log > metapost > log > loading metafun, including plain.mp version 1.004 for metafun iv and xl metapost > log > metapost > log > ! Not a cycle. metapost > log > <to be read again> metapost > log > withprescript metapost > log > <argument> ...i.fill.mfun_shade_path.withprescript metapost > log > "sh_domain="&decimal.domai... metapost > log > metapost > log > image->...ture;currentpicture:=nullpicture;(TEXT3) metapost > log > ;currentpicture.if.str(SUF... metapost > log > metapost > log > lmt_do_shade->...shed.evenly;fi.fi.popparameters;) metapost > log > endgroup metapost > log > <scantokens> lmt_do_shade metapost > log > metapost > log > <*> ...ar", colors = { "MyColor1", "MyColor3" }, ] metapost > log > ; StopPage; ; metapost > log > system > print height forced to paper height system > print width forced to paper width Thanks Keith

2 3

Lua related change in LuaMetaTeX?
by Marcel Fabian Krüger 29 Jul '20

29 Jul '20

Hi, starting with LuaMetaTeX 2.07.01, a C library I load from Lua started to segfault and valgrind indicates that it accesses invalid memory in multiple places in the middle of Lua internal functions?! The whole thing looks almost like the Lua versions in LuaMetaTeX and in the library are incompatible, but both seem to use 5.4.0. So I asked myself if there might be changes not reflected by the version number. tl;dr: Has the embedded Lua interpreter changed in some non ABI-compatible way in LuaMetaTeX 2.07.01? (Especially on Linux, x86-64. I didn't test other platforms yet) Best regards, Marcel

2 4