January 2022 - ntg-context - NTG Mailing Lists

Bug in alignment with LMTX version 2022.01.15 17:32
by Otared Kavian 18 Jan '22

18 Jan '22

Hi Hans and Mikael, While investigating the latest version regarding the math environment, I found that the alignments are not correct. Here is an example: % begin bug-alignment.tex \definemathmatrix[alignedcases] [align={right,left,left}, distance=3pt, left={\left\{}, right={\right.}, style=\displaystyle] \starttext \placeformula[eq:1] \startformula \startalignedcases \NC \partial_{t} u \NC = \Delta u + \epsilon^{-2}f(u) \NC\qquad\text{in }\, \Omega\times (0,+\infty) \NR \NC {\partial\phi(u) \over \partial{\bi n}} \NC = 0 \NC\qquad\text{on }\, \partial \Omega\times (0,+\infty)\NR \NC u(x,0) \NC = u_{0}(x)\NC\qquad\text{in }\, \Omega.\NR \stopalignedcases \stopformula \stoptext % end bug-alignment.tex Best regards: Otared

3 4

How to manually adjust the sort order of items appearing in a custom index?
by Joel 17 Jan '22

17 Jan '22

I created a custom index that displays a list of "Important Dates" appearing in my book. It lists the year, a short description of what happened, and should show the page number. I'm running into two errors though: First, if the date is the same year, it is sorting alphabetically, example,,,, \dateis{1900s+1912}{Yet another event happened} \dateis{1900s+1912}{Another event happened} ...will print the wrong one first in the index.. 1912 - Another even happened 1912 - Yet another event happened. Is there a way to manually tell it to display one first? I don't want to add visible month and day details, that would be even more confusing to the index as I have to print it in American order. Second, when it compiles it is not printing the page number, instead prints "[Entry not flushed]". -- Joel Here is my minimum working example: \defineregister[listdates][compress=yes] \setupregister[listdates][style=sansbold, textstyle=slanted, n=1, pagenumber=yes] \define[2]\dateis{% \listdates{#1~\emdash ~#2}% }% \starttext \dateis{1900s+1911}{Some event happened} \dateis{1900s+1912}{Yet another event happened} \dateis{1900s+1912}{Another event happened} \startchapter[title=Important Dates] \placelistdates \stopchapter \stoptext

2 1

Re: [NTG-context] \startcolumnset ... \stopcolumnset fatal error: return code 11
by Ben Moon 17 Jan '22

17 Jan '22

I too get an error trying to run John’s code and my own (I found this after that wouldn’t work) on macOS. My error code is 1 rather than 11. system > ConTeXt ver: 2022.01.15 17:32 LMTX fmt: 2022.1.17 int: English/english mtx-context | fatal error: return code: 1 Ben

1 0

How to achieve true double space text in ConTeXt?
by Joel 17 Jan '22

17 Jan '22

I need to display one article within my book that is in double space, like what is a basic requirement in US colleges for turning in papers. Basically, I need readers to have lots of space above the text to be able to write some notes above every line. This is a line of text. % <-- here is the space between lines % <-- this space here is as tall as a line of text. % <-- here is the next space between lines This is the next visible line of text. The closest I can get is the "big" setting in `\setupinterlinespace`, but it isn't big enough. I've also tried manual measurements in cm, but I have no idea which setting is typographically good. \setupinterlinespace[on, big] \startlinenumbering \input article \stoplinenumbering \setupinterlinespace[off] How can I achieve double space text in ConTeXt? --Joel

2 1

How to override ConTeXt-SBL titles, to make all titles everywhere capitalized?
by Joel 17 Jan '22

17 Jan '22

I am a few days from sending a document to a publisher, and using the Society of Biblical Literature style (via the macro ConTeXt-SBL) as it is very close to what I need, Chicago (numbers style) citations. One glaring difference I notice between the two styles is ConTeXt-SBL presents the titles of articles and books in lower case, but Chicago gives them in upper case (I think SBL should too, but maybe as my entire BibTeX file is lowercase, it is not). How can I tell ConTeXt to override the titles, everywhere they appear, so they are printed in uppercase? I've manually marked all of the words that should not be capitalized in my BiBTeX file as with \word{of} so they will ignore any instructions to become capitalized. --Joel

2 1

three suggestions for the statistical-charts module
by Pablo Rodriguez 17 Jan '22

17 Jan '22

Hi Tamara, Adriana and Tomáš, this is my first sample using statistical-charts (I attach the CSV file): \setupbodyfont[helvetica] \usemodule[statistical-charts] \starttext \setupframed[dotslabels][loffset=1.1cc, boffset=0.4cc] \linechart[basic][yscale=.25, xscale=1, distance=1, xgridlinesdensity=1, fillcolor=aquamarine, line=yes, linecolor=shamrock, dotscolor=shamrock, dotswidth=5, dotslabels=yes, axesunits=yes, xunit={Measurements}, yunit={Temperature}]% [method=dataset, dsname=main, filename=\jobname.csv, sep=;, cx={A2:A14}, cy=B2:B14] \stoptext I wonder whether this has been already proposed: 1. If the CSV file contains fields with quotes that the module reads, compilation breaks. Would it be possible that quotes could be ignored by the module? 2. Could you add an option to ignore the header (the first row), so that then "cx=A" cwould work without problems? 3. I haven’t found your module in https://modules.contextgarden.net. I think it would be great to have it there. Otherwise, users may not know of its existence. I have other questions, but this will be addressed in a next message. Many thanks for your excellent work, Pablo

1 0

How to troubleshoot why my document begins with a blank page?
by Joel 17 Jan '22

17 Jan '22

I created a book that strangely renders with an entirely blank page. There are tons and tons of macros, in dozens of files defined before the document starts, but the document itself starts quite simply with a title page set inside \startfrontmatter. How can I identify what types of preamble information would be causing an entire blank page to render before the document even begins? This minimum working example won't show me the error, but it does show I simply have \starttext followed by my title and nothing is between that should be rendering an entire blank page. --Joel My minimum working example is here: \definemakeup[titlepage][align=middle] \definealternativestyle[titlestyle][\ss\bfd][] \definealternativestyle[subtitlestyle][\ss\bfb][] \definealternativestyle[authorstyle][\ss\tfa][] \starttext % <-- there is no code between \starttext and \startfrontmatter below. \startfrontmatter \startmakeup[titlepage] \titlestyle{My story} \blank[big] \subtitlestyle{\date} \blank[big] \authorstyle{My name} \stopmakeup \stopfrontmatter \input knuth \stoptext

2 1

Simpleslides and LMTX
by Otared Kavian 17 Jan '22

17 Jan '22

Hi Aditya and Thomas, Following the hint given by Thomas about fixing the behaviour of the visual counter in the simpleslides module, I tried all the possible styles and found that once the PageNumber is changed into RealPageNumber in the s-simpleslides-*.tex style files. All the styles work fine unless three of them which I describe below. I don’t know how the modules are maintained on the wiki or elsewhere, but if you wish I can send you privately the files where I have changed PageNumber to RealPageNumber so that the simpleslides module can be used ot of the box with LMTX. Best regards: Otared PS: Here are the issues with the three styles which don’t work properly: • BigNumber: for the style to be typeset, one has to modify the part where BigNumberFont is defined %\beginOLDTEX %\loadmapfile[qhv-ec.map] %\definefontsynonym [BigNumberFont] [ec-qhvb] %\endOLDTEX % %\beginXETEX %\loadmapfile[qhv-ec.map] %\definefontsynonym [BigNumberFont] [ec-qhvb] %\endXETEX % %\beginLUATEX \definefontsynonym [BigNumberFont] [name:texgyreherosbold] %\endLUATEX Then the file « example.tex » can be typeset, but the big numbers shown are always 1. • Embossed: for the style to be typeset, one has to modify the part where EmbossedFont is defined %\beginOLDTEX %\loadmapfile[qhv-ec.map] %\definefontsynonym [Embossed] [ec-qhvb] %\endOLDTEX % %\beginXETEX %\loadmapfile[qhv-ec.map] %\definefontsynonym [Embossed] [ec-qhvb] %\endXETEX % %\beginLUATEX \definefontsynonym [Embossed] [name:texgyreherosbold] %\endLUATEX • SideToc: the file example.tex can be typeset with this style, but all pages come out in black… the text cannot be seen.

1 0

XML, dealing with whitespace
by denis.maier＠unibe.ch 17 Jan '22

17 Jan '22

Hi all, I have sources that look like this: %%%%%%%%%%%%%%%%%%%%% <?xml version="1.0" encoding="UTF-8"?> <article> <p>Bla Bla Bla</p> <p> <underline> <italic>Bla</italic> </underline>, Bla Bla.</p> </article> %%%%%%%%%%%%%%%%%%%%% Typesetting this with context gives me a spurious space after the underlined Bla in italics. Complete MWE : %%%%%%%%%%%%%%%%%%%%% \startxmlsetups xml:test \xmlsetsetup{#1}{*}{-} \xmlsetsetup{#1}{article|p|italic|underline}{xml:*} \stopxmlsetups \xmlregistersetup{xml:test} \startxmlsetups xml:article \starttext \xmlflush{#1} \stoptext \stopxmlsetups \startxmlsetups xml:p \xmlflush{#1}\par \stopxmlsetups \startxmlsetups xml:italic \emph{\xmlflush{#1}} \stopxmlsetups \startxmlsetups xml:underline \underbar{\xmlflush{#1}} \stopxmlsetups \startbuffer[test] <?xml version="1.0" encoding="UTF-8"?> <article> <p>Bla Bla Bla</p> <p> <underline> <italic>Bla</italic> </underline>, Bla Bla.</p> </article> \stopbuffer \xmlprocessbuffer{test}{test}{} %%%%%%%%%%%%%%%%%%%%% How can I get rid off spurious leading and trailing whitespace. I've found \xmlstrip and \xmlstripped, but I don't really understand how they work. I've also found out about \ignorespaces\xmlflush{#1}\removeunwantedspaces but this has then to be added to every definition, which would be a bit tedious... There have a been a couple of similar questions by Hans van der Meer about a decade ago, but I couldn't find the answer. Then, \xmlstripanywhere is also mentioned in xml-mkiv.pdf, but it's not explained. I found one example in the sources (https://source.contextgarden.net/tex/context/modules/mkiv/x-html.mkiv?searc…) but what does that do? Is that sort of need for \xmlstrip and friends to work? So, what would be the best way to deal with that situation? (More details below, perhaps there's an easier solution outside of context, because the problem is actually caused by xslt...) Best, Denis P.S. Background: I convert docx files with pandoc to jats xml. Pandoc does quite a decent job, but I need to tweak a few things with xslt. The actual transformation that I need works ok, but the transformation also causes other problems. This is the original markdown file : %%%%%%%%%%%%%%%%%%%%%%% Bla Bla Bla [*Bla*]{.underline} Bla Bla. %%%%%%%%%%%%%%%%%%%%%%% Pandoc produces a jats xml file that looks like this (simplified, empty nodes deleted) : %%%%%%%%%%%%%%%%%%%%%%% <?xml version="1.0" encoding="utf-8" ?> <article> <body> <p>Bla Bla Bla</p> <p><underline><italic>Bla</italic></underline>, Bla Bla.</p> </body> </article> %%%%%%%%%%%%%%%%%%%%%%% I use this xsl for tweaking pandoc's output %%%%%%%%%%%%%%%%%%%%%%% <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="1.0" xmlns:xsl=http://www.w3.org/1999/XSL/Transform xmlns:fo=http://www.w3.org/1999/XSL/Format> <xsl:output method="xml" indent="yes" />  <xsl:template match="*"> <xsl:copy> <xsl:copy-of select="@*"/> <xsl:apply-templates/> </xsl:copy> </xsl:template>      </xsl:stylesheet> %%%%%%%%%%%%%%%%%%%%%%% This is again much simplified, I've omitted the templates that do the actual tweaking. Anyway, both versions of the identity transformation produce this (using Saxon): %%%%%%%%%%%%%%%%%%%%%%% <?xml version="1.0" encoding="UTF-8"?> <article> <body> <p>Bla Bla Bla</p> <p> <underline> <italic>Bla</italic> </underline>, Bla Bla.</p> </body> </article> %%%%%%%%%%%%%%%%%%%%%%% I can get rid off all whitespace with indent="no", but that produces a rather unreadable file. xsl:strip-space has had no effect. Maybe someone knows a solution how to improve that step? Is there a way to convince an xslt-processor not to introduce the newlines after certain tags? Something like, treat paragraphs as a single unit or so. Am I missing something?

2 2

Re: [NTG-context] Changed behavior from \convertnumber{arabicdecimals}{..} as a textcommand for note
by musa furber 17 Jan '22

17 Jan '22

Dear Hans, Thank you for your reply. Here is the missing MWE. (I will also try to attach it.) % mwe % document is an English translation of Arabic text; all annotations are in English. % % concerning footnotes to Arabic text: % numbers in body should use Mashriki numbers (e.g. ٠١٢٣٤٥٦٧٨٩), and appear between parenthesis % numbers in footer should use Arabic numbers (e.g. 0123456789), and without parenthesis % % MWE uses dejavu for English and Amiri for and Arabic. Amiri is availble at https://www.amirifont.org/ \mainlanguage[en-gb] \setupdirections[bidi=global,method=one] \starttypescriptcollection [amiri] \starttypescript [serif] [amiri] \definefontsynonym [Serif] [file:Amiri-Regular.ttf] [features=arabic] \stoptypescript \starttypescript [amiri] \definetypeface [amiri] [rm] [serif] [amiri] [default] [fallbacks=latin-fallback] \stoptypescript \stoptypescriptcollection \define\setarabic{ \setupalign[r2l] \righttoleft \switchtobodyfont[amiri] } \define\setlatin{ \setupalign[l2r] \lefttoright \switchtobodyfont[dejavu] } \setupnotes[footnote][] \setupnotes[arfootnote][] \definenote[arfootnote][footnote] \setupnotation [arfootnote] [before=\setlatin, alternative=text, ] \setupnote [arfootnote] [headstyle={\switchtobodyfont[amiri]}, textcommand=\footnotenotenumbercommand, alternative=text, ] \protected\def\footnotenotenumbercommand#1{{\high{({\convertnumber{arabicdecimals}{#1}})}}} % unexpected results % \protected\def\footnotenotenumbercommand#1{{\high{({\convertnumber{abjadnumerals}{#1}})}}} % \protected\def\footnotenotenumbercommand#1{{\high{({\convertnumber{default}{#1}})}}} % % `\detokenize' variations, for comparison... % % \protected\def\footnotenotenumbercommand#1{{\high{(\detokenize{\convertnumber{arabicdecimals}{#1}})}}} % \protected\def\footnotenotenumbercommand#1{{\high{(\detokenize{\convertnumber{abjadnumerals}{#1}})}}} % \protected\def\footnotenotenumbercommand#1{{\high{(\detokenize{\convertnumber{default}{#1}})}}} \setupbodyfont[dejavu,11pt] \starttext \setarabic مرحبًا\arfootnote{Annotation text.} % expected footnote `(١)`, got `1arabic` مرحبًا\arfootnote{Annotation text.} % expected footnote `(٢)`, got `2arabic` \stoptext %%% end of mwe Thanks, Musa

1 0