July 2019 - ntg-context - NTG Mailing Lists

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 09 Jul '19

09 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

Typesetting Markdown – Part 5: Interpolation
by Thangalin 08 Jul '19

08 Jul '19

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. Thoughts?

2 4

From mkii to mkiv: MathML mtable alignment
by Duncan Hothersall 08 Jul '19

08 Jul '19

The command \setupMMLappearance[mtable][alternative=b] used to give me, in mkii, MathML layouts in which the first column was ragged left, the second column centred, and the third column ragged right. It now seems to be ignored, and the output has all three columns centred. Minimal working example showing the problem: \usemodule[mathml] \setupMMLappearance[mtable][alternative=c] \starttext Some text. \xmlprocessdata{}{<formula> <math xmlns='http://www.w3.org/1998/Math/MathML'> <mtable> <mtr> <mtd> <mi>x</mi> <mo>+</mo> <mi>y</mi> </mtd> <mtd> <mo>=</mo> </mtd> <mtd> <mn>2.56</mn> <mtext> million</mtext> </mtd> </mtr> <mtr> <mtd> <mi>x</mi> </mtd> <mtd> <mo>=</mo> </mtd> <mtd> <mn>2.56</mn> </mtd> </mtr> </mtable> </math> </formula>}{} Some more text. \stoptext What is the successor to \setupMMLappearance please? Thanks very much. Duncan

2 2

problems with images, layers and crop marks
by Henning Hraban Ramm 08 Jul '19

08 Jul '19

Hi all, I’m quite quiet at the moment, because I can access my mailing list address only via inconvenient webmail; since I updated MacOS, neither Apple Mail nor Thunderbird will take my password anymore... :-(( Besides, I’m currently well paid for working with LaTeX, and my other projects get less time. Anyway, one of our authors finally submitted her final corrections, and "of course" my ConTeXt setup that still worked well in May doesn’t behave any more: * stacked layers won’t work on the first page (there should be a title bar above an image; it works on the back cover, but not on the front; but I can enable one of both layers) That might be related to: * on some right pages, including p.1 (cover), crop marks are shifted one page width to the right. * on some pages, crop marks are shifted vertically; might be related to using \offset for image placement. I’m trying to cook up MWEs, but the behaviour is so strange and irregular, that I don’t know if I can reproduce it in a simpler environment... I suspect my combined use of postponing, makeups, layers and \offset might have grown side effects since May. Any ideas? Greetlings, Hraban Greetlings, Hraban Grüßlinge, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD

2 4

crappy names in the fontloader
by Marcel Fabian Krüger 08 Jul '19

08 Jul '19

Hi everyone, under default settings, the fontloaders discards all glyph names which are considered "crappy", meaning matching the "p_crappyname" pattern in "font-oup.lua". For some names this makes a lot of sense. For example the name "uni0303" is considered "crappy" and it really provides no useful information. Then there are other names like "t_uni0303" which are still considered "crappy" while they actually aren't completely useless. So I think there would be some value in preserving them. Of course, you can always enable "otf.keepnames" if you need names like this. But I actually want to talk about another class of names: Look at "Udotbelow". This is IMHO a perfectly normal and useful name, but the fontloader still considers it "crappy" because it starts with a "U" followed by a letter which could be a hexadecimal number. I think this is a bit over-agressive. Maybe the "p_crappyname" pattern could be changed to only look for "u<hexadecimal>" if followed by "p_done", marking the end of a component? Best regards, Marcel Krüger

2 2