/base/mkiv/context.mkiv
mtx-context | current version: 2021.05.20 16:06
mtx-context | main context file:
/home/vm/context/tex/texmf-context/tex/context/base/mkxl/context.mkxl
mtx-context | current version: 2021.05.20 16:06
it will produce an error (and an empty page)
metapost
-context | main context file:
/usr/local/context/tex/texmf-context/tex/context/base/mkxl/context.mkxl
mtx-context | current version: 2021.05.19 18:22
hm, maybe some missing file or so .. i'll check it
Hans
:
/usr/local/context/tex/texmf-context/tex/context/base/mkxl/context.mkxl
mtx-context | current version: 2021.05.19 18:22
Greetings Lutz
Am 20. Mai 2021 09:05:49 MESZ schrieb Otared Kavian :
>Hi,
>
>After updating to LMTX version 2021.05.15 22:45 the following does not
>show any math
f needed because we bump memory stepwise
(on demand). It depends on the kind of projects you have. One can also
sey { plus = 1 } to add more to the set size without bothering about
existing values. Now, if you watch closely you'll see that most max
values are high already (initial v
ontext file:
/home/pi/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2021.05.09 17:14
mtx-context | main context file:
/home/pi/context/tex/texmf-context/tex/context/base/mkxl/context.mkxl
mtx-context | current version: 2021.05.09
t; dist/tex/context/base/mkiv/context.mkiv
> mtx-context | current version: 2021.03.05 19:11
> mtx-context | main context file: /usr/share/texmf-
> dist/tex/context/base/mkxl/context.mkxl
> mtx-context | current version: 2021.03.05 19:11
>
> # Debian Buster Repos
> mtx
kiv/context.mkiv
mtx-context | current version: 2021.03.05 19:11
mtx-context | main context file: /usr/share/texmf-
dist/tex/context/base/mkxl/context.mkxl
mtx-context | current version: 2021.03.05 19:11
# Debian Buster Repos
mtx-context | ConTeXt Process Management 1.02
mtx-cont
is not readable
resolvers > resolving > file './lm.lfg' is not readable
weird, should be there (in tex/context/fonts/mkiv)
> resolvers > resolving > file 'lpdf-pdx.xml' is not readable
> resolvers > resolving > file './lpdf-pdx.xml' is no
three options, destination is a=#b. Both with MkIV and MkXL.
What am I missing to get the destination a={b}?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others
On 3/20/21 8:11 PM, Thangalin wrote:
> [...]
> Actual
> Build fails.
>
> resolvers > lua > loading file
> '/home/username/context/tex/texmf-context/tex/context/base/mkxl/spac-hor.lmt'
> succeeded
> tex error > tex error on line 25 in file spac-hor.m
> lua > loading file
'/home/username/context/tex/texmf-context/tex/context/base/mkxl/spac-hor.lmt'
succeeded
tex error > tex error on line 25 in file spac-hor.mkxl: Undefined
control sequence
\bitwiseflip \normalizelinemode \flattendiscretionariescode
The control sequence at the
' (number expected, got nil)
stack traceback:
[C]: in function 'string.format'
?: in field '?'
...ext/tex/texmf-context/tex/context/base/mkxl/luat-log.lmt:178: in
upvalue 'report'
...ext/tex/texmf-context/tex/context/base/mkxl/luat-log.lmt:391: in
upvalue 'report'
[string
:
[C]: in function 'string.format'
?: in field '?'
...ext/tex/texmf-context/tex/context/base/mkxl/luat-log.lmt:178: in
upvalue 'report'
...ext/tex/texmf-context/tex/context/base/mkxl/luat-log.lmt:391: in
upvalue 'report'
[string "
mtx-context | fatal error: return code:
' yearly current release
but of course after that there will be updates when needed. In these
updates we don't distinguish between betas and currents: we dropped that
some time ago because it was only confusing.
Last/this year much of LMTX (mkxl, mpxl, lmt files) already got split
and I expect
|
mtx-context | main context file: /tex/texmf-
context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2021.02.14 16:39
mtx-context | main context file: /tex/texmf-
context/tex/context/base/mkxl/context.mkxl
mtx-context | current version: 2021.02.14 16:39
Would
Hi,
I am getting the following error with luatex/mkiv with today's latest:
context --make
loading : ConTeXt Token Support / Initialization
/usr/share/texmf/tex/context/base/mkxl/toks-ini.lmt:21: attempt to call a
nil value (field 'getcommandvalues')
stack traceback:
/usr/share/texmf/tex
ers | formats | executing runner 'run luametatex format':
>>> ~/Library/ConTeXt/tex/texmf-osx-64/bin/luametatex --jobname="test"
>>> --fmt=~/Library/ConTeXt/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt
>>> --l
h/english
system >
system > 'cont-new.mkxl' loaded
open source > level 2, order 2, name
'/opt/context/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mkiv
close source> level 2, order 2, nam
Jano Kula schrieb am 17.01.2021 um 21:22:
Hello to everybody!
\setuphead[section][expansion=yes] expands xml reference to the actual
content in TUC file:
\xmlatt {xml:name::4}{title} → First section
for titles & bookmarks. The same is not true for userdata (mkiv & mkxl).
Do you
Hello to everybody!
\setuphead[section][expansion=yes] expands xml reference to the actual
content in TUC file:
\xmlatt {xml:name::4}{title} → First section
for titles & bookmarks. The same is not true for userdata (mkiv & mkxl). Do
you know how to force expansion of userdata?
MWE
Library/ConTeXt/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt
>> --lua=~/Library/ConTeXt/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.lui
>> --c:currentrun=1 --c:fulljobname="
--c:fulljobname="./test.lmtx" --c:input="./test.lmtx"
> --c:kindofrun=1 --c:maxnofruns=9
> --c:texmfbinpath="~/Library/ConTeXt/tex/texmf-osx-64/bin"
> system >
> system > ConTeXt ver: 2020.12.24 17:30 LMTX fmt: 2020.12.25
> int: english/englis
--c:texmfbinpath="~/Library/ConTeXt/tex/texmf-osx-64/bin"
system >
system > ConTeXt ver: 2020.12.24 17:30 LMTX fmt: 2020.12.25 int:
english/english
system >
system > 'cont-new.mkxl' loaded
open source > level 1, order 1, name
'~/
t;~/Library/ConTeXt/tex/texmf-osx-64/bin"
system >
system > ConTeXt ver: 2020.12.24 17:30 LMTX fmt: 2020.12.25
int: english/english
system >
system > 'cont-new.mkxl' loaded
open source > level 1, order 1, name
'~/Library/ConTeXt/t
pe-" prefix isn't anough anymore,
you have to change it to "type-imp-" (e.g. type-imp-sourceserif.tex) to
be found by ConTeXt.
Valid file extensions for a typescript file in LMTX (and MkIV) are
"tex&
in:
> > mtx-install | changed : 0 % : 2696864 :
> > tex/texmf-linux-aarch64/bin/luametatex
> >
> > Is there a problem on my side or is this a bug?
> >
> > Because of wrong binary version I can't run context --make
> >
> > This is LuaMetaTeX, Version 2.0
/tex/context/base/mkxl/cont-en.mkxl(context.mkxl(syst-ini.mkxl
! token call, execute: [\directlua]:1: array of names expected
stack traceback:
[C]: in function 'tex.enableprimitives'
[\directlua]:1: in main chunk.
}
something seemed messed up (incompleteupload or so) ... i'll make
| changed : 0 % : 2696864 :
tex/texmf-linux-aarch64/bin/luametatex
Is there a problem on my side or is this a bug?
Because of wrong binary version I can't run context --make
This is LuaMetaTeX, Version 2.08.03
2097153([...]/lmtx/tex/texmf-context/tex/context/base/mkxl/cont-en.mkxl(context.mkxl(syst
t; \stopitemize
> \stoptext
>
> I’m afraid that the link has problems with margin in MkXL (MkIV doesn’t
> have any problems with it).
>
> Could anyone confirm the issue?
>
> Many thanks for your help,
>
> Pablo
> --
> http://www.ousia.tk
> __
\letterhash e}}
\stopitemize
\stoptext
I’m afraid that the link has problems with margin in MkXL (MkIV doesn’t
have any problems with it).
Could anyone confirm the issue?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
Unfortunately after running install.bat script, I see errors at the end of installation run : This is LuaMetaTeX, Version 2.05.01 (INITEX)(D:/ConTeXt/lmtx/tex/texmf-context/tex/context/base/mkxl/cont-en.mkxl(context.mkxl! Undefined control sequence.l.31 \immutable \edef\contextformat
doesn’t use
the space to break. In fact, it doesn’t add the space.
There is a simple workaround for that (explicitly adding "\ " between
the closing bracket and the closing brace).
But I wonder whether this might point to a more general issue in LMTX
(or my lack of understandi
he impression that this should work.
I could do it manually by adding \writetolist as part of the renderingsetup,
but there are already multiple \writetolist in the annotation module, so I
think that I am missing a configuration option.
> btw, maybe wolfgang should turn that module into a core mkxl
add the space.
There is a simple workaround for that (explicitly adding "\ " between
the closing bracket and the closing brace).
But I wonder whether this might point to a more general issue in LMTX
(or my lack of understanding of MkXL).
Mnay thanks for your help,
Pablo
--
http://ww
}]
\input ward
\stoptest
just cheat:
\starttest[title={This is another title}, list={This is in the 2nd
list},after={\writetolist[test]{1}{what a cheat}}]
\input ward
\stoptest
btw, maybe wolfgang should turn that module into a core mkxl one using
the new fancy macro magic
anyway
main context file:
>> /home/ousia/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv
>> mtx-context | current version: 2020.11.24 00:41
>> mtx-context | main context file:
>> /home/ousia/context/tex/texmf-context/tex/context/base/mkxl/context.mkxl
>> mtx
mtx-context | current version: 2020.11.24 00:41
mtx-context | main context file:
/home/ousia/context/tex/texmf-context/tex/context/base/mkxl/context.mkxl
mtx-context | current version: 2020.11.24 00:41
Well I can see that there is two versions.
But when unzipping the new context-linux
nagement 1.04
mtx-context |
mtx-context | main context file:
/home/ousia/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2020.11.24 00:41
mtx-context | main context file:
/home/ousia/context/tex/texmf-context/tex/context/base/mkxl/context.mk
After running install.bat I see error : This is LuaMetaTeX, Version 2.08.03 2097153(D:/ConTeXt/lmtx/tex/texmf-context/tex/context/base/mkxl/cont-en.mkxl(context.mkxl(syst-ini.mkxl)(norm-ctx.mkxl)(syst-pln.mkxl)(syst-mes.mkxl)(luat-cod.mkxl<+ D:/ConTeXt/lmtx/tex/texmf-context/tex/context/base/m
osetinjector [#1][#2][#3]{\clf_setinjector{#1}{#2}{#3}}
Were the files mixed up?
Shouldn't the former be for mkxl (lmtx) and the latter for mkiv?
Adam
___
If your question is of interest to others as well, please add an entry
mat': /
> my-own-dir/ConTeXt/tex/texmf-linux-64/bin/luametatex --ini
> --lua=/my-own-dir/chantool/ConTeXt/tex/texmf-context/tex/context/base/mkiv/luat-cod.lmt
> /my-own-dir/ConTeXt/tex/texmf-context/tex/context/base/mkiv/cont-en.
> mkxl
> This is LuaMetaTeX, Version 2.08.01
> 2
n-dir/ConTeXt/tex/texmf-linux-64/bin/luametatex --ini
--lua=/my-own-dir/chantool/ConTeXt/tex/texmf-context/tex/context/base/mkiv/luat-cod.lmt
/my-own-dir/ConTeXt/tex/texmf-context/tex/context/base/mkiv/cont-en.
mkxl
This is LuaMetaTeX, Version 2.08.01
2097153(/my-own-dir/ConTeXt/tex/texmf-context
f /b/) – (height of /a/), which does not hold in my
> > case. So it looks like I need to find another way to set the TrimBox
> > (and the BleedBox, which I want to be 3mm wider and taller than the
> > TrimBox). Does anyone know how to do this?
>
> Hi Jack,
>
&g
eedBox, which I want to be 3mm wider and taller than the
> TrimBox). Does anyone know how to do this?
Hi Jack,
there seems to be a bug in ConTeXt (both in MkXL and MkIV).
From this code:
\setuplayout
[cropoffset=15ex,
trimoffset=20ex,
bleedoffset=25ex,
artoffset=30ex
{\dorecurse{25}{Section }3}
\section{Section 3}
\stoptext
For some strange reason (at least, to me), \placelist[alternative=d]
seems to misbehave when using \it or \bi as style.
Everthing is fine when italic fonts aren’t used.
I’m afraid I may be hitting a bug in both latest MkXL from 2020.03.10
14
On 2/25/20 8:56 PM, Wolfgang Schuster wrote:
> On Tue, 25 Feb 2020 20:43:59 +0100 Pablo Rodriguez wrote:
>> [...]
>> I mean, line isn’t broken after any "/".
>>
>> Is this a bug in MkXL (and MkIV) or am I missing something?
>
> The break happpens only
\stoptext
>
> I mean, line isn’t broken after any "/".
>
> Is this a bug in MkXL (and MkIV) or am I missing something?
The break happpens only when letters are on the left and right side but not for
numbers.
\setbreakpoints[compound]
\start
Dear list,
I cannot get this working:
\setuppapersize[A9]
\setupbodyfont[26pt]
\setbreakpoints[compound]
\starttext
1989/3242/CEE\\
2009/3926/UE\\
\stoptext
I mean, line isn’t broken after any "/".
Is this a bug in MkXL (and MkIV) or am I missing someth
On 2/17/2020 10:56 PM, Pablo Rodriguez wrote:
On 2/17/20 7:49 PM, Hans Hagen wrote:
On 2/17/2020 4:51 PM, Pablo Rodriguez wrote:
[...]
Sorry if I hadn’t expressed myself accurately before. The issue here
isn’t having exactly the same output in both MkIV and MkXL. The real
problem
On 2/17/20 7:49 PM, Hans Hagen wrote:
> On 2/17/2020 4:51 PM, Pablo Rodriguez wrote:
>> [...]
>> Sorry if I hadn’t expressed myself accurately before. The issue here
>> isn’t having exactly the same output in both MkIV and MkXL. The real
>> problem is that characters ar
t make any difference with TeX Gyre
Heros (https://pdf.ousia.tk/stretch-mkxl-hz.pdf) and it only corrected
one problematic case with Source Serif Pro
(https://pdf.ousia.tk/stretch-ssp-mkxl-hz.pdf).
Sorry if I hadn’t expressed myself accurately before. The issue here
isn’t having exactly the same outp
n’t make any difference with TeX Gyre
Heros (https://pdf.ousia.tk/stretch-mkxl-hz.pdf) and it only corrected
one problematic case with Source Serif Pro
(https://pdf.ousia.tk/stretch-ssp-mkxl-hz.pdf).
Sorry if I hadn’t expressed myself accurately before. The issue here
isn’t having exactly the
, hz]
\setupbodyfont[mainface, 17pt]
%~ \setupbodyfont[helvetica, 17pt]
\starttext
\input zapf
\stoptext
hz doesn’t work fine in MkXL, but it works fine in MkIV.
I think the flow of characters is broken in MKXL. Some
With TeX Gyre Heros (https://pdf.ousia.tk/mkiv-hz.pdf
]
%~ \setupbodyfont[helvetica, 17pt]
\starttext
\input zapf
\stoptext
hz doesn’t work fine in MkXL, but it works fine in MkIV.
I think the flow of characters is broken in MKXL. Some
With TeX Gyre Heros (https://pdf.ousia.tk/mkiv-hz.pdf and
https://pdf.ousia.tk/mkxl-hz.pdf):
- "computer&quo
file:
/home/massi/context/lmtx/tex/texmf-context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2019.07.24 11:31
mtx-context | main context file:
/home/massi/context/lmtx/tex/texmf-context/tex/context/base/mkiv/context.mkxl
mtx-context | current version: 2020.02
mf-context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2019.07.24 11:31
mtx-context | main context file:
/home/massi/context/lmtx/tex/texmf-context/tex/context/base/mkiv/context.mkxl
mtx-context | current version: 2020.02.11 16:41
"2020.02.11 16:41&q
indeed
> > >
> > >> * .mkiv: Is that just for ConTeXt or all LuaTeX stuff? Would
> > it make
> > >> sense to give text documents that extension?
> > >
> > > you can do that (or mkvi or lmtx or ...)
> >
>
ake
>> sense to give text documents that extension?
>
> you can do that (or mkvi or lmtx or ...)
Since there are already *.mkxl files in the ConTeXt distribution, I
think it may make sense to name the LMTX version MkXL.
In any case, MkXL is simpler and cl
ML files
> >> inside of ConTeXt itself
> >
> > context ctx files are xml files indeed
> >
> >> * .mkiv: Is that just for ConTeXt or all LuaTeX stuff? Would it make
> >> sense to give text documents that extension?
> >
> > you can
ents that extension?
>
> you can do that (or mkvi or lmtx or ...)
Since there are already *.mkxl files in the ConTeXt distribution, I
think it may make sense to name the LMTX version MkXL.
In any case, MkXL is simpler and clearer that MkIV with LMTX.
Pablo
--
http://www.ousia.tk
_
]
\setupinteractionscreen[option=attachment]
\starttext
a\attachment[file=xml-mkiv.pdf, name={attached.pdf}]
\stoptext
This happens with latest beta (from 2019.12.17) in both MkIV and MkXL.
https://www.pdfa.org/wp-content/uploads/2018/10/PDF20_AN002-AF.pdf#search=usability
warns about the use
]
\starttext
a\attachment[file=xml-mkiv.pdf, name={attached.pdf}]
\stoptext
This happens with latest beta (from 2019.12.17) in both MkIV and MkXL.
https://www.pdfa.org/wp-content/uploads/2018/10/PDF20_AN002-AF.pdf#search=usability
warns about the use of both /EmbeddedFiles and /FileAttachment
={attached.pdf}]
\stoptext
This happens with latest beta (from 2019.12.17) in both MkIV and MkXL.
https://www.pdfa.org/wp-content/uploads/2018/10/PDF20_AN002-AF.pdf#search=usability
warns about the use of both /EmbeddedFiles and /FileAttachment
annotations. Acrobat seems to be the problematic
x.
>
> Hans,
>
> I’m afraid that attachments in MkXL aren’t attached to the PDF document
> (using latest beta from 2019.12.12 13:15).
Hans,
many thanks for your ultra-fast fix in beta from 2019.12.12 19:35.
> BTW, if I try to compile this with MkIV beta from 2019.12.12 13:04, I
> get a c
On 12/12/19 1:37 AM, Hans Hagen wrote:
> [...]
> Anyway, hopefully nothing got broken. Peter Rolf and I are updating some
> of the pdf validation related stuff (additional formats), so that can be
> in flux.
Hans,
I’m afraid that attachments in MkXL aren’t attached to the PDF doc
> on Linux.
>>
>> Try also \dontleavehmode\llap{\ConTeXt} because \llap by itself does not
>> start
>> a paragraph.
>
> Hi Henri,
>
> many thanks for your reply.
>
> This is really weird, since I cannot make it work, either with Acrobat
> in Window
ing latest beta from 2019.11.14 17:07 (either MkIV or MkXL). Which
beta are you using?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
If your question is of interest to others as well, please add an entry
Am 08.10.19 um 15:11 schrieb Pablo Rodriguez:
> Dear list,
>
> I have the following sample:
>
> \setupinteraction[state=start, focus=standard]
> \starttext
> a\footnote{b}
> \stoptext
>
> Using latest beta from MkXL (2019.10.05 14:56), link for
Dear list,
I have the following sample:
\setupinteraction[state=start, focus=standard]
\starttext
a\footnote{b}
\stoptext
Using latest beta from MkXL (2019.10.05 14:56), link form footnote to
main text body doesn’t work.
Latest beta from MkIV (2019.10.05 14:45) has no issue
... not
something i want to do in the middle of other transitions like
mkiv->mkxl and such)
hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
.
Hello,
Why mkvi and not mkv ?
I guess because mkvi has four letters like mkii and mkiv but mkv ha only three.
So the next versions will be mkix, mkxi, mkxv, mkxx, mkxl, mkli, mklv, and
mkxc. It is gonig to get confusing real soon :)
BTW, does anyone has a minimal example on how to use mkvi
301 - 371 of 371 matches
Mail list logo
