Am 13.08.25 um 15:22 schrieb Denis Maier via ntg-context:
I imagine you should be able to keep track of the footnotes in a lua table
(just like shown in the xml-mkiv manual) and place them manually with
\placefootnotes where you want.
Something like this:
\setupfootnotes[location=text
Hi Thomas,
You know more about XML processing than I do, but how does your project
setup look like?
I imagine you should be able to keep track of the footnotes in a lua table
(just like shown in the xml-mkiv manual) and place them manually with
\placefootnotes where you want.
Something like
Am 10.08.25 um 21:28 schrieb Hans Hagen via ntg-context:
On 8/10/2025 9:09 PM, Hraban Ramm wrote:
What’s the difference between table.tofile and table.save? tofile is
documented in cld-mkiv* while save is not. table.save is also not
mentioned in the Lua reference manual. Where does it come
On 8/10/2025 9:09 PM, Hraban Ramm wrote:
What’s the difference between table.tofile and table.save? tofile is
documented in cld-mkiv* while save is not. table.save is also not
mentioned in the Lua reference manual. Where does it come from?
just look at the files ...
as all lua code in
found http://lua-users.org/wiki/SaveTableToFile
Is there already something (better) in ConTeXt? I'd assume, since
the functionality is needed for tuc files?
table.tofile("my_file.lua",my_table)
Thank you, I overlooked that in cld-mkiv, since I was looking for
table.save (which was
/SaveTableToFile
Is there already something (better) in ConTeXt? I'd assume, since the
functionality is needed for tuc files?
table.tofile("my_file.lua",my_table)
Thank you, I overlooked that in cld-mkiv, since I was looking for
table.save (which was mentioned in a thread about Ecir Baff’s
ConTeXt? I'd assume, since the
functionality is needed for tuc files?
table.tofile("my_file.lua",my_table)
Thank you, I overlooked that in cld-mkiv, since I was looking for
table.save (which was mentioned in a thread about Ecir Baff’s art).
And for reading context.runfile, r
catcode regimes, and these
vectors have plugins for active characters (think for instance
interpreting xml)
- in mkiv we use catcode tables (which are an engine feature brought in
at the start modelled after what context mkii liked) and again we
provide some plugin mechanism in context (mki
;$SELFAUTOPARENT/texmf-dist/"), but I have no idea how to do that.
> > Also, can you please rename m-texlive.mkxl to m-texlive.mkiv? LuaTeX
> > doesn't find the file with the ".mkxl" suffix, and I'd like to keep
> > supporting MkIV in TeX Live.
>
> hm
er for context which
leaves out complete subtrees. The file database isn't generated that
often, it's access during a run that matters more.
Also, can you please rename m-texlive.mkxl to m-texlive.mkiv? LuaTeX
doesn't find the file with the ".mkxl" suffix, and I'd like t
aTeX
doesn't find the file with the ".mkxl" suffix, and I'd like to keep
supporting MkIV in TeX Live.
Thanks,
-- Max
diff --git a/tex/context/base/mkiv/data-fil.lua
b/tex/context/base/mkiv/data-fil.lua
index 8dbc8a0..1f7ff94 100644
--- a/tex/context/base/mkiv/data-fil.lua
+++
nd the LMTX standalone distribution with all
modules installed is 479MB (including documentation), TeX Live with
scheme-context (which includes MkII, MkIV, and MkXL, all the modules,
but no documentation) is 514MB, and TL with scheme-infraonly and the
"context" package (MkXL only, without MkIV, a
On 7/12/2025 6:56 PM, Henning Hraban Ramm wrote:
Am 12.07.25 um 10:12 schrieb Max Chernoff:
Hi Hraban,
On Fri, 2025-07-11 at 09:39 +0200, Henning Hraban Ramm wrote:
the ConTeXt dockerfiles from “Island of TeX”
(https://github.com/islandoftex/context) …
– still distinguish MkIV beta/current
Am 12.07.25 um 10:12 schrieb Max Chernoff:
Hi Hraban,
On Fri, 2025-07-11 at 09:39 +0200, Henning Hraban Ramm wrote:
the ConTeXt dockerfiles from “Island of TeX”
(https://github.com/islandoftex/context) …
– still distinguish MkIV beta/current
– install modules via rsync also for LMTX which
Hi Hraban,
On Fri, 2025-07-11 at 09:39 +0200, Henning Hraban Ramm wrote:
> the ConTeXt dockerfiles from “Island of TeX”
> (https://github.com/islandoftex/context) …
> – still distinguish MkIV beta/current
> – install modules via rsync also for LMTX which pulls in some outdated ones
&g
Hi, esp. Max:
the ConTeXt dockerfiles from “Island of TeX”
(https://github.com/islandoftex/context) …
– still distinguish MkIV beta/current
– install modules via rsync also for LMTX which pulls in some outdated ones
– use Debian instead of Alpine because Linux/MUSL binary wasn’t working
at
]
\dorecurse{25}{\chapter{Chapter \recurselevel}}
\stoptext
It is a LMTX issue only, since MkIV works fine.
Line 527 from strc-lst.mkxl introduces a \normaldef in current latest
(2025.07.07 23:34). Before there was only a \def.
This apparently fixes the issue for me, but I have no idea whether this
s a LMTX issue only, since MkIV works fine.
Line 527 from strc-lst.mkxl introduces a \normaldef in current latest
(2025.07.07 23:34). Before there was only a \def.
This apparently fixes the issue for me, but I have no idea whether this
is the right way to do it.
Hans, could you confirm whether t
:
token call, execute:
...m64/tex/texmf-context/tex/context/base/mkxl/mlib-msh.lmt:45: attempt
to index a nil value (local 'contour')
stack traceback:
...m64/tex/texmf-context/tex/context/base/mkxl/mlib-msh.lmt:45: in local
'code'
...m64/tex/texmf-context/tex/context/base/mk
%%% end example
For those interested: you can run
context s-system-macros.mkxl
and see what is there and how macros are classified. The top of the file
says:
%D This file is for Wolfgang and Hans and it's used in the transition
%D from \MKIV\ to the more robust \LMTX.
which tells a
Administrator\Downloads\context-win64\tex\texmf-context\tex\context\test\mkiv
>
>
> resolvers | formats | executing runner 'run luametatex format':
> luametatex --jobname="./context-test.tex" --socket --shell-escape
> --fmt=C:/texlive/2025/texmf-var/luam
I installed TeXlive 2025, and today I did a new installation of
> ConText.
>
> After compiling the context.test today , I got:
>
>
> Command Line: context.exe --synctex=-1 "context-test.tex"
> Startup Folder:
> C:\Users\Administrator\Downloads
context.test today , I got:
Command Line: context.exe --synctex=-1 "context-test.tex"
Startup Folder:
C:\Users\Administrator\Downloads\context-win64\tex\texmf-context\tex\context\test\mkiv
resolvers | formats | executing runner 'run luametatex format':
luametatex
On 7/2/2025 6:11 AM, Max Chernoff via ntg-context wrote:
Hi Hans,
If you use "\show" anywhere in a document with MkIV, ConTeXt treats it
as a fatal error and immediately exits. The following document produces
the expected output with MkXL, but exits with "mtx-context | fatal
e
Hi Hans,
If you use "\show" anywhere in a document with MkIV, ConTeXt treats it
as a fatal error and immediately exits. The following document produces
the expected output with MkXL, but exits with "mtx-context | fatal
error" with MkIV:
\show\show
\showtokens{\showtok
; checks > registering extra script 'auto'
> > fonts > preloading latin modern fonts (second stage)
> > fonts > 'fallback modern rm 12pt' is loaded
> > backend > profiles > setting format 'pdf/ua-2' to 'pdf
rofiles > forcing pdf version 2.0, compression level
3, object compression level 3
backend > profiles > permitted colorspaces: rgb 'yes', cmyk 'yes'
colors > defining > supported models: gray 'true', rgb 'true',
cmyk 't
ct compression level 3
backend > profiles > permitted colorspaces: rgb 'yes', cmyk 'yes'
colors > defining > supported models: gray 'true', rgb 'true',
cmyk 'true', spot 'true'
transparencies > support > tran
er cases or not, I’m afraid I don’t
have the knowledge to distinguish their cause.
> (btw, I fix issues in lmtx and only occasionally backport to mkiv.)
MkIV? I only use it nowadays to check that LMTX isn’t misbehaving.
The moment I started using tw and th (and similar) as dimension units,
there
pe
whether they have any publicly accessible reference used for their
implementation.
They probably use some library. And then there is of course the issue of
bugs that became standards (as happened with some in pdf).
(btw, I fix issues in lmtx and only occasionally backport to mk
x27;t quite work (the second column is shifted a line
>> down from the first column - but I guess there's something I should have
>> set up initially to get it to work).
>>
>> It's not the definition of \yogh that would cause me any difficulty, but
>> the fact t
down from the first column - but I guess there's something I should have
> set up initially to get it to work).
>
> It's not the definition of \yogh that would cause me any difficulty, but
> the fact that I can't say:
>
> \defʒ
>
>
\def\MyHello{Hello!}
\def\d
)}]
\setuppagenumbering[location=,]
\starttext
\null
\stoptext
With two different installation I get this:
A
current version: 2025.06.12 14:21
backend > xmp > using file
'/home/juh/juh.context.20241101/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.x
Am 02.06.25 um 15:45 schrieb Matthias Weber:
Thank you Wolfgang. A fresh install fixed my initial problems.
mtxrun --script mtx-epub --make --purge epub-mkiv-demo
produces an epub. However, both Calibre and Thorium have trouble with it (not
displaying anything but error messages).
Are there
Thank you Wolfgang. A fresh install fixed my initial problems.
mtxrun --script mtx-epub --make --purge epub-mkiv-demo
produces an epub. However, both Calibre and Thorium have trouble with it (not
displaying anything but error messages).
Are there any steps I need to follow to create a
t minimal, so I think I have everything
Matthias
> On May 30, 2025, at 12:21 PM, Wolfgang Schuster
> wrote:
>
> Am 29.05.2025 um 22:54 schrieb Matthias Weber:
>> Hi,
>> I am trying to export to epub. I found epub-mkiv-demo.tex and
>> export-example.tex, and bo
Am 29.05.2025 um 22:54 schrieb Matthias Weber:
Hi,
I am trying to export to epub. I found epub-mkiv-demo.tex and
export-example.tex, and both compile fine, generating the XML tree. The
instructions say that I have to run
mtxrun --script epub --make --purge test
but I get unknown script
Hi,
I am trying to export to epub. I found epub-mkiv-demo.tex and
export-example.tex, and both compile fine, generating the XML tree. The
instructions say that I have to run
mtxrun --script epub --make --purge test
but I get unknown script ‘epub.lua’. I don’t have epub.lua anywhere.
It
:
\setupbackend
[format={pdf/a-2a},
profile={default_cmyk.icc,default_rgb.icc,default_gray.icc}]
\setuptagging
[state=start]
\enabledirectives
[backend.usetags=mkiv]
Specification: ISO 19005-2:2011, Clause: 6.2.4.3, Test number: 3
DeviceCMYK shall only be used if a device independent DefaultCMYK
]
\enabledirectives
[backend.usetags=mkiv]
Specification: ISO 19005-2:2011, Clause: 6.2.4.3, Test number: 3
DeviceCMYK shall only be used if a device independent DefaultCMYK colour
space has been set or if a DeviceN-based DefaultCMYK colour space has
been set when the DeviceCMYK colour
ucceeded in integrating the provided extension schema.
Just modifying a local copy of mkiv/lpdf-pua.xml seems to do it. (There
is no separate equivalent in the mkxl tree, so this is used for both.)
Both sets of changes (the extension schema and the actual setting
On 4/30/25 00:04, Mohammad Hossein Bateni wrote:
> Hello,
>
> I think the following used to place the footnote rule on the right side
> (as in rule=right). Now it doesn't.
Hi Mohammad,
I can confirm that with your source MkIV (LuaTeX 1.23 7679 + ConTeXt
MkIV 2025.04.28 14:29) p
Dear list,
I have the following sample:
\startbuffer[x]
a
\stopbuffer
\starttext
\savebuffer[x][\jobname-temp.tex, prefix=no]
whatever
\stoptext
Compiling it with current latest (2025.04.01 12:45) LMTX, the saved file
name is "x".
With current latest MkIV,
fonts are implemented like traditional tex fonts. This
makes math in the engine behave like xetex. The primitives that relate
to controling some aspects of math rendering are obsolete (we also
removed experimental additional italics mode code). This change doesn't
affect ConTeXt (MkIV) be
tx-context | main context file:
> /home/userland/lmtx/tex/texmf-context/tex/context/base/mkiv/context.mkiv
> mtx-context | current version: 2025.02.28 18:16
> mtx-context | main context file:
> /home/userland/lmtx/tex/texmf-context/tex/context/base/mkxl/context.mkxl
&g
Hi Jim,
it works here with your cow-jp2.jp2 without problems with:
┌──(userland㉿localhost)-[~]
└─$ context --version
mtx-context | ConTeXt Process Management 1.06
mtx-context |
mtx-context | main context file:
/home/userland/lmtx/tex/texmf-context/tex/context/base/mkiv/context.mkiv
t; level 1, order 2, name './P.CODE_CLIENT_(COUNTRY)_Rev.C..tex'
open source > level 2, order 3, name '.\\TEX\\00-CONFIG\\config.tex'
close source> level 2, order 3, name '.\\TEX\\00-CONFIG\\config.tex'
open source > level 2, order 4, name '.\\TEX\\
On 2025-03-09 08:12, Bruce Horrocks wrote:
On 7 Mar 2025, at 23:07, Rik Kabel wrote:
I am stumped trying to eliminate the extra vertical space in the following
example. Can anybody point out where it is coming from and, more importantly,
how to eliminate it. All lines should be on the grid, bu
> On 7 Mar 2025, at 23:07, Rik Kabel wrote:
>
> I am stumped trying to eliminate the extra vertical space in the following
> example. Can anybody point out where it is coming from and, more importantly,
> how to eliminate it. All lines should be on the grid, but the paragraphs
> environment c
environment clearly is introducing extra space (or
removing it). I do note that the problem exists with MkIV and LMTX not
giving the same result, but with neither setting on the grid.
[...]
The paragraphs environment is something like a light version of natural
tables or extreme tables rather than a
removing it). I do note that the problem exists with MkIV and LMTX not
giving the same result, but with neither setting on the grid.
\setuplayout [grid=on]
\showgrid
\defineparagraphs[TwoCols]
[n=2]
\setupparagraphs[TwoCols]
[each
On 3/5/25 05:23, Max Chernoff via ntg-context wrote:
> Hi Pablo,
Hi Max,
many thanks for your reply.
> Not quite what you're asking for, but the "compare" script does
> something fairly similar:
> [...]
> The source for that script is in
>
> tex/conte
t | Cmtx-context | ConTeXt Process Management
> > 1.06mtx-context |
> > mtx-context | main context file:
> > /usr/local/share/context/tex/texmf-
> > context/tex/context/base/mkiv/context.mkiv
> > mtx-context | current version: 2025.02.28 18:16
> > mtx-c
off for
the included streams
xml-mkiv.pdf268.614
one.pdf 328,094
two.pdf 1,206,034
after fixing this here (mkxl):
one.pdf 328,093
two.pdf 369,055
btw, --luatex (mkiv) gives:
one.pdf 413.981
two.pdf 499.895
processing xml-mkiv in lmtx actually
hat you're asking for, but the "compare" script does
something fairly similar:
$ context --extra=compare .pdf .pdf
$ context --extra=compare .pdf .pdf
--colors=red,blue --result=.pdf
The source for that script is in
tex/context/base/mkiv/mtx-context-compare.tex
so mayb
t | Cmtx-context | ConTeXt Process Management
> > 1.06mtx-context |
> > mtx-context | main context file:
> > /usr/local/share/context/tex/texmf-
> > context/tex/context/base/mkiv/context.mkiv
> > mtx-context | current version: 2025.02.28 18:16
> > mtx-c
mtx-context | Cmtx-context | ConTeXt Process Management 1.06mtx-context
|
mtx-context | main context file:
/usr/local/share/context/tex/texmf-
context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2025.02.28 18:16
mtx-context | main
Process Management 1.06mtx-context
|
mtx-context | main context file:
/usr/local/share/context/tex/texmf-
context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2025.02.28 18:16
mtx-context | main context file:
/usr/local/share/context/tex/texmf-
context/tex/context
d Ancient Greek patterns don’t interfere with each other
> -- and in any case the example with only the Greek patterns is already
> incorrect.
I think I (partially) discovered what is misbejaving here.
In lang-def.{mkxl|mkiv}, ancient Greek is defined:
\installlanguage
[\s!agr]
[\s!d
27;changelog.md', already: 'ChangeLog.md'
mtx-context | ConTeXt Process Management 1.06
mtx-context |
mtx-context | main context file:
/home/vm/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2025.02.24 16:28
mtx-context
On 2/20/2025 12:21 PM, Max Chernoff via ntg-context wrote:
\pi doesn't seem to be defined in MkIV anymore. I'm using the latest
from the standalone distribution, although the issue is also present in
the TL25 pretest. Minimal example:
% engine=luatex
\startTEXpage
Hi Hans,
\pi doesn't seem to be defined in MkIV anymore. I'm using the latest
from the standalone distribution, although the issue is also present in
the TL25 pretest. Minimal example:
% engine=luatex
\startTEXpage
\m{\pi}
\stopTEXpage
This was originally reported
},
]
\setuptagging
[state=start]
\enabledirectives
[backend.usetags=mkiv]
\starttext
a
\stoptext
is green with VeraPDF!
Many thanks for your testing, Thomas.
format={pdf/ua-2} is not defined I think, see: https://
source.contextgarden.net/tex/context/base/mkiv/lpdf-fmt.lua
It’s
On 2/16/25 11:09, Thomas Meyer wrote:
> \setupbackend[
> format={pdf/ua-1},
> profile={default_rgb.icc,default_gray.icc},
> ]
>
> \setuptagging
> [state=start]
>
> \enabledirectives
> [backend.usetags=mkiv]
>
> \starttext
> a
> \stoptext
>
&
\setupbackend[
format={pdf/ua-1},
profile={default_rgb.icc,default_gray.icc},
]
\setuptagging
[state=start]
\enabledirectives
[backend.usetags=mkiv]
\starttext
a
\stoptext
is green with VeraPDF!
format={pdf/ua-2} is not defined I think, see:
https://source.contextgarden.net/tex
checked some
>>> validators didn't like it and viewerd didn't do anything useful with it so
>>> ity made no sense to waste more time on it.
>>>
>>> Just putting stuff in a pdf for the sake of having something is is tricky
>>> because who kn
d chatbots can interpret an
untagged pdf quite well so we'll see.
That said: we have tagging in mkiv ... no one really cared that much (no
tools that use them) ... and in mkxl we updated it a bit (still no
tools) only to find out that tagged pdf (and the standard) has become
fluid, seems
ck traceback:
...ext/tex/texmf-context/tex/context/base/mkxl/node-ini.lmt:214: in
metamethod 'index'
...ext/tex/texmf-context/tex/context/base/mkxl/supp-box.lmt:37: in
local 'code'
...ext/tex/texmf-context/tex/context/base/mkiv/util-lua.lua:97: in
field 'loadedluacode'
.
ue (global 'mathematics')
stack traceback:
...ext/tex/texmf-context/tex/context/base/mkxl/node-ini.lmt:214: in
metamethod 'index'
...ext/tex/texmf-context/tex/context/base/mkxl/supp-box.lmt:37: in
local 'code'
...ext/tex/te
thematics')
> >stack traceback:
> >...ext/tex/texmf-context/tex/context/base/mkxl/node-ini.lmt:214:
> > in metamethod 'index'
> >...ext/tex/texmf-context/tex/context/base/mkxl/supp-box.lmt:37:
> > in local 'code'
> >
ase/mkxl/node-ini.lmt:214: in
metamethod 'index'
...ext/tex/texmf-context/tex/context/base/mkxl/supp-box.lmt:37: in
local 'code'
...ext/tex/texmf-context/tex/context/base/mkiv/util-lua.lua:97: in
field 'loadedluacode'
...ext/tex/texm
;
...ext/tex/texmf-context/tex/context/base/mkxl/supp-box.lmt:37: in
local 'code'
...ext/tex/texmf-context/tex/context/base/mkiv/util-lua.lua:97: in
field 'loadedluacode'
...ext/tex/texmf-context/tex/context/base/mkiv/luat-env.lua:108: in
field &#x
76fb1556f32e/fonts/otl/latinmodernmathcompanion-regular.tma'
into
'/Users/wolfrum/context-osx-arm64/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/latinmodernmathcompanion-regular.tmd'
stripped
fonts > otf loading > loading, optimizing,
ts (second stage)
fonts > 'fallback modern rm 12pt' is loaded
structure > sectioning > section @ level 3 : 0.0.1 -> test
pages > flushing realpage 1, userpage 1, subpage 1
close source> level 1, order 2, name './placelist_test.tex'
bac
$3+2=5 \quad \bf 3+2=5$
> \stoptext
The logs contain the following, which shows dejavusansmono is not loaded.
mkiv lua stats > loaded fonts: 3 files: texgyredejavu-math.otf,
> dejavuserif-bold.ttf, dejavuserif.ttf
IIUC one issue is that setupbodyfont kind of undoes the usetypescript
command b
\definefontfamily.
I’m experiencing this with LMTX only (MkIV is fine). I’m using current
latest (2025.02.07 20:46).
Could anyone confirm the issue?
I can't reproduce the error and the following works as intended.
\enableexperiments [fonts.compact]
\definefallbackfamily [mainface] [rm] [Dejavu
}]
\setupbodyfont [mainface]
\starttext
αβγ9 some word others\\
\sl αβγ9 some word others
\stoptext
The only way to get slanted Greek is either with disabled compact fonts,
or with fake slanted added to \definefontfamily.
I’m experiencing this with LMTX only (MkIV is fine). I’m using
Maybe:
https://source.contextgarden.net/tex/context/fonts/mkiv/?search=type-imp-
https://github.com/contextgarden/context/tree/main/tex/context/fonts/mkiv
___
If your question is of interest to others as well, please
mf-context/tex/context/base/mkxl/file-mod.lmt:78: attempt to
> call a nil value (field 'getrunstate')
> stack traceback:
> ...ext/tex/texmf-context/tex/context/base/mkxl/file-mod.lmt:78: in local
> 'code'
> ...ext/tex/texmf-context/tex/context/base/mkiv
>
> Startup Folder:
> C:\Users\Hermann\Downloads\context-win64\tex\texmf-context\tex\context\test\mkiv
>
>
>
>
>
> resolvers | formats | executing runner 'run luametatex format':
> luametatex --jobname="./item.tex" --socket --shell-escape
> -
:
C:\Users\Hermann\Downloads\context-mswin\tex\texmf-mswin\bin\context.exe
--synctex=-1 "item"
Startup Folder:
C:\Users\Hermann\Downloads\context-win64\tex\texmf-context\tex\context\test\mkiv
resolvers | formats | executing runner 'run luametatex format':
luametatex -
eld 'getrunstate')
stack traceback:
...ext/tex/texmf-context/tex/context/base/mkxl/file-mod.lmt:78: in
local 'code'
...ext/tex/texmf-context/tex/context/base/mkiv/util-lua.lua:97: in
field 'loadedluacode'
...ext/tex/texmf-context/tex/context/base/mkiv/luat-en
In my (non-TeXlive) ConTeXt installation, I've found the file:
$HOME/context/tex/texmf-context/tex/context/base/mkiv/util-jsn.lua
and added the changes you mentioned (so the end of the file now is):
package.loaded["util-jsn"] = json
package.loaded.json= json
return js
:
2024.12.30 16:14 LMTX fmt: 2025.1.24 int: english/english), I am hiting this
error:
```
token call, execute:
...ext/tex/texmf-context/tex/context/base/mkiv/util-sql.lua:91: attempt to
index a boolean value (local 'json')
stack traceback:
...ext/tex/texmf-context/tex/context
/english), I am hiting this
error:
```
token call, execute:
...ext/tex/texmf-context/tex/context/base/mkiv/util-sql.lua:91: attempt to
index a boolean value (local 'json')
stack traceback:
...ext/tex/texmf-context/tex/context/base/mkiv/util-sql.lua:91: in main
chunk
[C]:
tex', result
'./slide'
fonts > latin modern fonts are not preloaded
languages > language 'en' is active
open source > level 1, order 3, name './slide.tex'
open source > level 2, order 4, name 'env-slides.tex'
open source
On 1/17/2025 2:42 AM, wangzhongtian wrote:
hi, hans
when building following code( also attached) using context
(2024-11-01),lmtx will report an error. Is it a problem?
when change line 2596 of mkiv/publ-ini.lua from
local internal = specification.internal or ""
to
loca
hi, hanswhen building following code( also attached) using context (2024-11-01),lmtx will report an error. Is it a problem?when change line 2596 of mkiv/publ-ini.lua from local internal = specification.internal or ""tolocal internal = specification.internal or 0, all is ok.\define
On 1/13/2025 9:59 PM, garu...@azules.eu wrote:
Hi all,
With Debian, I created a /bin/mudraw
$ cat /bin/mudraw
#!/bin/sh
mutool draw "$@"
trying to compile the demo file:
context epub-mkiv-demo.tex
mtxrun --script epub --images epub-mkiv-demo.tex
mtxrun --script epub --make epub
makes them optional,
not their definition/fencing?
indeed, you could also do
\tolerant\def\foo(#1){...}
With \tolerant, we can not only forget about the last dodos (and even
single dos), but also about \dosingleargument & friends, right?
Are there cases where the MkIV way still makes s
parameters is just
a convention, i.e. only the handling of arguments makes them optional,
not their definition/fencing?
With \tolerant, we can not only forget about the last dodos (and even
single dos), but also about \dosingleargument & friends, right?
Are there cases where the MkIV way still m
Hi all,
With Debian, I created a /bin/mudraw
$ cat /bin/mudraw
#!/bin/sh
mutool draw "$@"
trying to compile the demo file:
context epub-mkiv-demo.tex
mtxrun --script epub --images epub-mkiv-demo.tex
mtxrun --script epub --make epub-mkiv-demo
the demo stopped just after by trying t
Hi Hans,
On Sat, Jan 11, 2025 at 11:48 (+0100), Hans Hagen wrote:
> On 1/11/2025 1:47 AM, Jim wrote:
>> Hi,
>> in .../tex/texmf-context/tex/context/base/mkiv/grph-inc.lua I see (at line
>> 333)
>> ["jp2"]= { list = { "jp2" }
On 1/11/2025 1:47 AM, Jim wrote:
Hi,
in .../tex/texmf-context/tex/context/base/mkiv/grph-inc.lua I see (at line
333)
["jp2"]= { list = { "jp2" } },
That is (AIUI) the proper extension for JPEG2000 (Part 1) images.
The JPEG2000 (Part 2) images I looked at
Hi,
in .../tex/texmf-context/tex/context/base/mkiv/grph-inc.lua I see (at line
333)
["jp2"]= { list = { "jp2" } },
That is (AIUI) the proper extension for JPEG2000 (Part 1) images.
The JPEG2000 (Part 2) images I looked at have the same magic bytes as
listed
!
Julius
context --version
mtx-context | ConTeXt Process Management 1.06
mtx-context |
mtx-context | main context file:
/Users/juliusross/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2024.11.01 19:19
mtx-context | main context file
: [172
29 80] n=3
otf reader > fatal error in file
'/home/florent/.local/share/fonts/SourceCodeVF-Upright.otf':
/home/florent/lmtx/tex/context/base/mkxl/font-cff.lmt:1956: attempt to
perform arithmetic on a nil value (field '?')
stack traceback:
/home/florent/lmtx/tex/context
ards,
lua error > lua error on line 18 in file file-mod.mklx:
token call, execute:
...ext/tex/texmf-context/tex/context/base/mkxl/file-mod.lmt:78: attempt to call
a nil value (field 'getrunstate')
stack traceback:
...ext/tex/texmf-context/tex/context/base/mkxl/file-mod
line 105) it looks like it was
something introduced to deal with an issue in mkiv that no longer applies? Hard
to tell without comparing both versions in detail. I can't create a test
example that shows a difference.
* In my notes, I found the remark that "between" items should be anch
c-lst.mkxl (line 105) it looks like it was
something introduced to deal with an issue in mkiv that no longer applies? Hard
to tell without comparing both versions in detail. I can't create a test
example that shows a difference.
> * In my notes, I found the remark that "between&quo
1 - 100 of 1384 matches
Mail list logo
