December 2021 - ntg-context - NTG Mailing Lists

Status of moderncv with ConTeXt ?
by Laurent Steffan 06 Dec '21

06 Dec '21

Hello, In the deprecated document about "Correspondence" dated 2010, the chapter on résumés describes a ConTeXt reimplementation of the moderncv package. Is this still usable, and if so, where can I get the relevant files ? Thanks in advance Laurent Steffan

3 5

upload
by Hans Hagen 06 Dec '21

06 Dec '21

Hi, a new upload - some keywords renamed in the engine and therefore more split between mkiv and lmtx (hopefully i included all files) .. if something doesn't work any more it might be because i missed a rename. - i finally decied that it does make sense to have native loops at the primitive level (after all, metapost as macro language also has them) and although much is possible in macros it doesn't mean we have to do it the (often ugly and showing-off-by-abusing-side-effects way). We have just a constructor: \unexpandedloop 1 100 1 {.} and a fully expandable one for e.g. use in \edef: \expandedloop 1 100 1 {.} plus an also fully expandable one for anywhere but with potential side effects (out of order local loops): \localcontrolledloop 1 100 1 {.} complemented by a few status primitives (integers, use \the or \number to serialize them): \currentloopiterator \currentloopnesting and a quitter that aborts at the next iteration: \quitloop as usual it's experimental for a while. Among the rationales are 'less tracing clutter', 'performance' and 'more natural primitive tex coding' (but that one is personal). 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 -----------------------------------------------------------------

2 2

m-database module error since update
by Jan-Erik Hägglöf 05 Dec '21

05 Dec '21

Since my update to LMTX 2021-12-03 the following error occured: tex error > tex error on line 41 in file /Users/jan-erikhagglof/context/context-osx-64/tex/texmf-context/tex/context/modules/mkiv/m-database.mkiv: Missing \endcsname inserted <to be read again> \endlocalcontrol <argument> \c !separator <macro> \mult_interfaces_get_parameters_item_okay #1=#2,->\ifarguments \or \mult_interfaces_get_parameters_item_error \else \defcsname \m_mult_interfaces_namespace #1 \endcsname {#2}\fi <macro> \mult_interfaces_get_parameters_item #*#1,->\ifarguments \else \mult_interfaces_get_parameters_item_okay #1, \ignorearguments \expandafter \mult_interfaces_get_parameters_item \fi <argument> \c !separator={,}, \c !quotechar=, \c !commentchar=, \c !strip=\v !no, \c !before=, \c !after=, \c !first=, \c !last=, \c !left=, \c !right= <macro> \mult_interfaces_get_parameters_indeed #1]->\mult_interfaces_get_parameters_item #1 \ignorearguments \ignorearguments ... <line 8.41> 31 [\c!separator={,}, 32 \c!quotechar=, 33 \c!commentchar=, 34 \c!strip=\v!no, 35 \c!before=, 36 \c!after=, 37 \c!first=, 38 \c!last=, 39 \c!left=, 40 \c!right=] 41 >> 42 % \let\currentdatabase\empty \the\everypresetdatabase % or just: 43 44 \setupdatabase 45 [\c!separator={,}] 46 47 \def\module_database_process#1#2#3% 48 {\edef\currentdatabasetype{#1}% 49 \edef\currentdatabase {#2}% 50 \edef\currentdatabasename{#3}% 51 \ifx\currentdatabasename\empty The control sequence marked <to be read again> should not appear between \csname and \endcsname. I have an older version of LMTX 2021-08-10 on my laptop that works fine on same document. Thanks in advance Jan-Erik Hägglöf

1 0

Blank lines discarded when \typing
by Thangalin 03 Dec '21

03 Dec '21

Note the presence of double-spaced blank lines in the following document and in the attached source file: \setuptyping[numbering=line] \starttext \startbuffer[javacode] try { final var num = stack.pop(); if( num != null ) { stack.push( blah ); } return true; } \stopbuffer \type{\typebuffer}: \typebuffer[javacode] \type{\typing}: \starttyping try { final var num = stack.pop(); if( num != null ) { stack.push( blah ); } return true; } \stoptyping \type{\typefile}: \typefile{t.java} \stoptext There appear to be two issues. First, \typefile produces what I'd consider the "correct" result, where the double-spaced lines appear on the page as a double-space. Both the \typebuffer and \typing commands ignore double-spacing. The double-spacing is also ignored by \xmldisplayverbatim. How would you configure to give \typebuffer, \typing, and \xmldisplayverbatim to honour double-spaces the same way as \typefile? Second, of lesser importance, is that the blank lines aren't numbered. This makes the line numbers inconsistent with respect to IDEs. How would you label all blank lines as well? Out of curiosity, does the second issue relate to the first? Thank you!

1 0

Wikified \commalistsentence
by Andres Conrado Montoya 03 Dec '21

03 Dec '21

Hi, just to let you know https://wiki.contextgarden.net/Command/commalistsentence has been wikified, feel free to make corrections or changes. -- 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

1 0

Bad linebreak in figure caption
by Marco Patzer 03 Dec '21

03 Dec '21

Hi! The caption "FOO" runs into the right figure's caption: \setuplayout [width=18.4cm] \setuptolerance [verytolerant, stretch] %% even with stretch \starttext \startplacefigure \startfloatcombination \startplacefigure [title=Unexpectedly unnecessary FOO-BAR whatever] \framed[width=.4\textwidth]{} \stopplacefigure \startplacefigure [title={Lorem ipsum dolor siit amet}] \framed[width=.4\textwidth]{} \stopplacefigure \stopfloatcombination \stopplacefigure \stoptext Why does ConTeXt not break the line between "unnecessary" and "FOO"? How to kindly persuade it to do so? Marco LMTX 2021.11.26 11:38

3 4

xml processing errors after latest upgrade
by denis.maier＠unibe.ch 01 Dec '21

01 Dec '21

Hi, the latest update may have introduced problems for xml processing : For a document I could convert with version 2021.10.24 21:45 without problems gives me now this error : %%%%%%%%%%%%%%%%%%%%%%%%% ... structure > sectioning > title @ level 2 : 0.0 -> \documentvariable {title} fatal lua error: registered function call [929]: ...ext/tex/texmf-context/tex/context/base/mkiv/scrn-ref.lua:31: attempt to call a nil value (upvalue 'expandcurrent') stack traceback: ...ext/tex/texmf-context/tex/context/base/mkiv/scrn-ref.lua:31: in function <...ext/tex/texmf-context/tex/context/base/mkiv/scrn-ref.lua:27> (...tail calls...) mtx-context | fatal error: return code: 1 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Not sure what is going wrong. Any hints how I can start debugging? Any ideas what could have caused that change? (Ok, let's build a MWE..) Best, Denis

4 10

getting sha512 from text in buffer
by Pablo Rodriguez 01 Dec '21

01 Dec '21

Dear list, I have this minimal sample: \ctxlua{require("util-sha")} \def\sha#1{% \ctxlua{context(utilities.sha2.hash512("#1"))}} \startbuffer[text] hola \stopbuffer \starttext \sha{hola} \sha{\typebuffer[text]} \stoptext How can I get that both commands get the same sha512sum? Many thanks for your help, Pablo

1 0

new upload
by Hans Hagen 01 Dec '21

01 Dec '21

Hi, (1) See previous mails on the list (those who requested it have to wikify): - mixed bars (with limitations) - horizontal registers (flushing) (2) As a side effect of reshuffling some code (as well as being complete): - \boxshift 0 = 10pt - hbox shift -10pt{...} These box shifts are what \moveleft, \raise etc use as well as some internal constructors like math. (3) Because there is no reason for a limitation to rules and boxes we can now also do: - x\cleaders \glyph`! \hfill x where as usual \glyph taking some options. (4) A few internals that users are unlikely to encounter (unless they mess with weird tokens in lua). Hopefully no bad side effects of all this (and if so, easy to solve). 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 -----------------------------------------------------------------

2 2