- ntg-context - Mailing Lists

Typesetting Markdown – Part 6: Computation
by Thangalin 11 Jul '19

11 Jul '19

This part of the series describes a way to produce and typeset dynamic documents using R Markdown and ConTeXt. https://dave.autonoma.ca/blog/2019/07/11/typesetting-markdown-part-6/ Comments or suggestions for improvement?

1 0

Strange error updatng LMTX
by Andres Conrado 11 Jul '19

11 Jul '19

When updating my LMTX installation today, I got this: tex error > tex error on line 179 in file /home/conrado/Apps/lmtx/tex/texmf-context/tex/context/base/mkiv/strc-flt.mkvi: ! Undefined control sequence <argument> \c!compressdistance =\emwidth \mult_interfaces_get_parameters_item ...2->\if ,#1 ,\expandafter \mult_interf... \mult_interfaces_get_parameters_indeed ...tem #1,] , \setup_float ...es_get_parameters {\??float :}[#1] \the \everysetupfloat \fi ... <to be read again> \syst_helpers_double_empty_two_nop \par l.179 169 \c!bottomoffset=\zeropoint, 170 \c!freeregion=\v!yes, 171 %\c!local=, 172 %\c!bottombefore=, % e.g. \vfill 173 %\c!bottomafter=, 174 %\c!default=, % default location 175 \c!sidethreshold=.5\strutdp, % set to "old" to check with old method 176 \c!numbering=\v!yes, 177 \c!compress=\v!yes, % when possible pack floats when flushing 178 \c!compressdistance=\emwidth] 179 >> 180 \setupfloatframed 181 [\c!frame=\v!off, 182 \c!offset=\v!overlay, 183 \c!strut=\v!no] 184 185 \appendtoks 186 \doifelse{\floatparameter\c!compress}\v!yes\settrue\setfalse\c_page_floats_pack_flushed 187 \d_page_floats_compress_distance\floatparameter\c!compressdistance\relax 188 \to \everysetupfloat 189 The control sequence at the end of the top line of your error message was never \def'ed. If you have misspelled it (e.g., '\hobx'), type 'I' and the correct spelling (e.g., 'I\hbox'). Otherwise just continue, and I'll forget about whatever was undefined. Seems to affect the floats mechanism. Andrés Conrado Montoya http://chiquitico.org

3 2

Split extreme tables across tables
by Thangalin 11 Jul '19

11 Jul '19

The following document does not split across tables, which is a little surprising: \starttext \startplacetable[title={Average Annual Temperatures}] \startxtable \startxtablehead[head] \startxrow \startxcell[align=middle,width={0.10\textwidth}] Year \stopxcell \startxcell[align=middle,width={0.14\textwidth}] Value \stopxcell \stopxrow \stopxtablehead \startxtablebody[body] \dorecurse{100}{% \startxrow \startxcell[align=middle,width={0.10\textwidth}] 1880 \stopxcell \startxcell[align=middle,width={0.14\textwidth}] 0.1146 \stopxcell \stopxrow} \stopxtablebody \startxtablefoot[foot] \startxrow \startxcell[align=middle,width={0.10\textwidth}] 2018 \stopxcell \startxcell[align=middle,width={0.14\textwidth}] 1.014 \stopxcell \stopxrow \stopxtablefoot \stopxtable \stopplacetable \stoptext I'd have thought the default behaviour would be to split because the alternative is for the table content to scroll into the footer and off the page. A fix is to use: \startplacetable[title={Average Annual Temperatures}, location={split}] However, when the document is generated using pandoc, injecting location={split} is not feasible. It would be convenient if there was a way to use setups to override the location option for \startplacetable. Henri Menke provided a work around: let\oldstartplacetable\startplacetable \unexpanded\def\startplacetable{\dosingleempty\newstartplacetable} \def\newstartplacetable[#1]{\oldstartplacetable[#1,location={split}]} See: https://tex.stackexchange.com/a/499453/2148 This does the job, but it doesn't feel like the ConTeXt way. How would you use setups to enable page splitting on extreme tables? Thank you!

1 2

an object representation of the node list of a paragraph: a lua table or a JSON
by mf 10 Jul '19

10 Jul '19

Hello list, i'd like having an object representation of a typeset paragraph or even a page, preferably as a JSON object, but a Lua table is equally good. My reference is section "4.4 Node lists" of the CLD manual. Before writing an iterator over the list of nodes of a paragraph, figuring out all the possible nodes and their fields, i'm wondering if there's some hidden tool in the ConTeXt coffer to simplify the task. Best wishes, Massimiliano

2 1

Fwd: [garden] debug getinfo error
by Taco Hoekwater 10 Jul '19

10 Jul '19

> Begin forwarded message: > > From: Husum42(a)t-online.de > Subject: [garden] debug getinfo error > Date: 10 July 2019 at 11:52:55 CEST > To: gardeners(a)contextgarden.net > > > There is a lua error after "debug.getinfo()". Why? > > Thanks for help > G.Lauber > > ------------------------- > mtx-context | run 1: luatex --fmt="/opt/context/beta-2018.09.01/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en" --jobname="texweb" --lua="/opt/context/beta-2018.09.01/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.lui" --c:currentrun=1 --c:fulljobname="./texweb.tex" --c:input="./texweb.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:texmfbinpath="/opt/context/beta-2018.09.01/tex/texmf-linux-64/bin" "cont-yes.mkiv" > > This is LuaTeX, Version 1.10.1 (TeX Live 2019) > system commands enabled. > open source > level 1, order 1, name '/opt/context/beta-2018.09.01/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv' > system > > system > ConTeXt ver: 2019.07.04 12:29 MKIV beta fmt: 2019.7.10 int: english/english > system > > system > 'cont-new.mkiv' loaded > open source > level 2, order 2, name '/opt/context/beta-2018.09.01/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv' > system > beware: some patches loaded from cont-new.mkiv > close source > level 2, order 2, name '/opt/context/beta-2018.09.01/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv' > system > files > jobname 'texweb', input './texweb', result 'texweb' > fonts > latin modern fonts are not preloaded > languages > language 'en' is active > open source > level 2, order 3, name '/tmp/uhd8RE/texweb.tex' > fonts > preloading latin modern fonts (second stage) > fonts > 'fallback modern-designsize rm 12pt' is loaded > > lua error > lua error on line 6 in file /tmp/uhd8RE/texweb.tex: > > [ctxlua]:1: attempt to call a nil value (field 'getinfo') > > 1 % generated by live script > 2 \setupexternalfigures[location={local,global,default}] > 3 \starttext > 4 \startlua > 5 debug.getinfo(2) > 6 >> \stoplua > 7 \stoptext > 8 > > mtx-context | fatal error: return code: 256 > > Taco Hoekwater Elvenkind BV

2 1

index page ranges where start page == end page
by Sanjoy Mahajan 10 Jul '19

10 Jul '19

The following probably well known minimal example \starttext \startregister[index][key1]{an entry}\input knuth\stopregister[index][key1] \placeindex \stoptext produces the index entry "an entry 1--1", where the page range should be just a single page. A question (and then two workarounds): Could ConTeXt automatically change such page ranges to the single page ("an entry 1")? Meanwhile, a couple of workarounds: In the MkII (pre-lua) days, I wrote a shell/sed/awk/perl script that converted the .pdf file to text, grepped for (strings that are likely to be) page ranges, and spat out lines where the page range should be a page. (Those days were so long ago that I've forgotten the script's language.) Then I would manually find and change the corresponding \startregister[index] in the source to a plain \index (and delete the corresponding \stopregister). In these MkIV days, with the index data in a lua table, I've been playing with the following python2 script that parse the .tuc file to spit out the same information slightly more reliably. In the next step, coming soon, the script will check that each \seeindex entry points to an actual entry and also that each \seeindex{also ...} entry originates from an actual entry (otherwise it shouldn't be "also"). The script requires the slpp package; pip install git+https://github.com/SirAnthony/slpp The parser in the script has a bug in that it doesn't handle minus signs in the lua table, maybe everywhere or maybe only some of them, so the script replaces them with "_" before sending the data to the parser (a terrible hack). To run the script: python check-index.py < file.tuc Here is check-index.py: # parse lua-format index-entry table extracted from book.tuc to check # that each xref points to an actual entry, and that, further, "see # also" src entries have at least one page ref (perhaps in subtree) # due to bug in slpp parser: replace "-" (minus signs) in data with "_" from slpp import slpp as lua from sys import stdin,stderr import re def tuclist2entry(l): return '+'.join(l) data = [] intro_re = r'utilitydata.structures.registers.collected\s*=' in_register_data = False for l in stdin: if re.match(intro_re, l): in_register_data = True data.append(re.sub(intro_re,'',l)) elif in_register_data: data.append(l) if re.match(r'}$', l): in_register_data = False data = re.sub("-", "_", ''.join(data)) dict = lua.decode(data) index = dict['index'] entries = [] xrefs = [] for entry in index['entries']: src = [x[0] for x in entry['list']] refs = entry['references'] if 'seeword' in entry: dest = entry['seeword']['text'] xrefs.append((src,dest)) else: page = refs['realpage'] if refs.get('lastrealpage',None) == page: print "silly range:", tuclist2entry(src) entries.append(src) for xref in xrefs: print tuclist2entry(xref[0]),'->', xref[1]

1 0

Is it possible to define a float environment that uses 2 captions? (and another question)
by Andres Conrado Montoya 09 Jul '19

09 Jul '19

I'm working on a book that uses tables and figures, but the editors want to use to diffferent captions for each figure: one as usual, with the float description and number, and another one with a "Source" for said float. Something like: --------------------------------- | | | Float | | | --------------------------------- Figure 1: The float description. Source: The float source. I know i can do it by hand, inserting line breaks in the caption and so on. But I was wondering if there is a programmatic way to do it, so I can, for example, change the "Caption" position to be above the float, but have the "Source" below it. LIke: Figure 1: The float description. --------------------------------- | | | Float | | | --------------------------------- Source: The float source. I've been reviewing the Wiki, but so far I have no idea how to approach it. Any recommendation will be very appreciated. Thank you for your time. Andrés Conrado Montoya Andi Kú andresconrado(a)gmail.com http://sesentaycuatro.com http://messier87.com http://chiquitico.org ---------------------------------------- Los fines no justifican los medios, porque la medida verdadera de nuestro carácter está dada por los medios que estamos dispuestos a utilizar, no por los fines que proclamamos. ---------------------------------------- “You develop an instant global consciousness, a people orientation, an intense dissatisfaction with the state of the world, and a compulsion to do something about it. From out there on the moon, international politics look so petty. You want to grab a politician by the scruff of the neck and drag him a quarter of a million miles out and say, ‘Look at that, you son of a bitch.’” — Apollo 14 astronaut Edgar Mitchell

1 0

Re: [NTG-context] Typesetting Markdown – Part 5: Interpolation
by Andres Conrado 09 Jul '19

09 Jul '19

Thank you. I still don't really understand why can't you have a "presentational" yaml file and a "content" yaml file (I do it like that... I have a "variables.yaml" file for content and a "settings.yaml" file for presentational stuff, and use a "template.context" file with all my mapped variables within the ConTeXt code, and compile everything using pandoc). But I guess you want to do it this way. Or maybe I'm not really understanding your process. It's quite interesting in any case, and I'm learning a lot. Thanks for sharing. Andrés Conrado Montoya http://chiquitico.org

1 0

Re: [NTG-context] Typesetting Markdown – Part 5: Interpolation
by Andres Conrado 09 Jul '19

09 Jul '19

You can do it on the template... you can use a yaml variable to determine if the toc should be printed or not. Like so: yaml file: --- toc: true ... template file: %%%%%%% $if(toc)$ \completecontent $endif$ %%%%%%% Andrés Conrado Montoya http://chiquitico.org El lun., 8 jul. 2019 a las 2:52, <ntg-context-request(a)ntg.nl> escribió: > 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: Typesetting Markdown – Part 5: Interpolation > (Aditya Mahajan) > 2. Re: Typesetting Markdown – Part 5: Interpolation (Thangalin) > 3. Re: Typesetting Markdown – Part 5: Interpolation > (Aditya Mahajan) > 4. request for \definefontfamily and \definefallbackfamily > (Pablo Rodriguez) > 5. Re: crappy names in the fontloader (Hans Hagen) > 6. problems with images, layers and crop marks (Henning Hraban Ramm) > 7. Re: problems with images, layers and crop marks (Hans Hagen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 7 Jul 2019 10:17:31 -0400 (EDT) > From: Aditya Mahajan <adityam(a)umich.edu> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Subject: Re: [NTG-context] Typesetting Markdown – Part 5: > Interpolation > Message-ID: <nycvar.YAK.7.76.1907071012590.13567@nqv-guvaxcnq> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > On Sat, 6 Jul 2019, Thangalin wrote: > > > Hello again! > > > > This part of the series describes how to reference *interpolated* strings > > inside Markdown documents. > > https://dave.autonoma.ca/blog/2019/07/06/typesetting-markdown-part-5/ > > > > There's a section at the end about eliminating the table of contents > from a > > reusable document template. I would have preferred using setups, rather > > than redefining the \completecontent macro, but didn't see an obvious way > > to do so. > > Why not simply omit \compltecontent from the pandoc template? > > Aditya > > > > ------------------------------ > > Message: 2 > Date: Sun, 7 Jul 2019 11:58:12 -0700 > From: Thangalin <thangalin(a)gmail.com> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Subject: Re: [NTG-context] Typesetting Markdown – Part 5: > Interpolation > Message-ID: > <CAANrE7qd81BudwSHBWufu=MpDDUPn5fh8ZBM63qLVZ160gZH= > g(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Thank you Aditya. > > The main.tex file is meant to be reusable for different document styles. By > removing \completecontent altogether from the main template, it would > preclude a different document from reusing the main.tex template with a > table of contents. I'd like the template to be "reusable"; making > modifications to "main.tex" --- or creating a copy --- would subvert that > goal. > > On Sun, Jul 7, 2019 at 7:17 AM Aditya Mahajan <adityam(a)umich.edu> wrote: > > > On Sat, 6 Jul 2019, Thangalin wrote: > > > > > Hello again! > > > > > > This part of the series describes how to reference *interpolated* > strings > > > inside Markdown documents. > > > https://dave.autonoma.ca/blog/2019/07/06/typesetting-markdown-part-5/ > > > > > > There's a section at the end about eliminating the table of contents > > from a > > > reusable document template. I would have preferred using setups, rather > > > than redefining the \completecontent macro, but didn't see an obvious > way > > > to do so. > > > > Why not simply omit \compltecontent from the pandoc template? > > > > > > >

2 1

interfaces.definecommand fails with brackets inside string arguments
by mf 09 Jul '19

09 Jul '19

Hello list, i've played a bit with interfaces.definecommand, that lets you define TeX macros from lua (see the "ConTeXt Lua Documents", 7.3 User interfacing). I found that the commands defined by interfaces.definecommand fail when you pass string arguments that contain brackets. I think cldf-int.lua needs a patch to support those kind of arguments. In the meantime it's possible to bypass the problem passing arguments with brackets inside double braces, as in the MWE attached. Best wishes, Massimiliano

3 3