March 2021 - ntg-context - NTG Mailing Lists

Grid typesetting, blockquotes in smaller font across pagebreaks
by denis.maier＠ub.unibe.ch 25 Mar '21

25 Mar '21

Hi, I'm playing around with grid typesetting. Consider the following example: -------------------------------------- \setuppapersize[A5][A5] \setupbodyfont[10pt] \setuplayout[grid=yes] \showgrid \setupdelimitedtext[blockquote] [ style=\tfx, %style=\tfx\setupinterlinespace, % this breaks grid snapping spacebefore=halfline, indentnext=no, leftmargin=no, rightmargin=no, ] \starttext \dorecurse{5}{ \dorecurse{5}{Some text on a grid. } \startblockquote \dorecurse{10}{A quotation in a smaller font. } \stopblockquote \dorecurse{5}{This should be on the grid again. }} \stoptext -------------------------------------- With style=\tfx it kind of works as long as the quotations don't run over page boundaries. With style=\tfx\setupinterlinespace paragraphs after quotations don't snap back to the grid. Spacebefore=line is somewhat better, but also only if I use \tfx without \setupinterlinespace. Any hints? (But maybe I'm approaching the problem from the wrong direction anyway... I need the have pages end consistently at the same baseline, and I thought grid typesetting might be an option here. But maybe that was a wrong assumption in the first place... Or there are better solutions.) Best, Denis

1 0

Summing up ligature prevention tests
by denis.maier＠ub.unibe.ch 25 Mar '21

25 Mar '21

Hi, Trying to sum up what we currently have regarding ligature prevention, it looks like we have three mechanisms available: 1. \replaceword[set][input][output] Ex.: \replaceword[ligs][Auflage][Au{fl}age] Replaces a word input with the corresponding output. Doesn't work at the moment with LMTX. Can be used for words with multiple wrong ligatures (Auflaufform). Does not take derived forms into account (e.g., replacements for Auflage and Auflagen must both be defined). 2. \blockligatures Works as a font feature to block certain ligatures Works also for derived forms of a given word (e.g., \blockligatures[Au:fl:age] will also block the fl-ligature in "Auflagen"). Currently, can't be used when multiple ligatures should be suppressed. \blockligatures[Au:fl:au:ff:orm] blocks the fl-ligature, but the ff-ligature still shows up. This here seems to works though: \blockligatures [ Au:fl:auf, au:ff:orm, ] Don't know if there are unwanted side-effects to that approach. 3. \startexceptions Works via hyphenation exceptions. To define exceptions for "Auflage" and "Auflaufform" use: \startexceptions[de] au{f-}{l}{fl}(f\zwnj l)age Au{f-}{l}{fl}(f\zwnj l)au{f-}{f}{ff}(f\zwnj f)orm \stopexceptions This does not work automatically for derived forms; you'll have to define plural and other forms as well. As this works with hyphenation exceptions you'll have to add legal hyphenation points as well, so for "Auflage", you will actually need: \startexceptions[de] au{f-}{l}{fl}(f\zwnj l)a-ge \stopexceptions IMO, the \blockligatures is the cleanest, both conceptually and syntax wise. Being able to implicitely disable derived forms is a big plus, but of course there may be drawbacks I don't see now. The only downsides I see currently is that you need workarounds to block multiple ligatures in a single words, of which there might not be too many. And, it's kind of an "all or nothing" approach as you cannot define sets of blocked ligatures. (But that may not be a relevant use case anyway.) Anything, I've missed? Other aspects to think about here? How about performance issues? (The blockligatures-mechanism resulted in this: with a word list of about 2200 words it took a bit more than five seconds to process 23 A5 pages than 2.5 seconds without the blocked ligatures. I'll test with the other methods later or tomorrow.) Denis

2 5

Writing to .tuc directly from Lua
by Jairo A. del Rio 24 Mar '21

24 Mar '21

Hi, list. I read about this: https://www.mail-archive.com/ntg-context@ntg.nl/msg60217.html But I want to know how to pass data to the .tuc file directly from Lua. I think about some complex strings are calculations which are done in each pass and slow down the whole compilation process. Something like: local function factorial(n) if in_tuc then -- whatever in_tuc means return factorials[n] else ... factorials[n] = ... return ... end end Is that feasible? Should I use the CLD versions of the TeX macros instead? Best regards, Jairo

3 6

Another bug with ligature-blocking?
by denis.maier＠ub.unibe.ch 24 Mar '21

24 Mar '21

Hi, I just ran into something strange with ligature blocking: --------------------------------------------------------------------------------------- \blockligatures[begrif:fl:ich] \definefontfeature[default][default][dlig=yes,liga=yes,] \definefontfeature[default:block][default][blockligatures=yes] \definefontfamily[times][rm][Times New Roman] \definefontfamily[termes[rm][TeX Gyre Termes] \starttext \switchtobodyfont[times] \definedfont[Serif*default] begrifflich \blank \definedfont[Serif*default:block] begrifflich \switchtobodyfont[termes] \definedfont[Serif*default] begrifflich \blank \definedfont[Serif*default:block] begrifflich \stoptext --------------------------------------------------------------------------------------- With <Times New Roman> I'm getting < begriff|lich> when blockligatures is activated. Does anyone know what's going on there? Best, Denis

2 3

Re: [NTG-context] Writing to .tuc directly from Lua
by Jairo A. del Rio 24 Mar '21

24 Mar '21

No, no actually. I only put a toy example. What I need to solve is related with storing data in the .tuc file when processes take a long time. Memoization doesn't work as data is lost with each new run. Jairo El mié, 24 de mar. de 2021 a la(s) 15:36, Aditya Mahajan (adityam(a)umich.edu) escribió: > On Wed, 24 Mar 2021, Jairo A. del Rio wrote: > > > Hi, Hans. Here's my (miserably failing) attempt: > > > > \definedataset[nicedata] > > > > \starttext > > > > \startluacode > > > > local name = "nicedata" > > > > > > -- For exposition only > > > > local function dofactorial(n) > > > > local function inner(c,m) > > > > if m<2 then return c end > > > > return inner(c*m, m-1) > > > > end > > > > return inner(1,n) > > > > end > > Is this an example or your actual use case? In case you want to just > compute the factorial without doing tail recursion: > > function factorial(n) > local product = 1 > for i = 1,n do > product = product * i > end > return product > end > > is reasonable fast (for values of n for which factorial(n) doesn't > overflow anyways). > > Aditya >

1 0

Replacement mechanism bug in LMTX?
by denis.maier＠ub.unibe.ch 24 Mar '21

24 Mar '21

Ah, I've now realized that the \blockligatures needs to be activated as a font feature... So forget about this point. But, it still looks like ligature prevention with \replaceword is not working with lmtx, but it works with --luatex. ---------------------------------------------------------------------------- % these don't prevent ligatures \replaceword[eka][auffasse][au{ff}asse] \replaceword[eka][auffasst][au{ff}asst] \replaceword[eka][auffasste][au{ff}asste] \replaceword[eka][asdf][jklö] % this works though % block as a font feature \blockligatures[ff] \definefontfeature[default:nolig][default][blockligatures=yes] % finally this here works \startexceptions[de] au{f-}{f}{ff}(f\zwnj f)asse au{f-}{f}{ff}(f\zwnj f)asste \stopexceptions \starttext no replacements\par asdf auffasste auffasse ff \blank with replacements\par \setreplacements[eka] asdf auffasste auffasse ff \blank disable replacements again\par \resetreplacements asdf auffasste auffasse ff \blank disable ligatures via font features\par \definedfont[Serif*default:nolig] asdf auffasste auffasse ff \definedfont[Serif*default] % back to normal font \blank now via exceptions\par \language[de] % this should trigger ligature handling via exceptions auffasste auffasse \stoptext ---------------------------------------------------------------------------- > -----Ursprüngliche Nachricht----- > Von: ntg-context <ntg-context-bounces(a)ntg.nl> Im Auftrag von > denis.maier(a)ub.unibe.ch > Gesendet: Montag, 22. März 2021 10:27 > An: j.hagen(a)xs4all.nl; ntg-context(a)ntg.nl > Betreff: [NTG-context] Replacement mechanism? > > Hi, > > last October I've reported a strange bug with \replaceword > > I know there's the new mechanism for dealing with ligatures, and I still intend > to convert the word list to the new format, but I'm still wondering whether > that has been fixed. > > Now, I've been testing with the minimal example below, and it looks there > might be another bug with the replacement and ligature blocking > mechanism: > > ------------------------------------------------------ > % these don't prevent ligatures > \replaceword[eka][auffasse][au{ff}asse] > \replaceword[eka][auffasst][au{ff}asst] > \replaceword[eka][auffasste][au{ff}asste] > \replaceword[eka][asdf][jklö] % this works though \setreplacements[eka] > > % doesn't block the ff ligature > \blockligatures[ff] > > % finally this here works > \startexceptions[de] > au{f-}{f}{ff}(f\zwnj f)asse > au{f-}{f}{ff}(f\zwnj f)asste > \stopexceptions > > > \starttext > asdf % replacements work in general > auffasste > auffasse > ff > > % now via exceptions: > \language[de] > auffasste > auffasse > ff > \stoptext > ------------------------------------------------------ > > > Best > Denis > > On 10/8/2020 3:15 PM, Denis Maier wrote: > > Ok, > > I've commented the whole nolig-german-wordlist out piece by piece, and > > it looks like it comes down to this: > > > > ``` > > \replaceword[eka][auffasse][au{ff}asse] > > \replaceword[eka][auffasst][au{ff}asst] > > > > \setreplacements[eka] > > > > \starttext > > auffasste > > auffasse > > \stoptext > > ``` > > > > Uncommenting one of the \replacewords makes the wrong replacement > > disappear. > > But I don't see why "auffasste" should trigger an replacement. What is > > happening here? > > i will look into it ... so patience is needed > > ----------------------------------------------------------------- > Hans Hagen | PRAGMA ADE > Ridderstraat 27 | 8061 GH Hasselt | The Netherlands > tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl > ----------------------------------------------------------------- > __________________________________________________________ > _________________________ > If your question is of interest to others as well, please add an entry to the > Wiki! > > maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg- > context > webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : > https://bitbucket.org/phg/context-mirror/commits/ > wiki : http://contextgarden.net > __________________________________________________________ > _________________________

1 0

Formulanumbers in margin
by Adam Reviczky 23 Mar '21

23 Mar '21

Hi, One more question on formulas. How can I get the formula number to be put into the left/right margin instead of left/right inside the text? I have tried the following: \starttext \showframe % figure caption into the margin \setupcaption[figure][location={rightmargin}] \startplacefigure[title=Cow] \externalfigure[cow] \stopplacefigure % this makes the formulanumber disappear % \setupformulas[location={rightmargin}] \startplaceformula[reference=eq1,location={rightmargin}] \startformula c^2 = a^2 + b^2 \stopformula \stopplaceformula \stoptext But the setupformulas will make the number disappear entirely, and the placeformula location doesn't seem to take the margin option. Thanks, Adam

2 5

Questions regarding \startexceptions and ligature prevention
by denis.maier＠ub.unibe.ch 22 Mar '21

22 Mar '21

Hi, there's this rather new mechanism for preventing ligatures: \startexceptions[de] au{f-}{f}{ff}(f\zwnj f)asse au{f-}{f}{ff}(f\zwnj f)asste \stopexceptions Two questions: 1. Can you have multiple \startexceptions[de] environments ? Will they accumulate ? (I'm thinking about preparing a general list of exceptions, but of course you will also want individual exceptions...) 2. What is the exact meaning of these four arguments ? {1}{2}{3} is clear, but what about the parentheses ? Best, Denis

2 5

Replacement mechanism?
by denis.maier＠ub.unibe.ch 22 Mar '21

22 Mar '21

Hi, last October I've reported a strange bug with \replaceword I know there's the new mechanism for dealing with ligatures, and I still intend to convert the word list to the new format, but I'm still wondering whether that has been fixed. Now, I've been testing with the minimal example below, and it looks there might be another bug with the replacement and ligature blocking mechanism: ------------------------------------------------------ % these don't prevent ligatures \replaceword[eka][auffasse][au{ff}asse] \replaceword[eka][auffasst][au{ff}asst] \replaceword[eka][auffasste][au{ff}asste] \replaceword[eka][asdf][jklö] % this works though \setreplacements[eka] % doesn't block the ff ligature \blockligatures[ff] % finally this here works \startexceptions[de] au{f-}{f}{ff}(f\zwnj f)asse au{f-}{f}{ff}(f\zwnj f)asste \stopexceptions \starttext asdf % replacements work in general auffasste auffasse ff % now via exceptions: \language[de] auffasste auffasse ff \stoptext ------------------------------------------------------ Best Denis On 10/8/2020 3:15 PM, Denis Maier wrote: > Ok, > I've commented the whole nolig-german-wordlist out piece by piece, and > it looks like it comes down to this: > > ``` > \replaceword[eka][auffasse][au{ff}asse] > \replaceword[eka][auffasst][au{ff}asst] > > \setreplacements[eka] > > \starttext > auffasste > auffasse > \stoptext > ``` > > Uncommenting one of the \replacewords makes the wrong replacement > disappear. > But I don't see why "auffasste" should trigger an replacement. What is > happening here? i will look into it ... so patience is needed ----------------------------------------------------------------- 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

Typing within doifmode leads to error
by Christoph Reller 21 Mar '21

21 Mar '21

Hi, Consider the following MWE: \definetyping[T] \definemode[mode][yes] \starttext \doifmode{mode}{% \startT Bla \stopT} \stoptext Compilation with the currently latest ConTeXt LMTX (ver: 2021.03.17 17:46 LMTX fmt: 2021.3.18) fails with: tex error > runaway error: end of file encountered mtx-context | fatal error: return code: 1 Compilation is successful if I replace doifmode{mode}{...} by \startmode[mode]...\stopmode. Is there anything I'm missing? (This could be a bug.) Cheers, Christoph Reller

3 14