[NTG-context] Math kerning broken in latest beta

Dear list, The math kerning seems to be broken in recent versions of LuaTeX.  When I process the MWE below with TeX Live 2017 (LuaTeX 1.0.4) I get a different result from the latest beta (LuaTeX 1.07.0).  However, I could only observe this behaviour with some fonts, e.g. stixtwo or lucidaot.  No

Re: [NTG-context] \ifcase changes default align in xtables

In your example the argument for the align key is always empty which results in the default alignment for a frame which put the content in the middle of the box. Wolfgang Pablo Rodriguez 10. April 2018 um 21:05 Dear list, I have the following sample:

Re: [NTG-context] conditional format in xtables

The normal \doif... commands don’t work because they aren’t expandable but you can use the \expdoif... commands (look into setup-en.pdf for all of them). Wolfgang Pablo Rodriguez 10. April 2018 um 19:18 Dear list, thanks to Wolfgang, I learnt to set conditional format

Re: [NTG-context] Build for Alpine Linux

On Tue, Apr 10, 2018 at 11:05:12AM +, Brian Hunt wrote: >> The caret in itself was not the problem, only that it was not escaped >> for the shell. Testing a regexp, with -E of course, is just as robust, >> and allows us to be more specific about what we test. > > Either is fine I am sure

[NTG-context] \ifcase changes default align in xtables

Dear list, I have the following sample: \setupxtable[mytable] [option={stretch, height}, align={\ifcase\currentxtablerow\fi}] \starttext \startxtable[mytable] \startxrow \startxcell 1 \stopxcell \startxcell 2 \stopxcell

[NTG-context] conditional format in xtables

Dear list, thanks to Wolfgang, I learnt to set conditional format in xtables, such as in: \setupxtable [foregroundcolor={\ifnum\currentxtablecolumn=2 red\else green\fi}] \starttext \startxtable \startxrow \startxcell one \stopxcell \startxcell

Re: [NTG-context] Build for Alpine Linux

On Tue, 10 Apr 2018 11:05:12 + Brian Hunt wrote: > from a code maintenance and testing > perspective I'd be more concerned about a regression or > misinterpretation to an unescaped carat that breaks the detection on > zsh Doesn't *everybody* use zsh? ;-)

[NTG-context] xmlrefatt

There is a slight restriction on \xmlrefatt that makes its use problematic, because it does not differentiate between an absent attribute and an attribute consisting of an empty string. The use for \xmlrefatt I had in mind was (a) do nothing if the attribute is absent, and (b) reset some value

Re: [NTG-context] Build for Alpine Linux

A few more notes: 1. Missing texlua - found The missing `texlua` from `bin/` and `tex/texmf-linuxmusl-64/bin` appears to be a problem originating at the rsync source, notably it appears that `texlua` is missing from these paths: http://standalone.contextgarden.net/setup/linuxmusl-64/

Re: [NTG-context] Build for Alpine Linux

> The caret in itself was not the problem, only that it was not escaped > for the shell. Testing a regexp, with -E of course, is just as robust, > and allows us to be more specific about what we test. Either is fine I am sure, but from a code maintenance and testing perspective I'd be more