xlive2020: there is
> no such directory in my home directory.
> There were three leftover directories .texlive2008, .texlive2010 and
> .texlive2019, which I removed.
> Doing
> mtxrun --generate
> creates a .texlive2019 directory which contains some other folders which are
>
which I removed.
Doing
mtxrun --generate
creates a .texlive2019 directory which contains some other folders which are
texmf-var/luatex-cache/context/88aacfe88c3cbee9a12d5f4bec4da90b/trees/
and in the latter folder there are 10 files with suffixes .lua and .luc.
Again
cont
ools
>> is
>> /Library/TeX/texbin/luatools
>> So the binaries are in /Library/TeX/texbin, which is in fact an alias for
>> /usr/local/texlive/2020/bin/x86_64-darwin
>> Now, as you and the « ConTeXt (LuaTeX) » engin suggest, if I do
>> luatools
/x86_64-darwin
Now, as you and the « ConTeXt (LuaTeX) » engin suggest, if I do
luatools --generate
then the answer is:
mtxrun | unknown script 'base.lua' or 'mtx-base.lua'
It is possible that the version of mtxrun or luatools scripts in TeXLive are
not working.
I don't remember what I
binaries are in /Library/TeX/texbin, which is in fact an alias for
> /usr/local/texlive/2020/bin/x86_64-darwin
>
> Now, as you and the « ConTeXt (LuaTeX) » engin suggest, if I do
> luatools --generate
Does
mtxrun —generate
work?
(LuaTeX) » engin suggest, if I do
luatools --generate
then the answer is:
mtxrun | unknown script 'base.lua' or 'mtx-base.lua'
It is possible that the version of mtxrun or luatools scripts in TeXLive are
not working.
I don't remember what I did with TeXLive2019 to fix the issue
typeset a simple test
> document with the option « ConTeXt (LuaTeX) » from the menu in TeXShop, where
> it does appear.
>
> Unfortunately when doing this all he gets in the log file is:
>
> /sw/bin/init.csh: No such file or directory.
> mtxrun | unknown script 'context.
typeset a simple test
> document with the option « ConTeXt (LuaTeX) » from the menu in TeXShop, where
> it does appear.
>
> Unfortunately when doing this all he gets in the log file is:
>
> /sw/bin/init.csh: No such file or directory.
My guess is that this missing init.csh
Hi all,
I suggested to a friend, who is using plain TeX and LaTeX, to switch to
ConTeXt, and since he is using TeXShop on MacOSX with a version of TeXLive2020
(named MacTeX2020), I thought he would just typeset a simple test document with
the option « ConTeXt (LuaTeX) » from the menu
Jairo A. del Rio schrieb am 08.08.2020 um 17:17:
Hi again!
When context --luatex is used with current version: 2020.08.07 23:37
LuaMetaTeX is still used. --engine=luatex has no effect, either. Is that
a bug? Thanks
I have no problems using LuaTeX on Windows.
You can try a new installation
Hi again!
When context --luatex is used with current version: 2020.08.07 23:37
LuaMetaTeX is still used. --engine=luatex has no effect, either. Is that a
bug? Thanks
Cordially,
Jairo :)
___
If your question
@ntg.nl/msg95268.html
There was a file missing in the lmtx setup.
New upload. I pruned some 15 year old stub code (from the early luatex
dev times, it was still around; probably more such old code can go), so
hopefully all generates well.
Happy testing,
Hans
Hi, list. I've found a (sort of) way to do LTL typesetting in Lua(La)TeX
based on "chickenize", a LuaTeX package. The font used is available here;
http://www.mongolfont.com/en/font/mnglwhiteotf.html
%Just for testing in LaTeX
\documentclass{article}
\usepackage{luacode}
\usepackag
Jairo A. del Rio schrieb am 23.07.2020 um 19:03:
Hi list! Is --engine=luatex working? Has it changed? The switch seems
to be ignored with newer ConTeXt distributions, so only LuaMetaTeX is
used. Thank you in advance.
context --luatex
Wolfgang
Hi list! Is --engine=luatex working? Has it changed? The switch seems to be
ignored with newer ConTeXt distributions, so only LuaMetaTeX is used. Thank
you in advance.
Jairo :)
___
If your question is of interest
7/2020 à 18:58, Hans Hagen a écrit :
On 7/20/2020 5:11 PM, Pablo Rodriguez wrote:
On 7/20/20 3:41 PM, Hans Hagen wrote:
On 7/20/2020 3:01 PM, Pablo Rodriguez wrote:
Dear list,
with current latest (LuaTeX 2.06 20200717 + ConTeXt MkIV 2020.07.20
10:48), I cannot open luamet
On 7/20/2020 5:11 PM, Pablo Rodriguez wrote:
On 7/20/20 3:41 PM, Hans Hagen wrote:
On 7/20/2020 3:01 PM, Pablo Rodriguez wrote:
Dear list,
with current latest (LuaTeX 2.06 20200717 + ConTeXt MkIV 2020.07.20
10:48), I cannot open luametatex.pdf (its SHA256 reads
On 7/20/20 3:41 PM, Hans Hagen wrote:
> On 7/20/2020 3:01 PM, Pablo Rodriguez wrote:
>> Dear list,
>>
>> with current latest (LuaTeX 2.06 20200717 + ConTeXt MkIV 2020.07.20
>> 10:48), I cannot open luametatex.pdf (its SHA256 reads
>> cff8b660b65f4f8c121c170bcd59545
everything related. Each meeting is source of inspiration for everybody,
> from beginner to expert. Friendly company is always looking for meeting new
> participants, users of LuaTeX, LuaMetaTeX, ConTeXt, Metapost, etc.
>
> There is a special discount for those, who attend the meeting
On 7/20/2020 3:01 PM, Pablo Rodriguez wrote:
Dear list,
with current latest (LuaTeX 2.06 20200717 + ConTeXt MkIV 2020.07.20
10:48), I cannot open luametatex.pdf (its SHA256 reads
cff8b660b65f4f8c121c170bcd59545c5467a7db02614da137e622ef1c5f3964).
Acrobat for Linux complains about malformed
On 7/20/2020 3:01 PM, Pablo Rodriguez wrote:
Dear list,
with current latest (LuaTeX 2.06 20200717 + ConTeXt MkIV 2020.07.20
10:48), I cannot open luametatex.pdf (its SHA256 reads
cff8b660b65f4f8c121c170bcd59545c5467a7db02614da137e622ef1c5f3964).
Acrobat for Linux complains about malformed
Dear list,
with current latest (LuaTeX 2.06 20200717 + ConTeXt MkIV 2020.07.20
10:48), I cannot open luametatex.pdf (its SHA256 reads
cff8b660b65f4f8c121c170bcd59545c5467a7db02614da137e622ef1c5f3964).
Acrobat for Linux complains about malformed document and Evince doesn’t
display anything
le{tufte}}\par
> \setfontcolorscheme[2] {\MyFontA \samplefile{tufte}}\par
> \setfontcolorscheme[3] {\MyFontA \samplefile{tufte}}\par
>
> \page
>
> \setfontcolorscheme[1] {\MyFontB \samplefile{tufte}}\par
> \setfontcolorscheme[2] {\MyFontB \samplefile{tufte}}\par
> \setfont
lorscheme[3] {\MyFontB \samplefile{tufte}}\par
\stoptext
Now, this is pretty (more than a decade) old functionality from early
days of mkiv/luatex when it was used for some tracing (by Idris) and it
still works (surprise).
Today I would definitely use more recent trickery. If there is real
d
minimal example from the contextgarden for gnuplot
> > (https://wiki.contextgarden.net/Gnuplot) I am getting the following
> > error message:
> >
> > This is LuaTeX, Version 1.13.0 (TeX Live 2021/dev/Debian)
> > system commands enabled.
> > open source &
On 7/13/2020 8:53 PM, Adam Reviczky wrote:
Hi,
Using the minimal example from the contextgarden for gnuplot
(https://wiki.contextgarden.net/Gnuplot) I am getting the following
error message:
This is LuaTeX, Version 1.13.0 (TeX Live 2021/dev/Debian)
system commands enabled.
open source
Hi,
Using the minimal example from the contextgarden for gnuplot (
https://wiki.contextgarden.net/Gnuplot) I am getting the following error
message:
This is LuaTeX, Version 1.13.0 (TeX Live 2021/dev/Debian)
system commands enabled.
open source > level 1, order 1, name
'/usr/share/texmf/
On 12/07/20 03:48, Henning Hraban Ramm wrote:
Hi,
I just installed the latest ConTeXt MkIV (LuaTeX 2.06 20200706 + ConTeXt MkIV
2020.07.09 14:51) to check if the CG journal will look the same as with my
"old” installation (LuaTeX 1.11 7215 + ConTeXt MkIV 2020.01.30 14:13).
All looks
Hi,
I just installed the latest ConTeXt MkIV (LuaTeX 2.06 20200706 + ConTeXt MkIV
2020.07.09 14:51) to check if the CG journal will look the same as with my
"old” installation (LuaTeX 1.11 7215 + ConTeXt MkIV 2020.01.30 14:13).
All looks well in Preview.app and PDF Studio 2019, but
tting
resolvers | formats |
resolvers | formats | binary path :
/Users/hansm/TeX/context-lmtx/tex/texmf-osx-64/bin
resolvers | formats | format path :
/Users/hansm/TeX/context-lmtx/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luamet
s | binary path :
/Users/hansm/TeX/context-lmtx/tex/texmf-osx-64/bin
resolvers | formats | format path :
/Users/hansm/TeX/context-lmtx/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex
resolvers | formats | luatex engine: luame
al/texlive/2020/texmf-dist/tex
> ~/lmtx/tex/texmf-modules/tex
> >
> > and similar (lmtx is my directory for the standalone).
> >
> > LuaTeX finds files without any issues. However LuaMetaTeX gives the
> > following error:
> >
stoptext
> >
> > works almost perfectly. However, the cross-reference does not work, even
> if the number of the enumeration is displayed correctly. The example fails
> both in LuaTeX and LuaMetaTeX. As I remember,
However, the cross-reference does not work, even if
> the number of the enumeration is displayed correctly. The example fails both
> in LuaTeX and LuaMetaTeX. As I remember, the problem appeared as early as
> 2019, so not a matter of a bad
}{\input ward}
\stopproposition
\in[prop:1]
\stoptext
works almost perfectly. However, the cross-reference does not work, even if
the number of the enumeration is displayed correctly. The example fails
both in LuaTeX and LuaMetaTeX. As I remember, the problem appeared as early
as 2019, so not a matter
The following gives wrong outputs both in LuaTeX and LuaMetaTeX:
\starttext $\sqrt{3}$ \stoptext
The beta date is 2020.7.5. Thank you very much.
Jairo :)
___
If your question is of interest to others as well, please add
The following gives wrong outputs both in LuaTeX and LuaMetaTeX:
\starttext $\sqrt{3}$ \stoptext
The beta date is 2020.7.5. Thank you very much.
Jairo :)
___
If your question is of interest to others as well
tex/texmf-modules/tex
> >
> > and similar (lmtx is my directory for the standalone).
> >
> > LuaTeX finds files without any issues. However LuaMetaTeX gives the
> > following error:
> >
> > runtime error : input file (name of file) is not found, quitting
&g
live/2020/texmf-dist/tex ~/lmtx/tex/texmf-modules/tex
>
> and similar (lmtx is my directory for the standalone).
>
> LuaTeX finds files without any issues. However LuaMetaTeX gives the
> following error:
>
> runtime error : input file (name of file) is not found, quitting
>
(lmtx is my directory for the standalone).
LuaTeX finds files without any issues. However LuaMetaTeX gives the
following error:
runtime error : input file (name of file) is not found, quitting
The same result is for modules, .sty files and .tex files. Is this
intentional, a bug in LMTX
on an article Taco wrote 2002
for MAPS.
The solution is to get rid of the old commands and focus on LuaTeX and
LuaMetaTeX solutions because the second allows different TeX code. The
following example shows one of these differences.
% LuaTeX
\def\mycommand
{\ifxxx
\expandafter\mycommanda
dd a check for that
Also for all other commands LuaTeX seems to apply range-checks to
ensure that such overflows don't happen, even if invalid values are
passed as firstargument.
indeed, but hadn't yet done that for data, it also need a more strict
check at the tex end (i'm still not sure
s not seem to be that such tokens do not exists because
\letdatacode\somedata="20
\directlua{
local t = token.create'somedata'
print(t.cmdname, t.command, t.index)
}
does print
data101 2097152
Also for all other commands LuaTeX seems to app
I'll take a look at it. Thank you a lot, Taco.
Regards,
Jairo :)
El lun., 29 de jun. de 2020 a la(s) 05:36, Taco Hoekwater (
t...@elvenkind.com) escribió:
> Hi,
>
> Oversimplifying:
>
> TeX (and derivatives like luatex) read the input file as a list of
> operators wi
mean "Does context use callbacks?" You can bet on that. It is how we
> came to implementing callbacks (over a decade ago now, Taco and I spend
> quite some time exploring all these things in the process of luatex dev
> ... fond memories and so).
>
> I don't know wh
way or is a better alternative
possible? Thank you very much.
You mean "Does context use callbacks?" You can bet on that. It is how we
came to implementing callbacks (over a decade ago now, Taco and I spend
quite some time exploring all these things in the process of luatex dev
Hi,
Oversimplifying:
TeX (and derivatives like luatex) read the input file as a list of operators
with optional suffix arguments.
In normal (text) mode, there is no expression state maintained except inside
the handling of such optional arguments.
It follows that, if there is a top-level
stem > currentrun="2"
system > fulljobname="./labels3.tex"
system > input="./labels3.tex"
system > kindofrun="2"
system > maxnofruns="9"
system >
texmfbinpath="/Users/jannema
> On 25 Jun 2020, at 17:54, Jan-Erik Hägglöf wrote:
>
> It is difficult to see the differences in this case, but I supply both
> logfiles
>
>
The two PATHs are not the same, so it is possible that one of the two
uses a different mtxrun, context and/or luatex that is els
will be the equivalent of \pxdimen in LMTX?
Just realized that this is a bug in t-drops: Line 143 of t-dropx.mkiv says
\doifundefined{pdfvariable} {\let\pxdimen\pdfpxdimen} % \pxdimen in luatex 0.85
Commenting that out fixes the bug.
Aditya
quot;d:/Lukas/ConTeXt/Styles"
system > texmfbinpath="d:/Ctx-Beta/tex/texmf-mswin/bin"
system > stop commandline options
system > start commandline files
system >1: D:/Lukas/ConTeXt/Test/IsMacDef3.mkiv
system > stop co
t i'll fix that)
i'll add a tex.getmarks("top|bottom|...",) for whatveer
use it might have and probably also backport that to luatex then
Hans
-
Hans Hagen | PRAGMA ADE
Ridde
way
> >
> > Thanks. Is there any way to convert either a token number (as given e.g.
> > by t.tok) or a numeric cs identifier (as given e.g. by t.tok-cs_token_flag)
> > to a token uservalue?
> > In LuaTeX I used to use `token.new(tok, 0)` for this, but LuaMetaTeX
> >
given e.g.
by t.tok) or a numeric cs identifier (as given e.g. by t.tok-cs_token_flag)
to a token uservalue?
In LuaTeX I used to use `token.new(tok, 0)` for this, but LuaMetaTeX
seems to do more checking here.
Indeed there is more checking. So, when you create a token you need to
use a vali
ß=\relax", no surprise here
\show\^^df % Should be the same, but actually shows "> \� %=undefined"
\show ß % Shows "> the letter ß"
\show ^^df % Should be the same, but actually shows "> the character "
% and "luatex warning > print: bad
t;\sqrt{5472132 \frac{1}{16}} \NR
\stopmathalignment
\stopformula
\stopTEXpage
It's actually nice to find those bugs when one makes heavy use of math
environments. For comparison, LuaTeX prints the correct output.
i uploaded a new version
On 6/12/2020 4:35 AM, Jairo A. del Rio wrote:
It's actually nice to find those bugs when one makes heavy use of math
environments. For comparison, LuaTeX prints the correct output.
Well, thanks for finding them! Normnally those bugs are easy to fix.
Concerning math, there are no real
t
\stopformula
\stopTEXpage
It's actually nice to find those bugs when one makes heavy use of math
environments. For comparison, LuaTeX prints the correct output.
Jairo :)
___
If your question is of interest to others a
dicals in LMTX give a funny font size compared
with LuaTeX, which gives the correct output. I cleaned the cache,
just in case. I attach code and outputs. Thank you in advance.
\startTEXpage
\startformula
a_{2n} = \sqrt{2-\sqrt{4-a_{2n}}}
\stopformula
\stopTEXpage
Ja
Hi,
I can confirm. The same problem goes with $\sqrt{\frac{2}{3}}$.
/Mikael
On Thu, Jun 11, 2020 at 1:53 PM Jairo A. del Rio
wrote:
> Hi list! Nesting radicals in LMTX give a funny font size compared with
> LuaTeX, which gives the correct output. I cleaned the cache, just in case.
>
Hi list! Nesting radicals in LMTX give a funny font size compared with
LuaTeX, which gives the correct output. I cleaned the cache, just in case.
I attach code and outputs. Thank you in advance.
\startTEXpage
\startformula
a_{2n} = \sqrt{2-\sqrt{4-a_{2n}}}
\stopformula
\stopTEXpage
Jairo :D
this
This is LuaMetaTeX, Version 2.06.07
system > ConTeXt ver: 2020.06.10
Seems OK to me.
I get the same result with LuaTeX+MkIV 2020-05-08 and LMTX 2020-06-10,
even commenting out \dontleavehmode.
The only difference is the figure color: blue for LMTX, yellow for MkIV.
Ma
e meaningful
> and robust subsystem (basically getting rid of funny numbers) ... this
> also will be discussed in an evenmore chapter .. not that users need it
> (i think)
>
> - as a side effect (or necessity) some low level recoding (and
> abstraction) had to happen but as far as we
nd it was all doable
because most of the preparation was already done over the last years
- in the process we got rid of a traditional tex data structure that was
left over from the 32 bit times but no longer needed in our 64 bit
luatex/luametatex universe (i might backport that simplificati
On 6/10/2020 7:49 AM, Jairo A. del Rio wrote:
Hi list! I'm curious about vertical typesetting in ConTeXt. As far as I
know, LuaTeX supports four text directions, but LTL is broken for Manchu
script (letters are displayed unjoined in LTL mode) and LuaMetaTeX does
not support vertical directions
Hi list! I'm curious about vertical typesetting in ConTeXt. As far as I
know, LuaTeX supports four text directions, but LTL is broken for Manchu
script (letters are displayed unjoined in LTL mode) and LuaMetaTeX does not
support vertical directions anymore, at least as primitives.
I found
of font design, but I've tried
\setuphead[section][sectionstarter=§]
And it worked. My question is: why? Is it a bug or a feature with
respect to \S? I'm using ConTeXt MKIV version 2020.05.25 23:39 with LuaTeX
I think a side effect of backwards compatibility to plain TeX which
provides \S
the surrounding letters. I thought it was a
matter of font design, but I've tried
\setuphead[section][sectionstarter=§]
And it worked. My question is: why? Is it a bug or a feature with respect
to \S? I'm using ConTeXt MKIV version 2020.05.25 23:39 with LuaTeX
Thank you in advance
Jairo :D
development of LuaMetaTeX, ConTeXt, and
everything related. Each meeting is source of inspiration for everybody,
from beginner to expert. Friendly company is always looking for meeting new
participants, users of LuaTeX, LuaMetaTeX, ConTeXt, Metapost, etc.
There is a special discount for those, who attend
umber(n)//5))..string.rep(one, (tonumber(n)%5))
end
\stopluacode
\def\tallymarks#1{\ctxlua{userdata.tallymarks("#1")}}
\starttext
\tallyfont \tallymarks{47}
\stoptext
This works on Lua 5.4.0 (rc4) interpreter, but it doen't on ConTeXt LMTX
nor LuaTeX and codes are printed instead (1D3781D
\stoptext
\MyMacroA is defined and has meaning undefined
\MyMacroB is undefined and has meaning undefined
You can do this in current luatex/mkiv:
if CONTEXTLMTXMODE == 0 then
local d = tokens.defined
local c = tokens.create
function tokens.defined(s,b)
er.
Could this be fixed or is it really a limiatation of Windows?
It depends on the version and engine. For luatex we also depends on the
interfacing that the texlive ecosystem provides. As Akira mentions,
there have been some developments in that area but I didn't test that
yet (no files with utf
d(s,true) and "defined" or
"undefined")) --% Hans' way
context(" and has meaning " .. (tokens.defined(s) and "defined"
or "undefined")) --% Hans' way
context.par()
end
whatever("MyMacroA")
whatever("MyMa
On 5/26/2020 11:30 PM, Marc Trius wrote:
Thank you! It makes a big difference. I distinctly remember reading
somewhere that the hyphen character can't be replaced... But it was last
year so I couldn't tell you where.
hm, i think it always could be changed, but afaik only luatex can do
sy because already reads the first line of the document
> for special setting (e.g. the engine) but anything which is set in the
> document requires more work because you don't know the new name *before*
> LuaTeX or LuaMetaTeX create the PDF.
You don’t need to know the
at contradicts the mode approach. It would be nice if we could set (or can
>> we?) the result from within the product, depending on a mode – since the
>> product is renamed only later anyway, that could be viable.
> This addition is easy because already reads the first line of the document
>
s addition is easy because already reads the first line of the
document for special setting (e.g. the engine) but anything which is set
in the document requires more work because you don't know the new name
*befor
uot;inject" TeX workflow or whether to
access LuaTeX internals (nodes?) to get the desired information.
- Is it possible somehow?
Too easy ...
\startluacode
function document.whatever()
context(nodes.hpack(tex.getnest().head.next).width)
end
\stopluacode
\unex
% Here I need to get width (or content) of the text from the
begin of the current line,
% i.e. width of the text "pqrs".
% (Depending of the width I will decide what to do later.)
\stoptext
I am too laical to know how to "inject" TeX workflow or whether to
nt) of the text from the
begin of the current line,
% i.e. width of the text "pqrs".
% (Depending of the width I will decide what to do later.)
\stoptext
I am too laical to know how to "inject" TeX workflow or whether to
access LuaTeX internals
ath="d:/Ctx-Beta/tex/texmf-mswin/bin"
system > stop commandline options
system > start commandline files
system >1: D:/Lukas/ConTeXt/Test/!Ctx/ColsRuleOn~.mkiv
system > stop commandline files
modules > start used modules
% i.e. width of the text "pqrs".
% (Depending of the width I will decide what to do later.)
\stoptext
I am too laical to know how to "inject" TeX workflow or whether to
access LuaTeX internals (nodes?) to get the desired information.
- Is it
Pablo pointed out the bug in Evince. Sorry too. I've used another PDF
viewer and SVG color displays correctly. Thanks.
El mié., 20 de may. de 2020 a la(s) 16:32, Jairo A. del Rio (
jairoadelr...@gmail.com) escribió:
> Info from \luatexbanner
>
> For ConTeXt (LuaTeX): This is LuaTeX
Info from \luatexbanner
For ConTeXt (LuaTeX): This is LuaTeX, Version 1.13.0 (TeX Live 2021/dev)
For ConTeXt (LMTX): This is LuaMetaTeX, Version 2.06.03
El mié., 20 de may. de 2020 a la(s) 16:25, Hans Hagen (j.ha...@xs4all.nl)
escribió:
> On 5/20/2020 10:26 PM, Jairo A. del Rio wrote:
> &
s not working at all. I get this error:
>>
>> mtx-context | processing extra: mtx-context-select.tex
>> mtx-context | redirect luametatex -> luatex: luatex --luaonly
>> "/opt/context-lmtx/tex/texmf-linux-64/bin/mtxrun.lua" --script mtx-context
>
at all. I get this error:
mtx-context | processing extra: mtx-context-select.tex
mtx-context | redirect luametatex -> luatex: luatex --luaonly
"/opt/context-lmtx/tex/texmf-linux-64/bin/mtxrun.lua" --script mtx-context
--extra=select --selection=2 file.pdf --redirecte
i has no color when compiled with LuaTeX. Furthermore, the log
includes a lot of lines like the ones below:
fonts > svg conversion > executing runner 'otfsvg': inkscape
--export-area-drawing --shell > temp-otf-svg-shape.log
fonts > svg conversion > processing 1829 svg containers
xml
{paperformat_print}{A4}]
\setuppaper
[offset=\getdocumentargumentdefault{paperformat_to}{0pt}]
With LMTX, --extra=select is not working at all. I get this error:
mtx-context | processing extra: mtx-context-select.tex
mtx-context | redirect luametatex -> luatex: luatex --luaonly
"/opt
ents works fine on LuaTeX (not LuaMetaTeX) based versions
of ConTeXt.
Best regards,
Marcel
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://
}
(That makes 100 errors; please try again.)resolvers | formats |
resolvers | formats | binary path :
C:/Users/MADELEN/Downloads/context-win64/tex/texmf-win64/bin
resolvers | formats | format path :
C:/Users/MADELEN/Downloads/context-win64/tex/texmf-cache/luatex-cache/context
| binary path : C:/lmtx/tex/texmf-win64/bin
resolvers | formats | format path :
C:/lmtx/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1f32e/formats/luametatex
text file:
/home/nother/bin/context/tex/texmf-
context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2020.05.12 16:17
mtx-context | main context file:
/home/nother/bin/context/tex/texmf-
context/tex/context/base/mkiv/context.mkxl
mtx-context | current version: 2020.05.12 1
.2: !
> Missing } inserted
>
>
> }
>
> \vfill
> l.4 \vfill
>
Version: This is LuaTeX, Version 1.12.0 (TeX Live 2020)
--
Bruce Horrocks
Hampshire, UK
___
If your question is of interes
\;C:\Program Files\Git\cmd
d:\Lukas\ConTeXt\Test\EnvHome>findfile context.exe
d:\Ctx-Beta\tex\texmf-mswin\bin\context.exe
d:\Lukas\ConTeXt\Test\EnvHome>context.exe EnvHome.mkiv --once
resolvers | formats | executing runner 'run luatex format':
d:/Ctx-Beta/tex/texmf-mswin/bin/luatex
i\Akce\Stechovice-I-etapa.RDS\Projekt.RDS\P.Prac\SO_251\TZ\14-001-TZ.mkiv
resolvers | formats | executing runner 'run luatex format':
d:/Ctx-Beta/tex/texmf-mswin/bin/luatex --jobname="14-001-TZ"
--fmt=d:/Ctx-Beta/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/format
://wiki.contextgarden.net/Windows_10_64_bit_Installation_2019
I forced 32b version due to some reasons.
But I'm still getting the same LuaTeX version:
I had the same issue. You have to add --context=latest:
https://mailman.ntg.nl/pipermail/ntg-context/2020/097651.html
Marco
ion, following exactly instructions
here:
https://wiki.contextgarden.net/Windows_10_64_bit_Installation_2019
I forced 32b version due to some reasons.
But I'm still getting the same LuaTeX version:
d:\Lukas\ConTeXt\Test\EnvHome>context.exe EnvHome.mkiv --once
resolvers | f
t\Test\EnvHome>context.exe EnvHome.mkiv
resolvers | formats | executing runner 'run luatex format':
d:/Ctx-Beta/tex/texmf-mswin/bin/luatex --jobname="EnvHome"
--fmt=d:/Ctx-Beta/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.fmt
--lua=d:
t; But I'm still getting the same LuaTeX version:
I had the same issue. You have to add --context=latest:
https://mailman.ntg.nl/pipermail/ntg-context/2020/097651.html
Marco
___
If your question is of interest to ot
nment.oldhome or "??")
\stopluacode
\stoptext
ChkEnv.pdf
Description: Adobe PDF document
-- generator : luat-sta.lua
-- state tag : whatever
return {
["context"]={
["version"]="beta",
},
["engines"]={
["luatex"]=true,
[&quo
701 - 800 of 10535 matches
Mail list logo
