- ntg-context - Mailing Lists

lmtx update
by Hans Hagen 06 Feb '23

06 Feb '23

Hi, We were considering to drop the virtual math fonts mechanism (which has served its purpose in the transition in the very early days of luatex but became obsolete as math fonts evolved) but in the end we were forced keep this feature and even upgrade it because we liked iwona, kurier and anwykwa math too much. A typical case where one needs a week for reviewing, supporting, discussing, testing a few fonts, so let's hope it wi;l be used. Iwona and Kurier are nice sansish fonts and antykwa has a rather distinctive look and feel. The current variant works okay for most of math (in most weights of the fonts) but then, these fonts are not used for complex math or math using obscure symbols anyway. It can also serve as a test case for somewhat ancient fonts but it is configured in the modern way we like more (as we might completely drop old code paths some day anyway). And so, this update is dedicated to Janusz Nowacki, a Polish font friend, who passed away some time ago. % \setupbodyfont[iwona] % \setupbodyfont[kurier] % \setupbodyfont[antykwa] Hans & Mikael ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Fwd: BachoTeX 2023: invitation and call for papers
by Henning Hraban Ramm 05 Feb '23

05 Feb '23

-------- Weitergeleitete Nachricht -------- Betreff: BachoTeX 2023: invitation and call for papers Datum: Wed, 1 Feb 2023 20:33:11 +0100 Von: Jerzy.Ludwichowski <Jerzy.Ludwichowski(a)gust.org.pl> Dear Friends, please pass on the BachoTeX 2023 announcement to your members. With best wishes, -- Jerzy Ludwichowski =========================================== Dear TeX users and friends, good news - come what may, there will be BachoTeX 2023 as indeed I promised when announcing BachoTeX 2022 cancellation. The SARS-CoV-2 virus did not disappear but seems to have become less of a danger as far as one can tell. The war in Ukraine is raging still, but none the less we decided to organize BachoTeX 2023 at the usual dates and venue. We hope that for the fall and to make up for the lost time by keeping the same theme as the cancelled 2020 conference. Please find below the call for papers for BachoTeX 2023, with the same theme as planned for BachoTeX 2020 and 2022. The dates are from 29th of April until 3rd of May, 2023. Registrations will be announced separately as soon as possible. -- Jerzy Ludwichowski (for the Organizing Committee) The 28th GUST TeX conference A model kit. Modeling and implementing text typesetting in TeX and other systems. TeX as a program created by a scientist - Professor of The Art of Computer Programming, D. E. Knuth - stands out among other typesetting programs. Here we have not only an implementation but also a theoretical model to explain its behavior. For example the line breaking algorithm is based on the "algebra of glue and boxes". Algorithms designed for TeX became the basis for several scientific publications. TeX became a suitable environment for research in typography. We ask participants to reflect on the dependencies between theoretical models and implementation. Do they help or are they an obstacle? * Papers/presentations Of course we also look forward to the normal mix of TeX, Metafont/Metapost (please, do not forget the fonts!), ConTeXt, LaTeX, and friends related presentations. We also do upkeep the BachoTeX trend in which we try to bring together programmers and designers of typographic systems, typographers and other users of such systems. The normal channel of offering papers is the emailing of proposals to the Program Committee, but before rushing off to the mailer, please consult the info for authors. * Workshops and tutorials We look forward to proposals for TeX-related tutorials or introductions. If you have suggestions for tutorials or workshops by others than yourself or about specific topics, please let us know. * Poster sessions As always at BachoTeX participants will be given the opportunity to present their TeX and typographic results in the form of posters for which we provide exhibition space. * Deadlines and addresses The deadline for "regular" abstracts and other proposals is March 26th, 2023. The deadline for final papers to appear in the conference materials is April 16th. Contributions should be sent by email to the Program Committee: prog-2023 at gust.org.pl. The Program Committee is chaired by Bogusław Jackowski (b_jackowski at gust dot org dot pl). For other conference details see http://gust.org.pl/bachotex/2023-en.

1 0

A corner case relating to corners!
by Bruce Horrocks 05 Feb '23

05 Feb '23

In the Wiki <https://wiki.contextgarden.net/Command/setupframed> the examples for corner styles 00 - 09 no longer work and the single digit values 0 - 9 need to be used instead. (Styles 10 upwards continue to work as per the page.) Is this a deliberate change and the Wiki needs to be updated or should the change be reverted for backwards compatibility? MWE: \starttext \framed[corner=7]{Some text} \stoptext With value 07 the frame doesn't display, with value 7 the frame appears as expected. (Readers with a long-haired white cat can try corner=007) ;-) Version: ConTeXt ver: 2023.01.26 18:34 LMTX — Bruce Horrocks Hampshire, UK

2 1

Font substitution for extensible symbols
by Yaroslav Beltukov 02 Feb '23

02 Feb '23

Good day everyone, I'm trying to replace the math radical symbol (with all its variants) in one font with another one. Some fonts have too few radical symbols of different sizes, which results in enormous spacing in radicals. However, there is a bug in the new font replacement mechanism. Here is MWE: % 0x221A is the radical symbol \definefallbackfamily [MainFace] [mm] [TeX Gyre Pagella Math] [force=yes, range=0x221A] \definefontfamily [MainFace] [tf] [Cambria] % or [XITS] \definefontfamily [MainFace] [mm] [Cambria Math] % or [XITS Math] \setupbodyfont [MainFace] \starttext \startformula \sqrt{\frac{1}{2}}\dorecurse{15}{+\sqrt{\blackrule[width=10pt,height=#1pt,depth=#1pt,color=gray]}} \stopformula \startformula \sqrt{\blackrule[width=10pt,height=100pt,depth=100pt,color=gray]} \stopformula \stoptext It works in MKIV but it gives the following error in the latest LMTX: ...mkxl/math-vfu.lmt:675: attempt to get length of a nil value (global 'hp') It is caused by the following loop in math-vfu.lmt: local pv = olddata.parts if pv then pv = fastcopy(pv) newdata.parts = pv for i=1,#hp do local pvi = pv[i] ... One can see that #hp should be #pv. After this correction, the error disappears and we get different sizes of radicals from the new font. However, now the extended version of the radical does not work. Actually, this loop is devoted to copying the parts of the extended symbol, and it does not work as expected. Obviously, there is something deeper than the correction of the typo. The same behaviour is for other extensible symbols (e.g. parentheses). I hope this issue can be resolved. A more deeper understanding is required here. Best regards, Yaroslav P.S. sometimes I get the following output. Maybe it is related: otf reader > cff > unknown local call ?, case 1 : [] n=0

1 0

list not following "focus=standard"?
by Pablo Rodriguez 31 Jan '23

31 Jan '23

Dear list, I have the following sample: \setupinteraction[state=start, focus=standard] \starttext \completecontent \dorecurse{25} {\section{Section} a\footnote{b}} \stoptext Using current latest (from 2023.01.26 18:34), destinations for TOC are pages (/D [ 7 0 R /Fit ]) and destinations for footnotes are named destinations (/D [ 1 0 R /XYZ 61.900625 141.0443 null ]). Compare https://pdf.ousia.tk/lst-fnt.pdf#_3 with any link from the TOC. I‘m afraid this might be a regression from a recently fixed issue. Could anyone confirm this issue? Many thanks for your help, Pablo

1 1

Wrong prefix in cross references to formulas in external document
by Yaroslav Beltukov 31 Jan '23

31 Jan '23

Dear Hans and all contributors, I really appreciate ConTeXt for the right way to obtain high quality documents. I'm a theoretical physicist and I'm going to write a book. I think ConTeXt is the right choice to work with a number of formulas, figures and cross-references. The visual quality of formulas is better than in regular LaTeX. The new feature with formula autosplitting looks also very promising. For me it is important to obtain the high quality without a lot of manual tweaks of each formula for each given document format and figure placement. However, I have found a problem with references if I compile one component only. The references to formulas in other components have wrong prefixes, e.g. (2.1) instead of (3.1). Needless to say, the right formula references are very important. I started looking into this issue. The references to other components are taken from the whole product as from an external document. It turned out that this is a general problem with references with prefixes to external documents. The prefix is stored in a tuc file as a reference to a section as a sequential number of the header in the document. As a result, the prefix from the external document is calculated using the structure of the current document. Here is the MWE, which consists of two files: foo.tex: \defineenumeration[remark][prefix=yes, prefixsegments=chapter:section] \starttext Equations: \in[eq1], \in[eq2], \in[eq3], \in[eq4] Sections: \in[sec1], \in[sec2], \in[sec3], \in[sec4] Chapters: \in[chap1], \in[chap2], \in[chap3], \in[chap4] Remarks: \in[remark1], \in[remark2] \startbodymatter \chapter[chap1]{Chapter} \placeformula[eq1]\startformula x = y\stopformula \chapter[chap2]{Chapter} \section[sec1]{Section} \section[sec2]{Section} \placeformula[eq1]\startformula x = y\stopformula \placeformula[eq2]\startformula x = y\stopformula \stopbodymatter \startappendices \chapter[chap3]{Chapter} \section[sec3]{Section} \placeformula[eq3]\startformula x = y\stopformula \section[sec4]{Section} \startremark[remark1]\stopremark \placeformula[eq4]\startformula x = y\stopformula \startremark[remark2]\stopremark \chapter[chap4]{Chapter} \stopappendices \stoptext bar.tex: \starttext Equations: \in[foo::eq1], \in[foo::eq2], \in[foo::eq3], \in[foo::eq4] Sections: \in[foo::sec1], \in[foo::sec2], \in[foo::sec3], \in[foo::sec4] Chapters: \in[foo::chap1], \in[foo::chap2], \in[foo::chap3], \in[foo::chap4] Remarks: \in[foo::remark1], \in[foo::remark2] % any chapters and sections here \stoptext It is expected to have the same first page on these documents: Equations: 1.1, 2.2, A.1, A.2 Sections: 2.1, 2.2, A.1, A.2 Chapters: 1, 2, A, B Remarks: A.2.1, A.2.2 However, the bar.tex produces wrong prefixes to formulas and remarks. The output depends on the document structure of bar.tex, not foo.tex. I started looking into the source code. Thanks to lua, it is not a big deal to track the problem. The prefixdata is complemented by the sectiondata after the loading the tuc file. So, the question is: is it possible to store the full prefixdata with all necessary prefix numbers in the tuc file? Here is my proposal to change the source code: --- strc-lst-old.lmt 2023-01-29 11:30:15.610309948 +0300 +++ strc-lst.lmt 2023-01-29 12:10:08.864228923 +0300 @@ -266,6 +266,16 @@ if r and not r.section then r.section = structures.sections.currentid() end + -- store sectiondata in prefixdata (necessary for external files) + if t.prefixdata and r.section then + local sectiondata = structures.sections.collected[r.section] + if sectiondata then + for k, v in next, sectiondata do + t.prefixdata[k] = v + end + end + end + -- local b = r and t.block if r and not b then local s = r.section --- strc-ref-old.lmt 2023-01-29 11:30:15.823643904 +0300 +++ strc-ref.lmt 2023-01-29 12:07:45.697109862 +0300 @@ -2318,7 +2318,17 @@ if data then numberdata = lists.reordered(data) -- data.numberdata if numberdata then - helpers.prefix(data,prefixspec) + -- helpers.prefix(data,prefixspec) + -- use the actual numbers from prefixdata + local prefixdata = data.prefixdata + if prefixdata then + -- adapted from helpers.prefix (not sure) + if (prefixspec and prefixspec == no) or prefixdata.prefix == no then + prefixdata = false + end + sections.typesetnumber(prefixdata,"prefix", prefixspec or false, prefixdata) + end + -- sections.typesetnumber(numberdata,"number",numberspec,numberdata) else local useddata = data.useddata After this small change, all the references are correct. However, I'm quite new to ConTeXt, so maybe here are some caveats. It would be great to fix the references to formulas, especially for the forthcoming document about maths. Best regards, Yaroslav Beltukov

3 3

Best way to access casul fonts
by Mattias Märka 30 Jan '23

30 Jan '23

Hi, I'm trying to access Lucida Casual. I see in type-imp-lucida-typeone.mkiv that there is, indeed, a typescript for it, but I can't figure out how to switch to it. That is, I want to make some text be Lucida Casual. I gather from a previous thread that I should be using \definefontstyle, but I don't know how to go about this. Currently I'm just defining a new typescript and making Lucida Casual a synonym for Serif and then using \switchtobodyfont --- but this feel silly. I searched the wiki and skimmed the reference manual, but to no avail. Perhaps I don't know what I should be looking for. Any help would be appreciated. What's the easiest way to access a casual font? What's the cleanest way? Thanks, Mattias Märka

5 10

layout for marked pages?
by Pablo Rodriguez 30 Jan '23

30 Jan '23

Dear list, I have the following sample: \showframe \setuplayout[width=middle] \definelayout[odd][reset] \definelayout[even][reset] \doiftext{\markedpages[zapf]} {\doloopoverlist{\markedpages[zapf]} {\definelayout[\recursestring][page]}} \starttext \dorecurse{50}{\input{knuth}\par} \page\startmarkpages[zapf] \dorecurse{50}{\input{zapf}\par} \stopmarkpages\page \dorecurse{50}{\input{knuth}\par} \stoptext I wanted to have page layout in pages marked with zapf. I thought \markedpages[zapf] was the way to go, but I only get text after marked pages, not before them. Which is the right approach to have marked pages with a different layout? I would be happy to update https://wiki.contextgarden.net/Page_Layout#Multiple_layouts. Many thanks for your help, Pablo

1 0

Subject: Leading spaces verbatim
by Kalouguine Andre 30 Jan '23

30 Jan '23

Good day to everyone, I'm trying to make a verbatim block of text with copiable leading spaces so that students can just copy my Python code snippets into their IDE. I believe the question has been asked before (though I confess I can't find the right search terms to find the answer again). I get that PDFs are not the optimal way to give code to students (which is why for longer snippets, I just give them the files or I attach them into the PDF), but for short snippets it would be so much simpler... I recently stumbled onto this article: https://www.overleaf.com/latex/examples/using-luatex-to-convert-interword-g… wherein the author replaces the TeX glue with spaces and kerning. I was wondering whether the same idea could be applied within the typing environment but making a primitive verbatim environment using \obeylines and \obeyspaces did not result in copiable spaces. Unfortunately, whilst I have some concepts of how luatex works on the input file, the step wherein a pdf is formed is fairly misterious to me, meaning I can't really understand the Lua code from said article (https://gist.github.com/Semptum/076cca71bc251ebe19ff96c5effca3cb) Hence, my three questions: - Is it even realistic to make such a typing environment? - What would be the best path to do so? - Can someone recommend some reading material specifically about this kind of typographical adjustments using LuaTex? Stuff like adjusting the glyphs's position, replacing characters with combined characters etc... Sorry if that's a bit vague, as you can see from the rest of the message, I never really went too deep into the later stages of the TeX pipeline. Best regards, Andre

4 8

how to change metadata halfway through document
by jbf 30 Jan '23

30 Jan '23

Am trying to understand how best to change the title metadata in headertext halfway through a document that has two parts: Constitutions and Regulations. My first attempt (did not work) \startsetups[headertext] \startdocument [metadata:title={Regulations}] \stopsetups \setupheadertexts [ ] [{\getmarking[chapter]\hskip1em \pagenumber}] [{\pagenumber \hskip1em \setup{headertext}}] [ ] My second attempt (quite crass, but it works!!) was to create a second \startdocument within the main \startdocument (obviously closing it towards the end but before the main \stopdocument), this time with [metadata:title={Regulations}] instead of the original [metadata:title={Constitutions}]. However, I have a strong feeling this is not a very elegant solution! Thoughts? Julian

2 2