November 2024 - ntg-context - NTG Mailing Lists

A few question about defining symbols and creating downarrow to illustrate function rules
by Jethro Djan 25 Nov '24

25 Nov '24

Hello, I have a few questions. 1. What is the best way to get a symbol from a font you are not using as your main? %% start MWE \starttext \definesymbol[cedis][\utfchar{“20B5}] \def\cedis{ \switchtobodyfont[dejavu]\tf\symbol[cedis] } I have GH\cedis 10.00 in my pocket \stoptext %% end MWE I tried to use \getglyph because I saw it being used in a similar way (but not with unicode characters) like this: \definesymbol[cedis][\getglyph{dejavu}{\utfchar{"20B5}}] It didn't work. 2. I would like a more robust method to create a diagram (ie., a series of input and outputs where you are then required to tell the rule of the mapping). The inputs will be up with the outputs below and a downward pointing arrow between them. %% start MWE \starttext \define[2]\xdownarrow{ \startframed[frame=off,offset=0pt,width=0.8cm] \startMPcode numeric u, w; u := .3cm; w := 2pt; pair pointX, pointY; path pointXY; pointX := origin; pointY := pointX shifted (0,-3u); draw pointX -- pointY withpen pencircle scaled .6w; drawarrow pointX -- pointY withpen pencircle scaled .6w; labeloffset := u; label.top (textext("\dm{#1}"), pointX); label.bot (textext("\dm{ #2 }"), pointY); \stopMPcode \stopframed } \startitemize[n] \item Find the rule of the mapping: \startplacefigure[location=none] \startframed[frame=off,offset=0pt,] \xdownarrow{x}{y} \hspace[big] \xdownarrow{1}{3} \hspace[big] \xdownarrow{2}{1} \hspace[big] \xdownarrow{3}{-1} \hspace[big] \xdownarrow{4}{-3} \hspace[big] \xdownarrow{5}{-5} \stopframed \stopplacefigure \startitemize[a] \item \im{y = 2x + 2} \item \im{y = -2x + 2} \item \im{y = 4x} \item \im{y = -2x + 5} \stopitemize \stopitemize %% stop MWR How can I achieve this more elegantly with better spacing and the arrow pointing to the number instead (-) for negative numbers? Regards, Jethro

3 4

Arranging sometimes adds a zero
by Max Chernoff 25 Nov '24

25 Nov '24

Hi Hans, The recent discussion of imposition reminded me of an arranging bug that I found a little while ago. MWE: \setuppapersize[A5,landscape][A4] \setuparranging[2TOPSIDE] %% Uncomment to "fix" the bug % \protected\expandafter\def\expandafter\fixedspace\expandafter{% % \fixedspace% % \setbox\scratchbox\emptybox% % } \starttext \dorecurse{4}{\samplefile{knuth}} \stoptext With this example, there is an extra page on page 2 that contains nothing but a "0" in the bottom left corner. Clearing \scratchbox before the imposition code runs seems to fix this, but I wasn't able to trace it any further. Thanks, -- Max

1 0

[ imposition schemas ]
by vm 25 Nov '24

25 Nov '24

Due to the sheer amount of possibilities combined with my current lack of full understanding how parameters work, what would be the (simple) way to layout an existing pdf containing A5 pages in to groups of booklets different from all or 4 A4 sheets each (32 pages of the pdf) e.g. the 2*2*4 does generate a booklets containing 4 sheets with 16 pages. Is there a way to change the number of sheets to bundles of 5 or 8 ? .F

2 5

Metafun : reuse a static picture
by Fabrice L 24 Nov '24

24 Nov '24

Dear list, I have some difficulty to reuse a static picture in a multipage MetaFun document. I wish to define a complex image, with graphic and texts, and manipulate this image at each page. As the minimal working example shows, if I define a particular picture in the variable « AnImage » and a random text in another picture called « AnotherImage », I can use these two pictures in the first page of the document, but only one of them appears in the second page of the document (with the same code). I know that if I replace startMPinclusions/stopMPinclusions by startMPinitializations/stopMPinitializations, this works, but the image is recalculated (a different number is drawn), and I do not want this since the image is complex and takes time to make. So the question : how to make the two pictures « AnImage » and « AnotherImage » appears in the both page ? Thanks for any help ! Fabrice, % MWE : % 8< --------------------------------------- \starttext \startMPinclusions picture AnImage , AnotherImage; AnImage := image ( draw fullcircle scaled 40; ); AnotherImage := image ( arandomnumber := uniformdeviate(1); draw textext(decimal(arandomnumber)) scaled 0.5; ); \stopMPinclusions \startMPpage draw AnImage ; draw AnotherImage ; \stopMPpage \startMPpage draw AnImage ; draw AnotherImage ; \stopMPpage \stoptext % 8< ---------------------------------------

1 0

[ errors imposition example ]
by vm 24 Nov '24

24 Nov '24

while trying the "Getting the last page of a Booklet" example on the wiki page https://wiki.contextgarden.net/Imposition context complains: open source > level 1, order 2, name './imposition_test2.tex' ! Control sequence expected instead of undefined. <argument> \v!nextquadruple <macro> \installpagebreakhandler #1#2->\defcsname \??pagebreakmethod #1 \endcsname {#2} <line 3.18> \fi} You injected something that confused the parser, maybe by using some Lua call. this is the example code: 8<--- \unprotect \startvariables all nextquadruple: nextquadruple \stopvariables \installpagebreakhandler \v!nextquadruple {\ifdoublesided \!!counta\realpageno \!!countb\realpageno \advance\!!counta 4 \divide\!!counta 4 \multiply\!!counta 4 \advance\!!countb 1 \advance\!!counta-\!!countb \executepagebreakhandler\v!yes \dorecurse\!!counta{\executepagebreakhandler\v!empty}% \fi} \protect \setuppapersize[A5][A4] \setuparranging[2UP,rotated,doublesided] \setuppagenumbering[alternative=doublesided] \starttext \subject{Front Cover} \dorecurse{10}{\input tufte \par} \page[nextquadruple] Back Cover \stoptext --->8 most likely there is a reason for the error...

1 0

\shiftdown
by Thomas Meyer 24 Nov '24

24 Nov '24

Hi guys, I would like to move the first capital letter of a term down so that the rest of the term ends up approximately in the centre of the capital letter. The capital letter should be larger than the rest and is not a problem in itself. However, I can't manage this with \shiftdown. It always shifts down at a fixed distance. And I can't work with \setupshift. The inputs of unit=pt, dy=5 etc. don't seem to do anything, at least nothing happens with \shiftdown. Any help would be appreciated Greetings Thomas

3 3

troubles with xtable (might be because I nest the same xtables)
by damien＠thiriet.web4me.fr 24 Nov '24

24 Nov '24

Hello, I have troubles with \definextable, something I obviously didn't understand This MWE compiles well. \definextable [Test] \setupxtable [Test] [frame=off] \starttext \startxtable %[Test] \startxrow \startxcell [Test] bla \stopxcell \startxcell [Test] bli \stopxcell \stopxrow \stopxtable \stoptext However, if I uncomment [Test] afetr \startxtable, I get this error: tex memory > bumping category 'parameter' succeeded, details: all=120000 | ini=-1 | max=100000 | mem=30000 | min=20000 | ptr=20002 | set=100000 | stp=10000 | top=20002 tex memory > bumping category 'parameter' succeeded, details: all=160000 | ini=-1 | max=100000 | mem=40000 | min=20000 | ptr=30002 | set=100000 | stp=10000 | top=30002 tex memory > bumping category 'input' succeeded, details: all=960000 | ini=-1 | max=100000 | mem=30000 | min=10000 | ptr=20001 | set=100000 | stp=10000 | top=20001 tex memory > bumping category 'parameter' succeeded, details: all=200000 | ini=-1 | max=100000 | mem=50000 | min=20000 | ptr=40002 | set=100000 | stp=10000 | top=40002 tex memory > bumping category 'parameter' succeeded, details: all=240000 | ini=-1 | max=100000 | mem=60000 | min=20000 | ptr=50002 | set=100000 | stp=10000 | top=50002 tex memory > bumping category 'input' succeeded, details: all=1280000 | ini=-1 | max=100000 | mem=40000 | min=10000 | ptr=30001 | set=100000 | stp=10000 | top=30001 tex memory > bumping category 'parameter' succeeded, details: all=280000 | ini=-1 | max=100000 | mem=70000 | min=20000 | ptr=60002 | set=100000 | stp=10000 | top=60002 tex memory > bumping category 'parameter' succeeded, details: all=320000 | ini=-1 | max=100000 | mem=80000 | min=20000 | ptr=70002 | set=100000 | stp=10000 | top=70002 tex memory > bumping category 'input' succeeded, details: all=1600000 | ini=-1 | max=100000 | mem=50000 | min=10000 | ptr=40001 | set=100000 | stp=10000 | top=40001 tex memory > bumping category 'parameter' succeeded, details: all=360000 | ini=-1 | max=100000 | mem=90000 | min=20000 | ptr=80002 | set=100000 | stp=10000 | top=80002 tex memory > bumping category 'parameter' succeeded, details: all=400000 | ini=-1 | max=100000 | mem=100000 | min=20000 | ptr=90002 | set=100000 | stp=10000 | top=90002 tex memory > bumping category 'input' succeeded, details: all=1920000 | ini=-1 | max=100000 | mem=60000 | min=10000 | ptr=50001 | set=100000 | stp=10000 | top=50001 tex memory > bumping category 'parameter' failed, details: all=400000 | ini=-1 | max=100000 | mem=100000 | min=20000 | ptr=100002 | set=100000 | stp=10000 | top=100002 tex error > tex error on line 3 in file virtual://buffer.x_table_1.1: TeX capacity exceeded, sorry [parameter=100000] {}>Test:[bad 43] <macro> \doxtableparentparameter #1#2-> \ifrelax #1\doxtablerootparameter {#2}\else \doxtableparameter {#1}{#2}\fi <macro> \doxtableparameter #1#2->\ifcsname #1:#2\endcsname \csnamestring \else \expandafter \doxtableparentparameter \csname #1:\s!parent \endcsname {#2} \fi <macro> \doxtableparentparameter #1#2->\ifrelax #1\doxtablerootparameter {#2}\else \doxtableparameter {#1}{#2} \fi <macro> \doxtableparameter #1#2->\ifcsname #1:#2\endcsname \csnamestring \else \expandafter \doxtableparentparameter \csname #1:\s!parent \endcsname {#2} \fi <macro> \doxtableparentparameter #1#2->\ifrelax #1\doxtablerootparameter {#2}\else \doxtableparameter {#1}{#2} \fi <macro> \doxtableparameter #1#2->\ifcsname #1:#2\endcsname \csnamestring \else \expandafter \doxtableparentparameter \csname #1:\s!parent \endcsname {#2} \fi ... <line 7.3> b la <empty file> If you really absolutely need more capacity, you can ask a wizard to enlarge me. Why can't I nest the same kind of xtable? Thanks, Damien

2 1

Remove umlauts etc. from input
by Wolfgang Schuster 24 Nov '24

24 Nov '24

Hi, is there an already existing option to reduce umlauts etc. to ascii counterparts, e.g. \starttext Füße \stoptext results in Fusse The fonts manual gives an example for a font feature with the desired output but it's possible I missed something or there is a better solution. \startluacode local shapedcodes = { } for k, v in next, characters.data do local s = v.shcode if s then if type(s) == "number" then shapedcodes[utf.char(k)] = { utf.char(s) } elseif #s == 2 then shapedcodes[utf.char(k)] = { utf.char(s[1]), utf.char(s[2]) } end end end fonts.handlers.otf.addfeature { name = "simplify", type = "multiple", data = shapedcodes, } \stopluacode \definefontfeature [simplify] [simplify=yes] \starttext Füße \feature[+][simplify]Füße \stoptext Wolfgang

1 0

rfc4180splitter not handling UTF-8 with BOM files
by Marco Patzer 23 Nov '24

23 Nov '24

Hi! I run into a problem reading in certain CSV files. I nailed it down to the following example: \starttext \startluacode local mycsvsplitter = utilities.parsers.rfc4180splitter{ separator = ",", quote = '"'} -- fails with -- token call, execute: [ctxlua]:11: attempt to index a nil value (local 'tablerows') -- local mycsv = io.loaddata("A.csv") -- works local mycsv = io.loaddata("B.csv") local tablerows = mycsvsplitter(mycsv) context(tablerows[1][1]) context(" ") context(tablerows[1][2]) \stopluacode \stoptext The compilation fails with token call, execute: [ctxlua]:11: attempt to index a nil value (local 'tablerows') The two files are attached. The only difference is that: A.csv: Unicode text, UTF-8 (with BOM) text B.csv: ASCII text Somehow the rfc4180splitter chokes on UTF-8 with BOM files. io.loaddata succeeds as far as I can tell. Is there a way to read in those files without pre-processing them? Marco version: 2024.09.17 13:15

2 1

save runtime information
by Thomas A. Schmitz 20 Nov '24

20 Nov '24

Hi, a couple of years ago, I asked whether it was possible to typeset the information about runtime that I get at the end of the context run. Hans provided an answer (https://www.mail-archive.com/ntg-context@ntg.nl/msg90554.html) > it's in the log file: > > local data = io.loaddata("oeps.log") or "" > > local pattern = "> runtime: ([%d%.]+) seconds, ([%d]+) processed pages, ([%d]+) shipped pages, ([%d%.]+) pages/second" > > > local r, n, s, p = string.match(data,pattern) > > print(r,n,s,p) The information I get this way is inaccurate. The runtime (in seconds) I see at the end of the run on the terminal: 5.635 vs. the value I get with the code: 0.660260200500488 I'm not sure whether something has changed with lmtx or if this was the case before (the log file is being written to during the run, so this may explain the difference?). So my question from then still stands: is it possible to extract the real runtime somehow? I would like to write it to a different file at the end of the run. What would be the best way to do this? All best Thomas

2 2