January 2020 - ntg-context - NTG Mailing Lists

luametatex segmentation fault
by Ramón Casares 12 Jan '20

12 Jan '20

Hi list, I am new to LMTX, so before going any further I wanted to compile my plain TeX documents with LMTX. I am aware that LMTX is experimental, so perhaps what I am doing is impossible for the moment or worse, it is not even in your plans. In any case, this is how I got a segmentation fault when I was trying to make the plain format for LMTX in my Debian 10 Buster OS on linux-64 PC. <pre> $ cd ~/context/ $ ./install.sh $ ~/context/tex/texmf-linux-64/bin/luametatex --ini lmtx.tex This is LuaMetaTeX, Version 2.03.7 (INITEX) Segmentation fault $ cd ~/context/tex/texmf-cache $ rm -R * $ cd ~/context/ $ ~/context/tex/texmf-linux-64/bin/mtxrun --generate $ ~/context/tex/texmf-linux-64/bin/context --make $ ~/context/tex/texmf-linux-64/bin/luametatex --ini lmtx.tex This is LuaMetaTeX, Version 2.03.7 (INITEX) Segmentation fault $ ~/context/tex/texmf-linux-64/bin/luametatex --ini plain.tex This is LuaMetaTeX, Version 2.03.7 (INITEX) Segmentation fault $ cat $(~/context/tex/texmf-linux-64/bin/mtxrun --locate lmtx.tex) \input plain \directlua {tex.enableprimitives('', tex.extraprimitives())} \pdfoutput=1 \everyjob \expandafter {% \the\everyjob \input luatex-basics.tex\relax \input luatex-fonts.tex\relax \input luatex-mplib.tex\relax } \edef\fmtversion{\fmtversion+lmtx} </pre> Best regards, Ramón Casares

2 7

Keep photographer in one line in a caption
by Henning Hraban Ramm 11 Jan '20

11 Jan '20

Yet another small problem: I my photo captions, the photographer should be right aligned and in one line, i.e. if it doesn’t fit into the last line of the caption, it should move to the next line. ATM I’m clueless... That’s not enough (also not a MWE): \define[1]\Foto{\hfill\hbox{\tfx Foto: #1}} Best, Hraban

3 2

Check for parity of pair tags on source file to be closed
by context＠vivaldi.net 11 Jan '20

11 Jan '20

Hello, in most cases, when a source file is to be closed, pair elements (tags) should balanced. This concerns e.g. { - }, \bgroup - \egroup, \startitemize - \stopitemize, \if - \fi etc. When we have a complicated project structure and when compiling the topmost (root) source, a log for a disbalanced tag may appear, but the unbalanced tag however may be difficult to find. Is there a way to enable "watching" pair tags (at least mentioned before) in the way that their disbalance would be reported (logged)? Maybe a "enable tracker" could provide that... Sample: ---- A.mkiv \starttext A \input B.mkiv \stoptext ---- B.mkiv \startitemize \item B ---- <- "\startitemize" is unbalanced (unfinished by \stopitemize) in the scope of B.mkiv, so a message/log ("unfinished \startitemize") should be printed when B.mkiv is to be closed. Best regards, Lukas

3 4

uppercase section titles: no line breaking?
by Henning Hraban Ramm 11 Jan '20

11 Jan '20

Hi again, I’m trying to get uppercase titles with \WORD, but they aren’t broken into lines; while \WORD works in normal text. What’s the matter? Best, Hraban %%%%% \define[2]\MyChapter{ \WORD{#2} } \setuphead[chapter][ command=\MyChapter ] \starttext \chapter{ \input tufte } \WORD{ \input knuth } \stoptext %%%%%

2 9

@inproceedings not formatted
by Exp 09 Jan '20

09 Jan '20

Hi all, It seems that the \placelistofpublications refuses to format the @inproceedings entries. Instead, it yields something like "inproceedings: [author: AnAuthor] [title: SomeTitle]". I tried the command \showbtxfields following [ http://pragma-ade.nl/general/manuals/mkiv-publications.pdf] Table 3.2, but instead of 25 entries where @inproceedings is supposed to appear, it gives only 4 (article, book, demo-a, demo-b). Any help would be appreciated! code list: (main.bib) @inproceedings{AnArticle, author="AnAuthor", title="SomeTitle" } (main.mkiv) \usebtxdataset[main.bib] \starttext \placelistofpublications[method=dataset] \stoptext (context --version) mtx-context | current version: 2019.03.21 21:39

1 1

interline space default changed?
by Sandra Snan 09 Jan '20

09 Jan '20

I was rerunning ConTeXt on some older documents and the interline space isn't the same. Sure, the new default looks great, but what was the old default? I need to match what I've already published. Thank you♥ Sandra

3 4

extreme table and right frames with vertically spanned cells
by Damien Thiriet 09 Jan '20

09 Jan '20

Hi list, It looks like switching off right frame is not taken into account when spanning cell vertically. Consider this example: \starttext \startxtable \startxrow \startxcell A \stopxcell \startxcell [ny=2,rightframe=off] B \stopxcell \stopxrow \startxrow \startxcell C \stopxcell \stopxrow \stopxtable \stoptext The output is |A|B |C| | And I would expect |A|B |C| Am I wrong somewhere? Regards and happy new year, Damien Thiriet

3 2

mtxrun font patterns
by Henning Hraban Ramm 08 Jan '20

08 Jan '20

I just recognized that mtxrun’s pattern matching is a bit off. E.g. if I look for mtxrun --script fonts --list --all --pattern=roboto I get roboto roboto robotoregular Roboto-Regular.ttf robotocondensednormal robotocondensed robotocondenseditalic RobotoCondensed-Italic.ttf robotocondensedregular robotocondensed robotocondensedlight RobotoCondensed-Light.ttf robotoitalic roboto robotoblackitalic Roboto-BlackItalic.ttf robotomononormal robotomono robotomonoitalic RobotoMono-Italic.ttf robotomonoregular robotomono robotomonolight RobotoMono-Light.ttf robotonormal roboto robotoitalic Roboto-Italic.ttf robotoregular roboto robotoblack Roboto-Black.ttf robotoslablight robotoslab robotoslabextralight RobotoSlab-ExtraLight.ttf robotoslabnormal robotoslab robotoslabregular RobotoSlab-Regular.ttf robotoslabregular robotoslab robotoslabblack RobotoSlab-Black.ttf But I’ve several more faces installed. ConTeXt finds them with mtxrun --script fonts --list --all --pattern=robot (ROBOT, not ROBOTO) as roboto roboto robotoregular Roboto-Regular.ttf robotoblack roboto robotoblack Roboto-Black.ttf robotoblackitalic roboto robotoblackitalic Roboto-BlackItalic.ttf robotobold roboto robotobold Roboto-Bold.ttf robotobolditalic roboto robotobolditalic Roboto-BoldItalic.ttf robotocondensed robotocondensed robotocondensedregular RobotoCondensed-Regular.ttf robotocondensedbold robotocondensed robotocondensedbold RobotoCondensed-Bold.ttf robotocondensedbolditalic robotocondensed robotocondensedbolditalic RobotoCondensed-BoldItalic.ttf robotocondenseditalic robotocondensed robotocondenseditalic RobotoCondensed-Italic.ttf robotocondensedlight robotocondensed robotocondensedlight RobotoCondensed-Light.ttf robotocondensedlightitalic robotocondensed robotocondensedlightitalic RobotoCondensed-LightItalic.ttf robotocondensednormal robotocondensed robotocondenseditalic RobotoCondensed-Italic.ttf robotocondensedregular robotocondensed robotocondensedregular RobotoCondensed-Regular.ttf robotoitalic roboto robotoitalic Roboto-Italic.ttf robotolight roboto robotolight Roboto-Light.ttf robotolightitalic roboto robotolightitalic Roboto-LightItalic.ttf robotomedium roboto robotomedium Roboto-Medium.ttf robotomediumitalic roboto robotomediumitalic Roboto-MediumItalic.ttf robotomono robotomono robotomonoregular RobotoMono-Regular.ttf robotomonobold robotomono robotomonobold RobotoMono-Bold.ttf robotomonobolditalic robotomono robotomonobolditalic RobotoMono-BoldItalic.ttf robotomonoitalic robotomono robotomonoitalic RobotoMono-Italic.ttf robotomonolight robotomono robotomonolight RobotoMono-Light.ttf robotomonolightitalic robotomono robotomonolightitalic RobotoMono-LightItalic.ttf robotomonomedium robotomono robotomonomedium RobotoMono-Medium.ttf robotomonomediumitalic robotomono robotomonomediumitalic RobotoMono-MediumItalic.ttf robotomononormal robotomono robotomonoitalic RobotoMono-Italic.ttf robotomonoregular robotomono robotomonoregular RobotoMono-Regular.ttf robotomonothin robotomono robotomonothin RobotoMono-Thin.ttf robotomonothinitalic robotomono robotomonothinitalic RobotoMono-ThinItalic.ttf robotonormal roboto robotoitalic Roboto-Italic.ttf robotoregular roboto robotoregular Roboto-Regular.ttf robotoslabblack robotoslab robotoslabblack RobotoSlab-Black.ttf robotoslabbold robotoslab robotoslabbold RobotoSlab-Bold.ttf robotoslabextrabold robotoslab robotoslabextrabold RobotoSlab-ExtraBold.ttf robotoslabextralight robotoslab robotoslabextralight RobotoSlab-ExtraLight.ttf robotoslablight robotoslab robotoslablight RobotoSlab-Light.ttf robotoslabmedium robotoslab robotoslabmedium RobotoSlab-Medium.ttf robotoslabnormal robotoslab robotoslabregular RobotoSlab-Regular.ttf robotoslabregular robotoslab robotoslabregular RobotoSlab-Regular.ttf robotoslabsemibold robotoslab robotoslabsemibold RobotoSlab-SemiBold.ttf robotoslabthin robotoslab robotoslabthin RobotoSlab-Thin.ttf robotothin roboto robotothin Roboto-Thin.ttf robotothinitalic roboto robotothinitalic Roboto-ThinItalic.ttf That’s strange, isn’t it? Might also explain why some fonts aren’t found? Best regards, Hraban --- https://www.fiee.net http://wiki.contextgarden.net https://www.dreiviertelhaus.de GPG Key ID 1C9B22FD

2 1

OSFONTDIR defined in texmf.cnf not used
by Exp 08 Jan '20

08 Jan '20

Hi all, I've put `OSFONTDIR=/usr/share/fonts` in ~/.../texlive/2019/texmf.cnf, but `mtxrun --script fonts --reload` refuses to look it up, even though `kpsewhich --expand-path '$OSFONTDIR'` gives /usr/share/fonts. `export OSFONTDIR=/usr/share/fonts` does work, but doesn't feel very tex-y. Any help is appreciated.

3 4

Line numbering in two column layout conflicts with marking
by Oliver von Criegern 07 Jan '20

07 Jan '20

Dear list members, line numbering in a two column layout apparently conflicts with the marking mechanism. Consider the following example: \setupcolumns[n=2] \setuplinenumbering [ step=5, method=page, align=flushright, ] \definemarking[Test] \setupheadertexts[{\fetchmark[Test][top] -- \fetchmark[Test][bottom]}] \startbuffer \dorecurse{12}{words } \stopbuffer \starttext \startcolumns \startlinenumbering \marking[Test]{ONE}ONE \dorecurse{12}{\getbuffer}\par \marking[Test]{TWO}TWO \dorecurse{29}{\getbuffer}\par \marking[Test]{THREE}THREE \dorecurse{12}{\getbuffer}\par \stoplinenumbering \stopcolumns \stoptext In the result, the header of the first page reads "ONE -- THREE", despite marking "THREE" being placed in the third line of the second page. Without linenumbering, the header of the first page reads "ONE -- TWO", as is to be expected. Best regards, Oliver -- Dr. Oliver von Criegern Referat für IT und Digital Humanities Bayerische Akademie der Wissenschaften Alfons-Goppel-Str. 11 80539 München Tel.: 089-23031-1310

3 5