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
stage)
fonts > 'fallback modern-designsize rm 12pt' is loaded
metapost> initializing instance 'metafun:1' using format 'metafun' and
method 'double'
metapost> loading 'metafun' as 'metafun.mpxl' using method 'double'
metapost> initializing number mod
Hi list,
I've been playing around with some of the Lua callbacks in LuaMetaTeX,
and I have a few questions/comments.
Context: I'm writing a Plain/LaTeX/ConTeXt module called
"lua-widow-control" that uses Lua callbacks to automatically remove
widows and orphans from documents. The re
} {2.200} \credittotal {3.600} \stopcredits\stoptaccount\stopTEXpage——
tst-taccount.pdf
Description: Adobe PDF document
the log——resolvers | formats | executing runner 'run luametatex format': /Users/hp/Library/context-osx-64/tex/texmf-osx-64/bin/luametatex --jobname="
On 2022-04-26 3:45 a.m., Eduardo Bohoyo wrote:
I can see "modules > 'lua-widow-control' is loaded".
But, luckily, I can also see this:
open source > level 2, order 4, name
'/opt/luametatex/texmf-modules/tex/context/third/lua-widow-control/t-lua-widow-control.mkxl
pen source > level 2, order 4, name
'/opt/luametatex/texmf-modules/tex/context/third/lua-widow-control/t-lua-widow-control.mkxl'
resolvers > lua > loading file
'/opt/luametatex/texmf-modules/tex/luatex/lua-widow-control/lua-widow-control.lua'
succeeded
close source > l
| formats | executing runner 'run luametatex format':
/Users/hp/Library/context-osx-64/tex/texmf-osx-64/bin/luametatex
--jobname="./tst-account.tex"
--fmt=/Users/hp/Library/context-osx-64/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/c
y, I can also see this:
open source > level 2, order 4, name
'/opt/luametatex/texmf-modules/tex/context/third/lua-widow-control/t-lua-widow-control.mkxl'
resolvers > lua > loading file
'/opt/luametatex/texmf-modules/tex/luatex/lua-widow-control/lua-widow-control.lua'
succeeded
cl
one".
But I didn't give it any importance, because I interpreted that they
could be inherent to the module.
I can see "modules > 'lua-widow-control' is loaded".
But, luckily, I can also see this:
open source > level 2, order 4, name
'/opt/luametatex/texmf-module
lua yields what you
would expect:
/opt/luametatex/texmf-modules/tex/luatex/lua-widow-control/lua-widow-control.lua
Thanks again for your work and yours observations.
Edu.
El 25/4/22 a las 22:00, Max Chernoff escribió:
(Please keep me CC'd as I'm not subscribed to the list)
Hi, I'm the
(Please keep me CC'd as I'm not subscribed to the list)
Hi, I'm the lua-widow-control author.
> lua error > lua error on line 74 in file
>
/opt/luametatex/texmf-modules/tex/context/third/lua-widow-control/t-lua-widow-control.mkxl
>
> The odd thing is that line 75 of the t-lu
Hi,
I would like to know if anyone has experienced the same error with the
lua-widow-control module when compiling the pdf:
modules > 'lua-widow-control' is loaded
open source > level 2, order 3, name
'/opt/luametatex/texmf-modules/tex/context/third/lua-widow-control/t-lua-widow-contro
El 21/4/22 a las 22:08, Eduardo Bohoyo escribió:
Hi,
I would like to know if anyone has experienced the same error with the
lua-widow-control module when compiling the pdf:
modules > 'lua-widow-control' is loaded
open source > level 2, order 3, name
'/opt/luametatex/texmf-modul
standalone installation and
> > do a fresh install
>
> I don’t think it would work, since it only works with LuaMetaTeX.
>
> I got the same results (in Windows [because I cannot make it work in
> Linux]) with LuaTeX 1.15 (the one that comes with ConTeXt LMTX).
>
»: never update ConTeXt
without a backup first.
> [...]
> Therefore i have the following questions
> - would it help to sacrifice the updated standalone installation and
>do a fresh install
I don’t think it would work, since it only works with LuaMetaTeX.
I got the same results (i
This is different from the path
>>> given on the wiki. The directory contained three files, two of which were
>>> aliases, libzint.2.10.dylib and libzint.dylib, and an exe file
>>> libzint.2.10.0.0.dylib
>> You have Hombrew installed in a non-standard location.
On 4/13/22 00:27, Bruce Horrocks via ntg-context wrote:
>> On 12 Apr 2022, at 18:14, Pablo Rodriguez via ntg-context
>> wrote:
>>
>> I wonder whether it would be possible that ConTeXt or LuaMeTaTeX could
>> be more verbose about an opened environment that isn’t
> On 12 Apr 2022, at 18:14, Pablo Rodriguez via ntg-context
> wrote:
>
> I wonder whether it would be possible that ConTeXt or LuaMeTaTeX could
> be more verbose about an opened environment that isn’t closed.
$ mtxrun --script check filename.tex
is something I learned
les linked into /usr/local/bin.
But, assuming other Homebrew commands work when run from Terminal then you
might still be okay.
3) I created the path $TEXROOT/tex/texmf-osx-64/bin/lib/luametatex/zint and
copied libzint.2.10.0.0.dylib into but replaced dylib with 'so' as suggested on
the w
nd
> > mtx-context | fatal error: return code: 1
> >
> > The one above is a stupid sample. But it took me about two hours to
> > discover what was triggering the fatal error message.
> >
> > I wonder whether it would b
sed pages,
>1 shipped pages, 2.592 pages/second
> mtx-context | fatal error: return code: 1
>
> The one above is a stupid sample. But it took me about two hours to
> discover what was triggering the fatal error message.
>
> I wonder whether it would be possible that C
ped pages, 2.592 pages/second
mtx-context | fatal error: return code: 1
The one above is a stupid sample. But it took me about two hours to
discover what was triggering the fatal error message.
I wonder whether it would be possible that ConTeXt or LuaMeTaTeX could
be more verbose about an ope
a non-standard location. Mine is in
/usr/local/Cellar with the executables linked into /usr/local/bin.
But, assuming other Homebrew commands work when run from Terminal then you
might still be okay.
> 3) I created the path $TEXROOT/tex/texmf-osx-64/bin/lib/luametatex/zint and
> copied libzint.2
On my macOS High Sierra your MWE works fine. Although I remember that
I didn't use Homebrew, but had to build zint manually.
>From log:
optional > using library
'/Users/monty/context/tex/texmf-osx-64/bin/lib/luametatex/zint/libzint.so'
Here it is enough that
libzint.so be a link:
libz
aliases, libzint.2.10.dylib and libzint.dylib, and an exe
file libzint.2.10.0.0.dylib
3) I created the path $TEXROOT/tex/texmf-osx-64/bin/lib/luametatex/zint
and copied libzint.2.10.0.0.dylib into but replaced dylib with 'so' as
suggested on the wiki instructions. So I basically added
lib
ith "mtxrun --script fonts --reload
--force", so I completely remove the contents from
"tex/texmf-cache/luametatex-cache/" (which requires "mtxrun --generate"
after).
"mtxrun --script cache --erase" used to do the same, but I cannot get it
working now (ei
Dear list,
I’m afraid that I have just found out that "mtxrun --scripts cache
--erase" doesn’t delete a single file from the cache.
Here is the output I get:
$ mtxrun --scripts cache --erase
mtx-cache | writable path: /context/tex/texmf-cache/
luametatex-cache/context
framedtext
\input zapf
\stopframedtext
\stoptext
> What version of ConTeXt are you using, Pablo?
Current latest from 2022.04.01 09:37. Binaries for 64bits on both OS.
Just in case it may help, I recommend the following approach.
1. Remove the file OpenSansEmoji.ttf.
2. Remove the directory
udes a "luatex-cache"
directory inside)
When I run "mtxrun --generate", all required files are generated in
"$HOME/context/tex/texmf-cache/luametatex-cache".
I wonder why "mtrun --generate" doesn’t generate a "luatex-cache"
directory in the same dire
When I run "mtxrun --generate", all required files are generated in
"$HOME/context/tex/texmf-cache/luametatex-cache".
I wonder why "mtrun --generate" doesn’t generate a "luatex-cache"
directory in the same directory containing "luametatex-cache".
nerate", all required files are generated in
"$HOME/context/tex/texmf-cache/luametatex-cache".
I wonder why "mtrun --generate" doesn’t generate a "luatex-cache"
directory in the same directory containing "luametatex-cache".
BTW, the
> the following:
>
> *\mathcal{A}*
>
> Then I try to compile the test_context.tex file:
>
> *context test_context.tex*
>
> Which unfortunately results in an error:
>
>
> *resolvers | formats | executing runner 'run luametatex format':
> C:/context/tex/texmf-
;
> \mathcal{A}
>
> Then I try to compile the test_context.tex file:
>
> context test_context.tex
>
> Which unfortunately results in an error:
>
> resolvers | formats | executing runner 'run luametatex format':
> C:/context/tex/texmf-win64/bin/lua
test.tex*
Pandoc appears to successfully generate a file test_context.tex containing
the following:
*\mathcal{A}*
Then I try to compile the test_context.tex file:
*context test_context.tex*
Which unfortunately results in an error:
*resolvers | formats | executing runner 'run luametatex format
results in an error:
*resolvers | formats | executing runner 'run luametatex format':
C:/context/tex/texmf-win64/bin/luametatex --jobname="./test_context.tex"
--fmt=C:/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.f
unfortunately results in an error:
*resolvers | formats | executing runner 'run luametatex format':
C:/context/tex/texmf-win64/bin/luametatex --jobname="./test_context.tex"
--fmt=C:/context/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/c
Hi all,
with the new upload, for me on Win64 the zint module does not work yet.
>cmd /c context test.tex && start sumatrapdf test.pdf
test.log:
resolvers | formats | executing runner 'run luametatex format':
C:/context/tex/texmf-win64/bin/luametatex --jobname="./te
in/lib/luametatex/zint/libzint.dll', quitting
mtx-context | fatal error: return code: 1
So, latest version in Windows breaks compilation on my computer.
What am I doing wrong?
Many thanks for your help,
Pablo
___
I
Hi Pablo,
You are correct, the LuaMetaTeX file is still expecting the old "isbn" as
the name, whereas the MKIV running zint directly requires the new one with
"isbnx".
Not sure with which zint version the "isbn" got changed to "isbnx".
@Hans Hagen can
width=4cm]
> >\stoptext
> >
> > Error message is rather weird on Linux:
> >
> >optional> using library '/home/ousia/context/tex/texmf-linux-
> > 64/bin/lib/luametatex/zint/libzint.so'
> >zint> unknown barcode alte
]
\barcode[alternative=isbnx, text=9783865419026, width=4cm]
\stoptext
Error message is rather weird on Linux:
optional> using library '/home/ousia/context/tex/texmf-linux-
64/bin/lib/luametatex/zint/libzint.so'
zint> unknown barcode alternative 'isbnx'
Error message is rather weird on Linux:
optional> using library '/home/ousia/context/tex/texmf-linux-
64/bin/lib/luametatex/zint/libzint.so'
zint> unknown barcode alternative 'isbnx'
zint>
zint> valid barcode alternat
ings and you can open it later by double-clicking it, like any saved
app.
Hope it helps !
JP
Le 12/03/2022 à 17:18, Gavin via ntg-context a écrit :
Hi Mojca,
I think my security settings are preventing me from using this luametatex file.
When trying to update the installation, I got a windo
On 3/12/2022 5:18 PM, Gavin wrote:
Hi Mojca,
I think my security settings are preventing me from using this luametatex file.
When trying to update the installation, I got a window that says:
“luametatex” can’t be opened because Apple cannot check it for
malicious software.
When I
On 3/12/2022 5:18 PM, Gavin wrote:
Hi Mojca,
I think my security settings are preventing me from using this luametatex file.
When trying to update the installation, I got a window that says:
“luametatex” can’t be opened because Apple cannot check it for
malicious software.
When I
Hi Mojca,
I think my security settings are preventing me from using this luametatex file.
When trying to update the installation, I got a window that says:
“luametatex” can’t be opened because Apple cannot check it for
malicious software.
When I tried running mtxrun --generate
Hi Mojca,
> Gavin, are you willing to try the binary from
>https://dl.contextgarden.net/build/luametatex/arm64-darwin/
> ?
I am willing to try. I downloaded the luametatex file at that address, but I’m
not sure what to do with it. Do I just replace the luametatex in my
ins
Hans,
I manually uploaded luametatex for arm64-darwin now.
Not that I actually checked anything.
Gavin, are you willing to try the binary from
https://dl.contextgarden.net/build/luametatex/arm64-darwin/
?
Mojca
exmf-osx-64/bin/context: No such file or
directory
mtx-install |
mtx-install |
mtx-install | ConTeXt LMTX with LuaMetaTeX is still experimental and
when you get a crash this
mtx-install | can be due to a mismatch between Lua bytecode and the
engine. In that case you can
mtx-install
ectory
mtx-install |
mtx-install |
mtx-install | ConTeXt LMTX with LuaMetaTeX is still experimental and
when you get a crash this
mtx-install | can be due to a mismatch between Lua bytecode and the
engine. In that case you can
mtx-install | try the following:
mtx-install |
m
On Sun, Feb 13, 2022 at 11:33 AM Henning Hraban Ramm via ntg-context <
ntg-context@ntg.nl> wrote:
> WTF, someone wrote a LaTeX format for LuaMetaTeX already 3 years ago:
> https://github.com/zauguin/luametalatex
>
>
>
sure -- he is not "someone"
WTF, someone wrote a LaTeX format for LuaMetaTeX already 3 years ago:
https://github.com/zauguin/luametalatex
(Herbert Voss just pointed me to it.)
Hraban
___
If your question is of interest to others as well
kIV, before AUR moved to
git. Not the AUR link has the latest PKGUILD.
> But following Hans kind advice I shall keep a low profile
> and wait for a safer version:)
The PKGBUILD for luametatex will install the latest _released_ vers
> On 1/27/2022 7:35 PM, Aditya Mahajan via ntg-context wrote:
>
> > 2. luametatex: https://aur.archlinux.org/packages/luametatex/
> Just an additional warning: one should not pick up bins from the build farm
> unless oen knows what's happening ... the current builds are okay f
upload. What is
the best method for this?
BTW, I am not sure which PKGBUILD you mean exactly. Note that there
are two PKGBUILDs for context on AUR:
1. context-minimal-git:
https://aur.archlinux.org/packages/context-minimals-git/#news
which installs ConTeXt MkIV
2. luametatex: https
On 1/27/2022 7:35 PM, Aditya Mahajan via ntg-context wrote:
2. luametatex: https://aur.archlinux.org/packages/luametatex/
Just an additional warning: one should not pick up bins from the build
farm unless oen knows what's happening ... the current builds are okay
for Mikael and me while
hich installs ConTeXt MkIV
2. luametatex: https://aur.archlinux.org/packages/luametatex/
which installs LuaMetaTeX.
So you probably need to use the luametatex PKGBUILD.
Aditya
___
If your question is of interest to o
: This is LuaMetaTeX 2.09.36 <> bin: This
is LuaMetaTeX 2.09.34), forcing remake
grep -r '09.34' finds a coincidence in mtxrun.exe. Is anyone else facing
this issue?
Are mtxrun.exe and context.exe copies of luametatex.exe (or links to
it)? They all should be the same.
Hi everyone! I've just installed ConTeXt on an old machine running Windows
8.1 (x86) and I've noticed the format is regenerated each time I process a
file. It can be read on the log (third line):
warning: engine mismatch (luv: This is LuaMetaTeX 2.09.36 <> bin: This is
LuaMetaTeX 2
}\mathrad {x}$\par
\stopTEXpage
tex has a few abstractions (thinmuskip etc) than basically postpone a
setting so that they can be adapted by setting these 'special - internal
in luametatex speak - mu glue registers' but is is being generalized so
that we can group math (integer, dimension, glue
the math machinery: constructs,
spacing etc in the perspective of what luametatex provided.
- We think we can improve spacing (more consistent) but it needs some
work and testing. Some gets shifted from engine heuristics to
predictable control.
- There will be a 'traditional swedish' spacing
gt;
>>> from the log:
>>>
>>> -
>>> fonts > otf loading > loading 'stixtwotext-regular.otf', hash
>>> 'stixtwotext-regular'
>>> otf reader > unknown version '
>>>
>>>
>>>
>>> ' in
wotext-regular.otf' in cache
system > lua > compiling
'/Users/hp/Library/context-osx-64/tex/texmf-cache/luametatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otl/stixtwotext-regular.tma'
into
'/Users/hp/Library/context-osx-64/tex/texmf-cache/luametatex-cache/context/5fe6
s//:/System/Library/ColorSync/Profiles//:'
>
> PATH=~/lmtx/tex/texmf-osx-64/bin:/Library/TeX/texbin:...
> (whereever you installed ConTeXt)
context, latex, mtxrun, mtxrun.lua are installed in
/Users/xxx/context/tex/texmf-osx-64/bin … I’ve forgotten that CTX doesn’t exist
no more since i
with LuaMetaTeX, Version 2.09.35 and ConTEXt 2021.12.30 19:03
*T*
fixed in next upload
(there might be a few more places that need adapting to compact)
Hans
-
Hans Hagen | PRAGMA ADE
Enabling compact fonts results in incorrect initials.
\enableexperiments[fonts.compact]
\starttext
\placeinitial
Tested with \luatexbanner and \ConTeXt\ \contextversion
\stoptext
Produces (approximately):
ested with LuaMetaTeX, Version 2.09.35 and ConTEXt 2021.12.30 19:03
number mode 'scaled'
metapost> trace > This is MPLIB for LuaMetaTeX, version 3.11, running
in scaled mode.
metapost> trace >
metapost> trace > loading metafun for lmtx, including the plain 1.004
base definitions
metapost> trace >
metafun
On 12/16/2021 3:01 PM, Ramkumar KB wrote:
Hans,
Thank you. Just to clarify, in my current installation - context and
mtxrun are already symlinks to the luametatex.
best make a copy of your tex directory and install in there
(btw, why is a new luametatex bin needed? are you sure the rest
Hans,
Thank you. Just to clarify, in my current installation - context and mtxrun
are already symlinks to the luametatex.
So all I need to do is replace the luametatex binay (dl from the build
server - debian9 build)? I also notice the luatex binary - I just leave it
as is?
best regards
eplace the luametatex binary after download the binary from
the build server? Is this correct?
keep in mind that context code and bin have to be in sync (at least as
long as we move on)
basically three bins: luametatex, context and mtxrun but the last two
can be symlinks to luametatex
Hello All,
If I have to just upgrade my context version installed in my linux VM
(x88-64 - amd - redhat) - is debain9 the correct package?
https://build.contextgarden.net/#/ - So I just replace the luametatex
binary after download the binary from the build server? Is this correct?
Thank you
as it's more 'an example of possibilities' code to luametatex
yet ... fwiw, we still share some lua files between engines.
Thanks for looking into that. I'll check the next upload.
- Afaiks you should now get return code 1 for other cases (say you
give \foo without meaning). It's a it tricky
401 - 500 of 1150 matches
Mail list logo