December 2020 - ntg-context - NTG Mailing Lists

Getting the filename which is being typeset
by Otared Kavian 05 Dec '20

05 Dec '20

Hi everyone, I have to typeset a few files which get each an input file named in a certain way. For instance, a file named « myfile.tex » in which another file named « myfile-buffer.tex » is used as an \input file, as in % content of myfile.tex %%%%% \starttext This is a test. \input myfile-buffer.tex \stoptext %%%%% When typesetting « myfile.tex » I wonder whether it is possible to get the name of the file without its suffix, that is to get « myfile », with a command such as \getNameOfCurrentFile and then be able to replace the above snippet by: % desired content of myfile.tex %%%%% \starttext This is a test. \input \getNameOfCurrentFile-buffer.tex \stoptext %%%%% Best regards and thanks for any hint: Otared K.

6 10

repeated chapter in LMTX Reference Manual?
by Pablo Rodriguez 04 Dec '20

04 Dec '20

Hi Hans, many thanks for your new upload that fixes the issue with scaled external figures. I have just accidentally realized: \startbodymatter \component luametatex-preamble \component luametatex-differences [...] \stopbodymatter \startbackmatter [...] \component luametatex-differences \component luametatex-statistics \stopbackmatter I mean, “Differences with LuaTeX” is the second chapter and the second appendix (sort of) in the “LuaMetaTEX Reference Manual”. I wonder whether this is intended. Just in case it might help, Pablo -- http://www.ousia.tk

2 1

\XeTeX\ misbehaving
by Pablo Rodriguez 04 Dec '20

04 Dec '20

Hans, just accidentally, I discovered that \XeTeX\ misbehaves: \starttext \input{zapf} \XETEX\ \input{knuth} \stoptext BTW, this is the MWE after I saw http://www.pragma-ade.com/general/manuals/luametatex.pdf#page=15. I hope it helps, Pablo -- http://www.ousia.tk

1 0

LMTX ignores figure size
by Henning Hraban Ramm 04 Dec '20

04 Dec '20

Hi, with latest LMTX, the size (width) of external figures is ignored in floats, while it works outside of floats and with MkIV. It also works with metapost figures (e.g. dum library). \setupexternalfigure[location=default] \starttext \startplacefigure[location=here] \externalfigure[cow][width=2cm] \stopplacefigure \stoptext Hraban

3 2

Is anyone having issues with magazines in LMTX?
by Jairo A. del Rio 04 Dec '20

04 Dec '20

Hi, list! When I want to compile magazines from source (such as mag-1102,mkiv), LMTX gives weird output (grayish background and misaligned titles). Compilation with MkIV gives normal results. My ConTeXt version is 2020.12.03 19:02. Thank you in advance. Cordially, Jairo :)

2 1

Re: [NTG-context] basic issues with formulas
by Andres Conrado Montoya 03 Dec '20

03 Dec '20

Hi pablo, regaring 1) TeX assumes that each character is a variable on math mode. You need to tell it that each "word" is, well, a "word": \starttext \startitemize[packed] \item Valor actual neto: $\text{\em beneficios} - \text{\em costes}$. % you can use typographical variations inside \text: \em, \bf, etc \item Beneficio por euro: $\frac{\text{\em beneficios}}{\text{\em costes}}$. \item Beneficio obtenido el primer año. \stopitemize \stoptext 2) will solve itself ather this. 3, I don't know. -- Andrés Conrado Montoya Andi Kú andresconrado(a)gmail.com http://sesentaycuatro.com http://messier87.com http://chiquitico.org ---------------------------------------- Los fines no justifican los medios, porque la medida verdadera de nuestro carácter está dada por los medios que estamos dispuestos a utilizar, no por los fines que proclamamos. ---------------------------------------- “You develop an instant global consciousness, a people orientation, an intense dissatisfaction with the state of the world, and a compulsion to do something about it. From out there on the moon, international politics look so petty. You want to grab a politician by the scruff of the neck and drag him a quarter of a million miles out and say, ‘Look at that, you son of a bitch.’” — Apollo 14 astronaut Edgar Mitchell

2 1

basic issues with formulas
by Pablo Rodriguez 03 Dec '20

03 Dec '20

Dear list, math is all Greek to me and I’m experiencing issues when typesetting the most basic inline formulas. \starttext \startitemize[packed] \item Valor actual neto: $beneficios - costes$. \item Beneficio por euro: $\frac{beneficios}{costes}$. \item Beneficio obtenido el primer año. \stopitemize \startitemize[packed] \item Valor actual neto: $beneficios - costes$. \item Beneficio por euro: $beneficios - costes$. \item Beneficio obtenido el primer año. \stopitemize \startitemize[packed, columns, two] \item Valor actual neto: $beneficios - costes$. \item Beneficio por euro: $\frac{beneficios}{costes}$. \item Beneficio obtenido el primer año. \stopitemize \startitemize[packed, columns, two] \item Valor actual neto: $beneficios - costes$. \item Beneficio por euro: $beneficios - costes$. \item Beneficio obtenido el primer año. \stopitemize \stoptext The issues I’m experiencing are: 1. Kernings around ligatures (fi) are wrong. 2. Is there a way to enable ligatures? 3. Packed works fine with fractions, but packed columns is wrong with them. It adds too much space. Again, formulas are totally foreign to my work with ConTeXt. I don’t know whether they are bugs in latest (2020.01.30 14:13) or there is a way to avoid the issues. Many thanks for your help, Pablo -- http://www.ousia.tk

4 7

Bug (?) using \externalfigure with layers and backgrounds
by Jairo A. del Rio 03 Dec '20

03 Dec '20

Hi everyone. The following \setuppagenumbering[state=stop] \definelayer[mybg] [ repeat=yes, x=0mm, y=0mm, width=\paperwidth, height=\paperheight, ] \setlayer[mybg]{\externalfigure[cow][width=\paperwidth,height=\paperheight]} \setupbackgrounds[page][background=mybg,state=repeat] \setupindenting[yes,small] \startsetups background:default \setupbackgrounds[page][background=mybg,state=repeat] \stopsetups \startsetups background:void \setupbackgrounds[page][background=] \stopsetups \starttext \dorecurse{7}{\input knuth} \page \setups[background:void] \dorecurse{8}{\input tufte} \page \setups[background:default] \dorecurse{7}{\input knuth} \page \stoptext works with a local image (say, if "cow" is in the same folder as the main file), but it doesn't find sample images (cow, hacker, etc.). Is that a bug or an intended result? Thank you in advance. Best regards, Jairo

2 2

Using ConTeXt-LMTX for modern Mathematically-Literate-Programming 1/2
by Stephen Gaito 03 Dec '20

03 Dec '20

Hello, I am slowly working on a Mathematical problem requiring underlying computation. As Mathematicians (myself included) are rather "conservative", I need to discuss each "chunk" of code with the full set of Mathematical notation. A couple of years ago I started using ConTeXt-MKIV as a Mathematically-Literate-Programming tool by using its excellent Lua interface to capture the code and dump it to disk for external compilation. I am now revisiting my original design and want to redo my tools using ConTeXt-LMTX. I would *like* to be able to "stop" the ConTeXt typesetting at various points for differing purposes: 1. After all macro expansions (and hence after *my* calls into Lua) but before line/paragraph/page layout begins. 2. After line/paragraph/page layout but before PDF generation. 3. After all PDF generated (ie. a "normal" "full" ConTeXt run). Stopping after all macro expansions would allow my code generation builds to proceed without the un-needed page setting or PDF generation. Stopping after the line/paragraph/page layout would allow multiple "faster(?)" ConTeXt runs while the "*.tuc" file converges to a complete set of page numbers and cross references (etc). Then, once the "*.tuc" file has converged, a full ConTeXt run with PDF output could be done. I am very aware that *internally* ConTeXt is probably structured as a tight pipeline with each of the "traditional" TeX stages "Mouth", "Stomach", "page setting", PDF generation.... tightly "chained"... This means that there is no "one" place in the code where all macro expansions have completed but before the page setting "starts", or similarly, after the page setting has finished but before the PDF generation "starts". ---- QUESTION: Is it possible to use the new LuaMetaTeX callbacks (found in chapter 10 of the "LuaMetaTEX Reference Manual") to "suppress" any further computation at various points in the ConTeXt pipeline? ---- For example, could I use one of the "*_linebreak_filter"s (or the "append_to_vlist_filter") to "return" an empty value and hence reduce further computation downstream in the pipeline? Could I use the "pre_output_filter" to "return" an empty value and hence "stop" PDF generation? (I realize that these callbacks *are* a currently fast moving target. I am happy to follow their changes, equally I would be testing their usefulness and/or impact) ---- ALTERNATIVE QUESTION: Would it be possible to provide official ConTeXt-LMTX "modes" which suppress further computation at these points? ---- This alternative, while some more work for the writing of ConTeXt-LMTX, would ensure less direct external dependence on the LuaMetaTeX callbacks, but would almost certainly be welcomed by the ConTeXt community. ---- QUESTION: Are the "stages" I have identified major, computationally expensive, "steps" in the overall ConTeXt "computation"? ---- Many thanks for an excellent tool! Regards, Stephen Gaito

3 8

Parallelizing typesetting of large documents with lots of cross-references
by Stephen Gaito 03 Dec '20

03 Dec '20

Hello, This email is largely a simple notification of one "Fool's" dream... ("Only Fools rush in where Angels fear to tread"). I am currently attempting to create "a" (crude) "tool" with which I can typeset: - very large (1,000+ pages), - highly cross-referenced documents, - with embedded literate-programmed code (which needs concurrent compiling and execution), - containing multiple MetaFun graphics, all based upon ConTeXt-LMTX. "In theory", it should be possible to typeset individual "sub-documents" (any section which is known to start on a page boundary rather than inside a page), and then re-combine the individual PDFs back into one single PDF for the whole document (complete with control over the page numbering). The inherent problem is that the *whole* of a ConTeXt document depends upon cross-references from *everywhere* else in the document. TeX and ConTeXt "solve" this problem by using a multi-pass approach (in, for example, 5 passes for the `luametatex` document). Between each pass, ConTeXt saves this multi-pass data (page numbers and cross-references) in the `*.tuc` file. Clearly any parallelization approach needs to have a process which coordinates the update and re-distribution of any changes in this multi-pass data obtained by typesetting each "sub-document". My current approach is to have a federation of Docker/Podman "pods". Each "pod" would have a number of ConTeXt workers, as well as (somewhere in the federation) a Lua based Multi-Pass-Data-coordinator. All work would be coordinated by messages sent and received over a corresponding federation of [NATS servers](https://nats.io/). (Neither [Podman](https://podman.io/) pods nor NATS message coordination are problems at the moment). -------------------------------------------------------------------- **The real problem**, for typesetting a ConTeXt document, is the design of the critical process which will act as a "Multi-Pass-Data-coordinator". -------------------------------------------------------------------- All ConTeXt sub-documents would be typeset in "once" mode using the latest complete set of "Multi-Pass-Data" obtained from the central coordinator. Then, once each typesetting run is complete, the resulting "Multi-Pass-Data" would be sent back to the coordinator to be used to update the coordinator's complete set of "Multi-Pass-Data" ready for any required next typesetting pass. (From the `context --help`: >mtx-context | --once only run once (no multipass data file is produced) I will clearly have to patch(?) the mtx-context.lua script to allow multipass data to be produced... this is probably not a problem). (There would also be a number of additional processes/containers for dependency analysis, build sequencing, compilation of code, execution or interpretation of the code, stitching the PDFs back into one PDF, etc -- these processes are also not the really critical problem at the moment). -------------------------------------------------------------------- QUESTIONS: 1. Are there any other known attempts to parallelize context? 2. Are there any other obvious problems with my approach? 3. Is there any existing documentation on the contents of the `*.tuc` file? 4. If there is no such documentation, is there any naming pattern of the Lua functions which get/set this multi-pass information that I should be aware of? -------------------------------------------------------------------- Many thanks for all of the very useful comments so far... Regards, Stephen Gaito

3 2