- ntg-context - NTG Mailing Lists

\startstructurelevel
by Denis Maier 20 Sep '20

20 Sep '20

Hi, I'm using \startstructurelevel so I can nest sections without having to worry about where I am at the moment. (Actually I'm typesetting JATS XML, and there's only one <sec> tag, and using \startstructurelevel makes the mapping easier.) Now, for the bibliography, I need an unnumbered heading. How can I get that? Browsing through the source I came across this: https://source.contextgarden.net/tex/context/base/mkiv/strc-lev.mkvi?search… So, it seems that \startstructurelevel is just an alias for \startsectionlevel. Right? Unnumbered headings can be produced with \startsubjectlevel So, is there a way to let \startstructurelevel the unnumbered variant, or should I just use \startsubjectlevel instead? By the way, is there a reason for the existence \startstructurelevel next to \startsectionlevel? What's the exact purpose of this? Best, Denis

2 2

Add arrow tips to axes in lmt_function
by Jairo A. del Rio 19 Sep '20

19 Sep '20

Hi, list! I want to know how to add arrow tips for axes (x, y) to a function. I did the following based on a luametafun example: \starttext \startMPcode{doublefun} draw lmt_function [ xmin=0, xmax=10, xstep=.05, ymin=-2, ymax=2, code="1.5 * math.cosd(240 * math.sqrt(x))", xlabels="no",ylabels="no", sx=2mm, sy=4mm, linewidth=.025mm, offset=.1mm,] xsized 8cm; \stopMPcode \stoptext But I didn't find anywhere in manuals or the mailing list concerning arrows, nor key-value pairs for lmt_function. Thank you in advance. Best regards, Jairo :)

1 0

Allow pagebreaks in footnotes
by denis.maier.lists＠mailbox.org 19 Sep '20

19 Sep '20

Hi Is there a setting that prevents footnotes from spreading over more than one page? I have a document where this seems to be the case, but I don't know why. It just looks like ConTeXt tries to keep the complete footnote on one page, which leads to ugly white space at the end of almost every page. (LaTeX has \interfootnotelinepenalty to customize this, but what about ConTeXt?) Best Denis

3 2

Error setting up ConTeXt in MacTeX 2020
by Felix Krause 18 Sep '20

18 Sep '20

Hi all, with MacTeX 2020 on a newly installed Mac, I have the problem that ConTeXt doesn't work anymore: $ context file.tex mtx-context | warning: no format found, forcing remake (commandline driven) […] snip lots of lines resolvers | formats | changing to format path '/var/folders/rj/hfjmjx796q102y4v23vh038c0000gp/T/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luatex' resolvers | formats | unable to change to format path '/var/folders/rj/hfjmjx796q102y4v23vh038c0000gp/T/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luatex' mtx-context | error, no format found with name: cont-en, aborting system | total runtime: 5.315 seconds The [ConTeXt docs][1] say that I should run `mtxrun --generate`, which seems to run successfully, and `context --make`, which finishes with the same „unable to change format path“ error (I believe this is what context automatically does when compiling my file, hinted by the „no format found. forcing remake“ message). I tried explicitly running `context --make cont-en` which yields the same result. The given path does exist on my hard drive. I don't even know if the „unable to change format path“ message is actually an error, but I have no other indicator of what goes wrong. The only line that explicitly says „error“ is the one I get when trying to process the file. Interestingly, I have another Mac where I upgraded from MacTeX 2019 to MacTeX 2020 and everything works there. I made sure that everything is up-to-date with the TeX Live Utility. How can I fix this problem? Regards, Felix [1]: https://wiki.contextgarden.net/Running_Mark_IV

7 12

Problem with fonts in Lua
by MANUEL GONZALEZ SUAREZ 18 Sep '20

18 Sep '20

Hi all: I have this minimal example (thanks to Pablo and Charles): \mainlanguage [es] \definefallbackfamily [mainface] [rm] [New Athena Unicode] [preset = range: greek, force = yes] % \definefallbackfamily [mainface] [rm] [Old Standard] % [preset = range: greek, force = yes] \definefontfamily [mainface] [rm] [TeX Gyre Pagella] \definefontfamily [mainface] [ss] [TeX Gyre Heros, scale = 0.75] \setupbodyfont [mainface] \starttext Spanish text \input tufte Greek Text: Μετὰ δὲ ταῦτα οὐ πολλαῖς ἡμέραις ὕστερον ἦλθεν ἐξ Ἀθηνῶν Θυμοχάρης ἔχων ναῦς ὀλίγας · καὶ εὐθὺς ἐναυμάχησαν αὖθις Λακεδαιμόνιοι καὶ Ἀθηναῖοι, ἐνίκησαν δὲ Λακεδαιμόνιοι ἡγουμένου Ἀγησανδρίδου. \stoptext I compile with TeXLive 2020 and Windows 10. I have the two fonts (New Athena Unicode and Old Standard) installed on my system but with New Athena Unicode it does not compile; on the other hand, with Old Standard it does compile. I do not know what I can do. Thanks for the help. Manuel González.

3 2

Struggling with startuseMPgraphic and string argument!
by Geert Verhaag 18 Sep '20

18 Sep '20

Hi, I'm trying to pass a string argument value to an MPgraphic but it doesn't seem to work: Tried the following: \startuseMPgraphic{name}{lbl} pair a ; a := (3cm,3cm) ;label.top("\MPvariable{lbl}",a) ; \stopuseMPgraphic \starttext \useMPgraphic{name}{lbl=1} \stoptext The above works as expected! But the following doesn't: \startuseMPgraphic{name}{lbl} pair a ; a := (3cm,3cm) ;label.top("\MPvariable{lbl}",a) ; \stopuseMPgraphic \starttext \useMPgraphic{name}{lbl=abc} \stoptext It yields: 1 \startuseMPgraphic{name}{lbl} 2 pair a ; a := (3cm,3cm) ;label.top("\MPvariable{lbl}",a) ; 3 \stopuseMPgraphic 4 5 %\startuseMPgraphic{name}fill fullcircle scaled 200pt withcolor .625yellow ;\stopuseMPgraphic 6 7 \starttext 8 Example: 9 >> \useMPgraphic{name}{lbl=abc} 10 \stoptext 11 <to be read again> a \m_meta_current_variable a-a bc <argument> ... \hbox {\scratchdimen \m_meta_current_variable sp}\ifzeropt \wd \b_meta_v... \secondoftwoarguments #1#2b-#2 \9>>1 #1,2-\meta_prepare_instance_variable {#1} \syst_helpers_do_process_comm... \syst_helpers_do_process_comma_list ...rgument #1, ]\relax \global \advance \... ... l.9 \useMPgraphic{name}{lbl=abc} So it seems that only numbers can be passed not character strings! Why is that? Is there a possibility to achieve this functionality? Regards, Gerard

2 4

\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