August 2015 - ntg-context - NTG Mailing Lists

Issues of export (structure bug)
by Henning Hraban Ramm 24 Aug '15

24 Aug '15

Hi, there’s another structure bug in export: from \startchapter[title=Something] ... \stopchapter \startchapter[title={Something Else}] ... \stopchapter I get in *—raw.xml: ... </sectioncontent> <sectiontitle>Something Else</sectiontitle> </section> <section detail="chapter" chain="chapter" level="2" implicit="4"> <sectioncontent> … That means, the title of a section is at the end of the previous section. Pleeeeease fix! Greetlings, Hraban --- http://www.fiee.net http://wiki.contextgarden.net https://www.cacert.org (I'm an assurer)

2 3

defining an alternate mono typeface
by Pablo Rodriguez 23 Aug '15

23 Aug '15

Dear list, I have the following sample: \definefontfamily [mainface] [rm] [TeX Gyre Pagella] \definefontfamily [mainface] [tt] [TeX Gyre Cursor] \definefontfamily [anothermono] [tt] [DejaVu Sans Mono] \setupbodyfont[mainface] \starttext \startTEXpage[offset=1em] \tfxx smaller text with {\doifdefinedelse{anothermono}{\anothermono}{\tt} second mono} \tfxx smaller text with {\doifdefinedelse{nomono}{\nomono}{\tt} second mono} \stopTEXpage \stoptext I would like to have an optional monospaced font, but when switching typefaces, font size isn’t retained. Is this a bug or am I missing something? Many thanks for your help, Pablo -- http://www.ousia.tk

1 0

Split numbers in natural tables
by Xan 23 Aug '15

23 Aug '15

Hi, I have a simple script in mako templates which generate this table: \starttext \bTABLE[align={lohi,middle}] \bTR \bTD[width=2.8cm, height=2.8cm] 1 \eTD \eTR \bTD[width=2.8cm, height=2.8cm] 2 \eTD \bTD[width=2.8cm, height=2.8cm] 4 \eTD \bTD[width=2.8cm, height=2.8cm] 8 \eTD \bTD[width=2.8cm, height=2.8cm] 16 \eTD \bTD[width=2.8cm, height=2.8cm] 32 \eTD \bTR \bTD[width=2.8cm, height=2.8cm] 64 \eTD \eTR \bTD[width=2.8cm, height=2.8cm] 128 \eTD \bTD[width=2.8cm, height=2.8cm] 256 \eTD \bTD[width=2.8cm, height=2.8cm] 512 \eTD \bTD[width=2.8cm, height=2.8cm] 1024 \eTD \bTD[width=2.8cm, height=2.8cm] 2048 \eTD \bTR \bTD[width=2.8cm, height=2.8cm] 4096 \eTD \eTR \bTD[width=2.8cm, height=2.8cm] 8192 \eTD \bTD[width=2.8cm, height=2.8cm] 16384 \eTD \bTD[width=2.8cm, height=2.8cm] 32768 \eTD \bTD[width=2.8cm, height=2.8cm] 65536 \eTD \bTD[width=2.8cm, height=2.8cm] 131072 \eTD \bTR \bTD[width=2.8cm, height=2.8cm] 262144 \eTD \eTR \bTD[width=2.8cm, height=2.8cm] 524288 \eTD \bTD[width=2.8cm, height=2.8cm] 1048576 \eTD \bTD[width=2.8cm, height=2.8cm] 2097152 \eTD \bTD[width=2.8cm, height=2.8cm] 4194304 \eTD \bTD[width=2.8cm, height=2.8cm] 8388608 \eTD \bTR \bTD[width=2.8cm, height=2.8cm] 16777216 \eTD \eTR \bTD[width=2.8cm, height=2.8cm] 33554432 \eTD \bTD[width=2.8cm, height=2.8cm] 67108864 \eTD \bTD[width=2.8cm, height=2.8cm] 134217728 \eTD \bTD[width=2.8cm, height=2.8cm] 268435456 \eTD \bTD[width=2.8cm, height=2.8cm] 536870912 \eTD \bTR \bTD[width=2.8cm, height=2.8cm] 1073741824 \eTD \eTR \bTD[width=2.8cm, height=2.8cm] 2147483648 \eTD \bTD[width=2.8cm, height=2.8cm] 4294967296 \eTD \bTD[width=2.8cm, height=2.8cm] 8589934592 \eTD \bTD[width=2.8cm, height=2.8cm] 17179869184 \eTD \bTD[width=2.8cm, height=2.8cm] 34359738368 \eTD \bTR \bTD[width=2.8cm, height=2.8cm] 68719476736 \eTD \eTR \bTD[width=2.8cm, height=2.8cm] 137438953472 \eTD \bTD[width=2.8cm, height=2.8cm] 274877906944 \eTD \bTD[width=2.8cm, height=2.8cm] 549755813888 \eTD \bTD[width=2.8cm, height=2.8cm] 1099511627776 \eTD \bTD[width=2.8cm, height=2.8cm] 2199023255552 \eTD \bTR \bTD[width=2.8cm, height=2.8cm] 4398046511104 \eTD \eTR \bTD[width=2.8cm, height=2.8cm] 8796093022208 \eTD \bTD[width=2.8cm, height=2.8cm] 17592186044416 \eTD \bTD[width=2.8cm, height=2.8cm] 35184372088832 \eTD \bTD[width=2.8cm, height=2.8cm] 70368744177664 \eTD \bTD[width=2.8cm, height=2.8cm] 140737488355328 \eTD \bTR \bTD[width=2.8cm, height=2.8cm] 281474976710656 \eTD \eTR \bTD[width=2.8cm, height=2.8cm] 562949953421312 \eTD \bTD[width=2.8cm, height=2.8cm] 1125899906842624 \eTD \bTD[width=2.8cm, height=2.8cm] 2251799813685248 \eTD \bTD[width=2.8cm, height=2.8cm] 4503599627370496 \eTD \bTD[width=2.8cm, height=2.8cm] 9007199254740992 \eTD \bTR \bTD[width=2.8cm, height=2.8cm] 18014398509481984 \eTD \eTR \bTD[width=2.8cm, height=2.8cm] 36028797018963968 \eTD \bTD[width=2.8cm, height=2.8cm] 72057594037927936 \eTD \bTD[width=2.8cm, height=2.8cm] 144115188075855872 \eTD \bTD[width=2.8cm, height=2.8cm] 288230376151711744 \eTD \bTD[width=2.8cm, height=2.8cm] 576460752303423488 \eTD \bTR \bTD[width=2.8cm, height=2.8cm] 1152921504606846976 \eTD \eTR \bTD[width=2.8cm, height=2.8cm] 2305843009213693952 \eTD \bTD[width=2.8cm, height=2.8cm] 4611686018427387904 \eTD \eTABLE \stoptext How can I do for, automatically, split the number in the cells? That is, I want the numbers to fit all the cell size, not matter what return carriages it needs. So some thing like \bTD[width=2.8cm, height=2.8cm] 4611686018427387904 \eTD would be transformed into: \bTD[width=2.8cm, height=2.8cm] 4611 686018427 387904 \eTD or something similar. Thanks, Xan

2 2

xmlconcat
by Meer, H. van der 23 Aug '15

23 Aug '15

There is a behaviour of xmlconcat that I do not understand. Calling as \xmlconcat{#1}{test}{xxx} correctly interjects the "xxx" between the successive members, in according with the documentation. But using the command version for calling: \xmlconcat{#1}{test/command(xmltest:test)}{yyy} does typeset the nodes but not the text from the third argument. It might be the correct behaviour but it confuses me. Any comments or enlightment? Thamks in advance. Hans van der Meer Minimal example: \setuppapersize[A6][A6] \startxmlsetups xmltest:setups \xmlsetsetup{\xmldocument}{root|test}{xmltest:*} \stopxmlsetups \xmlregistersetup{xmltest:setups} \startxmlsetups xmltest:root \writestatus{TEST}{calling xmltest:root} \xmlconcat{#1}{test}{xxx}\crlf \xmlconcat{#1}{test/command(xmltest:test)}{yyy}\crlf \stopxmlsetups \startxmlsetups xmltest:test \xmlflush{#1} \stopxmlsetups \startbuffer[xmlbuffer] <?xml version="1.0" encoding="UTF-8"?> <root> <test>node-1</test> <test>node-2</test> <test>node-3</test> <test>node-4</test> </root> \stopbuffer \starttext \xmlprocessbuffer{root}{xmlbuffer}{} \stoptext \endinput

2 1

\switchtobodyfont issue, also with newotf
by Rik Kabel 22 Aug '15

22 Aug '15

While working to get italic smallcaps in a secondary font face, I came across an issue with \switchbodyfont. When this is used in a certain way, the \tf font-style is changed, but not the \it, \bf, and so on. The example below compiles cleanly as presented, and the problem is not present. Each test line shows the expected font name and text. When the Oops! line is uncommented, the only test line for the test font that is correct is the \tf line. Other lines use the default font face in the specified font styles, but the font features are a mix (note that some are onum, some lining, and that long-s t ligatures are inconsistent). When the newotf module is enabled, the example fails to compile without errors, but produces similar results to non-newotf when the errors are ignored. This is not a problem with individual fonts—I have tried a variety of fonts both as default and secondary and get the same result. %\usemodule[newotf] \setupwhitespace[medium] \define\testAlphabet{\purefontname\font\quad ABCDEFGHIJKLmnopqrsſtuvwxyz \& 012345789} \starttypescript[Secondary] \definetypeface[Secondary][rm][serif][ebgaramond][default] % \definetypeface[Secondary][rm][serif][palatino][default] % \definetypeface[Secondary][rm][serif][libertine][default] \stoptypescript \setupbodyfont [modern, 10pt] %\setupbodyfont [palatino, 10pt] \starttext % {\switchtobodyfont[Secondary]Oops!\par}% Oops! Default tf: {\tf \testAlphabet}\par Default bf: {\bf \testAlphabet}\par Default it: {\it \testAlphabet}\par Default sl: {\sl \testAlphabet}\par Default bi: {\bi \testAlphabet}\par Default bs: {\bs \testAlphabet}\par Default sc: {\sc \testAlphabet}\par Default xx: {\it\setff{smallcaps}\testAlphabet}\par \switchtobodyfont[Secondary] Secondary tf: {\tf \testAlphabet}\par Secondary bf: {\bf \testAlphabet}\par Secondary it: {\it \testAlphabet}\par Secondary sl: {\sl \testAlphabet}\par Secondary bi: {\bi \testAlphabet}\par Secondary bs: {\bs \testAlphabet}\par Secondary sc: {\sc \testAlphabet}\par Secondary xx: {\it\setff{smallcaps}\testAlphabet}\par \stoptext Have I failed to properly specify the secondary typeface? Do I need a more complete typescript? Or is there a bug here? -- Rik

2 3

\installprettytype problem
by Matthieu Leroy 21 Aug '15

21 Aug '15

Hello, I want to use the " C-Pretty-Printing <http://modules.contextgarden.net/pret-c>" module. According to the "Verbatim" page of the Context garden, I have to use the \installprettytype command, but this one doesn't work (error : "undefined control sequence"). I'm using the 2015.08.13 19:33 Context version. Example : \installprettytype[C][C] \definetyping[C][option=C] \startC int func(int a){ if(a > 4) return 0; // comment else /* comment */ return 10; } \stopC Thank you.

5 7

Re: [NTG-context] m-graph read data and plot
by John Kitzmiller 21 Aug '15

21 Aug '15

On Aug 6, 2015, at 12:59 PM, Hans Hagen <pragma(a)wxs.nl <mailto:pragma@wxs.nl>> wrote: > > On 8/6/2015 5:30 PM, John Kitzmiller wrote: >> Given a file, data.d, containing 1 4 7 >> >> I expected the following code to draw a line from (4,1) to (7,1)… >> >> >> \enabletrackers[metapost.showlog] >> \usemodule[m-graph] >> \startMPpage[instance=graph,offset=3mm] >> draw begingraph(5cm,5cm); >> gdata("data.d", v, >> for n = 1 upto 3: >> a[n] = scantokens v[n]; >> endfor; >> >> show a1; show a2; show a3; % numeric >> show v1; show v2; show v3; % string >> gdraw (a2,a1)—(a3,a1); % same problem in or out of data group >> ); >> endgraph; >> \stopMPpage >> >> …the show lines return what I expected, but then come the complaints: >> >> ! Inconsistent equation (off by 0.90000000000000002)… >>>> (0,0,1,0,0,yypart S) >> ! Transform components aren't all known… >> > >> a[n] = scantokens v[n]; > > is a defined? Thank you Hans. Do you mean numeric a[n]? It was not explicitly declared; I did not think it needed to be—the show commands write what I expect to the log—anyway, declaring a did not help. > > also, use > > a[n] := scantokens v[n] ; Done. Still the same error messages and no pdf. > > > >> My goal is to draw multiple box plots >> https://en.wikipedia.org/wiki/Box_plot <https://en.wikipedia.org/wiki/Box_plot>, either vertical or horizontal, >> from data sets, but I am stuck at this early stage.

3 8

\startchemical
by Wolfgang Schuster 21 Aug '15

21 Aug '15

Hi, why does \startchemical take the name of a instance as argument (e.g. \startchemical[important]) when there is no way to create it because \definechemical is redefined and the original version isn’t saved. Even \setupchemical[important][..,..=..,..] can’t be used because it doesn’t resolve the parent setting. Wolfgang

3 3

Bad PDF to text crawlers
by Kip Warner 20 Aug '15

20 Aug '15

Hey list, I have an important document online that I would prefer to keep as a PDF and not in another format. Unfortunately bots frequently try to provide those looking for it with a text version they try to extract (beyond my control). The extraction looks just absolutely awful and has been a major pain in leaving readers with a really bad understanding of the contents of the document. I was thinking that there must be some way of tricking these bots, depending on how they are implemented, and let's assume they will always find the PDF, to get them to extract only a small invisible layer that just contains some hidden text directing a user to the location to download the original high quality ConTeXt PDF. Any suggestions? -- Kip Warner -- Senior Software Engineer OpenPGP encrypted/signed mail preferred http://www.thevertigo.com

4 4

\setupwhitespace and Natural Table paragraphs
by Pavneet Arora 18 Aug '15

18 Aug '15

I am trying to find the most effective way of changing paragraph spacing for paragraphs inside table cells, without resorting to explicit \blank directives. Here is a MWE to show what I mean. Outside of the table, the paragraph spacing seems to honour the \setupwhitespace directive. Not so inside the table. Curiously, though, the default enumeration inside the table *does* seem to honour \setupwhitespace, which you can affect using the before, after and inbetween options, as shown in the commented \startitemize line. advTHANKSance >>>> MWE % Change spacing \setupwhitespace[big] \setupinterlinespace[3.8ex] \starttext \input ward \input ward \midaligned{% \setupTABLE[frame=off]% \setupTABLE[offset=1em]% \setupTABLE[r][each][topframe=on,bottomframe=on]% \setupTABLE[c][1][align={flushleft,high},width=1.5in]% \setupTABLE[c][2][align={flushleft,lohi},width=4.0in]% \bTABLE \bTABLEbody \bTR \bTD {\bf 2014--2015} \eTD \bTD \input ward \input ward \blank \input ward \eTD \eTR \bTR \bTD {\bf 2013--2014} \eTD \bTD \input ward % \startitemize[before={\blank[small]},after={\blank[small]},inbetween={\blank[medium]}] \startitemize \item Item one. \item Item two. \item Item three. \stopitemize \eTD \eTR \eTABLEbody \eTABLE } \stoptext <<<< -- ---- Pavneet Arora m: 647.406.6843 Waroc Informatik t: 416.937.9276

2 1