e:
> > Hi,
> >
> > I'm in the process of updating to TeXlive 2023 after a long time of
> > light use with 2018. One issue I'm now having is an error when I try to
> > use Neo Euler as my math font.
> >
> > \definefontfamily[mypalatinoeuler][rm][TeX Gyre Page
On 3/31/2023 10:08 PM, Carlos via ntg-context wrote:
sure, why should it, you want lucida so better quit with an error than
kicking in some font; actually cmr math fonts have been obsoleted for way
over a decade by latin modern math fonts in 32 bit font engines
Font loading and processing
On 3/31/2023 9:58 PM, Rory Molinari via ntg-context wrote:
Hi,
I'm in the process of updating to TeXlive 2023 after a long time of
light use with 2018. One issue I'm now having is an error when I try to
use Neo Euler as my math font.
\definefontfamily[mypalatinoeuler][rm][TeX Gyre Pagella
as_place_number
> > \strc_formulas_flush_number \dostarttagged \t!formulacontent \empty
> > \dotagregisterformula \c_strc_formulas_n \csname \e!stop \formulaparameter
> > \c!alternative \v!formula \endcsname
>
> dunno, that's numbering, not math
>
> > Okay. So I tr
Hi,
I'm in the process of updating to TeXlive 2023 after a long time of light
use with 2018. One issue I'm now having is an error when I try to use Neo
Euler as my math font.
\definefontfamily[mypalatinoeuler][rm][TeX Gyre Pagella]
\definefontfamily[mypalatinoeuler][mm][Neo Euler
family. For example, plain TeX doesn't allow \it or \sl in
subscripts. Proceed, and I'll try to forget that I needed that character.»
There's not even a fallback to cmr or any other font.
sure, why should it, you want lucida so better quit with an error than
kicking in some font; actually cmr mat
have been set. This
is
normally done by loading special math fonts into the math family slots. Your
font
set is lacking at least the parameter mentioned earlier.»
Sorry, but sorry doesn't cut it here.
I guess it must have been referring to \strc_formulas_place_number
\strc_formulas_flush_number
On 3/30/2023 8:52 PM, Xavier B. via ntg-context wrote:
Hi,
I use artix linux (a fork of arch with systemd alternative init systems).
During the texlive package, I get this error:
return {
["filename"]="/usr/share/texmf-dist/tex/generic/pgf/basiclayer/pgfcorepoints.code.tex&qu
with the --luatex switch, I get this error
message:
tex error > tex error on line 101 in file
/mnt/shared/lmtx/tex/texmf-context/tex/context/base/mkiv/meta-imp-dum.mkiv: ! Undefined control sequence
l.101 \newinteger
\c_grph_replacement_n
So, I'm a bit stymied ri
while with my suggested fix I get:
one “Authǒr—One”
two “Authǒr—Two”
I'm using a CLD document to convert a bunch of old .bib and .tex files into
Lua tables (which I'll then convert into XML). I can't modify any of the
input files, so I'll need to somehow deal w
If I run the minimal context distro
[https://wiki.contextgarden.net/Installation], I get this:
$ context a.tex
resolvers | formats | executing runner 'run luametatex format':
/home/xan/bin/context-minimal/tex/texmf-linux-64/bin/luametatex
--jobname="./a.tex"
--fmt=/ho
Hi,
I use artix linux (a fork of arch with systemd alternative init systems).
During the texlive package, I get this error:
return {
["filename"]="/usr/share/texmf-dist/tex/generic/pgf/basiclayer/pgfcorepoints.code.tex",
["lastcontext"]="\n \n \\inacces
Hi all,
I wanted to use a rightbrace as background for a table, as defined in
meta-imp-fen.mkiv. Unfortunately, I can't get it to work, for 2 reasons:
1. meta-imp-fen doesn't appear to be ported to mkxl.
2. When I try to compile with the --luatex switch, I get this error message:
tex error
Removing the following lines
elseif not find(str,"\\",1,true) then
return str
from the definition of "characters.tex.toutf" in "char-tex.{lmt,lua}"
fixes this issue for me.
it is more side effect of removing the (declared obsolete some years
ago) ``
return str
from the definition of "characters.tex.toutf" in "char-tex.{lmt,lua}"
fixes this issue for me.
Thanks,
-- Max
___
If your question is of interest to others as well, please ad
On 3/28/2023 7:05 PM, Carlos via ntg-context wrote:
On Mon, Mar 27, 2023 at 03:43:47PM +0200, Hans Hagen via ntg-context wrote:
On 3/27/2023 3:31 PM, Carlos via ntg-context wrote:
mkiv lua stats > loaded fonts: 4 files: latinmodern-math.otf,
lmroman10-regular.otf, lucidabrightregular.ttf,
hell-initialize))
;; For configuring context
(add-to-list 'auto-mode-alist '("\\.tex\\'" . context-mode))
(eval-after-load 'tex '(add-to-list 'TeX-command-list
'("LuaMetaTeX"
"mtxrun --autogenerate --script context %t" TeX-run-command nil
(context-mode) :help &q
On Mon, Mar 27, 2023 at 03:43:47PM +0200, Hans Hagen via ntg-context wrote:
> On 3/27/2023 3:31 PM, Carlos via ntg-context wrote:
>
> > mkiv lua stats > loaded fonts: 4 files: latinmodern-math.otf,
> > lmroman10-regular.otf, lucidabrightregular.ttf, lucidasansregular.ttf
>
> i admit never
has to do is indicate the correct
path to ConText in the setup for this program, depending
on your OS and where you have installed it, e.g.
home/yourname/bin/context/tex/texmf-linux-64/bin if you
are using Linux and have installed it in \bin. Then choose
ConTeXt (LuaTeX) as the processing tool
On 3/27/2023 3:31 PM, Carlos via ntg-context wrote:
mkiv lua stats > loaded fonts: 4 files: latinmodern-math.otf,
lmroman10-regular.otf, lucidabrightregular.ttf, lucidasansregular.ttf
i admit never having seen lucida ttf files (but when opentype ttf files
are used with an afm file present
On Sat, Mar 25, 2023 at 09:26:36PM +0100, Hans Hagen via ntg-context wrote:
> On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
> > Hello list:
> >
> > This is under a fresh TeXLive installation. Sort as to put aside any
> > texlive prepackaged issues.
> >
> > And the followign lines is the
s | variable 'OSFONTDIR' specifies path
> > > > '/usr/share/fonts'
> > > > fonts | names | globbing path '/home/ce/**.otf'
>
> There is something strange here.
> Is maybe TEXMFHOME set?
>
> Since you use a TeX live installation, some other texmf
man12-regular.otf
mkiv lua stats > font engine: otf 3.113, afm 1.513, tfm 1.000, 12 instances, 6
shared in backend, 4 common vectors, 2 common hashes, load time 0.413 seconds
mkiv lua stats > used platform: linux-64, type: unix, binary subtree: usr
mkiv lua stats > used engine: luatex vers
s | variable 'OSFONTDIR' specifies path
> > > > > > '/usr/share/fonts'
> > > > > > fonts | names | globbing path '/home/ce/**.otf'
> > >
> > > There is something strange here.
> > > Is maybe TEXMFHOME set?
> > >
| globbing path '/home/ce/**.otf'
There is something strange here.
Is maybe TEXMFHOME set?
Since you use a TeX live installation, some other texmfcnf.lua or texmf.cnf
might interfere.
Look into /usr/local/texlive/2023/
I'll check again to make sure. But keep in mind this issue predates
s | variable 'OSFONTDIR' specifies path
> > > > '/usr/share/fonts'
> > > > fonts | names | globbing path '/home/ce/**.otf'
>
> There is something strange here.
> Is maybe TEXMFHOME set?
>
> Since you use a TeX live installation, some other texmfcnf.l
| names | variable 'OSFONTDIR' specifies path '/home/ce'
fonts | names | variable 'OSFONTDIR' specifies path '/usr/share/fonts'
fonts | names | globbing path '/home/ce/**.otf'
There is something strange here.
Is maybe TEXMFHOME set?
Since you use a TeX live installation, some
in the setup for this program, depending on your OS and where you have
installed it, e.g. home/yourname/bin/context/tex/texmf-linux-64/bin if
you are using Linux and have installed it in \bin. Then choose ConTeXt
(LuaTeX) as the processing tool.
(2) But to make things a lot easier, I also use Federico's
ntg-context wrote:
> > >
> > > >
> > > > ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: in
> > > > upvalue 'walk_tree'
> > > Maybe your OSFONTDIR is pointing to empty. Does
> >
> > Good call. Thank you for the reminder H
On 3/25/2023 10:36 PM, Carlos via ntg-context wrote:
On Sat, Mar 25, 2023 at 09:45:25PM +0100, Hans Hagen via ntg-context wrote:
On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: in
upvalue 'walk_tree'
Maybe your
On Sat, Mar 25, 2023 at 09:45:25PM +0100, Hans Hagen via ntg-context wrote:
> On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
>
> > ...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030:
> > in upvalue 'walk_tree'
> Maybe your OSFONTDIR is pointing
3/texmf-config,
home:texmf, !!selfautoparent:texmf-config, !!selfautoparent:texmf-var,
!!selfautoparent:texmf-project, !!selfautoparent:texmf-fonts,
!!selfautoparent:texmf-local, !!selfautoparent:texmf-dist}/tex/context//
resolvers | lists | res: .\{/home/ce/.texlive2023/texmf-config,
/home/c
On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
...xlive/2023/texmf-dist/tex/context/base/mkiv/font-syn.lua:1030: in
upvalue 'walk_tree'
Maybe your OSFONTDIR is pointing to empty. Does
mtxrun --script font --reload
work
Hans
On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
Hello list:
This is under a fresh TeXLive installation. Sort as to put aside any texlive
prepackaged issues.
And the followign lines is the output of the error I've been having with the
call of context on a recent texlive installation by
after.
mtxrun --script cache --erase has also been called out to no avail
registered function call [1160]:
...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.:
Permission denied
stack traceback:
[C]: in upvalue 'func'
...live/2023/texmf-dist/tex/context
ese TTC fonts, e.g.
> NotoSerifCJK-Regular.ttc. But when I use mtxrun command to search
them,
> I get an error.
>
> $ mtxrun --script font --list --file NotoSerifCJK-Regular.ttc
> lua error : function call:
>
...e/garfileo/opt/context/tex/texm
ch them,
> > I get an error.
> >
> > $ mtxrun --script font --list --file NotoSerifCJK-Regular.ttc
> > lua error : function call:
> > ...e/garfileo/opt/context/tex/texmf-linux-64/bin/mtxrun.lua:10012: bad
> > argument #9 to 'format' (number expected, got string)
> Where can
: function call:
...e/garfileo/opt/context/tex/texmf-linux-64/bin/mtxrun.lua:10012: bad
argument #9 to 'format' (number expected, got string)
Where can i find that font? There was a time when one could download a
zip with all noto fonts but last time i checked that option was gone and
one ends up
Hi Hans,
I have already installed some Chinese TTC fonts, e.g.
NotoSerifCJK-Regular.ttc. But when I use mtxrun command to search them, I
get an error.
$ mtxrun --script font --list --file NotoSerifCJK-Regular.ttc
lua error : function call:
...e/garfileo/opt/context/tex/texmf-linux-64/bin
On 3/16/23 17:44, Leah Neukirchen via ntg-context wrote:
> Hi,
>
> LMTX prints a bit weird error message for undefined control
> sequences:
>
> \starttext
> \zong
> \stoptext
>
> tex error > tex error on line 2 in file ./foo.tex: Undefined
>
Hi,
LMTX prints a bit weird error message for undefined control sequences:
\starttext
\zong
\stoptext
tex error > tex error on line 2 in file ./foo.tex: Undefined control
sequence \undefined
\zong
Shouldn't it print "\zong" in the "tex error" line to
below demonstrates the
behavior.
Obviously, I can use full names in my document. However, I would like the
standard SI symbols, which are single capital letters, to work for me and my
less TeX-savvy colaborators.
Thanks!
Gavin
\starttext
Units does not completely ignore case.
\startformula
Hi,
When I reinstall LMTX on my linux 64 system, the first executing
install.sh gives the error message:
tex error > tex error on line 34 in file
/home/garfileo/public/context/tex/texmf-context/tex/context/base/mkiv/type-set.mkiv:
! I can't find file `type-imp-latinmodern.mkiv'.
so I h
3.06 14:48])?
Many thanks for your help,
Pablo
lua error > lua error on line 21 in file
~/context/tex/texmf-context/tex/context/base/mkiv/back-pdf.mkiv:
...ext/tex/texmf-context/tex/context/base/mkiv/lpdf-nod.lua:72: creating
a whatsit requires the subtype number as a second argument
st
\stopitemize
\stoptext
```
This currently fails with:
```
resolvers | formats | executing runner 'run luametatex format':
/home/gerion/context/tex/texmf-linux-64/bin/luametatex --jobname="./test.tex"
--fmt=/home/gerion/context/tex/texmf-cache/luametatex-cac
eX's float positioning algorithm should be rather reliable
> and stable
Not as much as you would expect. The TeX page breaking algorithm is
greedy, single-pass, and dependant on every page prior, so you can get
some pretty chaotic results in pathological situations. "Typical"
documents don
iles (MWEs):
% index-1.tex
\setupinteraction[state=start]
\starttext
test \index{entry WB.1} \page empty \page
test \index{another WB.1} \page empty \page
test \index{onemore WB.1} \page empty \page
test \index{whatever WB.1} \page empty \page
test \index{common} \page e
Hans needs to confirm, "In the next update..."
Test files (MWEs):
% index-1.tex
\setupinteraction[state=start]
\starttext
test \index{entryWB.1} \page empty \page
test \index{another WB.1} \page empty \page
test \index{onemore WB.1} \page empty \page
test \inde
, I got the error: `tex error > tex error on line 30 in file
/Users/pmazaitis/Opt/context/tex/texmf-context/tex/context/modules/mkiv/m-databaseplus.mkiv:
! Undefined control sequence`
And then: `The control sequence at the end of the top line of your error
message was never
\def
now and did a fresh
> standalone install today:
>
> mtx-context | ConTeXt Process Management 1.04
> mtx-context |
> mtx-context | main context file:
> /home/gverhaag/ConTeXtInstallation/tex/texmf-context/tex/context/base/mkiv/context.mkiv
> mtx-context | current
Dear ConTeXt-user,
Have been using ConTeXt for quite some time now and did a fresh
standalone install today:
mtx-context | ConTeXt Process Management 1.04
mtx-context |
mtx-context | main context file:
/home/gverhaag/ConTeXtInstallation/tex/texmf-context/tex/context/base/mkiv
On 2/5/23 13:44, Hans Hagen via ntg-context wrote:
> On 2/4/2023 10:10 AM, Pablo Rodriguez via ntg-context wrote:
>>> https://wiki.contextgarden.net/French_spacing Not helpful alas.
>>
>> Would you be so kind to update the wiki?
>>
>> I hope it helps,
> Assuming that you document it I'll add
>
>
In my MacOSX Ventura 13.2 on M1, ConTeXt work fine.
$ context --version
mtx-context | ConTeXt Process Management 1.04
mtx-context |
mtx-context | main context file:
/Users/monty/context/tex/texmf-context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2023.01.15
On 2/12/2023 4:28 PM, Tommaso Gordini via ntg-context wrote:
The curious thing is that even by launching the ConTeXt present in TeX
Live, what really works is always MkIV Standalone.
There should be
mtxrun -> luametatex
context -> luametatex
links plus
mxtrun.lua
context.lua
in the
have gone wrong?
>
> My guess is that when you invoke ConTeXt, you are running it
from TeX
> Live (or from other than the wiki installation).
Hi Tommaso,
I forgot to mention, to avoid path clashes, you may invoke ConTeXt in
the following way (it is only one li
Gordini via ntg-context wrote:
> >> [...]
> >> Do you have any idea where I might have gone wrong?
> >
> > My guess is that when you invoke ConTeXt, you are running it from TeX
> > Live (or from other than the wiki installation).
>
> Hi Tommaso,
>
> I f
On 2/12/23 17:34, Pablo Rodriguez via ntg-context wrote:
> On 2/12/23 16:28, Tommaso Gordini via ntg-context wrote:
>> [...]
>> Do you have any idea where I might have gone wrong?
>
> My guess is that when you invoke ConTeXt, you are running it from TeX
> Live (or
LMTX doesn't even work
> from a terminal, of course.
I’m on Linux, so no TeXShop here.
BTW, I’m not sure "luametatex" may work as you intend (without any
format file).
> The curious thing is that even by launching the ConTeXt present in TeX
> Live, what really works is always MkIV
in the directory I've chosen:
charlie@Air-di-Tommaso ~ % which luametatex
/Users/charlie/Documents/ConTeXt/ConTeXt-LMTX/tex/texmf-osx-arm64/bin/luametatex
charlie@Air-di-Tommaso ~ % type luametatex
luametatex is
/Users/charlie/Documents/ConTeXt/ConTeXt-LMTX/tex/texmf-osx-arm64/bin/luametatex
charlie
Dear all,
I think that I found the cause.
The page layout of my file is different from that of MetaFun manual.
After borrowing the \setuplayout from MetaFun-000.tex, it works correctly.
I am sorry to give you a wrong example.
Thank you for reading.
Best regards,
Dalyoung
> 2023. 2. 10.
Dear all,
I copied the code of defining chapter command from metafun-000.tex, and run it.
But the result is different from that in MetaFun Manual.
There is a big spaces between the number and the title which yields the number
cannot be seen.
I commented out several lines which seems
>> [snip]
>> luatex warning > font: lua-loaded font '21' with name 'ex-iwonar' has no
>> characters
>> fonts > virtual math > the mapping is incomplete for 'iwonamath'
>> at 7pt
>> tex error > tex error on line 1 in file ./tt.te
iwonamath' at
7pt
tex error > tex error on line 1 in file ./tt.tex:
lua error:
registered function call [1154]:
...-64/tex/texmf-context/tex/context/base/mkxl/math-vfu.lmt:677: attempt to
index a nil value (local 'fci')
stack traceback:
...-64/tex/texmf-context/tex/conte
worked for me on the above MWE but Iwona failed with the log entry:
[snip]
luatex warning > font: lua-loaded font '21' with name 'ex-iwonar' has no
characters
fonts > virtual math > the mapping is incomplete for 'iwonamath' at
7pt
tex error > tex error on line 1 in f
===
Dear TeX users and friends,
good news - come what may, there will be BachoTeX 2023 as indeed I
promised when
announcing BachoTeX 2022 cancellation.
The SARS-CoV-2 virus did not disappear but seems to have become less of
a danger
as far as one can tell. The war
your point, since this is also a question of
perspective.
What may be named “French spacing” in English may be considered as
“English spacing” in any other European language.
But this is pure TeX
(https://git.savannah.gnu.org/cgit/teximpatient.git/plain/teximpatient/book.pdf#search=null
e page.)
Is this a deliberate change and the Wiki needs to be updated or should the
change be reverted for backwards compatibility?
yes and no ... we not handle them as strings (because we have more
variants) but i can catch it
(i'll send you a test)
% corners-001.tex
\setupbodyfont[dejavu]
\sta
rspective.
What may be named “French spacing” in English may be considered as
“English spacing” in any other European language.
But this is pure TeX
(https://git.savannah.gnu.org/cgit/teximpatient.git/plain/teximpatient/book.pdf#search=null):
\starttext
\startTEXpage[offset=1em]
PhD. Next senten
List: What method should one use to code whitespace after a period as
being sentence-ending, not midsentence, when not employing French
spacing? For example, if one writes
"... John Doe, PhD. Next sentence x y z ... ."
the space in "PhD. Next".
In LaTeX, we have "\@. " (code whitespace
is MWE:
% 0x221A is the radical symbol
\definefallbackfamily [MainFace] [mm] [TeX Gyre Pagella Math] [force=yes,
range=0x221A]
\definefontfamily [MainFace] [tf] [Cambria] % or [XITS]
\definefontfamily [MainFace] [mm] [Cambria Math] % or [XITS Math]
\setupbodyfont [MainFace]
\starttext
Am Sat, 28 Jan 2023 03:01:24 +0100 schrieb Kalouguine Andre via
ntg-context:
> I'm trying to make a verbatim block of text with copiable leading spaces
> so that students can just copy my Python code snippets into their IDE.
This basically doesn't work (quite unrelated to the tex code).
T
gt;
> > Yes, I want to mix casual with serif, sans-serif and so on.
>
> Hi Mattias (please, excuse my previous misspelling of your name),
>
> here you have it:
>
> \definefontfamily[mainface][rm][TeX Gyre Pagella]
> \definefontfamily[mainface][ss][TeX Gyre He
.. how reliable is is to
recognize a sentence and such, but given that tex is a programing
environment all is possible in the end
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27
-luatex-to-convert-interword-glue-to-spaces-and-kerns/sfdkdkybrvkv
wherein the author replaces the TeX glue with spaces and kerning. I was
wondering whether the same idea could be applied within the typing
environment but making a primitive verbatim environment using \obeylines
and \obeyspaces did
excluded experiments) is one of them. So, one has
to work with what one gets (not much different from the rest of tex
functionality). With careful coding the performance hit is not that
large and machines still get a bit get faster so that compensates it
anyway. Although some low level approaches can
on the kind of input, coding etc .. how reliable is is to
recognize a sentence and such, but given that tex is a programing
environment all is possible in the end
Hans
-
Hans Hagen
Dear list,
I have noticed a somewhat strange difference between protected macros
and protected luacalls, namely that the latter cannot be expanded by
\the. In the example below I define a Lua function that prints
\numexpr 17\relax to the token stream and I call it once from a
protected TeX macro
On 1/23/23 20:32, Mattias Märka via ntg-context wrote:
> Hi Pablo,
>
> Yes, I want to mix casual with serif, sans-serif and so on.
Hi Mattias (please, excuse my previous misspelling of your name),
here you have it:
\definefontfamily[mainface][rm][TeX Gyre Pagella]
\definef
Hi folks,
I forked the New Typesetting System (NTS) as KeenType. KeenType is a
100% pure Java library/app that can generate SVG diagrams from plain
TeX documents.
Here's a list of the changes (and sample output):
https://github.com/DaveJarvis/KeenType/releases/tag/1.0.0
Here's how typesetting
g/language/hyph-utf8/tex/generic/hyph-utf8/patterns/tex/hyph-el-polyton.tex).
Ironically, modern polytonic Greek patterns would be required to typeset
both the act and the decree that introduced the monotonic ortography.
2. Greek doesn’t seem to have language-dependent commands (such as
\c
82.
ConTeXt includes patterns for ancient and monotonic Greek, but none for
modern polytonic Greek
(http://mirror.ctan.org/language/hyph-utf8/tex/generic/hyph-utf8/patterns/tex/hyph-el-polyton.tex).
Ironically, modern polytonic Greek patterns would be required to typeset
both the act
ortography was polytonic before 1982.
ConTeXt includes patterns for ancient and monotonic Greek, but none for
modern polytonic Greek
(http://mirror.ctan.org/language/hyph-utf8/tex/generic/hyph-utf8/patterns/tex/hyph-el-polyton.tex).
Ironically, modern polytonic Greek patterns would be required
On 1/18/23 19:07, Hans Hagen via ntg-context wrote:
> On 1/18/2023 6:47 PM, Pablo Rodriguez via ntg-context wrote:
> [...]
>> If I’m not wrong (in my previous statement), I think this is
>> counterintuitive, since undefined commands are fine in TeX comments and
>> unde
On 1/18/2023 6:47 PM, Pablo Rodriguez via ntg-context wrote:
from what I understand is that undefined TeX commands cannot be added to
Lua comments.
Indeed. Of course we could have some 'ignore undefined command' feature
but that cripples the engine as well as then also never gives warning
nd somewhere
> in there?
Hi Bruce,
from what I understand is that undefined TeX commands cannot be added to
Lua comments.
If I’m not wrong (in my previous statement), I think this is
counterintuitive, since undefined commands are fine in TeX comments and
undefined variables are fine inside \startluacode … \s
1.15 14:04 LMTX fmt: 2023.1.16 int:
english/english
system >
system > 'cont-new.mkxl' loaded
open source > level 1, order 1, name
'/opt/luametatex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mk
\==12 %
\catcode`\,=12 %
\catcode`\|=12 %
\catcode`\&=12 %
\let~\pgfmath@char@quote
}}%
{\pgfmath@catcodes "}
\bye
works in Knuth TeX, so it's likely not our fault.
So what's with the double quote ...
I haven't looked pgf core in a while, but does it make
at's most likely due to
>
> https://github.com/pgf-tikz/pgf/issues/1062
> https://github.com/pgf-tikz/pgf/pull/1073
>
> but this MWE
>
> \catcode`\@=11
>
> \begingroup
> \lccode`\~=`\"
> \lowercase{\endgroup
> \def\pgfmath@catcodes{%
> \catcode`\
\def\pgfmath@catcodes{%
\catcode`\==12 %
\catcode`\,=12 %
\catcode`\|=12 %
\catcode`\&=12 %
\let~\pgfmath@char@quote
}}%
{\pgfmath@catcodes "}
\bye
works in Knuth TeX, so it's likely not our fault.
Cheers,
Henri
>
> Thanks,
> Aditya
>
1.15 14:04 LMTX fmt: 2023.1.16 int:
english/english
system >
system > 'cont-new.mkxl' loaded
open source > level 1, order 1, name
'/opt/luametatex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
system > beware: some patches loaded from cont-new.mkiv
On 1/16/23 02:42, Michal Vlasák via ntg-context wrote:
> [...]
> I would think that something like the attached could work. But in some
> cases it fails on the TeX side with something I am not sure about. I
> probably overlooked something. Anyways the idea is to just use the
> Star
:
\usemodule[pgfplots]
\starttext
Hello
\stoptext
gives
tex error > tex error on line 521 in file pgfplots.code.tex: Use of
\pgfplots@command@to@string@@ doesn't match its definition
just load tikz first so that the right loader helpers are there
\usemodule[tikz]
\usemodule[pgfplots]
\startt
nths.
> >
> > Thanks for all the great updates!
> these extra modules have bad loaders ... i'll send you better ones to test
pgfplots still appears to be broken in LMTX:
\usemodule[pgfplots]
\starttext
Hello
\stoptext
gives
tex error > tex error on line 521 in file pg
1-09-17), so
there was a bug. Reasoning for removal of the "Current" variants at the
time:
On Tue Sep 14, 2021 at 9:37 PM CEST, Hans Hagen wrote:
> Because \currentrendering is local we could as well drop the Current
> variants ... it's not like people will put hundreds of v
m your error message (\currentbtxloctext) seems
to be defined in four setups from tex/publ-imp-sbl.mkvi:
\def\currentbtxloctext{\btxparameter{loctext}}
The setups containing the definitions are btx:sbl:cite:inlinelong,
btx:sbl:cite:inlineshort, btx:sbl:cite:inline and btx:sbl:cite:shorthand.
You
g!
>> Last night I updated LMTX on my Raspberry Pi4. — After this action it
>> appeared, that I could no-more compile tex-files: error no format found.
>> I tried to generate a format manually., however this did not work out. In
>> the log-file the following error is placed:
>
Dear list,
as already reported in another thread, bimaries (for Linux64) weren’t
updated with current latest (2023.01.04 11:35),
Just in case it might help others (and to fix the issue), deleting the
file tex/texmf-linux-64.tma allows the download of newer binaries
(although the name for your
On 1/9/2023 6:54 PM, Willi Egger via ntg-context wrote:
Good morning!
Last night I updated LMTX on my Raspberry Pi4. — After this action it appeared,
that I could no-more compile tex-files: error no format found.
I tried to generate a format manually., however this did not work out
Good morning!
Last night I updated LMTX on my Raspberry Pi4. — After this action it appeared,
that I could no-more compile tex-files: error no format found.
I tried to generate a format manually., however this did not work out. In the
log-file the following error is placed:
…/anch-pgr.lmt:901
% : 3360848 :
tex/texmf-linux-64/bin/luametatex
mtx-install | tex/texmf-linux-64/bin/luametatex, try again later:
this is indeed an indication that an old binary is used
Hans
-
Hans Hagen
801 - 900 of 22999 matches
Mail list logo
