most basic uses.
Fortunately, my significantly more demanding needs for a client were met
with the invaluable help from LuaTeX, but that won't be enough for my
own projects, much more complex (facsimile of ancient editions), until
Google improves this font.
So actually the old pre-google fonts
Garamond unusable for anything but the most
basic uses.
Fortunately, my significantly more demanding needs for a client were met with
the invaluable help
from LuaTeX, but that won't be enough for my own projects, much more complex
(facsimile of
ancient editions), until Google improves this font.
Thomas
On 12/25/2021 11:52 PM, Thomas Savary via ntg-context wrote:
Hi Bruce and Hans !
Thank you very much for your answers, that helped me a lot.
In fact, though I would love to switch to ConTeXt one day, I am still
using LuaLaTeX — I am a slow learner and I know it will take me months
to be
Hi Bruce and Hans !
Thank you very much for your answers, that helped me a lot.
In fact, though I would love to switch to ConTeXt one day, I am still using
LuaLaTeX — I am a slow
learner and I know it will take me months to be able to achieve what I need for
my job with
ConTeXt and can do
On 12/25/2021 12:04 AM, Bruce Horrocks via ntg-context wrote:
On 24 Dec 2021, at 18:34, Thomas Savary via ntg-context
wrote:
Hello, dear list !
In order to fix a few bugs in some OpenType features included in EB Garamond
font provided by Google Fonts, I am trying to remove some ligatures
On 12/25/2021 12:04 AM, Bruce Horrocks via ntg-context wrote:
On 24 Dec 2021, at 18:34, Thomas Savary via ntg-context
wrote:
Hello, dear list !
In order to fix a few bugs in some OpenType features included in EB Garamond
font provided by Google Fonts, I am trying to remove some ligatures
> On 24 Dec 2021, at 18:34, Thomas Savary via ntg-context
> wrote:
>
> Hello, dear list !
>
> In order to fix a few bugs in some OpenType features included in EB Garamond
> font provided by Google Fonts, I am trying to remove some ligatures
> (erroneous in some contexts) with
Hello, dear list !
In order to fix a few bugs in some OpenType features included in EB Garamond
font provided by
Google Fonts, I am trying to remove some ligatures (erroneous in some contexts)
with
fonts.handlers.otf.addfeature.
I must be missing something, because I can't get it to work.
of
context is in sync? e.g. Some internal (lua) keys were normalized recently.)
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?
luatex is the same fr a while already
Hans
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
and/or
mechanisms will end up in lmtx. But of course when we find serious bugs
they can get solved. If it works for you it likely will keep working
(assuming that luatex keeps working as it does).
Hans
if the error changed or if I copied the wrong error
message in the OP, but a current LMTX throws:
close source> level 1, order 2, name './t.tex'
(\end occurred when parameter character
luatex warning > print: bad string offset
was incomplete)error (nodes): attempt to doubl
wrong error
message in the OP, but a current LMTX throws:
close source> level 1, order 2, name './t.tex'
(\end occurred when parameter character
luatex warning > print: bad string offset
was incomplete)error (nodes): attempt to double-free glue node 2986, ignored
LMTX 2021.
quot;; now it
makes "sS".
(If the current font contains an uppercase ß that would be even
better, but those are rare).
I can’t tell when it changed (some LMTX versions ago) and can’t check
MkIV, since "mtxrun --generate --luatex" doesn’t work.
Hans sent me a fix, I gues
(If the current font contains an uppercase ß that would be even
better, but those are rare).
I can’t tell when it changed (some LMTX versions ago) and can’t check
MkIV, since "mtxrun --generate --luatex" doesn’t work.
Hans sent me a fix, I guess it will be included in the next upload.
And y
ent font contains an uppercase ß that would be even
better, but those are rare).
I can’t tell when it changed (some LMTX versions ago) and can’t check
MkIV, since "mtxrun --generate --luatex" doesn’t work.
Hans sent me a fix, I guess it will be included in the next upload.
And y
hose are rare).
I can’t tell when it changed (some LMTX versions ago) and can’t check
MkIV, since "mtxrun --generate --luatex" doesn’t work.
Hans sent me a fix, I guess it will be included in the next upload.
And yes, uppercase ß (ẞ, U1E9E) would be even better, even according to
the
ons ago) and can’t check
MkIV, since "mtxrun --generate --luatex" doesn’t work.
Hraban
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl
computational work. This is not easy, but the diagrams are super fast,
> and I think they will always work.
I would be very interested to see an example of a Metafun drawing made with the
help of LuaTeX to speed up some calculations.
Thanks
Confirmed that the following worked:
1. Run: rm -rf /tmp/luatex-cache/ (your cache directory location will
differ)
2. Edit ./tex/texmf-context/tex/context/base/mkiv/scrn-ref.lua
3. Replace line 15 to assign the empty function as Hans indicated
4. Save the file
5. Run: ./bin
Another problem. Maybe that's related?
Running the file with the --luatex flag gives me this error message:
tx-context | redirect luametatex -> luatex: luatex --luaonly
"C:/context/tex/texmf-win64/bin/mtxrun.lua" --script mtx-context --luatex debug
--redirected
mtxrun
get correct results with the –luatex flag
Denis
Von: ntg-context
mailto:ntg-context-boun...@ntg.nl>> Im Auftrag von
Jean-Philippe Rey via ntg-context
Gesendet: Samstag, 27. November 2021 16:22
An: ntg-context@ntg.nl<mailto:ntg-context@ntg.nl>
Cc: Jean-Philippe Rey
mailto:j
Same here, but I get correct results with the –luatex flag
Denis
Von: ntg-context Im Auftrag von Jean-Philippe Rey
via ntg-context
Gesendet: Samstag, 27. November 2021 16:22
An: ntg-context@ntg.nl
Cc: Jean-Philippe Rey
Betreff: [NTG-context] Typographical quotes
Dear list,
When typing
so because
there is even more involved (which i happily let you guess about). I
want clean solution with no fancy (and somewhat obscure) tex macro doing
magic that only a few are supposed to understand.
When we started with luatex, and thereby mkiv, we immediately went full
unicode math (als
: the local box width
> \localboxoffset: the total distance to the edge
> \localboxleftskip : the effective leftskip
> \localboxrightskip : the effective rightskip
> \localboxlefthang : the current shape related value
> \localboxrighthang :
>>> would be interesting to hear about this from this community.
> >
> >> for sure i need more than an email to give a real answer (and some can
> >> be read between the lines of the history documents / articles that we
> >> ship); that said:
> >>
hat we
ship); that said:
the main reasons for choosing lua for luatex has been that it is
relatively small, has no dependencies, doesn't need tons of libraries
to make it useful, is made for embeded usage, evolves in a proper
academic setting, has long-term dedicated (nice) developers, is not
part o
en the lines of the history documents / articles that we
> ship); that said:
>
> the main reasons for choosing lua for luatex has been that it is
> relatively small, has no dependencies, doesn't need tons of libraries
> to make it useful, is made for embeded usage, evolves in a prope
still kind of work in progress, the old (luatex)
interfaces were not that usefui / interesting anyway, and we can
do more now)
would
be interesting to hear about this from this community.
for sure i need more than an email to give a real answer (and some can
be read between the lines of the history documents / articles that we
ship); that said:
the main reasons for choosing lua for luatex has been that it is
relatively smal
and nline
numbers now
(local boxes are still kind of work in progress, the old (luatex)
interfaces were not that usefui / interesting anyway, and we can do more
now)
Hans
-
Hans Hagen |
\contextmark \stopTEXpage
\stopbuffer
\starttext
\contextmark\
\typesetbuffer[Buffer]
\stoptext
I get "MKIV LMTX" when it is processed with context --luatex. I want
the buffer to be processed as MkIV.
Does patching line 691 in buff-ini.lua
template = (jit and "--jit --e
\contextmark\
\typesetbuffer[Buffer]
\stoptext
I get "MKIV LMTX" when it is processed with context --luatex. I want the
buffer to be processed as MkIV.
Does patching line 691 in buff-ini.lua
template = (jit and "--jit --engine=luajittex" or
"--engine=luatex")
;MKIV LMTX" when it is processed with context --luatex. I want the
buffer to be processed as MkIV.
--
Rik
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : n
Maybe because a requires , for example, 0003.
See line 1506 in file
/context/tex/texmf-context/tex/context/base/mkiv/syst-aux.mkiv
Luis Montgomery
On the first run of MkIV (context --luatex) after updating my installation
> on Win11-x64, I get a complaint just after load
.)
Hans
On the first run of MkIV (context --luatex) after updating my
installation on Win11-x64, I get a complaint just after loading
.../base/mkiv/syst-mac-lua :
open source > level 1, order 11, name
'C:/ConTeXt_LMTX/tex/texmf-context/tex/context/base/mkiv/syst-aux.m
. It definitely is some low
level mechanism but you can for instance use if for high performance
efficient maginal notes and line numbering in controlled situations.
(There is some room fro optimization in the engien but I deal with
that later.)
Hans
On the first run of MkIV (context --luatex
to normalized lines and as such there is plenty to
play with. Others can be seen in the examples.
I might add some more control to both these 'injection' mechanism
because directly out of the (pdftex/omega/luatex) they are not that
useful (which is probably also why we don't use them
It works. I don't know why, but it works now.
Best wishes
Jörg
Am 18.10.21 um 17:27 schrieb Jörg Hofmann via ntg-context:
Am 04.10.21 um 15:33 schrieb Taco Hoekwater via ntg-context:
We are busy with this off-list.
If it is urgent:
luatex --luaonly ~/lmtx/tex/texmf-osx-64/bin
Am 04.10.21 um 15:33 schrieb Taco Hoekwater via ntg-context:
We are busy with this off-list.
If it is urgent:
luatex --luaonly ~/lmtx/tex/texmf-osx-64/bin/mtxrun.lua --generate
fixed it for me (you’ll need to adjust the path, of course)
Best wishes,
Taco
But not for me. :(
After I set
ack the file
>>>>
>>>> /usr/local/texlive/2021/texmf-dist/tex/generic/context/luatex/luatex-math.tex
>>>> and use LuaTeX directly, now using Version 1.13.2 (TeX Live 2021), but I
>>>> get this error:
>>>> (./luaotfload.sty
>>>> (
y ditch this setup in favour of using 'context' directly, so it is
>>>> not so important if there is no fix.
>>> I have no clue ..
>> I made this as experiment to make a texinfo file along with a manual
>> generating a PDF to display math properly, which the Info format can
On 10/13/2021 6:54 PM, Hans Åberg wrote:
On 13 Oct 2021, at 18:37, Hans Hagen wrote:
On 10/13/2021 6:01 PM, Hans Åberg via ntg-context wrote:
I was suggested a long ago to hack the file
/usr/local/texlive/2021/texmf-dist/tex/generic/context/luatex/luatex-math.tex
and use LuaTeX directly
this as experiment to make a texinfo file along with a manual generating
a PDF to display math properly, which the Info format cannot do.
I'm not familiar with texinfo but in the context distribution are some
luatex-* files that show how to load the generic context font loader (in
plain tex). One can
> On 13 Oct 2021, at 18:37, Hans Hagen wrote:
>
> On 10/13/2021 6:01 PM, Hans Åberg via ntg-context wrote:
>> I was suggested a long ago to hack the file
>>
>> /usr/local/texlive/2021/texmf-dist/tex/generic/context/luatex/luatex-math.tex
>> and use LuaTeX d
On 10/13/2021 6:01 PM, Hans Åberg via ntg-context wrote:
I was suggested a long ago to hack the file
/usr/local/texlive/2021/texmf-dist/tex/generic/context/luatex/luatex-math.tex
and use LuaTeX directly, now using Version 1.13.2 (TeX Live 2021), but I get
this error:
(./luaotfload.sty
(/usr
a long ago to hack the file
> /usr/local/texlive/2021/texmf-dist/tex/generic/context/luatex/luatex-math.tex
> and use LuaTeX directly, now using Version 1.13.2 (TeX Live 2021), but I get
> this error:
> (./luaotfload.sty
> (/usr/local/texlive/2021/texmf-dist/tex/latex/base/ltluatex
I was suggested a long ago to hack the file
/usr/local/texlive/2021/texmf-dist/tex/generic/context/luatex/luatex-math.tex
and use LuaTeX directly, now using Version 1.13.2 (TeX Live 2021), but I get
this error:
(./luaotfload.sty
(/usr/local/texlive/2021/texmf-dist/tex/latex/base/ltluatex.tex
sed engine: luatex version: 1.13, functionality
level: 7420, banner: this is luatex, version 1.13.0 (tex live 2021)
mkiv lua stats > used hash slots: 48846 of 65536 + 25
mkiv lua stats > lua properties: engine: lua 5.3, used memory: 212 MB,
ctx: 210 MB, max: unknown MB, hash chars:
Hi all,
I have a document here for one of my classes: xml processed via context,
some layers, some two column paragraphs, a bibliography, nothing out of
the ordinary. With mkiv, it compiles cleanly:
mkiv lua stats > used engine: luatex version: 1.13, functionality
level: 7420, ban
” directory (around August 20).
> Previously, the cache for LMTX still used files under luatex-cache, just
> like MKIV. But since that change, the “context -—generate” call no longer
> updates files in luatex-cache, only in luametatex-cache.
>
>
> That is not a big problem unless som
Hi,
Here is what I assume has happened:
Hans gave LMTX its own "luametatex-cache” directory (around August 20).
Previously, the cache for LMTX still used files under luatex-cache, just like
MKIV. But since that change, the “context -—generate” call no longer updates
files in luatex-
> Am 04.10.2021 um 15:33 schrieb Taco Hoekwater via ntg-context
> :
>
> We are busy with this off-list.
>
> If it is urgent:
>
> luatex --luaonly ~/lmtx/tex/texmf-osx-64/bin/mtxrun.lua --generate
>
> fixed it for me (you’ll need to adjust the path, of course
We are busy with this off-list.
If it is urgent:
luatex --luaonly ~/lmtx/tex/texmf-osx-64/bin/mtxrun.lua --generate
fixed it for me (you’ll need to adjust the path, of course)
Best wishes,
Taco
> On 4 Oct 2021, at 15:28, Marcus Vinicius Mesquita via ntg-context
> wrote:
>
>
ntext | current version: 2021.09.26 17:00
> >> mtx-context | main context file:
> /Users/hraban/lmtx/tex/texmf-context/tex/context/base/mkxl/context.mkxl
> >> mtx-context | current version: 2021.09.26 17:00
> >> $ context --version --luatex
> >
ntext/tex/context/base/mkiv/context.mkiv
>> mtx-context | current version: 2021.09.26 17:00
>> mtx-context | main context file:
>> /Users/hraban/lmtx/tex/texmf-context/tex/context/base/mkxl/context.mkxl
>> mtx-context | current version: 2021.09.26 17:00
>>
/texmf-context/tex/context/base/mkxl/context.mkxl
mtx-context | current version: 2021.09.26 17:00
$ context --version --luatex
mtx-context | redirect luametatex -> luatex: luatex --luaonly
"/Users/hraban/lmtx/tex/texmf-osx-64/bin/mtxrun.lua" --script mtx-context
--ver
| current version: 2021.09.26 17:00
$ context --version --luatex
mtx-context | redirect luametatex -> luatex: luatex --luaonly
"/Users/hraban/lmtx/tex/texmf-osx-64/bin/mtxrun.lua" --script mtx-context
--version --luatex --redirected
mtxrun | unknown script 'mtx-context.lua
On 10/1/2021 11:36 AM, Henri Menke via ntg-context wrote:
When I last looked at it about a year ago it was completely unusable
with the LuaTeX driver because position tracking primitives were
removed (\pdflastxpos, \pdflastypos) and box keywords had changed
(\hbox dir TRT). Some catcode
at will be needed to add a LMTX "driver" for TikZ? Porting pgfsys-
> luatex.def to pgfsys-luametatex.def? Or is something else also
> needed?
Yes, there would have to be a pgfsys-luametatex.def and some detection
code to switch the driver appropriately but that latter part is easy.
On 9/11/2021 1:19 PM, Hugh Fisher wrote:
On Fri, 10 Sept 2021 at 21:47, Hans Hagen wrote:
[ munch ]
in this area there is nothing in luametatex that luatex can't do
As in my earlier reply, I'm thinking about replacing Adobe Illustrator with
Metapost, and LuaMetaTEX seems to have better
On Fri, 10 Sept 2021 at 21:47, Hans Hagen wrote:
>
[ munch ]
>
> in this area there is nothing in luametatex that luatex can't do
As in my earlier reply, I'm thinking about replacing Adobe Illustrator with
Metapost, and LuaMetaTEX seems to have better integration?
>
> so, if y
(nil headers and footers)
the resulting pdf can then be converted to html with pdftotex or
something like that
so, basically, you just typeset the html
So (finally) my question: is LuaMetaTEX what I'm looking for?
in this area there is nothing in luametatex that luatex can't do
Yes
t; context("word 2")
>> > context.NC()
>> > context("word 3")
>> > context.NC()
>> > context.AR()
>> > end
>> > context.stoptabulate()
>> >
>> > \stopluacode
>> > \stoptext
>> >
>> &g
> context.AR()
> > end
> > context.stoptabulate()
> >
> > \stopluacode
> > \stoptext
> >
> > But it compiles with no problems with MKIV.
> >
> > context version: 2021.09.06 11:47
> >
> > How to avoid this with lmtx?
> In luatex there is
()
context("word 1")
context.NC()
context("word 2")
context.NC()
context("word 3")
context.NC()
context.AR()
end
context.stoptabulate()
\stopluacode
\stoptext
But it compiles with no problems with MKIV.
context version: 2021.09.06 11:47
How to avoid this
On 08/09/2021 19:08, Henning Hraban Ramm wrote:
I just checked on my Linux laptop with a new installation, and it worked
exactly like this.
Did you check with --luatex (i.e. MkIV)?
What’s your ConTeXt version? You left out this essential piece of information.
$ context --version
mtx
arcode[alternative=isbn, text=9783865419026, width=4cm]
> \barcode[alternative=qr code, text={https://wiki.contextgarden.net},
> width=3cm]
> \stoptext
>
I just checked on my Linux laptop with a new installation, and it worked
exactly like this.
Did you check wit
210903, format id: 593, compiler: clang
mkiv lua stats > tex properties: 740039 hash slots used of 2097152, 46321
control sequences, approximate memory usage: 29 MB
mkiv lua stats > lua properties: engine: lua 5.4, used memory: 52 MB, ctx: 49
MB, max: 49 MB, symbol mask: utf (τεχ)
>
> hm, that looks bad ... maybe not have a look after all ... i get the
> impression that many originally small programs get bloated by pulling in one
> lib that then pulls in more,
Exactly. The criticism by the GM maintainers probably *is* justified.
(When I installed IM, actually all of
On 9/5/2021 10:14 AM, Hans van der Meer via ntg-context wrote:
There is something I do not understand in the passing of parameters from
TeX to LuaTex.
This is my TeX definition:
\def\ListSort[#1]#2{\directlua{hvdm.listsort([===[#2]===],[===[#1]===])}}
tex haalt de {} rond #2 weg
Calling
And \ListSort[[abc]]{value} turns out to be worse: doesn't makes it into LuaTeX
at all.
dr. Hans van der Meer
> On 5 Sep 2021, at 10:14, Hans van der Meer via ntg-context
> wrote:
>
> There is something I do not understand in the passing of parameters from TeX
> to LuaTex.
&
There is something I do not understand in the passing of parameters from TeX to
LuaTex.
This is my TeX definition:
\def\ListSort[#1]#2{\directlua{hvdm.listsort([===[#2]===],[===[#1]===])}}
Calling \ListSort[sep={ + }]{} delivers the string 'sep={ + }' into LuaTeX as
the printout in the logfile
ng in
one lib that then pulls in more, even if nothing of that is used or
useful to the task (we sort of had that when luatex used xpdf from which
we only need the reading part but we could not really complain about
that because it has been so from the start but it triggered quite a bit
of updati
ime on marks (aka markings),
think of running headers and so.
I'm considering replacing the marking code by new code that I already
have one my machine. In mkiv we;ve always used a more powerful
alternative for the marks that than what luatex and friends provide but
in luametatex I
resolvers | formats | executing runner 'run luametatex format':
/home/fvleung/ConTeXt/tex/texmf-linux-64/bin/luametatex --jobname="trial"
--fmt=/home/fvleung/ConTeXt/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt
--lua=/home/fvleung/Con
?
And is that right with A{ij}
After compiling i get the following
Command Line: context.exe --synctex=-1 "Example1.tex"
Startup Folder: C:\Users\Administrator\Documents\My Documents
resolvers | formats | executing runner 'run luatex format':
C:/texlive/2020/bin/win32/luatex --jobname
TEXMFCACHE to contain
/var/opt/texlive first and then also an individual directory under $HOME.
When I run context under my personal account, it only uses the second.
I assume that's because I may not write under the first. There's a comment
in texmfcnf.lua about that.
Does it perhaps make no sense at
I want to configure the system so that everybody may use contents from
TEXMFSYSVAR, but optionally uses an additional personal directory.
I don't know if this makes sense in the case of luatex-cache, but had
thought so.
Thanks, Rainer
_
/perl5/bin:.:/Applications/Qt/current/clang_64/bin:/usr/X11/bin
dvipdfmx: /opt/local/bin/dvipdfmx
dvips: /opt/local/bin/dvips
fmtutil: /opt/local/bin/fmtutil
kpsewhich: /opt/local/bin/kpsewhich
luatex:/opt/local/bin/luatex
mktexpk: /opt/local/bin/mktexpk
pdf
On 8/25/2021 6:05 PM, Adam Reviczky via ntg-context wrote:
Hi,
I have been using the ansi and ansilog flags in the past and they work
fine with lmtx, but do not seem to make a difference with luatex/mkiv.
(There was a thread back in 2019:
https://mailman.ntg.nl/pipermail/ntg-context/2019
Hi,
I have been using the ansi and ansilog flags in the past and they work fine
with lmtx, but do not seem to make a difference with luatex/mkiv. (There
was a thread back in 2019:
https://mailman.ntg.nl/pipermail/ntg-context/2019/095666.html)
I am trying just a simple hello world:
\starttext
Hi again,
Many thanks to Hans and Hans and Henri.
The solution (going to low level) provided by Hans works fine.
Best
Thierry
Le Monday 23 Aug 2021 à 17:13:00 (+0200), Hans Hagen a écrit :
> On 8/23/2021 4:46 PM, Thierry Horsin via ntg-context wrote:
> > Hi everybody.
> >
> > I wonder how does
On 8/23/2021 5:24 PM, Hans van der Meer via ntg-context wrote:
I guess the underlying library calls are from Lua5.4? Then it is perhaps
useful to know that between 5.3 and 5.4 there is mentioned a new
implementation for math.random. Perhaps it changes the sequence of
random values generated?
> random values generated? Someone who knows?
https://tex.stackexchange.com/questions/468466/tikz-graphdrawing-differences-between-luatex-versions
Cheers, Henri
>
> dr. Hans van der Meer
>
>
> > On 23 Aug 2021, at 17:13, Hans Hagen via ntg-context <
> > ntg-context
I guess the underlying library calls are from Lua5.4? Then it is perhaps useful
to know that between 5.3 and 5.4 there is mentioned a new implementation for
math.random. Perhaps it changes the sequence of random values generated?
Someone who knows?
dr. Hans van der Meer
> On 23 Aug 2021, at
On Mon, 2021-08-23 at 16:46 +0200, Thierry Horsin via ntg-context
wrote:
> Hi everybody.
>
> I wonder how does math.random() work in context. I found that this
> subject was discussed more than ten years ago by Otared and Taco and
> Thomas. It is clear to me how to obtain new results upon
On 8/23/2021 4:46 PM, Thierry Horsin via ntg-context wrote:
Hi everybody.
I wonder how does math.random() work in context. I found that this subject was
discussed more than ten years ago by Otared and Taco and Thomas. It is clear to
me how to obtain new results upon typesetting the same file
Hi everybody.
I wonder how does math.random() work in context. I found that this subject was
discussed more than ten years ago by Otared and Taco and Thomas. It is clear to
me how to obtain new results upon typesetting the same file by changing the
value of math.randomseed (with os.time()).
font context agreed more often with uniscribe
than xetex, but in the end on ehas to make the font okay for all i guess).
When we started with opentype (luatex showed up in 2005) we took
uniscribe as reference so that is our benchmark. And lack of specs made
us figure out things stepwise. Now
gt; loading failed due to read error
(This run used luametatex, but the same issue occurs when using luatex)
The same font worked correctly with the ConTeXt version from 2021-05-20.
that's because since then we check for the cycle (otherwise artifacts)
it probably relates to these extra point
tx/tex/texmf-context/tex/context/base/mkxl/font-ctx.lmt:1336:
in function <...mtx/tex/texmf-context/tex/context/base/mkxl/font-ctx.lmt:1193>
(...tail calls...)
fonts > otf loading > loading failed due to read error
(This run used luametatex, but the same issu
Keywords:
template Author: Mickey Mouse Creator:LuaTeX 2.07
20200920 + ConTeXt MkIV 2020.09.20 23:02 Producer: LuaTeX-2.07
CreationDate: Tue Aug 10 09:16:30 2021 +08 ModDate:Tue Aug 10
09:16:30 2021 +08 Tagged: no UserProperties: no Suspects
You are correct Hans, I was using Mk IV luatex as the engine, though I
could use lmtx. It's just that in a production environment I need to be
absolutely sure things work (printers deadlines and that sort of thing!)
and I know that the MkIV luatex scene always works. But I'll give the
lmtx
with startpostponingnotes
I assume that you use(d) mkiv/luatex and not lmtx/luametatex.
Footnotes are in tex speak 'inserts' and at some point they are filtered
and added to the datastructure (list) that is taken into account when
breaking a page.
When tex was written, the main application was books like
lias \ifexpression :
\ifnumexpression (2 * 10) + (3 << 4) > (4 & 5) \relax yes \else no \fi
\stoptext
Performance wise it is comparable to \dimexpr and \numexpr (these are a
bit faster in luametatex than in luatex), the final \relax is mandate
(so no lookahead side effects), and these don't su
a problem
the command line program qpdf is one of the best programs to check (when
luigi sand i were checking luatex pdf issues we used qpdf and mupdf mostly)
Now to the different mechanisms:
1) Sound objects
- First appeared in PDF 1.2 (1996), but had since been deprecated (PDF
1.5
oindent
\placerenderingwindow[myrenderingwindow][myvideo3]
\stoptext
All three file source types are demonstrated. Any "video.mp4" in the
directory you compile in will do. (Works as expected in Okular on
Linux.)
This was a dump of knowledge that I gained from writing my
before LMTX, thus it is not a regression.
% !TEX TS-program = ConTeXt (LuaTeX LMTX2021)
% !TEX encoding = UTF-8 Unicode
\starttext
\setupinitial[color=red]
\start
\setupinitial[n=2,m=1]
\placeinitial\input ward
\stop
\start
\setupinitial[style=\tf,n=2,m=1]
\placeinitial\input ward
\stop
{*lmtx}{lmtx}
I always get „mkiv“.
I’ve tried
- pre LMTX context
- LMTX --luatex
- LMTX (2021.07.23)
What is the recommended way to detect LMTX?
There is no mode value for LMTX, only MkIV is set. To check for LMTX
you have to use \ifcase\contextlmtxmode but an additional for lmtx
would be useful
301 - 400 of 10522 matches
Mail list logo
