- ntg-context - Mailing Lists

getting line numbers
by Thierry Horsin 05 Sep '21

05 Sep '21

Hi everybody Is there a way to have an automatic access to the current line number of a specific place inside a tex file ? To be more precise, here is what I would like to do. I am currently trying to have some automatic external compilation by g++ of some portion of my tex file as in the following example below. \startC \stopC defines a framed part of text written between lines 538 and 549. Of course, if I add something before or inbetween my framed code, 538 and/or 549 will change. Thus I would like to get these two numbers automatically. Thank you. Thierry \startC #include <iostream> using namespace std; int mysum(int,int); int a; int b; int main () { a=2; b=9; cout << mysum(a,b) << endl; return 0; } int mysum(int a, int b) { return a+b; } \stopC \startluacode myout = io.open("test.cpp", "w") myin = io.open(tex.jobname..".tex", "r") local n=0 for line in myin:lines() do n=n+1 if n>539 and n<550 then myout:write(line.."\n") end end myout:close() myin:close() os.execute("g++ -o test test.cpp") os.execute("./test > tmp") local file=assert(io.open("tmp","r")) local t = file:read("*all") tex.print(t) \stopluacode

4 5

parameters TeX->LuaTeX
by Hans van der Meer 05 Sep '21

05 Sep '21

There is something I do not understand in the passing of parameters from TeX to LuaTex. This is my TeX definition: \def\ListSort[#1]#2{\directlua{hvdm.listsort([===[#2]===],[===[#1]===])}} Calling \ListSort[sep={ + }]{} delivers the string 'sep={ + }' into LuaTeX as the printout in the logfile shows and as intended. However in \ListSort[{ + }]{} the braces have disappeared and transferred is nothing more than ' + '. Why is the transfer messing up the character string I am passing by removing the outer braces? Is this a bug or is it an unavoidable consequence of the TeX-LuaTeX interface? dr. Hans van der Meer

2 2

Re: [NTG-context] getting line numbers
by thierry horsin 04 Sep '21

04 Sep '21

Hi and thank you Aditaya and again Hans. By the way, just for fun , is there a(n easy) way to get the linenumber in the tex file ? Thanks On 03/09/2021 18:04, ntg-context-request(a)ntg.nl wrote: > > ------------------------------ > > Message: 4 > Date: Fri, 3 Sep 2021 14:16:40 +0200 > From: Hans Hagen <j.hagen(a)xs4all.nl> > To: mailing list for ConTeXt users <ntg-context(a)ntg.nl> > Cc: Thierry Horsin <horsin(a)free.fr> > Subject: Re: [NTG-context] getting line numbers > Message-ID: <807e4b7c-97ae-e20e-3207-28393544c5e5(a)xs4all.nl> > Content-Type: text/plain; charset=utf-8; format=flowed > > in this case, thinking a bit different is easier ... > > \starttext > > \startbuffer[MyBuffer] > #include <iostream> > > using namespace std; > int mysum(int,int); > int a; int b; > int main () { > a=2; b=9; > cout << mysum(a,b) << endl; > return 0; > } > int mysum(int a, int b) { > return a+b; > } > \stopbuffer > > We compile and run: > > \typebuffer[MyBuffer][option=C] > > \startluacode > io.savedata("test.cpp",buffers.getcontent("MyBuffer")) > --os.execute("g++ -o test test.cpp") > --os.execute("./test > test.tmp") > os.execute("echo done > test.tmp") > buffers.assign("MyBuffer",io.loaddata("test.tmp")) > \stopluacode > > And get: > > \typebuffer[MyBuffer] > > Or just: > > \typefile{test.tmp} > > \stoptext > > > ----------------------------------------------------------------- > Hans Hagen | PRAGMA ADE > Ridderstraat 27 | 8061 GH Hasselt | The Netherlands > tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl > ----------------------------------------------------------------- > > > ------------------------------ > > ------------------------------ > > Message: 6 > Date: Fri, 3 Sep 2021 09:53:58 -0400 (EDT) > From: Aditya Mahajan <adityam(a)umich.edu> > To: Thierry Horsin via ntg-context <ntg-context(a)ntg.nl> > Subject: Re: [NTG-context] getting line numbers > Message-ID: > <nycvar.YAK.7.77.849.2109030949370.477524(a)ervasbepr.pvz.zptvyy.pn> > Content-Type: text/plain; charset=US-ASCII > > On Fri, 3 Sep 2021, Thierry Horsin via ntg-context wrote: > > > https://github.com/adityam/filter > > Behind the scenes, it works by saving the content in an external file and then > running it through any external program. It also allows for caching the > result, and has many options for customizing the behavior. > > Aditya > >

3 2

Using \vrule within mathmatrix
by fv leung 04 Sep '21

04 Sep '21

\definemathmatrix[pmatrix][matrix:parentheses][simplecommand=pMat] \starttext I used to typeset an augmented matrix this way: \m{\pMat{1,7,-6,\vrule,-4;3,-4,7,\vrule,13;4,3,1,\vrule,9}} But this no longer works. Though I can get over this with \m{\pMat{1,7,-6,¦,-4;3,-4,7,¦,13;4,3,1,¦,9}} , I find the result from the old way looks nicer. Is the using of \backslash vrule within mathmatrix gone for good? \stoptext

2 1

update lmtx
by Hans Hagen 03 Sep '21

03 Sep '21

Hi, The end of the week update provides: \starttext \startTEXpage[offset=10pt] \starttabulate[|c|c|c|] \NC 1 \NC second column \NC third column \NC \NR \NC 2 \NC second \NC third \NC \NR \NC 3 r \NS[1][r]second & third \NC \NR \NC 3 c \NS[1][c]second & third \NC \NR \NC 3 l \NS[1][l]second & third \NC \NR \stoptabulate \stopTEXpage \stoptext where \NS means that there will be a span over columns (I needed such a span fro a manual but it only covers simple cases). There is also a new lowlevel manual, this time on marks (aka markings), think of running headers and so. I'm considering replacing the marking code by new code that I already have one my machine. In mkiv we;ve always used a more powerful alternative for the marks that than what luatex and friends provide but in luametatex I added a few of the missing pieces to the engine in addition to what already what there for a while. But I need Wolfgang to go over the code in order to identify possible side effects first. Hans ps. Because Dutch telecom (who so far took over all the providers we ever had so we had to change a few times) now completely quits web services we need to switch provider (again; so much for synergy) so the upcoming week there might be glitches in accessing the installer (we don't fallback on the garden yet). ----------------------------------------------------------------- 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

metafun doesn't compile \root 3 \of 2
by fv leung 03 Sep '21

03 Sep '21

\starttext \m{\root3\of2} \stoptext works. But \starttext \startMPcode label("\m{\root3\of2}", origin); \stopMPcode \stoptext doesn't. Running `LuaMetaTeX' on `trial' with ``/home/fvleung/ConTeXt/tex/texmf-linux-64/bin/mtxrun --autogenerate --script context trial.tex'' resolvers | formats | executing runner 'run luametatex format': /home/fvleung/ConTeXt/tex/texmf-linux-64/bin/luametatex --jobname="trial" --fmt=/home/fvleung/ConTeXt/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt --lua=/home/fvleung/ConTeXt/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui cont-yes.mkiv --c:currentrun=1 --c:fulljobname="./trial.tex" --c:input="./trial.tex" --c:kindofrun=1 --c:maxnofruns=9 --c:texmfbinpath="/home/fvleung/ConTeXt/tex/texmf-linux-64/bin" open source > level 1, order 1, name 'cont-yes.mkiv' fonts > beware: no fonts are loaded yet, using 'lm mono' in box system > system > ConTeXt ver: 2021.07.27 19:27 LMTX fmt: 2021.7.28 int: english/english system > system > 'cont-new.mkxl' loaded open source > level 2, order 2, name '/home/fvleung/ConTeXt/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > beware: some patches loaded from cont-new.mkiv close source > level 2, order 2, name '/home/fvleung/ConTeXt/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > files > jobname './trial', input './trial.tex', result './trial' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 2, order 3, name './trial.tex' fonts > preloading latin modern fonts (second stage) fonts > 'fallback modern-designsize rm 12pt' is loaded metapost > initializing instance 'metafun:1' using format 'metafun' and method 'default' metapost > loading 'metafun' as 'metafun.mpxl' using method 'default' metapost > initializing number mode 'scaled' metapost > trace > This is MPLIB for LuaMetaTeX, version 3.11, running in scaled mode. metapost > trace > metapost > trace > loading metafun for lmtx, including the plain 1.004 base definitions metapost > trace > tex error > tex error on line 7 in file ./trial.tex: Argument of \root has an extra } 32\normalstopimath \fi <inserted text> \par <to be read again> } <lua output> } <local> \global \setbox \mptextbox \hbox {\clf_mptexttoks } <inserted text> [[special cmd: end local call]] <to be read again> \relax ... <line 4.5> \stopMPcode 1 \starttext 2 3 \startMPcode 4 label("\m{\root3\of2}", origin); 5 \stopMPcode 6 7 >> \stoptext 8 I've run across a '}' that doesn't seem to match anything. For example, '\def\a#1{...}' and '\a}' would produce this error. The '\par' that I've just inserted will cause me to report a runaway argument that might be the root of the problem. mtx-context | fatal error: return code: 256 TeX Output exited abnormally with code 1 at Fri Sep 3 17:44:19

2 1

"*.jpg is bugged", previously working
by Henning Hraban Ramm 02 Sep '21

02 Sep '21

Hi again, was something changed WRT JPEG images? Since a few versions some images that used to work are denied with the error message "... is bugged". Maybe there *is* something wrong with them, but I don’t see a problem. "file" gives: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=12, height=3408, bps=0, PhotometricIntepretation=RGB, orientation=upper-left, width=2368], baseline, precision 8, 607x420, components 3 JPEG image data, JFIF standard 1.01, resolution (DPI), density 72x72, segment length 16, Exif Standard: [TIFF image data, big-endian, direntries=9, manufacturer=FLIR Systems AB, model=FLIR ONE Pro, orientation=upper-left, xresolution=152, yresolution=160, resolutionunit=2, software=Common_dll v1.0.0b1, datetime=2021:08:03 15:28:27], baseline, precision 8, 640x480, components 3 The latter is one of Harald’s infrared pictures. I can send them off-list, if you like. Hraban

2 5

line numbering restarts every page
by Henning Hraban Ramm 01 Sep '21

01 Sep '21

Hi again, if a "typing" environment with line numbering goes over a page break, the line numbers start at 1 again on the new page. It doesn’t happen with \start/stoplinenumbering. MWE: \setuptyping[ numbering=file, ] \setuppaper[A5] \setupbodyfont[18pt] \starttext \startbuffer Li Europan lingues es membres del sam familie. Lor separat existentie es un myth. Por scientie, musica, sport etc, litot Europa usa li sam vocabular. Li lingues differe solmen in li grammatica, li pronunciation e li plu commun vocabules. Omnicos directe al desirabilite de un nov lingua franca: On refusa continuar payar custosi traductores. At solmen va esser necessi far uniform grammatica, pronunciation e plu sommun paroles. Ma quande lingues coalesce, li grammatica del resultant lingue es plu simplic e regulari quam ti del coalescent lingues. Li nov lingua franca va esser plu simplic e regulari quam li existent Europan lingues. \stopbuffer \dorecurse{10}{ \samplefile{knuth} \typebuffer } \stoptext Hraban

3 3

MetaPost Examples
by Henning Hraban Ramm 01 Sep '21

01 Sep '21

Hi, I’m trying to “translate” the documentation of “fiziko”* from LaTeX to ConTeXt and would like to avoid the doubling of MP code like: \startMP path p; p := (0,0){dir(30)}..(5cm, 0)..{dir(30)}(10cm, 0); draw brush (p)(2minStrokeWidth*sin(offsetPathLength*pi)); \stopMP \startMPcode path p; p := (0,0){dir(30)}..(5cm, 0)..{dir(30)}(10cm, 0); draw brush (p)(2minStrokeWidth*sin(offsetPathLength*pi)); \stopMPcode I’m quite sure there’s a possibility with buffers, but how? \startbuffer path p; p := (0,0){dir(30)}..(5cm, 0)..{dir(30)}(10cm, 0); draw brush (p)(2minStrokeWidth*sin(offsetPathLength*pi)); \stopbuffer \typebuffer ... and then how do I get the MP graphic? Hraban *) https://github.com/jemmybutton/fiziko

2 2

Incorrect rendering in Devanagari forms in some fonts
by kauśika cittūr 01 Sep '21

01 Sep '21

Dear All, I have encountered a strange problem using certain Devanagari fonts for the Sanskrit languagein ConTeXt, wherein the rakaar ligatures are not rendered properly in some glyphs/conjuncts. The problem is not too easy to describe so please pardon this long email. The fonts I am using are as follows: • Shobhika – https://github.com/Sandhi-IITBombay/Shobhika • Murty Sanskrit – https://murtylibrary.com/mcli-fonts.php I had previously posted about this issue on TeX SE and Ulrike Fischer was kind enough to suggest that the problem might have something to do with the font rendering (since I have no issues in XeLaTeX (using Harfbuzz)): https://tex.stackexchange.com/questions/612634/devanagari-forms-in-context-… My ConTeXt (LMTX) version is: 2021.08.30 19:56 I am using the following typescript for Murty: \starttypescript [serif] [murty] \definefontsynonym [Serif] [name:murtysanskritregular] [features=devanagari-two] \stoptypescript \starttypescript [murty] \definetypeface [murty] [rm] [serif] [murty] [default] \stoptypescript and the following for Shobhika: \starttypescript [serif] [shobhika] \definefontsynonym [Serif] [name:shobhikaregular] [features=devanagari-two] \definefontsynonym [SerifBold] [name:shobhikabold] [features=devanagari-two] \stoptypescript \starttypescript [shobhika] \definetypeface [shobhika] [rm] [serif] [shobhika] \stoptypescript Below is the test file I am using to demonstrate the problem: \setupbodyfont[shobhika] \starttext \startcolumns ट्रा ट्रि ट्री ट्रु द्रू ट्रे ट्रै ट्रो ट्रौ ठ्रा ठ्रि ठ्री ठ्रु ठ्रू ठ्रे ठ्रै ठ्रो ठ्रौ ड्रा ड्रि ड्री ड्रु ड्रू ड्रे ड्रै ड्रो ड्रौ ढ्रा ढ्रि ढ्री ढ्रु ढ्रू ढ्रे ढ्रै ढ्रो ढ्रौ छ्रा छ्रि छ्री छ्रु छ्रू छ्रे छ्रै छ्रो छ्रौ \column क्र ख्र ग्र घ्र ण्र च्र छ्र ज्र झ्र ञ्र च्रे छ्रे ज्रे झ्रे ञ्रे त्रे थ्रे द्रे ध्रे न्रे प्र फ्र ब्र भ्र म्र य्र ल्र व्र स्र श्र ष्र ह्र \stopcolumns \stoptext When I use the 'devanagari-two' feature set, which sets the script tag to 'dev2', the rakaar forms (provided by the features 'rkrf=yes' and 'blwf=yes') do not render properly for some glyphs, namely the glyphs in the right column, enclosed in a red rectangle in the file 'devanagari-two-forms-shobhika.png' attached in the Drive folder here. When I switch to using the 'devanagari-one' feature set (in the foregoing typescript definitions), which sets the script tag to 'deva', the rakaar forms in the left column are rendered incorrectly in the file 'devanagari-one-forms-shobhika.png' attached in the Drive folder here. Analogous problems occur with the Murty font. Further, in the Murty font, one other conjunct, namely त् +‌ त does not render properly. I have highlighted this in the file 'murty-conjuct.png'. The sample images demonstrating the issues are available in the following public Google Drive folder: https://drive.google.com/drive/folders/1aOmPKqBzB5usVvT9g-Bxk87exyiQn7ax I must mention once again that I have no such problems using either of these fonts in XeLaTeX. What I am noticing is that this problem only occurs with consonant forms that have a 'circular base', i.e., have no danda (the vertical line) next to the character. For what it is worth, I have noticed also that I am able to 'circumvent' this issue if I write छ्र‌ +‌ ZWS + Devanagari vowel sign where ZWS is the zero-width space U+200B. Unfortunately, this quickly becomes very untenable in large documents. Since I was new to ConTeXt I did not venture to ask earlier on since I had not read much of the documentaion. Now, after having read quite a bit, I have mustered up the courage to ask here. As a stop-gap solution, I defined another font alternative with \definefontalternative[rk] and used that with a font synonym using 'devanagari-two' where necessary. I have completely migrated (away from (Xe)LaTeX )to ConTeXt for all my university work which is in English with lots of mathematics. I am by no means an expert but I have learned very much about ConTeXt by reading the excellent wiki, documentation and mailing list. I have no issues using ConTeXt on an everyday basis for my English-language based work. It is only when I tried to use it for my work in Indian-languages that I ran into this issue. I request your kind help in this matter. I really want to be able to use ConTeXt for these Indic works. I will be grateful for any help and/or guidance. Many thanks, kauśika

1 1