- ntg-context - Mailing Lists

Cron <context@zapf> /var/www/aanhet.net/context/bin/cron/context-mirror
by root＠ntg.nl 03 May '22

03 May '22

receiving incremental file list ./ ctan.lsr document-2.htm download-1.htm download-2.htm install.htm logo-ade.png logo-cts.png logo-pod.png rss.xml show-fil.pdf context/latest/ context/latest/cont-mpd.zip context/latest/cont-ppc.zip context/latest/cont-sci.zip context/latest/cont-tmf.zip sent 90,352 bytes received 18,536,958 bytes 3,386,783.64 bytes/sec total size is 456,819,434 speedup is 24.52 Running archiver: New dir: /var/www/aanhet.net/context//htdocs/archives/context-2022-05-02.17 137316935 /var/www/aanhet.net/context//htdocs/archives/context-2022-05-02.17/latest 126745317 /var/www/aanhet.net/context//htdocs/archives/context-2022-05-02.17/current 18956262 /var/www/aanhet.net/context//htdocs/archives/context-2022-05-02.17/alpha 126707516 /var/www/aanhet.net/context//htdocs/archives/context-2022-05-02.17/beta 409730126 /var/www/aanhet.net/context//htdocs/archives/context-2022-05-02.17 409730126 total

3 2

XML processing instructions
by Duncan Hothersall 03 May '22

03 May '22

I have a big set of existing XML books (held in a derivative of DocBook) which I'm looking to start processing directly with ConTeXt. (Up to now I have a system which converts the XML into ConTeXt code which is then processed, but this is inefficient and lots of the code is now unsupported.) I've had some success producing output, but my first real sticking point has come with processing instructions. The existing XML contains lots of processing instructions of the form <?capdm whatever?>, some of which can be conditional and introduce new data etc. But I'd be happy at this stage if I could just process the most basic one of them, which is used to introduce a line stop in a running paragraph of text. My best guess at how to do this was to use the lxml.preprocessor function to convert the processing instruction into an element, and then process the element as normal. But (a) my attempt didn't work, and (b) there may well be a better way. Minimal working example below, except that obviously the processing instruction bit doesn't work! Thanks for any help or insights. Duncan MWE: ------ \startbuffer[demo] <book> <para>A paragraph with<?capdm force_line_stop?>a processing instruction.</para> </book> \stopbuffer \startxmlsetups xml:demo:base \xmlsetsetup{#1}{*}{xml:demo:*} \stopxmlsetups \xmlregisterdocumentsetup{demo}{xml:demo:base} \startxmlsetups xml:demo:book \xmlflush{#1} \stopxmlsetups \startxmlsetups xml:demo:para \xmlflush{#1}\endgraf \stopxmlsetups \startluacode function lxml.preprocessor(data,settings) return string.find(data,"<?capdm *force_line_stop?>") and string.gsub(data,"<?capdm *force_line_stop?>","<capdmlinestop></capdmlinestop/>") or data end \stopluacode \startxmlsetups xml:demo:capdmlinestop \crlf \xmlflush{#1} \stopxmlsetups \setupbodyfont[modern] \starttext \xmlprocessbuffer{demo}{demo}{} \stoptext ------

2 5

fatal error again in LMTX
by Pablo Rodriguez 02 May '22

02 May '22

Hi Hans, as already reported (https://mailman.ntg.nl/pipermail/ntg-context/2022/105443.html) LMTX (from 2022.05.02 16:19) quits messaging only fatal error with such a sample: \starttext \startitemize \item one \stoptext I know that \stopitemize is missing above. But in real--world documents, this mistake may need hours to be fixed. Would it be possible that LMTX could provide more verbose information about unfinished \start-commands? Many thanks for your help, Pablo

1 0

process list items differently depending on position in list
by denis.maier＠unibe.ch 02 May '22

02 May '22

Hi, I need to process a comma separated list, and adapt the formatting according to the position of an item in the list (example below). Expected output would be: {\bf foo }, {\em bar} and baz. Is that possible? Can I somehow get the position of an item in the list? (My understanding is that \processcommalist and \processcommacommand apply a command to each list item, but there is no such thing as <position in the list>... I hope I'm wrong here.) Or is that something where using Lua would be a better choice? Best, Denis %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \define[1]\command {#1} \define\somelist {foo, bar, baz} \starttext \processcommacommand [\somelist] \command \stoptext %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

2 3

\getcommacommandsize not working in lmtx
by denis.maier＠unibe.ch 02 May '22

02 May '22

Hi, I've just ran into a behaviour that runs against what is shown on the wiki, https://wiki.contextgarden.net/System_Macros/Comma_Separated_Lists Maybe a bug? The wiki says you can use \getcommacommandsize to get the length of a comma separated list, but it does not seem to work. MWE below. Best, Denis \define\somelist {foo, bar, baz} \starttext \getcommacommandsize[\somelist] \commalistsize % Expected : 3 % Actual : 1 \expandafter\getcommalistsize\expandafter[\somelist] \commalistsize % Expected : 3 % Actual : 3 \stoptext

2 1

recursion in a table
by Henning Hraban Ramm 02 May '22

02 May '22

Hi, I was playing with the example from https://wiki.contextgarden.net/Scaling_Rotating_Mirroring_Clipping#Location… and tried to put it in a tabulate: \useMPlibrary[dum] \setupexternalfigures[width=3em,height=2em,frame=on,] %\def\TXT{\ruledhbox{\bf(XyX)}} \def\TXT{\externalfigure[pic]} \starttabulate[|l|l|l|l|l|l|] \NC\NC normal\NC depth\NC fit\NC broad\NC high\NC\NR \HL \dostepwiserecurse{0}{359}{45}{% %\expanded{\setuprotate[rotation=\recurselevel]} \NC{\expanded{\recurselevel}˚}% \NC{\ruledhbox{X\rotate[location=normal,rotation=\recurselevel]{\TXT}X}}% \NC{\ruledhbox{X\rotate[location=depth,rotation=\recurselevel] {\TXT}X}}% \NC{\ruledhbox{X\rotate[location=fit,rotation=\recurselevel] {\TXT}X}}% \NC{\ruledhbox{X\rotate[location=broad,rotation=\recurselevel] {\TXT}X}}% \NC{\ruledhbox{X\rotate[location=high,rotation=\recurselevel] {\TXT}X}}% \NC\NR} % \HL % error \stoptabulate This works, but \recurselevel is always 0. I know I must expand it (like in the original example), but I can’t make it work within the tabulation. In the first column, \expanded{\recurselevel} stays 0, and rotation=\expanded{\recurselevel} gives an error, while the \setuprotate line has no effect (if I remove "rotation=\recurselevel", of course). How would that work? Also, \HL doesn’t work at the end, and the second line of the error message makes no sense: """ I expect to see \noalign only after the \cr of an alignment. Proceed, and I'll ignore this case. mtx-context | fatal error: return code: 1 """ Hraban

3 2

Fuzzy paragraph when exporting to XML
by Aditya Mahajan 01 May '22

01 May '22

Hi, I am trying to debug a bug-report for t-vim: https://github.com/adityam/filter/issues/64 Exporting with trackers=export* gives a warning: backend > export > fuzzy paragraph: I have managed to narrow it down to the attached MWE (which does not depend on the t-vim module at all). Compiling it using $context --trackers=export\* lines gives the fuzzy paragraph warning. Any hints on how to resolve this? Thanks, Aditya

2 3

\doifnotdocumentargument in proper Lua
by Pablo Rodriguez 29 Apr '22

29 Apr '22

Dear list, I have the following command in one of my documents: \doifnotdocumentargument{no-metadata} {\ctxlua{document.transfer_metadata(document.main_file)}} Which would be the right way to write \doifnotdocumentargument in proper Lua? Many thanks for your help, Pablo

1 0

Problem with a defined colour in MetaFun
by Keith McKay 29 Apr '22

29 Apr '22

Hi, In the MWE below I define an rgb colour, myColor1, using random numbers for the r, g and b components. I then use it to fill a unitsquare the size of the page, which works as expected. In the loop that follows I then use the defined colour, myColor1, along with white and the variable r to create shades of myColor1 as in the MWE below. However, myColor1 is not recognised in the loop and seems to be replaced by black, although if I use a predefined colour, in this case BurntSienna from the crayola collection, it works as expected. I have tried a number of ways to get this to work as shown in the code but without success. I would be grateful for any suggestions. Best Wishes Keith McKay %%%%%%%%%%%%%%%%%%%%MWE%%%%%%%%%%%%% \setuppapersize[A4,portrait] \usecolors[crayola] \starttext \dorecurse{10}{ \startMPpage StartPage; \definecolor[name="myColor1", r = uniformdeviate(1), g = uniformdeviate(1), b = uniformdeviate(1) ] ; fill unitsquare xscaled PaperWidth yscaled PaperHeight withcolor "myColor1"; for i =2 step 2 until 10: r := i/10; fill unitsquare xscaled 5cm yscaled .5cm shifted (1cm,i*cm) withcolor(r[\MPcolor{BurntSienna},white]); fill unitsquare xscaled 5cm yscaled .5cm shifted (7cm,i*cm) withcolor(r[\MPcolor{myColor1}, white]); fill unitsquare xscaled 5cm yscaled .5cm shifted (13cm,i*cm) withcolor(r[\MPcolor{"myColor1"}, white]); %fill unitsquare xscaled 5cm yscaled .5cm shifted (13cm,i*cm) withcolor(r[myColor1 , white]); This line causes an error. endfor; StopPage; \stopMPpage } \stoptext %%%%%%%%%%%%%%%%%%%%%%%%%%%end MWE%%%%%%%%%%% I am running: system > system > ConTeXt ver: 2022.04.20 19:18 LMTX fmt: 2022.4.26 int: english/english system > system > 'cont-new.mkxl' loaded

3 5

Re: [NTG-context] lua-widow-control module error in LMTX
by Max Chernoff 29 Apr '22

29 Apr '22

On 2022-04-27 3:59 p.m., Eduardo Bohoyo wrote: > When I uncomment grid=yes in my \setuplayout, lwc makes its real > appearance on the scene. So it looks like lwc was broken with grid snapping. This surprised me -- I originally wrote lwc *specifically* to use with grid snapping -- but it looks like I quickly forgot about that goal and never actually tested it with grids. > I suppose that in other documents than mine, > i.e. less complex, this performance would be a success. But in my file > it is, considering my current aesthetic requirements, a failure. This is > because for me grid=yes is a non-negotiable part of my code. I _think_ that I've fixed it now. Can you try the beta version at https://github.com/gucci-on-fleek/lua-widow-control/releases/tag/release-47… please? Hopefully this solves the issue. > Do you want the new pdf with lwc actually acting on my file? Then you > can get a better idea of what I mean by the end of some pages when I > comment grid=yes (apart from the mischief that happens with the > horizontal spaces in some paragraphs of the bibliographic section). > > Or, if you prefer, and you need more feedback, I can send you my current > code to use it as a test bench for " daring " texts. I was able to reproduce the issue just by adding \setuplayout[grid=yes] to my "standard" test files, so I shouldn't need anything else, provided that the above beta actually fixes anything. If there are still lingering issues, then having the TeX source would likely simplify things on my end. -- Max

3 5