- ntg-context - NTG Mailing Lists

Interaction references with Reference List and Bibliography
by Adam Reviczky 10 Jun '20

10 Jun '20

Hi, When I try to create a "Reference List" (for cited references in the document) followed by a "Bibliography" (for the rest of literature, not cited) I get wrong references linked back in the document when citing a reference multiple times, although the citation in the text is always fine. See MWE: --- \setupinteraction[state=start] \usebtxdataset[sample.bib] \usebtxdefinitions[apa] \starttext \input tufte \cite[hh2010a] \input zapf \cite[hh2010a] \title{Reference List} \placelistofpublications[criterium=all] \title{Bibliography} \placelistofpublications[method=dataset] \stoptext --- Publications taken from (https://wiki.contextgarden.net/Sample_bib) as sample.bib. The outcome is correctly cited (Hagen, 2010a) including the interaction to the reference list, but the second citation is also linked to the first item in the bibliography Eijkhout, V. (1991) rather than the reference list entry again. If I cite the item again, then the second item in the bibliography is referenced and so on. "aps" doesn't seem to create an interactive back reference, so the issue is only with "apa". Is this because I mix both references and bibliography with placelistofpublications? Any other way to achieve this keeping interaction links in place? Thanks, Adam

1 0

\startplacefigure and \startframedtext in lmtx
by Otared Kavian 10 Jun '20

10 Jun '20

Hi all, I just noticed that in lmtx, the commands \startplacefigure and \startframedtext, when used together, do not behave in the same way as they do in mkiv. I wonder whether this is a permanent change or rather a buglet. I found a fix around the issue, but since in my document I have a certain number of cases where such combinations are used, I woul dlike to be sure to not make a mistake by changing all the instances… Here is an example: %% begin figure-framedtext.tex \useMPlibrary[dum] \defineexternalfigure[dummy] \starttext \startplacefigure[location=left,number=no,title={}] \externalfigure[dummy][width=.45\textwidth] \stopplacefigure \dontleavehmode % if this is commented out then the text and the figure are placed on top of each other \startframedtext[frame=off] \input ward.tex \stopframedtext \stoptext %% end figure-framedtext.tex In the above example the fix is to add \dontleavehmode between the figue and the framedtext. If one comments out that line then the issue can be seen. Thanks in advance for any help: Otared K.

4 4

problem with counters (page)
by Alan Bowen 10 Jun '20

10 Jun '20

My efforts to set up a new page counter in the footertexts of a book are not proving successful. The following code shows the nature of the problem. \definecounter[volpage][type=page, way=bypage] \starttext \setcounter[volpage][5] \dorecurse{3}{\startTEXpage[offset=2pc] \input ward \blank[medium] \centerline{\red\tfa\rawcounter[volpage]\incrementcounter[volpage]} \stopTEXpage} \stoptext As you will see, the counter is not incremented on pages 2 and 3. I expect that I have missed something important. But what? Alan

3 5

new version
by Hans Hagen 10 Jun '20

10 Jun '20

Hi, I uploaded a new version. There have been no changes to the typesetting machinery although we're still in the process of finetuning some updated low level macros. There was a fix in the font machinery (thanks to Kai) but that will probably go unnoticed as the issue has been there for years. Now, that doesn't mean that nothing has been changed. First of all there is a new data related mechanism. After Wolfgang had updated the definition files it became official. It was on the agenda for a while but finally a nice solution surfaced. The new thing is luatables that obey grouping. Normally what you do at the lua end is kind of global, but there can be cases where you really want it to behave like tex: obeying \bgroup/\egroup, { } etc. The examples given below show that you can create them at the tex end and access them in tex as well as lua. \starttext \dorecurse {100} { \setdatavalue{#1}{#1} } \start \tttf \darkred \raggedright \dorecurse {100} { #1=\scratchcounter\getdatavalue{#1}\the\scratchcounter } \par \stop \blank \start \tttf \darkgreen \raggedright \dorecurse {100} { #1=\thedatavalue{#1}% } \par \stop \blank \bgroup \tttf \newluatable\testtable \setluatable\testtable{ foo = 123, bar = "456", oof = "rab" } % \inspectluatable\testtable \darkblue foo = \getfromluatable\testtable{foo}\par bar = \getfromluatable\testtable{bar}\par oof = \getfromluatable\testtable{oof}\blank \bgroup \useluatable\testtable \setluatable\testtable{ foo = 123123, bar = "456456" } % \inspectluatable\testtable \darkmagenta foo = \getfromluatable\testtable{foo}\par bar = \getfromluatable\testtable{bar}\par oof = \getfromluatable\testtable{oof}\blank \startluacode local t = context.luatables.get("testtable") print(t.foo,t.bar,t.oof) \stopluacode \egroup \darkyellow foo = \getfromluatable\testtable{foo}\par bar = \getfromluatable\testtable{bar}\par oof = \getfromluatable\testtable{oof}\blank \startluacode local t = context.luatables.get("testtable") print(t.foo,t.bar,t.oof) \stopluacode % \inspectluatable\testtable \egroup \bgroup \tttf \newluatable\moretable \setluatable\moretable{ 1, "foo" } \darkblue [1] = \getfromluatable\moretable{1}\par [2] = \idxfromluatable\moretable 2 \blank \bgroup \useluatable\moretable \setluatable\moretable{ foo = 123123, bar = "456456" } \darkmagenta [1] = \getfromluatable\moretable{1}\par [2] = \idxfromluatable\moretable 2 \blank \startluacode local t = context.luatables.get("moretable") print(t[1],t[2]) \stopluacode \egroup \darkyellow [1] = \getfromluatable\moretable{1}\par [2] = \idxfromluatable\moretable 2 \blank \startluacode local t = context.luatables.get("moretable") print(t[1],t[2]) \stopluacode \egroup \stoptext This is only available in lmtx (until i see a real reason to cook up an alternative for mkiv, which is unlikely as no context code depends on this being available, at least not now). The datavalue macro you see there can be used to create massive amounts of numeric variable independent of counters, not that we really need it, but it was very cheap to implement. At the engine level there also have been some changes but these should not be visible for users. We just mention: - extensions to the macro definition and expansion mechanisms (for instance optional arguments, optional delimiters, and silent error recovery; there will be some explanation in the evenmore document and at some point - when stable - in the manual) .. this permits some cleaner low level code; only things were done that had no impact on performance (as macro definition and expansion is used a lot) and didn't make the code messy (it actually became cleaner) - some additional substring (ok, tex has no string, just tokens) parsing capabilities with optional tokens, which again permits a bit cleaner low level code - a slightly reorganized handling of tokens (one of tex's basic data structures) in the lua token interface so that we get a more meaningful and robust subsystem (basically getting rid of funny numbers) ... this also will be discussed in an evenmore chapter .. not that users need it (i think) - as a side effect (or necessity) some low level recoding (and abstraction) had to happen but as far as we can see it works ok (i admit it was a slow, tedious job with lots of intermediate testing on the suite to make sure nothign was broken) .. in the end it was all doable because most of the preparation was already done over the last years - in the process we got rid of a traditional tex data structure that was left over from the 32 bit times but no longer needed in our 64 bit luatex/luametatex universe (i might backport that simplification to luatex some day) ... it discards some checking and saves the same amount of memory that we had on the early day pc's (where we ran whole tex jobs in that amount) Of course ... all kind of small improvenments ... hopefully for the best, 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 -----------------------------------------------------------------

2 1

About vertical typesetting in ConTeXt
by Jairo A. del Rio 10 Jun '20

10 Jun '20

Hi list! I'm curious about vertical typesetting in ConTeXt. As far as I know, LuaTeX supports four text directions, but LTL is broken for Manchu script (letters are displayed unjoined in LTL mode) and LuaMetaTeX does not support vertical directions anymore, at least as primitives. I found the following solution: https://tex.stackexchange.com/a/140972/193767 I reproduce the code (in XeLaTeX), just in case % !TEX TS-program = xelatex\documentclass{scrartcl}\usepackage{fontspec}\newfontfamily{\dcw}[]{DaicingWhite}%\begin{document}\noindent Line above\\% to demonstrate that the lines are being stacked as normal\rotatebox{-90}{%\XeTeXupwardsmode1\\% successive lines will be stacked upwards instead of downwards\begin{minipage}{4em}% this will be the vertical length of the Mongolian section{\dcw% Font: Daicing White 1 ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ\\% direct Unicode input of Manchu letters 2 ᠮᠠᠨᠵᡠ ᡤᡳᠰᡠᠨ}% End font\end{minipage}\XeTeXupwardsmode0}% End rotatebox \noindent Line underneath\end{document} and I see XeTeX uses the primitive \XeTeXupwardsmode and some other tricks to get the proper display of Manchu text, so maybe MKII can do the magic using XeTeX as an engine. How would one use ConTeXt MKIV for this task? Is it possible to emulate \XeTeXupwardsmode in ConTeXt as a first step? Thank you very much. Jairo :D

2 1

accessing xml element attributes in lua, how, if you do not want to use the .at scheme?
by Gerben Wierda 09 Jun '20

09 Jun '20

I’ve been trying to find out how I can access XML node properties/attributes in lua other than via the .at syntactic scheme but using the property/attribute name as a string. E.g., currently I do: someVar = someNode.at.someProperty but I would like to do something like someVar = someNode[“someProperty”] or someNode.attribute(“someProperty”) or something where I can use the string version of the properties/attribute name. It’s probably possible (after all these are all dynamic structures that come from data), but how exactly? Thanks, G

2 1

Bug in lmtx or wrong setup?
by Jan U. Hasecke 09 Jun '20

09 Jun '20

Hi all, I encountered a very strange problem. I want to have section headlines expanding the whole textarea, but the following copy text of the section shall be typeset in columns. I have this setup and it works fine. \setuphead [section] [ insidesection=\startcolumns, aftersection=\stopcolumns, ] Except for one big problem. ConTeXt (current lmtx from 2020.05.18 16:50) sometimes has problems to make a page break. And I get the weird result shown on the attached screenshot. After the page break the text of the section does not continue. Instead a number is shown. In the log file I can't find something suspicious. When I compile the source with current context (2020.01.30 14:13) I get something like an infinite loop. ConTeXt hangs and has to be killed with kill pid, Ctrl-C in terminal does not work So, in my opinion my layout or setup causes a bad situation, where ConTeXt does not know where to make a page break. While context hangs and warns me, lmtx runs smoothly but places a number in the text, which is bad as I might overlook it. I tried to make mwe but I cannot reproduce the error. Any ideas to improve my setup? Is this a bug or the intended behaviour? juh

1 0

chapter numbers
by jbf 08 Jun '20

08 Jun '20

I am attempting to get the word 'Chapter' to appear in the Chapter title, followed by its number, and I attempted to do it simply with: \setupheadtext[chapter=Chapter] \setuphead [chapter] [header=empty] What I get is simply the number, e.g. 1 My first chapter, 2 My second chapter etc. \setupheadtext is being ignored. What am I doing wrong? Julian

3 4

use parentheses in itemize
by Mike Cooper 08 Jun '20

08 Jun '20

Hello list. Here is the first what will no doubt be many *VERY* basic questions. So far, I am having quite a difficult time finding any help in the documentation (not just this issue but pretty much anything, really). Anyway, I want to have a list like this: (a) 415,668 lb (b) 440,668 lb (c) 517,000 lb (d) 542,000 lb How do I get these parentheses with my itemization symbol? THANKS! Mike Cooper Technical Trainer Murchison Drilling Schools, Inc. 2501 Juan Tabo NE Albuquerque, NM 87112 Tel: (505) 293-6271 Fax: (505) 298-5294 Email: mike(a)murchisondrillingschools.com<mailto:mike@murchisondrillingschools.com> Website: www.murchisondrillingschools.com<http://www.murchisondrillingschools.com/> [cid:image007.jpg@01D03ADC.BD6E6850]<https://www.facebook.com/pages/Murchison-Drilling-Schools/158018484232622> [cid:image008.jpg@01D03ADC.BD6E6850] <http://www.linkedin.com/company/murchison-drilling-schools-inc-> [cid:image009.jpg@01D03ADC.BD6E6850] <https://twitter.com/trainingmds> Murchison Drilling Schools is now part of [cid:image001.png@01D63515.857FD120]

4 6

problem since previous versions
by Hans van der Meer 07 Jun '20

07 Jun '20

A problem has arisen up since previous versions, where code without a problem now raises an error. This is the afflicted code: % Assign values to \locationbox. \doif{top}{\placexlocation}% {\def\startlocationbox{\vtop\bgroup\vss}}% \doif{center}{\placexlocation}% {\def\startlocationbox{\vcenter\bgroup}}% \doif{bottom}{\placexlocation}% {\def\startlocationbox{\vbox\bgroup}}% And it is used here: \setbox\placexbox=\startlocationbox \ignorespaces Previously this worked without a hitch, now the error is: tex error > tex error on line 9 in file ./familie-events.tex: ! A <box> was supposed to be here <to be read again> \vcenter \startlocationbox ->\vcenter \bgroup \dostartcontentplacexinline ...ables \par \setbox \placexbox =\startlocationbox \ignorespaces <to be read again> \syst_helpers_single_empty_one_nop \xmlflush \21>:xmlplc:placexcontent ...le=\xmlatt {#1}{alttitle}]}\startcontent \xmlflush {#1}\stopcontent l.9 } I can try to make a minimal example, but not without the afflicted module of some 800 lines. So perhaps the problem will be located by the experts at first sight. It is of course the \vcenter playing havoc, because replacing it by \vtop or \vbox makes the error disappear. Thanks for looking into it, because my work more or less depends on this code working in good order. dr. Hans van der Meer

2 2