November 2020 - ntg-context - NTG Mailing Lists

Issue with tex.romannumeral output
by Joseph 25 Nov '20

25 Nov '20

4 4

Issue with LMTX and placeformula
by Jean-Philippe Rey 25 Nov '20

25 Nov '20

Dear list, \placeformula doesn't seem to work with LMTX. ================== \starttext \placeformula[F] \startformula a^2 + b^2 = c^2 \stopformula The \in[F] formula \stoptext ================== Thank you for your help. -- Jean-Philippe Rey jean-philippe.rey(a)centralesupelec.fr 91192 Gif-sur-Yvette Cedex - France Empreinte PGP : 807A 5B2C 69E4 D4B5 783A 428A 1B5E E83E 261B BF51

2 1

Fwd: Some ligatures don't work in latest LMTX
by Jairo A. del Rio 25 Nov '20

25 Nov '20

---------- Forwarded message --------- De: Jairo A. del Rio <jairoadelrio6(a)gmail.com> Date: mar, 24 de nov. de 2020 a la(s) 14:16 Subject: Re: [NTG-context] Some ligatures don't work in latest LMTX To: Hans Hagen <j.hagen(a)xs4all.nl> Thank you very much, Hans. Ligatures now work. However, diacritics aren't properly placed even using "features=arabic" (they appear below letters in LMTX). ConTeXt MkIV still gives correct output. Thank you in advance. Jairo El mar, 24 de nov. de 2020 a la(s) 12:04, Hans Hagen (j.hagen(a)xs4all.nl) escribió: > On 11/24/2020 8:12 AM, Jairo A. del Rio wrote: > > |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. > (you can probably best use the already define arabic featre because it > also does some contextual stuff) > > anyway, there was an issue with the state querying (isol etc) as side > effect of another thing .. fixed in next upload (there haven't been > fundamental changes to the font handling for quite a while) > > 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 > ----------------------------------------------------------------- >

1 1

Issue with grid
by Joseph 25 Nov '20

25 Nov '20

3 12

upload
by Hans Hagen 25 Nov '20

25 Nov '20

Hi, I uploaded a next iteration of lmtx. From now on there are dedicated sub directories for mklx and mpxl, which is an indication that we're on the way to a full code split. 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 -----------------------------------------------------------------

7 15

accessing tex variable on lua side
by Jano Kula 25 Nov '20

25 Nov '20

Hello, running in circles I have to give up on such an easy thing as passing a tex variable to lua (knowing everything is stored in lua). \setvariable{test}{something}{HHHH} \starttext \getvariable{test}{something}\par % how to access the variable on lua end? \startluacode -- var = \stopluacode \stoptext Thank you, Jano

2 3

Another LMTX small issue
by Rik Kabel 25 Nov '20

25 Nov '20

The following code generates an error message in the log under LMTX 2020.11.24 19:02 but compilation continues with no apparent issue. \starttext \framedtext{abc} \stoptext -- Rik

2 1

Error with spaces in Argument of \startproduct
by Jannik Voges 25 Nov '20

25 Nov '20

Hello, as the title suggested, I get an error when using spaces in the argument of \startproduct. For example typesetting \startproduct{foo bar} \starttext foo \stoptext \stopproduct results in an error: tex error > tex error on line 2 in file ./foo bar.tex: Too many }'s Best regards Jannik Voges

3 2

Unexpected underbar behaviour in sections
by Bruce Horrocks 24 Nov '20

24 Nov '20

The following is giving me a section title with triple underbars instead of single. \definehead [Heading] [section] \setuphead [Heading] [style={\underbar}] \starttext \Heading{First level section heading} \underbar{This is single underlined as expected} \stoptext (Same with \startHeading .. \stopHeading and for subsections, which is where I first noticed it.) It looks quite attractive in its own way - and certainly acts as a visual highlight - just not quite what I was expecting. ;-) version 2020.11.24 00:41 -- Bruce Horrocks Hampshire, UK

2 2

startCSV Wiki, Natural Table
by Fabrice L 24 Nov '20

24 Nov '20

Hi, I was using in the past (MKII) a snippet of code to produce (natural) tables from CSV. I was trying to compile my code with MKIV, but this does not work anymore. As a matter of fact, it doe snot work at all, nor MKII, nor MKIV (probably my error !). So I came back to the wiki, where my code came from, and the code below is just a copy for the wiki. It is supposed to make a table with three columns, but there is only one column in the resulting table… I admit I do not understand the code, but is there is missing \eTR somewhere ? Thanks for any help. Fabrice. Ps: in case someone is interested, I use this to produce statistical tables for teaching. I can share.. ! % ------------------------------------------------------ \starttext % Iterate over all the lines of text captured with \obeylines active % command to call is first argument, is not called for empty lines \bgroup \obeylines \gdef\ProcessLines#1#2{\doProcessLines{#1}#2^^M\doProcessLines}% \gdef\doProcessLines#1#2^^M#3\doProcessLines{% \doifnotempty{#2}{#1{#2}}% \doifnotempty{#3}{\doProcessLines{#1}#3\doProcessLines}% }% \egroup \def\startCSV{\bgroup\obeylines\dostartCSV} \def\TBLentry#1{\bTD#1\eTD} \def\TBLline#1{\bTR\processcommalist[#1]\TBLentry} \def\dostartCSV#1\stopCSV{% \bTABLE \ProcessLines\TBLline{#1}% \eTABLE \egroup } % some additional settings for the table may be made as well \setupTABLE[c][2][style=\tt] \setupTABLE[c][3][align=middle] \setupTABLE[r][1][style=bold] \startCSV Name,Email,Accepted \CONTEXT,worth(a)trying.to,Yes Hans,main(a)developer.of,Yes Bug,get(a)rid.of,No \stopCSV \stoptext

2 4