September 2020 - ntg-context - NTG Mailing Lists

\setbreakpoints[compound] with numbers
by Denis Maier 18 Sep '20

18 Sep '20

Hi, In the texts I'm currently typesetting, I occassionaly have to deal with ISBNs. So, e.g. 978-3-123456-78-9 \setbreakpoints[compound] does not enable automatic linebreaks after or before the hyphens. Is there a way to deal with this? Perhaps something similar like \hyphenatedurl{} or an extended version of \setbreakpoints. (I currently use zero-width spaces, so I got rid of ISBNs in the margins, but a more automatic solution would be great.) Best, Denis

2 2

Re: [NTG-context] lmtx update
by Eduardo Bohoyo 17 Sep '20

17 Sep '20

El 17/9/20 a las 1:07, ebohoyod escribió: > > El 16/9/20 a las 18:23, Wolfgang Schuster escribió: >> ebohoyod schrieb am 16.09.2020 um 17:52: >>> Hi, >>> >>> It seems that the Lettrine module is one of those affected: >>> >>> https://tex.stackexchange.com/questions/562534/does-context-fail-in-the-lmt… >>> >>> >>> But, honestly, first, I don't know what means "/Of course it might >>> have other side effects once in lmtx we everywhere expect freezing >>> to be enabled./" >>> I suppose that, in order not to be a nuisance (and not to digress >>> into this real subject of interest), a short answer would be enough >>> to put me on track to investigate it. >>> >>> On the other hand, I suppose the best practice, from what I have >>> just read, would be not to use \forgetparagraphfreezing globaly, but >>> \forgetparagraphfreezing and \setparagraphfreezing at the beginning >>> and end of the first paragraph respectively of each chapter. Would >>> this be the least harmful way? That is, wrapping it up to avoid this >>> provisional failure of the Lettrine with LMTX module, but at the >>> same time to avoid affecting that default freezing proposal in the >>> rest of the document, right? >>> >>> By the way, and just out of curiosity, how does the recommended >>> provisional command work? Would it be something like this in the >>> preamble?: >>> >>> \definingparagraphs >>> firstparagraph][n=1] >>> \setupparagraphs [firstparagraph][1][align={hanging}] >>> >>> And then this arrangement in the \input files?: >>> >>> \startfirstparagraph >>> \lettrine{B}{lah} blah, blah, blah... >>> \stopfirstparagraph >>> \blank [overlay] \strut >>> >>> I know it's a dirty, inelegant solution, but I can't think of a >>> better one at the moment. >> >> Below is a minimal example which doesn't rely on the module, >> the problem is caused by the order of the \noindent and \parshape >> command. >> >> When a paragraph starts before the \parshape values are set >> the arguments are ignored because the values are already frozen >> at this moment, when you set the values before the paragraphs >> starts ConTeXt applies them. >> >> \starttext >> >> \hsize 10cm >> >> % lettrine module, \noindent before \parshape >> >> \noindent >> \parshape 3 1cm 9cm 1.5cm 8.5cm 0cm 10cm >> \input weisman >> >> \blank >> >> % working order, \parshape before \noindent >> >> \parshape 3 1cm 9cm 1.5cm 8.5cm 0cm 10cm >> \noindent >> \input weisman >> >> \stoptext >> >> Wolfgang > Thank you for this illustrative example, Wolfgang. So, what \forgetparagraphfreezing does is to reverse the order that lmtx currently imposes by default, right? In other words, \forgetparagraphfreezing, recovers the default behaviour of MkIV. So, I suspect that this will not change; if we want to apply Lettrine to a paragraph, from now on we must wrap it up with \forgetparagraphfreezing and \setparagraphfreezing. Please correct me if I'm wrong. Eduardo.

2 3

lmtx update
by ebohoyod 16 Sep '20

16 Sep '20

Hi, It seems that the Lettrine module is one of those affected: https://tex.stackexchange.com/questions/562534/does-context-fail-in-the-lmt… But, honestly, first, I don't know what means "/Of course it might have other side effects once in lmtx we everywhere expect freezing to be enabled./" I suppose that, in order not to be a nuisance (and not to digress into this real subject of interest), a short answer would be enough to put me on track to investigate it. On the other hand, I suppose the best practice, from what I have just read, would be not to use \forgetparagraphfreezing globaly, but \forgetparagraphfreezing and \setparagraphfreezing at the beginning and end of the first paragraph respectively of each chapter. Would this be the least harmful way? That is, wrapping it up to avoid this provisional failure of the Lettrine with LMTX module, but at the same time to avoid affecting that default freezing proposal in the rest of the document, right? By the way, and just out of curiosity, how does the recommended provisional command work? Would it be something like this in the preamble?: \definingparagraphs firstparagraph][n=1] \setupparagraphs [firstparagraph][1][align={hanging}] And then this arrangement in the \input files?: \startfirstparagraph \lettrine{B}{lah} blah, blah, blah... \stopfirstparagraph \blank [overlay] \strut I know it's a dirty, inelegant solution, but I can't think of a better one at the moment.

2 1

sidefloats and narrower
by Henning Hraban Ramm 16 Sep '20

16 Sep '20

Hi again, this is related to “quotation with footnote“. If you compile the example with (latest) LMTX, all is good. But MkIV (--luatex) lets the quotations (“Zitat”) run over the float. Without the \setupdelimitedtext line, distances between paragraphs become irregular in both versions (but differently). \useMPlibrary[dum] \usemodule[visual] \setupwhitespace[halfline] \setupdelimitedtext[quotation][method=font] \setupnarrower[left=2em,right=1.5em] \definenarrower[Zitat] \setupnarrower[Zitat] [left=2em, right=1.5em, before=\dontleavehmode\hskip-0.33em\startquotation, after=\stopquotation] \starttext %\fakewords{50}{60} \startplacefigure[location={right,-line},title={\fakewords{7}{10}}] \externalfigure[022][width=0.33\textwidth,height=0.75\textheight] \stopplacefigure \startZitat \fakewords{30}{60} \stopZitat \fakewords{30}{60} \startZitat \fakewords{15}{20} \stopZitat \fakewords{30}{60} \stoptext Hraban

1 0

Re: [NTG-context] footnotes in captions in floatcombinations
by Henning Hraban Ramm 16 Sep '20

16 Sep '20

Thank you, Otared! I updated to LMTX/MkIV 2020.09.15 18:11: The images appear if I use --luatex (i.e. MkIV vs. LMTX), but the footnotes use the width of the image. The old MWE can’t show that. Without \automigrateinserts I get both images and the short footnote, but not the long one. \useMPlibrary[dum] \automigrateinserts \showframe \starttext \input lorem \startplacefigure[location=none] \startfloatcombination[2*1] \startplacefigure[title={Left Image\footnote[f:3]{\input knuth }}] \externalfigure[003][width=.48\textwidth] \stopplacefigure \startplacefigure[title={Right Image\footnote[f:4]{Anything}}] \externalfigure[004][width=.48\textwidth] \stopplacefigure \stopfloatcombination \stopplacefigure \input tufte \stoptext Am 14.09.2020 um 22:43 schrieb Otared Kavian <otared(a)gmail.com>: > > Hi Hraban, > > Your are right, your file is typeset correctly as expected with ConTeXt mkiv version 2020.06.25 10:55, but not with the current lmtx. > (I am sending you the output with this message). > > Best regards: Otared K. > > <footnote-in-captions.pdf> > >> On 14 Sep 2020, at 21:40, Henning Hraban Ramm <texml(a)fiee.net> wrote: >> >> Hi, >> I got a problem with current LMTX as well as with other versions – while I’m sure it used to work at some point: >> >> As soon as there’s a footnote in the caption of a placefigure within a floatcombination, the figure won’t get placed. There’s no problem outside of floatcombinations or with floatcombinations without footnotes. >> >> Please let there be an easy fix... >> >> Hraban >> >> >> \useMPlibrary[dum] >> \automigrateinserts >> \showframe >> >> \starttext >> >> \input knuth >> >> %\startplacefigure[location=none] >> %\startfloatcombination[2*1] >> \startplacefigure[title={Image with footnote\footnote[f:1]{foo bar baz}}] >> \externalfigure[001][width=.48\textwidth] >> \stopplacefigure >> \startplacefigure[title={Another image with footnote\footnote[f:2]{Something}}] >> \externalfigure[002][width=.48\textwidth] >> \stopplacefigure >> %\stopfloatcombination >> %\stopplacefigure >> >> \input lorem >> >> \startplacefigure[location=none] >> \startfloatcombination[2*1] >> \startplacefigure[title={Left Image\footnote[f:3]{doo be doo}}] >> \externalfigure[003][width=.48\textwidth] >> \stopplacefigure >> \startplacefigure[title={Right Image%\footnote[f:4]{Anything} >> }] >> \externalfigure[004][width=.48\textwidth] >> \stopplacefigure >> \stopfloatcombination >> \stopplacefigure >> >> \startplacefigure[location=none] >> \startfloatcombination[2*1] >> \startplacefigure[title={Left Image}] >> \externalfigure[005][width=.48\textwidth] >> \stopplacefigure >> \startplacefigure[title={Right Image}] >> \externalfigure[006][width=.48\textwidth] >> \stopplacefigure >> \stopfloatcombination >> \stopplacefigure >> >> \input tufte >> >> \stoptext >> >> >> >> ___________________________________________________________________________________ >> 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

Footnote font size equal to main text font size
by Jairo A. del Rio 16 Sep '20

16 Sep '20

Hi, list. I've adapted the following example from the mailing list. My aim is to use endnotes for each chapter: \mainlanguage[es] \definehead[footnotetitle][title] \startsetups[chapter:after] \ifcase\rawcountervalue[footnote]\relax \else \startfootnotetitle[title={Notas}] \placefootnotes \stopfootnotetitle \fi \stopsetups \setupnotes[location=none] \setupnotation[way=bychapter] \setupfootnotedefinition[style={\switchtobodyfont[12pt]}] \setuphead[chapter][aftersection=\setups{chapter:after}] \starttext \startchapter[title={Chapter One}] Here comes \footnote{a footnote}. Aquí \footnote{otra nota a pie de página}. \stopchapter \stoptext However, I'm concerned by \switchtobodyfont. How should I make footnote size the same as the default font size, even when an arbitrary font size is used. E.g.: \setupbodyfont[24pt] % It could be another number instead of 24 \setupfootnotedefinition[style={\switchtobodyfont[???]}] Thank you in advance. Jairo :)

3 2

Quotation with footnote
by Henning Hraban Ramm 16 Sep '20

16 Sep '20

My current book contains a lot of quotations with their sources marked as footnotes, e.g. \definedelimitedtext[Zitat][ %setups=Zitat, % doesn’t work!? left=», right=«, leftmargin=2em, rightmargin=1.5em, ] \startZitat A rose is a rose is a rose.\footnote{Marx brothers} \stopZitat Now, since the quotations are whole sentences or paragraphs, the footnote marker needs to be placed _after_ the closing quotation mark. (German typography, I learned it’s different at least in US English.) I tried several approaches e.g. with my own single start/stop macros that call \start/stopnarrower or \start/stopZitat – that always lead to unclosed environments. * Only the delimitedtext approach gives a hanging opening quotation mark (which looks nice and I’d like to have). * \stopnarrower within a macro doesn’t seem to work (all following text stays narrower). * I can’t get rid of that space introduced by the CR before \stop – didn’t find a place where \gobblespacetokens works, maybe that’s the wrong command. Most preferred would be a solution that checked if there’s a footnote in front of \stopZitat and would put the closing quotation mark in front instead of after. Without a footnote it would just place the mark. Something like \stopZitat\footnote{...} would also be nice, but I guess that’s too far outside of TeX’s logic. In the worst case I’d need to typeset the closing mark manually. Some hints please? Hraban

3 6

Documentation for the database module
by mylists＠posteo.de 16 Sep '20

16 Sep '20

Hi, I want to typeset a Periodic Table of the Elements. The according data is prepared in a file with comma separated values (csv/UNIX). I found some *very* basic informations how to get file based csv-data typeset, but the result is hardly recognizable as Periodic Table of the Elements. To understand how to use the according commands I need a documentation of it. What I found was this: https://wiki.contextgarden.net/M-database which is more a summary of two examples with no explanations and starting with the warning "This may be outdated". Where can I find a good one? Thanks a lot for any help in advance! Cheers! mcc

3 2

Bad argument #1 to 'prehypenchar'
by Aditya Mahajan 15 Sep '20

15 Sep '20

The following MWE gives an error with LMTX 2020.09.05 \usemodule[vim] \definevimtyping[MATLABCODE][syntax=matlab] \starttext \startMATLABCODE saveas(gcf(), "output/same-sigma.png") \stopMATLABCODE \stoptext The error message is: callback error: ...metatex/texmf-context/tex/context/base/mkiv/lang-ini.lua:509: bad argument #1 to 'prehyphenchar' (luatex.lang expected, got no value) stack traceback: [C]: in function 'lang.prehyphenchar' ...metatex/texmf-context/tex/context/base/mkiv/lang-ini.lua:509: in field 'prehyphenchar' ...metatex/texmf-context/tex/context/base/mkiv/typo-brk.lua:171: in local 'method' ...metatex/texmf-context/tex/context/base/mkiv/typo-brk.lua:392: in upvalue 'typesetters_breakpoints_handler' [string "local tonut = nodes.tonut..."]:16: in function <[string "local tonut = nodes.tonut..."]:11> (...tail calls...) ...metatex/texmf-context/tex/context/base/mkiv/node-pro.lua:88: in function <...metatex/texmf-context/tex/context/base/mkiv/node-pro.lua:79> 1 >> \SYNBOL{}saveas(gcf(), \SYN[String]{"output/same-sigma.png"})\SYNEOL{} 2 mtx-context | fatal error: return code: 256 Any idea what is going on? Thanks, Aditya

3 5

update and meeting
by Hans Hagen 15 Sep '20

15 Sep '20

Hi, I uploaded a new version. It is a follow up on the ctx meeting of last week (in a country side compound in czech with also some remote attendants, daily infrared health scans, an excursion, talks, breaks, food, and the usual have fun with context friends moments). There are a few changes that can affect users numbered 1 and 2 below. (1) During one of the coffebreak discussions we agreed to drop the two units that were never official and are kind of meaningless: 'nc' (new cicero) and 'nd' (new didot). Arthur made some stroing arguments and only Tomas remembered ever entering one of them so there was no resistance. We also considered that in order to enforce the use of si units the 'in' should go away but that has been postponed (it is anyway last in the checked keywords so has no overhead). At some point the "true" prefix might go too (never really used, but no overhead either). (2) Another change is in the \startdocument mechanism. This (already old and rusted) wrapper runs on top of variables but we think no one knows (or uses) that. So, it now is a real wrapper with inheritance and such. It is dedicated to Tomas Hala who had to struggle with the old one but still gave a presentation using it. Here's an example: \definedocument[thesis] \setupdocument[a=b,e=f] \setupdocument[thesis][a=x,c=d] % \startsetups[thesis:start] \startsetups[document:start] START \stopsetups \startsetups[thesis:stop] % \startsetups[document:stop] STOP \stopsetups % \startdocument[thesis] \startthesis (\currentdocument/a): \documentvariable{a}\par (\currentdocument/c): \documentvariable{c}\par (\currentdocument/e): \documentvariable{e}\par \stopthesis % \stopdocument There's also a user mode set with the document enviroments name. (3) Some other additions are for Taco so will not be disclosed here (yet). (4) There are some summaries of my presentations added to the distribution (the wiki will collect more at some point). 1 context-2020-mkii-mkiv-mkxl.pdf 2 context-2020-luametatex.pdf 3 context-2020-concepts.pdf 4 context-2020-tokens.pdf 5 context-2020-implementers.pdf 6 context-2020-datatypes.pdf 7 context-2020-ecmascript.pdf 8 context-2020-svg.pdf 9 context-2020-mp.pdf They use the new 'boring' presentation style and most are probably useless without demos and discussion but anyway ... The first one is an overview of the three successive context versions. The second one is about the state of luametatex and the third discusses a couple of things introduced last year (luametatex and lmtx). The tokens talk is for low level tex lovers (or those who need to impress other texies with token speak), and the talk about implementers was probably only useful for wolfgang and me, but who knows. The datatypes are an overview over what is standard in tex and in lua as well as what we have extra on top of that. The seventh talk fits in the 'we also need to have some fun talks', and the eigths one was for a large part a discussion and accompanied by a demo by Hraban. The last one is (of course) also a fun one and (of course) discusses Don Knuths latest font which (of course) is kind of special Anyway, it's all part of the 'we keep going' story, which is why they are in the distribution. (5) We had several talks / discussions about the greatly improved wiki and users are invited to participate in completing the pages that need to be filled in, but I leave that to Taco to summarize. 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 -----------------------------------------------------------------

1 0