[NTG-context] Re: Is TIFF image no longer supported?

[Henning Hraban Ramm]

Am 14.04.24 um 22:25 schrieb Denis Maier via ntg-context:
Thomas A. Schmitz > hat am 14.04.2024 22:18 CEST 
geschrieben:

On 4/14/24 22:11, Joel via ntg-context wrote:

I have a document with PNG, JPG, and TIFF. When I try using
\externalfigure[filename][frame=on, width=.\textwidth] it displays
JPG and PNG fine, but the TIFF files don't render. Is TIFF not supported
in ConTeXt anymore? --Joel

I don't think tiff has ever be supported?
Thomas

At least, this is what
https://wiki.contextgarden.net/Using_Graphics says.
But you can do implicit conversion of TIFF to PDF if you have the 
converter installed. (Maybe you've had that installed before?)


EPS, BMP, GIF, TIFF (and in MkIV, SVG) are only supported via conversion.
For EPS you need GhostScript (gs), for SVG Inkscape, and GraphicsMagick 
(gm convert) for the others.


Hraban
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Re: Is TIFF image no longer supported?

[Denis Maier via ntg-context]

 
 
  
    
   
   
   
Thomas A. Schmitz  hat am 14.04.2024 22:18 CEST geschrieben:

   
 

   
 

   
On 4/14/24 22:11, Joel via ntg-context wrote:



 I have a document with PNG, JPG, and TIFF. When I try using
 

 \externalfigure[filename][frame=on, width=.\textwidth] it displays
 

 JPG and PNG fine, but the TIFF files don't render. Is TIFF not supported
 

 in ConTeXt anymore? --Joel
 

   
I don't think tiff has ever be supported?

   
 

   
Thomas

   
  
    
   
  
   At least, this is what 
   
  
   https://wiki.contextgarden.net/Using_Graphics says.
   
  
   But you can do implicit conversion of TIFF to PDF if you have the converter installed. (Maybe you've had that installed before?)
   
  
   Best,
   
  
   Denis
   
   
   
___

   
If your question is of interest to others as well, please add an entry to the Wiki!

   
 

   
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl

   
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)

   
archive : https://github.com/contextgarden/context

   
wiki : https://wiki.contextgarden.net

   
___

  
 

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Re: Is TIFF image no longer supported?

[Thomas A. Schmitz]

On 4/14/24 22:18, Thomas A. Schmitz wrote:




I don't think tiff has ever be supported?

Thomas


s/be/been/ Sorry!

Thomas
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Re: Is TIFF image no longer supported?

[Thomas A. Schmitz]

On 4/14/24 22:11, Joel via ntg-context wrote:
I have a document with PNG, JPG, and TIFF. When I try using 
\externalfigure[filename][frame=on, width=.\textwidth] it displays 
JPG and PNG fine, but the TIFF files don't render. Is TIFF not supported 
in ConTeXt anymore? --Joel


I don't think tiff has ever be supported?

Thomas
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Is TIFF image no longer supported?

[Joel via ntg-context]

I have a document with PNG, JPG, and TIFF. When I try using 
\externalfigure[filename][frame=on, width=.\textwidth] it displays JPG and 
PNG fine, but the TIFF files don't render. Is TIFF not supported in ConTeXt 
anymore? --Joel
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Re: Wiki - test/proposal to further clarify documentation

[Peter Hopcroft via ntg-context]

It would be great if the main page actually said what Context does. 

> On 15/04/2024, at 2:18 AM, Henning Hraban Ramm  wrote:
> 
> Hi Garulfo,
> 
> I’m not against the “new order”, but I’d keep the colorful subject tiles. 
> Different accesses are good IMO (as long as it doesn’t get to convoluted).
> 
> I’d say updating, sorting, restructuring pages is more important than a new 
> start page.
> 
> Yes, please sort out reference vs. tutorials!
> 
> Often examples make sense in the reference pages, so the distinction is a bit 
> fuzzy, but there are enough where a subject/tutorial page would make more 
> sense than examples spread over several single command pages.
> 
> We could also define if the “main” reference page (with examples) is 
> \definestuff, \setupstuff, or \stuff – IMO \setupstuff makes the most sense, 
> since usually the others inherit from it.
> 
> Often enough, parameters aren’t explained in the reference pages; sometimes 
> you can find examples using them, but there are too many holes. I tried to 
> fix that where I could, but too often I don’t understand enough of the 
> sources to make sense of some setting.
> 
> For wiki contributors, it might make sense to combine the markup pages – in 
> many pages e.g.  is used where  would make more 
> sense; often \starttext … \stoptext is not necessary and just blows up 
> examples; markup is generally somewhat chaotic (e.g. , , or ``?).
> 
> Hraban
> 
>> Am 14.04.24 um 13:21 schrieb garu...@azules.eu:
>> I just discover the Diátaxis documentation framework :
>> - https://www.diataxis.fr/
>> - 30min video : "What nobody tells you about documentation", 
>> https://www.youtube.com/watch?v=t4vKPhjcMZg  , from Daniele Procida at PyCon 
>> 2017
>> As I understand it, it can help both readers and writers of the 
>> documentation by clarifying the purpose of each element.
>> So I started a potential new "welcome page" :  
>> https://wiki.contextgarden.net/Main_Page2
>> The main lines would be :
>> - Tutorials: installation pages, step by step examples
>> - How-to guides: most of the existing wiki pages which are not 
>> https://wiki.contextgarden.net/Commands/ ...
>> - Discussions and manuals: most of the existing manuals
>> - Reference : the pages dedicated to commands which already include link to 
>> mailing list, stack exchange, ConTeXt's source
>>   - https://wiki.contextgarden.net/Category:Commands
>>   - https://wiki.contextgarden.net/Special:PrefixIndex?prefix=Command%2F
>> To match the logic of Diátaxis, maybe some material from command pages 
>> should be moved from "Reference" to "How-to guides",
>> for example, when the examples go beyond "pure description" and begin to 
>> deal with "how-to" cases, e.g. :
>> - Reference for setuphead: https://wiki.contextgarden.net/Command/setuphead
>> - How-to guides for headings: https://wiki.contextgarden.net/Titles
>> If it make sense, and according to your feedbacks, I can continue to 
>> reallocate existing contents.
>> Thanks for your feedback and thoughts.
>> Garulfo
>> ___
>> If your question is of interest to others as well, please add an entry to 
>> the Wiki!
>> maillist : ntg-context@ntg.nl / 
>> https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
>> webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
>> archive  : https://github.com/contextgarden/context
>> wiki : https://wiki.contextgarden.net
>> ___
> 
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / 
> https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
> archive  : https://github.com/contextgarden/context
> wiki : https://wiki.contextgarden.net
> ___
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Re: Wiki - test/proposal to further clarify documentation

[Henning Hraban Ramm]

Hi Garulfo,

I’m not against the “new order”, but I’d keep the colorful subject 
tiles. Different accesses are good IMO (as long as it doesn’t get to 
convoluted).


I’d say updating, sorting, restructuring pages is more important than a 
new start page.


Yes, please sort out reference vs. tutorials!

Often examples make sense in the reference pages, so the distinction is 
a bit fuzzy, but there are enough where a subject/tutorial page would 
make more sense than examples spread over several single command pages.


We could also define if the “main” reference page (with examples) is 
\definestuff, \setupstuff, or \stuff – IMO \setupstuff makes the most 
sense, since usually the others inherit from it.


Often enough, parameters aren’t explained in the reference pages; 
sometimes you can find examples using them, but there are too many 
holes. I tried to fix that where I could, but too often I don’t 
understand enough of the sources to make sense of some setting.


For wiki contributors, it might make sense to combine the markup pages – 
in many pages e.g.  is used where  would 
make more sense; often \starttext … \stoptext is not necessary and just 
blows up examples; markup is generally somewhat chaotic (e.g. , 
, or ``?).


Hraban

Am 14.04.24 um 13:21 schrieb garu...@azules.eu:

I just discover the Diátaxis documentation framework :
- https://www.diataxis.fr/
- 30min video : "What nobody tells you about documentation", 
https://www.youtube.com/watch?v=t4vKPhjcMZg  , from Daniele Procida at PyCon 2017

As I understand it, it can help both readers and writers of the documentation 
by clarifying the purpose of each element.

So I started a potential new "welcome page" :  
https://wiki.contextgarden.net/Main_Page2

The main lines would be :
- Tutorials: installation pages, step by step examples
- How-to guides: most of the existing wiki pages which are not 
https://wiki.contextgarden.net/Commands/ ...
- Discussions and manuals: most of the existing manuals
- Reference : the pages dedicated to commands which already include link to 
mailing list, stack exchange, ConTeXt's source
   - https://wiki.contextgarden.net/Category:Commands
   - https://wiki.contextgarden.net/Special:PrefixIndex?prefix=Command%2F

To match the logic of Diátaxis, maybe some material from command pages should be moved from 
"Reference" to "How-to guides",
for example, when the examples go beyond "pure description" and begin to deal with 
"how-to" cases, e.g. :
- Reference for setuphead: https://wiki.contextgarden.net/Command/setuphead
- How-to guides for headings: https://wiki.contextgarden.net/Titles

If it make sense, and according to your feedbacks, I can continue to reallocate 
existing contents.

Thanks for your feedback and thoughts.
Garulfo
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Re: Wiki - question about Command/ pages which start with a space character

[Wolfgang Schuster]

Henning Hraban Ramm schrieb am 14.04.2024 um 14:53:

Am 14.04.24 um 14:46 schrieb Wolfgang Schuster:

garu...@azules.eu schrieb am 14.04.2024 um 12:41:

Hi all,

Is it on purpose that 128 pages 
"https://wiki.contextgarden.net/Command/ " start with a 
space character ?

I didn't find an explanation in https://wiki.contextgarden.net/Command

For example, these two pages exist :
- https://wiki.contextgarden.net/Command/startbuffer
- https://wiki.contextgarden.net/Command/_startbuffer

If it is on purpose:
- What is the purpose, and which page should contain which 
documentation?


The command pages which start with an underscore are probably leftovers
when Taco changed a page from manual command descriptions to auto
generated tables.

In the process to change the page he makes a copy of the current page
with an underscore at the beginning which is deleted after the change
but it's possible he forgot to delete a few of them.

When you notice no difference between both versions of a command page
you can delete all of the forgotten pages.


No!

These are the general pages in opposite to instance pages, e.g. 
"startsection" and "startchapter" are instances of "_startsection"?


https://wiki.contextgarden.net/Command/_placefloat is the general page 
for the instances placefigure, placetable etc.


My bad, thank you for the correction!

Wolfgang

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Re: Wiki - question about Command/ pages which start with a space character

[Henning Hraban Ramm]

Am 14.04.24 um 14:46 schrieb Wolfgang Schuster:

garu...@azules.eu schrieb am 14.04.2024 um 12:41:

Hi all,

Is it on purpose that 128 pages 
"https://wiki.contextgarden.net/Command/ " start with a space 
character ?

I didn't find an explanation in https://wiki.contextgarden.net/Command

For example, these two pages exist :
- https://wiki.contextgarden.net/Command/startbuffer
- https://wiki.contextgarden.net/Command/_startbuffer

If it is on purpose:
- What is the purpose, and which page should contain which documentation?


The command pages which start with an underscore are probably leftovers
when Taco changed a page from manual command descriptions to auto
generated tables.

In the process to change the page he makes a copy of the current page
with an underscore at the beginning which is deleted after the change
but it's possible he forgot to delete a few of them.

When you notice no difference between both versions of a command page
you can delete all of the forgotten pages.


No!

These are the general pages in opposite to instance pages, e.g. 
"startsection" and "startchapter" are instances of "_startsection"?


https://wiki.contextgarden.net/Command/_placefloat is the general page 
for the instances placefigure, placetable etc.


Hraban
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Re: Wiki - question about Command/ pages which start with a space character

[Wolfgang Schuster]

garu...@azules.eu schrieb am 14.04.2024 um 12:41:

Hi all,

Is it on purpose that 128 pages "https://wiki.contextgarden.net/Command/ 
" start with a space character ?
I didn't find an explanation in https://wiki.contextgarden.net/Command

For example, these two pages exist :
- https://wiki.contextgarden.net/Command/startbuffer
- https://wiki.contextgarden.net/Command/_startbuffer

If it is on purpose:
- What is the purpose, and which page should contain which documentation?


The command pages which start with an underscore are probably leftovers
when Taco changed a page from manual command descriptions to auto
generated tables.

In the process to change the page he makes a copy of the current page
with an underscore at the beginning which is deleted after the change
but it's possible he forgot to delete a few of them.

When you notice no difference between both versions of a command page
you can delete all of the forgotten pages.

Wolfgang

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Wiki - test/proposal to further clarify documentation

[garulfo]

Hi all,

I just discover the Diátaxis documentation framework :
- https://www.diataxis.fr/
- 30min video : "What nobody tells you about documentation", 
https://www.youtube.com/watch?v=t4vKPhjcMZg  , from Daniele Procida at PyCon 
2017

As I understand it, it can help both readers and writers of the documentation 
by clarifying the purpose of each element.

So I started a potential new "welcome page" :  
https://wiki.contextgarden.net/Main_Page2

The main lines would be :
- Tutorials: installation pages, step by step examples
- How-to guides: most of the existing wiki pages which are not 
https://wiki.contextgarden.net/Commands/ ...
- Discussions and manuals: most of the existing manuals
- Reference : the pages dedicated to commands which already include link to 
mailing list, stack exchange, ConTeXt's source
  - https://wiki.contextgarden.net/Category:Commands
  - https://wiki.contextgarden.net/Special:PrefixIndex?prefix=Command%2F

To match the logic of Diátaxis, maybe some material from command pages should 
be moved from "Reference" to "How-to guides",
for example, when the examples go beyond "pure description" and begin to deal 
with "how-to" cases, e.g. :
- Reference for setuphead: https://wiki.contextgarden.net/Command/setuphead
- How-to guides for headings: https://wiki.contextgarden.net/Titles

If it make sense, and according to your feedbacks, I can continue to reallocate 
existing contents.

Thanks for your feedback and thoughts.
Garulfo
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Wiki - question about Command/ pages which start with a space character

[garulfo]

Hi all,

Is it on purpose that 128 pages "https://wiki.contextgarden.net/Command/ 
" start with a space character ?
I didn't find an explanation in https://wiki.contextgarden.net/Command

For example, these two pages exist :
- https://wiki.contextgarden.net/Command/startbuffer
- https://wiki.contextgarden.net/Command/_startbuffer

If it is on purpose: 
- What is the purpose, and which page should contain which documentation?

If it is not: 
- Is there a way to automatically merge the content of the couple of pages, and 
to remove the "wrong" pages, or should it be done manually ?

Thanks for your help.

List :
Command/ attachment
Command/ background
Command/ bar
Command/ beginblock
Command/ button
Command/ characterkerning
Command/ comment
Command/ completecombinedlist
Command/ completelistoffloats
Command/ completelistofsorts
Command/ completelistofsynonyms
Command/ completeregister
Command/ copylabeltext
Command/ ctxfunction
Command/ ctxfunctiondefinition
Command/ currentlabel
Command/ delimitedtext
Command/ description
Command/ enumeration
Command/ fence
Command/ fraction
Command/ framed
Command/ framedtext
Command/ getbuffer
Command/ hbox
Command/ help
Command/ high
Command/ highlight
Command/ label
Command/ labellanguage
Command/ labeltext
Command/ labeltexts
Command/ language
Command/ leftlabeltext
Command/ linenote
Command/ low
Command/ lowhigh
Command/ lowmidhigh
Command/ margindata
Command/ mathcommand
Command/ mathdoubleextensible
Command/ mathextensible
Command/ mathframed
Command/ mathmatrix
Command/ mathornament
Command/ mathoverextensible
Command/ mathovertextextensible
Command/ mathradical
Command/ mathtriplet
Command/ mathunderextensible
Command/ mathundertextextensible
Command/ mathunstacked
Command/ nextparagraphs
Command/ note
Command/ ornament
Command/ paragraphs
Command/ placecombinedlist
Command/ placefloat
Command/ placelistoffloats
Command/ placelistofsorts
Command/ placelistofsynonyms
Command/ placement
Command/ placepairedbox
Command/ placeregister
Command/ presetlabeltext
Command/ referenceformat
Command/ register
Command/ rightlabeltext
Command/ script
Command/ section
Command/ seeregister
Command/ setupcombinedlist
Command/ setupitemgroup
Command/ setuplabeltext
Command/ setuppairedbox
Command/ setupregister
Command/ shift
Command/ sorting
Command/ startattachment
Command/ startbackground
Command/ startbuffer
Command/ startcolumnset
Command/ startcomment
Command/ startdelimitedtext
Command/ startdescription
Command/ starteffect
Command/ startenumeration
Command/ startfittingpage
Command/ startfloattext
Command/ startformula
Command/ startframedtext
Command/ starthelp
Command/ startindentedtext
Command/ startitemgroup
Command/ startlabeltext
Command/ startlinenote
Command/ startlines
Command/ startmakeup
Command/ startmathalignment
Command/ startmathcases
Command/ startmathmatrix
Command/ startmixedcolumns
Command/ startnarrower
Command/ startnote
Command/ startpagecolumns
Command/ startparagraphs
Command/ startparallel
Command/ startplacefloat
Command/ startplacepairedbox
Command/ startsection
Command/ startsectionblock
Command/ startstartstop
Command/ startstop
Command/ startstyle
Command/ starttabulate
Command/ starttextbackground
Command/ starttyping
Command/ startviewerlayer
Command/ startxtable
Command/ stoplinenote
Command/ style
Command/ synonym
Command/ textbackground
Command/ textnote
Command/ tooltip
Command/ type
Command/ typebuffer
Command/ unit
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Re: Most recent context doesn't like synctex?

[Henning Hraban Ramm]

Am 13.04.24 um 22:28 schrieb Mikael Sundqvist:

What will work will depend on the viewers. We noticed a few weeks ago
that synctex (pdf -> editor) was not working in a few viewers (okular)
while it was working in others. 


Could you please tell us which combinations of viewers and editors you 
checked and how to configure them to make it work?


Hraban

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___

[NTG-context] Re: unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua

[Martin Hasoň]

Hi Denis,

I made a similar solution for docker image [minidocks/context](https://hub.docker.com/r/minidocks/context):
[https://github.com/minidocks/context/commit/9b3ccc1eb62e556cada29b5b761207a526bca52e](https://github.com/minidocks/context/commit/9b3ccc1eb62e556cada29b5b761207a526bca52e).

You can get inspired. Everything works as it should:

```
$ docker run --rm -it minidocks/context --luatex --version  
resolvers   | globbing | confusing filename, name: 'CHANGELOG.md', lower: 'changelog.md', already: 'ChangeLog.md'  
mtx-context | redirect luametatex -> luatex: luatex --luaonly --socket "/usr/share/tex/texmf/bin/mtxrun.lua" --script mtx-context --luatex --version --redirected  
resolvers   | globbing | confusing filename, name: 'CHANGELOG.md', lower: 'changelog.md', already: 'ChangeLog.md'  
mtx-context | ConTeXt Process Management 1.06  
mtx-context |  
mtx-context | main context file: /usr/share/tex/texmf-context/tex/context/base/mkiv/context.mkiv  
mtx-context | current version: 2024.04.01 08:59  
mtx-context | main context file: /usr/share/tex/texmf-context/tex/context/base/mkxl/context.mkxl  
mtx-context | current version: 2024.04.01 08:59
```

Best,

Martin Hasoň
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___