On Sun Sep 5, 2021 at 7:37 PM CEST, Hans Hagen wrote:
> On 9/5/2021 5:51 PM, Michal Vlasák via ntg-context wrote:
> > Hello Hraban,
>
> > "execute" should be a function defined in LuaMetaTeX, that internally
> > calls zint functions.
> does
>
> conte
On 9/5/2021 5:51 PM, Michal Vlasák via ntg-context wrote:
Hello Hraban,
"execute" should be a function defined in LuaMetaTeX, that internally
calls zint functions.
does
context libs-imp-zint.mkxl
produce
On Sun Sep 5, 2021 at 6:30 PM CEST, Henning Hraban Ramm via ntg-context wrote:
> > Am 05.09.2021 um 17:51 schrieb Michal Vlasák :
> > "execute" should be a function defined in LuaMetaTeX, that internally
> > calls zint functions.
>
> Hm, ok, but where are the zint
place where you can keep an eye on
>them being updated, like
>
> c:/data/tex-context/tex/texmf-win64/bin/lib/luametatex/foo/libfoo.dll
Oh, yes, I should still know that from mujs. Works with a symlink.
I.e. no need to change that in the module.
>> But then still zin
nt.dylib"*.
> I changed that in the source and the file appears to be found.
> Could you add that, Hans?
From libraries-mkiv:
It is best to keep libraries in a place where you can keep an eye on
them being updated, like
c:/data/tex-context/tex/texmf-win64/bin/lib/luametate
passing by
removing the outer braces? Is this a bug or is it an unavoidable
consequence of the TeX-LuaTeX interface?
\starttext
\def\foo#1{\detokenize{#1}} \foo{hvdm has to read the tex book}
\def\foo#+{\detokenize{#1}} \foo{hvdm has to read the luametatex
ime on marks (aka markings),
think of running headers and so.
I'm considering replacing the marking code by new code that I already
have one my machine. In mkiv we;ve always used a more powerful
alternative for the marks that than what luatex and friends provide but
in luametatex I a
\starttext
\m{\root3\of2}
\stoptext
works.
But
\starttext
\startMPcode
label("\m{\root3\of2}", origin);
\stopMPcode
\stoptext
doesn't.
Running `LuaMetaTeX' on `trial' with
``/home/fvleung/ConTeXt/tex/texmf-linux-64/bin/mtxrun --autogenerate
--script conte
(also discusses luametatex)
new : lowlevel-alignments (also discusses luametatex)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel
option is like g but better so it sort of replaces it.
updated: lowlevel-expansion (also discusses luametatex)
new: lowlevel-alignments (also discusses luametatex)
Hans
-
Hans Hagen
.. doing
> metapost things is a nice distraction and with the mp extensions that we
> have in luametatex we can do quite a lot)
>
> Hans
>
> -
>Hans Hagen | PRAGMA ADE
>
have wished for metafun they can let me know ... doing
metapost things is a nice distraction and with the mp extensions that we
have in luametatex we can do quite a lot)
Hans
-
Hans Hagen
at when I copy the "faulty" part (my table) to another
document (including all relevant defs etc.) it just works fine. So, I think it must have
to do something with the placement of the float on the page.
Any hints what has changed?
your luametatex binary seems older than
l documents, but it can
> accumulate; also less memory used then; i could bring down an extreme 2000
> page 5 column doc tuc file down to 5% -- it was 70 MB; for the luametatex
> manual it reducec the tuc more than 30%; hard to tell if there will be an
> associated performance hit, b
extreme
2000 page 5 column doc tuc file down to 5% -- it was 70 MB; for the
luametatex manual it reducec the tuc more than 30%; hard to tell if
there will be an associated performance hit, but i'm sure thomas will
complain if that's the case
I never realized that tuc files can grow s
doc tuc file down to 5% -- it was 70 MB; for the
> luametatex manual it reducec the tuc more than 30%; hard to tell if
> there will be an associated performance hit, but i'm sure thomas will
> complain if that's the case
I never realized that tuc files can grow so big. Fo
Hi,
Here are the highlights of todays update:
- somewhat more compact tuc files, not for all documents, but it can
accumulate; also less memory used then; i could bring down an extreme
2000 page 5 column doc tuc file down to 5% -- it was 70 MB; for the
luametatex manual it reducec the tuc
otf reader > fatal error in file 'Fraunces.ttf':
...e0dde776fb1556f32e/formats/luametatex/font-ttf-macro.lua:274: attempt to index
a nil value (local 'p1')
stack traceback:
...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:2
dde776fb1556f32e/formats/luametatex/font-ttf-macro.lua:274: attempt to
index a nil value (local 'p1')
stack traceback:
...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:2339:
in metamethod 'index'
...e0dde776fb1556f32e/formats/luametatex
ct:A ConTeXt template Keywords: template Author:
Mickey Mouse Creator:LuaMetaTeX 2.09 20210418 + ConTeXt LMTX
2021.04.21 11:39 Producer: LuaMetaTeX-2.09 CreationDate: Tue Aug 10
10:18:36 2021 +08 ModDate:Tue Aug 10 10:18:36 2021 +08 Tagged:
no UserProperties: n
l ~/lmtx/tex/texmf-osx-64/bin/lib/luametatex/mujs/
> total 2832
> -rw-r--r-- 1 hraban staff 517K 7 Aug 09:49 libmujs.o
> -rw-r--r-- 1 hraban staff 9,2K 7 Aug 09:49 main.o
> -rwxr-xr-x 1 hraban staff 413K 7 Aug 09:49 mujs*
> -rwxr-xr-x 1 hraban staff 408K 7 Aug 09:49 mujs-pp*
> -rw-
osx-64/bin/lib/luametatex/mujs/
total 2832
-rw-r--r-- 1 hraban staff 517K 7 Aug 09:49 libmujs.o
-rw-r--r-- 1 hraban staff 9,2K 7 Aug 09:49 main.o
-rwxr-xr-x 1 hraban staff 413K 7 Aug 09:49 mujs*
-rwxr-xr-x 1 hraban staff 408K 7 Aug 09:49 mujs-pp*
-rw-r--r-- 1 hraban staff 2,9K
Hi Taco (et al.),
for running the ECMAscript part of the CG journal, I cloned the repo from
https://github.com/ccxvii/mujs/ and executed "make release".
I copied the resulting files to my TeX tree:
ll ~/lmtx/tex/texmf-osx-64/bin/lib/luametatex/mujs/
total 2832
-rw-r--r-- 1 hraban st
is
needed. localfootnotes does work but places the footnote immediately
below the framed text, and I wanted it to appear in the usual
footnote location, which is achieved with startpostponingnotes
I assume that you use(d) mkiv/luatex and not lmtx/luametatex.
Footnotes are in tex speak 'inserts
se the old one, so that's somewhat problematic).
it's not too hard to make it work, see attached, but the new one is
nicer because it permits more detailed control
in luametatex you can do things like
Au{\norightligaturing f}lage
that is: each character can have a set of options;
startpostponingnotes
I assume that you use(d) mkiv/luatex and not lmtx/luametatex.
Footnotes are in tex speak 'inserts' and at some point they are filtered
and added to the datastructure (list) that is taken into account when
breaking a page.
When tex was written, the main application was
finalizing some luametatex code. Part of it had been there in
commented form as I had not yet made up my mind about how much is
needed. In the end I decided to *not* integrate it in the \numexpr an
d\dimexpr primitives because of potential compatibility issues (although
that is unlikely given the way
ver: 2021.07.16 22:03 LMTX fmt: 2021.7.21 int:
english/english
metapost> trace > This is MPLIB for LuaMetaTeX, version 3.11, running
in scaled mode.
metapost> trace >
metapost> trace > loading metafun for lmtx, including the plain 1.004
base definitio
format 'metafun'
and method 'default'
% metapost> loading 'metafun' as 'metafun.mpxl' using method 'default'
% metapost> initializing number mode 'scaled'
% metapost> trace > This is MPLIB for LuaMetaT
Jdh,
Can you please try again with this binary?
https://dl.contextgarden.net/build/luametatex/aarch64-linux/
On Fri, 16 Jul 2021 at 22:16, Alan Braslau wrote:
>
> Freebsd on arm64 is now a Tier 1 architecture. ;-)
I figured out that there are should-be-working-out-of-the-box imag
Although now it remains to apply this technique to LuaMetaTeX. Without
access to source code I can't try anything, but the general ideas should
apply:
I used Zig for cross compiling. While Zig is a full fledged programming
language in its own right, it also has the ability to compile C/C++
qemu-aarch64 ./ltex-aarch64-linux-musl --help
>
>The above are cross compiled (debug) builds of very stripped down
>version of LuaTeX, that I have been experimenting with. They won't
>solve
>the immediate problem, but the cross compiling procedure could be used
>to generate luamet
g procedure could be used
to generate luametatex binaries for this target until a better option is
available. Of course, depending on whether it even works. :)
Michal Vlasák
___
If your question is of interest to others as
\setupinteraction[state=start]
\usemodule[animation]
\starttext
\useMPanimation[menu=yes]{demo}
\stoptext
Placing this excerpt in a file and compiling it I get an error:
$ context animation.tex
resolvers | formats | executing runner 'run luametatex format':
/home/vm/context/tex/texmf-li
install on github which would then involve:
-- core context code (with luametatex in source tree too:
tex/texmf-context in the distribution
-- the minimal set of resources: tex/texmf in the distribution
-- binaries (which is the more complex part)
-- modules: texmf/modules
So, basically
On 6/29/2021 12:06 PM, Steffen Wolfrum wrote:
When running this mwe with luatex, the command \- could be used to manually
break the line, even though it is set up nothyphenated.
When running luametatex the word does not break:
\setuppapersize[A10]
\showframe
\setuphead[chapter][align
While luametatex works fine, running this mwe with luatex ends in an error:
\startexceptions
con-text
\stopexceptions
\starttext
context
\stoptext
...-64/tex/texmf-context/tex/context/base/mkiv/lang-ini.lua:198: attempt to
call a nil value (global 'sortedhash')
stack
When running this mwe with luatex, the command \- could be used to manually
break the line, even though it is set up nothyphenated.
When running luametatex the word does not break:
\setuppapersize[A10]
\showframe
\setuphead[chapter][align={nothyphenated}]
\starttext
\chapter{abc\-def
Steffen Wolfrum schrieb am 27.06.2021 um 15:55:
uncommenting the following \setupcolors changes magenta to black when running
luatex.
but when running luametatex the footnote is crippled to «error»:
\starttext
\definestartstop[UL][color=magenta]
%\setupcolors[state=stop,conversion=never
uncommenting the following \setupcolors changes magenta to black when running
luatex.
but when running luametatex the footnote is crippled to «error»:
\starttext
\definestartstop[UL][color=magenta]
%\setupcolors[state=stop,conversion=never]% <- bw with lualatex, but «error»
with luameta
\skip0=10pt plus 10pt minus 10pt plus 20pt
test \skip0=10pt plus 10pt plus 20pt minus 10pt
test \vrule width 10pt height 10pt depth 10pt depth 10pt height 10pt
% test \hbox to 10pt to 10pt {x}
\stoptext
compare pdftex and luametatex.
ok. but why does this run fine
\starttext
Test
t
> test \skip0=10pt plus 10pt minus 10pt plus 20pt
>
> test \skip0=10pt plus 10pt plus 20pt minus 10pt
>
> test \vrule width 10pt height 10pt depth 10pt depth 10pt height 10pt
>
> % test \hbox to 10pt to 10pt {x}
>
> \
10pt
test \vrule width 10pt height 10pt depth 10pt depth 10pt height 10pt
% test \hbox to 10pt to 10pt {x}
\stoptext
compare pdftex and luametatex.
Hans
-
Hans Hagen | PRAGMA ADE
gt; Steffen
>
> –––
>
> … $ ~/context-osx-64/tex/texmf-osx-64/bin/mtxrun --script context
> --autogenerate /Users/steffen/Desktop/error_1.tex
>
> resolvers | formats | executing runner 'run luametatex format':
> /Users/steffen/context-osx-64/tex/texmf-osx
| executing runner 'run luametatex format':
/Users/steffen/context-osx-64/tex/texmf-osx-64/bin/luametatex
--jobname="error_1"
--fmt=/Users/steffen/context-osx-64/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt
--lua=/Users/steffe
form optimizations (so one needs to
run configure scripts) ... in luametatex i try to stay away from that ..
but loading as external lib is of course an option; we already support
zip, gz, tar, lz4, lzma (xz), lzo, xstd but i doubt if in practice they
are used often (zip we need for pdf, gz for
variant uses the
basic decompressor of the engine (different in lmtx than in mkiv but
that should not matterl i only tested lmtx). The xz one is a bit more
special as it uses the external xz program unless one has limlzma
installed, e.g. in:
tex/texmf-win64/bin/lib/luametatex/lzma
rmula
>> \stoptext
> it's a bug i introduced in the engine .. you can try a newer bin from:
>
> https://dl.contextgarden.net/build/luametatex/
>
>
> -
> Hans H
\cup B = X \cap Y$
\startformula
A \bigcup B = X \bigcap Y
\stopformula
\stoptext
it's a bug i introduced in the engine .. you can try a newer bin from:
https://dl.contextgarden.net/build/luame
wired
properties. I know that not all of that is really needed (also because
much of tex math is chisseled in stone and not supposed to be controlled
although in context i suppose we have a bit more freedom) but it simply
fit in the luametatex effort to do so.
Of course there might be math fields
pages > flushing realpage 7, userpage 6, subpage 7
pages > flushing realpage 8, userpage 7, subpage 8
pages > flushing realpage 9, userpage 8, subpage 9
[Gets stuck at this point, with luametatex using 100% CPU]
3. Fatal error in both cases:
$ /Libr
7; with
``/home/viserion/LMTX/tex/texmf-linux-64/bin/mtxrun --autogenerate --script
context --autopdf --purgeall hans-33''
resolvers | formats | executing runner 'run luametatex format':
/home/viserion/LMTX/tex/texmf-linux-64/bin/luametatex --jobname="hans-33"
--fmt=/ho
x = \int\Umathadaptsize^1_2 x =
> x = \rab\Umathadaptsize^1_2^^1__2 \mathinner{\vrule height 30mm
> depth 30mm width 5mm}
> $
>
> \stoptext
>
> After playing with several solutions (delimiters, fences, radicals etc)
> I just settled for a few line extension to the engine
= \rab\Umathadaptsize^1_2^^1__2 \mathinner{\vrule height 30mm
depth 30mm width 5mm}
$
\stoptext
After playing with several solutions (delimiters, fences, radicals etc)
I just settled for a few line extension to the engine (there was already
plenty in place in luametatex for that anyway) and i
e are implemented and the way
TeX (the engine) works when it reads arguments.
and, also in mkiv \dofmode is unexpandable so cannot act as keyword
(it might not crash but also doesn't work)
Here is a short example which demonstrates the differences between
LuaTeX (eTeX, pdfTeX etc.) and
de{aaa}{on}} [[\meaningless\foo]]
only in luametatex/lmtx
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pra
t-pgf.tex
>
For me this builds fine with MkIV (TeX Live 2021 on Arch, specifically
2021.58686-3), however TikZ is incompatible with LMTX right now:
https://github.com/pgf-tikz/pgf/issues/990
There I get the following issue which is slightly different than yours
though:
resolvers
\startTEXpage[offset=1ex]
\startitemize
\item \MyURL{a.b\\/c.d\letterhash e}
\stopitemize
\stopTEXpage
\stoptext
I’m using current latest from 2021.06.04 17:28.
LuaTeX generates the link rectangle right.
LuaMetaTeX generates a wrong link rectangle.
In the attached image, you can see
{a.b\\/c.d\letterhash e}
\stopitemize
\stopTEXpage
\stoptext
I’m using current latest from 2021.06.04 17:28.
LuaTeX generates the link rectangle right.
LuaMetaTeX generates a wrong link rectangle.
In the attached image, you can see the output I get (MkIV and LMTX).
Could anyone confirm the
\usemodule[sql]
you also need to have the sql library in the tex binary tree
(see manual)
(in luatex/mkiv it's best to use the ffi variant that interfaces to
the mysql library; in luametatex/lmtx it's a - by default - build in
optional which loads the lib on demand; in all cases most
"--purgeall".
This happens both with MkIV (LuaTeX 1.13 7420 + ConTeXt MkIV 2021.06.04
17:28) and LMTX (LuaMetaTeX 2.09 20210531 + ConTeXt LMTX 2021.06.04 17:28).
Contents seem to be irrelevant, but actual contents of "mwe.tex" read:
\starttext
\input zapf
\stopt
appens both with MkIV (LuaTeX 1.13 7420 + ConTeXt MkIV 2021.06.04
17:28) and LMTX (LuaMetaTeX 2.09 20210531 + ConTeXt LMTX 2021.06.04 17:28).
Contents seem to be irrelevant, but actual contents of "mwe.tex" read:
\starttext
\input zapf
\stoptext
I’m afraid that this might be
e
(see manual)
(in luatex/mkiv it's best to use the ffi variant that interfaces to the
mysql library; in luametatex/lmtx it's a - by default - build in
optional which loads the lib on demand; in all cases most happens in lua)
so, if it doesn't work, y
0, late: 0, function 0, total: 0 (0 per page)
mkiv lua stats > randomizer: resumed with value 0.19171403880136
mkiv lua stats > loaded patterns: en::1, load time: 0.000
mkiv lua stats > loaded fonts: 3 files: latinmodern-math.otf, lmmono10-regular.otf, lmroman12-regular.otf
mkiv lua st
ins everything that is needed.
In lmtx "mtxrun" and "context" are just links to "luametatex" and when
called with a different name than "luametatex" they will try to locate
scripts with their name in the same path (so there need to be
mtxrun.lua and conte
they would not
conflict. LMTX contains everything that is needed.
In lmtx "mtxrun" and "context" are just links to "luametatex" and when
called with a different name than "luametatex" they will try to locate
scripts with their name in the same path (
ist callback tasks: 9 unique task lists, 8 instances
(re)created, 47 calls
mkiv lua stats > used backend: pdf (backend for directly generating pdf output)
mkiv lua stats > jobdata time: 0.001 seconds saving, 0.000 seconds loading
mkiv lua stats > callbacks: internal: 0, file: 0, direct:
Dear list,
For some reason pgfplots has a \pgfkeys invocation where the argument
has more than 4000 lines. This crashes LuaMetaTeX with the message
tex error > tex error on line 4045 in file pgfplots.code.tex: TeX capacity
exceeded, sorry [token memory size=100]
It doesn't se
Il 25/05/21 17:25, Henri Menke ha scritto:
Dear list,
For some reason pgfplots has a \pgfkeys invocation where the argument
has more than 4000 lines. This crashes LuaMetaTeX with the message
tex error > tex error on line 4045 in file pgfplots.code.tex: TeX capacity
exceeded, sorry [to
erribly long. I hope
that’s not bad etiquette. (I’m fairly new here.)
Thanks!
Gavin
> mtx-context | redirect luametatex -> luatex: luatex --luaonly
> "/Users/Gavin/context-osx-64/tex/texmf-osx-64/bin/mtxrun.lua" --script
> mtx-context --luatex --autopdf GlyphExp.
t someones pride and
> joy
> > over a nice and complex macro doing the same ... don't worry, i threw
> > away plenty of code by now
> >
> > -- significant performance gain: which is seldom the case (there
> really
> > is not much to gain, at
ext which is rather optimized
already)
-- giving way less noise in tracing: which for me is a good reason
(tracing changed a bit anyway)
-- not adding much code to the engine or the need to refactor: although
for some luametatex extensions some internals had to change
fundame
to gain, at least not in context which is rather optimized
> already)
>
> -- giving way less noise in tracing: which for me is a good reason
> (tracing changed a bit anyway)
>
> -- not adding much code to the engine or the need to refactor: although
> for some luametatex exten
Julian, is the luametatex file in that directory executable?
both context and mtxrun are links to it:
lrwxrwxrwx 1 xxx xxx 10 context -> luametatex
-rw-r--r-- 1 xxx xxx 1315 context.lua
-rwxr-xr-x 1 xxx xxx 2957368 luametatex
-rwxr-xr-x 1 xxx xxx 7150016 luatex
lrwxrwxrwx 1 xxx
already)
-- giving way less noise in tracing: which for me is a good reason
(tracing changed a bit anyway)
-- not adding much code to the engine or the need to refactor: although
for some luametatex extensions some internals had to change fundamentally
a good example is the extended macr
On 5/19/2021 9:56 PM, Alan Bowen wrote:
I seem to be stuck at ver. 209.08 (context ver. 2021.04.29).
I downloaded context-osx-64.zip and made a clean install following the
instructions for macOS on the wiki.
context—version showed v. 2021.04.29
So I removed texmf cache and ran
mtxrun —generate
showed ver. 2021.04.29
when I ran
sh install.sh
again, the result was the same. The version installed was still 2021.04.29
But this time the log showed an error
mtx-install | running:
/Users/bowen1/Desktop/LuaMetaTeX/tex/texmf-osx-64/bin/mtxrun --generate
lua error : startup file:
...owen1/Desktop
cted
to an usb3 ssd). My laptop is from 2013 (decent intel 3840QM cpu + 16 GB
mem and ssd and so) and is about 3 times slower than the rpi 4 in the
luametatex manual.
Your file in mkiv does a decent ppm (is that an arm or intel mac?)
mkiv lua stats > lua properties: engine: lua 5.3, used memor
pen"] =500, -- i use 2000
["luatex.maxprintline"] = 1, -- no need to change
["luatex.maxstrings"]= 50, -- maybe sometimes
["luatex.paramsize"] = 25000, -- seldom
["luatex.savesize"] = 10, -- often an error if more needed
Hi,
With luametatex becoming more mature, it's time to get rid of some old
code. For instance, we have lmt files that assume 5.4, but regular lua
files should work for luajittex (5.2) and luatex (5.3). Most noticable
are the lack of bitwise operators and integer devision in luajittex
On 5/3/2021 5:58 PM, Alan Bowen wrote:
I have re-installed the latest luametatex (macOS) following the
directions on the wiki
(https://wiki.contextgarden.net/Installing_ConTeXt_LMTX_on_MacOS
<https://wiki.contextgarden.net/Installing_ConTeXt_LMTX_on_MacOS>)
Though
luametatex --version
I have re-installed the latest luametatex (macOS) following the
directions on the wiki (
https://wiki.contextgarden.net/Installing_ConTeXt_LMTX_on_MacOS)
Though
luametatex --version
mtxrun --generate
are successful,
context --version
context --make --all
gets
mtxrun | unknown script
\exhyphenchar, in luametatex we can tag any char
as such
in traditional tex th ehyphenation, ligature building and kerning wre
integrated, so handling - -- --- -- is kind of complex
in luatex these stages are split but there's still messy logic wrt
successive hyphens
imapact in the lmtx code is that (when we go that route) some font
code can be dropped. The impact on luametatex-the-engine is that all
font related dimensions have more complex calculations, and of course
the impact on the math code is even larger because there we also have
the styles to deal
On Sat, Apr 24, 2021 at 1:33 AM Sylvain Hubert
wrote:
> You're right, I just checked the symbols of luatex and they contain all
> the APIs of lua 5.3.
> So I guess the problem is specific to luametatex and the latest context.
>
> > but in any case you should compile aga
You're right, I just checked the symbols of luatex and they contain all the
APIs of lua 5.3.
So I guess the problem is specific to luametatex and the latest context.
> but in any case you should compile against the luatex headers, not the
stock lua 5.3.6.
Does luatex have dedicated
erver:
https://dl.contextgarden.net/build/luametatex/win64/
make sure you replace/link luametatex.exe, mtxrun.exe and context.exe so
that all then use the replacement. Mojca also configured the setup for
native 32 bit binaries in case you need those. (The clang variants are
compiled because wa
refore luametatex --luaonly can’t execute it.
I suppose we can make it work (because lmtx can call out to kpse if
needed) but it's not worth the trouble because afaiks it depends on
perl, does all kind of map things, probably donwloads more than one
needs and I actually prefer to be expli
Hi!
The LMTX distribution comes with few binaries, texlua being none of them.
The getnonfreefonts <https://www.tug.org/fonts/getnonfreefonts/> script
seems simple enough, but it relies on a global “kpse” which it uses to get
kpse variables. Therefore luametatex --luaonly can’t execute i
ot and gets
added to LMTX. I could backport some but it probably makes no sense
(some is probably easy). There is of course untested code like the
overload protection mechasnisms but I have that enabled on my machine
(users can do that too) so I can notice side effects.
The new engine (luam
ications/LuaMetaTeX/tex/texmf-context/te..."]:1343: attempt to
concatenate a boolean value (local 'v')
I did a new upload that fixes is (had to do with 'nicer looking' logging).
Hans
-
ications/LuaMetaTeX/tex/texmf-context/te..."]:1343: attempt to
concatenate a boolean value (local 'v')
can you run on a shorter path so that we can see where?
-
Files that ran well with ver ConTeXt ver: 2021.02.20 16:50 LMTX and
earlier now fail with the following message:
tex error > tex error on line 74 in file
c_Review-0201-01_Bojowald.tex:
lua error:
run callback [36]: [string
"/Applications/LuaMetaTeX/tex/texmf-context/te..."]:
\luametatex\wincon\wincon.dll
(mtxrun --generate)
maybe
\enabletrackers[resolvers.libraries]
gives you a clue
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The
the latest luametatex/lmtx combination. It was crosscompiled on an
intel mac which took ages so it stuck as experiment. Because th eintel
bin runs on the arm mac it has a low priority (unless someone donates
an arm mini to the farm). So, forget about the arm apple bins for now.
We do generate wi
On 2/23/21 6:45 PM, Hans Hagen wrote:
> On 2/23/2021 6:15 PM, kaddour kardio wrote:
>> Thank you Hans and Pablo, symlinking the font directories to luametatex
>> font directory worked as expected. I guess i have to follow the same
>> steps after every update..
> no, beca
On 2/23/2021 6:15 PM, kaddour kardio wrote:
Thank you Hans and Pablo, symlinking the font directories to luametatex
font directory worked as expected. I guess i have to follow the same
steps after every update..
no, because texmf-fonts is never touched by an update
Hans
,
Shade) which is part of the ARM 64bit tree but not in the manual in the
X86 64bits tree.
That arm version was an experiment so it's definitely not in sync with
the latest luametatex/lmtx combination. It was crosscompiled on an intel
mac which took ages so it stuck as experiment. Becau
Thank you Hans and Pablo, symlinking the font directories to luametatex
font directory worked as expected. I guess i have to follow the same steps
after every update..
Le dim. 21 févr. 2021 à 18:42, Pablo Rodriguez a écrit :
> On 2/21/21 5:05 PM, Hans Hagen wrote:
> > On 2/21/202
dating the metafun manual (but first i need to do the
periodical update of the luametatex manual - kind of boring an dless fun
than metafun)
-
Hans Hagen | PRAGMA ADE
Ridde
601 - 700 of 1181 matches
Mail list logo
