November 2020 - ntg-context - NTG Mailing Lists

Display reference number as Roman number
by Rik Kabel 06 Jan '21

06 Jan '21

Hello all, What I thought should be a simple conversion escapes me. I have a reference (created originally via a label defined by \definelabel) that, when referenced as *\in[label]* or *\ref[number][label]* displays a number, and that is how I normally use it. However, I want to display it in one instance as a Roman numeral. *\**Romannumerals{\in[label]}* complains that it is not being fed a number. How can I display the label number in Roman number format in this one instance? -- Rik

2 1

Re: [NTG-context] Hyphenation pattern for Esperanto
by Alain Delmotte 23 Dec '20

23 Dec '20

3 3

Re: [NTG-context] Installing VSCode extension?
by Jeong Dal 17 Dec '20

17 Dec '20

Dear Alasdair McAndrew, I am using vscode in iMac, so my setting may not work for you. 1. First, find files for vscode in your TeX folder. In my case, /ConTeXt-homefolder/tex/texmf-context/context/data/vacode/extensions/context/*.* 2. In a homefolder, there is a hidden folder “.vacode”. Copy context/*.* to ./vscode/extensions/context/*.* 3. Open vscode and enable context-extension. Since it was long time ago, my memory may not be correct. However, I hope that it may give you an idea. Best wishes, Dalyoung

4 6

checkbox in fields show the word yes
by Jan U. Hasecke 11 Dec '20

11 Dec '20

Hi all, with this example I get a checkbox that does not work; in my real world document it works, I can't say why. But this minimal example shows the problem I have in my real document. \usemodule[fields] \setupinteraction [state=start] \setupfield[cbox][width=1em,height=1em,option=printable,frame=on,offset=0.5mm,frameoffset=1mm,type=radio,color=black] \definefield[test][check][cbox][yes][no] \starttext \field[test] \space Do you see the word »yes«? \stoptext Unfortunately in Firefox and some other PDF Viewer there is the word "yes" written in the checkbox. This makes the form useless as people think the given option is set to yes by default. Can I avoid this somehow? TIA juh

3 3

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

Re: [NTG-context] Installing VSCode extension?
by Jeong Dal 02 Dec '20

02 Dec '20

Dear Mikael, > 2) Is there a nice way to compile the tex file from > within vs code? As of > now, I opened a terminal and compiled from that, but that feels like the > wrong way of doing it. For the first question, I don’t know either. For the second question, I’d like to explain what I did for compiling TeX file in vscode. Since I use vscode in MacOsX, you may find your way in Linux. There is a tasks.json file in .vscode folder. I added the following script in the “tasks":[ ] and save it. (You have to modify the "texmf-osx-64/bin” path in the following script from your machine. { "label": "ConTeXt LuaMetaTeX", "type": "shell", "command": "export PATH=/Users/graph/ConTeXtLM/tex/texmf-osx-64/bin:$PATH;mtxrun --autogenerate --script context --autopdf --purge '${file}'", "args": [], "options": { "cwd": "${fileDirname}" }, "group": { "kind": "build", "isDefault": true } }, When you want to compile a ConTeXt file, find “terminal > Run Build task” in the menu, then “ConTeXt LuaMetaTex” will pop up. Or just use the key “command-shift-B” instead using menu item. I hope that it may help. Best wishes, Dalyoung

3 2

Install Problems with 64 bit ARM Linux
by Christian Prim 01 Dec '20

01 Dec '20

Hi everyone Is there a reason why the arm binaries for ARM Linux use version 2.29 of glibc? My actual debian buster installation is still on glibc-2.28. The x86_64 Linux binaries also use the older 2.28-version which is widely used among many distros. I would be very happy if I could install a 2.28-version on my ARM Linux box. Else I have to compile my own glic... or my own mtxrun... Many thanks for your clarifications Christian PS.: error messages during the install: .../lmtx/bin/mtxrun: /lib/aarch64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by .../lmtx/bin/mtxrun)

4 11

install.sh not working on Linux (Ubuntu 20.04)?
by Jairo A. del Rio 01 Dec '20

01 Dec '20

Hi everybody. Is anyone else having problems with recent ConTeXt updates on Linux? Since last month, install.sh isn't doing anything. However, when I go to Pragma ADE's website, I can download newer releases and they work fine (e.g. --permitloadlib works now). I'm not so picky about manual downloads, but I think install.sh is (or was) quite better. I'm on Ubuntu 20.04, in case it helps. Thank you very much. Regards, Jairo :)

3 3

Adding syntax highlighting when typesetting from xml (asciidoc/docbook)
by Mojca Miklavec 01 Dec '20

01 Dec '20

Hi, A while ago Hans provided an example of typesetting a document from a docbook source. I'm attaching an over-simplified version of the initial module (a somewhat more complete version exists, but it still needs lots of work) and a minimum working example with XML. I'm not sure how to extend the xml parser to support typesetting from something like this: <section xml:id="_hello_world_in_c_and_context"> <title>Hello World in C and ConTeXt</title> <programlisting language="cpp" linenumbering="unnumbered">#include <stdio.h> int main() { printf("Hello, World!\n"); return 0; }</programlisting> <programlisting language="context" linenumbering="numbered">\starttext Hello world! \stoptext</programlisting> </section> Maybe using the vim module would be the right approach here (since the built-in parser only has support for a limited set of languages), but I'm not exactly sure about the implementation to achieve that goal. I started with \startxmlsetups xml:programlisting \dontleavehmode \startframedtext[background=color,backgroundcolor=lightgray] \obeylines \tt \xmlflush{#1} \stopframedtext \stopxmlsetups but something more is needed to properly handle new lines and to properly pass the text to vim, for example. Any hints welcome. Thank you, Mojca

2 1

framedtext is (still) broken in LMTX
by Rik Kabel 30 Nov '20

30 Nov '20

With ConTeXt ver: 2020.11.28 13:18 LMTX fmt: 2020.11.29 the *\framedtext* output is consistently *0.8\textwidth*. MkiV gives the expected result. \starttext \framedtext{Fail}\par \framedtext[width=fit]{Fail}\par \framedtext[width=3cm]{Fail}\par \framedtext[width=0.8\textwidth]{Fine by accident}\par \framedtext[width=\textwidth]{Fail}\par \framed{Fine}\par \framed[width=fit]{Fine}\par \framed[width=3cm]{Fine}\par \framed[width=0.8\textwidth]{Fine}\par \framed[width=\textwidth]{Fine}\par \stoptext -- Rik

3 4