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'
s set correctly, this is not the output from using the regular
TeXlive package which uses luatex, terminates because it doesn't understand
\pgfsetxvec{\pgfpoint{1cm}{0cm}} and makes no reference to Hercule Poirot.
I ingenuously tried to explicitly set some formats in the file
~/.local/share/co
with ConTeXt
are great), but I was used to printing books with an old Type-1 Minion
(www.ctan.org/pkg/w-a-schmidt) and find it hard to accept that this
should not be possible with the
modern flavours of TeX.
My system:
This is LuaTeX, Version 1.16.0 (TeX Live 2023/Arch Linux)
open source > le
to printing books with an old Type-1 Minion
(www.ctan.org/pkg/w-a-schmidt) and find it hard to accept that this
should not be possible with the
modern flavours of TeX.
My system:
This is LuaTeX, Version 1.16.0 (TeX Live 2023/Arch Linux)
open source > level 1, order 1, name
'/usr/share/texmf-d
\completecontent
\dorecurse{5}
{a\footnote{}}
\stoptext
LuaTeX generates fine hyperlinks for footnotes.
My guess is that the issue is in the LuaMetaTeX binary.
Could anyone confirm this issue?
i'll upload a fix later today (some sensitivity to an extra return value
of a helper)
Hans
\completecontent
\dorecurse{5}
{a\footnote{}}
\stoptext
LuaTeX generates fine hyperlinks for footnotes.
My guess is that the issue is in the LuaMetaTeX binary.
Could anyone confirm this issue?
i'll check it but (maybe side effect of some ref things Alan and I are
working on). The engine has
Dear list,
in the following sample, hyperlinks for footnotest don’t work with
current latest (2023.05.28 18:57) with current LMTX (20230528):
\setupinteraction
[state=start,
focus=standard]
\starttext
\completecontent
\dorecurse{5}
{a\footnote{}}
\stoptext
LuaTeX
(Sorry for the delay, I wanted to be sure that building phase was over)
==
LuaTeX 1.17.0 2023-04-29
==
- A breaking backward compatibility change: by default the socket
On Tue, May 09, 2023 at 07:00:15PM +0200, Hans Hagen via ntg-context wrote:
>
> On 5/9/2023 6:24 PM, Carlos via ntg-context wrote:
>
> > With that being said, in that sense (not that I need it though, to be
> > honest), the luatex lmtx approach is more of an instant grati
sense (not that I need it though, to be
> > > honest), the luatex lmtx approach is more of an instant gratification,
> > > whereas with latex and the metrics of the file afterwards, any math
> > > environment is certainly possible, while loading myriad and minion et co
>
On Tue, May 09, 2023 at 07:00:15PM +0200, Hans Hagen via ntg-context wrote:
>
> On 5/9/2023 6:24 PM, Carlos via ntg-context wrote:
>
> > With that being said, in that sense (not that I need it though, to be
> > honest), the luatex lmtx approach is more of an instant grati
On 5/9/2023 6:24 PM, Carlos via ntg-context wrote:
With that being said, in that sense (not that I need it though, to be
honest), the luatex lmtx approach is more of an instant gratification,
whereas with latex and the metrics of the file afterwards, any math
environment is certainly possible
t; This is
> > > normally done by loading special math fonts into the math family slots.
> > > Your font
> > > set is lacking at least the parameter mentioned earlier.
> > >
> > > What parameter is this referring to here?
> >
> > Looks like you m
> message:
>
> /home/vm/context/tex/texmf-linux-64/bin/luatex: unrecognized option
> '--socket'
>
> there is probably a reason for it, context seems to compile just
fine.
ah, ok, so that luatex update even broke the context updater (i didn't
rea
On Sun, 7 May 2023 at 16:05, Hans Hagen via ntg-context
wrote:
> On 5/7/2023 3:18 PM, vm via ntg-context wrote:
> > running the sh install.sh script to update to the latest version i get a
> > message:
> >
> > /home/vm/context/tex/texmf-linux-64/bin/luatex: unreco
On 5/7/2023 3:18 PM, vm via ntg-context wrote:
running the sh install.sh script to update to the latest version i get a
message:
/home/vm/context/tex/texmf-linux-64/bin/luatex: unrecognized option
'--socket'
there is probably a reason for it, context seems to compile just fine.
ah, ok, so
running the sh install.sh script to update to the latest version i get a
message:
/home/vm/context/tex/texmf-linux-64/bin/luatex: unrecognized option
'--socket'
there is probably a reason for it, context seems to compile just fine.
mtx-context | current version: 2023.05.05 18:39
s to luametatex is not
really putting a (performance) burden on this engine. In pdftex and
luatex it would have an impact, although in luatex somewhat less because
we prioritize our favourite units anyway.)
-
make run a symlink to the LuaMetaTeX-based ConTeXt wrapper, it
> looks for texmfcnf.lua relative to the symlink location, not the symlink
> target. With the old LuaTeX/kpse-based wrapper, the script would look
> for texmfcnf.lua relative to the symlink target.
>
> I know that my descri
LuaMetaTeX-based ConTeXt wrapper, it
looks for texmfcnf.lua relative to the symlink location, not the symlink
target. With the old LuaTeX/kpse-based wrapper, the script would look
for texmfcnf.lua relative to the symlink target.
I know that my description above is terrible, so here's a demo:
$ bi
tely updates.
>
> The rules are:
>
> - Packages and formats are updated about 24 hours after a new version
> is uploaded to CTAN.
>
> - Binaries are only updated once-per-year.
>
> But there are also some special cases:
>
> - The luatex binary will be upda
pecial cases:
- The luatex binary will be updated shortly for "reasons" (details to
be made public later).
- The luametatex binary is allowed to be updated whenever.
https://tug.org/pipermail/tex-live/2023-March/049058.html
- I have no idea how ConTeXt is added to TL, but i
how to make it work because
there is some init order issue and we want to be sure that context (and
its scripts) keep working. It would be sort of weird if context (where
luatex originates) would stop working as expected. Keep in mind that
luatex is also a lua engine. and I assume that the texlive
is the yearly snapshot. I actually dont' know the
rules for updating texlive but there are definitely updates. But as much
relates there (like engines shared between macro packages) it can be
that only macros get updated and not engines (also relates to multiple
platforms) so fundamental changes to luatex
;
> I uploaded a new version with some new features discussed at the end of this
> mail.
>
> - A next version of luatex will break context (format making etc) but the
> change is unavoidable because of other macro package demands wrt security
> (context does that differently)
gards
El mié, 26 abr 2023 a la(s) 16:56, Hans Hagen via ntg-context (
ntg-context@ntg.nl) escribió:
> Hi,
>
> I uploaded a new version with some new features discussed at the end of
> this mail.
>
> - A next version of luatex will break context (format making etc) but
> the
Hi,
I uploaded a new version with some new features discussed at the end of
this mail.
- A next version of luatex will break context (format making etc) but
the change is unavoidable because of other macro package demands wrt
security (context does that differently). The low level start up
/;context --luatex --synctex --batchmode %S'
```
--
Kalouguine Andre___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman
ipt context.lua mtx-context.lua
will certainly pop up all over again
only after moving/removing texmf it'd go through or else it won't .
then yes
context --luatex --generate
context --luatex --make
or
context --make
p.s
and all of the above over a lucida sans that was my own misconfig
a
> > day?
> as long as the five mentioned files are there (and best hand mtxrun, context
> and luametatex the same so use links) ... luametatex is the engine as well
> as stub runner (runs the luatex file in the same path with the same name and
> suffix lua)
>
I was just going over pa
a
> > day?
> as long as the five mentioned files are there (and best hand mtxrun, context
> and luametatex the same so use links) ... luametatex is the engine as well
> as stub runner (runs the luatex file in the same path with the same name and
> suffix lua)
>
thank you for the clarificat
it a
day?
as long as the five mentioned files are there (and best hand mtxrun,
context and luametatex the same so use links) ... luametatex is the
engine as well as stub runner (runs the luatex file in the same path
with the same name and suffix lua
kpsewhichmft pdflatextlshell
> > context.lua fmtutil-sys latexmkindex pdftex updmap
> > dvilualatex fmtutil-user luahbtex mktexfmt pktogf updmap-sys
> > dviluatexgftodvi lualatex mktexlsr pktype
&g
luaotfload-tool mktexpk simpdftex xdvi-xaw
dvipdft inimf luatex mktextfm tex xdvipdfmx
dvipsinitexmakeindexmptopdf texhash
ebb kpseaccessman mtxruntexlua
Do you see that context and context.lua out there, right
xfmt pktogf updmap-sys
dviluatexgftodvi lualatex mktexlsr pktype updmap-user
dvipdfm gftopkluametatex mktexmf rungs xdvi
dvipdfmx gftypeluaotfload-tool mktexpk simpdftex xdvi-xaw
dvipdft inimf luatex mkte
it to path somehow.
i'm not sure what you installed but the stand alone installer installs
luametatex / luatex and therefore has
luametatex
mtxrun -> luametatex
context -> luametatex
mtxrun.lua
context.lua
in the same path (the links are stubs, not uncommon in the tex world
All the other wiki pages are outdated.
This is just a wild guess, so I may be very wrong here.
If this doesn't work, then what do you get when you run
type -ap context
type -ap luatex
type -ap texlua
type -ap luametatex
/full/path/to/texlive/2023/context --version
/full/path/to/co
-64/bin` or something similar.
with texmfcnf.lua and the contextbinary from just hte TeX Live infrastructure
there is an interesting conflict with the same ol' same ol'
anyhow
[2/2, 00:02/02:56] install: context [92021k]
running mktexlsr ...
done running mktexlsr.
running mtxrun --generate ...
d
> sources instead of inventing it (and when it comes to answering tex related
> questions chargpt is pretty unreliable, but that's another topic)
>
> > But instaed I looked at it and though to myself «how much has changed?!» In
> > plain TeX (I have forgotten it a bit) but I c
; \end
and it'll produce a dvi file in return.
a lot has changed: opentype math, unicode, more demands but indeed there
is nothing against using plain tex with cmr and dvi fonts if that suits
well; and plain tex will always be faster than context (or latex) just
like pdftex with 8 bit fonts is
with the --luatex switch, I get this error
message:
tex error > tex error on line 101 in file
/mnt/shared/lmtx/tex/texmf-context/tex/context/base/mkiv/meta-imp-dum.mkiv: ! Undefined control sequence
l.101 \newinteger
\c_grph_replacement_n
So, I'm a bit stymied ri
Hi all,
I wanted to use a rightbrace as background for a table, as defined in
meta-imp-fen.mkiv. Unfortunately, I can't get it to work, for 2 reasons:
1. meta-imp-fen doesn't appear to be ported to mkxl.
2. When I try to compile with the --luatex switch, I get this error message:
tex error
has to do is indicate the correct
path to ConText in the setup for this program, depending
on your OS and where you have installed it, e.g.
home/yourname/bin/context/tex/texmf-linux-64/bin if you
are using Linux and have installed it in \bin. Then choose
ConTeXt (LuaTeX) as the processing tool
man12-regular.otf
mkiv lua stats > font engine: otf 3.113, afm 1.513, tfm 1.000, 12 instances, 6
shared in backend, 4 common vectors, 2 common hashes, load time 0.413 seconds
mkiv lua stats > used platform: linux-64, type: unix, binary subtree: usr
mkiv lua stats > used engine: luatex vers
in the setup for this program, depending on your OS and where you have
installed it, e.g. home/yourname/bin/context/tex/texmf-linux-64/bin if
you are using Linux and have installed it in \bin. Then choose ConTeXt
(LuaTeX) as the processing tool.
(2) But to make things a lot easier, I also use Federico's
On 3/6/23 21:10, Hans Hagen via ntg-context wrote:
> On 3/6/2023 7:46 PM, Pablo Rodriguez via ntg-context wrote:
>> [...]
>> Could anyone confirm that the format file for MkIV (LuaTeX) cannot be
>> generated with current latest (from today [2023.03.06 14:48])?
> hm, loo
On 3/6/2023 7:46 PM, Pablo Rodriguez via ntg-context wrote:
Dear list,
I have the following sample:
\starttext
\null
\stoptext
Trying to compile it with "context --luatex", I get the error message
copied bellow.
Could anyone confirm that the format file for MkIV (LuaT
Dear list,
I have the following sample:
\starttext
\null
\stoptext
Trying to compile it with "context --luatex", I get the error message
copied bellow.
Could anyone confirm that the format file for MkIV (LuaTeX) cannot be
generated with current latest (from today [2023.0
that
luametatex will be the runner for luatex, so in order to run mkiv one
then needs:
context --luatex
on texlive (2023) that will be the way to go now which basically means
that as mkii is frozen, mkiv is now frozen in favor of mkxl (aka lmtx)
Hans
na]
>> % \setupbodyfont[kurier]
>> % \setupbodyfont[antykwa]
>> \starttext
>> Some text
>> \stoptext
>> I did a ./install.sh update with no obvious errors and afterwards Kurier and
>> Antykwa worked for me on the above MWE but Iwona failed with the log entry:
update with no obvious errors and afterwards Kurier and
Antykwa worked for me on the above MWE but Iwona failed with the log entry:
[snip]
luatex warning > font: lua-loaded font '21' with name 'ex-iwonar' has no
characters
fonts > virtual math > the mapping is incomplete for '
worked for me on the above MWE but Iwona failed with the log entry:
[snip]
luatex warning > font: lua-loaded font '21' with name 'ex-iwonar' has no
characters
fonts > virtual math > the mapping is incomplete for 'iwonamath' at
7pt
tex error > tex error on line 1 in f
Hi,
We were considering to drop the virtual math fonts mechanism (which has
served its purpose in the transition in the very early days of luatex
but became obsolete as math fonts evolved) but in the end we were forced
keep this feature and even upgrade it because we liked iwona, kurier
-luatex-to-convert-interword-glue-to-spaces-and-kerns/sfdkdkybrvkv
wherein the author replaces the TeX glue with spaces and kerning. I was
wondering whether the same idea could be applied within the typing
environment but making a primitive verbatim environment using \obeylines
and \obeyspaces did
which is out of my scope).
That would probably need an extra branch in the switch(cur_cmd) in
scan_something_internal. Currently protected luacall just goes to the
default branch (You can't use ...).
For various reasons luatex got frozen around version 1 and demand for
stability (which also
nctions_table()
> > > > t[\string#t + 1] = userdata.test
> > > > token.set_lua("test", userdata.test, \string#t,
> > > > "protected")
> > > > }
> > > > \meaning\test\par
> > > > \edef\x{\test}\meaning\x
ot;protected")
}
\meaning\test\par
\edef\x{\test}\meaning\x\par
\the\test
from the code it looks like we're talking plain luatex ...
\the is very selective and doesn't work for all primitives or macros
compare it to \number which accepts any number representation
following
it while \the
t; >t[\string#t + 1] = userdata.test
> >token.set_lua("test", userdata.test, \string#t, "protected")
> > }
> > \meaning\test\par
> > \edef\x{\test}\meaning\x\par
> > \the\test
> from the code it looks like we're talking plain luatex ...
&g
ning\x\par
\the\test
\directlua{
local t = lua.get_functions_table()
t[\string#t + 1] = userdata.test
token.set_lua("test", userdata.test, \string#t, "protected")
}
\meaning\test\par
\edef\x{\test}\meaning\x\par
\the\test
from the code it looks like we're talking plain luat
l this is resolved:
\usemodule[filter]
\startbuffer[tikz-start]
\usemodule[tikz]
% Add font setup
% Add tikz setup
\starttext
\startTEXpage
\starttikzpicture
\stopbuffer
\startbuffer[tikz-stop]
\stoptikzpicture
\stopTEXpage
\stoptext
\stopbuffer
\defineexternalfilter
[tikzpicture]
spac-chr.mkiv",
author= "Hans Hagen, PRAGMA-ADE, Hasselt NL",
copyright = "PRAGMA ADE / ConTeXt Development Team",
license = "see context related readme files"
}
local byte, lower = string.byte, string.lower
-- beware: attribute copying is
ls are missing unnoticed in the output.
>
> Will never be default, you can play with:
>
> % \checkmissingcharacters
> % \removemissingcharacters
> % \replacemissingcharacters
> % \handlemissingcharacters
>
>> (However, \tracinglostchars=3 also doesn't seem to work with
>
put.
Will never be default, you can play with:
% \checkmissingcharacters
% \removemissingcharacters
% \replacemissingcharacters
% \handlemissingcharacters
(However, \tracinglostchars=3 also doesn't seem to work with
LuaTeX+MKIV, probably because there is code to fallback to other fonts?)
and if
1 (report). Making these
a fatal error (with exit status != 0) would be useful for automated
typesetting, as missing characters easily can get lost in the logs,
and then symbols are missing unnoticed in the output.
(However, \tracinglostchars=3 also doesn't seem to work with
LuaTeX+MKIV, probabl
;
> \eTR
>
> \bTR
>
> \bTD r6c1 \eTD
>
> \bTD r6c2 \eTD
>
> \eTR
>
> \stoptable
>
>
>
> I get this :
>
> Command Line: C:\texlive\2022\bin\win32\context.exe --synctex=1
> "Tabular.tex"
>
> Startup Folder: C:\texlive\My Documen
"Tabular.tex"
Startup Folder: C:\texlive\My Documents\My Documents
resolvers | formats | executing runner 'run luatex format':
C:/texlive/2022/bin/win32/luatex --jobname="Tabular"
--fmt=C:/texlive/2022/texmf-var/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/format
]}]
\starttext
\section{Just text}
{\feature[+][section]Just text}
\stoptext
LMTX outputs no small caps and it fallbacks to Noto Emoji. LuaTeX gives
the right output.
Am I missing something or have I hit a bug in LMTX?
more a bug in your approach: you specify a range where you also
overwrite
LMTX outputs no small caps and it fallbacks to Noto Emoji. LuaTeX gives
the right output.
Am I missing something or have I hit a bug in LMTX?
Many thanks for your help,
Pablo
___
If your question is of interest
'?'
...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 catch it
2. The other font is Recursive
(https://github.com/arrowtype/rec
xmf-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/main/fonts/recursive_for_googlefonts).
\usemodule[fonts-variable]
\sta
:
...MTX/tex/texmf-context/tex/context/base/mkxl/font-hsh.lmt:151:
table index is nil
It fails differently in MkIV (but it is nice to see that the new command
has been backported):
luatex warning > node filter: error:
...MTX/tex/texmf-context/tex/context/base/mkiv/node-nut.lua:
Hi Hans,
> i'll bypass that warnign when the mode is zero
I saw that you made that change in the latest upload, thanks.
Unfortunately, I'm still getting the same output:
luatex warning > linebreak: list seems already prepared
luatex warning > linebreak: [ leftinit |
e test file reporting the background issue is
>> typeset fine also).
>> Best regards : Otared
>
> Thanks, Otared - that's bizarre. I just tried both on linux64 and macos
> (12.6, arm): run install.sh, reload font cache and run context without the
> luatex switch on the minima
t file reporting the background issue
>> is typeset fine also).
>> Best regards : Otared
>
> Thanks, Otared - that's bizarre. I just tried both on linux64 and
> macos (12.6, arm): run install.sh, reload font cache and run context
> without the luatex switch on the minimal
, Otared - that's bizarre. I just tried both on linux64 and macos
(12.6, arm): run install.sh, reload font cache and run context without
the luatex switch on the minimal example with the XITS Math font, and on
both systems, I get the error that I have sent this afternoon. Can you
try after
Here comes another one that works with the switch --luatex but not in lmtx:
\setuppapersize[A6,landscape][A6,landscape]
\startuseMPgraphic{ornament}
StartPage ;
save diff ;numeric diff;
diff = .3cm ;
save w; numeric w;
w = xpart (lrcorner Field[Text][Text] - llcorner Field[Text][Text]) - diff
I don’t see any warnings or errors, just
> unexpected results (which is not a good thing). I’m starting with the
> fundamentals. Here is a fairly minimal example: compile with context --luatex
> to see the expected result and with lmtx to see what is wrong.
>
> All best
>
>
starting with the fundamentals. Here
is a fairly minimal example: compile with context --luatex to see the expected
result and with lmtx to see what is wrong.
All best
Thomas
\setuppapersize[A6,landscape][A6,landscape]
\setuplayout[backspace=1cm,
topspace=0.4cm,
marking
end)
}
\starttext
\input knuth
\stoptext
Produces this output:
luatex warning > linebreak: list seems already prepared
luatex warning > linebreak: [ leftinit | rightinit | leftfill | rigthfill
] expected
nil
i'll bypass that warnign when the m
Produces this output:
luatex warning > linebreak: list seems already prepared
luatex warning > linebreak: [ leftinit | rightinit | leftfill | rigthfill ]
expected
nil
Thanks,
-- Max
___
If your questio
[...]
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
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
have to give the full script path here to mtxrun
Thanks! Running:
luatex --luaonly "/opt/context/tex/texmf-linux-64/bin/mtxrun.lua" --script
/opt/context/tex/texmf-context/scripts/context/lua/mtx-context.lua --luatex --make
--redirected
has fixed the format issue.
I now unfortun
have to give the full script path here to mtxrun
Thanks! Running:
luatex --luaonly "/opt/context/tex/texmf-linux-64/bin/mtxrun.lua" --script
/opt/context/tex/texmf-context/scripts/context/lua/mtx-context.lua --luatex
--make --redirected
has fixed the format issue.
I now unfortunat
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 --luaonly
"
On 10/14/22 16:34, Alain Delmotte via ntg-context wrote:
> Hi!
Hi Alain,
many thanks for your help.
> For me it works! And
>
> also for this!
I’m afraid that I cannot make latest from 2022.10.14 10:16 with LuaTeX.
I’m on Linux64. I hope I may make it work with Win64.
As f
101 - 200 of 10535 matches
Mail list logo
