;>> https://tex.stackexchange.com/questions/596610/how-to-use-luatex-with-large-unicode-codepoint
>>>>
>>>> <https://tex.stackexchange.com/questions/596610/how-to-use-luatex-with-large-unicode-codepoint>,
>>>> I tried to replicate it in ConTeX
On Tue, May 11, 2021 at 3:41 PM Taco Hoekwater wrote:
>
>
> > On 11 May 2021, at 15:16, Hans Hagen wrote:
> >
> > On 5/11/2021 2:08 PM, Jairo A. del Rio wrote:
> >> Hi, list! Following this thread:
> https://tex.stackexchange.com/questions/596610/how-to-use
On 5/11/2021 3:40 PM, Taco Hoekwater wrote:
On 11 May 2021, at 15:16, Hans Hagen wrote:
On 5/11/2021 2:08 PM, Jairo A. del Rio wrote:
Hi, list! Following this thread:
https://tex.stackexchange.com/questions/596610/how-to-use-luatex-with-large-unicode-codepoint
<ht
> On 11 May 2021, at 15:16, Hans Hagen wrote:
>
> On 5/11/2021 2:08 PM, Jairo A. del Rio wrote:
>> Hi, list! Following this thread:
>> https://tex.stackexchange.com/questions/596610/how-to-use-luatex-with-large-unicode-codepoint
>>
>> <https://tex.st
On 5/11/2021 2:08 PM, Jairo A. del Rio wrote:
Hi, list! Following this thread:
https://tex.stackexchange.com/questions/596610/how-to-use-luatex-with-large-unicode-codepoint
<https://tex.stackexchange.com/questions/596610/how-to-use-luatex-with-large-unicode-codepoint>,
I tried to rep
Hi, list! Following this thread:
https://tex.stackexchange.com/questions/596610/how-to-use-luatex-with-large-unicode-codepoint,
I tried to replicate it in ConTeXt. Both LMTX and LMTX fail to display the
right symbol and, as it's discussed in the linked page, there's an offset
by 14
; initializing number mode 'scaled'
> input stack overflow
> mtx-context | fatal error: return code: 256
>
> Commenting out "StartPage" and "StopPage" compiles.
>
> mtx-context | current version: 2021.05.09 17:14
&
and "StopPage" compiles.
mtx-context | current version: 2021.05.09 17:14
This is LuaTeX, Version 1.14.0
Development id: 7438
Adam
On Sun, May 9, 2021 at 9:57 PM Adam Reviczky wrote:
> Hi,
>
> With the latest luatex change from
> https://github.com/TeX-Live/luatex/commit/15
Hi,
With the latest luatex change from
https://github.com/TeX-Live/luatex/commit/1566b63b338abbe38ed839fac9f2022ebbfa7d59
(and MKIV 2021-05-09 17:14:00) I get an input stack overflow:
simpleslides> loading style Boxed
system > command '\NormalHeight' is already defined
Hi,
With luametatex becoming more mature, it's time to get rid of some old
code. For instance, we have lmt files that assume 5.4, but regular lua
files should work for luajittex (5.2) and luatex (5.3). Most noticable
are the lack of bitwise operators and integer devision in luajittex
On 5/4/2021 4:58 PM, Pablo Rodriguez wrote:
On 5/4/21 9:51 AM, denis.ma...@ub.unibe.ch wrote:
Hi Pablo
[...]
Confirmed here.
I've also tried with --luatex, but that doesn't find the font at all.
(Do I have to update the font database for luatex separately?)
Many thanks for the confirmation
On 5/4/21 9:51 AM, denis.ma...@ub.unibe.ch wrote:
> Hi Pablo
> [...]
> Confirmed here.
>
> I've also tried with --luatex, but that doesn't find the font at all.
> (Do I have to update the font database for luatex separately?)
Many thanks for the confirmation, Denis,
--luat
\bi}
> {\startpar\recursestring\input zapf\stoppar}
> \stoptext
>
> Could anyone confirm this? I wonder whether the typeface itself is missing
> something.
Confirmed here.
I've also tried with --luatex, but that doesn't find the font at all. (
d perfectly fine
> each time I tested.
>
> > Using the https://live.contextgarden.net/ with (LuaTeX 2.06 20200630 +
> > ConTeXt MkIV 2020.06.30 17:30) looks good, but evince does not display
> > the field.
>
> Evince never displays the signature field, only when signed.
>
>
’t working, you mean that the output PDF document
from fields-007.tex cannot be signed with Acrobat DC, don’t you?
Sorry for asking the obvious question, but this worked perfectly fine
each time I tested.
> Using the https://live.contextgarden.net/ with (LuaTeX 2.06 20200630 +
> ConTeXt
tps://live.contextgarden.net/ with (LuaTeX 2.06 20200630 +
ConTeXt MkIV 2020.06.30 17:30) looks good, but evince does not display the
field.
Adam
On Fri, Apr 23, 2021 at 8:52 PM Leonard Janis Robert König
wrote:
> Hello,
>
> I currently try to build a document with AcroForms, e.g., the exa
quot;,
MPINPUTS= ".;$TEXMF/metapost/{context,base,}//",
-- In the next variable the inputs path will go away.
TEXMFSCRIPTS=
".;$TEXMF/scripts/context/{lua,ruby,python,perl}//;$TEXINPUTS",
PERLINPUTS = "
On Fri, 30 Apr 2021 at 20:53, Nicola wrote:
>
> This installs and configures repos for Alpine Linux 3.12. Then,
> I install TeX Live as follows:
>
> apk add texlive-full texlive-xetex texlive-luatex texlive-dev
> apk add ghostscript ghostscript-fonts ghostscript
a /etc/apk/repositories
apk update
This installs and configures repos for Alpine Linux 3.12. Then,
I install TeX Live as follows:
apk add texlive-full texlive-xetex texlive-luatex texlive-dev
apk add ghostscript ghostscript-fonts ghostscript-dev
apk add graphicsmagick graphics
\exhyphenchar, in luametatex we can tag any char
as such
in traditional tex th ehyphenation, ligature building and kerning wre
integrated, so handling - -- --- -- is kind of complex
in luatex these stages are split but there's still messy logic wrt
successive hyphens
al character for em- and en-dashes
than three or two hyphens.
It took me a while since I accidentally discovered a document with a
wrong line break between a real em-dash and a point followed by a
footnote number.
So my question is what \hccode stands for?
From luametatex.pdf in the distribution,
On Sat, Apr 24, 2021 at 1:33 AM Sylvain Hubert
wrote:
> You're right, I just checked the symbols of luatex and they contain all
> the APIs of lua 5.3.
> So I guess the problem is specific to luametatex and the latest context.
>
> > but in any case you should compile against
You're right, I just checked the symbols of luatex and they contain all the
APIs of lua 5.3.
So I guess the problem is specific to luametatex and the latest context.
> but in any case you should compile against the luatex headers, not the
stock lua 5.3.6.
Does luatex have dedicated head
ontext/tex/context/base/mkiv/l-package.lua:348: error
> loading module 'lpeglabel' from file './lpeglabel.so':
> ./lpeglabel.so: undefined symbol: lua_gettop
>
>
hm, lua_gettop is a global symbol in latest luatex, it's not undefined...
>
> nor does LuaTeX:
> $ luatex -luaonly te
nor does LuaTeX:
$ luatex -luaonly testlabel.lua
error loading module 'lpeglabel' from file './lpeglabel.so':
./lpeglabel.so: undefined symbol: lua_getiuservalue
It seems that lua_gettop and others are optimized out from the `context`
binary, while lua_getiuservalue and others are missing from `lua
Hub is (according to
pdfinfo):
> Creator: LuaTeX 1.10 7138 + ConTeXt MkIV 2019.08.20 17:20
> Producer: macOS Version 10.14.6 (Build 18G5033) Quartz
PDFContext
I also remebered another time were I toyed around with it and indeed
that PDF also had broken form field children:
> Creator:
X fmt: 2021.4.20 int: english/english
>
> And even with --luatex
> ConTeXt ver: 2021.04.18 18:12 MKIV fmt: 2021.4.21 int: english/english
>
> Always the result as attached.
>
> Denis
>
>
> > -Ursprüngliche Nachricht-
> > Von: ntg-context Im Au
Hi
What's the exact issue?
I get the same results on my TeXLive version and on the latext lmtx:
ConTeXt ver: 2020.01.26 18:34 MKIV beta fmt: 2020.10.2 int: english/english
ConTeXt ver: 2021.04.18 18:12 LMTX fmt: 2021.4.20 int: english/english
And even with --luatex
ConTeXt ver
Hi,
I'm checking out some old experiments (either use or drop 'm) and here's
one that made it into lmtx in the end (not much code). We have a bunch
of arrays in the engine: \uccode, \lccode, \sfcode, \efcode, catcodes
etc and while traditional tex just has 256 slot arrays in luatex
$ sudo su -
$ rm -rf /opt/context
$ mkdir -p /opt/context
$ cd /opt/context
$ wget http://lmtx.pragma-ade.nl/install-lmtx/context-linux-64.zip
$ unzip *zip
$ export TEXMFCACHE=/tmp
$ sh install.sh
$ exit
$ cat test.tex
\starttext
Test
\stoptext
$ export TEXMFCACHE=/tmp
$ sudo rm -rf /tmp/luatex
zip>
$ unzip *zip
$ sh install.sh
$ exit
$ cat test.tex
\starttext
Test
\stoptext
$ export TEXMFCACHE=/tmp
$ rm -rf $TEXMFCACHE/luatex-cache
$ /opt/context/tex/texmf-linux-64/bin/mtxrun --autogenerate --script
mtx-context --autopdf test.tex
...
resolvers | resolving | remembered fil
$ rm -rf $TEXMFCACHE/luatex-cache
$ /opt/context/tex/texmf-linux-64/bin/mtxrun --autogenerate --script
mtx-context --autopdf test.tex
...
resolvers | resolving | remembered file 'mtx-context.lua'
resolvers | resolving | remembered file 'mtx-contexts.lua'
resolvers | resolving
ble
new stuff there)
the type-imp-loc file for users who want to test / overload fonts or
whatever (not in distribution)
These are not in distribution at all, naturally missing in
/tex/texmf-cache/luatex-cache/context/.../trees/*.lua
resolvers > resolving > file 'lm.lfg'
olving > file './type-imp-loc.mkiv' is not readable
>
resolvers > resolving > file 'type-imp-loc.tex' is not readable
resolvers > resolving > file './type-imp-loc.tex' is not readable
resolvers > resolving > file 'type-imp-loc.tex' is not readable
These are
On 4/6/2021 8:59 PM, Thangalin wrote:
Thanks Aditya.
What do you think of changing the default luatex-cache directory to the
system's temporary directory? Consider:
* The $HOME directory is sacrosanct (4784 people agree:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1575053
Perfect, thank you.
Will be Wikified.
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage :
On Tue, 6 Apr 2021, Thangalin wrote:
> Thanks Aditya.
>
> What do you think of changing the default luatex-cache directory to the
> system's temporary directory? Consider:
>
>- The $HOME directory is sacrosanct (4784 people agree:
>https://bugs.launchpad.net/ubun
Thanks Aditya.
What do you think of changing the default luatex-cache directory to the
system's temporary directory? Consider:
- The $HOME directory is sacrosanct (4784 people agree:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1575053)
- The temp directory is cleared on Linux
On Mon, 5 Apr 2021, Thangalin wrote:
> Peter Münster once asked:
>
> > What should I do please, to prevent ConTeXt from creating
> $HOME/luatex-cache?
>
> I'd like to do the same:
>
> $ cd $HOME
> $ ls luatex-cache
> ls: cannot access 'luatex-cache': No s
Peter Münster once asked:
> What should I do please, to prevent ConTeXt from creating
$HOME/luatex-cache?
I'd like to do the same:
$ cd $HOME
$ ls luatex-cache
ls: cannot access 'luatex-cache': No such file or directory
$ context test.tex
$ ls luatex-cache/
context
$ rm -rf luatex-ca
==
LuaTeX 1.13.1 2021-04-02
==
Fixed an unwanted space in btex etex in metapost, introduced
after a patch for troff.
--
luigi
==
LuaTeX 1.13.0 2021-03-12
==
This is the release for TeX live 2021.
Callback for nesting level used in tracingmacros.
It is is a variant of \tracingstacklevels
by Petr Olsak
Ah, I've now realized that the \blockligatures needs to be activated as a font
feature... So forget about this point.
But, it still looks like ligature prevention with \replaceword is not working
with lmtx, but it works with --luatex
that this year all the lua and mp files also will be
independent so that at some point we have a more or less frozen MKIV
that uses luatex (which doesn't change fundamentally apart from fixes so
we don't need to adapt code to it i.e. MKIV should keep working just
like MKII does with pdftex; updates
Forgot to mention that my program is LuaTeX 2.08 20210220 + ConTeXt MkIV
2021.02.23 17:47
Also I like \setupbacked for what it does (export html/xml/css), I just
wasn't aware that it makes bibliography render strangely when outputting a
pdf.
On Sun, 28 Feb 2021 at 11:42, a badin wrote:
> D
On 2/26/2021 6:58 PM, Wolfgang Schuster wrote:
Hans Hagen schrieb am 26.02.2021 um 18:36:
On 2/26/2021 6:01 PM, Lukas/ConTeXt wrote:
Hello,
after I renewed ConTeXt MkIV, I started to get the following warning:
"
...
luatex warning > nodes: unable to store reference from lu
Hans Hagen schrieb am 26.02.2021 um 18:36:
On 2/26/2021 6:01 PM, Lukas/ConTeXt wrote:
Hello,
after I renewed ConTeXt MkIV, I started to get the following warning:
"
...
luatex warning > nodes: unable to store reference from lua in tex
...
(repeated more times)
"
This happe
On 2/26/2021 6:01 PM, Lukas/ConTeXt wrote:
Hello,
after I renewed ConTeXt MkIV, I started to get the following warning:
"
...
luatex warning > nodes: unable to store reference from lua in tex
...
(repeated more times)
"
This happens when I try to typeset a looo...ong tab
Hello,
after I renewed ConTeXt MkIV, I started to get the following warning:
"
...
luatex warning > nodes: unable to store reference from lua in tex
...
(repeated more times)
"
This happens when I try to typeset a looo...ong table (by
\start/\stop-tabulate) over several pages.
It
ple runs could take a while
> (many minutes, iir some 15 depending on how it was run). That was no fun.
>
> In mkiv with luatex and the built in mp library this dramatically went down
> to 18.1 seconds for one run and 14.2 seconds for luajittex, for 428
> pages.
>
> This not
could take
a while (many minutes, iir some 15 depending on how it was run). That
was no fun.
In mkiv with luatex and the built in mp library this dramatically went
down to 18.1 seconds for one run and 14.2 seconds for luajittex, for 428
pages.
This not bad considering that a lots of features
On 2/17/2021 7:23 PM, Adam Reviczky wrote:
Hi,
I am getting the following error with luatex/mkiv with today's latest:
hm, looks like some split / file mixup .. i'll upload a new zip tomorrow
Hans
Hi,
I am getting the following error with luatex/mkiv with today's latest:
context --make
loading : ConTeXt Token Support / Initialization
/usr/share/texmf/tex/context/base/mkxl/toks-ini.lmt:21: attempt to call a
nil value (field 'getcommandvalues')
stack traceback:
/usr/share/texmf/tex
nistrator
> resolvers | formats | executing runner 'run luatex format':
> C:/texlive/2020/bin/win32/luatex --jobname="Math 2"
> --fmt=C:/texlive/2020/texmf-var/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luatex/cont-en.fmt
&g
tup Folder: C:\Users\Administrator
resolvers | formats | executing runner 'run luatex format':
C:/texlive/2020/bin/win32/luatex --jobname="Math 2"
--fmt=C:/texlive/2020/texmf-var/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luatex/cont-en.fmt
--lua=C:/texlive/2
and linux. Context --luatex
worked fine.
A minimal file based on the wiki examples produced the same error on
\completelistoftests:
\definesynonyms[test][tests][\infull]
\setupsynonyms[test][criterium=all]
\test{ITU}{International Telecommunication Union}
\test{MID}{Maritime Identification Digit
Hello all,
I've used ConTeXt MkIV for years to make technical reports. For a new
computer I looked for updates of the software and discovered LMTX. I ran
it on my latest report and found an error on
\completelistofabbreviations, both on win-64 and linux. Context --luatex
worked fine
w method (more lmtx-ish)
(actually with mkii in pdftex we need .3 seconds, xetex freezes with
100K but needs 0.53 for 10K, luatex needs 0.18)
but I'm sure you don't care much about that so I just implements a
variant with warning which takes .19 seconds per 100K so it's a nice
compromise. (Prob
, it should disappear,
that’s the part that is not working.
My idea was to put the text into a buffer and ignore it, that didn’t work.
% !TEX TS-program = ConTeXt (LuaTeX 1.0.9)
% !TEX encoding = UTF-8 Unicode
%\enablemode[change]
% Paragraph removed
\definestartstop[ChangePR][
before={\doifmodeelse
that is not working.
My idea was to put the text into a buffer and ignore it, that didn’t work.
% !TEX TS-program = ConTeXt (LuaTeX 1.0.9)
% !TEX encoding = UTF-8 Unicode
%\enablemode[change]
% Paragraph removed
\definestartstop[ChangePR][
before={\doifmodeelse{change}
{\startsidebar[rulecolor=red
,
>>> author = {Angerer, Philipp and Haghverdi, Laleh and B{\"{u}}ttner, Maren
>>> and Theis, Fabian J and Marr, Carsten and Buettner, Florian},
>>> doi = {10.1093/bioinformatics/btv715},
>>> issn = {14602059},
>>> journal = {Bioinformatics},
&g
xt/base/mkiv/mtx-context-combine.tex
resolvers | formats | executing runner 'run luametatex format':
/opt/context/tex/texmf-linux-64/bin/luametatex --jobname="mtx-context-combine"
--fmt=/opt/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametate
en to
> a buffer of configurable name, and that (with preamble setup) will get run
> through LaTeX. I read pgf had some restrictions in plain TeX mode, but perhaps
> we can also use LuaTeX in plain mode to avoid the LaTeX dependency.
>
> Best, Hraban
> __
ill get written
> >> to a buffer of configurable name, and that (with preamble setup) will get
> >> run through LaTeX. I read pgf had some restrictions in plain TeX mode, but
> >> perhaps we can also use LuaTeX in plain mode to avoid the LaTeX dependency.
> > In the following
setup) will get
>> run through LaTeX. I read pgf had some restrictions in plain TeX mode, but
>> perhaps we can also use LuaTeX in plain mode to avoid the LaTeX dependency.
> In the following case the buffer only gets typeset when it changes:
Thank you (and Henri)! But we’d need to in
a
buffer of configurable name, and that (with preamble setup) will get run
through LaTeX. I read pgf had some restrictions in plain TeX mode, but perhaps
we can also use LuaTeX in plain mode to avoid the LaTeX dependency.
In the following case the buffer only gets typeset when it changes:
\starttext
\start
) will get run
through LaTeX. I read pgf had some restrictions in plain TeX mode, but perhaps
we can also use LuaTeX in plain mode to avoid the LaTeX dependency.
Best, Hraban
___
If your question is of interest to othe
Pagella font (I do not know if the same issue
> >> occurs with other fonts as I haven't tested them).
> >>
> >> If I compile with LMTX, the spacing between letters becomes very small
> >> so that when I type "|f|", for example, the second "|"
with LMTX, the spacing between letters becomes very small
so that when I type "|f|", for example, the second "|" intersects the
f and looks rather ugly. However, compiling with the --luatex switch
fixes these issues and the math looks nice again.
Can anybody else replicate this iss
very small
so that when I type "|f|", for example, the second "|" intersects the f
and looks rather ugly. However, compiling with the --luatex switch fixes
these issues and the math looks nice again.
Can anybody else replicate this issue, and does anybody know
aven't tested them).If I compile with LMTX, the spacing between letters becomes very
small so that when I type "|f|", for example, the second "|"
intersects the f and looks rather ugly. However, compiling with
the --luatex switch fixes these issues and the math
ot;|f|", for example, the second "|" intersects the f
and looks rather ugly. However, compiling with the --luatex switch fixes
these issues and the math looks nice again.
Can anybody else replicate this issue, and does anybody know why it is
happening?
This the code I used to te
e marker at the closing quotation mark.
\setupdelimitedtext... does that, but kills the indent. Without the setup, I
get the indent, but the footnote marker moves to the next line.
And there’s a problem with MkIV (--luatex): TeX stops with **, after entering
\end, I get the PDF, so something’s unclosed.
it seems it's there.
depends on what you consider (non) hdpi ... the positioning of glyphs
depends on font scale, rounding of stems and such (hints in fonts but
these get less relevant with high res displays), caching, inter glyph
corrections (that pdftex/luatex/...) put in the text stream
well? Because it seems it's there.
>
> depends on what you consider (non) hdpi ... the positioning of glyphs
> depends on font scale, rounding of stems and such (hints in fonts but
> these get less relevant with high res displays), caching, inter glyph
> corrections (that pdftex/luatex/...)
ion of this software is covered by the
terms
of the GNU General Public License, version 2 or (at your option) any later
version. For more information about these matters, see the file named
COPYING
and the LuaTeX source.
Functionality : level 20210107
Support : cont...@ntg.nl
Copyright : The
Hello,
I compared latest ConTeXt standalone (LuaTeX 2.08) against TeX Live 2020
(LuaTeX 1.12). The produced PDFs are:
https://miletic.net/lipsum-112.pdf
https://miletic.net/lipsum-208.pdf
Viewing them with Evince (and I assume Adobe Reader, I don't have it at
hand to test) shows only minor
of glyphs
depends on font scale, rounding of stems and such (hints in fonts but
these get less relevant with high res displays), caching, inter glyph
corrections (that pdftex/luatex/...) put in the text stream to resync
within certain tolerances, etc ... (often a print is a better reference
On 1/7/2021 10:10 PM, Vedran Miletić wrote:
Hello,
I compared latest ConTeXt standalone (LuaTeX 2.08) against TeX Live 2020
(LuaTeX 1.12). The produced PDFs are:
https://miletic.net/lipsum-112.pdf
https://miletic.net/lipsum-208.pdf
Viewing them with Evince (and I assume Adobe Reader, I
the meantime we got etex extensions, which
adds a few more, and then pdftex ades some, as well as omega and after
that of course luatex. In luametatex we dropped some, and added others,
so there we currently have 770 primitives. The increase of number is
partly due to the 166 extra math related
Patoline is partly LaTeX based, Speedata Publisher uses LuaTeX, and I know
> of troff and XSL/FO.
The interesting thing here is that Patoline and SILE use some TeX-like syntax,
but the underlying engine is not based on TeX at all. With Speeddata Publi
Also thank you!
Patoline is partly LaTeX based, Speedata Publisher uses LuaTeX, and I know of
troff and XSL/FO.
I’d be interested to hear about experiences with other code based typesetting
engines (besides ConTeXt and LaTeX), since I used LinoSetting and 3B2 in
earlier days.
A healthy
{Destiny: Diffusion maps for large-scale single-cell data in R}},
>> url = {
>> http://bioinformatics.oxfordjournals.org/lookup/doi/10.1093/bioinformatics/btv715
>> files/103/Angerer et al. - 2016 - destiny diffusion maps for large-scale
>> single-cel.pdf},
>> volume
for your work on digestif and improving ConTeX support!
> Digestif plugs into any editor that support the Language Server
> Protocol
I'd probably like to use it with SublimeText which I favour over VScode...
> Another nice thing is that Digestif is a Lua program, and can run on
> t
anything of help in this direction currently, right?
Another nice thing is that Digestif is a Lua program, and can run on
the LuaTeX interpreter with no extra dependencies. On the other hand, I
didn't get the change to test it on Windows or editors other than
Emacs, although both things should work
have small examples
right now, but I want to point out that there are two more areas where
current lmtx has serious problems that luatex doesn't have:
Must have been some side effect of some of the font stuff as iI didn't
really touch the alignment code.
1. I have a bibliography
to point out that there are two more areas where
current lmtx has serious problems that luatex doesn't have:
1. I have a bibliography that is structured in sections. lmtx does not
respect the scope of these sections, but prints the entire
bibliographical list at the first occurrence
!`.
There are probably more silent TeX errors that I currently don't have in mind.
Are these things possible in LuaTeX right now or could they be made possible in
the future?
Kind regards,
Henri
___
If your question
Are these things possible in LuaTeX right now or could they be made possible in
the future?
all is possile but this will not happen ... enabling callbacks like that
would make luatex unuseable slow (which is probably not what you want
because pgf is already kind of slow) (even checking for the callback
mkiv and generic in node-gcm.lua, but this file is not included in the
> > packaged generic fontloader. Therefore the current luatex-fonts-merged.lua
> > breaks with "trying to call a nil value (upvalue flush_components)".
> >
> > Could you please add a definiti
the current luatex-fonts-merged.lua
breaks with "trying to call a nil value (upvalue flush_components)".
Could you please add a definition for nuts.flush_components in the
generic version?
I'll add it to (the rest in):
luatex-basics-nod.lua
(it's a dummy funct
Hi,
in font-ots.lua (which becomes part of the generic fontloader)
nuts.flush_components is used, while it seems to be defined for
mkiv and generic in node-gcm.lua, but this file is not included in the
packaged generic fontloader. Therefore the current luatex-fonts-merged.lua
breaks with "t
maps for large-scale
> single-cel.pdf},
> volume = {32},
> year = {2016}
> }
>
> This log occurs:
>
> ❯ context test.lmtx
> resolvers | formats | executing runner 'run luametatex format':
> ~/Library/ConTeXt/tex/texmf-osx-64/bin/luametatex --jobname="
olume = {32},
year = {2016}
}
This log occurs:
❯ context test.lmtx
resolvers | formats | executing runner 'run luametatex format':
~/Library/ConTeXt/tex/texmf-osx-64/bin/luametatex --jobname="test"
--fmt=~/Library/ConTeXt/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0d
year = {2016}
}
This log occurs:
❯ context test.lmtx
resolvers | formats | executing runner 'run luametatex format':
~/Library/ConTeXt/tex/texmf-osx-64/bin/luametatex --jobname="test"
--fmt=~/Library/ConTeXt/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/for
main computer.
I just want to know when I should update the Linux version.
You can just try it as parallel installation. Mojca's farm also breeds
the 32 bit binaries. Because luametatex is leaner on memory and less
demanding wrt the cpu, if luatex works, luametatex should also work.
Hans
able in some articles.
I tried Wolfgang's amendment (see his posting) just now using MacTeX 2020, and
the plain LuaTeX without Harfbuzz worked well too.
Regards,
Robert
___
If your question is of interest to others as
Robert Zydenbos schrieb am 19.12.2020 um 02:47:
Dear all,
Recently I read about the use of Harfbuzz-enhanced LuaTeX with LaTeX for
writing Arabic. Following that example, I wrote a minimal test text that worked
excellently for Kannada script as well:
-
\documentclass{article}
\usepackage
:24 p. m., Robert Zydenbos <
cont...@zydenbos.net> escribió:
> Dear all,
>
> Recently I read about the use of Harfbuzz-enhanced LuaTeX with LaTeX for
> writing Arabic. Following that example, I wrote a minimal test text that
> worked excellently for Kannada script as well:
>
Dear all,
Recently I read about the use of Harfbuzz-enhanced LuaTeX with LaTeX for
writing Arabic. Following that example, I wrote a minimal test text that worked
excellently for Kannada script as well:
-
\documentclass{article}
\usepackage{fontspec}
\setmainfont{Kedage}[RawFeature={mode
501 - 600 of 10528 matches
Mail list logo
