Re: [NTG-context] Bug in context

2023-05-13 Thread Marco Patzer via ntg-context
On Sat, 13 May 2023 14:04:49 +0200 Lutz Haseloff via ntg-context wrote: > When I invoke context with parameter --ansi, the logfile remains > empty. I can confirm: https://www.mail-archive.com/ntg-context@ntg.nl/msg90303.html Marco

Re: [NTG-context] \typefile not including file and returning success

2023-02-21 Thread Marco Patzer via ntg-context
On Wed, 21 Dec 2022 13:17:15 +0100 Hans Hagen via ntg-context wrote: > The next upload will have: > > \adddefaultsuffix[foo,{},crap] > \adddefaultsuffix[{}] > > \typefile{./crapcrap} > \typefile{crapcrap} > > which someone has to document on the wiki Apologies for taking so long. But I just

Re: [NTG-context] \typefile not including file and returning success

2022-12-21 Thread Marco Patzer via ntg-context
On Wed, 21 Dec 2022 13:17:15 +0100 Hans Hagen via ntg-context wrote: > > But context returning success when it clearly doesn't include the > > file is unfortunate. The missing file might go completely unnoticed. > > I'd expect an error there. > The next upload will have: > >

Re: [NTG-context] \typefile not including file and returning success

2022-12-17 Thread Marco Patzer via ntg-context
On Sat, 17 Dec 2022 10:41:11 -0800 skyhorse--- via ntg-context wrote: > The context wiki says: > "When no file extension is specified the extension .tex is assumed." It's not on the page for typefile: https://wiki.contextgarden.net/Command/typefile And that surely makes sense for TeX

Re: [NTG-context] \typefile not including file and returning success

2022-12-17 Thread Marco Patzer via ntg-context
On Sat, 17 Dec 2022 16:25:01 +0100 Otared Kavian via ntg-context wrote: > If I create a file named « bar.txt » then > > \starttext > Nothing to say\dots > > \typefile{bar.txt} > > \stoptext > > gives the correct result. I can confirm that. > However ConTeXt seems to dislike \typefile{bar}

[NTG-context] \typefile not including file and returning success

2022-12-17 Thread Marco Patzer via ntg-context
Hi! In the following example the file “bar” is not included: # create file “bar” echo Bar > bar # t.tex \starttext Foo \typefile{bar} \stoptext Then run context --errors='*' t.tex The text “bar” is not included in the PDF, only Foo is. The log file shows: verbatims > file

Re: [NTG-context] cannot update ConTeXt to 2022.09.16

2022-09-21 Thread Marco Patzer via ntg-context
On Mon, 19 Sep 2022 17:16:19 +0200 Pablo Rodriguez via ntg-context wrote: > Could anyone confirm the issue? I can confirm. On a fresh install I'm getting 2022.09.11 20:44 Marco ___ If your question is of

Re: [NTG-context] [secure site not available]

2022-09-15 Thread Marco Patzer via ntg-context
On Wed, 14 Sep 2022 19:19:05 +0200 Pablo Rodriguez via ntg-context wrote: > https://lmtx.pragma-ade.nl, https://pragma-ade.nl and > https://pragma-ade.com seem to use a certificate that is only valid > for https://lmtx.pragma-ade.com (according to Firefox). Correct. This is a misconfigured

Re: [NTG-context] Typearea module fails with “Missing number”

2022-08-29 Thread Marco Patzer via ntg-context
On Mon, 29 Aug 2022 09:30:34 +0200 Marco Patzer via ntg-context wrote: > The typearea module fails on LMTX (runs ok with MkIV): > > tex error > tex error on line 89 in file > /usr/local/share/context-lmtx/tex/texmf-modules/tex/context/third/typearea/t-typearea.tex: &

[NTG-context] Typearea module fails with “Missing number”

2022-08-29 Thread Marco Patzer via ntg-context
Hi! The typearea module fails on LMTX (runs ok with MkIV): tex error > tex error on line 89 in file /usr/local/share/context-lmtx/tex/texmf-modules/tex/context/third/typearea/t-typearea.tex: Missing number, treated as zero LMTX 2022.08.25 19:21 Marco

[NTG-context] Database of translations (was: Simple question)

2022-05-10 Thread Marco Patzer via ntg-context
On Tue, 10 May 2022 00:15:30 +0200 Gerben Wierda via ntg-context wrote: > What is the easiest way to have a ‘database’ of translations for > strings and maybe links? Here's an idea: \usemodule [translate] %% \mainlanguage [nl] \assigntranslation [en=alpha, nl=beta]\to\TRfoo \translateinput

Re: [NTG-context] Switching fonts changes framedtext justification

2022-04-03 Thread Marco Patzer via ntg-context
On Sat, 2 Apr 2022 17:36:35 -0700 Thangalin via ntg-context wrote: > The following code produces framed text areas, each having different > justification: > > […] > How would you ensure that both text areas remain fully justified? I don't have that Emoji font, but replacing it with other

Re: [NTG-context] tilde character

2022-03-14 Thread Marco Patzer via ntg-context
On Mon, 14 Mar 2022 18:36:08 +0100 Henning Hraban Ramm via ntg-context wrote: > How do I get the default tilde character from a font? \starttext \startasciimode a~b \stopasciimode a\textasciitilde b \stoptext Marco

[NTG-context] Errors compiling the MetaFun manual

2022-03-12 Thread Marco Patzer via ntg-context
Hi! I tried to compile the MetaFun manual from /doc/context/sources/general/manuals/metafun and ran into a few issues. I don't know if that's expected or if it's supposed to work on a current LMTX. Attached are the first two issues. It takes a while to boil it down to MWEs. Let me know if I

Re: [NTG-context] \asciimode and MetaPost in LMTX result in “Isolated expression”

2022-03-12 Thread Marco Patzer via ntg-context
On Sat, 12 Mar 2022 22:27:38 +0100 Henning Hraban Ramm via ntg-context wrote: > My current and most MP-heavy project so far, fails in asciimode with > "Extra }, or forgotten \endgroup" You can't just run “normal” projects with \asciimode. Chances are, constructs are being used that are invalid

Re: [NTG-context] \asciimode and MetaPost in LMTX result in “Isolated expression”

2022-03-12 Thread Marco Patzer via ntg-context
On Sat, 12 Mar 2022 15:51:16 +0100 Hans Hagen wrote: > you can try this > (in cont-new.tex): > > \prependtoks > \setcatcodetable\ctxcatcodes > \to \everyMPgraphic > > and then do lots of tests with and without asciimode so see if this > doesn't interfere I run almost every document with

Re: [NTG-context] \asciimode and MetaPost in LMTX result in “Isolated expression”

2022-03-12 Thread Marco Patzer via ntg-context
On Mon, 31 Jan 2022 20:02:42 +0100 Marco Patzer via ntg-context wrote: > LMTX seems to have an issue with \asciimode and MetaPost: > > \asciimode > \starttext > \startMPcode > fill unitsquare scaled 2cm; > \stopMPcode > \stoptext > > Results in: >

Re: [NTG-context] Few quick questions

2022-03-08 Thread Marco Patzer via ntg-context
On Tue, 08 Mar 2022 20:45:17 +0100 Christoph Hintermüller via ntg-context wrote: > Hans indicated a tool, a program, which allows to verify that that > all start* stop* tag pairs are symmetric and placed in correct > order. I just cant remember how it is called. Can anybody help > here?

Re: [NTG-context] PageNumber in MetaFun

2022-03-02 Thread Marco Patzer via ntg-context
On Wed, 2 Mar 2022 13:15:18 +0100 "Thomas A. Schmitz via ntg-context" wrote: > try "RealPageNumber" instead of "PageNumber." That works. Thanks for the quick reply. Marco ___ If your question is of interest to

[NTG-context] PageNumber in MetaFun

2022-03-02 Thread Marco Patzer via ntg-context
Hi! Has something changed regarding PageNumber? Take the following example: \starttext foo\page \startMPcode if PageNumber==1: fill unitsquare scaled 1cm; elseif PageNumber==2: fill fullcircle scaled 2cm; fi \stopMPcode \stoptext LMTX 2022.01.21 20:13 produces a

[NTG-context] \asciimode and MetaPost in LMTX result in “Isolated expression”

2022-01-31 Thread Marco Patzer via ntg-context
Hi! LMTX seems to have an issue with \asciimode and MetaPost: \asciimode \starttext \startMPcode fill unitsquare scaled 2cm; \stopMPcode \stoptext Results in: metafun > log > error: Isolated expression metafun > log > metapost> trace > E.dash.patterns metapost

Re: [NTG-context] Defining new float types fails in LMTX

2022-01-18 Thread Marco Patzer via ntg-context
On Sun, 16 Jan 2022 16:53:16 +0100 Marco Patzer via ntg-context wrote: > Still an issue with 2022.01.15 17:29. Fixed as of 2022.01.18 10:48. Thanks Hans. Marco ___ If your question is of interest to others as w

Re: [NTG-context] Defining new float types fails in LMTX

2022-01-16 Thread Marco Patzer via ntg-context
On Fri, 10 Dec 2021 18:22:46 +0100 Marco Patzer via ntg-context wrote: > On Fri, 10 Dec 2021 17:01:26 +0100 > Hans Hagen wrote: > > > no example code > > The MWE was included in the OP on 2021-10-30. But here it is again: Still an issue with 202

Re: [NTG-context] local notes, "serried" (paragraph) or column style.

2021-12-29 Thread Marco Patzer via ntg-context
On Wed, 29 Dec 2021 08:29:34 -0300 Youssef Cherem via ntg-context wrote: > I've tried to implement some sort of affiliation description with > local notes. I'd like them to be either in a single paragraph or in > columns (e.g., 3), but the options `serried` or `n=3` don't seem to > work for

Re: [NTG-context] Using a system font

2021-12-27 Thread Marco Patzer via ntg-context
On Sun, 26 Dec 2021 21:21:10 +4000 jdh via ntg-context wrote: > \starttext >I want to use the Mathjax_Fraktur font, which the font-manager on > Ubuntu reports that it has. >{\switchtobodyfont[Mathjax_Fraktur] .. but, this text doesn't show > up in Mathjax_Fraktur.} > > \stoptext Try:

Re: [NTG-context] Errors in source files return success

2021-12-26 Thread Marco Patzer via ntg-context
On Thu, 18 Nov 2021 19:27:25 +0100 Marco Patzer via ntg-context wrote: > Is there a way to return failure if *any* error is encountered or > do they need to be enabled each individually? A solution is to use patterns (supported in the upcoming upload): \enabledirectives [logs.

Re: [NTG-context] upload

2021-12-25 Thread Marco Patzer via ntg-context
On Sat, 25 Dec 2021 12:44:31 +0100 Hans Hagen wrote: > because these are not errors in the sense of 'quit' ... for instance > missing references can be resolved in a second run Ok, but that's what the context runner is for, not? It's smart and knows when it's hitting the last run and if there

Re: [NTG-context] upload

2021-12-25 Thread Marco Patzer via ntg-context
On Sat, 25 Dec 2021 11:55:31 +0100 Hans Hagen wrote: > >mtxrun --autogenerate --script context --autopdf "oeps.tex" > > > > mkiv lua stats > runtime: 0.485 seconds, 1 processed pages, 1 > shipped pages, 2.062 pages/second > mtx-context | fatal error: return code: 1 > > so ... an

Re: [NTG-context] Defining new float types fails in LMTX

2021-12-25 Thread Marco Patzer via ntg-context
On Tue, 30 Nov 2021 15:51:24 +0100 Marco Patzer via ntg-context wrote: > There's an issue with defining new floats in LMTX in combination > with bottom placement. > > The following works in MkIV, but throws an error in LMTX: Short followup: This issue is still present in 2021

Re: [NTG-context] location=outer causes bad page break in LMTX

2021-12-25 Thread Marco Patzer via ntg-context
On Tue, 30 Nov 2021 14:13:52 +0100 Marco Patzer via ntg-context wrote: > In the following example “Lorem ipsum” sits on an otherwise empty > page in LMTX. Output is as expected with MkIV. This is now fixed in the latest version. Thanks Hans.

Re: [NTG-context] upload

2021-12-25 Thread Marco Patzer via ntg-context
On Fri, 24 Dec 2021 19:45:05 +0100 Hans Hagen via ntg-context wrote: > When wrapping up before the weekend I uploaded a new lmtx (bottom > floats fixed afaiks If you mean the issue I posted on 2021-11-30, then no. It still throws an error here on my end. > exit codes more reliable The example

Re: [NTG-context] Errors in source files return success

2021-12-15 Thread Marco Patzer via ntg-context
On Wed, 15 Dec 2021 20:48:29 +0100 Hans Hagen wrote: > You can check in the next upload: > > - The 'failure' that you saw was actually a real lua error because I > hadn't adapted some fancy, a very old 'around' 2006 feature, seldom > used as it's more 'an example of possibilities' code to

Re: [NTG-context] Errors in source files return success

2021-12-15 Thread Marco Patzer via ntg-context
Hi Hans, a followup to our conversation in the meeting: here's an MWE demonstrating that errors aren't passed on to the runner script, except for "logs.errors=missing characters", which in fact do return failure, all others do return success. %% enables logging of errors same as --errors

Re: [NTG-context] Defining new float types fails in LMTX

2021-12-10 Thread Marco Patzer via ntg-context
On Fri, 10 Dec 2021 17:01:26 +0100 Hans Hagen wrote: > no example code The MWE was included in the OP on 2021-10-30. But here it is again: \setupfloat [figure] [default=bottom] %% fails %% [default=top] %% works \definefloat [foo] [foos] [figure] \starttext \startplacefigure

Re: [NTG-context] Defining new float types fails in LMTX

2021-12-10 Thread Marco Patzer via ntg-context
On Tue, 30 Nov 2021 15:51:24 +0100 Marco Patzer via ntg-context wrote: > There's an issue with defining new floats in LMTX in combination > with bottom placement. > > The following works in MkIV, but throws an error in LMTX: I don't know if the error changed or if I copied the

Re: [NTG-context] location=outer causes bad page break in LMTX

2021-12-06 Thread Marco Patzer via ntg-context
On Tue, 30 Nov 2021 14:13:52 +0100 Marco Patzer via ntg-context wrote: > In the following example “Lorem ipsum” sits on an otherwise empty > page in LMTX. Output is as expected with MkIV. Has the interface > changed or may it be a bug in LMTX? Any idea

Re: [NTG-context] Bad linebreak in figure caption

2021-12-03 Thread Marco Patzer via ntg-context
On Fri, 3 Dec 2021 09:14:59 +0100 Taco Hoekwater wrote: > Captions have their own alignment setting: > > \setupcaption[figure][align={verytolerant,stretch}] Thanks. Wikified: https://wiki.contextgarden.net/Command/setuptolerance Is there a good reason why captions (as well as e.g. framed

Re: [NTG-context] Bad linebreak in figure caption

2021-12-02 Thread Marco Patzer via ntg-context
On Mon, 29 Nov 2021 16:44:07 +0100 Marco Patzer via ntg-context wrote: > Why does ConTeXt not break the line between "unnecessary" and "FOO"? Any ideas how to fix this? Marco ___ If your

[NTG-context] Defining new float types fails in LMTX

2021-11-30 Thread Marco Patzer via ntg-context
Hi! Apologies for spamming this list with my all the floaty stuff. There's an issue with defining new floats in LMTX in combination with bottom placement. The following works in MkIV, but throws an error in LMTX: I'm ignoring this; it doesn't match any \if. mtx-context | fatal error:

Re: [NTG-context] Parameter order in float location matters

2021-11-30 Thread Marco Patzer via ntg-context
On Tue, 30 Nov 2021 14:05:23 +0100 Henning Hraban Ramm via ntg-context wrote: > Maybe you could define your own float type for the cases without > caption? I've done that for other options, too, I guess no-caption-floats get a dedicated float type as well now. It's more robust than relying on

[NTG-context] location=outer causes bad page break in LMTX

2021-11-30 Thread Marco Patzer via ntg-context
Hi! In the following example “Lorem ipsum” sits on an otherwise empty page in LMTX. Output is as expected with MkIV. Has the interface changed or may it be a bug in LMTX? \starttext \null\godown [15.5cm] \samplefile{knuth} Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod

Re: [NTG-context] Parameter order in float location matters

2021-11-30 Thread Marco Patzer via ntg-context
On Tue, 30 Nov 2021 13:06:00 +0100 Henning Hraban Ramm via ntg-context wrote: > Well, in {bottom,top,here} it’s the order that TeX should try. “location“ sets the location of the caption as well as the position of the entire float. If you want to influence one, you'll also have to specify the

[NTG-context] Parameter order in float location matters

2021-11-30 Thread Marco Patzer via ntg-context
Hi! Today I discovered that the parameter order in float location matters: \starttext \samplefile{knuth} \startplacefigure [location={top,none}] %% works: float is at the top \externalfigure \stopplacefigure \startplacefigure [location={none,top}] %% top is ignored here

[NTG-context] Bad linebreak in figure caption

2021-11-29 Thread Marco Patzer via ntg-context
Hi! The caption "FOO" runs into the right figure's caption: \setuplayout [width=18.4cm] \setuptolerance [verytolerant, stretch] %% even with stretch \starttext \startplacefigure \startfloatcombination \startplacefigure [title=Unexpectedly unnecessary FOO-BAR whatever]

Re: [NTG-context] Influence location of luametatex-cache

2021-11-29 Thread Marco Patzer via ntg-context
On Mon, 29 Nov 2021 12:07:51 +0100 Henning Hraban Ramm via ntg-context wrote: > > How to influence the location of the cache directory? > > Try to set TEXMFCACHE That's it. Thanks Peter and Henning. Marco ___ If

[NTG-context] Influence location of luametatex-cache

2021-11-29 Thread Marco Patzer via ntg-context
Hi! when LMTX is installed in a read-only location (e.g. /opt) it creates a directory "luametatex-cache" in $HOME. How to influence the location of the cache directory? Marco ___ If your question is of interest to

[NTG-context] Automatic counting groupsuffix for subfigures

2021-11-24 Thread Marco Patzer via ntg-context
Hi! I'd like to use subfigure numbering for floats. This works: \useMPlibrary [dum] \starttext \startplacefigure [location=none] \startfloatcombination [nx=2] \startplacefigure [title=Left, reference=ref:left, group=one, groupsuffix=a] \externalfigure \stopplacefigure

[NTG-context] Errors in source files return success

2021-11-18 Thread Marco Patzer via ntg-context
Hi! ConTeXt can detect issues in the sources and report them on the console with the argument --errors or with \enabledirectives [logs.errors]. The return value is still “0” (=success) even with errors present. Right now I use a script that parses the log file and lets me know if a run has

Re: [NTG-context] Space before/after combinations + centring

2021-11-17 Thread Marco Patzer via ntg-context
On Wed, 17 Nov 2021 20:17:52 +0100 Wolfgang Schuster wrote: > 2. There are no changes to adjust the vertical before and after a > combination environment. That's unfortunate. > Local patches can also be tricky because ConTeXt tries to freeze > the definitions of many user level commands which

[NTG-context] Space before/after combinations + centring

2021-11-17 Thread Marco Patzer via ntg-context
Hi! I'm in the process of converting some projects to LMTX. Combinations lacking “”before” and “after” keys (that place content before/after the *entire* combination, rather than the individual cell pairs), I came up with the following ugliness – which worked for longer than it deserved: