ntg-context December 2020

ntg-context@ntg.nl

60 participants
129 discussions

Re: [NTG-context] ntg-context Digest, Vol 198, Issue 8
by Andres Conrado Montoya 02 Dec '20

02 Dec '20

You are naming your font "english". If you call "ebgaramond" it will always take the default ebgaramond features. Just call your font with the name you gave it. \definefontfamily[english] [rm] [ebgaramond] [features={dlig=no}] \setupbodyfont[english,10pt] \starttext ct st \stoptext -- 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

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

Context install for Apple Silicon M1 mac mini
by Keith McKay 01 Dec '20

01 Dec '20

Hi, I have recently retired my 2012 mac mini in favour of a new Apple silicon M1 mac mini on which I would like to install ConTeXt. I know that their are no ARM binaries yet for ConTeXt but Apple say that intel binaries can be run on an ARM using the Rosetta emmulation software. I tried to download the intel binaries using the install.sh that comes with the context-osx-64.zip file but of course it does not recognise the ARM chip and suggests contacting the mailing list. In some previous emails to the list, in which I was a participent, (see the post "new upload" of 26/11/2020) their was some discussion on how Context could be set up to work on these machines by building binaries using Xcode. I am afraid this is well above my skillset so I was wondering how I could get the Intel binaries and then set up ConTeXt running with the Rosetta emulation software. I should be able to do that. If this is possible, I would be very happy to do some testing and report back my experiences to the list. Best Wishes Keith McKay Scotland, UK

3 3

new upload
by Hans Hagen 01 Dec '20

01 Dec '20

Hi, I uploaded a new version. This time some cleanup of the backend, so let's see where I messed up this time. The installer has been adapted so that an apple m1 machine is recognized. No native arm bins, that has to wait till we have some hardware available. 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 0

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

Bug in lmtx bibliography (numerals in entry?)
by Damien Thiriet 01 Dec '20

01 Dec '20

Hello, My bibliography files compiles fine in mkiv, but hangs in lmtx Here is the error message: tex error > tex error on line 30 in file ./Nation_rev_empire.mkiv: Use of \btxshowentryinline doesn't match its definition <macro> \btxflushlisttext ...tyleandcolor \c!style \c!color \ignorespaces \publ_fast_setup \plusfour \s!list \currentbtxcategory \removeunwantedspaces \endgroup <argument> \btxflushlisttext \ifx \currentbtxcombis \empty \else \btxrenderingparameter \c!separator \btxflushlistcombis \fi <macro> \btx:list:inject:text ...al \btxinteractivetext \ifx \currentbtxinternal \empty #1\else \goto {#1} [\s!internal (\currentbtxinternal )]\fi \else #1 \fi <macro> \btx_entry_inject ...onal \c_btx_list_texts \dostarttagged \t!listtext \s!left \currentbtxbefore \dostoptagged \fi \btx_entry_inject_list_text \ifconditional \c_btx_list_pages \dostarttagged \t!listpage \empty \btx_entry_inject_pages \dostoptagged \fi \ifconditiona... <macro> \currentlistentrytitle \dostarttagged \t!listcontent \empty \btx_list_reference_inject \btx_entry_inject \dostoptagged <macro> \22>:139>:paragraph ...\relax \fi \fi \fi \begingroup \useliststyleandcolor \c!textstyle \c!textcolor \setstrut \begstrut \currentlistentrytitle \endstrut \endgroup \ifconditional \c_lists_has_page \ifconditional \c_lists_show_page \nobreak \currentlistfiller \beging... […] If you say, e.g., '\def\a1{...}', then you must always put '1' after '\a', since control sequence names are made up of letters only. The macro here has not been followed by the required stuff, so I'm ignoring it. I am using a custom biblio style, but the command \btxshowentryinline is not directly called inside. My ConTeXt version mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: /usr/local/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2020.11.19 11:28 mtx-context | main context file: /usr/local/context/tex/texmf-context/tex/context/base/mkiv/context.mkxl mtx-context | current version: 2020.11.19 11:28 AFAIU, it means my entry shouldn’t have numbers, right? If so, this may be a bug, since entry biblio files often have a number inside Best regards, Damien Thiriet

2 1

Combinations not working as expected
by Christoph Reller 01 Dec '20

01 Dec '20

Dear list, In the latest version 2020.11.28 13:18 of ConTeXt LMTX, combinations don't seem to work as expected. Example: \starttext \startcombination[2*1] {first}{a} {second}{b} \stopcombination \blank[big] \startcombination[1*2] {first}{a} {second}{b} \stopcombination \stoptext The output is [image: image.png] The layout argument [2*1] or [1*2] does not seem to have an effect and the caption placement for "b" is strange. Am I doing something wrong? Cheers, Christoph

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context December 2020