- ntg-context - NTG Mailing Lists

issue embedding from Lua code
by Pablo Rodriguez 01 Nov '19

01 Nov '19

Dear list, I have the following sample: \setupinteraction[state=start] \starttext \startluacode function document.special_attachment(reference) year = reference:sub(7, 10) attachment_url = "https://www.boe.es/buscar/pdf/" .. year .. "/" .. reference .. "-consolidado.pdf" return attachment_url end \stopluacode \unexpanded\def\giveattachment#1{% \cldcontext{document.special_attachment("#1")}} \def\cE{BOE-A-1978-31229} \attachment[file={\giveattachment{\cE}}, color=red] \attachment[file={https://www.boe.es/buscar/pdf/1978/BOE-A-1978-31229-consolidado.pdf}, color=blue] \giveattachment{\cE} \stoptext I don’t know why I do get the second attachment, but not the first one. Lua code seems to be fine (given the last command in the sample). Could anyone explain me what I’m doing wrong? Many thanks for your help, Pablo -- http://www.ousia.tk

3 6

\setuppagenumbering doublesided generates blank pages
by Kerry Sainsbury 30 Oct '19

30 Oct '19

Hi there, I am a newbie, and have *seem* to have discovered that \setuppagenumbering [alternative=doublesided] generates a blank page between chapters. \setupheadertexts[chapter] \setuppagenumbering [alternative=doublesided,location={header,inmargin}] \starttext \startchapter[title={October 2000}] Blah One \stopchapter \startchapter[title={November 2000}] Blah Two \stopchapter \stoptext This produces a PDF in TeXworks containing 4 pages: - Page 1 with a header an 'October 2000' header and 'Blah One' content - Page 2 with a header an 'October 2000' header only. - Page 3 with a header an 'November 2000' header and 'Blah Two' content - Page 4 which is completely blank If I remove the \setuppagenumbering line the PDF contains just two pages, with the expected content. I'm using "ConTeXt ver: 2019.10.11 15:47 MKIV beta fmt: 2019.10.25 int: english/english" Am I doing something wrong, or is this just a bug? Thanks for your help. ConTeXt is making my life *much* easier right now! Kerry

3 3

Images run into each other when using side floats
by Marco Patzer 30 Oct '19

30 Oct '19

Hi! Some images run into each other when using floats. The following example illustrates this. The second image (or frame) runs into the side figure frame. How to prevent this? \setupfloat [figure] [default=left] \starttext \samplefile{knuth} \startplacefigure [title=Foo] \framed [width=5cm, height=5cm]{} \stopplacefigure \samplefile{ward} \blank \framed [width=4cm, height=4cm]{} \samplefile{knuth} \stoptext context 2019.10.29 15:00 Marco

3 5

LMTX not hyphenating about contents
by Pablo Rodriguez 30 Oct '19

30 Oct '19

Dear list, using LuaTeX 2.00 20190729 + ConTeXt MkIV 2019.10.28 18:57 with this sample: \starttext \chapter[refer]{amazingchapter} \hsize\zeropoint \about[refer] \stoptext I’m afraid that LMTX doesn’t hyphenate the word, while MkIV hyphenates it fine. Could anyone confirm this issue? Many thanks for your help, Pablo -- http://www.ousia.tk

2 1

beta
by Hans Hagen 29 Oct '19

29 Oct '19

Hi, I uploaded a beta. In lmtx there is now a bit more advanced support for svg. A preliminary manual is included that explains a few things. As a teaser ... it is also possible to embed svg code, as in: \startbuffer[svgtest] <svg> <circle cx="50" cy="50" r="40" stroke="green" stroke-width="10" stroke-opacity="0.3" fill="red" fill-opacity="0.3" /> <circle cx="150" cy="50" r="40" stroke="green" stroke-width="10" fill="red" opacity="0.3" /> </svg> \stopbuffer \startTEXpage \includesvgbuffer[svgtest] \stopTEXpage \startTEXpage \includesvgbuffer[svgtest][offset=2bp] \stopTEXpage or in metapost disguise: \startMPpage vardef svg expr c = lmt_svg [ code = c ] enddef ; draw svg "<svg> <circle cx='50' cy='50' r='40' stroke='green' stroke-width='10' stroke-opacity='0.3' fill='red' fill-opacity='0.3' /> <circle cx='150' cy='50' r='40' stroke='green' stroke-width='10' fill='red' opacity='0.3' /> </svg>" ; \stopMPpage It is not a replacement for metapost (which is more efficient runtime anbyway) but for artistic images a mixture might work out ok. In principle inclusion with externalfigure also works when conversion=mps is set but, although I have some 1500 test images, not all might work out well. There can be a lot of crap be hidden in svg files and angle brackets are no guarantee for properly structured images. Especially fonts can be troublesome. On the other hand, if one has very structured input, text labels can be swapped for propertly typeset ones (like math), but that's for later to explain (experimental stuff). We'll see. 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 3

Bug in latest LMTX?
by Otared Kavian 29 Oct '19

29 Oct '19

Hi Hans, Last night I updated to th elatest beta LMTX (version 2019.10.28 18:57), and noticed that several things don't work as usual. I have not yet been able to find all the examples, but here is one in math: \definemathfence[abs][bar][command=yes,factor=auto] \starttext \startformula \sup_{t\in {\Bbb R}}\abs{f(t + T) - f(t)} \leq \epsilon. \stopformula \stoptext The above does not typeset and I have the following error message: tex error > tex error on line 7 in file ./bug-math.tex: ! This can't happen (mlist2) \stopforceddisplaymath ->\endgroup \stopimath \strc_math_box_stop ->\stopforceddisplaymath \egroup \d_strc_math_number_wid... \stopdisplaymath ...xpandafter \stopinnermath \fi \afterdisplayspace \egroup \strc_formulas_stop_formula ...formula \endcsname \dostoptagged \dostoptagge... l.7 \stopformula 1 \definemathfence[abs][bar][command=yes,factor=auto] 2 3 \starttext 4 5 \startformula 6 \sup_{t\in {\Bbb R}}\abs{f(t + T) - f(t)} \leq \epsilon. 7 >> \stopformula 8 9 \stoptext I'm broken. Please show this to someone who can fix me. mtx-context | fatal error: return code: 256 Thanks for your attention: OK PS: the PDF produced now with a colorful « error » is very nice… but the error messages are cryptic :-)

2 1

Fails with MkIV works with LMTX
by Rik Kabel 29 Oct '19

29 Oct '19

This works with the 20191028 LMTX beta, fails with the 20191028 MkIV beta: \starttext This\footnote{that} \stoptext Error log: return { ["filename"]="c:/Users/micro/Desktop/fn.tex", ["lastcontext"]="\n<inserted text> ...s \\inheritmaintextcolor \\strc_itemgroups_push \n \n\\handlenoteinsert ...tes_synchronize \\the \\everybeforenoteinsert \n \\insert \\currentnoteinsert...\n\\235>notation:note ...enoteinsert \\currentnote \\currentnotenumber \n \\fi \\fi \\fi \\endgroup \\fi ...\n\\m_syst_action_nop ...dler \\currentconstructionhandler \\endcsname \n \\strc_constructions_finali...\nl.2 This\\footnote{that}\n ", ["lastluaerror"]="?", ["lasttexerror"]="! Undefined control sequence", ["linenumber"]=2, ["offset"]=10, } Can anyone reproduce this? I have tried rebuilding. -- Rik

3 2

A question about an algorithm environment
by Fabrice Couvreur 28 Oct '19

28 Oct '19

Hi Wolfgang, Why in the first example, the indentation of my Python code that I wish is not respected and that I have to do as the second example to have what I want ? Thank you. Fabrice \defineframedtext [algorithmframe] [width=fit, location=middle, foregroundstyle={\tt\switchtobodyfont[11pt]}, framecolor=darkblue, corner=round] \definelines [algorithm] [space=on, before=\startalgorithmframe, after=\stopalgorithmframe] \starttext \startlinecorrection[blank] \startmidaligned \startalgorithm {\blue def nom} (argument1, argument2,\unknown): \unknown {\orange return} résultat \stopalgorithm \stopmidaligned \stoplinecorrection \startlinecorrection[blank] \startmidaligned \startalgorithm {\blue def nom} (argument1, argument2,\unknown): \unknown {\orange return} résultat \stopalgorithm \stopmidaligned \stoplinecorrection \stoptext

1 0

Luatex 1.08.0 announcement
by luigi scarso 28 Oct '19

28 Oct '19

============================================================== LuaTeX 1.08 2018-08-28 ============================================================== (1) This release is a prelude to 1.10, the next stable iteration of LuaTeX after version 1.00. (2) Lua 5.3 is now considered to be default and we might use 5.4 in version 1.10. There are no real functional changed expected. You still need to rename the binary for 5.3! (3) Binary mode is no longer available in MPlib but it is still available in stand alone MetaPost. This simplifies compilation and reduces dependencies. (4) The dependency on Poppler for pdf image inclusion has been removed. We now use a small dedicated library written by Pawel Jakowski. We no longer need c++ compilers. We're in the process of making it behave well on all platforms. It has been tested on intel platforms. (5) We know that there can be some (alignment) issues with the arm platform but these are looked into. Therefore, later this year we will release 1.09. Version 1.10 is planned for TeXlive. We hope that ffi works ok on intel and arm platforms at that point. (6) There have been some extensions to the Lua libraries and some callbacks have been added. Also, a few new primitives have been introduced. The documentation mentions the stable extensions. (7) There are the usual bug fixes and cleanups but there have been no real fundamental changes in the API. The LuaTeX team

3 10

questions about publ-imp-apa.mkvi
by Damien Thiriet 28 Oct '19

28 Oct '19

Hello, Why do we have in publ-imp-apa.mkvi, line 1182 sq \btxdoif {number} { %\btxleftparenthesis (\btxflush{number} \btxrightparenthesis } and not \btxdoif {number} { \btxleftparenthesis \btxflush{number} \btxrightparenthesis } ? Damien Thiriet

1 0