ntg-context April 2021

ntg-context@ntg.nl

40 participants
73 discussions

xml processing in latest
by Thomas A. Schmitz 21 Apr '21

21 Apr '21

Hi all, the latest has some strange problems with xml processing. The example below shows an issue with itemize. In my real file, I also get pages that are filled only two thirds and rugged right instead of justified, but I haven't been able to reproduce this in a MWE. Maybe this one can give a start; I assume it's some fundamental typo somewhere. All best Thomas \startbuffer[test] <document> <p>test</p> <numbered> <item> one </item> <item> two </item> </numbered> </document> \stopbuffer \startxmlsetups xml:testsetups \xmlsetsetup{#1}{*}{-} \xmlsetsetup{#1}{document|p|numbered|item}{xml:*} \stopxmlsetups \xmlregistersetup{xml:testsetups} \startxmlsetups xml:document \xmlflush{#1} \stopxmlsetups \startxmlsetups xml:p \xmlflush{#1} \par \stopxmlsetups \startxmlsetups xml:numbered \startitemize [n] \xmlflush{#1} \stopitemize \stopxmlsetups \startxmlsetups xml:item \startitem \xmlflush{#1} \stopitem \stopxmlsetups \starttext \xmlprocessbuffer{main}{test}{} \stoptext

2 3

\processassignmentlist inside a \setup... or related
by Jairo A. del Rio 20 Apr '21

20 Apr '21

Hi, list! I hope my example shows clearly enough what I intend to do: \startluacode userdata = userdata or {} userdata.mydata = {} local function registermydata(data,...) table.insert(userdata.mydata, data) end interfaces.implement{ name = "registermydata", arguments = "2 strings", actions = registermydata } \stopluacode \unprotect \def\mysetups[#1]% {\getdummyparameters[#1]% \processassignmentlist[#1]\clf_registermydata} \protect \starttext \mysetups[love=nice,hate=awful]% \dummyparameter{love} \cldcontext{userdata.mydata[2]} \stoptext What I want to know is if there's a less hackish way to pass keys (yep, only keys, not values) to Lua using \getdummyparameters (actually I'm using an user-defined \setupsomething, but it's more or less the same) and \processassignmentlist. Is it possible, for instance, to automatically pass a key to Lua when it's set in \setupsomething? Thanks in advance. Jairo PS: Sorry if I missed something in the test suite again

2 3

\frac error
by thierry horsin 19 Apr '21

19 Apr '21

Hi everybody Since I updated to the last version of context , I cannot use \frac anymore in \startformula. I get the following message "I can't work with sizes bigger than about 19 feet. Continue and I'll use the largest value I can." Yet, between $ $ it is fine. Any ideas ? Many thanks.

2 5

context() does not ignore space in empty line
by Sylvain Hubert 19 Apr '21

19 Apr '21

Dear list, does anyone have an idea why, in the example below, context() starts a new paragraph at "\n\n" but not at "\n \n" with a space in between? Is there any way to fix it? \starttext Without using context(), inside the next parentheses is a new line: ( ) note that a space sits between the two line breaks. \startluacode context('Using context(), inside the next parentheses is also a new line: (\n\n) because there is *no* space between the two line breaks.\n\n') context('Using context(), inside the next parentheses is however *no* new line: (\n \n) because of the space between the two line breaks.\n\n') \stopluacode \stoptext Any help is appreciated. Best, Sylvain

2 1

Analyze hyphenations
by denis.maier＠ub.unibe.ch 18 Apr '21

18 Apr '21

Hi, a couple of weeks ago Hans has implemented a tracker that adds a list of hyphentated words to the log file. I finally managed to play with this. The result is attached to this mail. This will permit analyzing hyphenations based on a ConTeXt log file. You need to enable hyphenation tracking in the ConTeXt file with \enabletrackers[hyphenation.applied]. Then, you can run the script with lua check-hyphens.lua input_file whitelist.ending As we assume .log for the input_file, the input file should be supplied without file ending. For the (optional) whitelist a file ending has to be supplied. Maybe I should wikify this, any suggestion where that would fit? HTH, Denis

1 0

lmtx update: two experimental features
by Hans Hagen 18 Apr '21

18 Apr '21

Hi, I uploaded a new version. There are two new features that are experimental. This time we attempt to deal with the more tricky things and artifacts of the otherwise nice tex machinery we need to get rid of. One can rightfully argue that they are not really issues as one can work around them (and so they are never brought to attention) but why not make things better (cleaner) if we can. (1) Languages: hyphenation normally uses a hyphen and the engine has some messy work-around-border-cases in the hyphenator. So, I wondered if we could improve that. First of all, there can now be more than one hyphen character so here is the way to deal with it (the hyphenchar code is like the other 'codes'): \hccode"002D = "002D \hccode"2010 = "2010 \hccode"2013 = "2013 \hccode"2014 = "2014 This makes all these four into (kind of) compound word seperators: \startTEXpage \hsize3mm firstpart\char"002D secondpart\blank firstpart\char"2010 secondpart\blank firstpart\char"2013 secondpart\blank firstpart\char"2014 secondpart \stopTEXpage will work ok. There are provisions for those characters being at the left and right edges. All is under low level (engine) option controls (compatibility and such) but currently I enable all. With a bit of definitions one can for the 002D and 2010 cases deal with pre/post variants .. the question is do we need that for more, if so, then I need to add some more code (doable). This feature relates to Denis collection of German compound words and ligature prevention data. Dutch has the same issue. (Denis: we can ditch the compound word entries now, the ones with -.) Also, this kind of automatism (keep in mind that normally tex won't hyphenate the first word in such a compound) is especially handy in cases where there is no control over the input as with xml (when we do have control you can use || as compound word marker). (I'm wondering if we should deal with the typical somewhat archaic tex -- and --- in a different manner, but I'll come back to that.) (2) Math: what is added is not so much an issue in traditional tex math usage which is for journals but as context is used for educational purposes and thereby has quite some tricks built in. Some of these jump through ugly hoops to get it done. Here I stick to color as example. Just try this (notice the spacing): \startTEXpage[offset=10pt] \showmakeup[mathglue]% \enableexperiments[simplegroups]% $ a = b \color[red]{=} c \startcolor[blue]=\stopcolor d $\par $ \sin \color[green]{(x)} = \sin {(x)} $\par \disableexperiments[simplegroups]% $ a = b \color[red]{=} c \startcolor[blue]=\stopcolor d $\par $ \sin \color[green]{(x)} = \sin {(x)}$\par \stopTEXpage The 'simplegroups' experiment enables a more hybrid grouping model but we (read: Wolfgang, Aditya and I, but input is welcome) need to check for side effects carefully. The 'mathglue' tracker is also new, and it exposes what actually goes on. It has to do with the fact that something grouped with { } creates a math list which enforces different spacing but in the case of color that is a side effect we don't want (of course it relates to how context implements the \color macro and one could work around it, but the problem is of a more general nature. 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

Sorting items in Lua
by Jairo A. del Rio 18 Apr '21

18 Apr '21

Hi, list. I want to know how to use ConTeXt sorters, as those used in registers, in Lua. Like this: \starttext \startluacode --Spanish local list = {"ñandú", "perrera", "zócalo", "árnica"} --What's "sortingfunction"? context(table.concat(sortingfunction(list)," ")) \stopluacode \stoptext Also, as registers allow to set a language for sorting, I want to know how to do the same through Lua, e.g., sorting the same list according to English and then Spanish rules. I've searched for examples in the archive, but I've only found cases working on the TeX side. Thank you in advance. Jairo

2 2

\externalfigure for only one page of a multiple page pdf
by a.rosenstock＠web.de 18 Apr '21

18 Apr '21

2 2

No space between \cite and next word.
by Mikael Sundqvist 18 Apr '21

18 Apr '21

Hi, I think there has been some change recently. Is it on purpose that there is no space after the \cite. Look how the parenthesis that ends the citation and the word "text" are set without space inbetween. /Mikael \startbuffer[mybib] @article{a, author = {An Author}, title = {A title}, year = {2021}, } \stopbuffer \usebtxdefinitions [apa] \usebtxdataset [mybib.buffer] \starttext Text \cite[a] text. \placelistofpublications \stoptext

2 2

Macro to write a letter with \ mathscript{}
by Fabrice Couvreur 18 Apr '21

18 Apr '21

Hi, This is going to be difficult to explain because the code below works but in a project with many components does not. Actually the macro does not work in the definition environment in my project but in the same environment of this simple code yes. Thank you for your possible help. Fabrice \setupbodyfont[modern] \setupenumerations [before={}, after={\blank}, alternative=serried, number=no, title=yes, titleleft={(}, titleright={)}, prefix=yes, prefixsegments=chapter, way=bychapter, titlestyle=bold, width=broad] \defineenumeration [definition] [text=Définition, number=no, headcommand=\groupedcommand{}{}, style=slanted] \setupmathematics[stylealternative=calligraphic] \unexpanded\def\CScript#1#2{\start\switchtobodyfont[stixtwo]\m{{\mathscript{#1}}_{#2}}\stop} \unexpanded\def\cscript#1{\start\switchtobodyfont[stixtwo]\m{{\mathscript{#1}}}\stop} \starttext \startdefinition \placefigure[right]{}{ \startMPcode path rectangle; rectangle=unitsquare xscaled 6cm yscaled 4cm; draw rectangle withcolor green; label.bot("\cscript{C}", center rectangle); \stopMPcode} Soit \m{f} une fonction continue et positive sur un intervalle \m{[a\,;b]} et \cscript{C} sa courbe représentative dans un repère orthogonal. L'aire du domaine délimité par la courbe \cscript{C}, l'axe des abscisses et les droites d'équations \m{x=a} et \m{x=b}, exprimée en unité d'aire, est appelée {\bi intégrale de \m{a} à \m{b} de la fonction \m{f}}. \stopdefinition \stoptext

3 3

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ntg-context April 2021