hen possible following lmtx, otherwise frozen
>
> Because we develop lmtx and luametatex alongside it is no problem if we
> have experimental (and even temporary imperfect) code in the engine:
> context knows about it and especially with experiments, we try to make
> sure it doesn'
possible following lmtx, otherwise frozen
Because we develop lmtx and luametatex alongside it is no problem if we
have experimental (and even temporary imperfect) code in the engine:
context knows about it and especially with experiments, we try to make
sure it doesn't hit users (who we don't expect
Jairo A. del Rio schrieb am 23.07.2020 um 19:03:
Hi list! Is --engine=luatex working? Has it changed? The switch seems
to be ignored with newer ConTeXt distributions, so only LuaMetaTeX is
used. Thank you in advance.
context --luatex
Wolfgang
Hi list! Is --engine=luatex working? Has it changed? The switch seems to be
ignored with newer ConTeXt distributions, so only LuaMetaTeX is used. Thank
you in advance.
Jairo :)
___
If your question is of interest
hmode --silent --noconsole" compilation options.
>> Somewhat related question: is there a way to get rid of the
>>“This is LuaMetaTeX, Version 2.06.18 “
>> line on the terminal ?
> Ah, you want to completely hide that tex is used, just in case someone who
> watches a run gets bad feelings (and
. In order for this to work I used with previous versions
the "--nonstopmode --batchmode --silent --noconsole" compilation options.
Somewhat related question: is there a way to get rid of the
“This is LuaMetaTeX, Version 2.06.18 “
line on the terminal ?
Ah, you want to completely hid
r this to work I used with
> previous versions
>
> the "--nonstopmode --batchmode --silent --noconsole" compilation options.
Somewhat related question: is there a way to get rid of the
“This is LuaMetaTeX, Version 2.06.18 “
l
> For the second time we will held the meeting at the friendly farm U Škodů,
> at the eastern border of Prague. See the gallery from 2018
> <http://kostverlorenvaart.nl/context2018/> by Frans Goddijn.
>
> Topics will cover usage and development of LuaMetaTeX, ConTeXt, and
>
tting
resolvers | formats |
resolvers | formats | binary path :
/Users/hansm/TeX/context-lmtx/tex/texmf-osx-64/bin
resolvers | formats | format path :
/Users/hansm/TeX/context-lmtx/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luamet
s | binary path :
/Users/hansm/TeX/context-lmtx/tex/texmf-osx-64/bin
resolvers | formats | format path :
/Users/hansm/TeX/context-lmtx/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex
resolvers | formats | luatex engine : luame
0)--(100,0) dashed withdots;
> \stopMPpage
>
> When run through LuaMetaTeX produces a PDF about which Acrobat complains:
>
> The dimensions of this page are out-of-range. Page content might be
> truncated.
>
> and Adobe InDesign cannot handle it at all (displays emp
gt; \stopMPpage
>
> When run through LuaMetaTeX produces a PDF about which Acrobat complains:
>
> The dimensions of this page are out-of-range. Page content might be
> truncated.
>
> and Adobe InDesign cannot handle it at all (displays empty).
>
> The error message stays with
>
The following code:
\startMPpage[instance=doublefun]
draw (0,0)--(100,0) dashed withdots;
\stopMPpage
When run through LuaMetaTeX produces a PDF about which Acrobat complains:
The dimensions of this page are out-of-range. Page content might be
truncated.
and Adobe InDesign cannot
al/texlive/2020/texmf-dist/tex
> ~/lmtx/tex/texmf-modules/tex
> >
> > and similar (lmtx is my directory for the standalone).
> >
> > LuaTeX finds files without any issues. However LuaMetaTeX gives the
> > following error:
> >
stoptext
> >
> > works almost perfectly. However, the cross-reference does not work, even
> if the number of the enumeration is displayed correctly. The example fails
> both in LuaTeX and LuaMetaTeX. As I remember,
However, the cross-reference does not work, even if
> the number of the enumeration is displayed correctly. The example fails both
> in LuaTeX and LuaMetaTeX. As I remember, the problem appeared as early as
> 2019, so not a matter of a bad
}{\input ward}
\stopproposition
\in[prop:1]
\stoptext
works almost perfectly. However, the cross-reference does not work, even if
the number of the enumeration is displayed correctly. The example fails
both in LuaTeX and LuaMetaTeX. As I remember, the problem appeared as early
as 2019, so not a matter
The following gives wrong outputs both in LuaTeX and LuaMetaTeX:
\starttext $\sqrt{3}$ \stoptext
The beta date is 2020.7.5. Thank you very much.
Jairo :)
___
If your question is of interest to others as well, please add
The following gives wrong outputs both in LuaTeX and LuaMetaTeX:
\starttext $\sqrt{3}$ \stoptext
The beta date is 2020.7.5. Thank you very much.
Jairo :)
___
If your question is of interest to others as well
tex/texmf-modules/tex
> >
> > and similar (lmtx is my directory for the standalone).
> >
> > LuaTeX finds files without any issues. However LuaMetaTeX gives the
> > following error:
> >
> > runtime error : input file (name of file) is not found, quitting
&g
live/2020/texmf-dist/tex ~/lmtx/tex/texmf-modules/tex
>
> and similar (lmtx is my directory for the standalone).
>
> LuaTeX finds files without any issues. However LuaMetaTeX gives the
> following error:
>
> runtime error : input file (name of file) is not found, quitting
>
are welcome.
The download feature for binary files is broken, at least a leading
newline is prefixed to the download. But even then
https://source.contextgarden.net/source/luametatex/luametatex-source.tar.xz
is corrupted.
just ignore it ... it's just a left over crap file from some test
Hans
e download feature for binary files is broken, at least a leading
newline is prefixed to the download. But even then
https://source.contextgarden.net/source/luametatex/luametatex-source.tar.xz
is corrupted.
Cheers,
--
Leah Neukirchenhttps://
(lmtx is my directory for the standalone).
LuaTeX finds files without any issues. However LuaMetaTeX gives the
following error:
runtime error : input file (name of file) is not found, quitting
The same result is for modules, .sty files and .tex files. Is this
intentional, a bug in LMTX
on an article Taco wrote 2002
for MAPS.
The solution is to get rid of the old commands and focus on LuaTeX and
LuaMetaTeX solutions because the second allows different TeX code. The
following example shows one of these differences.
% LuaTeX
\def\mycommand
{\ifxxx
\expandafter\mycommanda
On 7/4/2020 7:22 AM, Marcel Fabian Krüger wrote:
Anyway, tehre is another thing I am wondering about: In the latest
luametatex versions, error help strings do not seem to work like they used to.
Especially after \errhelp{some help}\errmessage{error} or
tex.error('fdfd', {'some help
Hi all,
I have a bash script which converts a CSV file into a Lua table, which is then
used in ConTeXt.
It works fine, but I wonder whether there is a code within LuaMetaTeX for doing
this directly there (writing a new file which contains the Lua table). This
would be more efficient and neater
On Fri, Jul 03, 2020 at 09:56:28PM +0200, Hans Hagen wrote:
> On 7/3/2020 2:55 PM, Marcel Fabian Krüger wrote:
> > Hi,
> >
> > I recently noticed some cases where luametatex behaved in unexpected
> > ways:
> >
> >- The "Extra \fi&q
On 7/3/2020 2:55 PM, Marcel Fabian Krüger wrote:
Hi,
I recently noticed some cases where luametatex behaved in unexpected
ways:
- The "Extra \fi" error isn't triggered, instead an extra `\fi`
freezes luametatex. (Can be reproduced by compiling a document which
onl
Hi,
I recently noticed some cases where luametatex behaved in unexpected
ways:
- The "Extra \fi" error isn't triggered, instead an extra `\fi`
freezes luametatex. (Can be reproduced by compiling a document which
only consists of a single \fi)
- token.new can only create
t;
> > > \def#1\macro{blabla#1}
> > >
> > > where arguments come before. The only partial exceptions are commands
> > > like \atop or \over, which are in fact primitives. Is there a way to
> do
> > > this in ConTeXt?
> > >
> > > Could i
ome before. The only partial exceptions are commands
> > like \atop or \over, which are in fact primitives. Is there a way to do
> > this in ConTeXt?
> >
> > Could it be a feature request for LuaMetaTeX? I've seen Hans
> > experimenting a lot with new primitives and new p
le in TeX
> >
> > \def#1\macro{blabla#1}
> >
> > where arguments come before. The only partial exceptions are commands
> > like \atop or \over, which are in fact primitives. Is there a way to do
> > this in ConTeXt?
> >
> > Could it be a feature reque
it be a feature request for LuaMetaTeX? I've seen Hans
experimenting a lot with new primitives and new possibilities for
arguments, like #0 and co., so I ask in case it's not too nonsensical to
propose it. Regards
Every \foo will be looked up, so by the time \macro in:
bla bla {\bf xxx}\macro{xxx
I've read the following is not possible in TeX
\def#1\macro{blabla#1}
where arguments come before. The only partial exceptions are commands like
\atop or \over, which are in fact primitives. Is there a way to do this in
ConTeXt?
Could it be a feature request for LuaMetaTeX? I've seen Hans
mkiv lua stats > loaded fonts: 3 files: lmsans10-regular.otf,
texgyrepagella-math.otf, dejavusansmono.ttf
mkiv lua stats > font engine: otf 3.111, afm 1.513, tfm 1.000, 15 instances,
10 shared in backend, 3 common vectors, 7 common hashes, load time 0.365
seconds
mkiv lua stats >
there is
not much (measurable) to gain at the macro level wrt speed. Most
bottlenecks are at the Lua end anyway.
(1) macro arguments:
In tex a macro argument is defined with numbers, so
\def\foo#1#2{... #2 ... #2 ...}
in luametatex we can have some variants
#0 : the argument is picked up but not stored
On 6/17/2020 4:24 PM, Marcel Fabian Krüger wrote:
How does this work with mark nodes? Their mark field has a table
containing triples of command, character and "cs" value. How can the
actual csname of a controlsequence be extracted from this in LuaMetaTeX?
at the token ends marks
gt; > again
> > >
> > > > Beside that, I noticed a smaller weird thing when using LuaMetaTeX in
> > > > ini
> > > > mode without Context: The default mathcodes for digits and letters have
> > > > their class and family values switched. So e.
On 6/17/2020 12:10 PM, Marcel Fabian Krüger wrote:
On Mon, Jun 15, 2020 at 04:16:06PM +0200, Hans Hagen wrote:
ah, i removed some doee that i though was never seen; i'll add that bit
again
Beside that, I noticed a smaller weird thing when using LuaMetaTeX in ini
mode without Context
ue?
>
> Many thanks for your help,
>
> Pablo
Hi Pablo,
I fear I don't understand what issue you mean, therefore I append my output
here.
I'm using:
LuaMetaTeX, Version 2.04.02
ConTeXt ver: 2020.02.17 19:36 MKIV beta fmt: 2020.2.23
Best wishes,
Rudol
Hi,
in the latest luametatex version, \the\font does ... something weird:
E.g. with a current, fully updated lmtx, I get for
\starttext
\showthe\font
\stoptext
the output
> }\ifempty \currentstyleparameter \else \dousecurrentstyleparameter \fi
instead of the expected
> \3>modern-d
On 6/11/2020 10:47 PM, Marcel Fabian Krüger wrote:
The following document:
\starttext
\def\mymacro#1 bc{}
{\mymacro a b bc}
\stoptext
used to work and lead to no output. But in the new luametatex version,
it complains about "! Argument of \mymacro has an extra }" as if it
doesn't se
nd ^^ is the only way to get
that without introducing actual changes to behavior.
I had another issue with the latest luametatex:
The following document:
\starttext
\def\mymacro#1 bc{}
{\mymacro a b bc}
\stoptext
used to work and lead to no output. But in the new luametatex version,
it complains about
I run the "Userland" App from Playstore.
That App integrates well with Android.
I can edit with vim in the kali linux terminal or with any other Editor for
Android like Jota+.
I can try to compile the luametatex manual and send you the results.
Greetings Lutz
Am 10. Juni 2020 19:
, but how
about the disk. How do you edit on such a device?
(Over the time lmtx became more efficient in terms on memory (access)
and such. Compiling the luametatex manual on the RPI 4 (somewhat
overclocked) takes 3 times when my laptop does which I consider okay,
although the aim of course
this
This is LuaMetaTeX, Version 2.06.07
system > ConTeXt ver: 2020.06.10
Seems OK to me.
I get the same result with LuaTeX+MkIV 2020-05-08 and LMTX 2020-06-10,
even commenting out \dontleavehmode.
The only difference is the figure color: blue for LMTX, yellow for MkIV.
Ma
this
This is LuaMetaTeX, Version 2.06.07
system > ConTeXt ver: 2020.06.10
No problem here (but the version from May a problem).
mtx-context | current version: 2020.06.10 12:26
Wolfgang
___
If your quest
figure-framedtext.tex
In the above example the fix is to add \dontleavehmode between the figue and
the framedtext. If one comments out that line then the issue can be seen.
Thanks in advance for any help: Otared K.
can others confirm this
This is LuaMetaTeX, Version 2.06.07
system
e meaningful
> and robust subsystem (basically getting rid of funny numbers) ... this
> also will be discussed in an evenmore chapter .. not that users need it
> (i think)
>
> - as a side effect (or necessity) some low level recoding (and
> abstraction) had to happen but as far as we
nd it was all doable
because most of the preparation was already done over the last years
- in the process we got rid of a traditional tex data structure that was
left over from the 32 bit times but no longer needed in our 64 bit
luatex/luametatex universe (i might backport that simplificati
On 6/10/2020 7:49 AM, Jairo A. del Rio wrote:
Hi list! I'm curious about vertical typesetting in ConTeXt. As far as I
know, LuaTeX supports four text directions, but LTL is broken for Manchu
script (letters are displayed unjoined in LTL mode) and LuaMetaTeX does
not support vertical directions
Hi list! I'm curious about vertical typesetting in ConTeXt. As far as I
know, LuaTeX supports four text directions, but LTL is broken for Manchu
script (letters are displayed unjoined in LTL mode) and LuaMetaTeX does not
support vertical directions anymore, at least as primitives.
I found
11:34 AM, Otared Kavian wrote:
>> Hi all,
>> When I run
>> sh install.sh
>> in order to update my installation of LuaMetaTeX, I keep getting version
>> 2020.05.25 23:39.
>> Is this the latest version, or have I an issue with the install script?
> There hav
On 6/7/2020 11:34 AM, Otared Kavian wrote:
Hi all,
When I run
sh install.sh
in order to update my installation of LuaMetaTeX, I keep getting version
2020.05.25 23:39.
Is this the latest version, or have I an issue with the install script?
There have been no updates last week
Hi all,
When I run
sh install.sh
in order to update my installation of LuaMetaTeX, I keep getting version
2020.05.25 23:39.
Is this the latest version, or have I an issue with the install script?
Thanks in advance for any help: Otared K
In the current beta ( LuaMetaTeX, Version 2.06.05),
\m{\frac{28}{8\times29}}
puts the numerator and denominator too close to the dividing line.
Similarly for the variants of \frac and \over.
\m{{28}\over{8\times29}}
Alan
development of LuaMetaTeX, ConTeXt, and
everything related. Each meeting is source of inspiration for everybody,
from beginner to expert. Friendly company is always looking for meeting new
participants, users of LuaTeX, LuaMetaTeX, ConTeXt, Metapost, etc.
There is a special discount for those, who attend
uot;ξ" with an ASCII character.
Could this be fixed or is it really a limiatation of Windows?
It depends on the version and engine. [...]
In luametatex things are different. There all windows specific
operations have wide-character support, that is, the utf8 goes via utf16
and codepages and such:
" with an ASCII character.
>>
>> Could this be fixed or is it really a limiatation of Windows?
> It depends on the version and engine. [...]
> In luametatex things are different. There all windows specific
> operations have wide-character support, that is, the utf8 goes via
names here) but I trust his (always done) testing
of context. That will trickle into future binaries (which is somewhat
tricky as we have experimental as well as current).
In luametatex things are different. There all windows specific
operations have wide-character support, that is, the utf
On 5/28/2020 4:03 PM, Marcel Fabian Krüger wrote:
Hi,
I had two issues with luametatex:
The manual documents getters and setters for the directions:
The direction states can be queried and set with:
tex.gettextdir() tex.getpardir() tex.setmathdir()
tex.getlinedir() tex.settextdir
Hi,
I had two issues with luametatex:
The manual documents getters and setters for the directions:
The direction states can be queried and set with:
tex.gettextdir() tex.getpardir() tex.setmathdir()
tex.getlinedir() tex.settextdir() tex.setpardir()
tex.getmathdir() tex.setlinedir
Hi!
LMTX and MkIV behave differently if dots are used in the file
name. Example:
printf '%s\n' '\starttext\null\stoptext' > foo.10.tex && context foo.10.tex
MkIV: → foo.10.pdf
LMTX: → foo.pdf
Is this intentional?
This is LuaMetaTeX, Version 2.06.05
current version: 2020.05.25 2
rttext
\bTABLE
\bTR
\bTD \samplefile{knuth} \eTD
\bTD \samplefile{knuth} \eTD
\eTR
\eTABLE
\stoptext
This is LuaMetaTeX, Version 2.06.05
current version: 2020.05.25 23:39
Marco
___
I
sy because already reads the first line of the document
> for special setting (e.g. the engine) but anything which is set in the
> document requires more work because you don't know the new name *before*
> LuaTeX or LuaMetaTeX create the PDF.
You don’t need to know the
at contradicts the mode approach. It would be nice if we could set (or can
>> we?) the result from within the product, depending on a mode – since the
>> product is renamed only later anyway, that could be viable.
> This addition is easy because already reads the first line of the document
>
s addition is easy because already reads the first line of the
document for special setting (e.g. the engine) but anything which is set
in the document requires more work because you don't know the new name
*befor
, Version 1.13.0 (TeX Live 2021/dev)
> For ConTeXt (LMTX): This is LuaMetaTeX, Version 2.06.03
>
> El mié., 20 de may. de 2020 a la(s) 16:25, Hans Hagen (j.ha...@xs4all.nl)
> escribió:
>
>> On 5/20/2020 10:26 PM, Jairo A. del Rio wrote:
>> > I did. It turns out that instal
Info from \luatexbanner
For ConTeXt (LuaTeX): This is LuaTeX, Version 1.13.0 (TeX Live 2021/dev)
For ConTeXt (LMTX): This is LuaMetaTeX, Version 2.06.03
El mié., 20 de may. de 2020 a la(s) 16:25, Hans Hagen (j.ha...@xs4all.nl)
escribió:
> On 5/20/2020 10:26 PM, Jairo A. del Rio wrote:
> &
s not working at all. I get this error:
>>
>> mtx-context | processing extra: mtx-context-select.tex
>> mtx-context | redirect luametatex -> luatex: luatex --luaonly
>> "/opt/context-lmtx/tex/texmf-linux-64/bin/mtxrun.lua" --script mtx-context
>
of the returned table. But that never happens (This might be a related
bug: In my experiments, even for files loaded with `\input`, the close
function is never called.) and the issue seems to occur even if there is
no real file opened for this. So I don't see why LuaMetaTeX should call
fclose here at all
at all. I get this error:
mtx-context | processing extra: mtx-context-select.tex
mtx-context | redirect luametatex -> luatex: luatex --luaonly
"/opt/context-lmtx/tex/texmf-linux-64/bin/mtxrun.lua" --script mtx-context
--extra=select --selection=2 file.pdf --redirecte
`open_data_file` callback, so even if they
are closed they probably should be closed by calling the `.close` member
of the returned table. But that never happens (This might be a related
bug: In my experiments, even for files loaded with `\input`, the close
function is never called.) and the i
{paperformat_print}{A4}]
\setuppaper
[offset=\getdocumentargumentdefault{paperformat_to}{0pt}]
With LMTX, --extra=select is not working at all. I get this error:
mtx-context | processing extra: mtx-context-select.tex
mtx-context | redirect luametatex -> luatex: luatex --luaonly
"/opt
system (linux x64, latest lmtx) this results in
mtx-context | fatal error: return code: 139
Running the command after "executing runner 'run luametatex format':"
directly gives
segmentation fault (core dumped)
/home/marcel/lmtx-install/tex/texmf-linux-64/bin/luametatexcon
the binary from the following link but only the 32bit
version for Windows is up-to-date.
http://dl.contextgarden.net/build/luametatex/
Wolfgang,
many thanks for the information.
Pablo
--
http://www.ousia.tk
but only the 32bit
version for Windows is up-to-date.
http://dl.contextgarden.net/build/luametatex/
Wolfgang,
many thanks for the information.
Pablo
--
http://www.ousia.tk
___
Hallelulah! I now have a working LMTX again
link but only the 32bit
> version for Windows is up-to-date.
>
> http://dl.contextgarden.net/build/luametatex/
Wolfgang,
many thanks for the information.
Pablo
--
http://www.ousia.tk
___
If your question is of inter
download the binary from the following link but only the 32bit
version for Windows is up-to-date.
http://dl.contextgarden.net/build/luametatex/
Wolfgang
___
If your question is of interest to others as well, please add
2020-05-19 02:13:54.961276226 -0400
+++ /opt/luametatex/texmf-context/tex/context/base/mkiv/back-exp.lua
2020-05-19 02:13:01.687385009 -0400
@@ -2305,8 +2305,10 @@
if not p then
-- skip
elseif exportproperties == v_yes
/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex
resolvers | formats | luatex engine: luametatex
resolvers | formats | lua startup file :
C:/Users/MADELEN/Downloads/context-win64/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua
resolvers | formats | context file :
C
| binary path : C:/lmtx/tex/texmf-win64/bin
resolvers | formats | format path :
C:/lmtx/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1f32e/formats/luametatex
Dear list,
the “LuaMeTaTeX Reference Manual” describes that the command line
argument "--nodates" removes time dependent information in the output file.
I’m afraid it doesn’t work. "\enabledirectives[backend.date=no]" doesn’t
work either.
This is really useful to be able t
compiler under WLS (1). I also compile native binaries (a little
slower than the cross compiled but a smaller file) and clang binaries
(much slower and larger). The farm also has a windows set up now for
luametatex but I just use the ones I make here. So, what gets shipped,
the mingw ones, should
On 5/9/2020 6:26 PM, Giulio Bertellini wrote:
>> sh-3.2# context metafun
Ha, I admit that I never tried that yet with lmtx. (The reason is that I
then have to enter updating mode for all these new features. More
something for end-of-the-year dark evenings with a stack of new cd's.)
>>
On 5/9/2020 12:26, Giulio Bertellini wrote:
*
*
*about LuaMetaTeX, Version 2.06.02* On Mac OS Catalina 10.15.4 .
Hope this may convey some useful information. On Mac OS Catalina
10.15.4 ( Mac mini late 2012, I5, 16GB RAM), using the current LMTX
version just downloaded from Pragma Ade, I
*about LuaMetaTeX, Version 2.06.02* On Mac OS Catalina 10.15.4 .
Hope this may convey some useful information. On Mac OS Catalina 10.15.4 (
Mac mini late 2012, I5, 16GB RAM), using the current LMTX version just
downloaded from Pragma Ade, I installed Context LMTX and tested the
download
On 5/9/2020 09:33, Hans Hagen wrote:
On 5/9/2020 3:27 PM, Rik Kabel wrote:
On 5/9/2020 02:52, Hans Hagen wrote:
looks like a wrong binary .. should be 2.06.02 .. can you try this
binary:
http://dl.contextgarden.net/build/luametatex/x86_64-darwin/
(the farm generates two binaries for osx
On 5/9/2020 3:27 PM, Rik Kabel wrote:
On 5/9/2020 02:52, Hans Hagen wrote:
looks like a wrong binary .. should be 2.06.02 .. can you try this
binary:
http://dl.contextgarden.net/build/luametatex/x86_64-darwin/
(the farm generates two binaries for osx and it looks like the legacy
machine
On 5/9/2020 02:52, Hans Hagen wrote:
looks like a wrong binary .. should be 2.06.02 .. can you try this
binary:
http://dl.contextgarden.net/build/luametatex/x86_64-darwin/
(the farm generates two binaries for osx and it looks like the legacy
machine has gone off line which happens when osx
Hi Benjamin,
Thanks for sharing your nice code, which is very useful.
However I wanted to let you know that it seems it does not work correctly with
LuaMetaTeX version 2020.04.30 11:10, even though it works fine with ConTeXt
mkiv.
Best regards: Otared K.
> On 9 May 2020, at 12:39, Benja
On 5/9/2020 4:50 AM, Jeong Dal wrote:
Hi,
I tried to update luametatex which was running well(it was installed
following the process in the wiki>installation> MacOsX catalina), but I
got the following error after all the files are downloaded.
resolvers > lua > loading f
Hi,
I tried to update luametatex which was running well(it was installed following
the process in the wiki>installation> MacOsX catalina), but I got the following
error after all the files are downloaded.
resolvers > lua > loading file
'/Users/graph/ConTeXtL/tex/texmf
/tex/texmf-context/tex/context/base/mkiv/l-package.lua:325: error
loading module 'mapm' from file './mapm.so':
./mapm.so: undefined symbol: lua_settop
I believe that the luametatex binary is stripped, so there any unused symbol
is removed.
Aditya
hat doesn't work out)
luajittex has a limited stack of 8000 so it will also crash
luametatex uses lua 5.4 which uses a bit different stack model and can't
go that high (it has a default of 2000 but i will bnump that to 6000
which still seems to work ok, that way i get upto a 120 maze)
(new lmtx uploa
My update script reports:
2020-04-27T12:40:53 ConTeXt updated from 2020.04.19T19:43 to
2020.04.26T19:59
2020-04-27T12:40:53 LuaMetaTeX updated from 2.05.02 to 2.05.01
2020-04-27T12:40:53 LuaMetaTeX functionality updated from 20200413
to 20200402
Is this an intentional rollback
be an interesting new
(luametatex) option as it saves kerns in some cases)
My use cases of negative vrule is a little tricky. I'm trying to comply with
W3C's [Requirements for Japanese Text Layout](https://www.w3.org/TR/jlreq/).
It states that
In principle, closing brackets (cl-02), commas (cl
, the result looks as if there is no `\vrule' between `a' and `b'. And if
I run with `context --engine=luatex', the expected result is back. I have
checked the luametatex manual but it doesn't seem to mention the difference. My
luametatex version is
mkiv lua stats > used engine: luametatex version: 2.0
, the result looks as if there is no `\vrule' between `a' and `b'. And if
I run with `context --engine=luatex', the expected result is back. I have
checked the luametatex manual but it doesn't seem to mention the difference. My
luametatex version is
mkiv lua stats > used engine: luametatex vers
801 - 900 of 1150 matches
Mail list logo
