May 2020 - ntg-context - NTG Mailing Lists

Inkscape command line arguments have changed
by Thangalin 19 May '20

19 May '20

$ inkscape --version Inkscape 1.0 (4035a4fb49, 2020-05-01) Pango version: 1.44.7 With the new release of Inkscape, --export-pdf no longer exists. The new options appear to be: --export=type=pdf --export=pdf-version=1.5 (or 1.4) --export-filename=filename.pdf Aditya has shown a work-around on TeX.SE. I've changed the code a little: \startluacode figures.programs.inkscape={ command="inkscape", pdfargument=[[ "%oldname%" --export-dpi=600 --export=type=pdf --export-filename="%newname%" ]], pngargument=[[ "%oldname%" --export-dpi=600 --export=type=png --export-filename="%newname%" ]], } \stopluacode Unfortunately, this does override outdated command line argument. ConTeXt appears to pass in the old argument: context --purgeall --trackers=graphics.conversion filename.tex Shows: Unknown option --export-pdf=images/m_k_i_v_genealogy.svg.pdf How would you replace the export-pdf option for the new version of Inkscape? (I'll send a bug to the Inkscape issue tracker; it strikes me that --export-pdf could have remained an alias.) Thank you!

2 2

LMTX not working in Windows 10
by Jairo A. del Rio 19 May '20

19 May '20

Hi everyone! I've tried installing LMTX on Windows 10 (x64) (I use Ubuntu, but my PC isn't available now). Whatever. When I try to execute context.exe the following appears: ! Parameters must be numbered consecutively. <to be read again> 0 l.214 \def\gobbleoneargument #0 {} ! Parameters must be numbered consecutively. <to be read again> 0 l.215 \def\gobbletwoarguments #0 #0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.215 \def\gobbletwoarguments #0#0 {} ! Parameters must be numbered consecutively. <to be read again> 0 l.216 \def\gobblethreearguments #0 #0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.216 \def\gobblethreearguments #0#0 #0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.216 \def\gobblethreearguments #0#0#0 {} ! Parameters must be numbered consecutively. <to be read again> 0 l.217 \def\gobblefourarguments #0 #0#0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.217 \def\gobblefourarguments #0#0 #0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.217 \def\gobblefourarguments #0#0#0 #0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.217 \def\gobblefourarguments #0#0#0#0 {} ! Parameters must be numbered consecutively. <to be read again> 0 l.218 \def\gobblefivearguments #0 #0#0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.218 \def\gobblefivearguments #0#0 #0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.218 \def\gobblefivearguments #0#0#0 #0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.218 \def\gobblefivearguments #0#0#0#0 {} ! Parameters must be numbered consecutively. <to be read again> 0 l.219 \def\gobblesixarguments #0 #0#0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.219 \def\gobblesixarguments #0#0 #0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.219 \def\gobblesixarguments #0#0#0 #0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.219 \def\gobblesixarguments #0#0#0#0 {} ! Parameters must be numbered consecutively. <to be read again> 0 l.220 \def\gobblesevenarguments #0 #0#0#0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.220 \def\gobblesevenarguments #0#0 #0#0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.220 \def\gobblesevenarguments #0#0#0 #0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.220 \def\gobblesevenarguments #0#0#0#0 #0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.220 \def\gobblesevenarguments #0#0#0#0#0 {} ! Parameters must be numbered consecutively. <to be read again> 0 l.221 \def\gobbleeightarguments #0 #0#0#0#0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.221 \def\gobbleeightarguments #0#0 #0#0#0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.221 \def\gobbleeightarguments #0#0#0 #0#0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.221 \def\gobbleeightarguments #0#0#0#0 #0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.221 \def\gobbleeightarguments #0#0#0#0#0 #0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.221 \def\gobbleeightarguments #0#0#0#0#0#0 {} ! Parameters must be numbered consecutively. <to be read again> 0 l.222 \def\gobbleninearguments #0 #0#0#0#0#0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.222 \def\gobbleninearguments #0#0 #0#0#0#0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.222 \def\gobbleninearguments #0#0#0 #0#0#0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.222 \def\gobbleninearguments #0#0#0#0 #0#0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.222 \def\gobbleninearguments #0#0#0#0#0 #0#0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.222 \def\gobbleninearguments #0#0#0#0#0#0 #0{} ! Parameters must be numbered consecutively. <to be read again> 0 l.222 \def\gobbleninearguments #0#0#0#0#0#0#0 {} ! Parameters must be numbered consecutively. <to be read again> 0 l.224 \def\gobbleoneoptional [#0 ]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.225 \def\gobbletwooptionals [#0 ][#0]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.225 \def\gobbletwooptionals [#0][#0 ]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.226 \def\gobblethreeoptionals[#0 ][#0][#0]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.226 \def\gobblethreeoptionals[#0][#0 ][#0]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.226 \def\gobblethreeoptionals[#0][#0][#0 ]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.227 \def\gobblefouroptionals [#0 ][#0][#0][#0]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.227 \def\gobblefouroptionals [#0][#0 ][#0][#0]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.227 \def\gobblefouroptionals [#0][#0][#0 ][#0]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.227 \def\gobblefouroptionals [#0][#0][#0][#0 ]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.228 \def\gobblefiveoptionals [#0 ][#0][#0][#0][#0]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.228 \def\gobblefiveoptionals [#0][#0 ][#0][#0][#0]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.228 \def\gobblefiveoptionals [#0][#0][#0 ][#0][#0]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.228 \def\gobblefiveoptionals [#0][#0][#0][#0 ][#0]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.228 \def\gobblefiveoptionals [#0][#0][#0][#0][#0 ]{} ! Parameters must be numbered consecutively. <to be read again> 0 l.2655 \def\firstoftwoarguments #1#0 {#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2656 \def\secondoftwoarguments #0 #2{#2} ! Parameters must be numbered consecutively. <to be read again> 0 l.2658 \def\firstofthreearguments #1#0 #0{#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2658 \def\firstofthreearguments #1#0#0 {#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2659 \def\secondofthreearguments #0 #2#0{#2} ! Parameters must be numbered consecutively. <to be read again> 0 l.2659 \def\secondofthreearguments #0#2#0 {#2} ! Parameters must be numbered consecutively. <to be read again> 0 l.2660 \def\thirdofthreearguments #0 #0#3{#3} ! Parameters must be numbered consecutively. <to be read again> 0 l.2660 \def\thirdofthreearguments #0#0 #3{#3} ! Parameters must be numbered consecutively. <to be read again> 0 l.2662 \def\firstoffourarguments #1#0 #0#0{#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2662 \def\firstoffourarguments #1#0#0 #0{#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2662 \def\firstoffourarguments #1#0#0#0 {#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2663 \def\secondoffourarguments #0 #2#0#0{#2} ! Parameters must be numbered consecutively. <to be read again> 0 l.2663 \def\secondoffourarguments #0#2#0 #0{#2} ! Parameters must be numbered consecutively. <to be read again> 0 l.2663 \def\secondoffourarguments #0#2#0#0 {#2} ! Parameters must be numbered consecutively. <to be read again> 0 l.2664 \def\thirdoffourarguments #0 #0#3#0{#3} ! Parameters must be numbered consecutively. <to be read again> 0 l.2664 \def\thirdoffourarguments #0#0 #3#0{#3} ! Parameters must be numbered consecutively. <to be read again> 0 l.2664 \def\thirdoffourarguments #0#0#3#0 {#3} ! Parameters must be numbered consecutively. <to be read again> 0 l.2665 \def\fourthoffourarguments #0 #0#0#4{#4} ! Parameters must be numbered consecutively. <to be read again> 0 l.2665 \def\fourthoffourarguments #0#0 #0#4{#4} ! Parameters must be numbered consecutively. <to be read again> 0 l.2665 \def\fourthoffourarguments #0#0#0 #4{#4} ! Parameters must be numbered consecutively. <to be read again> 0 l.2667 \def\firstoffivearguments #1#0 #0#0#0{#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2667 \def\firstoffivearguments #1#0#0 #0#0{#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2667 \def\firstoffivearguments #1#0#0#0 #0{#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2667 \def\firstoffivearguments #1#0#0#0#0 {#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2668 \def\secondoffivearguments #0 #2#0#0#0{#2} ! Parameters must be numbered consecutively. <to be read again> 0 l.2668 \def\secondoffivearguments #0#2#0 #0#0{#2} ! Parameters must be numbered consecutively. <to be read again> 0 l.2668 \def\secondoffivearguments #0#2#0#0 #0{#2} ! Parameters must be numbered consecutively. <to be read again> 0 l.2668 \def\secondoffivearguments #0#2#0#0#0 {#2} ! Parameters must be numbered consecutively. <to be read again> 0 l.2669 \def\thirdoffivearguments #0 #0#3#0#0{#3} ! Parameters must be numbered consecutively. <to be read again> 0 l.2669 \def\thirdoffivearguments #0#0 #3#0#0{#3} ! Parameters must be numbered consecutively. <to be read again> 0 l.2669 \def\thirdoffivearguments #0#0#3#0 #0{#3} ! Parameters must be numbered consecutively. <to be read again> 0 l.2669 \def\thirdoffivearguments #0#0#3#0#0 {#3} ! Parameters must be numbered consecutively. <to be read again> 0 l.2670 \def\fourthoffivearguments #0 #0#0#4#0{#4} ! Parameters must be numbered consecutively. <to be read again> 0 l.2670 \def\fourthoffivearguments #0#0 #0#4#0{#4} ! Parameters must be numbered consecutively. <to be read again> 0 l.2670 \def\fourthoffivearguments #0#0#0 #4#0{#4} ! Parameters must be numbered consecutively. <to be read again> 0 l.2670 \def\fourthoffivearguments #0#0#0#4#0 {#4} ! Parameters must be numbered consecutively. <to be read again> 0 l.2671 \def\fifthoffivearguments #0 #0#0#0#5{#5} ! Parameters must be numbered consecutively. <to be read again> 0 l.2671 \def\fifthoffivearguments #0#0 #0#0#5{#5} ! Parameters must be numbered consecutively. <to be read again> 0 l.2671 \def\fifthoffivearguments #0#0#0 #0#5{#5} ! Parameters must be numbered consecutively. <to be read again> 0 l.2671 \def\fifthoffivearguments #0#0#0#0 #5{#5} ! Parameters must be numbered consecutively. <to be read again> 0 l.2673 \def\firstofsixarguments #1#0 #0#0#0#0{#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2673 \def\firstofsixarguments #1#0#0 #0#0#0{#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2673 \def\firstofsixarguments #1#0#0#0 #0#0{#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2673 \def\firstofsixarguments #1#0#0#0#0 #0{#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2673 \def\firstofsixarguments #1#0#0#0#0#0 {#1} ! Parameters must be numbered consecutively. <to be read again> 0 l.2674 \def\secondofsixarguments#0 #2#0#0#0#0{#2} ! Parameters must be numbered consecutively. <to be read again> 0 l.2674 \def\secondofsixarguments#0#2#0 #0#0#0{#2} ! Parameters must be numbered consecutively. <to be read again> 0 l.2674 \def\secondofsixarguments#0#2#0#0 #0#0{#2} ! Parameters must be numbered consecutively. <to be read again> 0 l.2674 \def\secondofsixarguments#0#2#0#0#0 #0{#2} (That makes 100 errors; please try again.)resolvers | formats | resolvers | formats | binary path : C:/Users/MADELEN/Downloads/context-win64/tex/texmf-win64/bin resolvers | formats | format path : C:/Users/MADELEN/Downloads/context-win64/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex resolvers | formats | luatex engine : luametatex resolvers | formats | lua startup file : C:/Users/MADELEN/Downloads/context-win64/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua resolvers | formats | context file : C:/Users/MADELEN/Downloads/context-win64/tex/texmf-context/tex/context/base/mkiv/cont-en.mkxl resolvers | formats | run time : 2.197 seconds resolvers | formats | return value : error resolvers | formats | mtx-context | error, no format found with name: cont-en, aborting system | total runtime: 2.874 seconds of 3.016 seconds To sum up, it doesn't compile anything. How do I fix it?

5 6

two superscript versions with Garamond Libre
by Pablo Rodriguez 19 May '20

19 May '20

Dear list, I’m accesing superscript glyphs for Garamond Libre with the OT feature and the character with the following sample: \definefontfeature[sups][script=latn, sups=yes] \definefontfamily[twoface][rm][GaramondLibre] \definefontfamily[mainface][rm][EB Garamond 12] \setupbodyfont[mainface] \starttext \startTEXpage[offset=1ex] {\feature[+][sups]1}¹{\feature[+][sups]2}²{\feature[+][sups]3}³% {\feature[+][sups]8}⁸{\feature[+][sups]9}⁹{\feature[+][sups]0}⁰\\ \setupbodyfont[twoface] {\feature[+][sups]1}¹{\feature[+][sups]2}²{\feature[+][sups]3}³% {\feature[+][sups]8}⁸{\feature[+][sups]9}⁹{\feature[+][sups]0}⁰\\ \stopTEXpage \stoptext Typeface is available at https://github.com/dbenjaminmiller/garamond-libre/releases/latest. Sorry, but I’m a bit thick now. Does anyone know why characters and OT sups provide differently sized glyphs? I think there might be a bug in the typeface, but I need to know first what to report. Many thanks for your help, Pablo -- http://www.ousia.tk

4 6

\setbreakpoints[compound] and numbers
by Peter Münster 19 May '20

19 May '20

Hi, How could I get breaking lines with numbers please? Example: \setbreakpoints[compound] \setuplayout[width=1mm] \starttext xxx/xxx % line break is ok here xx1/xxx % I would like a linebreak here too \stoptext TIA for any help, -- Peter

1 0

Can someone explain the \startuseMPgraphic interface to me?
by Gerben Wierda 19 May '20

19 May '20

In details.pdf, I encounter \startuseMPgraphic{mpos:par:columnset:shade} numeric h ; for i=1 upto nofmultipars : h := bbheight(p) ; if multikind[i] = "single" : fill multipars[i] topenlarged -.5h When I encounter that, I wonder: - where do nofmultipars, p, multikind, and multpars come from? - what does mpos:par:columnset:shade signify? Just a name? Do the ’:’ have meaning? G.

1 0

Minimal code for exporting custom tags
by Aditya Mahajan 19 May '20

19 May '20

Hi, What is needed to enable export of user defined macros? Consider the following example: ``` \def\startmycommand{\dostarttagged{mycommand}\empty} \def\stopmycommand {\dostoptagged} \setupbackend[export=xml, level=0] \starttext \startsection[title={Sample document}] \startparagraph This is a paragraph \stopparagraph \startmycommand This is mycommand \stopmycommand \stopsection \stoptext ``` If I compile using `context --trackers=structures.tags filename`, I get ``` backend > tags > U+0031:1 => U+0031:1 : 00004 document>1 section>1 sectioncaption>1 sectionnumber>1 backend > tags > U+0053:S => U+0074:t : 00005 document>1 section>1 sectioncaption>1 sectiontitle>1 backend > tags > U+0054:T => U+0068:h : 00007 document>1 section>1 sectioncontent>1 paragraph>1 backend > tags > U+0054:T => U+0064:d : 00008 document>1 section>1 sectioncontent>1 mycommand>1 ``` so the tag is applied. I can also verify this by looking at the PDF which contains ``` << /K 27 0 R /ParentTree 2 0 R /RoleMap << /document /Div /mycommand /Span /paragraph /P /section /Sect /sectioncaption /Div /sectioncontent /Div /sectionnumber /H /sectiontitle /H >> /Type /StructTreeRoot >> ``` and the tag `mycommand` is used at appropriate location. However, the exported xml file contains no tag: ``` <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>   <document context="2020.04.30 11:10" date="2020-05-18T03:00:33-04:00" file="test-tag" language="en" version="0.35" xmlns:m="http://www.w3.org/1998/Math/MathML"> <metadata> </metadata> <section detail="section" chain="section" implicit="1" level="3"> <sectioncaption> <sectionnumber>1</sectionnumber> <sectiontitle>Sample document</sectiontitle> </sectioncaption> <sectioncontent> <paragraph>This is a paragraph</paragraph> </sectioncontent> </section> </document> ``` What am I missing in order to pass user-defined macros to the exporter? Thanks, Aditya

2 5

Problem updating to new version for Win64
by Todd DeVries 19 May '20

19 May '20

Hello, I tried updating my version of LMTX. A file which compiled under the old version (from earlier this year) now errors out. I moved my directory, downloaded a fresh copy of the install scripts and made a fresh installation. What am I missing? Errors below are from my terminal. l.2674 \def\secondofsixarguments#0#2#0#0 #0#0{#2} ! Parameters must be numbered consecutively. <to be read again> (That makes 100 errors; please try again.)resolvers | formats | resolvers | formats | binary path : C:/lmtx/tex/texmf-win64/bin resolvers | formats | format path : C:/lmtx/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1f32e/formats/luametatex resolvers | formats | luatex engine : luametatex resolvers | formats | lua startup file : C:/lmtx/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua resolvers | formats | context file : C:/lmtx/tex/texmf-context/tex/context/base/mkiv/cont-en.mkxl resolvers | formats | run time : 4.533 seconds resolvers | formats | return value : error resolvers | formats | mtx-context | error, no format found with name: cont-en, aborting system | total runtime: 5.171 seconds of 5.216 seconds -- Todd DeVries *Phone: (208) 847-5996* Secure chat: https://keybase.io/tdevries/chat “Not less than knowing, doubting pleases me.” —DANTE, The Inferno

1 0

Styling of included buffers or files
by Jan U. Hasecke 18 May '20

18 May '20

Hi all, I am currently writing a text where I want to include text snippets either by including files or including buffers. What is the best way to style all these included buffers? I know that I can do something like this: \startcolumns \getbuffer[Muenchen] \stopcolumns Or do something with \defineparagraph Is it somehow possible to apply styles to all buffers that gets included via \getbuffer by defining a special getbuffer-style? TIA juh

3 3

Looking for a way to use lua to output console/debug messages from MetaPost instead of 'show'
by Gerben Wierda 18 May '20

18 May '20

I often need some debugging info to find out what is going on in my METAPOST code (as I often do not have exact knowledge of what some things do). MetaPost’s ‘show’ command has limited formatting functionality (e.g. I would like to add a number as a string to a show message instead of putting it out as number and let ‘show' make a lot of lines out of it). I would like to instead use a lua function and I think I recall having seen somewhere the use of a call like lua( ….) or lua.foo.bar() in a MetaPost/MetaFun/LMTX example but I cannot find it anymore. Is it possible to do a lua() call from within MetaPost within LMTX and if so, what is the way to do it? This below is the state of my misguided attempts: \startluacode function warnWithLabelIfVerbose( str, ... ) texio.write_nl( str .. string.format(...)) end \stopluacode \startMPdefinitions{doublefun} %def somefunction ( expr str, number) = % lua.warnWithLabel( "LABEL: ", "%s %d", str, number); %enddef; \stopMPdefinitions \startMPpage[instance=doublefun] lua.texio.write_nl( "HELLO!"); % This works %lua.texio.write( "HELLO!\%n"); % This doesn't %string outs; outs := lua.string.format( "HELLO! \%s \%0.3f", "aap", 12.6); %somefunction( "aap", 12.6); \stopMPpage Thx, G

1 0

Custom color schemes in t-vim
by Nicola 18 May '20

18 May '20

Quick question: Is \startcolorscheme... \stopcolorscheme (still) supported by t-vim? In a template I wrote long time ago to typeset code, I have: \usemodule[vim] \unprotect \startcolorscheme[oceansunset] \definesyntaxgroup[Comment][\c!color={colortwo},\c!style=italic] % etc. \stopcolorscheme \protect which I use as described in the wiki: \definevimtyping [...] [... alternative=oceansunset, ...] But that does not seem to have any effect (if I change the colors, the syntax highlighting does not change). I can use pscolor and blackandwhite, though. I see that \startcolorscheme is not documented, so maybe there is another mechanism? Nicola

2 12