ng 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 --redi
hrough the `open_data_file` callback, so even if they
are closed they probably should be closed by calling the `.close` member
of the returned table. But that never happens (This might be a related
bug: In my experiments, even for files loaded with `\input`, the close
function is never called.)
{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
On my system (linux x64, latest lmtx) this results in
mtx-context | fatal error: return code: 139
Running the command after "executing runner 'run luametatex format':"
directly gives
segmentation fault (core dumped)
/home/marcel/lmtx-install/tex/texmf-linux-64/bin/lu
the binary from the following link but only the 32bit
version for Windows is up-to-date.
http://dl.contextgarden.net/build/luametatex/
Wolfgang,
many thanks for the information.
Pablo
--
http://www.ousia.tk
only the 32bit
version for Windows is up-to-date.
http://dl.contextgarden.net/build/luametatex/
Wolfgang,
many thanks for the information.
Pablo
--
http://www.ousia.tk
___
Hallelulah! I now have a working LMTX again
but only the 32bit
> version for Windows is up-to-date.
>
> http://dl.contextgarden.net/build/luametatex/
Wolfgang,
many thanks for the information.
Pablo
--
http://www.ousia.tk
___
If your question is of interest
You can download the binary from the following link but only the 32bit
version for Windows is up-to-date.
http://dl.contextgarden.net/build/luametatex/
Wolfgang
___
If your question is of interest to others as well, ple
ck-exp.lua 2020-05-19 02:13:54.961276226 -0400
+++ /opt/luametatex/texmf-context/tex/context/base/mkiv/back-exp.lua
2020-05-19 02:13:01.687385009 -0400
@@ -2305,8 +2305,10 @@
if not p then
-- skip
elseif exportproperties ==
he/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex
resolvers | formats | luatex engine: luametatex
resolvers | formats | lua startup file :
C:/Users/MADELEN/Downloads/context-win64/tex/texmf-context/tex/context/base/mkiv/luat-cod.lua
resolvers | formats | context fi
| binary path : C:/lmtx/tex/texmf-win64/bin
resolvers | formats | format path :
C:/lmtx/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1f32e/formats/luametatex
Dear list,
the “LuaMeTaTeX Reference Manual” describes that the command line
argument "--nodates" removes time dependent information in the output file.
I’m afraid it doesn’t work. "\enabledirectives[backend.date=no]" doesn’t
work either.
This is really useful to be able t
cross compiler under WLS (1). I also compile native binaries (a little
slower than the cross compiled but a smaller file) and clang binaries
(much slower and larger). The farm also has a windows set up now for
luametatex but I just use the ones I make here. So, what gets shipped,
the mingw ones, s
On 5/9/2020 6:26 PM, Giulio Bertellini wrote:
>> sh-3.2# context metafun
Ha, I admit that I never tried that yet with lmtx. (The reason is that I
then have to enter updating mode for all these new features. More
something for end-of-the-year dark evenings with a stack of new cd's.)
>> m
On 5/9/2020 12:26, Giulio Bertellini wrote:
*
*
*about LuaMetaTeX, Version 2.06.02* On Mac OS Catalina 10.15.4 .
Hope this may convey some useful information. On Mac OS Catalina
10.15.4 ( Mac mini late 2012, I5, 16GB RAM), using the current LMTX
version just downloaded from Pragma Ade, I
*about LuaMetaTeX, Version 2.06.02* On Mac OS Catalina 10.15.4 .
Hope this may convey some useful information. On Mac OS Catalina 10.15.4 (
Mac mini late 2012, I5, 16GB RAM), using the current LMTX version just
downloaded from Pragma Ade, I installed Context LMTX and tested the
download by
On 5/9/2020 09:33, Hans Hagen wrote:
On 5/9/2020 3:27 PM, Rik Kabel wrote:
On 5/9/2020 02:52, Hans Hagen wrote:
looks like a wrong binary .. should be 2.06.02 .. can you try this
binary:
http://dl.contextgarden.net/build/luametatex/x86_64-darwin/
(the farm generates two binaries for osx
On 5/9/2020 3:27 PM, Rik Kabel wrote:
On 5/9/2020 02:52, Hans Hagen wrote:
looks like a wrong binary .. should be 2.06.02 .. can you try this
binary:
http://dl.contextgarden.net/build/luametatex/x86_64-darwin/
(the farm generates two binaries for osx and it looks like the legacy
machine
On 5/9/2020 02:52, Hans Hagen wrote:
looks like a wrong binary .. should be 2.06.02 .. can you try this
binary:
http://dl.contextgarden.net/build/luametatex/x86_64-darwin/
(the farm generates two binaries for osx and it looks like the legacy
machine has gone off line which happens when osx
Hi Benjamin,
Thanks for sharing your nice code, which is very useful.
However I wanted to let you know that it seems it does not work correctly with
LuaMetaTeX version 2020.04.30 11:10, even though it works fine with ConTeXt
mkiv.
Best regards: Otared K.
> On 9 May 2020, at 12:39, Benja
On 5/9/2020 4:50 AM, Jeong Dal wrote:
Hi,
I tried to update luametatex which was running well(it was installed
following the process in the wiki>installation> MacOsX catalina), but I
got the following error after all the files are downloaded.
resolvers > lua > loading f
Hi,
I tried to update luametatex which was running well(it was installed following
the process in the wiki>installation> MacOsX catalina), but I got the following
error after all the files are downloaded.
resolvers > lua > loading file
'/Users/graph/ConTeXtL/tex/
...xt/tex/texmf-context/tex/context/base/mkiv/l-package.lua:325: error
loading module 'mapm' from file './mapm.so':
./mapm.so: undefined symbol: lua_settop
I believe that the luametatex binary is stripped, so there any unused s
get a message or crash when that doesn't work out)
luajittex has a limited stack of 8000 so it will also crash
luametatex uses lua 5.4 which uses a bit different stack model and can't
go that high (it has a default of 2000 but i will bnump that to 6000
which still seems to work ok, that way
My update script reports:
2020-04-27T12:40:53 ConTeXt updated from 2020.04.19T19:43 to
2020.04.26T19:59
2020-04-27T12:40:53 LuaMetaTeX updated from 2.05.02 to 2.05.01
2020-04-27T12:40:53 LuaMetaTeX functionality updated from 20200413
to 20200402
Is this an intentional rollback
e .. could be an interesting new
(luametatex) option as it saves kerns in some cases)
My use cases of negative vrule is a little tricky. I'm trying to comply with
W3C's [Requirements for Japanese Text Layout](https://www.w3.org/TR/jlreq/).
It states that
In principle, closing brackets
, the result looks as if there is no `\vrule' between `a' and `b'. And if
I run with `context --engine=luatex', the expected result is back. I have
checked the luametatex manual but it doesn't seem to mention the difference. My
luametatex version is
mkiv lua stats > used e
, the result looks as if there is no `\vrule' between `a' and `b'. And if
I run with `context --engine=luatex', the expected result is back. I have
checked the luametatex manual but it doesn't seem to mention the difference. My
luametatex version is
mkiv lua stats >
vrule' between `a' and `b'. And if
I run with `context --engine=luatex', the expected result is back. I have
checked the luametatex manual but it doesn't seem to mention the difference. My
luametatex version is
mkiv lua stats > used engine: luametatex version: 2.0502,
func
As per the fuller console output I included (where you can find all the details
of the run as put out by ConTeXt):
This is LuaMetaTeX, Version 2.05.01
open source > level 1, order 1, name 'cont-yes.mkiv'
system >
system > ConTeXt ver: 2020.04.03 1
gt;
> (Latest ConTeXt on MacOS Mojave.)
No such luck for me. Any help welcome. I did remove the macOS font cache with
sudo atsutil databases -remove and I rebooted. I am running an up to date macOS
Mojave.
\starttext
\definefontfamily[mainface][rm][Optima]
\setupbodyfont[mainface,10pt]
{\bf
Live 2019)
system commands enabled.
2)
resolvers | formats | executing runner 'run luametatex format':
/Users/charlesdoherty/context-osx-64/tex/texmf-osx-64/bin/luametatex
--jobname="Newsletter2019-20"
--fmt=/Users/charlesdoherty/context-osx-64/tex/texmf-cache/luatex-ca
#x27; resolvers | resolving |
> looking for fallback 'contextcnf.lua' on given path
> '/home/gour/opt/texmf-dist/web2c' from specification
> 'selfautoparent:/texmf-dist/web2c' resolvers | resolving |
> looking for fallback 'contextcnf.lua
serif-devanagari-fonts
available for Fedora, it still does not work:
$ context t.tex
resolvers | formats | executing runner 'run luametatex format':
/home/gour/opt/lmtx/tex/texmf-linux-64/bin/luametatex --jobname="t"
--fmt=/home/gour/opt/lmtx/tex/texmf-cache/luatex-cache/contex
t
which I would like to quote - I am somewhat familiar with latin transliteration
via diacritics, but completely ignorant in regard to Devanagari - but wonder
what is required to make ConText (lmtx) typeset it?
Here is the log file:
$ context t.tex
resolvers | formats | executing runne
On 4/19/2020 12:44 PM, Henning Hraban Ramm wrote:
Am 19.04.2020 um 11:57 schrieb Hans Hagen :
As a side note: a while ago mojca and i discussed the future repository and
installation setup which will use github repositories
(1) - context (including luametatex sources)
(2) - binaries (for
?
I'm using LuaMetaTex Version 2.05.01 ConTeXt ver: 2020.04.03 10:31 MKIV
beta fmt: 2020.4.6 int: english/english
Thanks and stay safe.
Best Wishes
Keith McKay
%%% MWE %%% \setuppapersize[A4,landscape]
\definelayer[mybg]
[x=0mm, y=0mm,
width=\paperwidth, h
> Am 19.04.2020 um 11:57 schrieb Hans Hagen :
> As a side note: a while ago mojca and i discussed the future repository and
> installation setup which will use github repositories
>
> (1) - context (including luametatex sources)
> (2) - binaries (for a subset of platforms)
a while ago mojca and i discussed the future repository
and installation setup which will use github repositories
(1) - context (including luametatex sources)
(2) - binaries (for a subset of platforms)
(3) - resources (like fonts and such)
(4) - modules (stable ones pushed from the main garden rep
Hans Hagen schrieb am 03.04.2020 um 11:07:
Hi,
One problem of mixed usage of mkiv (with luatex) and lmtx (with
luametatex) is that in the later we use a different (initial) context
runner. Basically all platforms are now handled the same (in mkiv there
was a stub and no texlua, in unix
On Thu, 16 Apr 2020, kaddour kardio wrote:
Pablo yes I meant 'mtxrun'.
Hans by googling about my issue I found a commentary by Aditya of the issue
on the git repos.
Which git repo?
I maintain the luametatex AUR for archlinux. So, if the install script
asked you to run `mtx-run
Dear list,
this is a new experience deep inside LuaMetaTeX (for me).
I need to compose a new document from selected pages (which are marked
automatically and stored in /PrintPageRange) in a PDF document
containing 1000 pages.
It has to be one of the worst coding snippets ever written, but it
Pablo yes I meant 'mtxrun'.
Hans by googling about my issue I found a commentary by Aditya of the issue
on the git repos.
Le jeu. 16 avr. 2020 à 08:51, Pablo Rodriguez a écrit :
> On 4/16/20 1:14 AM, kaddour kardio wrote:
> > running `mtx run ---generate` with 3 dashes fixed the issue.
> > [.
On 4/16/20 1:14 AM, kaddour kardio wrote:
> running `mtx run ---generate` with 3 dashes fixed the issue.
> [...]
> mtx-run --generate
> give me this error
> unknown script 'cache.lua' or 'mtx-cache.lua'
Sorry, but I think the command reads:
mtxrun --generate
I mea
On 4/16/2020 1:14 AM, kaddour kardio wrote:
running `mtx run ---generate` with 3 dashes fixed the issue.
strange ; nothing has changed in that code so why three dashes
Hans
-
Hans Hagen
running `mtx run ---generate` with 3 dashes fixed the issue.
Le jeu. 16 avr. 2020 à 00:03, kaddour kardio a
écrit :
> Hi! my issue is probably only distro related but i was unable to use
> luametatex after an update from AUR repos in Archlinux.
> running
> mtx-run --genera
Hi! my issue is probably only distro related but i was unable to use
luametatex after an update from AUR repos in Archlinux.
running
mtx-run --generate
give me this error
unknown script 'cache.lua' or 'mtx-cache.lua'
--
Dr YAHYAOUI Mohamed
rt expect a number between 1 and 7 and
> result in a label for the requested day of the week but it's not meant
> to be used in \currentdate.
>
> > Still using luatex and not luametatex.
>
> To get the short names with \currentdate you have to append ":mnem" to
&g
t expect a number between 1 and 7 and
result in a label for the requested day of the week but it's not meant
to be used in \currentdate.
Still using luatex and not luametatex.
To get the short names with \currentdate you have to append ":mnem" to
the weekday, w, WEEKDAY or
\date[d=8,m=4,y=2008][{\dayshort\normalday},{,~},day,~,month,~,year]
\stoptext
This gives me (note "sun" is missing in the second line):
sat, 7 April 2008
, 8 April 2008
Am I using the options correctly?
Still using luatex and not luametatex.
ConTeXt ver: 2020.04.08 14:34 MKIV
e
> the engine in the usual way with "% engine=luatex" at the top line of the
> source file (but no pdftex and xetex in this installer).
I updated LMTX on MacOSX 10.13 today.
The luatex binary in not executable, thus when I run
axel$ context --luatex --version
mtx-context
Hi,
One problem of mixed usage of mkiv (with luatex) and lmtx (with
luametatex) is that in the later we use a different (initial) context
runner. Basically all platforms are now handled the same (in mkiv there
was a stub and no texlua, in unix something shebang with texlua because
of
Dear Hans,
Thank you for the examples. Usually glue is only set at the end of a
list and the last active glue will be used, so the \frozen mechanism is
a bit confusing maybe. Anyway, is there an ETA for the release of the
luametatex source? I'd really like to see how \frozen is implem
Now, to come to your question / remark, it is trivial to introduce a
parameters, say \mathspacingmode, that obeys these spacing options
(apart from possible weird side effects) but they are global.
However, in luametatex we can do this:
\def\whatevera
{\frozen\Umathordrelspacing \texts
On 3/11/2020 4:54 PM, Axel Kielhorn wrote:
Hello Hans and mailing list!
Thank you so much.
With this example and the help I received earlier from Massi,
I’ve been able to write my first finalizer today.
It is amazing how powerful luatex is.
indeed (and luametatex is supposed to be even bit
Hi,
I uploaded an update of lmtx. The current version of luametatex is 2.05
which is kind of the first supposedly stable release because it
incorperates most of what was on my agenda for the first phase
(functionality level 20200229 which was when it happened). Of course I
expect there to be
another way to install the "t-letter" module for use with LMTX?
>>
>
> #!/bin/sh
>
> # Install or update texmf-modules
> # Requires: awk, rsync
>
> # Check whether LuaMetaTeX is available
> if ! command -v luametatex > /dev/null; then
>echo
>
> and then run with --mode=epub
I am running with:
mtxrun --autogenerate --mode=epub --script context "$1"
but no epub document is generated, just the same result.pdf I get without that
mode.
In .bashrc using:
# The current version of the ConTeXt luametatex in use:
CONTE
e.svg" ] ;
\stopMPcode
I get this error.
! Not implemented: (unknown numeric)=(string).
]
<*> ... ; p := lmt_svg [ filename = "sample.svg" ]
That's because it's LMTX only (the "lmt" prefix of "lmt_svg" should
stand for "luametatex").
Y
aw lmt_svg [ filename = "sample.svg" ] ;
>>>> \stopMPcode
>>> I get this error.
>>>
>>> ! Not implemented: (unknown numeric)=(string).
>>>
>>> ]
>>> <*> ... ; p := lmt_svg [ filename = "sample.svg" ]
>&
MPcode
>> I get this error.
>>
>> ! Not implemented: (unknown numeric)=(string).
>>
>> ]
>> <*> ... ; p := lmt_svg [ filename = "sample.svg" ]
>>
> That's because it's LMTX only (the &q
t_svg [ filename = "sample.svg" ]
That's because it's LMTX only (the "lmt" prefix of "lmt_svg" should
stand for "luametatex").
You find documentation about that in LMTX docs, luametafun.pdf, chapter
"SVG".
Best wishes,
Massi
___
characters are misplaced in MkXL with hz enabled. I
think this might be a bug.
hm, i uploaded a maybe better variant
Many thanks for the new version, Hans.
It works much better now. Dos the improvement come from the new
LuaMetaTeX binary?
not this time. its from usage
Hans
e misplaced in MkXL with hz enabled. I
>> think this might be a bug.
>
> hm, i uploaded a maybe better variant
Many thanks for the new version, Hans.
It works much better now. Dos the improvement come from the new
LuaMetaTeX binary?
Many than
s for clarifying. I’ve set up the mirror so the “beta”
branch will be continued from “latest”.
> > PS: I’m out of the loop; is the mirror actually still needed or
> > is there an official repo now?
> Mojca is working on a repository setup for sources (what we have now but
&g
4/bin/luametatex
b95ca64fabcb3f09edd861c4b87671cc bin/mtxrun
b95ca64fabcb3f09edd861c4b87671cc tex/texmf-linux-64/bin/luametatex
$ md5sum bin/mtxrun.lua tex/texmf-linux-64/bin/mtxrun.lua
4d73c3608cc2463e80c59942b3db7158 bin/mtxrun.lua
4d73c3608cc2463e80c59942b3db7158 tex/texmf-linux-64/bin/mtxrun.lua
On 15-02-2020 06:40, Rudolf Bahr wrote:
> I hope this helps you! At least in the case you're using linux.
it appears as that many of the files in the two path are sort of identical:
~/data/context
$ md5sum bin/mtxrun tex/texmf-linux-64/bin/luametatex
b95ca64fabcb3f09edd861c4b8767
Wolfgang's t-letter module, you can use
>
> first-setup.sh --modules="t-letter"
>
>
> BUT, the LMTX standalone does not have any "first-setup.sh" shell script.
>
> Is there another way to install the "t-letter" module for use with LMTX?
>
t
This document was produced using version \contextversion\ of
\ConTeXt\ \doifelse{\texenginename}{luametatex}{LMTX}{\contextmark}
with the version \texengineversion\ of \texenginename.
\attachment[file=./\jobname.tex,
method={\do
The output of ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun --generate is
> > big,
> > so I append it here by the file "Aditya-I".
> > It's made by
> > LuaMetaTeX, Version 2.03.15
> > ConTeXt ver: 2020.02.11 16:41 MKIV beta fmt: 2020.2.11
>
>
whereis mtxrun" gives:
> > > > ~/context-lmtx/bin/mtxrun.lua
> > > > ~/context-lmtx/bin/mtxrun
> > > > ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun.lua
> > > > ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun
> > > i assume th
correctly).
Hi Aditya!
Thank you for your answer!
The output of ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun --generate is big,
so I append it here by the file "Aditya-I".
It's made by
LuaMetaTeX, Version 2.03.15
ConTeXt ver: 2020.02.11 16:41 MKIV beta fmt: 2020.2.11
ya!
Thank you for your answer!
The output of ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun --generate is big,
so I append it here by the file "Aditya-I".
It's made by
LuaMetaTeX, Version 2.03.15
ConTeXt ver: 2020.02.11 16:41 MKIV beta fmt: 2020.2.11
Just for fun (but perh
hash 'dcb651482955ac31eaab7723b70e0184'
resolvers | caching | preparing 'files' for 'selfautoparent:texmf'
resolvers | caching | category 'files', cachename 'selfautoparent:texmf' saved in '/home/rbm49/lmtx/tex/texmf-cache/luatex-cache/conte
'files' for 'selfautoparent:texmf'
resolvers | caching | category 'files', cachename 'selfautoparent:texmf' saved in '/home/rbm49/lmtx/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/trees/dcb651482955ac31eaab7723b70e0184.lua&#
inux-64/bin/mtxrun.lua
> ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun
i assume that you run the last one in this list, which is a copy of or link
to the luametatex binary in the texmf-linux-64/bin path
Hans, thank you for your answer!
So I run explicitly the second one:
~/context-lmtx/bi
run.lua
> > ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun
> i assume that you run the last one in this list, which is a copy of or link
> to the luametatex binary in the texmf-linux-64/bin path
Hans, thank you for your answer!
So I run explicitly the second one:
~/context-lmtx/bi
On Tue, 11 Feb 2020, Rudolf Bahr wrote:
On Tue, Feb 11, 2020 at 04:57:15PM +0100, Pablo Rodriguez wrote:
On 2/11/20 4:23 PM, Rudolf Bahr wrote:
>
> How should it be possible to mix mkiv and lmtx, when I install "LuaMetaTeX
2.03.15"
> and "ConTeXt 2020.02.10 MKIV bet
is a copy of or
link to the luametatex binary in the texmf-linux-64/bin path
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel:
On Tue, Feb 11, 2020 at 04:57:15PM +0100, Pablo Rodriguez wrote:
> On 2/11/20 4:23 PM, Rudolf Bahr wrote:
> >
> > How should it be possible to mix mkiv and lmtx, when I install "LuaMetaTeX
> > 2.03.15"
> > and "ConTeXt 2020.02.10 MKIV beta" in my
On 2/11/20 4:23 PM, Rudolf Bahr wrote:
>
> How should it be possible to mix mkiv and lmtx, when I install "LuaMetaTeX
> 2.03.15"
> and "ConTeXt 2020.02.10 MKIV beta" in my linux directory "~/context-lmtx",
> correct
> the PATH variable after in
On Tue, Feb 11, 2020 at 01:07:23PM +0100, Hans Hagen wrote:
> On 2/11/2020 11:56 AM, Rudolf Bahr wrote:
> > On Mon, Feb 10, 2020 at 01:03:38PM +0100, Bahr Rudolf wrote:
> > > On Mon, Feb 10, 2020 at 11:54:49AM +0100, Bahr Rudolf wrote:
> > > >
> > > > Hel
On 2/11/2020 11:56 AM, Rudolf Bahr wrote:
On Mon, Feb 10, 2020 at 01:03:38PM +0100, Bahr Rudolf wrote:
On Mon, Feb 10, 2020 at 11:54:49AM +0100, Bahr Rudolf wrote:
Hello ConTeXters!
LuaMetaTeX, Version 2.03.15
ConTeXt ver: 2020.02.07 18:36 MKIV beta fmt: 2020.2.10
works well doing my usual
On Mon, Feb 10, 2020 at 01:03:38PM +0100, Bahr Rudolf wrote:
> On Mon, Feb 10, 2020 at 11:54:49AM +0100, Bahr Rudolf wrote:
> >
> > Hello ConTeXters!
> >
> > LuaMetaTeX, Version 2.03.15
> > ConTeXt ver: 2020.02.07 18:36 MKIV beta fmt: 2020.2.10
> > works
On Mon, Feb 10, 2020 at 11:54:49AM +0100, Bahr Rudolf wrote:
>
> Hello ConTeXters!
>
> LuaMetaTeX, Version 2.03.15
> ConTeXt ver: 2020.02.07 18:36 MKIV beta fmt: 2020.2.10
> works well doing my usual tasks.
>
> Now, I put an .otf-font into ".../tex/texmf-
Hello ConTeXters!
LuaMetaTeX, Version 2.03.15
ConTeXt ver: 2020.02.07 18:36 MKIV beta fmt: 2020.2.10
works well doing my usual tasks.
Now, I put an .otf-font into ".../tex/texmf-local/", and made
mtxrun --generate
mtxrun --script fonts --reload
mtxrun --script fonts --
ficial repo now?
Mojca is working on a repository setup for sources (what we have now but
also including luametatex sources), installation (including binaries
taken from the compile farm), extras (like modules taken from the garden
repository) so at some point we can make those official. Till the
, LuaMetaTeX, ConTeXt and their
practical usage. Talks are not compulsory neither to give nor to attend.
Still everyone is welcome to even few minutes presentation on her/his
experiences or troubles and challenges.
Registration will begin on May 1. There will be cheaper early-bird
period May–June and
w to apply primitives.
Maybe not PlainTeX, but plain TeX.
E.g. we usually use TeX primitives like \def (even if we have \define), while
with LaTeX you use \newcommand, similar with \vbox and others.
I understood LuaMetaTeX, as a stripped-down typesetting engine, would be closer
to the spirit of K
f how to apply primitives.
Maybe not PlainTeX, but plain TeX.
E.g. we usually use TeX primitives like \def (even if we have \define), while
with LaTeX you use \newcommand, similar with \vbox and others.
I understood LuaMetaTeX, as a stripped-down typesetting engine, would be closer
to the spir
On 2/4/20 4:15 PM, Philipp A. wrote:
> Thank you all! What is lmtx? Is there any link with infos?
Dear Philipp,
LuaMetaTeX is LuaTeX developed only for ConTeXt.
More infos:
https://mailman.ntg.nl/pipermail/ntg-context/2019/094476.html
https://mailman.ntg.nl/pipermail/ntg-context/2
Dear all,
as you may have noticed: the 14th ConTeXt Meeting will be held in Sibřina,
Czech Republic on
*September 6–12 (Sun–Sat), 2020*
Meeting people you know from the list is always a great pleasure and fun as
are discussed topics on LuaTeX, LuaMetaTeX, ConTeXt and their practical
usage
: mkii (probaly not used that much any longer)
luatex|luajittex : mkiv (also the test for luatex dev)
luametatex : lmtx (the (upcoming) real deal)
Mojca and I are diuscussing / working on an upgrade of the context
garden installations and repositories but more about that later,
Will lmtx be av
he website).
>
> I like this change.
>
>> A more fundamental distinction is between the versions:
>>
>> pdftex|xetex : mkii (probaly not used that much any longer)
>> luatex|luajittex : mkiv (also the test for luatex dev)
>> luametatex : lmtx (the
e test for luatex dev)
luametatex : lmtx (the (upcoming) real deal)
Mojca and I are diuscussing / working on an upgrade of the context
garden installations and repositories but more about that later,
Will lmtx be available on the next texliv
t from the fact that we no longer
use the labels (and distinction on the website).
A more fundamental distinction is between the versions:
pdftex|xetex : mkii (probaly not used that much any longer)
luatex|luajittex : mkiv (also the test for luatex dev)
luametatex : lmtx (the (upcoming)
incompetent now because linenumbering behaves in unexpected ways:
you can set some values (like the starting number) with the simple
\startlinenumbering command but not all values. And there's this strange
difference between luatex and luametatex... Without this mailing list,
I'd be reall
On Fri, 24 Jan 2020 18:57:50 +0100
Tomas Hala wrote:
>
> Hi Thomas,
>
> I compiled (TL2019) it with as well as without \setbreakpoints[compound] and
> I got the same result -- in both case I see both colours.
The output with LuaTeX is correct but when you use LuaMetaTeX the s
On 1/12/2020 1:23 PM, Ramón Casares wrote:
On Sun, 12 Jan 2020 12:00:55 +0100
Hans Hagen wrote:
On 1/12/2020 8:22 AM, Ramón Casares wrote:
~/context/tex/texmf-linux-64/bin/luametatex --ini lmtx.tex
so what is that call?
luametatex --ini lmtx.tex
what in that tex file?
$ cat
On Sun, 12 Jan 2020 12:42:50 +0100
Hans Hagen wrote:
> On 1/12/2020 8:22 AM, Ramón Casares wrote:
> > ~/context/tex/texmf-linux-64/bin/luametatex --ini lmtx.tex
>
> next version will say:
>
> >luametatex --ini whatever.tex
> This is LuaMetaTeX, Version 2.03.
901 - 1000 of 1181 matches
Mail list logo
