t-win64.zip.
>
> Having said that, the latest problem with the update has to do with an
> updated luametatex binary, so your method might have worked by
> updating the binary with the unzip, even if it is not a "fresh"
> install.
For information:
I tried updating by downl
llation and run install.bat to create a new
> distribution?
This is not a *fresh* install. In fact, you can simply run
./install.bat - there is no need to download context-win64.zip.
Having said that, the latest problem with the update has to do with an
updated luametatex binary, so your method mi
had seen it yet. Can
anyone confirm (or yell “works for me!”)?
You luametatex binary is too old and fails on the new
\advanceby command.
When I tried to update my current installation a few
moments ago the updater also failed to load the new
luametatex binary (I haven't tried to regenerat
On 1/8/2023 9:32 PM, Thomas A. Schmitz via ntg-context wrote:
On 1/8/23 21:02, Wolfgang Schuster via ntg-context wrote:
You luametatex binary is too old and fails on the new \advanceby command.
When I tried to update my current installation a few moments ago the
updater also failed to load
On 1/8/23 21:02, Wolfgang Schuster via ntg-context wrote:
You luametatex binary is too old and fails on the new \advanceby command.
When I tried to update my current installation a few moments ago the
updater also failed to load the new luametatex binary (I haven't tried
to regenerat
te_yes #1#2#3#4#5->\ifnum #1<#4\relax \global
\advanceby #1\plusone \permanent \global #3#5=#1\relax \else \writestatus {warning}{no
room f
But I was surprised that nobody else had seen it yet. Can anyone confirm (or
yell “works for me!”)?
You luametatex binary is too old and fail
gt;
>
> Running `lmtX' on `complexes_2' with
> ``/home/fabrice/LMTX/tex/texmf-linux-64/bin/mtxrun --autogenerate --script
> context --autopdf --purgeall complexes_2''
>
> resolvers | formats | executing runner 'run luametatex format':
> /home/f
--autopdf --purgeall complexes_2''
resolvers | formats | executing runner 'run luametatex format':
/home/fabrice/LMTX/tex/texmf-linux-64/bin/luametatex
--jobname="./complexes_2.tex"
--fmt=/home/fabrice/LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0
spoils spacing (as one can end up with an empty
nucleus inserted)
- in mkiv we use different magick than in mkii
anyway, in lmtx (luametatex) primes have been promoted to first class
citizens which means that a nucleus can have
- super(post)script
- sub(post)script
- superprescript
):
\starttext
\null
\stoptext
resolvers | formats | executing runner 'run luametatex format':
~/context/tex/texmf-linux-64/bin/luametatex --jobname="./a.tex"
--fmt=~/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en
| formats | executing runner 'run luametatex format':
~/context/tex/texmf-linux-64/bin/luametatex --jobname="./a.tex"
--fmt=~/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt
--lua=~/context/tex/texmf-c
the latest update broke my installation on linux.
How can I revert to a working version?
.F
$ context context18.tex
resolvers | globbing | confusing filename, name: 'CHANGELOG',
lower: 'changelog', already: 'ChangeLog'
resolvers | formats | ex
\getbuffer[b] \stop
\stoptext
$ context context\ 17.tex
resolvers | globbing | confusing filename, name: 'CHANGELOG',
lower: 'changelog', already: 'ChangeLog'
resolvers | formats | executing runner 'run luametatex format':
/home/vm/context/tex
nt. (It is mostly
about consistent support luametatex engine features but it might come in
handy.)
Some other 'new' things are too obscure to mention now,
Hans
-
Han
atest.
Many thanks again for the improvement,
Pabloresolvers | formats | executing runner 'run luametatex format': ~/context/tex/texmf-linux-64/bin/luametatex --jobname="./xml-context.xml" --fmt=~/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb
nt embedding time: 0.104 seconds, 23 fonts
mkiv lua stats > result saved in file: v32.pdf, compresslevel 0,
objectcompresslevel 0
mkiv lua stats > positions: 8572 collected, 4774 deltas, 8565 shared
partials, 305 partial entries
mkiv lua stats > used platform: linux-64, ty
a stats > result saved in file: v32.pdf, compresslevel 0,
objectcompresslevel 0
mkiv lua stats > positions: 8572 collected, 4774 deltas, 8565 shared
partials, 305 partial entries
mkiv lua stats > used platform: linux-64, type: unix, binary subtree:
texmf-linux-64
mkiv lua stats >
ed
partials, 304 partial entries
mkiv lua stats > used platform: linux-64, type: unix, binary subtree:
texmf-linux-64
mkiv lua stats > used engine: luametatex version: 2.1004, functionality
level: 20221214, format id: 679, compiler: gcc
mkiv lua stats > tex properties: 740852 hash
-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e
mkiv lua stats > resource resolver: loadtime 0.003 seconds, 0 scans with
scantime 0.000 seconds, 0 shared scans, 98 found files, scanned paths:
mkiv lua stats > stored bytecode data: 507 modules (0.117 sec), 106 tables
(0.0
gt; used cache path:
C:/ConTeXt_LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e
mkiv lua stats > resource resolver: loadtime 0.045 seconds, 1 scans
with scantime 0.037 seconds, 0 shared scans, 37 found files, scanned
paths: C:/Users/micro/texmf
mkiv lua stats
hes,
load time 1.076 seconds
which means that you don't run in compact mode
Indeed, I had a typo. Running with compact fonts, I get:
mkiv lua stats > used config file: selfautoparent:/texmf/web2c/texmfcnf.lua
mkiv lua stats > used cache path:
C:/ConTeXt_LMTX/tex/texmf-cache/lu
2c/texmfcnf.lua
mkiv lua stats > used cache path:
C:/ConTeXt_LMTX/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e
mkiv lua stats > resource resolver: loadtime 0.045 seconds, 1 scans
with scantime 0.037 seconds, 0 shared scans, 37 found files, scanned
nly tables are contents
and acronyms, and such, nothing complex. No graphics. Compact fonts are
enabled.
mkiv lua stats > used config file:
selfautoparent:/texmf/web2c/texmfcnf.lua
mkiv lua stats > used cache path:
C:/ConTeXt_LMTX/tex/texmf-cache/luametatex-cach
On 12/16/2022 8:36 PM, Henning Hraban Ramm via ntg-context wrote:
Am 16.12.22 um 18:10 schrieb Hans Hagen via ntg-context:
So the challenge is how to determine bottlenecks. Are there users on
this list that have document runs of more than 10 seconds (as
reference: the luametatex manual takes
Am 16.12.22 um 18:10 schrieb Hans Hagen via ntg-context:
So the challenge is how to determine bottlenecks. Are there users on
this list that have document runs of more than 10 seconds (as reference:
the luametatex manual takes < 9 seconds for 350 pages and loads plenty
fonts and has m
Hi,
I'm (occasionally) trying to 'minimize' bottlenecks in the context /
luametatex code. This is kind of hard because both are rather efficient
already. On regular runs performance is probably okay but there are
cases when one has a large complex document (e.g. with many table
edocument'
...base/mkxl/lpdf-lmt.lmt:3413: in field '?'
...base/mkxl/luat-run.lmt:58: in function
<...ext/tex/texmf-context/tex/context/base/mkxl/luat-run.lmt:56>
mtx-context | fatal error: return code: 1
This crashes LuaMetaTeX but not LuaTeX.
i'll
7;
...base/mkxl/luat-run.lmt:58: in function
<...ext/tex/texmf-context/tex/context/base/mkxl/luat-run.lmt:56>
mtx-context | fatal error: return code: 1
This crashes LuaMetaTeX but not LuaTeX.
2. The other font is Recursive
(https://github.com/arrowtype/recursive/tree/mai
;
otf reader > fatal error in file
'/mnt/shared/lmtx/tex/texmf/fonts/data/public/dejavu/DejaVuSansMono.ttf': ...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:1040: attempt to call a nil value (field 'to16dot16')
It concerns several fonts, both my own and (as he
/tex/texmf/fonts/data/public/dejavu/DejaVuSansMono.ttf':
...e0dde776fb1556f32e/formats/luametatex/font-otr-macro.lua:1040:
attempt to call a nil value (field 'to16dot16')
It concerns several fonts, both my own and (as here) from the
installation, and the first error is always thi
ote:
> > Hi,
> >
> >> I want to simulate \hss in lua end in ConTeXt/luametatex environment.
> >> For example,
> >>
> >> ```ConTeXt
> >> a{\raise 1.5ex\hbox to 0pt{\hss b}}c
> >> ```
> >
> >> And in lua, I do as follows(pa
g it relative.
Best regards
Huang Fusyong(黄复雄)
Max Chernoff via ntg-context 于2022年11月11日周五 17:55写道：
>
> Hi,
>
> > I want to simulate \hss in lua end in ConTeXt/luametatex environment.
> > For example,
> >
> > ```ConTeXt
> > a{\raise 1.5ex\hbox to 0pt{\hss b}
On 11/11/2022 10:53 AM, Max Chernoff via ntg-context wrote:
Hi,
I want to simulate \hss in lua end in ConTeXt/luametatex environment.
For example,
```ConTeXt
a{\raise 1.5ex\hbox to 0pt{\hss b}}c
```
And in lua, I do as follows(part of my app seen in attachment):
Your code doesn&#
Hi,
> I want to simulate \hss in lua end in ConTeXt/luametatex environment.
> For example,
>
> ```ConTeXt
> a{\raise 1.5ex\hbox to 0pt{\hss b}}c
> ```
> And in lua, I do as follows(part of my app seen in attachment):
Your code doesn't compile as is. I think that thi
Hi list,
I want to simulate \hss in lua end in ConTeXt/luametatex environment.
For example,
```ConTeXt
a{\raise 1.5ex\hbox to 0pt{\hss b}}c
```
should get 'b' on top of 'a', as follows:
```pdf
b
ac
```
and in lua, I see a before "b" node, width
width:
On 11/7/2022 11:40 AM, Max Chernoff via ntg-context wrote:
Hi Hans,
Using node.setglue in LuaMetaTeX sets all of the glue components to
zero.
This example:
\startluacode
local stretch_order = "stretch_order"
local shrink_order = "shrink_or
Hi Hans,
Using node.setglue in LuaMetaTeX sets all of the glue components to
zero.
This example:
\startluacode
local stretch_order = "stretch_order"
local shrink_order = "shrink_order"
if status.luatex_engine == "luametatex" then
and
compatibility wrt dvi driver related features (i'm not even sure if
luametatex makes sense for other macro packages but we'll see, these
things happens outside my scope anyway)
Hans
-
Hi Hans,
> Anyway, I'll check it. Is anyone still using this "true" actually?
I've been playing around with LuaMetaLaTeX/LuaMetaPlain recently
https://github.com/zauguin/luametalatex
and plain.tex uses truein for typesetting the footnote rule. It's trivial
to fix that specific case, but
On 10/27/2022 8:11 AM, Max Chernoff via ntg-context wrote:
Hi Hans,
The unit scanner in LuaMetaTeX fails for any of the "true" dimensions.
With this test file:
\starttext
\vrule width 1truein height 1pt depth 0pt\relax
\vrule width 1in height 1pt depth
Hi Hans,
The unit scanner in LuaMetaTeX fails for any of the "true" dimensions.
With this test file:
\starttext
\vrule width 1truein height 1pt depth 0pt\relax
\vrule width 1in height 1pt depth 0pt\relax
\stoptext
I get this output:
tex error >
Dear Pablo,
Am Sun, Oct 16, 2022 at 08:43:25PM +0200 schrieb Pablo Rodriguez via
ntg-context:
> On 7/25/22 14:00, juh+ntg-context--- via ntg-context wrote:
> > [...]
> > They hint to LuaMetaTex as the cause of the problem. You can follow the
> > discussio
On 10/17/2022 8:43 AM, Otared Kavian via ntg-context wrote:
I use Lucida in my documents and did not notice any problem with the integrals
and other large operators.
Do you mean in the future I have to update to a new version of Lucida (and pay
again…) or will future versions of LuaMetaTeX
Lucida (and
> pay again…) or will future versions of LuaMetaTeX handle correctly large
> operators typeset in Lucida ?
In Lucida the integrals have almost been at the right place. See the
attached screenshot. To the left, the unfixed Lucida (first aligned at
the base line, and then centered a
Hi Mikael,
I use Lucida in my documents and did not notice any problem with the integrals
and other large operators.
Do you mean in the future I have to update to a new version of Lucida (and pay
again…) or will future versions of LuaMetaTeX handle correctly large operators
typeset in Lucida
On 7/25/22 14:00, juh+ntg-context--- via ntg-context wrote:
> [...]
> They hint to LuaMetaTex as the cause of the problem. You can follow the
> discussion here.
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=1781022
Hi juh,
this should have been fixed in current latest. So I
component file to the product PDF, I get the correct page but
> no highlighting.
>
> I am using TeXShop ver. 5.03—
> sync method: Both Pdf Sync and Search
> Alternative Path:
> /Users/bowen1/Applications/LuaMetaTeX/tex/texmf-osx-arm64/bin
>
> and a
happens when I sync from the PDf file to the component file, and
when I sync from the component file to the product PDF, I get the correct
page but no highlighting.
I am using TeXShop ver. 5.03—
sync method: Both Pdf Sync and Search
Alternative
Path: /Users/bowen1/Applications/LuaMetaTeX/tex/texmf
/luametatex what should be the LMTX source
(about 11MB).
It zips to 2 MB and totals to less of a picture on a fancy phone ...
Many thanks for your reply, Hans.
At least on my system, I think every file is downloaded uncompressed.
With a low speed connection (here, the service isn’t great all the
time
On 10/15/22 09:41, Hans Hagen via ntg-context wrote:
> On 10/14/2022 4:14 PM, Pablo Rodriguez via ntg-context wrote:
>> [...]
>> Many thanks for the new version, Hans.
>>
>> I have discovered that it includes in
>> tex/texmf-context/source/luametatex what should
[...]
Hi Roman,
I compiled your code with version from 2022.09.11 20:44.
I attach an overlay of the results from both LuaMeTaTeX (in red) and
LuaTeX (in darkgreen).
It seems that MkIV is doing fine, but LMTX isn’t aligning the dots (for
some reason unknown to me).
Latest from 2022.10.14 10:16 gives
progress, we will clean them up later) as
part of improving the rendering of math.
Many thanks for the new version, Hans.
I have discovered that it includes in
tex/texmf-context/source/luametatex what should be the LMTX source
(about 11MB).
It zips to 2 MB and totals to less of a picture on a
On 10/15/2022 12:33 AM, Max Chernoff via ntg-context wrote:
Hi Alan,
On Fri, 2022-10-14 at 16:20 -0600, Alan Braslau wrote:
On Fri, 14 Oct 2022 15:38:52 -0600
Max Chernoff via ntg-context wrote:
$ context --luatex test.tex
mtx-context | redirect luametatex -> luatex: lua
tunately have a new issue (probably for Hans or Mikael).
Running:
context --luatex empty.tex
where "empty.tex" is:
\starttext
\null
\stoptext
gives me this output:
mtx-context | redirect luametatex -> luatex: luatex --luaonly
"/opt/context/
tunately have a new issue (probably for Hans or Mikael).
Running:
context --luatex empty.tex
where "empty.tex" is:
\starttext
\null
\stoptext
gives me this output:
mtx-context | redirect luametatex -> luatex: luatex --luaonly
"/opt/context/tex
Hi Alan,
On Fri, 2022-10-14 at 16:20 -0600, Alan Braslau wrote:
> On Fri, 14 Oct 2022 15:38:52 -0600
> Max Chernoff via ntg-context wrote:
>
>
>$ context --luatex test.tex
>mtx-context | redirect luametatex -> luatex: luatex --luaonly
> "/opt/c
On Fri, 14 Oct 2022 15:38:52 -0600
Max Chernoff via ntg-context wrote:
$ context --luatex test.tex
mtx-context | redirect luametatex -> luatex: luatex --luaonly
"/opt/context/tex/texmf-linux-64/bin/mtxrun.lua" --script mtx-context --luatex
test.tex --redirec
Hi Pablo,
> I’m afraid that I cannot make latest from 2022.10.14 10:16 with LuaTeX.
>
> I’m on Linux64.
I've got the same configuration and I'm getting the same results:
$ context --luatex test.tex
mtx-context | redirect luametatex -> luatex: luatex --luao
th version from 2022.09.11 20:44.
I attach an overlay of the results from both LuaMeTaTeX (in red) and
LuaTeX (in darkgreen).
It seems that MkIV is doing fine, but LMTX isn’t aligning the dots (for
some reason unknown to me).
Latest from 2022.10.14 10:16 gives exactly the same result for LMTX, and
Mk
On Fri, 14 Oct 2022 16:14:01 +0200
Pablo Rodriguez via ntg-context wrote:
> I have discovered that it includes in
> tex/texmf-context/source/luametatex what should be the LMTX source
> (about 11MB).
>
> I wonder whether this could be made optional. Internet speed is not
> con
r) as
> part of improving the rendering of math.
Many thanks for the new version, Hans.
I have discovered that it includes in
tex/texmf-context/source/luametatex what should be the LMTX source
(about 11MB).
I wonder whether this could be made optional. Internet speed is not
constant where I live and
>
>> On 10/9/2022 8:03 AM, Max Chernoff via ntg-context wrote:
>>> Hi all,
>>>
>>>> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>>>>
>>>> Here's a tiny test document, I disabled PDF compression but it al
Hans Hagen via ntg-context writes:
> On 10/9/2022 8:03 AM, Max Chernoff via ntg-context wrote:
>> Hi all,
>>
>>> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>>>
>>> Here's a tiny test document, I disabled PDF compression but it
works.
The log tells me:
This is LuaTeX, Version 1.13.0 (TeX Live 2021)
Compiling with LMTX, i read:
ConTeXt ver: 2022.09.11 20:44 LMTX
And compiling with MkIV (of the TeX Live 2022):
This is LuaTeX, Version 1.15.0 (TeX live 2022)
in a setup where lmtx is leading mtxrun/context will use luame
On 10/9/2022 8:03 AM, Max Chernoff via ntg-context wrote:
Hi all,
I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
Here's a tiny test document, I disabled PDF compression but it also
doesn't work with the default settings.
\setupbackend[level=0,compresslevel=0]
\startt
Hi all,
> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>
> Here's a tiny test document, I disabled PDF compression but it also
> doesn't work with the default settings.
>
> \setupbackend[level=0,compresslevel=0]
> \starttext
> Just a line of t
whether bisecting the snapshot-repo would work.
>> But I only have one LMTX binary; this font handling should be all in
>> lua code tho?
>
> It makes no sense to compare luametatex and luatex .. it's different
> machinery.
>
> Btw, some in the thread mention issues
e all in
lua code tho?
It makes no sense to compare luametatex and luatex .. it's different
machinery.
Btw, some in the thread mention issues (like bad looking heros shapes)
but in your case there is no print at all, so that is different. Isn't
there some error log in these
On 10/5/2022 6:02 PM, Pablo Rodriguez via ntg-context wrote:
It happens both with LuaMetaTeX and LuaTeX. When playing with certain
levels of zooming, some blank spots are displayed inside the characters
(printing is fine).
Such artifacts can result from operating in the extremes and one has
pTEXpage
\stoptext
It happens both with LuaMetaTeX and LuaTeX. When playing with certain
levels of zooming, some blank spots are displayed inside the characters
(printing is fine).
BTW, as Hans explained
(https://mailman.ntg.nl/pipermail/ntg-context/2022/106840.html), the
following top line avoids
Hans Hagen via ntg-context writes:
> On 10/3/2022 7:17 PM, Leah Neukirchen via ntg-context wrote:
>> Hi,
>> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>> Here's a tiny test document, I disabled PDF compression but it also
>> doesn't work with t
On 10/3/2022 7:17 PM, Leah Neukirchen via ntg-context wrote:
Hi,
I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
Here's a tiny test document, I disabled PDF compression but it also
doesn't work with the default settings.
\setupbackend[level=0,compresslevel=0]
\starttext
J
Leah Neukirchen via ntg-context writes:
> Hi,
>
> I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
>
> Here's a tiny test document, I disabled PDF compression but it also
> doesn't work with the default settings.
>
> \setupbackend[level=0,compressleve
Hi,
I use LuaMetaTeX 2.10 20220918 + ConTeXt LMTX 2022.09.11.
Here's a tiny test document, I disabled PDF compression but it also
doesn't work with the default settings.
\setupbackend[level=0,compresslevel=0]
\starttext
Just a line of text.
\stoptext
When I print this "directly
On Wed, Sep 28, 2022 at 03:59:07PM +0200, Hans Hagen via ntg-context wrote:
changed to have 'context file.txt' to compile using luatex instead of
LuaMetaTeX?
top line:
% engine=luatex
Thank you, I'll add that to my source files from now on.
but lmtx is and will stay as d
le only in LuaMetaTeX.
plenty (also font features) not in luatex indeed
I agree with Hans that LuaMetaTeX is here to stay. He may correct me,
but as far as I understand it, LuaMetaTeX is LuaTeX-2.0.
there maybe any other potentially undesirable side
> effect?
The main issue would be pretending to use with LuaTeX some features
available only in LuaMetaTeX.
> Also, I guess that can be configured somehow so, what would need to be
> changed to have 'context file.txt' to compile
how so, what would need to be
changed to have 'context file.txt' to compile using luatex instead of
LuaMetaTeX?
top line:
% engine=luatex
but lmtx is and will stay as default (btw, you don't run the latest
greatest)
Hans
--
work "out of the box" and
produce a correct and complete PDF output. Would it be possible to have
that changed? Or is there maybe any other potentially undesirable side
effect?
Also, I guess that can be configured somehow so, what would need to be
changed to have 'context file.
On Tue, Sep 27, 2022 at 04:03:06PM +0200, Pablo Rodriguez via ntg-context wrote:
Producer: LuaMetaTeX-2.09
No, this was compiled with LuaMetaTeX.
It looks so obvious now, but it didn't (to me) before. :-)
In that case, run "context --luatex --generate" first an
Hi,
At the ctx meeting we released luametatex, that is, the source code is
now in the context zip (so it grew a few MB). At the same time Mojca set
up some contextgarden repositories on github. We're working on a setup
for users to generate older snapshots, if needed (for instance be
On 9/26/22 20:26, Angel M Alganza via ntg-context wrote:
> On Mon, Sep 26, 2022 at 07:10:40PM +0200, Pablo Rodriguez via ntg-context
> wrote:
> [...]
>> There might be a workaround (or a way of testing this), compiling the
>> PDF document with LuaTeX instead of with LuaMetaTe
ion > 1.7
mtx-pdf | major version > 1
mtx-pdf | minor version > 7
mtx-pdf | number of pages > 1
mtx-pdf | title > a6
mtx-pdf | creator > LuaMetaTeX 2.09 20220429 + ConTeXt
LMTX 2022.05.11 11:36
mtx-p
1
mtx-pdf | minor version > 7
mtx-pdf | number of pages > 1
mtx-pdf | title > a6
mtx-pdf | creator > LuaMetaTeX 2.09 20220429 + ConTeXt LMTX
2022.05.11 11:36
mtx-pdf | producer > LuaMetaTeX-2.09
mtx-pdf | auth
uaTeX instead of with LuaMetaTeX.
It seems it is compiled with LuaTeX:
$ pdfinfo a6.pdf
Title: a6
Creator: LuaMetaTeX 2.09 20220429 + ConTeXt LMTX 2022.05.11 11:36
Producer: LuaMetaTeX-2.09
CreationDate: Tue Sep 20 07:19:29 2022 CEST
ModDate:Tue Sep 20 07:19:29 2022
version of your PDF document?
I think that your printer is having issues with the embedded font in
your PDF document.
There might be a workaround (or a way of testing this), compiling the
PDF document with LuaTeX instead of with LuaMetaTeX.
If you compile it invoking "context source.tex"
fonts: 3 files: xitsmath-bold.otf,
xitsmath-regular.otf, lato-regular.ttf
---
ConTeXt ver: 2022.09.11 20:44 LMTX - luametatex version: 2.1,
functionality level: 20220918:
mtxrun --script fonts --list --all --pattern=*lato*
identifier familyname fontname filename
Hi Hans,
I see that you've released the LuaMetaTeX source code, yay! I'm really
impressed with how easy it is to build, and with how quickly it builds.
Can you please apply this patch to the LuaMetaTeX source code:
~~~
Hi Mikael,
> I don't see this problem with the latest. Moreover, I think the
> version of luametatex was pushed to 2.10, so there might be a
> mis-match in your case. I hope it helps.
I just tried updating again, and it says that I'm up to date, but:
$ luametatex -
| formats | using lua stub file
> '/opt/context/tex/texmf-context/tex/context/base/mkxl/luat-cod.lmt'
>resolvers | formats | changing to format path
> '/home/max/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex'
>resol
ormats | changing to format path
'/home/max/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex'
resolvers | formats | executing runner 'make luametatex format':
/opt/context/tex/texmf-linux-64/bin/luametatex --ini
--lua=/opt/context/tex/texmf-
Hi Michal and Hans,
My LuaMetaTeX version (and ConTeXt LMTX...) was from 18.04.2022. That
was the reason...
As soon as I installed the fresh version, it started working properly,
even with my library build.
So next time before writing to list, I'll do the update and check first ;)
That
i have as it is how i compile luametatex)
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl |
empty page
>
> Best regards,
> Ivan
First, try without the \startTEXpage / \stopTEXpage, so you don't have
empty first page.
Now, as mentioned, the library loads correctly, but luametatex can't
read the binary structures passed in memory by zint. This can be due to
ABI
On 9/4/2022 1:36 AM, Ivan Pešić via ntg-context wrote:
Hi Pablo,
I'm resurrecting this thread, as I've just managed to get some progress
on Windows with zint in LMTX.
The thing is that you need 64-bit DLL, because LuaMetaTex is built for
64-bit architecture on Windows.
As it is not
Hi Pablo,
I'm resurrecting this thread, as I've just managed to get some progress
on Windows with zint in LMTX.
The thing is that you need 64-bit DLL, because LuaMetaTex is built for
64-bit architecture on Windows.
As it is not available, I built 64-bit zint.dll (and zlib + libpng)
, creators are "LuaMetaTeX 2.10 20220818 + ConTeXt
LMTX 2022.08.25 17:43".
I don’t know whether I’m missing something (in that case, the error
message should be more verbose).
Many thanks for your help,
you're missing an \egroup
\starttext
\doloopoverlist{\tf,\ss,\tt}
}\egroup}
\stoptext
I get the following error:
mtx-context | fatal error: return code: 1
But when checking the sources, no error is found:
$ mtxrun --script check test-file.tex
no error
Just in case it helps, creators are "LuaMetaTeX 2.10 20220818 + ConTeXt
LMTX 2022.08.25 17:43
age descriptions", so maybe even a Makefile like
> > I had wouldn't be needed.
>
> just a note: the mtxrun[.exe] and context[.exe] commands are not really
> wrappers but symlinks to the binary luametatex[.exe] (i didn't test if
> mtxrun.lua and context.lua can
ntext[.exe] commands are not really
wrappers but symlinks to the binary luametatex[.exe] (i didn't test if
mtxrun.lua and context.lua can be symlinks but that are to be in the
same path in order to be seen)
one can actually use the default texmf.cnf if one sets TEXMF or one of
its co
301 - 400 of 1020 matches
Mail list logo
