Re: [NTG-context] What to do when ConTeXt not revealing the error details?

On Mon, 31 Oct 2022, Joel via ntg-context wrote: > I found what it was, a % in the text preventing a \stopitemize to close a > list. Thanks! --Joel mtxrun concheck filename is very useful in such situations. Aditya

Re: [NTG-context] What to do when ConTeXt not revealing the error details?

I found what it was, a % in the text preventing a \stopitemize to close a list. Thanks! --Joel On Sunday, October 30, 2022 at 07:56:44 PM MDT, Gavin wrote: Hi Joel, I get this error frequently when I forget to stop an environment, for example a \startsection with no \stopsection or

Re: [NTG-context] What to do when ConTeXt not revealing the error details?

Hi Joel, I get this error frequently when I forget to stop an environment, for example a \startsection with no \stopsection or a \startplacefigure with no \stopplacefigure. This freqeuntly doesn’t cause an error because the engine is happily packing my entire book into a margin figure. See if

[NTG-context] What to do when ConTeXt not revealing the error details?

I have a very large document that, when compiled, produces a PDF, but reports the error "mtx-context | fatal error: return code: 1". The PDF can open, but after about 100 pages in, the content starts appearing all in the wrong place. Usually when I compile, it says there is an error, and I

Re: [NTG-context] is something wrong with the mailing list?

Am 30.10.22 um 16:56 schrieb Gavin: Hi Hraban, It has been pretty quiet, but there were some posts on Oct 27. You could check the bottom of the web version to see if you have been missing activity. https://mailman.ntg.nl/pipermail/ntg-context/2022/date.html Of course, could have thought of

Re: [NTG-context] something’s wrong with \definefontfallback

Am 30.10.22 um 16:54 schrieb Hans Hagen via ntg-context: On 10/30/2022 4:43 PM, Henning Hraban Ramm via ntg-context wrote: This used to work: \definefontfallback[seguiFB]    [file:seguisym.ttf]    [0x0-0xF]    [check=yes,force=no] \definetypeface [contextstart] [ss] [sans]  [segoe]

Re: [NTG-context] is something wrong with the mailing list?

Hi Hraban, It has been pretty quiet, but there were some posts on Oct 27. You could check the bottom of the web version to see if you have been missing activity. https://mailman.ntg.nl/pipermail/ntg-context/2022/date.html

Re: [NTG-context] something’s wrong with \definefontfallback

On 10/30/2022 4:43 PM, Henning Hraban Ramm via ntg-context wrote: This used to work: \definefontfallback[seguiFB]   [file:seguisym.ttf]   [0x0-0xF]   [check=yes,force=no] \definetypeface [contextstart] [ss] [sans]  [segoe] [default][fallbacks=seguiFB] (Intention is to take all

[NTG-context] is something wrong with the mailing list?

Hi again, I didn’t get any mails from ntg-context between 2022-10-26, 01:52 and my mails now. Was there no activity? (Maybe I was switched off due to bounced mails, because my provider had left outdate the ssl certificate of the mail server...) Hraban

[NTG-context] something’s wrong with \definefontfallback

This used to work: \definefontfallback[seguiFB] [file:seguisym.ttf] [0x0-0xF] [check=yes,force=no] \definetypeface [contextstart] [ss] [sans] [segoe] [default][fallbacks=seguiFB] (Intention is to take all missing characters from this symbol font.) But with current LMTX, I

[NTG-context] Undefined control sequence \bodyfontsizevariable

Latest LMTX, probably an error in mkxl/s-fonts-show.mkxl: \starttext \showbodyfont \showbodyfontenvironment % error! As you can see, the font class is called \quotation{\fontclass} and the bodyfont is typeset from \quotation{\fontname\font} in \the\globalbodyfontsize. \stoptext Hraban