[NTG-context] Strangely placed dot

Hi, what is going on with the placement of the dot in this example, and how can I avoid it? \starttext \startTEXpage[offset=3bp] $E_tE_s=E_{\min(t,s)}$. \switchtobodyfont[stixtwo]$E_tE_s=E_{\min(t,s)}$. \switchtobodyfont[lucidaot]$E_tE_s=E_{\min(t,s)}$. \stopTEXpage \stoptext Output attached.

[NTG-context] unwanted vertical spaces after sectionhead in column layout

Hello list, Looks like lmtx adds extra vertical space after heads. Compare those two MWE: \setuppapersize [S4] \setuphead [subject] [after={}] \starttext \startsubject[title={blabla}] \input knuth \stopsubject \stoptext \setuppapersize [S4] \setuphead [subject] [after={}] \starttext

[NTG-context] [ibmplex setup script]

At present the ibmplexmonothin font is seen by the mtxrun script mtxrun --script fonts --list --all --pattern=ibmplexmonothin* identifier familynamefontnamefilename subfont instances ibmplexmonothin ibmplexmono ibmplexmonothin

Re: [NTG-context] module article-basic interferes with \definebodyfont?

On 5/1/2020 1:15 PM, Gerben Wierda wrote: The following code: \enabletrackers[context.trace] %\usemodule[article-basic] \starttypescript [sans] [optima]    \setups[font:fallback:sans]    \definefontsynonym [Sans]           [file:Optima.ttc(Optima Regular)]     [features=default]    

Re: [NTG-context] \definehead behaving differently when in an environment file versus \input'ed

> On 2 May 2020, at 17:08, Wolfgang Schuster > wrote: [comprehensive answer snipped] Thank-you, very helpful. > I attached a slightly modified version of your project structure to show a > different way to organize documents. What I would change is to use a better > section name for each

Re: [NTG-context] \definehead behaving differently when in an environment file versus \input'ed

n...@scorecrow.com schrieb am 02.05.2020 um 17:14: I'm having trouble with \definehead behaving differently depending upon whether I process a file that includes it via a \input statement versus a project structure that calls it via an environment file referenced from a component file.

Re: [NTG-context] Blank page added after pagecolumns

I recently found the pagecolumns manual ( http://www.pragma-ade.com/general/manuals/pagecolumns.pdf), and in several of the examples (including those for side floats and footnotes), the addition of a blank page after the end of the pagecolumns environment also seems to occur. So when the manual

Re: [NTG-context] \definehead behaving differently when in an environment file versus \input'ed

And the attachment (d'oh): <> ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage :

[NTG-context] \definehead behaving differently when in an environment file versus \input'ed

I'm having trouble with \definehead behaving differently depending upon whether I process a file that includes it via a \input statement versus a project structure that calls it via an environment file referenced from a component file. Overall aim: I currently produce a small circulation

Re: [NTG-context] followtext, lmt_followtext and an offset of the glyphs typeset along the path

> On 1 May 2020, at 17:33, Gerben Wierda wrote: > > > >> On 1 May 2020, at 17:10, Henning Hraban Ramm wrote: >> >> >> >>> Am 01.05.2020 um 10:26 schrieb Gerben Wierda : >>> >>> I have been looking at lmt_followtext and followtext to get typesetting >>> done along a path. That works