:
- unzip the main zip file
- goto the source subtree
- run build.sh (assumes compiler and cmake installed)
- move the binary file to the relevant bin location
- set symlinks from luametatex to mtsrun and context
- copy mtxrun.lua and context.lue there too
- adapt your path
- maybe add texmf-fonts
022 4:08 PM, amano.kenji wrote:
>
> > Sorry for spamming the list a little bit.
> >
> > If there was something like
> > https://www.linuxfromscratch.org/lfs/view/stable/chapter06/ncurses.html for
> > ConTeXt and luametatex (binary), then distribution maintainer
18th, 2022 at 5:16 PM, Hans Hagen
wrote:
> On 8/18/2022 4:08 PM, amano.kenji wrote:
>
> > Sorry for spamming the list a little bit.
> >
> > If there was something like
> > https://www.linuxfromscratch.org/lfs/view/stable/chapter06/ncurses.html for
> >
On 8/18/2022 4:08 PM, amano.kenji wrote:
Sorry for spamming the list a little bit.
If there was something like
https://www.linuxfromscratch.org/lfs/view/stable/chapter06/ncurses.html for
ConTeXt and luametatex (binary), then distribution maintainers can make
packages for ConTeXt easily.
I
Sorry for spamming the list a little bit.
If there was something like
https://www.linuxfromscratch.org/lfs/view/stable/chapter06/ncurses.html for
ConTeXt and luametatex (binary), then distribution maintainers can make
packages for ConTeXt easily.
I don't know TeX/TeXLive/kpathsea/Co
Imagine installation instructions given by linux from scratch.
install.sh is like `apt-get install ConTeXt`.
Linux from scratch would document the following commands.
```
tar xf luametatex-2022.06.tar.xz
cd /path/to/luametatex-2022.06
make
cp luametatex /usr/bin
tar xf context-2022.06.tar.xz
eXt to. Copying luametatex to /usr/bin is going to be easy.
I never had to understand TexLive/ConTeXt directory structure because I just
used TexLive OS package. Now, I'm stuck reverse-engineering a black box.
Am I supposed to execute the following commands in
https://github.com/contextg
istributions are very particular
about this.
I cannot understand the thrust of this thread.
It appears that the only issue for now concerns the distribution of the
luametatex source tree. This is not yet the case as luametatex has been
undergoing much experimentation. A classic opensource deposito
By the way, all POSIX-like opearting systems including BSDs and linux
distributions share one way of making system packages.
For all POSIX-like operating systems, a simple Makefile can build LuaMetaTex.
Since each linux distribution may have a slightly different directory
structure, it would
re time and money on this
as after all it comes for free).
Mojca and I have been discussing the binary part wrt githib but even
with the relatively small luametatex binaries it's a bit of a challenge
on git. We have some ideas but need time to do it and it doesn't have a
high priori
nfiguration file
>
> there are some boundary conditions:
>
> - we use mtxrun as runner and that one used luatex as lua engine
> - this means that mtxrun[.lua] has to be in the same path as the binary
>
> in lmtx we even go a bit further:
>
> - in lmtx there is mtxrun
; binaries that are either copies or
symlinks to luametatex in the same path
- this is the same on unix and windows
in lmtx luametatex is also used as runner for mkiv when installed
on unix i normally just install the minimal tree and then either add the
bin path to the path or just run mtxrun
http://lmtx.pragma-ade.nl/install-lmtx/texmf-context.zip is not versioned.
If the file changes later, linux distributions refuse to use the file.
I wish ConTeXt and LuaMetaTex were versioned and provided `offline` build
instructions. The vast majority of programs are versioned and can be built
Hi Hans,
> > First, how do I get an insert's class/type from the "insert" nodes on
> > the page? With LuaTeX, the insert's class/type is the same as the
> > subtype of the "ins" nodes, but the subtype of the "insert" nodes is
> >
Okay, I'm seeing a few separate issues here.
1. Gentoo expects to compile everything from source.
This isn't an option here since LuaMetaTeX doesn't have any source
available (yet). So for the time being, you'll need to use the provided
binaries. These suppo
On 8/15/2022 8:18 AM, Max Chernoff via ntg-context wrote:
Hi all,
I'm trying to manipulate some inserts from Lua in LuaMetaTeX, and I'm
having some problems that I'm not having with LuaTeX.
First, how do I get an insert's class/type from the "insert" nodes
Hi all,
I'm trying to manipulate some inserts from Lua in LuaMetaTeX, and I'm
having some problems that I'm not having with LuaTeX.
First, how do I get an insert's class/type from the "insert" nodes on
the page? With LuaTeX, the insert's class/type is the sam
On 8/5/2022 4:37 PM, Aditya Mahajan via ntg-context wrote:
Hi,
I cannot view the onandon.pdf manual. pdfinfo says that it a malformed PDF.
bah, probably i ran some test .. some code there only works in older
luametatex .. (keep in mind that i seldom run these manuals as a whole
so sometimes
fonts are
set up that way). In lmtx (luametatex) primes are native features and
assume dimensions that we can work with (primes and minutes are a
typical example of messed up math unicode).
Hans
taking advantage of floating-point MetaPost (thus
> simplified).
>
>
>
> I have been working on a completely new luagraph module that does much
> in lua. It has, notably, arbitrary coordinate systems.
>
> This has been a moving target as I put more and more into lua
> and less
uch
in lua. It has, notably, arbitrary coordinate systems.
This has been a moving target as I put more and more into lua
and less and less in Metapost. I have also been playing chase with the
development of luametatex (and have fallen behind).
On 7/25/22 14:00, juh+ntg-context--- via ntg-context wrote:
>
> I reported the bug to Mozilla and they answered very fast.
>
> Sadly up too now without a good solution.
Many thanks for the bug report.
> They hint to LuaMetaTex as the cause of the problem. You can follow the
> d
I reported the bug to Mozilla and they answered very fast.
Sadly up too now without a good solution.
They hint to LuaMetaTex as the cause of the problem. You can follow the
discussion here.
https://bugzilla.mozilla.org/show_bug.cgi?id=1781022
juh
d not run/mix lmtx with texlive
- we use luametatex as runner for both luametatex and luatex runs
- mtxrun.lua and context.lua are both in the bin path (as usual)
- mtxrun.exe and context.exe are symlinks to luametatex.exe
that is the same for all platforms but in tex live on windows there is
>> I hope it helps,
>>
>> Pablo
>
> Hi Pablo and Haram,
>
> When I was running mtxrun --generate, there was an interference with TeX
> Live, so I uninstalled it, then it worked. I do not know if that time I did
> run mtxrun. But under TeXworks when I selected contex
t?
the next upload will have a prepare helper
print("=")
local h = nodes.copylist(head)
tex.preparelinebreak(h)
local n = tex.linebreak(h)
nodes.flushlist(n)
print("==
guide at:
https://github.com/AKielhorn/Context-Intro
Just for the record: luametatex is *not* optimized for context, it just
provides (rather generic) stuff not present in other engines that we can
benefit from. That said: of course after decades of context we know what
is missing in tex that we
has to be careful
where linebreak hackery is applied.
Oh yes, I'm well aware :) Earlier versions of my module would silently
eat entire paragraphs, which was very not good. Luckily that problem is
fixed now.
And finally, thanks for all your work with LuaMetaTeX. This new engine
is quite
ore alien 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 w
t describe 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 ar
run-command 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 luam
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)")
("luametat
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
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
ning mtxrun --generate, there was an
interference with TeX Live, so I uninstalled it, then it
worked. I do not know if that time I did run mtxrun. But
under TeXworks when I selected context as program it kept
electing luametatex, and it didn't work; so I manually wrote
&
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
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
end
>
>if n.id == glyph_id then
>back_chars = back_chars + 1
>end
>
> n = n.prev
>end
>
>width = 0
>chars
ed width. Let me
know if this works; 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 "discret
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 lis
e below 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
ex\\'" . 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
>
system > approximate memory: 26048523 (24 MB)
system >
system > expansion depth : min: 1, max: 100, set: 1, top: 5
system >
system > luabytecode registers : 1002
system > luabytecode bytes
xt | ConTeXt Process Management 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 luame
> > '/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
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/
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/libzin
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>
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 it s
;
> % 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 LMT
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 wou
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-6
xperiments.tex'
fonts > preloading latin modern fonts (second stage)
fonts > 'fallback modern-designsize rm 12pt' is loaded
metapost> initializing instance 'metafun:1' using format 'metafun' and
method 'double'
met
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 documen
\credit{Schulden} {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/b
it!)
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-lu
so 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'
| 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/lu
;.
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'
resolvers > lua > loading file
'/opt/luametatex/texmf-modules/tex/luatex/lua-widow-control/lua-wi
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/lua
--find-file lua-widow-control.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
(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
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-l
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/luameta
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
in
>>> /opt/homebrew/Cellar/zint/2.10.0/lib . 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
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
/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.10.0.0.dylib into but replaced dyl
gt; > 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 ConTeX
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 b
which were 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
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
startframedtext
\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 dire
ted (which includes 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 i
ectory 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 directory containing "luametatex
un --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".
.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':
&
;
> \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-win
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 f
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
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/lu
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=
n64/bin/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
___
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 ba
]
\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
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> va
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 window t
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
401 - 500 of 1011 matches
Mail list logo
