ntg-context January 2019

ntg-context@ntg.nl

43 participants
71 discussions

Setup typing indent next
by Hans Åberg 10 Jan '19

10 Jan '19

There seems to be no option for \setuptyping[indentnext=...] following the TeX convention to indent new paragraphs, as followed by a blank row, but not otherwise.

2 4

issue with backend.date
by Pablo Rodriguez 10 Jan '19

10 Jan '19

Dear list, I have the following sample: \enabledirectives[backend.date=no] \enabledirectives[backend.info=no] \enabledirectives[backend.xmp=no] \starttext a \stoptext At least, backend.date doesn’t work with latest beta (2019.01.07 16:10) as it used to work before. I think this might be a bug. Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

local ToC after each chapter title
by Henning Hraban Ramm 10 Jan '19

10 Jan '19

Hello again, in my current book project I need a local ToC after each chapter title. What’s wrong with my use of "after"? The following example leads to a "TeX capacity exceeded" error: \setupcombinedlist[content][% list={chapter,section},] \setuplist[chapter][ before=, after={\placecombinedlist[content][criterium=local]},] \starttext \completecontent \chapter{One} \section{Knuth} \input knuth \section{Tufte} \input tufte \chapter{Two} \section{Tufte 2} \input tufte \chapter{Three} \section{Zapf} \input zapf \stoptext (MkIV, version 2018.12.19 19:22) Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD

2 2

final thoughts on experiments with lua
by Thomas A. Schmitz 10 Jan '19

10 Jan '19

I've finished testing my lua script, and it does exactly what I need. I think I'll write a small article about it for one of the next context group proceedings, but wanted to just give a very brief summary that might be of interest to some: Pure Lua is wonderful, but as the language is deliberately kept very small, one sometimes has to find rather cumbersome workarounds. If you run Lua under ConTeXt (with mtxrun --script), you get a version with batteries included, which is perfect for manipulating and analyzing text. Some areas that I found particularly impressive: 1. I've tried several times to make use of lpegs. Hans' code is full of it, and I know that it's fast and extremely versatile, but I found it difficult to wrap my head around its functioning and write useful code with lpegs. The ConTeXt wrapper makes this extremely easy; this is lpeg for the rest of us. It's really a delight to build patterns and see them work immediately! 2. The utf library and string manipulation with characters.(...) is absolutely necessary if you want to handle non-ASCII text because pure Lua gives very unexpected results in this area. These operations work wonderfully with the context libraries. 3. Lua's handling of tables is very efficient and fast. For analyzing my Greek texts, I have to use huge tables for morphological parsing, with more than 900,000 entries. Looking up words in these tables is around 3x faster in Lua than in python! One final thought: one limitation that I still find cumbersome to work around is the fact that associative arrays ("pairs" in Lua speak) do not have an order. When I analyze my texts, I want book numbers, chapters, paragraphs preserved in the order in which they are read (entered into the table). In many cases, it is not possible (or extremely awkward) to sort these numbers, since chapters may be numbered something like 2, 2a, 3, 3α, 3β etc. python has the OrderedDict() in its collections module. In Lua, the best I could find was entering the chapter numbers into an array (ipair) and then retrieve it from there. Maybe there is a better way? All of this just to say how grateful I am for the way Hans, Taco, Wolfgang, Luigi, and the other developers have enhanced Lua. Thanks guys, you make my work much more pleasant and efficient! Thomas

6 10

further experiments with lua
by Thomas A. Schmitz 09 Jan '19

09 Jan '19

Hi Hans, I'm doing some further experiments with the utf and lpeg libraries. This code fails, and I don't understand why: local s = "Ä" print(characters.uccode(s)) mtxrun --script test.lua ./test.lua:3: attempt to index global 'characters' (a nil value) Thomas

3 3

nice overview of tex
by Hans Hagen 09 Jan '19

09 Jan '19

Hi, There are two extensive historic articles on tex here: http://walden-family.com/ieee/texhistory.html -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

2 1

Fwd: issue: multiple viewer layers
by User 19087 08 Jan '19

08 Jan '19

Layers are not properly closed when using more than one layer, so that each layer subsumes all subsequent content. Tested in Adobe Reader 11. I first mentioned this at https://tex.stackexchange.com/a/467005/174577, so I'm basically rehashing all the examples: When \showallmakeup is enabled, all content after \viewerlayer[print] belongs to that layer: \defineviewerlayer[print][state=stop,printable=yes,] \showallmakeup \starttext \viewerlayer[print]{One} more. \samplefile{knuth} \stoptext The same problem as above, demonstrated with \start...stopviewerlayer rather than \viewerlayer: \defineviewerlayer[print][state=stop,printable=yes,] \showallmakeup \starttext \startviewerlayer[print] And then: \stopviewerlayer \samplefile{knuth} \stoptext Rather than two independent layers, the print layer (along with other content) belongs to the view layer. So hiding the view layer hides all content in this document: [view] --- first --- \samplefile{knuth} --- [print] ------ second \defineviewerlayer[print][state=stop,printable=yes,] \defineviewerlayer[view][state=start,printable=no,] \starttext \startviewerlayer[view]{first} \samplefile{knuth} \startviewerlayer[print]{second} \stoptext

2 2

Get list of all buffer names from lua
by Stanislav Sokolenko 08 Jan '19

08 Jan '19

Dear list, As the subject line states, I am looking for a means of retrieving a table of all saved buffer names from lua. A MNWE would looks like: \starttext \startbuffer[ex1] Buffer 1 \stopbuffer \startbuffer[ex2] Buffer 2 \stopbuffer % Should return {ex1, ex2} or similar \ctxlua{context(...)} \stoptext The underlying idea is to store a large number of example problems in individual buffers that could be retrieved either by specific name or as a complete list. I'm having a problem with the latter as it seems like all the lua buffer commands I've encountered assume that buffer names are known in advance: buffers.getcontent(b) buffers.raw(b) buffers.getlines(b) buffers.erase(b) buffers.assign(b, text, catcodes) buffers.append(b, text) buffers.exists(b) buffers.collectcontent(names, seperator) Thanks, Stan

3 5

Process file with '#' in the file name
by Procházka Lukáš Ing. 07 Jan '19

07 Jan '19

Hello, is there a way to process a file with '#' in the file name by ConTeXt? E.g. file "T#.mkiv" with \starttext A \stoptext fails - not so surprisingly; but anyway - is there a way or "trick" to process it? Bets regards, Lukas

1 0

Update problems
by Weber, Matthias 07 Jan '19

07 Jan '19

Dear List, After a while I decided updating my ConTeXt installation to ConTeXt ver: 2019.01.07 10:07 MKIV beta fmt: 2019.1.7. With an old document of mine I ran into two issues so far: Some of my old pdf images are not accepted as figures anymore. Example: \starttext \externalfigure[cardioid.pdf][width=1.5in]{Cardioid} \stoptext Using the following pdf which is version 1.4

4 4

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context January 2019