- ntg-context - NTG Mailing Lists

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

styling part of an index entry
by jbf 07 Jan '21

07 Jan '21

I'm wondering if further progress has been made in Mk IV on styling parts of an index (register) entry? I have followed the explanation on the wiki, but do not seem to be able to achieve what I need. And what I need is to be able to italicise entries that refer to newspaper names, e.g. The Observer MWE \defineregister[myindex] \defineprocessor[style][style=italic] \starttext In \myindex{style->Observer, The} {\em The Observer} of 31 July 2018 \stoptext The only result I am getting is: ->Observer, The 223 But what I want is /Observer, The/ (in other words, in italics). Clearly I am doing something wrong, or not enough, or... maybe there is another way to achieve waht I need? Julian

3 6

odd behaviour of mp odd function in lmtx
by Damien Thiriet 07 Jan '21

07 Jan '21

Hi, I may have found the bug that broke my metafun file. Looks like it is connected to odd function. This snippet of code: \starttext \startMPpage path p;p:=origin--(20,20); draw p; draw p reflectedabout ((10,10),(10,-10)) withcolor red; for i=1 upto 2: if odd i: draw p yshifted 20 withcolor green; else: draw p xshifted 20 withcolor blue; fi; endfor; \stopMPpage \stoptext does not compile as I would expect (no green line drawn). I noticed such behaviour in 2020.12.30 16:45 version. I updated a few minutes ago and have the same output. I hope I didn't miss anything. Best regards, Damien Thiriet

2 1

odd seems to be broken in lmtx-metafun
by Damien Thiriet 07 Jan '21

07 Jan '21

Hi, I think I found the bug that made me send a "false positive" a few days ago. Looks like something messes up with metafun odd function. This snippet of code: \starttext \startMPpage path p;p:=origin--(20,20); draw p; draw p reflectedabout ((10,10),(10,-10)) withcolor red; for i=1 upto 2: if odd i: draw p yshifted 20 withcolor green; else: draw p xshifted 20 withcolor blue; fi; endfor; %draw (0,0)--(20,20) withcolor red; \stopMPpage \stoptext does not compile as I would expect it: no green line is drawn (but there is an output). I hope I did not miss something and won't waste your time. This appeared at least in 2020.12.30 16:45 version (I don't update often enough to give better hints) Best regards, Damien Thiriet

1 0

Problem with show command in MetaFun
by Keith McKay 07 Jan '21

07 Jan '21

In the MWE below I would expect the "show" command to print the value of p in the console output (I use Texworks), however this does not seem to be happening. I haven't used "show" in MetaFun for a while, am I implementing it correctly? Best Wishes Keith McKay %%%%%%%% MWE %%%%%%%%% \setuppapersize[A4, portrait] \starttext \startMPpage StartPage; width := PaperWidth ; height := PaperHeight ; unit := cm ; numeric p; p := 0; for q = 0 step 1 until 10: show p; p := p + 1; fill fullcircle xyscaled(3cm,4cm) shifted ((p +2)*cm, (p + 2)*cm) withcolor red ; endfor; StopPage; \stopMPpage \stoptext

2 2

Re: [NTG-context] Continued chapter numbers
by jbf 07 Jan '21

07 Jan '21

\defineresetset [jbfreset] [] [0] \setuphead [chapter] [sectionresetset=jbfreset] That does indeed work for me. I had searched everywhere on the wiki and in the manuals for something like this, based on 'reset' but could not find it. While it is clearly something you knew (and I now know!), do you know where this is mentioned in any ConTeXt documentation? Grateful for the solution! Julian

4 5