March 2020 - ntg-context - NTG Mailing Lists

Why does this METAPOST vardef 'save' statement fail?
by Gerben Wierda 14 Mar '20

14 Mar '20

I have this vardef: vardef Foo(expr w, h) = save pth; path pth; %save pth2; path pth2; save pic; picture pic; pth = fullsquare xysized (w, h); %pth2 = fullsquare xysized (h/4, h/8) pic := image ( draw pth; %draw pth2 shifted (-w/2, -h/4); % all kind of stuff here ); setbounds pic to pth; pic enddef ; As soon as I uncomment the bold line (first comment) a mtxrun fails. Whatever I try, a single save statement, etc., I fail in getting a second local variable. The METAPOST manual is no help. The error shown is: metapost log > ! Extra tokens will be flushed. metapost log > <to be read again> metapost log > 2 metapost log > Foo->...h;path.pth;save.pth2 metapost log > ;path.pth2;save.pic;pictur... metapost log > <*> ... ; s := Foo(8cm, 2cm) metapost log > ; draw s; drawdot center l... metapost log > Why? G

1 1

Hatch color in a table cell
by Fabrice Couvreur 12 Mar '20

12 Mar '20

Hi, I would like to hatch the cell green. Thank you. Fabrice \usecolors[xwi] \startuniqueMPgraphic{meta:hash}{linewidth,linecolor,angle,gap} if unknown context_back : input mp-back ; fi ; some_hash ( OverlayWidth, OverlayHeight , \MPvar{linewidth}, \MPvar{linecolor} , \MPvar{angle}, \MPvar{gap} ) ; \stopuniqueMPgraphic \setupMPvariables [meta:hash] [gap=.25\bodyfontsize, angle=45, linewidth=\overlaylinewidth, linecolor=\overlaylinecolor] \def\metahashoverlay#1{\uniqueMPgraphic{meta:hash}{angle=#1}} \defineoverlay[meta:hash:right] [\metahashoverlay{ +45}] \defineoverlay[meta:hash:left] [\metahashoverlay{ -45}] \defineoverlay[meta:hash:horizontal][\metahashoverlay{+180}] \defineoverlay[meta:hash:vertical] [\metahashoverlay{ -90}] \starttext \startmidaligned \startxtable [align={lohi,middle}, width=1.5cm, background=color, backgroundcolor=white, framecolor=purple, meta:hash:linecolor=green] \startxrow \startxcell[background=color,backgroundcolor=paleturquoise] i \stopxcell \startxcell[background=meta:hash:right,frame=off] \stopxcell \startxcell 0 \stopxcell \startxcell 1 \stopxcell \startxcell 2 \stopxcell \stopxrow \startxrow \startxcell[background=color,backgroundcolor=paleturquoise] S \stopxcell \startxcell 0 \stopxcell \startxcell \stopxcell \startxcell \stopxcell \startxcell \stopxcell \stopxrow \startxrow \startxcell[background=color,backgroundcolor=paleturquoise] a \stopxcell \startxcell 3 \stopxcell \startxcell \stopxcell \startxcell \stopxcell \startxcell \stopxcell \stopxrow \stopxtable \stopmidaligned \stoptext

1 0

ePub issues: XML structure
by Henning Hraban Ramm 12 Mar '20

12 Mar '20

Not only Hans van der Meer is producing (or trying to produce) ePubs at the moment; I reviewed my XSLT workflow (https://wiki.contextgarden.net/Epub_Sample) since my publisher colleagues and our distributor aren’t happy about just publishing PDFs as eBooks. While the first book in a series of four is now ready with a lot of manual corrections, in the second one the XML structure is messed up: the chapter title structure comes only after the chapter content, and index entry tags are empty with the actual entry behind like this: <paragraph>Ein sentimentales Rührstück ist <highlight detail="emph">Rico, Oskar und die Tieferschatten</highlight> dennoch nicht. Die beiden Hauptdarsteller <registerlocation detail="index" internal="396"></registerlocation>Anton Petzold (Rico) und <registerlocation detail="index" internal="397"></registerlocation>Juri Winkler (Oskar) füllen ihre Rollen ganz wunderbar aus...</paragraph> In ConTeXt code I marked the actors with \def\NPers#1#2{\index{#2, #1}#1 #2} as \NPers{Anton}{Petzold}. But since that just uses \index, the XML tag should catch the contents, don’t you think? I’ll come up with a MWE; don’t know if I’ll manage to reproduce the title/contents mixup though. The other book’s export is ok within the same project. It uses the same environment, but a slightly differing chapter setup. Any hints which setting could cause the re-ordering? (And I use \startchapter … \stopchapter of course.) Best, Hraban

4 6

Install Tikz in LMTX tree
by Jorge Manuel 11 Mar '20

11 Mar '20

Dear Sirs, I download tikz.tds.zip <http://mirrors.ctan.org/install/graphics/pgf/base/pgf.tds.zip> from ctan and unzip it in /Applications/Context/context-osx-64/tex/texmf. Next I run mtxrun --generate context —make My test file contains: #### \setupcolors[state=start] \usemodule[tikz] \starttext \starttikzpicture [node distance=4cm, place/.style={circle,draw=blue!50,fill=blue!20,thick, inner sep=0pt,minimum size=6mm}] \node[place] (wat) {}; \node[place] (wag) [below=of wat] {}; \stoptikzpicture \stoptext #### The log is: open source > level 1, order 1, name 'cont-yes.mkiv' system > system > ConTeXt ver: 2020.02.17 19:36 MKIV beta fmt: 2020.3.9 int: english/english system > system > 'cont-new.mkiv' loaded open source > level 2, order 2, name '/Applications/Context/context-osx-64/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv' system > beware: some patches loaded from cont-new.mkiv close source > level 2, order 2, name '/Applications/Context/context-osx-64/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv' system > files > jobname 'Recuperacao', input './Recuperacao', result 'Recuperacao' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 2, order 3, name './Recuperacao.tex' modules > 'tikz' is loaded open source > level 3, order 4, name '/Applications/Context/context-osx-64/tex/texmf/tex/context/third/pgf/frontendlayer/t-tikz.tex' loading > ConTeXt User Module / tikz open source > level 4, order 5, name 't-pgf.tex' loading > ConTeXt User Module / pgf open source > level 5, order 6, name 't-pgfcor.tex' loading > ConTeXt User Module / pgfcor open source > level 6, order 7, name 't-pgfsys.tex' loading > ConTeXt User Module / pgfsys open source > level 7, order 8, name 't-pgfrcs.tex' loading > ConTeXt User Module / pgfrcs open source > level 8, order 9, name 't-pgfmod.tex' loading > ConTeXt User Module / pgfmodules system > module wrapping error in 'tikz' close source > level 8, order 9, name 't-pgfmod.tex' open source > level 8, order 10, name 'pgfutil-common.tex' open source > level 9, order 11, name 'pgfutil-common-lists.tex' close source > level 9, order 11, name 'pgfutil-common-lists.tex' close source > level 8, order 11, name 'pgfutil-common.tex' open source > level 8, order 12, name 'pgfutil-context.def' close source > level 8, order 12, name 'pgfutil-context.def' open source > level 8, order 13, name 'pgfrcs.code.tex' tex error > tex error on line 11 in file pgfrcs.code.tex: ! Package PGF Error: PGF requires etex in extended mode \pgfutil@packageerror #1#2#3->\errhelp {#3}\errmessage {Package #1 Error: #2} l.11 \pgfutil@packageerror{PGF}{PGF requires etex in extended mode}{} % <empty file> This error message was generated by an \errmessage command, so I can't give any explicit help. Pretend that you're Hercule Poirot: Examine all clues, and deduce the truth by order and method. Anybody has a clue how to fix this? Thanks to all.

3 5

Re: [NTG-context] XML to ConTeXt: converting date attribute from ISO date
by Axel Kielhorn 11 Mar '20

11 Mar '20

> Am 11.03.2020 um 15:19 schrieb Hans Hagen <j.hagen(a)xs4all.nl>: > > On 3/11/2020 3:12 PM, Axel Kielhorn wrote: >>> Am 11.03.2020 um 15:01 schrieb Hans Hagen <j.hagen(a)xs4all.nl>: >>> >>> On 3/11/2020 2:14 PM, Axel Kielhorn wrote: >>>> >>>> Had to change it to: >>>> \startluacode >>>> function xml.finalizers.tex.MyDate(e,what,how) >>>> local ee = e[1].at[what] >>>> local t = (string.split(ee,"-")) >>>> context.date( >>>> { y = t[1], m = t[2], d = t[3] }, >>>> { how } >>>> ) >>>> end >>>> \stopluacode >>> You mean the () around the split? weird. Anyway, there's also a time splitter (dedicated to Alan who needed one): >> No, sorry that’s an artifact from testing. >> I had to assign: >> local ee = e[1].at[what] >> and >> string.split(ee,"-") >> in two steps while the original had >> local t = string.split(e[1].at[what],"-") > still strange because it's one value, if it were multiple you could do This is strange. Now it works. Earlier I had context.date complaining that it got a table and not a string. That’s why I took the t = assignment apart into pieces. Now I copied the code from the original reply and it works. Sorry for the noise. Axel

2 2

Outputting custom types in MKiv bibliography
by Mike O'Connor 11 Mar '20

11 Mar '20

Hello, I’m trying to create my first publication using ConTeXt mkiv. All going well except for the bibliography formatting. Previously I have used LaTeX, standard entry types in BibTeX, and custom output formats using Biblatex. My publication cites lots of historical sources, viz.: (1) Newspaper articles — currently stored as ‘article’ types in BibTex. (2) Archival sources (historic letter, some leather-bound volume, a catalogued box of old photographs, etc.) — currently stored as ‘unpublished’ or ‘misc'. I would prefer to store these (in BibTeX, buffer, lua, or xml) as custom types (eg. ‘newspaper’, ‘archivalItem’), create setups for how they are output and which fields I output. I found a ’newspaper’ type (and other non-BibTeX types) defined in publ-imp-apa.mkiv as: \startsetups btx:apa:list:newspaper \fastsetup{btx:apa:list:article} \stopsetups I hoped this would mean I could output something: Boxing. (1903, September 13). The Sunday Times, p.8 However, if I create an item of type 'newspaper’ and \cite it I get an output of all stored fields: newspaper: [day: 13] [journal: {The Sunday Times}] [month: 09] [pages:8][title: {Boxing.}] [type: newspaper article] [year: 1903] A similar thing happens if I try to cite the standard BibTeX type ‘misc’. If I store the newspaper item as type ‘article’ I get: “Boxing.”, The Sunday Times, 8, 1903. (missing day and month) Is it relevant that there is a problem when I include \showbtxfields[rotation=30] in my document? The resulting table has ‘*’ for fields in ‘article’, ‘book’, ‘demo-a’, ‘demo-b’ but the columns for ‘newspaper’ and ‘misc’ are empty. Any pointers gratefully received. Cheers, Mike O’Connor P.S. I am working in TeXShop on OSX (10.11.3), and it reports: This is LuaTeX, Version beta-0.80.0 (TeX Live 2015) (rev 5238) ConTeXt ver: 2015.05.18 12:26 MKIV current fmt: 2016.3.19 int: english/english

4 5

Need help processing XML in luacode
by Axel Kielhorn 11 Mar '20

11 Mar '20

Hi, after one year I’m back at a project processing XML with ConTeXt. Here is what I want to do: I have an XML file that I want to format with ConTeXt. I got this working last year. Now I want to take some information from a second file. My idea is to read the second file, store the data into a table and write auxiliary functions to access the data and insert them into the TeX output. When I process the included files with context --environment=prozess-style-ecm.tex prozess.xml I get [ctxlua]:19: table index is nil 12 13 doc = xml.load(doclistfile, settings) 14 15 for v in xml.collected(doc,"/doclist/psdoc/") do 16 -- print ((xml.filter(v,"//docnr/stripped()"))) 17 docnr = (cropstring(xml.filter(v,"/docnr/text()"))) 18 docname = (cropstring(xml.filter(v,"/docname/text()"))) 19 -- es kann mehrere DOCAN geben! 20 docan = (cropstring(xml.filter(v,"/docan/text()"))) 21 docverantwortlich = (cropstring(xml.filter(v,"/docverantwortlich/text()"))) 22 >> docstruktur[docnr]={} The xml.collected works, but the xml.filter returns nil. What did I miss? mtx-context | ConTeXt Process Management 1.03 mtx-context | mtx-context | main context file: /Volumes/Macintosh HD/usr/local/texlive/context-109/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2020.01.30 14:13 mtx-context | main context file: /Volumes/Macintosh HD/usr/local/texlive/context-109/tex/texmf-context/tex/context/base/mkiv/context.mkxl mtx-context | current version: 2020.01.30 14:13 The same code works when I use it in a Lua file that I call with mtxrun --script panalyse.lua Greetings Axel

2 2

Only-black emojis in LMTX
by Alejo Barrio Blaya 11 Mar '20

11 Mar '20

I'm trying to get emojis working. The examples that do, are only printing plain black emojis. Not colors, nor greyscales. I'm using the latest beta of LMTX. Thanks, Alejo

3 2

\bTABLE bug, please help !
by Taco Hoekwater 10 Mar '20

10 Mar '20

Hi, Please see the attached example. The \bTABLE in the footer of the page ‘inherits' the first line of the split \bTABLE in the running text. I have no idea how to fix this or why this even happens. Help! I’ll need a way to work around this problem in my current ConTeXt installation for this project. That is now nearly 4 years old, but the same bug is still happens with a new beta of mkiv. I cannot switch to \startxtable because I would need \startembeddedxtable, and that has way too many limitations to be useful in this project. Best wishes, Taco

2 3

update lmtx / luametatex 2.05
by Hans Hagen 10 Mar '20

10 Mar '20

Hi, I uploaded an update of lmtx. The current version of luametatex is 2.05 which is kind of the first supposedly stable release because it incorperates most of what was on my agenda for the first phase (functionality level 20200229 which was when it happened). Of course I expect there to be bugs but not much that can't be solved fast. This version will be the starting point for Wolfgang and me to explore future possibilities (more deep down in the context source code as well as in the engine). We'll see. Although the performance of lmtx compared to mkiv is hit by more time onsuming backend code, it gets compensated by some optimizations elswehere, a smaller memory footprint, etc. As no one complains about performance it doesn't matter much anyway. Unless you used luajittex there will be no real difference in most cases. We're in tex live code freeze time so I don't want to change much to the lua and tex part of the distribution right now but nevertheless there has been some minor (practical) adaptations in applying fonts that also reflects on mkiv but that should not be noticeable in practice (also because I rejected some adaptations that had a performance impact in mkiv). Mojca and I decided to support yet another platform, this time arm 64 bit for which we use a raspberry pi running ubuntu 64 bit, which brings the platforms supported by the build bot to 15: freebsd freebsd-amd64 openbsd6.5 openbsd6.5-64 openbsd6.6 openbsd6.6-64 linux-armhf linux-aarch64 linux linux-64 osx-64 mswin win64 plus windows-clang-x86_64 and windows-x86_64 because they help to identify issues (and provide useful compiler warnings) but for now we stick to the mingw variants because they run a few percent faster than the (smaller) native windows version. For those interested in tiny machines: the rpi performs roughly one third of what my laptop does which is not bad, although I suppose a more modern intel gen 10 i9 machine will be quite a bit faster. The benchmark is processing the luametatex manual which takes about 12 seconds on the laptop (252 pages, lots of tables, 250+ mp images, 20+ fonts files). A 64 rpi is a little faster than the 32 bit variant. Because tex is a single thread/core process overclocking the little thingie has a positive effect too. Anyway, it makes us confident that when the source gets into the distribution, which depends on the upcoming repository setup and should not interfere with the tl code freeze, users can compile themselves, something that can contribute to a more comfortable feeling of independence of complex and large compilation infrastructures. Hopefully I didn't mess up too much, 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