May 2021 - ntg-context - NTG Mailing Lists

Unicode normalization and Hebrew in ConTeXt
by Joey McCollum 18 Aug '21

18 Aug '21

I am typesetting a document in Hebrew that includes pointing (e.g., vowels, shin and sin dots, dagesh, etc.) using ConTeXt. The Hebrew text that I want to typeset has been normalized into Unicode's NFC canonical form. It is well-known that the Unicode canonical ordering of Hebrew points conflicts with the recommended mark ordering of specific points based on their functions (see https://www.sbl-site.org/Fonts/SBLHebrewUserManual1.5x.pdf for more on this topic). Thankfully, many typesetting engines automatically reorder the points to ensure that they are combined according to the specifications of many fonts. I'm pretty sure that XeLaTeX is one of these, as it typesets Hebrew letters with multiple points correctly even when the Hebrew text is in NFC form. My question is, can ConTeXt with LuaTeX handle the same situation correctly? In the following minimal example, ConTeXt typesets pointed Hebrew correctly when the characters are in the typographically recommended order, but not when they are in Unicode canonical order: ``` %Setup Hebrew text font: \definefontfeature[f:pointedhebrew][default][ ccmp=yes, mark=yes, script=hebr ] \definefontfamily[hebrew] [rm] [SBL Hebrew] [features=f:pointedhebrew] %Set the body font: \setupbodyfont[hebrew] %Set up right-to-left alignment: \setupalign[r2l] \starttext %Characters after normalization, in Unicode canonical order (bet + segol + dagesh + final nun): בֶּן %A word with characters in typographically recommended order (bet + dagesh + segol + final nun): בֶּן \stoptext ``` I typeset this using ConTeXt version 2020.03.10, as released with TeXLive 2020. I got the SBL Hebrew font from https://www.sbl-site.org/educational/BiblicalFonts_SBLHebrew.aspx. According to the font's user manual (see the link above the MWE), the font should be able to combine the marks to form the correct glyph regardless of their order after the consonant, but that doesn't seem to be the case here. I also tried using the predefined "hebrew" featureset, but that did not change anything. Is there some other OpenType feature or featureset I need to enable to fix this, or is there some module or option I can include to get ConTeXt to typeset Unicode-normalized Hebrew as if it were ordered in the recommended way, like XeLaTeX does? I see that the uninormalize module is mentioned in the thread "XeLaTeX, LuaLaTeX, fontspec, unicode and normalization" on TeX Stack Exchange ( https://tex.stackexchange.com/questions/229044/xelatex-lualatex-fontspec-un…) can that be used with ConTeXt? Thank you, Joey

2 10

Footnotes in columns
by Clyde Johnston 13 Aug '21

13 Aug '21

I can no longer print the footnotes when I using columns in LTMX. If I remove the \{start|stop}columns, it works fine. This works on my old MKIV 2018.07.02 14:39 version. \setupcolumns[n=2,rule=off,balance=no] \starttext \startcolumns \input ward\footnote{A small footnote here} \stopcolumns \stoptext Context Version: 2021.01.24 16:07 Clyde

4 8

img.scan in lmtx?
by Henning Hraban Ramm 05 Aug '21

05 Aug '21

Hi, I use the lua function img.scan{filename}, but in lmtx I get "attempt to index a nil value (global 'img')", so I guess this got renamed or moved? HR

2 6

A not so short introduction to ConTeXt Mark IV
by Joaquín Ataz López 28 Jul '21

28 Jul '21

Hello to all: Two months ago I informed to the list that I had written an introduction in Spanish to ConTeXt Mark IV. This interested several people, and in order to increase their potential audience, a member of this list (native English speaker) has proceeded to translate my text into English. It is precisely the members of this list who need no introduction at all, but it can sometimes be useful to help someone get started with the fascinating typesetting system that is ConTeXt. As for the English translation, I have made some small changes to the Spanish version, so anyone who understands Spanish and prefers to read it in its original language can download the new version: Both versions are available at the following links - Spanish: https://webs.um.es/jal/docs/introCTX_esp.pdf - Engilish: https://webs.um.es/jal/docs/introCTX_eng.pdf Soon I will send both texts, with their source files, to the documentation section of the CTAN repository. -- Joaquín Ataz López Derecho Civil Universidad de Murcia

17 35

LMTX: different output if dots are used in the file name
by Marco Patzer 08 Jul '21

08 Jul '21

Hi! LMTX and MkIV behave differently if dots are used in the file name. Example: printf '%s\n' '\starttext\null\stoptext' > foo.10.tex && context foo.10.tex MkIV: → foo.10.pdf LMTX: → foo.pdf Is this intentional? This is LuaMetaTeX, Version 2.06.05 current version: 2020.05.25 23:39 Marco

5 17

PDF forms not creating proper children
by Leonard Janis Robert König 09 Jun '21

09 Jun '21

Hello, I currently try to build a document with AcroForms, e.g., the examples from [1] also linked in the Wiki. The most recent example is in the form/ subdirectory and dated mid 2020. However, when building the file(s) with my ConTeXt distribution the file created is broken, in comparison to the PDF checked in into the Git. The more obvious difference is that the PDF in the repository can be filled in the Firefox 89 beta, while the other PDF doesn't even display the fields as forms. Running pdfinfo also yields: > Syntax Error: Form field child is not a dictionary I suspect that due to some breakage the forms children aren't set in the AcroForms dictionary anymore? My ConTeXt versions are: # ArchLinux Repos context --version mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: /usr/share/texmf- dist/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2021.03.05 19:11 mtx-context | main context file: /usr/share/texmf- dist/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2021.03.05 19:11 # Debian Buster Repos mtx-context | ConTeXt Process Management 1.02 mtx-context | mtx-context | main context file: /usr/share/texmf/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2018.04.04 00:51 # Docker Image: Current mtx-context | ConTeXt Process Management 1.03 mtx-context | mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2020.01.30 14:13 mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkiv/context.mkxl mtx-context | current version: 2020.01.30 14:13 # Docker Image: Beta mtx-context | ConTeXt Process Management 1.03 mtx-context | mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2020.01.30 14:13 mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkiv/context.mkxl mtx-context | current version: 2020.01.30 14:13 # Docker Image: LMTX mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2021.04.14 22:58 mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2021.04.14 22:58 # Docker Image: Beta from 2019-09 mtx-context | ConTeXt Process Management 1.03 mtx-context | mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2019.09.10 20:03 mtx-context | main context file: /context/tex/texmf- context/tex/context/base/mkiv/context.mkxl mtx-context | current version: 2019.09.10 20:03 The ConTeXt version of the checked in file on GitHub is (according to pdfinfo): > Creator: LuaTeX 1.10 7138 + ConTeXt MkIV 2019.08.20 17:20 > Producer: macOS Version 10.14.6 (Build 18G5033) Quartz PDFContext I also remebered another time were I toyed around with it and indeed that PDF also had broken form field children: > Creator: LuaTeX 1.12 7306 + ConTeXt MkIV 2020.03.10 14:44 > Producer: LuaTeX-1.12 A broken version that I built locally using the :current IslandOfTeX [2] can be found at [3]. The version difference between the broken and not-broken PDFs hints that the breakage occured between 2019.08.20 and 2019.09.10-beta, while the Debian breackage might be due to a backport(?) Alternatively, this could just be a mistake on my side? Cheers Leo König [1]: https://github.com/fiee/ConTeXt [2]: https://gitlab.com/islandoftex/images/context/ [3]: https://mega.nz/file/ThcghTqb#JqRCSsd59bBbMgTMr3ahaPdU4LPlZd0cpA3ZFBJLJ3A

4 12

Hyphenation again
by Denis Maier 06 Jun '21

06 Jun '21

Hi, another weird thing: In this example I use \startexceptions to set hyphenation exceptions: ``` \mainlanguage[en] \startexceptions[en] appli-cable obli-gated \stopexceptions \setuplayout[width=1cm] \starttext \currentmainlanguage \currentlanguage \hyphenatedword{applicable} applicable \hyphenatedword{obligated} obligated \stoptext ``` What am I missing? Best, Denis

4 3

new upload
by Hans Hagen 01 Jun '21

01 Jun '21

Hi, I uploaded a new lmtx version. This time a new mechanism. ----------------------------- From an upcoming details chapter: ----------------------------- The mechanism described here is still experimental. Although it could be implemented in \MKIV\ it is only available in \LMTX. Already early in \MKII\ we had a positioning mechanism available. At that time we had \DVI\ output and specials were used to track positions. A script calculated the positions that were then fed back into the second run. Later Taco wrote \DVIPOS\ which sped up the analysis between runs. When \PDFTEX\ showed, an equivalent positioning mechanism was added there. In \MKIV\ positioning support was optimized a bit as part of the upgrading process but the principles remained the same. The interface to positioning comes with a lot of commands and many of them relate to what we want to do with \METAFUN. The alternative interface discussed here is a bit simpler and has (at least now) less commands and, combined with local name spaces, can be easier to use in more local situations. It's also integrated in the frequently used \type {\framed} commands and has basic support at the \METAFUN\ end. The performance is comparable to the regular positioning mechanisms but especially at the \METAPOST\ end has less overhead. ----------------------------- Here are some examples: ----------------------------- \framed [synchronize=yes,align=normal] {% test test test 1 \sync{one}{1}test test 2 \crlf test test 1 \sync{one}{1}test test test 2 \crlf test 1 \sync{one}{1}test 2 \crlf test test test test 1 \sync{one}{1}test test 2 } \framed [synchronize=yes,align=normal] {% one one \sync{a}{1}two \sync{a}{2}three \crlf one one \sync{a}{1}two two \sync{a}{2}three \crlf one \sync{a}{1}two \sync{a}{2}three \crlf one one one \sync{a}{1}two \sync{a}{2}three } \framed [synchronize=yes,align=normal] {% \syncanchor{one}{1}{1}A \syncanchor{one}{2}{1}BBB \syncanchor{one}{3}{1}C \crlf \syncanchor{one}{1}{2}AA \syncanchor{one}{3}{2}C \crlf \syncanchor{one}{1}{3}AAA \syncanchor{one}{2}{3}BB \syncanchor{one}{3}{3}C } \framed [synchronize=yes,align=normal] {% \alignanchor{one}{1}{1}{l}A \alignanchor{one}{1}{2}{m}AA \alignanchor{one}{1}{3}{r}AAA \syncanchor {one}{1}{4}\crlf \alignanchor{one}{2}{1}{right}B \alignanchor{one}{2}{2}{middle}BB \alignanchor{one}{2}{3}{left}BBB \syncanchor {one}{2}{4} } \startuseMPgraphic{whatever-1} fill OverlayBox withcolor "lightgray" ; drawdot anchorxy("one", 0, 1) withpen pencircle scaled 1mm withcolor "red" ; drawdot anchorxy("one", 0, 2) withpen pencircle scaled 1mm withcolor "red" ; drawdot anchorxy("two", 0, 1) withpen pencircle scaled 1mm withcolor "red" ; drawdot anchorxy("two", 0, 2) withpen pencircle scaled 1mm withcolor "red" ; drawdot anchorxy("three", 0, 1) withpen pencircle scaled 1mm withcolor "red" ; setbounds currentpicture to OverlayBox ; \stopuseMPgraphic \startuseMPgraphic{whatever-2} pair a ; a := anchorxy("one", 0, 1) ; pair b ; b := anchorxy("one", 0, 2) ; drawarrow anchorxy("one", 0, 1) { right } .. anchorxy("one", 0, 2) withcolor "blue" withtransparency (1,.75) ; drawarrow anchorxy("two", 0, 1) { down } .. anchorxy("two", 0, 2) withcolor "blue" withtransparency (1,.75) ; drawarrow anchorxy("two", 0, 1) { dir 30 } .. anchorxy("three", 0, 1) withcolor "blue" withtransparency (1,.75) ; setbounds currentpicture to OverlayBox ; \stopuseMPgraphic \defineoverlay[whatever-1][\useMPgraphic{whatever-1}] \defineoverlay[whatever-2][\useMPgraphic{whatever-2}] \framed [synchronize=yes, align=normal, offset=10pt, frame=off, background={whatever-1,foreground,whatever-2}] {% \markanchor{two}{0}{1}{\red\bf foo}% \markanchor{one}{0}{1} bar rab oof\crlf foo bar rab oof\crlf oof rab bar foo\crlf oof rab \markanchor{two}{0}{2}{\red\bf bar}% \markanchor{one}{0}{2} foo% \markanchor{three}{0}{1}% } \framed [synchronize=yes, align=normal, offset=10pt, frame=off, background={whatever-1,foreground,whatever-2}] {% one one one \syncanchor{a}{1}{1}two two two \syncanchor{a}{2}{1}three three\par one \syncanchor{a}{1}{2}two \syncanchor{a}{2}{2}three\par one \syncanchor{a}{1}{3}two \syncanchor{a}{2}{3}three\par \blank \markanchor{two}{0}{1}{\red\bf foo}% \markanchor{one}{0}{1} bar rab oof\crlf foo bar rab oof\crlf oof rab bar foo\crlf oof rab \markanchor{two}{0}{2}{\red\bf bar}% \markanchor{one}{0}{2} foo% \markanchor{three}{0}{1}% \blank one one \syncanchor{a}{1}{4}two two \syncanchor{a}{2}{4}three\par one one \syncanchor{a}{1}{5}two two \syncanchor{a}{2}{5}three three% \markanchor{three}{0}{1}% } \framed[synchronize=yes,align=normal]{% one one \sync{a}{1}two \sync{a}{2}three\par one one \sync{a}{1}two two \sync{a}{2}three\par \blank tst tst \sync{b}{1}tst \sync{b}{2}tst\par tst \sync{b}{1}tst tst \sync{b}{2}tst\par \blank one \sync{a}{1}two \sync{a}{2}three } \page \startpacked $a = b + c $\par $b = c + d $\par $c = e + f $\par \stoppacked \startpacked \startsynchronizing $a \syncanchor{one}{1}{1}= b \syncanchor{one}{2}{1}+ c$\par $b \syncanchor{one}{1}{2}= c \syncanchor{one}{2}{2}+ d$\par $c \syncanchor{one}{1}{3}= e \syncanchor{one}{2}{3}+ f$\par \stopsynchronizing \stoppacked \startpacked \startsynchronizing $a \sync{one}{1}= b \sync{one}{2}+ c$\par $b \sync{one}{1}= c \sync{one}{2}+ d$\par $c \sync{one}{1}= e \sync{one}{2}+ f$\par \stopsynchronizing \stoppacked \startpacked \startsynchronizing $a \mathsync{1}= b \mathsync{2}+ c$\par $b \mathsync{1}= c \mathsync{2}+ d$\par $ \mordsync{1}= e \mathsync{2}+ f$\par \stopsynchronizing \stoppacked ----------------------------- remark ----------------------------- So, it's a varaant on the positioning mechanism. It also works in framed when the synchronization option is enabled. Don't enable that when not used (as there is some overhead involved). I have no clue how useful it is but users always find a way to use mechanisms. One can do really freaky things with it. Who knows what gets added over time. Also, it doesn't replace the existing positioning mechanism which served us well for decades; it's just a lightweight variant with different pros and cons. 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 5

what happend to \writeline?
by Werner Hennrich 31 May '21

31 May '21

Hello everyone, I'm looking into my environment's logging to trace a problem and realize that \writeline is gone mute - that is, the output of subsequent logging lines now gets joined up in the same line, very hard to read... I observe this in version: 2021.05.27 14:15, as well as in version: 2021.05.27 14:15 the last one I used where \writeline did write (and end) the logging line was version: 2021.03.17 17:46. \def\log#1{ \message{ logging: #1} \writeline logging #1\par } \starttext \log{the} \log{quick} \log{brown} \log{fox} \stoptext used to log like this: logging: the logging: quick logging: brown logging: fox but now: logging: the logging: quick logging: brown logging: fox Any idea how I can switch back the old behavior (on the new lmtx)? Thanks you, Werner

2 2

new page before xtable with repeated headers
by Werner Hennrich 31 May '21

31 May '21

Hello everyone, I'm having an xtable spanning several pages and need to have its headers repeated. For this I've set "split=repeat", but unfortunately this causes the table to start with a new new page leaving the rest of the preceding page empty. Having "split=yes" makes the tabe continue on the previous page as a need it to, but then the header isn't repeated any longer. I realize that there has been a very similar question already in https://www.mail-archive.com/ntg-context@ntg.nl/msg93775.html, but my problem happens isolated in a very clean situation w/o any header, floats or the like - and I don't see yet how I can get this working in my situation. Any help is highly appreciated, here is a MWE of my problem: \definextable[mytable] \setupxtable[mytable] [ option=max, split=repeat, %split=yes, header=repeat, width=\textwidth ] \definextable[mytable:header] \setupxtable[mytable:header] [ foregroundstyle=\bf, foregroundcolor=darkred, ] % ================================================== \startdocument \dorecurse{2} { \input tufte \vskip7mm } \startxtable[mytable] \startxtablehead \startxrow[mytable:header] \startxcell Some Header \stopxcell \startxcell More Header \stopxcell \stopxrow \stopxtablehead \startxtablebody \dorecurse{10} { \startxrow \startxcell {\bf (\recurselevel) some tale:} \startitemize \item a quick \item brown fox \item jumps over \item the lazy dog \stopitemize \stopxcell \startxcell {\bf and a fact:} \startitemize \item the vodka \item is good \item but the meat \item is rotten \stopitemize \stopxcell \stopxrow } \stopxtablebody \stopxtable \stopdocument Thank you very much i.a., Werner

2 7