October 2020 - ntg-context - NTG Mailing Lists

Which version of MkIV should we use?
by Rik Kabel 28 Oct '20

28 Oct '20

Hello all, I have noticed some differences between the MkIV installed as part of LMTX and the MkIV installed via first-setup. Which should be used going forward when one wants to use MkIV? (One difference: \contextkind is defined in file context.mkiv installed via first-setup. It is not defined in the file of the same name installed as part of LMTX. Another, more significant difference, is loading modules.) -- Rik

2 3

troubles with cutafter
by Damien Thiriet 27 Oct '20

27 Oct '20

Hello, I went into some troubles with cutafter. Must have missed something obvious. \starttext \startMPpage path p[]; p1:= origin -- (100,0); p2:= (50,-50) -- (50,100); draw p1; draw p2; draw (p1 cutafter (p1 intersectionpoint p2)) withcolor red; \stopMPpage \stoptext Can someone explain me why the whole path p1 of this MWE is in red? I expected only its first half to be in red, and the whole line is. Thanks, Damien Thiriet

2 1

Bug(s)(?) in \processwords (Mark IV)
by Jairo A. del Rio 27 Oct '20

27 Oct '20

The following: \starttext \unexpanded\def\lol#1% { \begingroup \let\processword\inframed \processwords{#1}% \endgroup } \lol{nice $x^2$} %see what happens with the superscript \stoptext works with ConTeXt LMTX, but fails with ConTeXt MkIV: ...mtx/tex/texmf-context/tex/context/base/mkiv/attr-ini.lua:144: attempt to call a nil value (upvalue 'currentattributes') stack traceback: ...mtx/tex/texmf-context/tex/context/base/mkiv/attr-ini.lua:144: in function <...mtx/tex/texmf-context/tex/context/base/mkiv/attr-ini.lua:142> (...tail calls...) In both cases, including inline math gives funny outputs. Regards, Jairo :)

1 0

Re: [NTG-context] Fw: statistical charts (was: Changing the colors of Charts in luametafun)
by Tamara Kocurova 26 Oct '20

26 Oct '20

Hi Jan, Thank you for noticing! Probably the fastest way to fix this would be making the dots more dense. We will add a parameter for that in the near future (it is also possible to add it directly to the code). Best, Tamara ---------- Forwarded message ---------- > From: "Jan U. Hasecke" <juh+ntg-context(a)mailbox.org> > To: ntg-context(a)ntg.nl > Cc: > Bcc: > Date: Mon, 19 Oct 2020 20:16:16 +0200 > Subject: [NTG-context] statistical charts (was: Changing the colors of > Charts in luametafun) > > Hi all, > > I play around with the charts module by Tamara Kocurová & Adriana > Kašparová. Great work! I really like it. > > https://akela.mendelu.cz/~thala/statcharts/ > > There is one very nitpicking thing. The dots of the grid are not always > in a regularly fixed distance as the attached screenshot shows. > > I am not sure if this can be solved with a customized configuration. > > Ciao! > juh > > > > ___________________________________________________________________________________ > If your question is of interest to others as well, please add an entry to > the Wiki! > > maillist : ntg-context(a)ntg.nl / > http://www.ntg.nl/mailman/listinfo/ntg-context > webpage : http://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : http://contextgarden.net > > ___________________________________________________________________________________ > >

1 0

MkIV and LMTX difference in comma list expansion
by Rik Kabel 26 Oct '20

26 Oct '20

Hello list, Another difference, perhaps the result of my lack of knowledge, but a difference. The following example produces different results for the fourth sequence, with the index being passed one item under MkIV and two items under LMTX. (The code is stripped out of a much more complex bit to show the issue.) % macros=mkvi \starttexdefinition unexpanded startBlockQuotation \dosingleempty\dostartBlockQuotation \stoptexdefinition \starttexdefinition dostartBlockQuotation [#SETUPS] \getrawparameters[BlockQuotation] [index=,#SETUPS] \expandafter\processcommalist \expandafter[\BlockQuotationindex]\doIndexIt{} \stoptexdefinition \starttexdefinition stopBlockQuotation \stoptexdefinition \starttexdefinition doIndexIt #INDEXTERM indexer sees #INDEXTERM\ \index{#INDEXTERM} \stoptexdefinition \starttext \startBlockQuotation[index=aaa] \startparagraph 1 \quad when indexing aaa. \stopparagraph \stopBlockQuotation \startBlockQuotation[index={aab}] \startparagraph 2 \quad when indexing \{aab\}. \stopparagraph \stopBlockQuotation \startBlockQuotation[index={aac, aad}] \startparagraph 3 \quad when indexing \{aac, aad\}. \stopparagraph \stopBlockQuotation \startBlockQuotation[index={{aae, aaf}}] \startparagraph 4 \quad when indexing \{\{aae, aaf\}\}. \stopparagraph \stopBlockQuotation \startBlockQuotation[index={{{aag, aah}}}] \startparagraph 5 \quad when indexing \{\{\{aag, aah\}\}\}. \stopparagraph \stopBlockQuotation \startBlockQuotation[index={{aai, aaj},{aak, aal}}] \startparagraph 6 \quad when indexing \{\{aai, aaj\},\{aak, aal\}\}. \stopparagraph \stopBlockQuotation \startBlockQuotation[index={{{aam, aan}},{{aao, aap}}}] \startparagraph 7 \quad when indexing \{\{\{aam, aan\}\},\{\{aao, aap\}\}\}. \stopparagraph \stopBlockQuotation \placeindex \stoptext Did I misuse the comma list processing, or is this a bug? -- Rik

2 1

marvosym on the wiki
by Mojca Miklavec 26 Oct '20

26 Oct '20

Hi, Someone asked me a question about marvosym In LaTeX (I just pointed him to the documentation), but then I checked the wiki and noticed that the wiki page is showing latin modern for \showfont[fmvr8x] https://wiki.contextgarden.net/Symbols/mvs What would be the correct syntax for the wiki nowadays? Thank you, Mojca

2 2

Concerning text backgrounds (and further tuning) in references
by Jairo A. del Rio 24 Oct '20

24 Oct '20

Hi, list! I've seen the following question in TeX.SE. My attempt of solving was: https://tex.stackexchange.com/questions/567655/change-background-color-of-h… \setupinteraction [state=start]\definetextbackground[MyUrl] [ location=text, background=color, backgroundcolor=yellow, frame=off, ]\def\myfootnote#1{\MyUrl{\high{#1}}} \setupfootnotes[textcommand=\myfootnote] \definepapersize[default][A8,portrait]\setuppapersize [default]\useURL[aurl] [https://wiki.contextgarden.net] [] [\MyUrl{ConTeXt Garden}]\starttext Testing links to same page\footnote{This should create links to same page} and an external link: \from[aurl].\stoptext When one tries to use `\setupinteraction[...style=\MyUrl...]` either it doesn't work or displays a background which doesn't break well across lines. Is there a workaround or another method? Maybe a feature request for a more customizable setup for references? I had the same problem some time ago and I guess some others too. Thank you in advance, Jairo :)

2 2

space between chapter and chapter number (in words)
by jbf 24 Oct '20

24 Oct '20

I wonder if someone could explain to me what controls (or how to control) the space between Chapter and chapter number in my TOC given the setup I have. At the moment I get ChapterOne instead of Chapter One, and I do not know what is causing that. Here is my set up (at least all the parts that I think are controlling the appearance of Chapter Number in the TOC). Am I missing something? I thought perhaps the third line in the ChapterListCommand below might be what controls this, so I did try adding \hskip 1em (or 2em etc.) in the \currentlistsymbol section of that line, but it did nothing to solve the problem: \define[3]\ChapterListCommand {\hbox\bgroup \hbox to 2.5cm{\currentlistsymbol\hss}% number + labeltext \vtop\bgroup \hsize\dimexpr\makeupwidth-2.5cm\relax \doifsomething{\rawstructurelistuservariable{year}} {{\structurelistuservariable{year}}\crlf}% \currentlistentrytitle % title \doifsomething{\rawstructurelistuservariable{author}} {\crlf{\structurelistuservariable{author}}}% \hfill\currentlistentrypagenumber % pagenumber \egroup \egroup} \setuplabeltext [en] [ chapter=\bf Chapter , ] \setuplist [chapter] [label=yes, alternative=command, command=\ChapterListCommand] Julian

2 1

Filler rules
by Willi Egger 22 Oct '20

22 Oct '20

Good afternoon! I am dealing with a book, which has a short black rule under the title of the chapters. I see, that the old rule mechanisms are no more available in LMTX and are replaced by fillers. Now with the following setup, I would expect a 50mm line placed centered. Hoewever this seems not to work in this way. What am I missing? kind regards Willi \definefiller [Titlerule] [alternative=rule, left=\hfil, right=\hfil, method=local, width=50mm, height=2pt, leftmargin=1pt, rightmargin=1pt, align=middle] \starttext \midaligned{Some text} \filler[Titlerule] \stoptext

2 4

lmts status
by Hans Hagen 22 Oct '20

22 Oct '20

Hi, There haven't been lmtx updates for while now but there is a reason for it. On my machine I have luametatex 2.08 (so we jump number) which is in terms of typesetting the 20201010 version. That version has some reorganized internals, most have to do with consistency in the token interface at the Lua end. Of course there are some new and improved things too but those will be revealed in articles or manuals or the development status documents (already on my machine but they need checking). However, around that date I also decided to play a bit with some pending features: extended macro definitions and frozen macros. The first has to do with extensions to the macro definition code. Some are already present for a while, others have been added. The challenge there is to make defining macros somewhat more convenient and at the same time get rid of often too confusing error messages when a user does something bad with arguments (those foo_bar_whatever kind of things which might look impressive but often is pretty ugly). Of course that only makes sense when we keep the current performance: only gain, no pain. But, it also means that we need to adapt quite some code in order to benefit from it and when I started doing that one quickly ends up in a chain reaction: from a dozen files to over 100 and fives times that amount pending. But it's actually kind of fun (also for users I think). And hopefully Wolfgang will find my many errors. In parallel I played with the other feature: some kind of protection against macro abuse. This is actually related to the above because when you want to see macros with readable names in error messages, you cannot protect them with underscores and other ugly tricks that at the same time make stuff unreadable and ugly. We have a chicken and egg issue there. Anyway, the reason for this mail is that I want to warn users that the next lmtx release will use several protection mechanisms. Checking will for now be off by default but one can bump the level of protection at runtime. Just to give you an idea: we have primitives that can get a heavy protection against overload. We also have macro package system commands and these can get a pretty hard protection too. Commands defined by users (using \define...) can be treated less strict. Of course we also have all kind of runtime (temporary) macros that we have to protect (freeze) but also be able to redefine when we want to (think of variables). Then we have properties that are not primitives but nevertheless need the same strong protection, think of predefined counters, dimensions etc. So, you can imagine that there is some work involved in getting all that up and running. A side effect of that is that occasionally I notice some undesired hack or something that needs attention. The good news is that this probably can be pulled off without a real hit on performance. However, one side effect is that when users enable this (off by default) mechanism the might run into messages (when only warnings are enables) or errors (when they go for the full package). Now, in order to get this working well (as intended) I'd like users who then run into issues to make small examples that we we add to the test suite (unless of course they decide to fix the style, simply because they figure that they did something wrong). You're warned. So, when the next lmtx hits the web, make sure that you keep the old tree because one never knows where I mess up. I don't know when I'll upload. After all Wolfgang and I need to come to the conclusion that it's the way to go. More later, Hans PS. When doing this one runs into quite interesting conceptual issues, even in a system like context that is rather structured. But this is also why the final solution needs somewhat more work that one thinks when one starts with it. A macro language like tex is quite different from some regular programming language (and making it look like one doesn't help). ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

1 0