January 2021 - ntg-context - NTG Mailing Lists

Math align not working
by Johann Birnick 09 Jan '21

09 Jan '21

Hi there, I noticed that Math align is not working properly. In particular I mean the alignment. For example, the following code \starttext \startformula \startalign[m=2,distance=8em,n=5, align={right,middle,middle,middle,left}] \NC 0 \NC < \NC 2x + 5y \NC < \NC 10 \NC 4 \NC < \NC 3x + y \NC < \NC 9 \NR \NC 3 \NC < \NC 2y + 3z \NC < \NC 15 \NC 10\NC < \NC 8y + 5z \NC < \NC 20 \NR \stopalign \stopformula \stoptext is copied from https://dl.contextgarden.net/myway/mathalign.pdf but doesn't produce the intended result. What's wrong? Best regards, Johann

6 11

Weekdays and others as numbers
by Jairo A. del Rio 08 Jan '21

08 Jan '21

ConTeXt has some inbuilt functions for dates. I see that the following \mainlanguage[spanish] \starttext \dayoftheweek{4}{5}{1992} \stoptext gives "lunes" (Monday). How to get a weekday number (2 in this case) instead? Sincerely, Jairo

1 0

Missing kern when using \feature
by Joseph 08 Jan '21

08 Jan '21

2 2

space after \date[]
by Peter Münster 08 Jan '21

08 Jan '21

Hi, There is no more space after \date[] with the latest version. Is this wanted, or a bug? Example: \starttext \date[d=1] X % no space before "X" \stoptext Kind regards, -- Peter

1 0

tikz-module not up to date (synchronisation problem with contextgarden?)
by Christian Prim 08 Jan '21

08 Jan '21

Hi It's been a long time, since a solution for the 'module wrapping error' in tikz has been proposed here in the list: https://mailman.ntg.nl/pipermail/ntg-context/2017/090404.html Since July a fix has been published: https://github.com/pgf-tikz/pgf/commit/9b24e5cdb8246b1075d02c02c75ff8bcac64… A few days ago the release containing the fix was released. On contextgarden the manual under modules/t-tikz/doc/generic/pgf shows the current version 3.1.8b, but the source doesn't include the fix. I compared the source on context-garden (rsync:// contextgarden.net/minimals/current/modules/) with the zip ( https://github.com/pgf-tikz/pgf/archive/3.1.8b.zip) In the zip file the fix is included, so I'm puzzled... Is there a synchronisation-problem? Just wanted to mention it. It's not crucial. Thanks Christian

1 0

Size problems in fencing
by Mikael Sundqvist 08 Jan '21

08 Jan '21

Hi, I have written about these problems some months(year?) ago, but since I noticed today that the problem persists, I write again. The first problem is with sizes of nested fences, the second one with the size of lucida fences. The test file is pasted below. Let me also take the opportunity to thank for the nice card that arrived in the mail. Last year's card was still on the refrigerator, and its message is kind of funny/scary in retrospect. I wish you all a good 2021! /Mikael \definemathfence[Set][left="007B,right="007D,command=yes] \definemathfence[Paren][left="0028,right="0029,command=yes] \starttext When using nested fences, if one set the size of the outer one, it applies also to the inner one, with the same size: \startformula \Paren[size=2]{\int_0^1 \Paren{f_1(x)+f_2(x)}\,dx} \stopformula If one is not specifying the size of the outer fence, it seems to work correctly: \startformula \Paren{\int_0^1 \Paren{f_1(x)+f_2(x)}\,dx} \stopformula \startformula \Paren{\int_0^1 \Paren[size=1]{f_1(x)+f_2(x)}\,dx} \stopformula With most fonts, the sizing works well: \startformula \Set[size=0]{a}\quad \Set[size=1]{a}\quad \Set[size=2]{a}\quad \Set[size=3]{a} \stopformula \switchtobodyfont[lucidaot] If we switch to lucida, the \type{size=1} and \type{size=2} are the same: \startformula \Set[size=0]{a}\quad \Set[size=1]{a}\quad \Set[size=2]{a}\quad \Set[size=3]{a} \stopformula \stoptext

1 0

squeezed
by Hans Hagen 08 Jan '21

08 Jan '21

Hi, Another example: \definetweakedfont[squeezed] [xscale=0.90] \bTABLE \bTR \bTD foo \eTD \bTD[style=\squeezed] $x = 1$ \eTD \eTR \bTR \bTD oof \eTD \bTD[style=\squeezed] $x = 2$ \eTD \eTR \eTABLE \bTABLE[style=squeezed] \bTR \bTD $x = 1$ \eTD \bTD $x = 3$ \eTD \eTR \bTR \bTD $x = 2$ \eTD \bTD $x = 4$ \eTD \eTR \eTABLE \bTABLE[style=\squeezed\squeezed\squeezed] \bTR \bTD $x = 1$ \eTD \bTD $x = 3$ \eTD \eTR \bTR \bTD $x = 2$ \eTD \bTD $x = 4$ \eTD \eTR \eTABLE ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

1 0

new upload
by Hans Hagen 08 Jan '21

08 Jan '21

Hi, A new upload ... I'm playing abit with font tweaks ... \enableexperiments[fonts.compact] % for the definitions \starttext \definefont[FooA][Serif*default @ 12pt 1800 500] \definefont[FooB][Serif*default @ 12pt 0.85 0.50] \definefont[FooC][Serif*default @ 12pt] \definetweakedfont[runwider] [xscale=1.5] \definetweakedfont[runtaller][yscale=2.5,xscale=.8,yoffset=-.2ex] {\FooA test test \runwider test test \runtaller test test}\par {\FooB test test \runwider test test \runtaller test test}\par {\FooC test test \runwider test test \runtaller test test}\par \blank {\input tufte } \blank {\glyphxscale 1070 \input tufte } \definetweakedfont[squeezed] [xscale=0.9] \blank $a = mb^2 + \sqrt{123}$ \blank {\squeezed $a = mb^2 + \sqrt{123}$} \stoptext Just run these examplex in lmtx to get an idea. It might come in handy for special cases, like making sure something fits in some area or make for instance last lines look a bit better (posters or so). For the moment I decided for two additional (optional) scale directives in the font definition (hopefully i didn't mess up the ctx parser for that). Scales are either fractions or integers (the traditional tex scaling in permilles). Hans (also, odd in mp and ligs in some cases fixed) ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Some ligatures don't work in latest LMTX
by Jairo A. del Rio 08 Jan '21

08 Jan '21

Hi everyone. The following example works fine with MkIV, but fails with latest LMTX. To be specific, the lam-alif ligature isn't working. Compile with both to see differences. Majalla is a Windows font, so I guess it's available for testing: \mainlanguage[arabic]\definefontfeature [arabic] [mode=node,language=dflt,script=arab, init=yes,medi=yes,fina=yes,isol=yes, liga=yes,dlig=yes,rlig=yes,clig=yes, mark=yes,mkmk=yes,kern=yes,curs=yes]\definefontfamily[main][serif][sakkalmajalla][features=arabic]\setupbodyfont[main]\setupdirections[bidi=global]\starttext أهلاً وسهلاً\stoptext Is that a bug or are more features to be specified? Thank you in advance. Jairo

4 7

LuaTeX and PDF.js
by Vedran Miletić 08 Jan '21

08 Jan '21

Hello, I compared latest ConTeXt standalone (LuaTeX 2.08) against TeX Live 2020 (LuaTeX 1.12). The produced PDFs are: https://miletic.net/lipsum-112.pdf https://miletic.net/lipsum-208.pdf Viewing them with Evince (and I assume Adobe Reader, I don't have it at hand to test) shows only minor differences in (horizontal) character spacing, which I would expect; the text looks reasonably good either way. However, viewing them with PDF.js shows a large difference: https://miletic.net/lipsum-pdfjs-112.png https://miletic.net/lipsum-pdfjs-208.png As you can observe, b, m, n, p, and r (and possibly others) are moved slightly above other letters. Is this the expected behavior? If not, is this an issue with the way PDF.js is displaying the PDF or the way LuaTeX is producing it? Thanks in advance. Regards, Vedran Miletić -- Vedran Miletić vedran.miletic.net

3 5