ntg-context July 2020

ntg-context@ntg.nl

44 participants
89 discussions

Height of parentheses in a matrix with lmtx
by Fabrice Couvreur 28 Jul '20

28 Jul '20

Hi Hans, With the upgraded version of lmtx, the parentheses of the matrix are no longer adjusted to the content. Thank you. Fabrice \definemathmatrix [pmatrix][matrix:parentheses][simplecommand=MATRIX] \starttext \math{\MATRIX{\MPcode{draw (0,0) -- (1cm,0);} ;\MPcode{draw (0,0) -- (1cm,0);} }} \stoptext

2 1

upload
by Hans Hagen 28 Jul '20

28 Jul '20

Hi, Normally we don't report on successive loe level improvements in the engine or the core of context (we do so in articles and wrapups), and much goes unnoticed anyway (which is good). But ... the last couple of weeks we have been playing with some adapted functionality in lmtx and some of the experimental low level code has now made it in core. Normally users will not notice this but who knows. There are already features in lmtx that are not (and are unlikely to be) in mkiv (most significant in the metapost related part). When possible new macros and additions to mechanism will be in both mkiv and lmtx, but lmtx users will be better off in the end. We're mostly talking of the more tricky mechanisms here, those that currently have limitations due to all kind of possible interferences. To summarize: mkii : frozen (seldom patches) lmtx : cutting edge mkiv : when possible following lmtx, otherwise frozen Because we develop lmtx and luametatex alongside it is no problem if we have experimental (and even temporary imperfect) code in the engine: context knows about it and especially with experiments, we try to make sure it doesn't hit users (who we don't expect to use those, often undocumented, new tricks anyway). It's sometimes the only way to go forward (stepwise testing). So, here is an example of where lmtx can do better than mkiv: \placefigure[left]{}{} \input ward \par \placefigure[left]{}{} {\bf \input ward} \par Another area is in using footnotes. As a first step to more robust handling of deeply nested notes, lmtx now defaults to (the more than a decade optional in mkiv) \automigrateinserts, but with less overhead (for performance reasons, it was never enabled in mkiv, apart from occasional side effects). It is features like these that will stepwise be improved, at least that is what we hope for. So, the current upload has some new stuff, hopefully without too many side effects, but if so, we'll deal with it as usual. As a result, the latest lmtx could be a little slower, but I wonder if someone will notice it in practice. 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

another question about markings
by Joey McCollum 26 Jul '20

26 Jul '20

1 0

question on page transitions
by Pablo Rodriguez 25 Jul '20

25 Jul '20

Dear list, I have a question about page transitions (lines 297-304 from scrn-pag.mkvi): \def\scrn_transitions_set_indeed {\begingroup \edef\currentinteractionscreendelay{\interactionscreenparameter\c!delay}% \clf_setpagetransition n {\scrn_transitions_list}% delay \ifx\currentinteractionscreendelay\v!none \zerocount\else\currentinteractionscreendelay\fi \relax \endgroup} I wonder whether the "delay" option in \setupinteractionscreen defines the number of seconds for the page or for the transition. From what I read in the code above, I would say that the duration is defined for the transition itself. Inspecting the output PDF code in generated documents, the duration is set for the page. In PDF code. /Page <</Duration 5>> sets the number of seconds for the page (https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#sear…). /Page <</Trans <</D 5>> >> sets the number of seconds for the transition (https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#name…). With the followling sample: \setuppapersize[A9,landscape] \setupinteraction[state=start] \setupinteractionscreen[option=max, delay=5] \setuppagetransitions[random] \setupbodyfont[50pt] \starttext \dorecurse{2}{% \startmakeup[page][style=\bf\ss, align=center] \recurselevel \stopmakeup% } \stoptext The output PDF document may contain a /Page object such as: 6 0 obj << /Contents 4 0 R /Dur 5 /Trans << /Di 90 /M /O /S /Fly >> /Type /Page >> endobj This forces the viewer to advance the page after 5s. To have a transition duration of 5s, it should read: 6 0 obj << /Contents 4 0 R /Trans << /D 5 /Di 90 /M /O /S /Fly >> /Type /Page >> endobj https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#name… shows the difference between /Dur and /D. Could anyone confirm whether this should be fixed (or I’m missing something)? Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

Presentation effects
by Kumar Appaiah 25 Jul '20

25 Jul '20

Dear ConTeXt users, I have been trying to get the presentation effects listed here to work: https://wiki.contextgarden.net/Presentation_effects But I am unable to build the example. I am using the Debian ConTeXt (version 2020.03.10.20200331-1). Please let me know if I am missing something. Thanks. Kumar -- Kumar Appaiah

2 1

\documentvariable (used in environment)
by Alan Braslau 25 Jul '20

25 Jul '20

Hello, I have put the following in an environment \startenvironment MYENVIRONMENT \setupdocument [metadata:title={\documentvariable{title}}, metadata:subtitle={\documentvariable{subtitle}}, metadata:author={\documentvariable{author}}, metadata:keywords={\documentvariable{keywords}}] \stopenvironment and correct use would be \environment MYENVIRONMENT \startdocument [title={My title}] \stopdocument because, of course, the environment contains more than \setupdocument such as font loading that should be done before the \startdocument. The metadata does not get set properly, having to do with expansion or other notions of TeX that I never seem to get right. What might be the proper way of handling this? Thank you Alan

3 5

indentnext option for \setuplanguage?
by Pablo Rodriguez 23 Jul '20

23 Jul '20

Hans, as Garulfo mentioned in a previous message (https://mailman.ntg.nl’t /pipermail/ntg-context/2020/098826.html), French may require that all paragraphs are indented (no matter what comes before the paragraph). Spanish also requires that. How about a key for "indentnext" in \setuplanguage? That makes it easier to have documents that require all "indentnext" keys set to "yes". I don’t mean changing the default behaviour for any language. Could the "indentext" option be added to \setuplanguage? Pablo -- http://www.ousia.tk

1 0

\insertpages and remote file
by Pablo Rodriguez 23 Jul '20

23 Jul '20

Dear list, I have the following sample: \setupinteraction[state=start] \starttext \insertpages [https://eur-lex.europa.eu/legal-content/EL/TXT% /PDF/?uri=CELEX:32015D0022] [width=0pt] \attachment[file=https://eur-lex.europa.eu/% legal-content/EL/TXT/PDF/?uri=CELEX:32015D0022] \attachment[https://eur-lex.europa.eu/legal-content/% EL/TXT/PDF/?uri=CELEX:32015D0022] \stoptext The docuemnt may be attached to the PDF document, but pages cannot be inserted to generate a booklet. Attachment doesn’t work either when the "file" key is removed (see second one. Would it be possible that \insertpages and \filterpages could deal with these urls? Or what am I missing here? Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

context --engine=luatex not working
by Jairo A. del Rio 23 Jul '20

23 Jul '20

Hi list! Is --engine=luatex working? Has it changed? The switch seems to be ignored with newer ConTeXt distributions, so only LuaMetaTeX is used. Thank you in advance. Jairo :)

2 1

--silent and so on
by thierry horsin 23 Jul '20

23 Jul '20

Hi everybody I am a current context user since now many years and in particular I use it on linux with automatic compilation with a bash script detecting any modifications of the .tex file. In order for this to work I used with previous versions the "--nonstopmode --batchmode --silent --noconsole" compilation options. With these options with a new error in the .tex files with old versions of mkiv the previous pdf produced was not changed. Now with lmtx, appears a single page pdf file with ERROR written on it. Are there compulations options with lmtx in order to have something similar as before ? Any ideas ? Thanks

4 5

← Newer
1
2
3
4
5
6
7
8
9
Older →

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context July 2020