er 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 (
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 printer?
Hans
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
\stopTEXpage
\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 avo
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 the default
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
Just a line
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,compresslevel=0]
&g
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" (i.
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 default
To bad
lable 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.
y 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 using luatex instead of
&
uld 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
-
t 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.txt' to compile usin
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 and the
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 because
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 Lua
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
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 CEST
f 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", use &quo
-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
subfont instances
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:
diff
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
ub 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'
> resolvers | formats | executing runner 'make luam
/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-context/tex/context/base/mkxl/luat-cod.lmt
/opt/context/tex
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
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 | www.pragma
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 mismatch for d
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 available
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) from
, 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 be symlink
[.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 companion
assets. This would require special care both from me
and the hypothetical packagers who would have to use the less
discoverable asset instead of the standard "git(hub) archive" way.
Anyway I think that a much better solution can be made once luametatex
source code becomes available -
most users won't
> notice many differences from MkXL/LMTX, the "experimental" version.
>
> By policy, TeX Live only updates its binaries once per year. This would
> be pretty much unworkable with LuaMetaTeX due to its frequent upgrades.
> At some point when LuaMetaTeX is st
> Live only includes MkIV, the "stable" version, but most users won't
> notice many differences from MkXL/LMTX, the "experimental" version.
>
> By policy, TeX Live only updates its binaries once per year. This would
> be pretty much unworkable with LuaMetaTeX due to it
; version, but most users won't
notice many differences from MkXL/LMTX, the "experimental" version.
By policy, TeX Live only updates its binaries once per year. This would
be pretty much unworkable with LuaMetaTeX due to its frequent upgrades.
At some point when LuaMetaTeX is stable
mmands.
>
> ```
> tar xf luametatex-2022.06.tar.xz
> cd /path/to/luametatex-2022.06
> make
> cp luametatex /usr/bin
>
> tar xf context-2022.06.tar.xz
> cd /path/to/context-2022.06
> cp -r font /path/to/usr/share/texmf-dist
> ...
> ```
>
> I want somet
ot; of the current
> ConTeXt (or make use of the public git mirror)
> - you currently can't build luametatex binary from source, you would
> have to download it prebuilt (and also keep snapshots of it)
> - different directory structure expected by Linux distributions (FHS,
> "file
):
%%%begin error
resolvers | formats | executing runner 'run luametatex format':
D:/venvs/context-win64/tex/texmf-win64/bin/luametatex
--jobname="d:/ah21/TEX/vertical-and-ruby-examples/ruby.lmtx"
--fmt=D:/venvs/context-win64/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776
d to maintain your own "snapshots" of the current
ConTeXt (or make use of the public git mirror)
- you currently can't build luametatex binary from source, you would
have to download it prebuilt (and also keep snapshots of it)
- different directory structure expected by Linux distributions
e relevant bin location
> - set symlinks from luametatex to mtsrun and context
> - copy mtxrun.lua and context.lue there too
> - adapt your path
> - maybe add texmf-fonts and texmf-projects
> - and you're done
>
> so, something like that, or ... use the online installer instead.
>
is:
- unzip the main zip file
- goto the source subtree
- run build.sh (assumes compiler and cmake installed)
- move the binary file to the relevant bin location
- set symlinks from luametatex to mtsrun and context
- copy mtxrun.lua and context.lue there too
- adapt your path
- maybe add texmf-fonts
022 4:08 PM, amano.kenji wrote:
>
> > Sorry for spamming the list a little bit.
> >
> > If there was something like
> > https://www.linuxfromscratch.org/lfs/view/stable/chapter06/ncurses.html for
> > ConTeXt and luametatex (binary), then distribution maintainer
:16 PM, Hans Hagen
wrote:
> On 8/18/2022 4:08 PM, amano.kenji wrote:
>
> > Sorry for spamming the list a little bit.
> >
> > If there was something like
> > https://www.linuxfromscratch.org/lfs/view/stable/chapter06/ncurses.html for
> > ConTeXt and lu
On 8/18/2022 4:08 PM, amano.kenji wrote:
Sorry for spamming the list a little bit.
If there was something like
https://www.linuxfromscratch.org/lfs/view/stable/chapter06/ncurses.html for
ConTeXt and luametatex (binary), then distribution maintainers can make
packages for ConTeXt easily.
I
Sorry for spamming the list a little bit.
If there was something like
https://www.linuxfromscratch.org/lfs/view/stable/chapter06/ncurses.html for
ConTeXt and luametatex (binary), then distribution maintainers can make
packages for ConTeXt easily.
I don't know TeX/TeXLive/kpathsea/ConTeXt
Imagine installation instructions given by linux from scratch.
install.sh is like `apt-get install ConTeXt`.
Linux from scratch would document the following commands.
```
tar xf luametatex-2022.06.tar.xz
cd /path/to/luametatex-2022.06
make
cp luametatex /usr/bin
tar xf context-2022.06.tar.xz
luametatex to /usr/bin is going to be easy.
I never had to understand TexLive/ConTeXt directory structure because I just
used TexLive OS package. Now, I'm stuck reverse-engineering a black box.
Am I supposed to execute the following commands in
https://github.com/contextgarden/context-mirror
butions are very particular
about this.
I cannot understand the thrust of this thread.
It appears that the only issue for now concerns the distribution of the
luametatex source tree. This is not yet the case as luametatex has been
undergoing much experimentation. A classic opensource deposito
By the way, all POSIX-like opearting systems including BSDs and linux
distributions share one way of making system packages.
For all POSIX-like operating systems, a simple Makefile can build LuaMetaTex.
Since each linux distribution may have a slightly different directory
structure, it would
een discussing the binary part wrt githib but even
with the relatively small luametatex binaries it's a bit of a challenge
on git. We have some ideas but need time to do it and it doesn't have a
high priority. I expect that one of these days the binaries won't change
that much. We're still enha
e
>
> there are some boundary conditions:
>
> - we use mtxrun as runner and that one used luatex as lua engine
> - this means that mtxrun[.lua] has to be in the same path as the binary
>
> in lmtx we even go a bit further:
>
> - in lmtx there is mtxrun.lua
> - as
ies or
symlinks to luametatex in the same path
- this is the same on unix and windows
in lmtx luametatex is also used as runner for mkiv when installed
on unix i normally just install the minimal tree and then either add the
bin path to the path or just run mtxrun fully qualified (actually alw
http://lmtx.pragma-ade.nl/install-lmtx/texmf-context.zip is not versioned.
If the file changes later, linux distributions refuse to use the file.
I wish ConTeXt and LuaMetaTex were versioned and provided `offline` build
instructions. The vast majority of programs are versioned and can be built
Hi Hans,
> > First, how do I get an insert's class/type from the "insert" nodes on
> > the page? With LuaTeX, the insert's class/type is the same as the
> > subtype of the "ins" nodes, but the subtype of the "insert" nodes is
> > always ze
Okay, I'm seeing a few separate issues here.
1. Gentoo expects to compile everything from source.
This isn't an option here since LuaMetaTeX doesn't have any source
available (yet). So for the time being, you'll need to use the provided
binaries. These support pretty much every
On 8/15/2022 8:18 AM, Max Chernoff via ntg-context wrote:
Hi all,
I'm trying to manipulate some inserts from Lua in LuaMetaTeX, and I'm
having some problems that I'm not having with LuaTeX.
First, how do I get an insert's class/type from the "insert" nodes on
the page? W
Hi all,
I'm trying to manipulate some inserts from Lua in LuaMetaTeX, and I'm
having some problems that I'm not having with LuaTeX.
First, how do I get an insert's class/type from the "insert" nodes on
the page? With LuaTeX, the insert's class/type is the same as the
subtype of the &
On 8/5/2022 4:37 PM, Aditya Mahajan via ntg-context wrote:
Hi,
I cannot view the onandon.pdf manual. pdfinfo says that it a malformed PDF.
bah, probably i ran some test .. some code there only works in older
luametatex .. (keep in mind that i seldom run these manuals as a whole
so sometimes
fonts are
set up that way). In lmtx (luametatex) primes are native features and
assume dimensions that we can work with (primes and minutes are a
typical example of messed up math unicode).
Hans
taking advantage of floating-point MetaPost (thus
> simplified).
>
>
>
> I have been working on a completely new luagraph module that does much
> in lua. It has, notably, arbitrary coordinate systems.
>
> This has been a moving target as I put more and more into lua
> and less
s much
in lua. It has, notably, arbitrary coordinate systems.
This has been a moving target as I put more and more into lua
and less and less in Metapost. I have also been playing chase with the
development of luametatex (and have fallen behind).
On 7/25/22 14:00, juh+ntg-context--- via ntg-context wrote:
>
> I reported the bug to Mozilla and they answered very fast.
>
> Sadly up too now without a good solution.
Many thanks for the bug report.
> They hint to LuaMetaTex as the cause of the problem. You can follow the
> d
I reported the bug to Mozilla and they answered very fast.
Sadly up too now without a good solution.
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
juh
hould not run/mix lmtx with texlive
- we use luametatex as runner for both luametatex and luatex runs
- mtxrun.lua and context.lua are both in the bin path (as usual)
- mtxrun.exe and context.exe are symlinks to luametatex.exe
that is the same for all platforms but in tex live on windows there is
;> Pablo
>
> Hi Pablo and Haram,
>
> When I was running mtxrun --generate, there was an interference with TeX
> Live, so I uninstalled it, then it worked. I do not know if that time I did
> run mtxrun. But under TeXworks when I selected context as program it kept
> electing luam
ext upload will have a prepare helper
print("=")
local h = nodes.copylist(head)
tex.preparelinebreak(h)
local n = tex.linebreak(h)
nodes.flushlist(n)
print("====
guide at:
https://github.com/AKielhorn/Context-Intro
Just for the record: luametatex is *not* optimized for context, it just
provides (rather generic) stuff not present in other engines that we can
benefit from. That said: of course after decades of context we know what
is missing in tex that we
would silently
eat entire paragraphs, which was very not good. Luckily that problem is
fixed now.
And finally, thanks for all your work with LuaMetaTeX. This new engine
is quite nice to work with and has some pretty cool new features.
Thanks,
-- Max
___
en stuff to m-oldmath in due time
>
> We paid a lot of attention to details of positioning, sizing and spacing
> of glyphs. We do have some documents in the making that describe this
> (some are in the ontarget namespace) and the second half of this year we
> use for writin
this
(some are in the ontarget namespace) and the second half of this year we
use for writing a math manual (Mikael) and updating the luametatex
manual (Hans). For sure we will run into unforseen issues, come up with
additional things and try to please users who have demands. There are
'hidden
d t :help "Run context (MarkIV)")
("luametatex"
"context --purgeall %t"
TeX-run-command t :help "Run context (LMTX)")
) TeX-command-list
)
)
)
--
Assuming that the runner (mtxrun or context) is an alias to luametatex,
y
You can try adding a TeX-command with this:
(eval-after-load "context"
'(setq TeX-command-list
(append
'(
("context"
"context --purgeall %t"
TeX-run-command t :help "Run context (MarkIV)")
("luametatex"
&
It seems to use the old texexec with your configuration example
Running `ConTeXt Full' on `rutor' with ``texexec --engine=luametatex
--interface=en --nonstop rutor.tex''
/bin/sh: texexec: command not found
TeX Output exited abnormally with code 127 at Sat Jul 2 09:50:33
> 1 juli 2022 kl.
Curious - I just tried on another computer (Mac) using the exact same
source and MS .ttf files and I do not get bold regular text. Both use
updated lmtx. Something odd going on (that I will try to figure out).
Clearing the luametatex cache corrected the problem - sorry all for the
noise.
Alan
terference with TeX Live, so I uninstalled it, then it
worked. I do not know if that time I did run mtxrun. But
under TeXworks when I selected context as program it kept
electing luametatex, and it didn't work; so I manually wrote
"context" and it worked!!
Thanks f
gt; If I change line 81 of
>>
>> texmf-context/scripts/context/lua/mtx-cache.lua
>> [...]
>> to
>> if find(filename,"luametatex%-cache") then
>> the problem appears to be fixed.
> maybe can you test with
>
> LUA
ge line 81 of
texmf-context/scripts/context/lua/mtx-cache.lua
from
if find(filename,"luatex%-cache") then
to
if find(filename,"luametatex%-cache") then
the problem appears to be fixed.
maybe can you test with
LUATEXENGINE .. "
.lua
from
if find(filename,"luatex%-cache") then
to
if find(filename,"luametatex%-cache") then
the problem appears to be fixed.
-- Max
___
If your question is of interest
ph_id then
>back_chars = back_chars + 1
>end
>
>n = n.prev
>end
>
> width = 0
>chars = 0
>end
>
>
s; if not, there's a more complex fix that I can try.
Unfortunately, I don't know what to change; I know a bit about "glyph" and "glue", but
what is "disc" and would it help here?
"disc" nodes are "discretionaries", which are usually potential hyphen
On 6/24/2022 8:28 AM, Max Chernoff wrote:
2. The LuaMetaTeX manual says that "pre_linebreak_filter" is called
_after_ the parfillskip glue has been added, but this doesn't seem
to be the case. With LuaLaTeX/Plain LuaTeX/MkIV, this is true, but
the node l
is mostly copied from an earlier email, "Callbacks (and
nodes) in LuaMetaTeX")
1. In LMTX, calling "tex.linebreak" produces a
luatex warning > tex: left parfill skip is gone
warning. I don't get this warning in Plain LuaTeX, LuaLaTeX, or
MkIV, so I t
; . context-mode))
(eval-after-load 'tex
'(add-to-list
'TeX-command-list
'("LuaMetaTeX"
"C:\\Users\\Leung\\AppData\\Local\\Programs\\ConTeXt\\tex\\texmf-win64\\bin\\mtxrun.exe
--autogenerate --script context --autopdf %t"
TeX-run-command nil (context-mode) :help "Run
: 2
system > function callbacks: 1137
system > value callbacks : 1
system > message callbacks : 0
system > bytecode callbacks: 600
system >
system > mp instances : 0
system >
ement 1.04
mtx-context |
mtx-context | main context file: [snip]
mtx-context | current version: 2022.05.11 11:36
mtx-context | main context file: [snip]
mtx-context | current version: 2022.05.11 11:36
ldd "$(type -p luametatex)"
linux-vdso.so.1
> > '/Users/janneman/CTX/tex/texmf-osx-64/bin/lib/luametatex/zint/libzint.so'
> > zint> something went wrong: invalid result vector
> > zint> something went wrong: invalid result vector
> > zint > something went wrong: invalid
On Mon May 30, 2022 at 8:19 PM CEST, Jan-Erik Hägglöf via ntg-context wrote:
> With latest LMTX installed on my Monterey intel MacBook Air and Zint version
> 2.11
>
> optional> using library
> '/Users/janneman/CTX/tex/texmf-osx-64/bin/lib/luametatex/zint/
e issues to get this to work
>
> With latest LMTX installed on my Monterey intel MacBook Air and Zint
> version 2.11
>
> This appears in my log entry
>
> …
> optional> using library
> '/Users/janneman/CTX/tex/texmf-osx-64/bin/lib/luametatex/zint/libzint.so'
>
Hi!
I have issues to get this to work
With latest LMTX installed on my Monterey intel MacBook Air and Zint version
2.11
This appears in my log entry
…
optional> using library
'/Users/janneman/CTX/tex/texmf-osx-64/bin/lib/luametatex/zint/libzint.so'
zint> somethin
mit LuaMetaTeX wird das nix... ;)
Grüßlinge, Hraban
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : <mailto:ntg-context@ntg.nl> ntg-context@ntg.nl
Am 30.05.22 um 18:37 schrieb Jürgen Althaus via ntg-context:
Von meinem Commodore 64 geschickt
Hallo Jürgen,
ich meine mich zwar zu erinnern, dass es eine TeX-Distribution für C64
gab, aber mit LuaMetaTeX wird das nix... ;)
Grüßlinge, Hraban
1.
>>
>> Name: LMTX
>>
>> % Here you need to use the Browse button to get to the mtxrun. On my mac
>> it is the path to the directory tex which contains the file mtxrun as
>> shown below. Yours may be different. Since mtxrun is an alias for
>> luametatex
X
>
> % Here you need to use the Browse button to get to the mtxrun. On my mac
> it is the path to the directory tex which contains the file mtxrun as
> shown below. Yours may be different. Since mtxrun is an alias for
> luametatex it substitutes luametatex. I edited this to, mtxr
set this up on my mac mini M1.
Name: LMTX
% Here you need to use the Browse button to get to the mtxrun. On my mac
it is the path to the directory tex which contains the file mtxrun as
shown below. Yours may be different. Since mtxrun is an alias for
luametatex it substitutes luametatex. I edi
Hello list,
forgive me if my question is too general and trivial and without a minimum
code.
In the current state of ConTeXt development, which engine do you recommend
to use *definitively*? ConTeXt MkIV or LMTX?
I use macOS 10.15.7, on which I have MacTeX-2022, ConTeXt Standalone and
ConTeXt
Hi list,
I haven't had any luck solving any of the issues from my previous email:
[NTG-context] Callbacks in LuaMetaTeX
https://mailman.ntg.nl/pipermail/ntg-context/2022/105566.html
Admittedly, my problems are fairly obscure (and likely self-inflicted),
but any suggestions would
umnset
Why does context fail, producing an empty .log and .pdf, with the following
information to the terminal:
resolvers | formats | executing runner 'run luametatex format':
/usr/local/sw/versions/context-osx-64/tex/texmf-osx-64/bin/luam
301 - 400 of 1121 matches
Mail list logo
