over new frontiers:
NTS, MetaFun, Oriental TeX, LuaTeX, mplib, LuaMetaTeX…
They’re also dubbed the incisors (AKA cutting edge) of the dinosaur of
Open Source.
ConTeXt is aimed at creative users, known for advanced features like
extensive font control and direct XML processing, with a deep
can get inspired. Everything works as it should:
```
$ docker run --rm -it minidocks/context --luatex --version
resolvers | globbing | confusing filename, name: 'CHANGELOG.md', lower: 'changelog.md', already: 'ChangeLog.md'
mtx-context | redirect luametatex -> luatex: luatex --luao
output was handled by the PdfTeX engine
in MKII in 2005. What sort of output did the software produce before
PdfTeX was introduced? Was this the same as the output produced by the
software before the publication of the PDF specification?
2005 is when we started with luatex which is a follow up
>
> all in the same (bib) path
>
> ... always has been so ...
But now it seems that luatex has disappeared from our bin directories.
Was this intended (because of the issues with the build farm)?
Many thanks for your help,
Pablo
___
On 4/11/2024 5:25 PM, Pablo Rodriguez via ntg-context wrote:
On 4/10/24 22:28, Denis Maier wrote:
[...]
context --luatex --generate
Thanks, Pablo.
I've tried it, but it doesn't seem to work...
I get the same result on Win64 when I move the luatex binary from the
tex/texmf-win64/bin
On 4/11/24 17:39, Denis Maier via ntg-context wrote:
> [...]
> Ok. It wasn't there. I have now copied it from my Miktex installation, but
> it still does not work. (Looks like some path issue. The luatex binary from
> the miktex installation seems to take priority over the one now in t
>
> On 4/10/24 22:28, Denis Maier wrote:
> >> [...]
> >> context --luatex --generate
> >
> > Thanks, Pablo.
> > I've tried it, but it doesn't seem to work...
>
> I get the same result on Win64 when I move the luatex binary from the
> tex/texmf-win64
On 4/10/24 22:28, Denis Maier wrote:
>> [...]
>> context --luatex --generate
>
> Thanks, Pablo.
> I've tried it, but it doesn't seem to work...
I get the same result on Win64 when I move the luatex binary from the
tex/texmf-win64/bin/ directory.
This may sound stupid
13:59, Denis Maier via ntg-context wrote:
> > Hi,
> > I wanted to test my earlier example (float placement) also with MKIV,
> > but context ---luatex … give me this error message :
> > unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua How can I
> > make it wor
On 4/10/24 13:59, Denis Maier via ntg-context wrote:
> Hi,
> I wanted to test my earlier example (float placement) also with MKIV, but
> context ---luatex …
> give me this error message :
> unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua
> How can I make it work?
Hi D
Hi,
I wanted to test my earlier example (float placement) also with MKIV, but
context ---luatex .
give me this error message :
unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua
How can I make it work?
Best,
Denis
]
\starttext
\xmlprocessbuffer{main}{demo}{}
\type{a --b c}
\stoptext
Using current latest (from 2024.03.11 09:34), LMTX transforms "--" in
"–" (en-dash) only with \xmlinlineprettyprinttext (LuaTeX writes the
en-dash in the three cases).
This issue has been driving me
\stoptext
Current latest (from 2024.03.11 09:34) breaks compilation with both LMTX
and LuaTeX.
As far as I know, this sample should be compiled without any issue.
Could you be so kind to confirm the issue or explain me what am I missing?
The footnote environment is just a fancy way
LMTX
and LuaTeX.
As far as I know, this sample should be compiled without any issue.
Could you be so kind to confirm the issue or explain me what am I missing?
Many thanks for your help,
Pablo
___
If your question
ame obvious when MS reprocessed a graphic, as last year we switched
from scsled (no bug) to double (long time bug exposed). (The bug is also
present in LuaTeX double/binary mode but it will be fixed there too
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
On 3/8/24 19:09, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
[...]
LMTX gets b, c and d in slanted form.
LuaTeX gets only b and c in slanted form.
[...]
I get b and d in italic which
On 3/8/24 19:09, Wolfgang Schuster wrote:
> Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
>> [...]
>> LMTX gets b, c and d in slanted form.
>>
>> LuaTeX gets only b and c in slanted form.
> [...]
> I get b and d in italic which is the expected out
\\
\stopTEXpage
\stoptext
LMTX gets b, c and d in slanted form.
LuaTeX gets only b and c in slanted form.
With latest LMTX (2024.03.05), b and d are slanted, as I would expect.
This might be just a test case, but I’d avoid switches like \em without
grouping.
Hraban
\\
\stopTEXpage
\stoptext
LMTX gets b, c and d in slanted form.
LuaTeX gets only b and c in slanted form.
I think LMTX may have an issue here.
Could anyone be so kind to confirm this?
I get b and d in italic which is the expected output.
Wolfgang
: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d\\
\stopTEXpage
\stoptext
LMTX gets b, c and d in slanted form.
LuaTeX gets only
Pablo Rodriguez via ntg-context schrieb am 04.03.2024 um 07:17:
On 3/4/24 01:18, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 03.03.2024 um 20:02:
[...]
With LuaTeX, I get PDF metadata. With LuaMetaTeX, I cannot get them.
[...]
I can confirm the issue and it happens
With current latest (2024.02.27 09:21), LuaTeX gets boldened and slanted
for regular (but the other fonts cannot inherit the wider feature and
wider will not mix with boldened-30 [even when specified]).
For some reason, LMTX from current latest cannot get slanted and
boldened-30 (but it mixes the inherited
On 3/4/24 01:18, Wolfgang Schuster wrote:
> Pablo Rodriguez via ntg-context schrieb am 03.03.2024 um 20:02:
>> [...]
>> With LuaTeX, I get PDF metadata. With LuaMetaTeX, I cannot get them.
>> [...]
> I can confirm the issue and it happens because Hans changed t
Pablo Rodriguez via ntg-context schrieb am 03.03.2024 um 20:02:
Dear list,
this issue has been bugging me for some time:
[...]
With LuaTeX, I get PDF metadata. With LuaMetaTeX, I cannot get them.
For both, I’m using current latest (from 2024.02.27 09:21).
Could anyone confirm the issue
[state=start]
\xmlprocessbuffer{main}{demo}{}
\stoptext
With LuaTeX, I get PDF metadata. With LuaMetaTeX, I cannot get them.
For both, I’m using current latest (from 2024.02.27 09:21).
Could anyone confirm the issue or explain me what I am missing?
Many thanks for your help,
Pablo
}},
bi={style: regular, features:{default, boldened-30, slanted}}]
\setupbodyfont
[mainface, 30pt]
\starttext
\startTEXpage[offset=1ex]
a
{\it a}\\
{\bf a}
{\bi a}
\stopTEXpage
\stoptext
With current latest (2024.02.27 09:21), LuaTeX gets boldened and slanted
for regular
ême que \LaTeX, est une
suite logicielle qui contient les macros de \LaTeX, les routines du
langage {\em Perl}, ainsi que les macros de \LuaTeX. On peut donc
définir à peu près tout ce qui est exigé au niveau de l'édition
professionnelle, sans entrer dans la connaissance technique du
; │ ├── luametatex-cache
> │ │ └── context
> │ └── luatex-cache
> │ └── context
> ├── texmf-context (main tree)
> │ ├── colors
OK, I unpacked the main distribution in context/tex, set PATH and ran
mtxrun --generate
which output:
resolvers | resolving | var
nly)
└── tex
├── texmf-cache (necessary, but auto-created?)
│ ├── luametatex-cache
│ │ └── context
│ └── luatex-cache
│ └── context
├── texmf-context (main tree)
│ ├── colors
│ │ └── icc
│ ├── context
│ │ └── data
The upcoming version 1.18.0 has some changes that are not compatible with
previous versions but should only apply in kpse mode:
1) the debug library is disabled; can be enabled with --luadebug
2) os.rename os.remove and lfs library functions are checked
from kpse to see if the path is legal
I'm
2023). In ConTeXt
terms, this is almost ancient (»uralt«).
ConTeXt MkII used pdfTeX as engine. In MkIV, the engine is LuaTeX. The
latest engine is LuaMetaTeX for what is named either LMTX or MkXL.
The format file is for pdfLaTeX, so ConTeXt cannot really do anything
with it. It is consistent that
ittle more detailed. Once this documentation has been passed
as an introductory part (itself containing chapters explaining how this
page of documentation was put together, with notes in the margins,
etc.), this book could introduce MKIV, LuaTeX, MetaPost and so on, but
with a clear distincti
s
a bit less consuming)
on the one hand luametatex is more efficient than luatex due to
all kind
of ímprovements' but some nodes are larger so that takes more
memory,
which is only noticed when one has lots of text on a page (or keeps
boxes stuff around)
curious about what has changed in recent upload, that memory
>> > consumption is about 60% of earlier versions.
>> it's hard to tell what exact consumpiton is becaue for instance when lua
>> creates tables, they grow by factors two when then have to (maybe 5.5 is
>> a
what has changed in recent upload, that memory
> > consumption is about 60% of earlier versions.
> it's hard to tell what exact consumpiton is becaue for instance when lua
> creates tables, they grow by factors two when then have to (maybe 5.5 is
> a bit less consuming)
>
> on
to tell what exact consumpiton is becaue for instance when lua
creates tables, they grow by factors two when then have to (maybe 5.5 is
a bit less consuming)
on the one hand luametatex is more efficient than luatex due to all kind
of ímprovements' but some nodes are larger so that takes more memory
On 2/14/2024 6:10 PM, Henning Hraban Ramm wrote:
Sorry, I can’t help ATM.
But Hans’ latest upload includes 32bt Linux binaries again.
Indeed. I have to improvise a bit as the build is only partially working
so some binaries i generate myself and currently we skip luatex (no big
deal as most
on. Rephrasing the question, can
> > LuaMetaTeX/ConTeXt compile
> > plain TeX files. If yes, how can I do that?
>
> You mix up two different things here.
>
> 1. Plain TeX is a collection of TeX macros like ConTeXt or LaTeX.
>
> 2. LuaMetaTeX is a program like pdfTeX or Lu
or LaTeX.
2. LuaMetaTeX is a program like pdfTeX or LuaTeX which provides commands
which are used by above mentioned collections to create macros.
Even though ConTeXt provides some commands which available in plain TeX
not all of the are supported which means you can't process plain TeX
documents
: luametatex has a smaller memory footprint than luatex
although nodes are way bigger but even that won't make it run well on an
8 bit processor, assuming it can address 32 bit mem.
Context mkii started on 4.7 Mhz intel (386) so now we're 1000 times
faster but performance gain is not linear
in engine.
One thing to keep in mind is that tex is an interpreter and all gets
tokenized which is more costly in a 32 bit engine than in an 8 bit one
(like pdftex). And although luametatex is more efficient than luatex
that gets offset by more features that come at a price, but we still
win
quite wel now and refactoring is for me
counter productive. These are projects running for decades and engines
need to be stable so changes come slow.
You can compare the luanmetatex source to luatex and pdftex to see how
we proiceed.
Hans
nything in the defaults. I'll try to figure out how
to load opentype fonts in latex, and test lualatex.
> > MKIV: 130 pages/sec
> > LMTX: 147 pages/sec
>
> that is weird as lmtx is always faster here (we loose some 15% on the backend
> compared to luatex, maybe even mo
. Here
are the results:
pdflatex: 547 pages/sec
lualatex: 308 pages/sec
opentype or type 1 ?
MKIV: 130 pages/sec
LMTX: 147 pages/sec
that is weird as lmtx is always faster here (we loose some 15% on the
backend compared to luatex, maybe even more, but we gain back quite a
bit elsewhere
Hi all,
I just updated the wiki ConTeXt to 20240108.
The tag on the wiki by default uses luametatex (LMTX), but if you
want luatex instead (MKIV), you can still do that by using .
There have been some problems recently because Hans’ new binaries needed a
newer version of various system
or \startMPpage…\stopMPpage, so that it can be typeset
> as-is.
>
> If you want to do 3D, you may want to get Lua involved for calculations. I
> use
>
> - Programming in LuaTeX page on the wiki (
> https://wiki.contextgarden.net/Programming_in_LuaTeX)
> - Programming in Lua, 4t
…\stoptext or \startMPpage…\stopMPpage, so that it can be typeset
as-is.
If you want to do 3D, you may want to get Lua involved for calculations. I use
- Programming in LuaTeX page on the wiki
(https://wiki.contextgarden.net/Programming_in_LuaTeX)
- Programming in Lua, 4th ed.
by Roberto Ierusalimschy
Hi Shiv and Fabrice,
> On Dec 30, 2023, Shiv Shankar Dayal wrote:
> It would be nice to either support Metapost 3D or Asymptote.
> On Dec 6, 2021, Fabrice L wrote:
> I would be very interested to see an example of a Metafun drawing made with
> the help of LuaTeX to speed up so
-context@ntg.nl
Betreff: [NTG-context] Re: QR Code
Am 18.12.23 um 17:05 schrieb Ursula Hermann:
> Dear List
> After compiling
> \usemodule[m-zint]
> \starttext
> \barcode[alternative=isbnx, text=9783865419026, width=4cm] \blank[big]
> \barcode[alternative=qrcode, text={wie weet wa
ou see in the pdf.
Are you using MkIV (LuaTeX) or LMTX (LuaMetaTeX)?
What’s your ConTeXt version, and how did you install it? (TeX live, Linux
distribution, LMTX distribution?)
I guess a missing EPS means you load the MkIV version of the module, probably
because "m-zint".
Is there an err
On Mon Dec 18, 2023 at 9:35 PM CET, Pablo Rodriguez via ntg-context wrote:
> On 12/18/23 20:34, Henning Hraban Ramm wrote:
> > [...]
> > Are you using MkIV (LuaTeX) or LMTX (LuaMetaTeX)?
>
> Many thanks for your reply, Hraban.
>
> I understood my issue with your
On 12/18/23 20:34, Henning Hraban Ramm wrote:
> [...]
> Are you using MkIV (LuaTeX) or LMTX (LuaMetaTeX)?
Many thanks for your reply, Hraban.
I understood my issue with your reply (I known, your answer is intended
to Uschi).
It is also in the sent file:
Creator:
LuaMetaTeX 2.10.11 20
in the pdf.
Are you using MkIV (LuaTeX) or LMTX (LuaMetaTeX)?
What’s your ConTeXt version, and how did you install it? (TeX live,
Linux distribution, LMTX distribution?)
I guess a missing EPS means you load the MkIV version of the module,
probably because "m-zint".
Is there an err
; the LuaTeX engine
returns the following error message:
"error (luacall): invalid number
mtx-context | fatal error: return code: 1"
Unfortunately, the error message provides no additional clues. To investigate
further, I created a minimal example, which you can easily verify at
https
Hello,
I am reaching out to seek assistance regarding a compatibility issue I have
encountered after installing ConTeXt on a new computer. The problem arises when
attempting to compile documents that utilize the spy library; the LuaTeX engine
returns the following error message:
"
a pdf viewer that intercept some 'goto the text file' command and then
> launches an editor (afik the library has some heuristics build in wrt boxes
> and nesting and so); at the tex end there is also a library that kicks in
> addiional code for nodes and the backend (which is why enablin
and luatex environments?
The parser recognizes chunks of metapost and latex code and marks them in the
syntax tree, but does nothing else: I figured the best approach here was to let
applications call out to various tree-sitter parsers as needed.
I don't know of a tree-sitter parser for either
)
wrt the synctex file, that one is generated by context (so we don't use
the synctex code in luatex and as luametatex has no backend there it's
even completely absent ... context generates the file itself which is
also a bit more efficient)
Unfortunately, it’s not a drop-in replacement, so
On 11 Nov 2023, at 14:52, Aditya Mahajan wrote:
> Last time I checked tree-sitter on neovim, there were no good tree-sitters
> for context. I'd be interested in testing this out.
Happy to have feedback!
> Does the parser detect nested metapost and luatex environments?
The parser r
document
> hierarchy.)
Last time I checked tree-sitter on neovim, there were no good tree-sitters for
context. I'd be interested in testing this out.
Does the parser detect nested metapost and luatex environme
Dear list,
These are the following first four lines of a CSV file:
,,
"About \LuaTeX\ and
\ConTeXt","about.pdf","https://www.pragma-ade.com/general/manuals/about.pdf;
"l2r, r2l: A Few
Tips","bidi.pdf","https://www.pragma-ade.com/general/manuals
angles, and convert them to the
> desired format in python and write them to a temp file. Read that temp file
> in lua and typeset it as you want.
>
> Another option is an old proof of concept by Luigi:
>
em to a temp file. Read that temp file in
lua and typeset it as you want.
Another option is an old proof of concept by Luigi:
https://github.com/bastibe/lunatic-python which allowed two-way communication
between python and luatex. No
So clearly I would need to upgrade my version. It does not work with
what I have at the moment. Thank you.
Julian
On 22/9/23 02:04, Wolfgang Schuster wrote:
I get a line below the chapter title with LMTX and LuaTeX with the
current ConTeXt version
else underlined in 'Ward'.
I get a line below the chapter title with LMTX and LuaTeX with the
current ConTeXt version.
begin example
\setuphead
[chapter]
[textcommand={\setbar[underbar]}]
\starttext
\startchapter[title={My title}]
\input ward
\stopchapter
\stoptext
end example
raphicsmagick to
convert tiffs to pdf on the fly. However, as it seems, graphicsmagick is
producing invalid pdfs.
For every included tiff I have something like this in the log:
luatex warning > pdfe: invalid 11 0 R object at offset 573751
luatex warning > pdfe: invalid 11 0 R object at of
Sorry, that was too quick...
Hi,
currently, ConTeXt can't use tiffs directly, but it uses Graphicsmagick to
convert tiffs to pdf on the fly. However, as it seems, graphicsmagick is
producing invalid pdfs.
For every included tiff I have something like this in the log:
luatex warning > p
of this kind and might be able to give me a
hint to follow?
This is fairly close to what you're looking for I think (the manual, not
the package itself):
http://mirrors.ctan.org/macros/luatex/generic/lua-widow-control/lua-widow-control.pdf
The source is a little messy, but I've used
w?
This is fairly close to what you're looking for I think (the manual, not
the package itself):
http://mirrors.ctan.org/macros/luatex/generic/lua-widow-control/lua-widow-control.pdf
The source is a little messy, but I've used it in a bunch of other
documents and it seems fairly robust:
> > \startcomponent includes \starttext in its
> > definition.
> >
> > > begin example
> > > \starttext
> > >
> > > \starttext
> > >
> > > \stoptext
> > >
> > > \stoptext
> > > end example
>
end example
Wolfgang
Take a look at the command line when you process a file and you should see
something like this:
As you can see the luatex engine processes the file cont-yes.mkiv and not your
document which put as argument to context. Your document is just read by
cont-yes.mkiv
end example
Wolfgang
Take a look at the command line when you process a file and you should see
something like this:
As you can see the luatex engine processes the file cont-yes.mkiv and not your
document which put as argument to context. Your document is just read by
cont-yes.mkiv
gin example
> \starttext
>
> \starttext
>
> \stoptext
>
> \stoptext
> end example
>
> but this doesn't.
>
> begin example
> \starttext
>
> \starttext
> end example
>
> Wolfgang
Take a look at the command line when you pr
On 8/18/2023 8:48 PM, Carlos wrote:
And with luatex frozen for better or for worse, I better stick to plain
tex
not sure what frozen has to do with it ... it will be around and
maintained forever but no fundamental new functionality will be added
that said: luametatex is of not much use when
, except that the uppercase letters ‘A’ through ‘Z’ have code 999.
> > > (This
> > > slight difference is what makes punctuation act differently after an
> > > uppercase letter; do
> > > you see why?) Plain TEX redefines a few of these codes using the \sf
gt; \sfcode‘)=0
> > \sfcode‘.=3000
> > make right parentheses “transparent” to the space factor, while tripling
> > the stretcha-
> > bility after periods. The \frenchspacing operation resets \sfcode‘. to
> > 1000.»
>
> Everything you cite above is very like
On 8/16/2023 9:27 PM, Xavier B. wrote:
OK. Thanks but it's about luatex
[https://tracker.luatex.org/changelog_page.php]. Does we use luametatex?
lmtx uses luametatex ... luatex dev is basically frozen (has to be
stable because used by several macro packages now)
Hans
OK. Thanks but it's about luatex
[https://tracker.luatex.org/changelog_page.php]. Does we use luametatex?
On Wed, 16 Aug 2023 21:07:47 +0200
Wolfgang Schuster ha escrit:
> Xavier B. schrieb am 16.08.2023 um 20:38:
> > Thanks.
> > Anyway do ypu have public triaging bugs
Hi,
On Sun, Aug 13, 2023 at 9:13 AM Xavier B. wrote:
>
> So,
>
> Finally is it a bug in MKIV? It seems you fix some kind of bug in your
> messages. Is it true?
>
> > The output with Luametatex is correct but Luatex creates a raised bar
> >
at tug meetings on YT.
The output with Luametatex is correct but Luatex creates a raised bar
(and different linebreaking).
\showglyphs
\startTEXpage[offset=1ex]
\ruledhbox{$\overline{OA} = \overbar {OA} = 4.2$}
\par
\ruledhbox{$\underline {OA} = \underbar
So,
Finally is it a bug in MKIV? It seems you fix some kind of bug in your
messages. Is it true?
> The output with Luametatex is correct but Luatex creates a raised bar
> (and different linebreaking).
>
> \showglyphs
>
> \startTEXpage[offset=1ex]
> \ruledh
the modern-math.lfg file have:
AccentTopShiftUp = -60,
FlattenedAccentTopShiftUp = -60,
I assume it has the same lm math font as we use.
Do you test with Luatex?
Only when asked.
The output with Luametatex is correct but Luatex creates
:
AccentTopShiftUp = -60,
FlattenedAccentTopShiftUp = -60,
I assume it has the same lm math font as we use.
Do you test with Luatex?
The output with Luametatex is correct but Luatex creates a raised bar
(and different linebreaking).
Wolfgang
Hi everyone,
I'm finalising packaging TeX Live 2023 for OpenBSD and have an issue with
context using the new luametatex engine.
I'm getting various Lua errors when running `context --make`, like:
node-ini.lmt:54: attempt to call a nil value (local 'getvalues')
and:
node-nut.lmt:22:
> preloading modern (mono)
>> fonts > 'fallback modern tt 12pt' is loaded
>> luatex warning > pdfe lib: lua expected
>> luatex warning > pdfe lib: lua expected
>> fonts > checking > char [ (U+0005B) in font '' with id 0: missing
1, order 2, name './ArchiMate-sheets.tex'
fonts > preloading modern (math)
fonts > 'fallback modern mm 12pt' is loaded
fonts > preloading modern (mono)
fonts > 'fallback modern tt 12pt' is loaded
luatex warning > pdfe lib: lua expected
lu
ex'
fonts > preloading modern (math)
fonts > 'fallback modern mm 12pt' is loaded
fonts > preloading modern (mono)
fonts > 'fallback modern tt 12pt' is loaded
luatex warning > pdfe lib: lua expected
luatex warning > pdfe lib: lua expected
fonts
frontend here; omega is dvi based
so like regular tex and etex whatever it does with fonts is not really
related to the engine bu tup to the backend: the engine only needs
metrics (omega extended tfm into ofm for that).
pdftex brought a pdf backend, xetex pipes into a dvi backend, luatex has
a pdf
nce between commercial fonts and free ones
> as they use the same technology; with some exceptions, fonts are not that
> expensive (take lucida from tug, making fonts takes time after all); and for
> publishers it's noise on their budgets.
>
> > p.s many many years ago
many years ago I read and followed some publications about
the aformentioned extension and just went over them recently, to
have an idea what did and did not work. In regards to typefaces,
its goal was unmatched, or so I think.
It might be comforting to know that right from the start luatex made
or for that matter this one lualatex too
or find(n,"plain")
or find(n,"optex")
-- or find(n,"luatex")
-- or find(n,"pdftex")
)
end
just getting rid of files we don't need
Hans
--
find(n,"latex")
what's the point of latex there?
> -- or find(n,"lualatex")
or for that matter this one lualatex too
> or find(n,"plain")
> or find(n,"optex")
> -- or find(n,"luatex")
> -- or fi
both drivers.
> >
> > @Hans, so the validate function should be:
> >
> > local function validate(n)
> > return not (
> > find(n,"latex")
> > -- or find(n,"lualatex")
> > or find(n,"plain")
> >
uses both drivers.
@Hans, so the validate function should be:
local function validate(n)
return not (
find(n,"latex")
-- or find(n,"lualatex")
or find(n,"plain")
or find(n,"optex")
-- or find(n,"luatex"
oth drivers.
@Hans, so the validate function should be:
local function validate(n)
return not (
find(n,"latex")
-- or find(n,"lualatex")
or find(n,"plain")
or find(n,"o
at is going on.
This was a bit crazy to track down. Here is the fix:
In line 180 of mtx-install-modules.lua, comment the line
or find(n,"luatex")
Otherwise, the file
tex/generic/pgf/systemlayer/pgfsys-luatex.def
is not extracted from the tikz.zip!
I don't know why OP and I (
I miss anything? It works just fine.
>
> On a new machine and pgfsys-luatex.def is missing for me as well. I'll try to
> check what is going on.
This was a bit crazy to track down. Here is the fix:
In line 180 of mtx-install-modules.lua, comment the line
or find(n,"luatex&qu
mtxrun --script install-modules --install --all
> >
> > doing exactly that?
> >
>
> Okay Floris. I see Aditya nearby. He'll take over from now on :) stand
> by please. I know you didn't ask the original question but this is over
> the pgfsys-pdftex and the
:) stand
by please. I know you didn't ask the original question but this is over
the pgfsys-pdftex and the pgfsys-luatex. It's a race between them !!
sort of
The solutions are a few if any really, either as I suggested first and update
afterwards or install tikz
if the driver is the problem, what does
ny
explicit help. Pretend that you're Hercule Poirot: Examine all clues, and deduce
the truth by order and method.
mtx-context | fatal error: return code: 1
The PATH is set correctly, this is not the output from using the regular
TeXlive package which uses luatex, terminates because it doesn'
1 - 100 of 10522 matches
Mail list logo
