April 2019 - ntg-context - NTG Mailing Lists

Fine-tuning of aps style
by Dmitry Starostin 14 Apr '19

14 Apr '19

To cite like [1, p. 101] \cite[righttext={\nbsp p.~101}][Hankins:2014] works, but has no comma \cite[righttext={, p.~101}][Hankins:2014] produces no page \cite[righttext={,\nbsp p.~101}][Hankins:2014] gives no page at all \cite[righttext={\nbsp, p.~101}][Hankins:2014] gives no page at all. righttext seems to be reluctant over the initial comma right after the reference number.

2 1

index entries printed over each other
by Henning Hraban Ramm 14 Apr '19

14 Apr '19

Hi, on the last page of my index, there are two entries printed over each other, see attached screenshot. How can this happen? Any hints how to avoid it? Sorry, no MWE yet, probably hard to reproduce... Latest, i.e. yesterday’s beta with LuaTeX; the same with the previous version. Also the same problem with lmtx, except that the text is garbage (I’m using Cambria.ttc). Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD

2 2

Fwd: Re: Already new binaries?
by Hans Hagen 14 Apr '19

14 Apr '19

Hi, Forwarded ... gmx.* mail accounts bounce here (always have) so i cc to the list. -------- Forwarded Message -------- Subject: Re: Already new binaries? Date: Sun, 14 Apr 2019 15:25:02 +0200 From: Hans Hagen <j.hagen(a)xs4all.nl> To: Peter Rolf <indiego(a)gmx.net> On 4/14/2019 2:13 PM, Peter Rolf wrote: > Hi Hans, > > does the latest version (2019.04.13 17:01) already contain the binaries > with increased stack size? I can see that the binaries are new, but the > crash still occurs at the same page. Before I waste my time in bug > hunting, I just want to make sure that the binaries are already adjusted. Akira was talking of his windows binaries. The lmtx ones are cross compiled by me. I do nothing with sizes. > In the meantime I have tested all the included PDF (exported from > Inkscape) with an online validator. No problems found. > > Thanks for all the help so far (also to Luigi and Akira). You can try \showusage and see what mem values you have to change. 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 -----------------------------------------------------------------

2 2

Lmtx and Cambria font
by Lutz Haseloff 14 Apr '19

14 Apr '19

Hi Hans, hi all, my fresh installation of lmtx for win64 on Win 10 seems to have a problem with the Windows font cambria. I get no readeable text in the pdf. Other fonts work o.k. Greetings Lutz

3 2

How to make the adjustments to the aps style?
by Dmitry Starostin 13 Apr '19

13 Apr '19

1. to cite in the order of appearance (probably one setting) 2. 'author initials' instead of the default 'initials authors'.

2 1

error in generic fontloader (upvalue 'getglyphdata')
by Ulrike Fischer 13 Apr '19

13 Apr '19

Hans, we think that line 206 and 207 in luatex-basics-nod.lua are faulty and lead to the error attempt to call a nil value (upvalue 'getglyphdata') nuts.getglyphdata = direct.getattr nuts.setglyphdata = direct.setattr should be nuts.getglyphdata = direct.get_attribute nuts.setglyphdata = direct.set_attribute or nuts.getglyphdata = nuts.getattr nuts.setglyphdata = nuts.setattr -- Ulrike Fischer https://www.troubleshooting-tex.de/

2 1

Lua error with fontstrip in today’s beta
by Henning Hraban Ramm 12 Apr '19

12 Apr '19

I just updated my minimals installation (2019.04.12 17:43, still not lmtx) and run into this error: lua error > lua error on line 1 in file fontstriptest.tex: ...xmf/tex/texmf-context/tex/context/base/mkiv/node-nut.lua:284: attempt to call a nil value (global 'setfield') 1 >> \starttext 2 3 \showfontstrip 4 5 \stoptext MWE: \starttext \showfontstrip \stoptext Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD

3 2

caching buffers?
by Henning Hraban Ramm 12 Apr '19

12 Apr '19

Ahoi, in my book I use a lot of buffers for examples. These get typeset (compiled) anew on every tex run (i.e. several times per context run). This needs a lot of time and is quite annoying. Is this somehow cacheable, so that it compiles only once per context run or (even better) only if the buffer changed? How does the filter module handle this? I know it uses some checksum. Should I "outsource" my buffers via t-filter? If you need a MWE for this, I’ll assemble one. My actual setup is quite complicated, maybe that’s the problem... Greetlings, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD

2 2

luaotfload
by Herbert Voss 12 Apr '19

12 Apr '19

Hello all, If I run the following document on a 8 GByte RAM Linux machine. It takes more than 30 minutes until luaotfload has build the cache for Sparks-Dotline-Medium.otf. If I run another Program in the background that it never ends (too less memory). On my Mac the first run with context (upcoming TL2019) needs 9.5 Gbyte memory and nearly 100% CPU load to scan the Sparks-Dotline font. This one is, of course, 400 kB big, but why do we need more than 8 GByte Ram?? The font files are here: http://tug.org/~hvoss/Sparks-Bar-Medium.otf http://tug.org/~hvoss/Sparks-Dotline-Medium.otf -rw-r--r-- 1 voss voss 34412 Apr 11 18:54 Sparks-Bar-Medium.otf -rw-r--r-- 1 voss voss 403776 Apr 11 18:54 Sparks-Dotline-Medium.otf \definefont[sparkBarMedium][file:Sparks-Bar-Medium.otf:mode=node;+calt] \definefont[sparkDotlineMedium][file:Sparks-Dotline-Medium.otf:mode=node;+calt] \starttext Text {\sparkBarMedium{14,95,68,9,19,41,91,1,81,97,79,45,96,76,17,65,8,92}} Text Text {\sparkDotlineMedium{14,95,68,9,19,41,91,1,81,97,79,45,96,76,17,65,8,92}} Text \stoptext Herbert

2 3

Re: [NTG-context] Unwanted uppercase letter in \high{} within bibliography
by Huseyin Özoguz 12 Apr '19

12 Apr '19

> Hello @list, > > > > I have an unwanted output that might be a bug in my bibliographies. > Consider this MWE : > > \setuppapersize[S4] > \mainlanguage[fr] > \language[fr] > > \startbuffer[bib] > > > @book{Manuel5, > editor = {Martin Ivernel and Benjamin Villemagne and Jean Hubac}, > title = {Histoire Géographie EMC 5\high{ème}, cycle 4}, > publisher = {Hatier}, > address = {Paris}, > year = {2016}, > pagetotal = {398}, > language = {french} > } > \stopbuffer > > \usebtxdataset[bib.buffer] > \definebtxrendering > [biblio] > [apa] > [numbering=no, > sorttype=cite, > title="Bibliographie"] > > \starttext > \nocite[Manuel5] > \placelistofpublications > \stoptext > > As you can see, we get Ème in the output instead of ème. > Is this a bug, or did I miss something? > > Regards, > > > Damien Thiriet Hi, same issue here with \low and \lohi – I don't know if it is a bug or for purpose. But there is a simple workaround: Dirty workaround: \high{\color[white]{e}\hskip-1.3ex ème} Maybe better: \lohi{\color[white]{b}}{ème} -- Huseyin Özoguz E-Mail: h.oezoguz(a)mmnetz.de

2 1