[NTG-context] Re: Wiki - test/proposal to further clarify documentation
Am 14.04.24 um 21:45 schrieb Peter Hopcroft via ntg-context: It would be great if the main page actually said what Context does. In my poster (still WIP) I wrote: start --- The “infamous” alternative to LaTeX While most designers use graphical tools, there are still areas where code-based typesetting systems are fun, make sense or are even superior. While LaTeX is the most known of these, ConTeXt is used by a growing minority of ambitioned enthusiasts around the world. The small but active and creative community of ConTeXt users and developers is always driving TeX development over new frontiers: NTS, MetaFun, Oriental TeX, LuaTeX, mplib, LuaMetaTeX… They’re also dubbed the incisors (AKA cutting edge) of the dinosaur of Open Source. ConTeXt is aimed at creative users, known for advanced features like extensive font control and direct XML processing, with a deep integration of Lua and MetaPost. --- ConTeXt was invented in the 1990s by Hans Hagen and Ton Otten of the Dutch company “Pragma Advanced Document Engineering” for typesetting schoolbooks. Taco Hoekwater refactored the TeX source code to create LuaTeX which was further developed into LuaMetaTeX by Hans Hagen (and lately Mikael Sundqvist for refined math typography). --- “To be fair, switching to the ConTeXt way of thinking and doing things was not an overnight process […]. But once I got used to it, I could not imagine going back to LaTeX. I’ll go even further and say that, in my view, ConTeXt is the future of TeX. (Prof. Idris Samawi Hamid, 2009) Source: www.tug.org/interviews/hamid.html --- “ConTeXt is LaTeX done right. It is simple, flexible and powerful.” (J. U. Hasecke on Mastodon, 2022) --- Is ConTeXt for me? If you want … * to design your own layout * best quality math typesetting * to use Lua functions e.g. for processing data * deep integration of a graphics language (MetaPost) * to process XML input * no package conflicts * to use OpenType features * consistent setup commands * to place stuff on layers * visual debugging features * to have a lean, but mighty TeX system * to typeset much faster than with LaTeX * high quality Arabic typography … then ConTeXt is for you! --- stop ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua
Hi Denis, I made a similar solution for docker image [minidocks/context](https://hub.docker.com/r/minidocks/context): [https://github.com/minidocks/context/commit/9b3ccc1eb62e556cada29b5b761207a526bca52e](https://github.com/minidocks/context/commit/9b3ccc1eb62e556cada29b5b761207a526bca52e). You can get inspired. Everything works as it should: ``` $ docker run --rm -it minidocks/context --luatex --version resolvers | globbing | confusing filename, name: 'CHANGELOG.md', lower: 'changelog.md', already: 'ChangeLog.md' mtx-context | redirect luametatex -> luatex: luatex --luaonly --socket "/usr/share/tex/texmf/bin/mtxrun.lua" --script mtx-context --luatex --version --redirected resolvers | globbing | confusing filename, name: 'CHANGELOG.md', lower: 'changelog.md', already: 'ChangeLog.md' mtx-context | ConTeXt Process Management 1.06 mtx-context | mtx-context | main context file: /usr/share/tex/texmf-context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2024.04.01 08:59 mtx-context | main context file: /usr/share/tex/texmf-context/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2024.04.01 08:59 ``` Best, Martin Hasoň ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Back in the 90s
On 4/13/2024 2:12 PM, Riviera Taylor wrote: Hello, I was reading about the history of ConTeXt in the Not So Short Introduction To ConTeXt and I have a historical question. I noticed that the PDF specification was published in 1993 yet ConTeXt was invented in 1991. The book suggests that PDF output was handled by the PdfTeX engine in MKII in 2005. What sort of output did the software produce before PdfTeX was introduced? Was this the same as the output produced by the software before the publication of the PDF specification? 2005 is when we started with luatex which is a follow up on pdftex, and pdftex is more a mid 90's thing; we immediately adopted pdftex (which made some believe that context depended on pdftex which is not true) anyway, we started with dvi which needs a postprocessor to go to some printer format like specific hp or more general postscript but also can drive viewers we went from epson dot matrix printer -> early 300 dpi laser -> 600 dpi laser printer -> high speed oce 512 dpi printer (metric) -> high speed oce 600 dpi printer (+ crappy canon color laser printer) -> fast page-wide hp color inkjet office printer in mkii all is controlled by backend drivers, that use so called specials to support color, hyperlinks, images so a workflow can have - dvipsone : high quality postscript - dviwindo : viewer with typeone support and hyperlinks - acrobat : postscript to pdf and as all these external backends have their demands we could handle all these things in an abstract way (that way one could also drive printer properties like duplex or paper bins etc from a tex job) that meant that when pdf came around we could almost immediately support most of the interactive features in a dvi -> ps -> acrobat workflow when pdftex came around the intermediate step of postscript could be avoided which btw was also possible with dvipdfm(x) so we also supported that so to summarize, it went from tex -> dvi -> printer format tex -> dvi -> postscript -> more generic printer format tex -> dvi -> pdf -> print from acrobat tex -> pdf -> print from pdf viewer in the meantime we are pdf (as from that one can produce other formats) Hans (btw, the fact that we could easily support pdf was also a reason why at that time some adobe folk in nl used documents produced by context to show somewhat extrems usage of interactive features, thanks to the fact that tex can adapt to such new situations, also via the dvi route in this case with pdfmarks; at that time pdf usage - and features - was a bit more dualistic: ps replacement format versus storage and preview format, but that's a different story; but it still shows in how the standard evolved) - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua
On 4/11/24 18:56, Hans Hagen via ntg-context wrote: > [...] > it searches for mtxrun.lua and context.lua in the same path so you need: > > luametatex.exe > mtxrun.exe (can be link to luametatex.exe) > context.exe (can be link to luametatex.exe) > context.lua > mtxrun.lua > > all in the same (bib) path > > ... always has been so ... But now it seems that luatex has disappeared from our bin directories. Was this intended (because of the issues with the build farm)? Many thanks for your help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua
On 4/11/2024 5:25 PM, Pablo Rodriguez via ntg-context wrote: On 4/10/24 22:28, Denis Maier wrote: [...] context --luatex --generate Thanks, Pablo. I've tried it, but it doesn't seem to work... I get the same result on Win64 when I move the luatex binary from the tex/texmf-win64/bin/ directory. This may sound stupid, but could you check whether the bin directory contain the required binary? Sorry, "luatex --version" and even "whereis luatex" should give the same result (but on Windows, it seems to be https://ss64.com/nt/where.html). I hope it may help, it searches for mtxrun.lua and contextl.lua in the same path so you need: luametatex.exe mtxrun.exe (can be link to luametatex.exe) context.exe (can be link to luametatex.exe) context.lua mtxrun.lua all in the same (bib) path ... always has been so ... Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua
On 4/11/24 17:39, Denis Maier via ntg-context wrote: > [...] > Ok. It wasn't there. I have now copied it from my Miktex installation, but > it still does not work. (Looks like some path issue. The luatex binary from > the miktex installation seems to take priority over the one now in the > ConTeXt installation. Looks like I'm getting somewhere...) I wonder whether the path order might give priority. But in any case, I wonder whether it is intended that current latest (from the ConTeXt distribution) is intended neither to have the latest LuaTeX nor to have any LuaTeX binary at all. Hans (or Luigi), are we (just humble users) missing something here? Many thanks for your help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua
> -Ursprüngliche Nachricht- > Von: Pablo Rodriguez via ntg-context > Gesendet: Donnerstag, 11. April 2024 17:26 > An: 'mailing list for ConTeXt users' > Cc: Pablo Rodriguez > Betreff: [NTG-context] Re: unknown script 'mtx-context.lua' or 'mtx-mtx- > context.lua > > On 4/10/24 22:28, Denis Maier wrote: > >> [...] > >> context --luatex --generate > > > > Thanks, Pablo. > > I've tried it, but it doesn't seem to work... > > I get the same result on Win64 when I move the luatex binary from the > tex/texmf-win64/bin/ directory. > > This may sound stupid, but could you check whether the bin directory contain > the required binary? > > Sorry, "luatex --version" and even "whereis luatex" should give the same result > (but on Windows, it seems to be https://ss64.com/nt/where.html). > > I hope it may help, > > Pablo Ok. It wasn't there. I have now copied it from my Miktex installation, but it still does not work. (Looks like some path issue. The luatex binary from the miktex installation seems to take priority over the one now in the ConTeXt installation. Looks like I'm getting somewhere...) Thanks for your help, Denis ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua
On 4/10/24 22:28, Denis Maier wrote: >> [...] >> context --luatex --generate > > Thanks, Pablo. > I've tried it, but it doesn't seem to work... I get the same result on Win64 when I move the luatex binary from the tex/texmf-win64/bin/ directory. This may sound stupid, but could you check whether the bin directory contain the required binary? Sorry, "luatex --version" and even "whereis luatex" should give the same result (but on Windows, it seems to be https://ss64.com/nt/where.html). I hope it may help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua
> -Ursprüngliche Nachricht- > Von: Pablo Rodriguez via ntg-context > Gesendet: Mittwoch, 10. April 2024 19:35 > An: ntg-context@ntg.nl > Cc: Pablo Rodriguez > Betreff: [NTG-context] Re: unknown script 'mtx-context.lua' or 'mtx-mtx- > context.lua > > On 4/10/24 13:59, Denis Maier via ntg-context wrote: > > Hi, > > I wanted to test my earlier example (float placement) also with MKIV, > > but context ---luatex … give me this error message : > > unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua How can I > > make it work? > > Hi Denis, > > as far as I know, this is required first: > > context --luatex --generate Thanks, Pablo. I've tried it, but it doesn't seem to work... I'm getting this: resolvers | resolving | resolvers | resolving | warning: no lua configuration files found resolvers | resolving | no texmf paths are defined (using TEXMF) resolvers | resolving | mtxrun | the resolver databases are not present or outdated And again: mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua' Any ideas? Best, Denis ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua
On 4/10/24 13:59, Denis Maier via ntg-context wrote: > Hi, > I wanted to test my earlier example (float placement) also with MKIV, but > context ---luatex … > give me this error message : > unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua > How can I make it work? Hi Denis, as far as I know, this is required first: context --luatex --generate BTW, although LuaTeX 1.18 has been released, my Linux64 ConTeXt contains version 1.17.x. In fact, the LuaTeX binary was removed in an update some weeks (or months) ago. I had to copy it from a backup from a previous version. I hope it helps, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua
Hi, I wanted to test my earlier example (float placement) also with MKIV, but context ---luatex . give me this error message : unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua How can I make it work? Best, Denis ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] issue with \xmlinlineprettyprinttext
Dear list,
I have the following sample:
\startbuffer[demo]
a --b c
a --b c
\stopbuffer
\startxmlsetups xml:initialize
\xmlsetsetup{#1}{doc|code|inlinecode}{xml:*}
\stopxmlsetups
\xmlregistersetup{xml:initialize}
\startxmlsetups xml:doc
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:code
\xmlprettyprinttext{#1}{none}
\stopxmlsetups
\startxmlsetups xml:inlinecode
\xmlinlineprettyprinttext{#1}{none}
\stopxmlsetups
\definefontfamily[mainface][tt][TeX Gyre Cursor]
[features={default, quality}]
\setupbodyfont[mainface]
\starttext
\xmlprocessbuffer{main}{demo}{}
\type{a --b c}
\stoptext
Using current latest (from 2024.03.11 09:34), LMTX transforms "--" in
"–" (en-dash) only with \xmlinlineprettyprinttext (LuaTeX writes the
en-dash in the three cases).
This issue has been driving me crazy, since it took me a while what was
different here.
Is there something I can do to get \xmlinlineprettyprinttext as
\xmlprettyprinttext in this point?
Many thanks for your help,
Pablo
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: issue with typing in footnotes
Pablo Rodriguez via ntg-context schrieb am 17.03.2024 um 17:38:
Dear list,
I have the following sample (which was on the way of showing another issue):
\starttext
a
\starttyping
b
\stoptyping
c
\startfootnote
a
\starttyping
b
\stoptyping
c
\stopfootnote
\stoptext
Current latest (from 2024.03.11 09:34) breaks compilation with both LMTX
and LuaTeX.
As far as I know, this sample should be compiled without any issue.
Could you be so kind to confirm the issue or explain me what am I missing?
The footnote environment is just a fancy way for a command with a
argument and buffers don't like being part of arguments.
You can put the code in buffer outside of the footnote and type the
content of the buffer in the footnote.
begin example
\starttext
\def\startfoo#1\stopfoo{#1}
% \startfoo
% xxx
% \starttyping
% yyy
% \stoptyping
% zzz
% \stopfoo
\startbuffer
yyy
\stopbuffer
\startfoo
xxx
\typebuffer
zzz
\stopfoo
\stoptext
end example
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] issue with typing in footnotes
Dear list, I have the following sample (which was on the way of showing another issue): \starttext a \starttyping b \stoptyping c \startfootnote a \starttyping b \stoptyping c \stopfootnote \stoptext Current latest (from 2024.03.11 09:34) breaks compilation with both LMTX and LuaTeX. As far as I know, this sample should be compiled without any issue. Could you be so kind to confirm the issue or explain me what am I missing? Many thanks for your help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] update
Hi,
Todays update has a fix for the compact mode slant interference (as
explained by Wolfgang a few days ago). Hopefully that works out well.
We (MS and HH) also managed to make curve detection more accurate (the
decision routine that is responsible for straight lines in the MP
output) so that extreme paths with control points way beyond reasonable
still produce the right output (before we could get a wrong bbox due to
clipping the curve in the backend). One can actually also force "always
curve" with "withcurvature 1" (more variants might follow) but that is
more or us to have a test option. Curvature detection is mostly a pdf
efficiency feature and normally users should rely on the default to work
okay.
Other new mp features are relative and absolute points which makes it
possible to define paths in a turtle graphics way (a bit like hlineto
and vline in postscript), a native "--" operator (equivalent but
somewehat more efficient on huge generated paths). The luametafun manual
has a chapter on paths that describes some of this.
Yet another new feature is "firstcontrol" and "secondcontrol" that is an
addendum to controls that makes both control points the same when only
one is given.
Finally there is a fix in mp where some directions, think { dir 120 },
gave the wrong result due to sign swapping (so it was seen as { dir 200}
or { dir -60 }) as side effect of negative zeros fed into tan2. This
became obvious when MS reprocessed a graphic, as last year we switched
from scsled (no bug) to double (long time bug exposed). (The bug is also
present in LuaTeX double/binary mode but it will be fixed there too.)
The rest is not (yet) worth mentioning,
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: \em issue in MkXL (2024.03.05 11:26)
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
On 3/8/24 19:09, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
[...]
LMTX gets b, c and d in slanted form.
LuaTeX gets only b and c in slanted form.
[...]
I get b and d in italic which is the expected output.
Sorry, my LuaTeX is getting slanted b and d ("c" was my typo).
But I see what was causing my issue (line from
~/texmf/texmf-local/cont-loc.mkxl):
\enableexperiments[fonts.compact]
Which seeems weird to me. Or at least, I thought I read that Hans
enabled it by default in LMTX.
AFAIR Hans uses the setting in his own documents.
Then my question is whether this was caused by simply enabling compact
fonts or by doing it twice.
The results happen when you use compact mode and is a result of
\glyphslant which keeps the value of the italic style even when you
switch back to the upright style.
\enableexperiments[fonts.compact]
\definefontfamily[mainface][rm][TeX Gyre Termes]
[it={style:regular, features:{default,slanted}},
sl={style:regular, features:{default,slanted}}]
\setupbodyfont[mainface]
\starttext
\tf h\showcurrentfont[]\crlf
\it h\showcurrentfont[]\crlf
%\glyphslant\zerocount
\tf h\showcurrentfont[]\crlf
\it h\showcurrentfont[]
\stoptext
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: \em issue in MkXL (2024.03.05 11:26)
On 3/8/24 19:09, Wolfgang Schuster wrote:
> Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
>> [...]
>> LMTX gets b, c and d in slanted form.
>>
>> LuaTeX gets only b and c in slanted form.
> [...]
> I get b and d in italic which is the expected output.
Sorry, my LuaTeX is getting slanted b and d ("c" was my typo).
But I see what was causing my issue (line from
~/texmf/texmf-local/cont-loc.mkxl):
\enableexperiments[fonts.compact]
Which seeems weird to me. Or at least, I thought I read that Hans
enabled it by default in LMTX.
Then my question is whether this was caused by simply enabling compact
fonts or by doing it twice.
Many thanks for your help,
Pablo
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: \em issue in MkXL (2024.03.05 11:26)
Am 08.03.24 um 18:50 schrieb Pablo Rodriguez via ntg-context:
Dear list,
the following latest gets differents results when compiled with MkXL and
MkIV (in current latest from 2024.03.05 11:26):
\definefontfamily[mainface][rm][TeX Gyre Termes]
[features={default, quality},
it={style: regular, features:{default, quality, slanted}},
sl={style: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d\\
\stopTEXpage
\stoptext
LMTX gets b, c and d in slanted form.
LuaTeX gets only b and c in slanted form.
With latest LMTX (2024.03.05), b and d are slanted, as I would expect.
This might be just a test case, but I’d avoid switches like \em without
grouping.
Hraban
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: \em issue in MkXL (2024.03.05 11:26)
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
Dear list,
the following latest gets differents results when compiled with MkXL and
MkIV (in current latest from 2024.03.05 11:26):
\definefontfamily[mainface][rm][TeX Gyre Termes]
[features={default, quality},
it={style: regular, features:{default, quality, slanted}},
sl={style: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d\\
\stopTEXpage
\stoptext
LMTX gets b, c and d in slanted form.
LuaTeX gets only b and c in slanted form.
I think LMTX may have an issue here.
Could anyone be so kind to confirm this?
I get b and d in italic which is the expected output.
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] \em issue in MkXL (2024.03.05 11:26)
Dear list,
the following latest gets differents results when compiled with MkXL and
MkIV (in current latest from 2024.03.05 11:26):
\definefontfamily[mainface][rm][TeX Gyre Termes]
[features={default, quality},
it={style: regular, features:{default, quality, slanted}},
sl={style: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d\\
\stopTEXpage
\stoptext
LMTX gets b, c and d in slanted form.
LuaTeX gets only b and c in slanted form.
I think LMTX may have an issue here.
Could anyone be so kind to confirm this?
Many thanks for your help,
Pablo
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: missing metadata in LMTX
Pablo Rodriguez via ntg-context schrieb am 04.03.2024 um 07:17:
On 3/4/24 01:18, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 03.03.2024 um 20:02:
[...]
With LuaTeX, I get PDF metadata. With LuaMetaTeX, I cannot get them.
[...]
I can confirm the issue and it happens because Hans changed they way
how the values of the \setupinteraction commands are passed to Lua
side of ConTeXt to be written to the PDF file.
Many thanks for your reply and your explanation, Wolfgang.
I can provide at the moment solutions which ensure the information
appear in the PDF but none of the is very elegant and I hope Hans
can help with a clean solution.
The first one avoids the issue until Hans provides a final fix.
Here is the official solution:
\startxmlsetups xml:meta
\setupmetadata
[author={\xmltext{#1}{/author}},
title={\xmltext{#1}{/title}}]
\stopxmlsetups
The command is new and accepts the following keys:
- title
- subtitle
- author
- keyword
- date
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: issue mixing font features (LMTX & MkIV)
On 3/3/2024 11:54 AM, Pablo Rodriguez via ntg-context wrote:
Dear list,
I have the following sample:
\definefontfeature[wider][extend=2]
\definefontfamily[mainface][rm][TeX Gyre Pagella]
[features={default, quality, wider},
it={style: regular, features:{default, slanted, quality}},
bf={style: regular, features:{default, boldened-30}},
bi={style: regular, features:{default, boldened-30, slanted}}]
\setupbodyfont
[mainface, 30pt]
\starttext
\startTEXpage[offset=1ex]
a
{\it a}\\
{\bf a}
{\bi a}
\stopTEXpage
\stoptext
With current latest (2024.02.27 09:21), LuaTeX gets boldened and slanted
for regular (but the other fonts cannot inherit the wider feature and
wider will not mix with boldened-30 [even when specified]).
For some reason, LMTX from current latest cannot get slanted and
boldened-30 (but it mixes the inherited wider feature in all fonts).
This began to behave differently in latest from 2024.01.08 11:23 (which
is my next version after the one from 2023.09.26 18:19).
Could anyone confirm the issue?
accumulating these effects is dependent on how the features that you use
are defined
in luametatex we have a bit more advanced mechanism (also relates to
compact mode) because th eengine is a bit more clever
just make sure that you don't add up features where one calcels the
other, so use for instance:
\definefontfeature[wide] [extend=2]
\definefontfeature[wideslant][extend=2,slant=.2]
\definefontfeature[widebold] [extend=2,weight=.1]
\definefontfeature[wideboldslant][extend=2,weight=.1,slant=.2]
\definefontfamily[mainface][rm][TeX Gyre Pagella]
[tf={style:regular,features:{default,quality,wide}},
it={style:regular,features:{default,quality,wideslant}},
bf={style:regular,features:{default,quality,widebold}},
bi={style:regular,features:{default,quality,wideboldslant}}]
\setupbodyfont
[mainface,30pt]
\starttext
\startTEXpage[offset=1ex]
a
{\it a}
{\bf a}
{\bi a}
\stopTEXpage
\stoptext
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: missing metadata in LMTX
On 3/4/24 01:18, Wolfgang Schuster wrote: > Pablo Rodriguez via ntg-context schrieb am 03.03.2024 um 20:02: >> [...] >> With LuaTeX, I get PDF metadata. With LuaMetaTeX, I cannot get them. >> [...] > I can confirm the issue and it happens because Hans changed they way > how the values of the \setupinteraction commands are passed to Lua > side of ConTeXt to be written to the PDF file. Many thanks for your reply and your explanation, Wolfgang. > I can provide at the moment solutions which ensure the information > appear in the PDF but none of the is very elegant and I hope Hans > can help with a clean solution. The first one avoids the issue until Hans provides a final fix. Many thanks for your help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: missing metadata in LMTX
Pablo Rodriguez via ntg-context schrieb am 03.03.2024 um 20:02:
Dear list,
this issue has been bugging me for some time:
[...]
With LuaTeX, I get PDF metadata. With LuaMetaTeX, I cannot get them.
For both, I’m using current latest (from 2024.02.27 09:21).
Could anyone confirm the issue or explain me what I am missing
I can confirm the issue and it happens because Hans changed they way
how the values of the \setupinteraction commands are passed to Lua
side of ConTeXt to be written to the PDF file.
I can provide at the moment solutions which ensure the information
appear in the PDF but none of the is very elegant and I hope Hans
can help with a clean solution.
The first solution works around the grouping issue of the xmlsetups
environment and pushes the setting beyond the limit of it.
\startxmlsetups xml:meta
\aftergrouped{\setupinteraction
[author={\xmltext{#1}{/author}},
title={\xmltext{#1}{/title}}]}
\stopxmlsetups
The second solution makes the assignment to the \setupinteraction
command global to ensure they are kept even the environment ends,
int old MkII days ConTeXt provided a \startglobal environment to
do this but now I have rely on the primitives.
\startxmlsetups xml:meta
\globaldefs\plusone
\setupinteraction
[author={\xmltext{#1}{/author}},
title={\xmltext{#1}{/title}}]
\globaldefs\zerocount
\stopxmlsetups
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] missing metadata in LMTX
Dear list,
this issue has been bugging me for some time:
\startbuffer[demo]
author
title
text
\stopbuffer
\starttext
\startxmlsetups xml:initialize
\xmlsetsetup{#1}{code|meta|text}{xml:*}
\stopxmlsetups
\xmlregistersetup{xml:initialize}
\startxmlsetups xml:doc
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:meta
\setupinteraction
[author={\xmltext{#1}{/author}},
title={\xmltext{#1}{/title}}]
\stopxmlsetups
\startxmlsetups xml:text
\xmlflush{#1}
\stopxmlsetups
\setupinteraction[state=start]
\xmlprocessbuffer{main}{demo}{}
\stoptext
With LuaTeX, I get PDF metadata. With LuaMetaTeX, I cannot get them.
For both, I’m using current latest (from 2024.02.27 09:21).
Could anyone confirm the issue or explain me what I am missing?
Many thanks for your help,
Pablo
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] issue mixing font features (LMTX & MkIV)
Dear list,
I have the following sample:
\definefontfeature[wider][extend=2]
\definefontfamily[mainface][rm][TeX Gyre Pagella]
[features={default, quality, wider},
it={style: regular, features:{default, slanted, quality}},
bf={style: regular, features:{default, boldened-30}},
bi={style: regular, features:{default, boldened-30, slanted}}]
\setupbodyfont
[mainface, 30pt]
\starttext
\startTEXpage[offset=1ex]
a
{\it a}\\
{\bf a}
{\bi a}
\stopTEXpage
\stoptext
With current latest (2024.02.27 09:21), LuaTeX gets boldened and slanted
for regular (but the other fonts cannot inherit the wider feature and
wider will not mix with boldened-30 [even when specified]).
For some reason, LMTX from current latest cannot get slanted and
boldened-30 (but it mixes the inherited wider feature in all fonts).
This began to behave differently in latest from 2024.01.08 11:23 (which
is my next version after the one from 2023.09.26 18:19).
Could anyone confirm the issue?
Many thanks for your help,
Pablo
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Wiki page : Mixed languages sample (French, Ancient Greek, Arabic, Chinese)
ι. ταῦτα δὴ ἐκαλλωπισάμην, ἵνα καλὸς
παρὰ καλὸν ἴω}.
\noindent \quotation{Je rencontrai, dit-il, Socrate, sortant du bain et
les pieds chaussés de sandales, ce qui n'est guère dans ses habitudes,
et je lui demandai où il allait si beau. Il me répondit : «Je vais dîner
chez Agathon. Je me suis dérobé hier à la fête qu'il a donnée en
l'honneur de sa victoire, parce que je craignais la foule; mais je me
suis engagé à venir le lendemain : voilà pourquoi je me suis paré; je
voulais être beau pour venir chez un beau garçon}\inmargin{Platon, {\em
Banquet}, 174a}.
\stopnarrower
On pourrait assurément faire mieux en matière d'édition. Par exemple,
mettre le texte grec à gauche et sa traduction française à droite sur la
même page, ce qui donnerait quelque chose comme ceci :
\startnarrower[1*left,1*right]\tfx\setupinterlinespace
\startTwoColumns
\quotation{Ἔφη γάρ οἱ Σωκράτη ἐντυχεῖν λελουμένον τε καὶ τὰς βλαύτας
ὑποδεδεμένον, ἃ ἐκεῖνος ὀλιγάκις ἐποίει· καὶ ἐρέσθαι αὐτὸν ὅποι ἴοι οὕτω
καλὸς γεγενημένος. καὶ τὸν εἰπεῖν ὅτι· Ἐπὶ δεῖπνον εἰς Ἀγάθωνος. χθὲς
γὰρ αὐτὸν διέφυγον τοῖς ἐπινικίοις, φοβηθεὶς τὸν ὄχλον· ὡμολόγησα δ᾽ εἰς
τήμερον παρέσεσθαι. ταῦτα δὴ ἐκαλλωπισάμην, ἵνα καλὸς παρὰ καλὸν
ἴω}.\TwoColumns
\quotation{Je rencontrai, dit-il, Socrate, sortant du bain et les pieds
chaussés de sandales, ce qui n'est guère dans ses habitudes, et je lui
demandai où il allait si beau. Il me répondit : «Je vais dîner chez
Agathon. Je me suis dérobé hier à la fête qu'il a donnée en l'honneur de
sa victoire, parce que je craignais la foule ; mais je me suis engagé à
venir le lendemain : voilà pourquoi je me suis paré ; je voulais être
beau pour venir chez un beau garçon}.
\stopTwoColumns
\stopnarrower
\section{Éditer avec \LaTeX : l'alternative \ConTeXt}
Les lecteurs habitués ont reconnu dans les paragraphes précédents la
marque et la technique du logiciel d'édition \LaTeX. Cependant,
l'utilisation de ce logiciel repose sur un ensemble assez important de
déclarations et il est nécessaire d'avoir une longue pratique pour
arriver à jouer avec, sinon la puissance, du moins la finesse de \LaTeX.
Les commandes sont très nombreuses et il faut recourir souvent à un
Manuel pour se remémorer les subtilités qui ont permis d'atteindre tel
rendu à l'impression. Bien entendu, il existe des logiciels commerciaux
d'aide à l'édition professionnelle pour le secteur des Humanités. Mais
d'une part ils sont payants et relativement coûteux pour une personne,
sans parler du prix des licences pour les groupements professionnels
d'enseignants et de chercheurs.
Devant cet état de choses, on peut se tourner vers \ConTeXt, qui n'est
pas une alternative à \LaTeX, mais une manière plus synthétique (voire
plus élégante) d'utiliser \LaTeX. \ConTeXt, de même que \LaTeX, est une
suite logicielle qui contient les macros de \LaTeX, les routines du
langage {\em Perl}, ainsi que les macros de \LuaTeX. On peut donc
définir à peu près tout ce qui est exigé au niveau de l'édition
professionnelle, sans entrer dans la connaissance technique du langage
\LaTeX. Bien entendu, on n'échappera pas à un certain nombre de
questions techniques, si l'on veut travailler avec ce type d'outil :
pour le mathématicien, rendre possible la présentation et l'édition
parfaites d'équations complexes, mais aussi de schémas et de tableaux
nécessite un apprentissage assez poussé. C'est vrai aussi pour les les
utilisateurs qui viennent des Humanités, qui connaissent leur domaine,
et qui veulent rédiger un document simple, un article de revue, voir des
chapitres entiers d'un ouvrage. Très certainement, ce sont les éditeurs
qui se chargent de la mise en page (sur la base d'une feuille de style
Word) du document que l'on veut publier. Mais parfois, s'il s'agit d'un
dossier de plusieurs articles, voire d'une édition avec une aide
financière à la publication, on aimerait avoir la main sur la qualité du
document imprimé. C'est une des raisons qui font que l'on pourrait
désirer maîtriser la chaîne éditoriale, non seulement pour se passer
éventuellement d'un éditeur, mais pour disposer d'un aperçu de son
propre travail.
\section{Faire coexister du Grec, du Chinois et de l'Arabe dans le même
texte}
Il n'est pas d'usage commun de lire dans le même document du texte
courant en français, une référence en grec, par exemple, lorsque dans le
{\em Timée}, Platon indique que le plus difficile est de commencer par
un commencement qui soit naturel (κατὰ φύσιν ἀρχήν)\inmargin{Platon,
{\em Timée}, 29b.}, une indication du nom du philosophe chinois {\em
Tchouang Tseu} (en {\em pinyin}\footnote{Le {\em pinyin} (chinois
classique 漢語拼音, littéralement “assembler les sons de la langue des
Han”), est une romanisation de la langue chinoise, qui est écrite en
alphabet latin. Ainsi, au lieu d'écrire 漢語拼音 en chinois traditionnel, ou
bien 汉语拼音 en chinois simplifié, on écrira {\em Hànyù Pīnyīn}.} Zhuangzi
et en chinois classique et simplifié :
[NTG-context] Re: FreeBSD 13.2
Hello, Henning Hraban Ramm writes: > > I guess you’re lacking the main distribution package. > > My installation (tree -dL 4, partly shortened): > > . > ├── bin (installation only) > └── tex > ├── texmf-cache (necessary, but auto-created?) > │ ├── luametatex-cache > │ │ └── context > │ └── luatex-cache > │ └── context > ├── texmf-context (main tree) > │ ├── colors OK, I unpacked the main distribution in context/tex, set PATH and ran mtxrun --generate which output: resolvers | resolving | variable 'SELFAUTOLOC' set to '/usr/home/rmason/context/tex/texmf-freebsd-amd64/bin' resolvers | resolving | variable 'SELFAUTODIR' set to '/usr/home/rmason/context/tex/texmf-freebsd-amd64' resolvers | resolving | variable 'SELFAUTOPARENT' set to '/usr/home/rmason/context/tex' resolvers | resolving | variable 'TEXMFCNF' set to '' resolvers | resolving | variable 'TEXMF' set to '' resolvers | resolving | variable 'TEXOS' set to 'texmf-freebsd-amd64' resolvers | resolving | resolvers | resolving | using configuration specification 'home:texmf/web2c;selfautoparent:/texmf-local/web2c;selfautoparent:/texmf-context/web2c;selfautoparent:/texmf/web2c' resolvers | resolving | resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/home/rmason/texmf/web2c' from specification 'home:texmf/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/usr/home/rmason/context/tex/texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/usr/home/rmason/context/tex/texmf-context/web2c' from specification 'selfautoparent:/texmf-context/web2c' resolvers | resolving | looking for regular 'texmfcnf.lua' on given path '/usr/home/rmason/context/tex/texmf/web2c' from specification 'selfautoparent:/texmf/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/home/rmason/texmf/web2c' from specification 'home:texmf/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/usr/home/rmason/context/tex/texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/usr/home/rmason/context/tex/texmf-context/web2c' from specification 'selfautoparent:/texmf-context/web2c' resolvers | resolving | found fallback configuration file '/usr/home/rmason/context/tex/texmf-context/web2c/contextcnf.lua' resolvers | resolving | looking for fallback 'contextcnf.lua' on given path '/usr/home/rmason/context/tex/texmf/web2c' from specification 'selfautoparent:/texmf/web2c' resolvers | resolving | resolvers | resolving | skipping configuration file 'selfautoparent:/texmf-context/web2c/texmfcnf.lua' (no valid format) resolvers | resolving | no texmf paths are defined (using TEXMF) resolvers | resolving | mtxrun | mtxrun | elapsed lua time: 0.041 seconds Looks like the unset TEXMF and TEXMFCNF envars are a problem. What should they be set to and where should they be set? Thanks, Roger ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: FreeBSD 13.2
Am 25.02.24 um 20:24 schrieb Roger Mason: Hello Hraban, Henning Hraban Ramm writes: Am 25.02.24 um 17:08 schrieb Roger Mason: Do I need mtxrun? If so, where are the sources and how do I build it? Yes, you need it, but it’s just an alias to luametatex: ~/context/tex/texmf-osx-64/bin $ ll total 7704 -rw-r--r--@ 1 hraban staff 6,0K 14 Dez 19:11 .DS_Store lrwxr-xr-x 1 hraban staff10B 22 Feb 18:47 context@ -> luametatex -rw-r--r-- 1 hraban staff 1,3K 10 Aug 2023 context.lua -rwxr-xr-x 1 hraban staff 2,9M 22 Feb 18:47 luametatex* lrwxr-xr-x 1 hraban staff10B 22 Feb 18:47 mtxrun@ -> luametatex -rw-r--r-- 1 hraban staff 685K 22 Feb 18:47 mtxrun.lua The mtxrun in ~/context/bin is only used during installation. What else do I need in ~/context/tex? Currently I have . ├── texmf-context │ └── web2c │ └── contextcnf.lua └── texmf-freebsd-amd64 └── bin ├── context -> luametatex ├── context.lua ├── luametatex ├── mtxrun -> luametatex └── mtxrun.lua I guess you’re lacking the main distribution package. My installation (tree -dL 4, partly shortened): . ├── bin (installation only) └── tex ├── texmf-cache (necessary, but auto-created?) │ ├── luametatex-cache │ │ └── context │ └── luatex-cache │ └── context ├── texmf-context (main tree) │ ├── colors │ │ └── icc │ ├── context │ │ └── data │ ├── doc │ │ ├── context │ │ └── fonts │ ├── fonts// (etc.) │ ├── metapost │ │ └── context │ ├── scripts │ │ └── context │ ├── source │ │ └── luametatex │ ├── tex │ │ ├── context │ │ └── generic │ └── web2c ├── texmf-fonts (not necessary) ├── texmf-local (not necessary) │ └── doc │ └── context ├── texmf-modules (not necessary) │ ├── doc// (etc.) │ ├── fonts// (etc.) │ ├── metapost │ │ └── context │ ├── scripts │ │ ├── context │ │ └── pgfplots │ ├── source │ │ ├── context │ │ └── luatex │ ├── tex │ │ ├── context │ │ ├── generic │ │ └── luatex │ └── tpm ├── texmf-osx-64 │ └── bin └── texmf-project (not necessary) HTH Hraban ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] LuaTeX 1.18.0
The upcoming version 1.18.0 has some changes that are not compatible with previous versions but should only apply in kpse mode: 1) the debug library is disabled; can be enabled with --luadebug 2) os.rename os.remove and lfs library functions are checked from kpse to see if the path is legal I'm sure some packages that use debug won't work without --luadebug at least. LuaLaTeX should be ok, and also ConTeXt mkiv should be ok. -- luigi ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Sorry for once more asking, i am at Work
On 2/20/24 14:45, Ursula Hermann wrote: > Dear Pablo, Dear List > > I have done all you told me yesterday. > > What I do not understand is that the Diagnosis in WinEdt 11 says, > that everything is ok. Also the PDF-Viewer. Sorry, but I can't copy > it, so I tell what I see. What I do not understand, because there is > no PDF Sorry, dear Uschi, but I’m afraid that I’m on Linux and WinEdt is totally unknown to me. That being said, if the messages from your computer are in German, there is no problem with the language (after all, https://www.deepl.com/ is an option too). Reading your log (which I simply ignored and Gavin took care to read it [totally my fault]), the first line you get is: This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023) (preloaded format=pdflatex 2024.2.6) 19 FEB 2024 12:41 The engine you are using is pdfTeX (from TeX Live 2023). In ConTeXt terms, this is almost ancient (»uralt«). ConTeXt MkII used pdfTeX as engine. In MkIV, the engine is LuaTeX. The latest engine is LuaMetaTeX for what is named either LMTX or MkXL. The format file is for pdfLaTeX, so ConTeXt cannot really do anything with it. It is consistent that ConTeXt complains about not finding the format file. > But now I tried to do what you have told me and the last line, Pablo > in cmd.exe says the same, what I get, if I compile: no format five > given, quitting. If you still happen to have the brand new installation on your desktop (and "test-doc.tex" [sorry, but redo if required]), open the command prompt and do the following: cd %USERPROFILE%\Desktop set PATH=%USERPROFILE%\Desktop\context\tex\texmf-mswin\bin For that window (or session), your system will be able to find only the path to the latest ConTeXt. This will prevent TeX Live 2023 messing with ConTeXt (well, if system-wide paths are not set for TeX Live [you might check that with "echo %PATH%" after setting the path as explained in the previous command]). After that, you may run: mtxrun --generate && context test-doc.tex If this works, the installation of TeX Live seems to set paths in a way that prevent ConTeXt to work. In that case, you would have to ask about that on the TeX Live list. I hope it helps now, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: manuals
Hello everyone! As an eternal newbie (with a memory like a goldfish), I started by building my own documentation from the web pages constructed by Bertrand Masson (prehistory archaeologist in Northern France) "les fiches à Bébert" (obsolete version here: http://bertrandmasson.free.fr/; new recommended version here: http://lesfichesabebert.fr/TeX/context/context-intro.html). As mentionned by Alain Delmotte. Bertrand Masson always keeps his site up to date, as he gives references to the documentation compiled by Garulfo (Joaquín Ataz López ), available in several languages, which I personally found well-done, useful and welcome. It's interesting to note with a rather positive smile that documentations, even if they're never really up to date in the details of ConTeXt's evolution, copy each other: that's what I did to write the beginning of a Wikibook in French (https://fr.wikibooks.org/wiki/ConTeXt/Qu%27est-ce_que_ConTeXt_%3F). I took things written by Bertrand Masson and was partially taken over by Garulfo and so on. Fortunately, the ConTeXT discussion list offers MWEs: all you have to do is to test them and save these examples on your system in the CTX-TESTS document folder. The next step is to classify these examples under the appropriate headings, then insert them into a coding system for a complex document that always calls for requests for explanations from discussion list participants. This question of documentation seems to me to be an age-old snake, not only on a technical subject which can be complex, as ConTeXt can be, but also concerning other types of documentation. For my part, although I haven't yet exhausted all the available documentation resources, whether internal to the distribution, or online like the ConTeXt Garden wiki, I think (but this has been better expressed here by others than me) that a real documentation refresh could be carried out collectively, with the great ambition of keeping obsolete documentation in an archive, while proposing a wiki with the date of update visible, in correlation with the PDF version. I have no idea how this documentation update could be achieved, but the fact is that it would be desirable to devote a section to the purely technical and basic aspects of CTX installation and font availability on Windows, Mac OS, Linux, BSD, etc., with MWEs and examples a little more detailed. Once this documentation has been passed as an introductory part (itself containing chapters explaining how this page of documentation was put together, with notes in the margins, etc.), this book could introduce MKIV, LuaTeX, MetaPost and so on, but with a clear distinction between the objectives sought: writing documentation with figures, writing a thesis in mathematics and physics, how to construct figures, or a bibliography. Not to mention the handling of photographs in an aesthetically demanding layout; all this with the possibility of showing complete or partial examples of work produced... In a nutshell: even if I give the impression that I'm asking you to reinvent the wheel, in reality it's a question of collating relevant existing information in a way that is intelligible and clear to the neophyte, but that also meets the demands of experienced users, who don't all use ConTeXt for the same reasons. Don't get me wrong: I'm not telling you what to do, I'm just giving you my opinion. Basically, I'm saying: documentation exists, but it has to be reliable, up to date, easy to find and enable you to make progress in difficult situations. As I said, I found Garulfo's work very welcome. It's not obsolete and doesn't need replacing. But perhaps it could be amended on certain points and completed and made available both in PDF and online in the ConTeXt Garden wiki pages? So, if by hypothesis the relevant documentation exists, here and there, but it's in the middle of pages that are in the past, it can be considered a daunting task to go looking for information that you realize is no longer up to date, because experience shows that it's no longer reliable. If confusion reigns, those seeking to apply what they've read risk turning away from ConTeXt, or asking the same questions over and over again. So there's plenty of food for thought to be had when it comes to methods for overhauling existing documentation. It's not a question of thinking long and hard about the availability of this documentation (on line or as a PDF?), but rather of knowing whether to build an encyclopedia, or a series of manuals, each of which is intended to circumscribe as closely as possible the problems encountered when attempting this or that form of page layout. I remember being astonished to discover, when I first started learning ConTeXt, all the vocabulary that existed around page layout (in French: Grand fond, petit fond, blanc de tête, blanc de pied, etc.), vocabulary that we ignore when we come from Word office autom
[NTG-context] Re: Memory consumption in new upload
On 2/17/2024 10:50 PM, Shiv Shankar Dayal wrote: I assume you would have created typescripts for those fonts. Can you please add them to ConTeXt distribution, at least for the popular fonts? Many of those are covered by typescripts. Those that are not, are on my machine because we needed them (often long ago) for a project (these are commercial fonts, in most cases typeone and of such a collection actually a few were used then). There are also some commercial fonts that I got for free. Then there are fonts that I have to check because users had an issue (public ones, of different quality and useability). Of those 'trying to cover all of unicode with different fonts of the same design' I tested subsets. And of course the fonts that come with the operating system (basically all fonts that context can access during a run). We're not going to make typescripts for every combination as in practice for most documents one needs a single setup and therefore only a handful of lines of code (and likely use some typescript file for a math font). There's also the selectfont mechanism that uses heuristics to do the same. There are plenty of examples in the distribution and for a specific style that demands certain fonts one can also put the definitions in the style. On Sun, Feb 18, 2024 at 3:12 AM Shiv Shankar Dayal mailto:shivshankar.da...@gmail.com>> wrote: The only change I made was that I started using a 9pt modern font than a 10 pt modern font. My document decreased from 580+ pages to 500 pages after that. About your document, I assume you had a lot of Graphics because text only 180MB is too high. I have only few diagrams and my file size is only 3MB. On Sun, Feb 18, 2024 at 2:13 AM Hans Hagen mailto:j.ha...@xs4all.nl>> wrote: On 2/17/2024 6:17 PM, Shiv Shankar Dayal wrote: > Thanks for new upload. I see that memory consumption is much less than > previous version. So > once again, thanks a lot. > > I am curious about what has changed in recent upload, that memory > consumption is about 60% of earlier versions. it's hard to tell what exact consumpiton is becaue for instance when lua creates tables, they grow by factors two when then have to (maybe 5.5 is a bit less consuming) on the one hand luametatex is more efficient than luatex due to all kind of ímprovements' but some nodes are larger so that takes more memory, which is only noticed when one has lots of text on a page (or keeps boxes stuff around) anyway, not that much changed since the previous upload, so maybe you just stay below a threshold I recently generated a 180MB document with 2500 fonts + metapost outlines of them and that could bump mem usage (with empty cache) to 30 GB (less after fonts were cached) but normally we stay around 125 MB for a document. Anyway, tex mem consumption can often be neglected compared to other applications. Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl <http://www.pragma-ade.nl> | www.pragma-pod.nl <http://www.pragma-pod.nl> - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl <mailto:ntg-context@ntg.nl> / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl <https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl> webpage : https://www.pragma-ade.nl <https://www.pragma-ade.nl> / https://context.aanhet.net <https://context.aanhet.net> (mirror) archive : https://github.com/contextgarden/context <https://github.com/contextgarden/context> wiki : https://wiki.contextgarden.net <https://wiki.contextgarden.net> ___ -- Respect, Shiv Shankar Dayal -- Respect, Shiv Shankar Dayal ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : http
[NTG-context] Re: Memory consumption in new upload
I assume you would have created typescripts for those fonts. Can you please add them to ConTeXt distribution, at least for the popular fonts? On Sun, Feb 18, 2024 at 3:12 AM Shiv Shankar Dayal < shivshankar.da...@gmail.com> wrote: > The only change I made was that I started using a 9pt modern font than a > 10 pt modern font. > > My document decreased from 580+ pages to 500 pages after that. > > About your document, I assume you had a lot of Graphics because text only > 180MB is too high. > I have only few diagrams and my file size is only 3MB. > > On Sun, Feb 18, 2024 at 2:13 AM Hans Hagen wrote: > >> On 2/17/2024 6:17 PM, Shiv Shankar Dayal wrote: >> > Thanks for new upload. I see that memory consumption is much less than >> > previous version. So >> > once again, thanks a lot. >> > >> > I am curious about what has changed in recent upload, that memory >> > consumption is about 60% of earlier versions. >> it's hard to tell what exact consumpiton is becaue for instance when lua >> creates tables, they grow by factors two when then have to (maybe 5.5 is >> a bit less consuming) >> >> on the one hand luametatex is more efficient than luatex due to all kind >> of ímprovements' but some nodes are larger so that takes more memory, >> which is only noticed when one has lots of text on a page (or keeps >> boxes stuff around) >> >> anyway, not that much changed since the previous upload, so maybe you >> just stay below a threshold >> >> I recently generated a 180MB document with 2500 fonts + metapost >> outlines of them and that could bump mem usage (with empty cache) to 30 >> GB (less after fonts were cached) but normally we stay around 125 MB for >> a document. Anyway, tex mem consumption can often be neglected compared >> to other applications. >> >> Hans >> >> >> - >>Hans Hagen | PRAGMA ADE >>Ridderstraat 27 | 8061 GH Hasselt | The Netherlands >> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl >> - >> >> >> ___ >> If your question is of interest to others as well, please add an entry to >> the Wiki! >> >> maillist : ntg-context@ntg.nl / >> https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl >> webpage : https://www.pragma-ade.nl / https://context.aanhet.net >> (mirror) >> archive : https://github.com/contextgarden/context >> wiki : https://wiki.contextgarden.net >> >> ___ >> > > > -- > Respect, > Shiv Shankar Dayal > -- Respect, Shiv Shankar Dayal ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Memory consumption in new upload
The only change I made was that I started using a 9pt modern font than a 10 pt modern font. My document decreased from 580+ pages to 500 pages after that. About your document, I assume you had a lot of Graphics because text only 180MB is too high. I have only few diagrams and my file size is only 3MB. On Sun, Feb 18, 2024 at 2:13 AM Hans Hagen wrote: > On 2/17/2024 6:17 PM, Shiv Shankar Dayal wrote: > > Thanks for new upload. I see that memory consumption is much less than > > previous version. So > > once again, thanks a lot. > > > > I am curious about what has changed in recent upload, that memory > > consumption is about 60% of earlier versions. > it's hard to tell what exact consumpiton is becaue for instance when lua > creates tables, they grow by factors two when then have to (maybe 5.5 is > a bit less consuming) > > on the one hand luametatex is more efficient than luatex due to all kind > of ímprovements' but some nodes are larger so that takes more memory, > which is only noticed when one has lots of text on a page (or keeps > boxes stuff around) > > anyway, not that much changed since the previous upload, so maybe you > just stay below a threshold > > I recently generated a 180MB document with 2500 fonts + metapost > outlines of them and that could bump mem usage (with empty cache) to 30 > GB (less after fonts were cached) but normally we stay around 125 MB for > a document. Anyway, tex mem consumption can often be neglected compared > to other applications. > > Hans > > > - >Hans Hagen | PRAGMA ADE >Ridderstraat 27 | 8061 GH Hasselt | The Netherlands > tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl > - > > > ___ > If your question is of interest to others as well, please add an entry to > the Wiki! > > maillist : ntg-context@ntg.nl / > https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl > webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) > archive : https://github.com/contextgarden/context > wiki : https://wiki.contextgarden.net > > ___ > -- Respect, Shiv Shankar Dayal ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Memory consumption in new upload
On 2/17/2024 6:17 PM, Shiv Shankar Dayal wrote: Thanks for new upload. I see that memory consumption is much less than previous version. So once again, thanks a lot. I am curious about what has changed in recent upload, that memory consumption is about 60% of earlier versions. it's hard to tell what exact consumpiton is becaue for instance when lua creates tables, they grow by factors two when then have to (maybe 5.5 is a bit less consuming) on the one hand luametatex is more efficient than luatex due to all kind of ímprovements' but some nodes are larger so that takes more memory, which is only noticed when one has lots of text on a page (or keeps boxes stuff around) anyway, not that much changed since the previous upload, so maybe you just stay below a threshold I recently generated a 180MB document with 2500 fonts + metapost outlines of them and that could bump mem usage (with empty cache) to 30 GB (less after fonts were cached) but normally we stay around 125 MB for a document. Anyway, tex mem consumption can often be neglected compared to other applications. Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Fwd: Re: Context lmtx for 32bit under LUBUNTU 18.04
On 2/14/2024 6:10 PM, Henning Hraban Ramm wrote: Sorry, I can’t help ATM. But Hans’ latest upload includes 32bt Linux binaries again. Indeed. I have to improvise a bit as the build is only partially working so some binaries i generate myself and currently we skip luatex (no big deal as most use luametatex anyway). Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Using plain TeX commands in ConTeXt
Thanks for correcting me, Wolfgang. I meant only TeX commands not plan TeX macros. On Wed, Jan 24, 2024 at 9:20 PM Wolfgang Schuster < wolfgang.schuster.li...@gmail.com> wrote: > Shiv Shankar Dayal schrieb am 24.01.2024 um 16:37: > > For example: \kern, \parindent and so on. Rephrasing the question, can > > LuaMetaTeX/ConTeXt compile > > plain TeX files. If yes, how can I do that? > > You mix up two different things here. > > 1. Plain TeX is a collection of TeX macros like ConTeXt or LaTeX. > > 2. LuaMetaTeX is a program like pdfTeX or LuaTeX which provides commands > which are used by above mentioned collections to create macros. > > Even though ConTeXt provides some commands which available in plain TeX > not all of the are supported which means you can't process plain TeX > documents. > > On the other hand commands which are provided by the engine like > \parindent can be used in a ConTeXt document but higher level mechanism > like \setupindenting are the better choice. > > Wolfgang > > -- Respect, Shiv Shankar Dayal ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Using plain TeX commands in ConTeXt
Shiv Shankar Dayal schrieb am 24.01.2024 um 16:37: For example: \kern, \parindent and so on. Rephrasing the question, can LuaMetaTeX/ConTeXt compile plain TeX files. If yes, how can I do that? You mix up two different things here. 1. Plain TeX is a collection of TeX macros like ConTeXt or LaTeX. 2. LuaMetaTeX is a program like pdfTeX or LuaTeX which provides commands which are used by above mentioned collections to create macros. Even though ConTeXt provides some commands which available in plain TeX not all of the are supported which means you can't process plain TeX documents. On the other hand commands which are provided by the engine like \parindent can be used in a ConTeXt document but higher level mechanism like \setupindenting are the better choice. Wolfgang ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Why LuaMetaTex is so slow?
On 1/19/2024 11:00 AM, Henning Hraban Ramm wrote: Am 19.01.24 um 10:31 schrieb Hans Hagen: (that said: luametatex runs fine on my mobile phone) What’s the smallest/oldest device someone tried LMTX on? (We were joking about “Hans’ thermostate and Alan’s fridge“…) Would it run on some 8 bit homecomputer? (I’d guess the RAM is too limited, and loading from datasette would need hours…) Just curious. The smallest i have here is a https://en.wikipedia.org/wiki/RCA_1802 which actually was a very nicely designed thing (also powers the hubble); processors never became cleaner. Now, as the kit I used only had 512 bytes ram (later 2K or so) it really learns one how to program efficiently (thihk of writing a simple game, save and load from cassette player, etc in that space; dynamic adaptive functions and such) and you know where I'm coming from'(later pascal and modula). That said: luametatex has a smaller memory footprint than luatex although nodes are way bigger but even that won't make it run well on an 8 bit processor, assuming it can address 32 bit mem. Context mkii started on 4.7 Mhz intel (386) so now we're 1000 times faster but performance gain is not linear. After all, tex has to compete with other applications running at the same time (browsers, remote clients, media apps, web polling apps, zoom, etc.) so it's kin dof amazing that it actually performs okay. What boosted performance is for instance ssd's. What might boost is ddr5 memory but that has to catch up with ddr4 first. What also boosted luametatex is cpu cache. I remember when taco and I moved to the math part we noticed a drop in performance, until machines got updated with larger cache. We'd just crossed some magic threshold. Actually, I kind of assume that we're stuck with cpu performance but nevertheless luametatex became faster. It helps to develop on an older machine and not on a yearly updated one as that obscures matters. (Not that I'd not like a faster machine, but that comes at a steep price.) Hans ps. In the tranmsition from pdftex to luatex to luametatex one should not underestimate Taco's effort of going from basically unreadable and useless C output by web2c (pascal -> c) to what became the luatex C code base (with embedded original documentation). From that we added more functionality gradually over a decade till luametatex spun off, which then lead to quite a bit of refactoring again (but trying to maintain the spirit of how tex is programmed). - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Why LuaMetaTex is so slow?
On 1/18/2024 11:15 PM, Bruce Horrocks wrote: On 18 Jan 2024, at 18:56, Shiv Shankar Dayal wrote: I understand that why it is slow, but the problem is that the difference is too high. My book has lots of math, so perhaps that is the reason. Option 1: Buy or borrow a faster computer. You'll get your desired speed-up far faster than waiting for Hans to make changes, even assuming there is something that can be changed. I'd recommend a Mac M3 :-) As tex is a single core process (ok, the os might delegate some file handling to other cores) it benefits from jump in core speed. I use a 2017 laptop with a reasonable fast intel xeon. I have a few docks spread round with different resolution monitors (1920x1200, 2560×1440, 4096×2160) and performance also depends on the connected monitor. I'd be curious to know how much these new processors impact performance over time because the ages of dohbling performance every year are past. There are several factors that impact performance: tex engine : quite a bit faster in luametatex mp engine : quite a bit faster in luametatex lua engine : not much we can do about but inefficient macros and usage can offset any gain in engine. One thing to keep in mind is that tex is an interpreter and all gets tokenized which is more costly in a 32 bit engine than in an 8 bit one (like pdftex). And although luametatex is more efficient than luatex that gets offset by more features that come at a price, but we still win. It helps a bit to know what tex does and what macros add to that. Simple timing operations is useless as in practice we have less cache hits than with a simple loop test: tex is jumping all over memory. Bottlenecks are often noe where one expects them. Anyway, if one can choose: go for a few high perfotmance cores over dozens of so called efficient cores. (that said: luametatex runs fine on my mobile phone) Option 2: Split your book into a project with each chapter, or even part of a chapter as a separate component and compile only the chapter you are working on. Set up a nighttime (or lunchtime) run to regenerate the entire book while you're away from the computer and speed doesn't matter. Indeed. That's the natural way to deal with large documents. Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: LuaMetaTeX code
On 1/19/2024 9:26 AM, Shiv Shankar Dayal wrote: Dear Hans, I saw the C code of LuaMetaTeX and I saw a lot of gotos which is not good coding practice. These potions of code which have goto should be refactored. I am a C programmer, but I know very little of TeX. If you can point me towards where should I start for TeX(perhaps TeX Book or TeX for the Impatient), I can help with refactoring of code to make is more efficient/easier. Luametatex evolves out of traditional tex so we have/keep some and although i grew up in the 'anti goto' times (pascal) there are plenty cases where i see no problem. Occasionaly I clean up such bits (when it makes sense). And I'm not going to enter coding practice discussions. Forget about refactoring ... there has already be done a lot of that and we want to stay sort of close to the original (also due to doicumentation). I know the code quite wel now and refactoring is for me counter productive. These are projects running for decades and engines need to be stable so changes come slow. You can compare the luanmetatex source to luatex and pdftex to see how we proiceed. Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Why LuaMetaTex is so slow?
On Fri, 19 Jan 2024, Hans Hagen via ntg-context wrote:
> On 1/19/2024 12:34 AM, Aditya Mahajan wrote:
> > On Thu, 18 Jan 2024, Hans Hagen wrote:
> >
> >> Of course we'll never be as fast as (pure) plain tex (no layers added) or
> >> latex (which often is advocated as faster than context).
> >
> > I was curious, so did a quick experiment: typeset \input knuth 500 times.
> > Here are the results:
> >
> > pdflatex: 547 pages/sec
> > lualatex: 308 pages/sec
>
> opentype or type 1 ?
type 1. I did not change anything in the defaults. I'll try to figure out how
to load opentype fonts in latex, and test lualatex.
> > MKIV: 130 pages/sec
> > LMTX: 147 pages/sec
>
> that is weird as lmtx is always faster here (we loose some 15% on the backend
> compared to luatex, maybe even more, but we gain back quite a bit elsewhere
> for various reasons)
LMTX is faster for me as well.
> > Interestingly, pdflatex, lualatex, and MkIV all generated pdf with 1112
> > pages, while LMTX generated a pdf with 1250 pages. Both MkIV and LMTX take
> > the same time to run (8.5 sec) but LMTX generates more pages so it is
> > faster.
>
> puzzling
>
> > Of course, this is a meaningless experiment from a practical point of view
> > as a 1000 page document will be more complex than just text.
> % engine=pdftex 1.2
> % engine=luatmetatex 1.6
> % engine=luatex 1.8
> % engine=xetex 2.4
>
> \starttext
>
> \dorecurse{500} {
> \input knuth \par
> }
>
> \stoptext
>
> 125 pages, so how does your test file look
5000 recursions (not 500, sorry about that).
\starttext
\dorecurse{5000}{\ReadFile{knuth}}
\stoptext
I'll send you the PDFs offlist.
Aditya
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: Why LuaMetaTex is so slow?
On 1/19/2024 12:34 AM, Aditya Mahajan wrote:
On Thu, 18 Jan 2024, Hans Hagen wrote:
Of course we'll never be as fast as (pure) plain tex (no layers added) or
latex (which often is advocated as faster than context).
I was curious, so did a quick experiment: typeset \input knuth 500 times. Here
are the results:
pdflatex: 547 pages/sec
lualatex: 308 pages/sec
opentype or type 1 ?
MKIV: 130 pages/sec
LMTX: 147 pages/sec
that is weird as lmtx is always faster here (we loose some 15% on the
backend compared to luatex, maybe even more, but we gain back quite a
bit elsewhere for various reasons)
Interestingly, pdflatex, lualatex, and MkIV all generated pdf with 1112 pages,
while LMTX generated a pdf with 1250 pages. Both MkIV and LMTX take the same
time to run (8.5 sec) but LMTX generates more pages so it is faster.
puzzling
Of course, this is a meaningless experiment from a practical point of view as a
1000 page document will be more complex than just text.
% engine=pdftex 1.2
% engine=luatmetatex 1.6
% engine=luatex 1.8
% engine=xetex 2.4
\starttext
\dorecurse{500} {
\input knuth \par
}
\stoptext
125 pages, so how does your test file look
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Wiki update
Hi all, I just updated the wiki ConTeXt to 20240108. The tag on the wiki by default uses luametatex (LMTX), but if you want luatex instead (MKIV), you can still do that by using . There have been some problems recently because Hans’ new binaries needed a newer version of various system libraries. I fixed that this morning after Hraban spotted the issue, but it means that there may be wiki pages with ConTeXt processing errors in them now. These can be recognised by either the colorised “error” output, or some cryptic “copy failed” message instead of the actual output. If you see one of those pages, Edit it. For the colorised “error” output you need to make a tiny change to the example itself (because that “error” output is correct as far as the wiki software can tell, so you have to force it to regenerate). For the “copy failed” case, you just have to start an edit and then immediately save again. The wiki will autogenerate any missing examples on save. Best wishes, Taco — Taco Hoekwater E: t...@bittext.nl genderfluid (all pronouns) ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Metapost docs
Dear Gavin, I am aware of these resources. My question is about docs of those Metapost libs which are in the distribution in Metapost directory. On Thu, Jan 11, 2024 at 9:12 PM Gavin via ntg-context wrote: > Hi Shiv, > > I am working with MetaPost in ConTeXt. Here are the resources I use, > roughly in the order I search when trying to solve a problem. > > - MetaFun Manual (http://www.pragma-ade.nl/general/manuals/metafun-p.pdf) > This is most comprehensive and helpful source. > - MetaPost Manual (http://mirrors.ctan.org/systems/doc/metapost/mpman.pdf) > This is not specific to ConTeXt, but it is very useful. > - The MetaFun page on the ConTeXt wiki ( > https://wiki.contextgarden.net/MetaFun_-_MetaPost_in_ConTeXt) Other pages > in the wiki’s graphics area are also helpful. ( > https://wiki.contextgarden.net/Graphics) Searching the wiki for specific > documentation on things like chemical structures is a little hit-or-miss, > but often quite useful. > -The mailing list. I have the most luck with very specific questions that > include a minimal working example. It should include the appropriate > \starttext…\stoptext or \startMPpage…\stopMPpage, so that it can be typeset > as-is. > > If you want to do 3D, you may want to get Lua involved for calculations. I > use > > - Programming in LuaTeX page on the wiki ( > https://wiki.contextgarden.net/Programming_in_LuaTeX) > - Programming in Lua, 4th ed. > by Roberto Ierusalimschy (https://www.amazon.com/gp/product/8590379868) > > If you provide an example of what you hope to accomplish with MetaPost, we > might have more specific recommendations. Below are two graphs that I made > in TikZ, which I hope to convert to MetaPost (actually LMTX). These are > from my chapter on elliptical orbits. > > I hope that helps you get started. > > Gavin > > > ___ > If your question is of interest to others as well, please add an entry to > the Wiki! > > maillist : ntg-context@ntg.nl / > https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl > webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) > archive : https://github.com/contextgarden/context > wiki : https://wiki.contextgarden.net > > ___ > -- Respect, Shiv Shankar Dayal ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Metapost docs
Hi Shiv, I am working with MetaPost in ConTeXt. Here are the resources I use, roughly in the order I search when trying to solve a problem. - MetaFun Manual (http://www.pragma-ade.nl/general/manuals/metafun-p.pdf) This is most comprehensive and helpful source. - MetaPost Manual (http://mirrors.ctan.org/systems/doc/metapost/mpman.pdf) This is not specific to ConTeXt, but it is very useful. - The MetaFun page on the ConTeXt wiki (https://wiki.contextgarden.net/MetaFun_-_MetaPost_in_ConTeXt) Other pages in the wiki’s graphics area are also helpful. (https://wiki.contextgarden.net/Graphics) Searching the wiki for specific documentation on things like chemical structures is a little hit-or-miss, but often quite useful. -The mailing list. I have the most luck with very specific questions that include a minimal working example. It should include the appropriate \starttext…\stoptext or \startMPpage…\stopMPpage, so that it can be typeset as-is. If you want to do 3D, you may want to get Lua involved for calculations. I use - Programming in LuaTeX page on the wiki (https://wiki.contextgarden.net/Programming_in_LuaTeX) - Programming in Lua, 4th ed. by Roberto Ierusalimschy (https://www.amazon.com/gp/product/8590379868) If you provide an example of what you hope to accomplish with MetaPost, we might have more specific recommendations. Below are two graphs that I made in TikZ, which I hope to convert to MetaPost (actually LMTX). These are from my chapter on elliptical orbits. I hope that helps you get started. Gavin chapter07-t-b-8c929184fdcc9da93d1ffe5262fc9842.pdf Description: Adobe PDF document chapter07-t-b-613fffa20a4b3581222e7b521bef3ace.pdf Description: Adobe PDF document ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: Status of Asymptote
Hi Shiv and Fabrice, > On Dec 30, 2023, Shiv Shankar Dayal wrote: > It would be nice to either support Metapost 3D or Asymptote. > On Dec 6, 2021, Fabrice L wrote: > I would be very interested to see an example of a Metafun drawing made with > the help of LuaTeX to speed up some calculations. I made a module that draws 3D globes with MetaPost and Lua. This was my first step toward drawing general projections. If anyone would like to join this project, I’d love some help. The globes module is only about 300 lines of code, and most of the challenge was hiding paths and parts of paths that are on the back side of the globe. Anybody could get up to speed pretty quickly. (I am completely new to both MetaPost and Lua, so I tried to be very clear in my coding.) My goal is a drawing process which starts with Lua tables containing data in arbitrary coordinates. The data could be any number of dimensions, and need not be rectangular. (For the globes the data is latitude and longitude points on the countries' boundaries.) The tables could be from an outside source (like the geographic data) or it could be calculated in Lua (for graphing functions or doing simulations). Lua does all of the calculations to project this data down to two dimensional, rectangular coordinates. Lua then passes these two dimensional points, or paths made from them, to MetaPost. MetaPost uses the points and paths to draw dots, curves and areas, to place labels, etc. The only transformation performed by MetaPost is the final scaling for drawing everything on the page. You can find the globe module on GitHub: https://github.com/GavinPolhemus/luageo I am relatively new to Git as well, so have patience if you start commenting or contributing there. I’ll learn fastest if there are collaborators! Gavin ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: QR Code
\Program Files\MiKTeX 2.9\miktex\bin\yap.exe
TeX-Bin (TeX.exe): OK*
C:\Program Files\MiKTeX 2.9\miktex\bin\tex.exe
TeX-Bin (LaTeX.exe): OK*
C:\Program Files\MiKTeX 2.9\miktex\bin\latex.exe
TeX-Bin (PDFTeX.exe): OK*
C:\Program Files\MiKTeX 2.9\miktex\bin\pdftex.exe
TeX-Bin (PDFLaTeX.exe): OK*
C:\Program Files\MiKTeX 2.9\miktex\bin\pdflatex.exe
TeX-Bin (BibTeX.exe): OK*
C:\Program Files\MiKTeX 2.9\miktex\bin\bibtex.exe
TeX-Bin (dvips.exe): OK*
C:\Program Files\MiKTeX 2.9\miktex\bin\dvips.exe
TeX-Bin (ps2pdf.exe): OK*
C:\Program Files\MiKTeX 2.9\miktex\bin\ps2pdf.exe
TeX-Bin (dvipdfmx.exe): OK*
C:\Program Files\MiKTeX 2.9\miktex\bin\dvipdfmx.exe
TeX-Bin (mf.exe): OK*
C:\Program Files\MiKTeX 2.9\miktex\bin\mf.exe
TeX-Bin (mpost.exe): OK*
C:\Program Files\MiKTeX 2.9\miktex\bin\mpost.exe
MiKTeX-Bin (TeXify.exe): OK*
C:\Program Files\MiKTeX 2.9\miktex\bin\texify.exe
My question is: Should I put the PATH in WinEdt or in Windows? Or in ConTeXt?
$TEXROOT/tex/texmf-$ARCH/bin/lib/luametatex/zint
Many thanks
Uschi
Von: Henning Hraban Ramm
Gesendet: Montag, 18. Dezember 2023 20:34:15
An: ntg-context@ntg.nl
Betreff: [NTG-context] Re: QR Code
Am 18.12.23 um 17:05 schrieb Ursula Hermann:
> Dear List
> After compiling
> \usemodule[m-zint]
> \starttext
> \barcode[alternative=isbnx, text=9783865419026, width=4cm] \blank[big]
> \barcode[alternative=qrcode, text={wie weet waar willem wever woont},
> width=3cm] \stoptext
>
> I got , what you see in the pdf.
Are you using MkIV (LuaTeX) or LMTX (LuaMetaTeX)?
What’s your ConTeXt version, and how did you install it? (TeX live,
Linux distribution, LMTX distribution?)
I guess a missing EPS means you load the MkIV version of the module,
probably because "m-zint".
Is there an error message with \loadmodule[zint]?
I can’t help with Windows; since Hans developed it on Windows, it should
work (but don’t ask me how).
Hraban
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: QR Code
Dear Hraban,
Thank your for your mail.
I have the latest ConTeXt version, and I have Texlive.
Uschi
-Ursprüngliche Nachricht-
Von: Henning Hraban Ramm
Gesendet: Montag, 18. Dezember 2023 20:34
An: ntg-context@ntg.nl
Betreff: [NTG-context] Re: QR Code
Am 18.12.23 um 17:05 schrieb Ursula Hermann:
> Dear List
> After compiling
> \usemodule[m-zint]
> \starttext
> \barcode[alternative=isbnx, text=9783865419026, width=4cm] \blank[big]
> \barcode[alternative=qrcode, text={wie weet waar willem wever woont},
> width=3cm] \stoptext
>
> I got , what you see in the pdf.
Are you using MkIV (LuaTeX) or LMTX (LuaMetaTeX)?
What’s your ConTeXt version, and how did you install it? (TeX live, Linux
distribution, LMTX distribution?)
I guess a missing EPS means you load the MkIV version of the module, probably
because "m-zint".
Is there an error message with \loadmodule[zint]?
I can’t help with Windows; since Hans developed it on Windows, it should work
(but don’t ask me how).
Hraban
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: QR Code
On Mon Dec 18, 2023 at 9:35 PM CET, Pablo Rodriguez via ntg-context wrote:
> On 12/18/23 20:34, Henning Hraban Ramm wrote:
> > [...]
> > Are you using MkIV (LuaTeX) or LMTX (LuaMetaTeX)?
>
> Many thanks for your reply, Hraban.
>
> I understood my issue with your reply (I known, your answer is intended
> to Uschi).
>
> It is also in the sent file:
>
> Creator:
>LuaMetaTeX 2.10.11 20230908 + ConTeXt LMTX 2023.09.26 18:19
> PDF Producer:
>LuaMetaTeX-2.10.11
>
> > I guess a missing EPS means you load the MkIV version of the module,
> > probably because "m-zint".
> >
> > I can’t help with Windows; since Hans developed it on Windows, it should
> > work (but don’t ask me how).
>
> I will try to explain what I understand from this (intended for Uschi).
>
> Given that there are two modules (m-zint and zint), there are two options:
>
> 1. Either you use the LMTX module (\usemodule[zint]) and you need the
> Zint library (as explained in
> https://wiki.contextgarden.net/Barcodes#Zint_module).
>
> 2. Or you use the MkIV module (\usemodule[m-zint]) and you need the Zint
> binary installed and CMD should be able to invoke it (already knowing
> its past).
>
> You may have the Zint binary installed, ConTeXt may be generating the
> required EPS files, but either Inkscape is not installed (or its path is
> unknown to the system), or ConTeXt cannot simply find where the
> converted PDF versions of the zint images are.
>
> If I have the following source in testing-barcodes.tex:
>
> \usemodule[m-zint]
> \starttext
> \startTEXpage[offset=1dk]
> \barcode[alternative=isbnx, text=9783865419026, width=4cm]
> \stopTEXpage
> \stoptext
>
> ConTeXt compiles it generating to extra files (when compared to the pure
> zint module for LMTX only):
>
> zint-isbnx-fe90eda0e93cf020312eps
> m_k_i_v_zint-isbnx-fe90eda0e93cf020312_eps_c60ccda70ef.pdf
>
> (Removed some characters in strings so file names fit in a single line.)
>
> The first file is generated by the Zint binary itself. The second one is
> the automatic conversion (through Inkscape) that ConTeXt needs to embed
> EPS (and SVG) files in the final PDF document.
>
> If m_k_i_v_zint-*.pdf files are missing, the problem might be that
> Inkscape isn’t installed (or its path is unknown to the system).
>
> If also zint-*.eps files are missing, you should find where Zint is
> generating them.
I will just add to the excellent answers above, that I very much
recommend LMTX and the LMTX way of using the zint _library_. I published
compiled versions of zint and couple of other libraries to the optional
libraries repository:
https://github.com/contextgarden/luametatex-optional-libraries
https://github.com/contextgarden/luametatex-optional-libraries/releases/tag/v20230902
I tested the steps on the wiki and libzint.dll works without problems:
i.e. install ConTeXt, create a few folders, move the dll and
mtxrun --generate.
My goto document for testing zint, that went without problems (even the
hexagons!):
\starttext
\usemodule[zint]
\barcode[alternative=isbnx, text=9783865419026, width=4cm]
\barcode[alternative=qrcode, text={https://wiki.contextgarden.net},
width=3cm]
\barcode[alternative=maxicode, text={test}, width=3cm]
\stoptext
Michal
PS: Coincidentally zint 2.13 has been released just today. Usually every
new zint release requires an update on the ConTeXt side, but older
releases still work well with ConTeXt (e.g. currently ConTeXt supports
2.10, 2.11 and 2.12). The version linked above works.
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: QR Code
On 12/18/23 20:34, Henning Hraban Ramm wrote: > [...] > Are you using MkIV (LuaTeX) or LMTX (LuaMetaTeX)? Many thanks for your reply, Hraban. I understood my issue with your reply (I known, your answer is intended to Uschi). It is also in the sent file: Creator: LuaMetaTeX 2.10.11 20230908 + ConTeXt LMTX 2023.09.26 18:19 PDF Producer: LuaMetaTeX-2.10.11 > I guess a missing EPS means you load the MkIV version of the module, > probably because "m-zint". > > I can’t help with Windows; since Hans developed it on Windows, it should > work (but don’t ask me how). I will try to explain what I understand from this (intended for Uschi). Given that there are two modules (m-zint and zint), there are two options: 1. Either you use the LMTX module (\usemodule[zint]) and you need the Zint library (as explained in https://wiki.contextgarden.net/Barcodes#Zint_module). 2. Or you use the MkIV module (\usemodule[m-zint]) and you need the Zint binary installed and CMD should be able to invoke it (already knowing its past). You may have the Zint binary installed, ConTeXt may be generating the required EPS files, but either Inkscape is not installed (or its path is unknown to the system), or ConTeXt cannot simply find where the converted PDF versions of the zint images are. If I have the following source in testing-barcodes.tex: \usemodule[m-zint] \starttext \startTEXpage[offset=1dk] \barcode[alternative=isbnx, text=9783865419026, width=4cm] \stopTEXpage \stoptext ConTeXt compiles it generating to extra files (when compared to the pure zint module for LMTX only): zint-isbnx-fe90eda0e93cf020312eps m_k_i_v_zint-isbnx-fe90eda0e93cf020312_eps_c60ccda70ef.pdf (Removed some characters in strings so file names fit in a single line.) The first file is generated by the Zint binary itself. The second one is the automatic conversion (through Inkscape) that ConTeXt needs to embed EPS (and SVG) files in the final PDF document. If m_k_i_v_zint-*.pdf files are missing, the problem might be that Inkscape isn’t installed (or its path is unknown to the system). If also zint-*.eps files are missing, you should find where Zint is generating them. Just in case it might help, Pablo ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: QR Code
Am 18.12.23 um 17:05 schrieb Ursula Hermann:
Dear List
After compiling
\usemodule[m-zint]
\starttext
\barcode[alternative=isbnx, text=9783865419026, width=4cm] \blank[big]
\barcode[alternative=qrcode, text={wie weet waar willem wever woont},
width=3cm] \stoptext
I got , what you see in the pdf.
Are you using MkIV (LuaTeX) or LMTX (LuaMetaTeX)?
What’s your ConTeXt version, and how did you install it? (TeX live,
Linux distribution, LMTX distribution?)
I guess a missing EPS means you load the MkIV version of the module,
probably because "m-zint".
Is there an error message with \loadmodule[zint]?
I can’t help with Windows; since Hans developed it on Windows, it should
work (but don’t ask me how).
Hraban
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: Compatibility Issue with TikZ/Spy Library in ConTeXt: Seeking Solutions
On 11/24/2023 11:17 AM, wolfgangbackes--- via ntg-context wrote:
Hello,
I am reaching out to seek assistance regarding a compatibility issue I have
encountered after installing ConTeXt on a new computer. The problem arises when
attempting to compile documents that utilize the spy library; the LuaTeX engine
returns the following error message:
"error (luacall): invalid number
mtx-context | fatal error: return code: 1"
Unfortunately, the error message provides no additional clues. To investigate
further, I created a minimal example, which you can easily verify at
https://context-on-web.eu/. The example employs the spy library within a TikZ
environment. Surprisingly, the same example runs without error on my local
LaTeX engine, indicating a potential compatibility issue between ConTeXt and
the spy library.
Here is the minimal example for your reference:
\starttext
\usemodule[tikz]
\usetikzlibrary {spy}
\starttikzpicture[spy using overlays={size=12mm}]
\draw (0,0) -- (1,1) -- (2,-1);
\spy [blue,magnification=5] on (1,1) in node at (3,0);
\stoptikzpicture
\stoptext
I am curious if anyone else has encountered a similar problem with the spy
library and ConTeXt and, if so, if there is a known solution. Any insights or
guidance would be greatly appreciated.
Thank you for your time and assistance.
the log probably mentions some call lua issue .. tikz is somewhat hard
to debug but in the end i figured out that it relates to the way it
registers function where it assumes that it's the only pqackage in the
tex universe
put this before you load tikz:
\ifdefined\pdfstrcmp\else
\def\pdfstrcmp{\directlua{
local a = token.scan_string()
local b = token.scan_string()
context((a < b and -1) or (a > b and 1) or 0)
}}
\fi
i'll add more efficient ones to the tikz modules
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Compatibility Issue with TikZ/Spy Library in ConTeXt: Seeking Solutions
Hello,
I am reaching out to seek assistance regarding a compatibility issue I have
encountered after installing ConTeXt on a new computer. The problem arises when
attempting to compile documents that utilize the spy library; the LuaTeX engine
returns the following error message:
"error (luacall): invalid number
mtx-context | fatal error: return code: 1"
Unfortunately, the error message provides no additional clues. To investigate
further, I created a minimal example, which you can easily verify at
https://context-on-web.eu/. The example employs the spy library within a TikZ
environment. Surprisingly, the same example runs without error on my local
LaTeX engine, indicating a potential compatibility issue between ConTeXt and
the spy library.
Here is the minimal example for your reference:
\starttext
\usemodule[tikz]
\usetikzlibrary {spy}
\starttikzpicture[spy using overlays={size=12mm}]
\draw (0,0) -- (1,1) -- (2,-1);
\spy [blue,magnification=5] on (1,1) in node at (3,0);
\stoptikzpicture
\stoptext
I am curious if anyone else has encountered a similar problem with the spy
library and ConTeXt and, if so, if there is a known solution. Any insights or
guidance would be greatly appreciated.
Thank you for your time and assistance.
Best regards,
Wolfgang Backes
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: context not producing synctex output that my synctex program can use
Henning and Hans, thanks for the replies. I have two follow-up questions below, as well as some other comments which other synctex users might find useful. On Sun, Nov 12, 2023 at 10:26 (+0100), Henning Hraban Ramm wrote: > Am 12.11.23 um 00:59 schrieb Jim: >> Hi, >> I've read the wiki, looked at workflows-synctex.tex, searched the web, and >> scratched my head, all to no avail. So here I am, cap in hand... >> When I run context, I get a .synctex file which has some information in it, >> but I can't find any invocation of synctex to return anything useful. Nor >> does the okular example in the wiki (https://wiki.contextgarden.net/SyncTeX) >> work for me. Ocular starts, but always on the first page, regardless of >> what line number I give it. >> On the other hand, pdftex creates a .synctex file which my copy of synctex >> find useful. >> I am using the synctex from the current version of texlive: >> This is SyncTeX command line utility, version 1.5 >> Can anyone either >> (a) enlighten me on what I am doing wrong; or >> (b) definitively confirm that context is not currently playing nicely with >> synctex (the wiki notwithstanding) and I should give up this quest for >> now. > ConTeXt doesn’t work with the synctex binary, but with > mtxrun --script synctex Thanks for that pointer. Q1: Should that be in the wiki (https://wiki.contextgarden.net/SyncTeX) somewhere? When I try that out, for example with mtxrun --script synctex --edit --name=a.tex --line=222 a.tex I am rewarded with sandbox | variable 'linenumber' has no checker (I tried various variations on that line I won't bore you with, but I keep getting that error message.) I also tried mtxrun --script synctex --goto --page=4 --x=100 --y=100 a.synctex and that silently returns without apparently doing anything. (While I don't have a 'scite' editor, I created a program called 'scite' that pops a message up on the screen if it is called.) Similar to --edit, mtxrun --script synctex --goto --page=19 --x=400 --y=180 --tolerance=99 --editor=scite a.synctex complains sandbox | variable 'tolerance' has no checker Although I don't know lua, the code is easy enough to read, but a short dive in to mtx-synctex.lua did not enlighten me. Q2: any enlightening comments on why I am getting these complaints. In any case, --find and --report (appear to) give meaningful results, so I can work with those. > Unfortunately, it’s not a drop-in replacement, so it doesn’t work with most > editors. (I was thinking about a translating wrapper script, but didn’t do > anything yet.) So much code to write, so little time ...:-) My immediate concern is forward search (i.e., editor tells viewer which page to display) and that one should be easy for me to create a wrapper. (I use emacs + auctex, which calls the synctex program, so writing my own synctex wrapper looks easy. Hopefully I won't regret using the word "easy" later.) > AFAIK TeXshop (MacOS) is the only TeX editor that supports ConTeXt’s > workflow. I've been thinking of patching some of evince's more annoying features, if I do, maybe I should look into making it work with context. > ConTeXt’s synctex format is much simpler than the “standard” LaTeX one and > should be at least as good, but alas it needs support from the editors. Indeed! On Sun, Nov 12, 2023 at 12:00 (+0100), Hans Hagen wrote: > On 11/12/2023 10:26 AM, Henning Hraban Ramm wrote: >> Am 12.11.23 um 00:59 schrieb Jim: >>> Hi, >>> >> ConTeXt doesn’t work with the synctex binary, but with >> mtxrun --script synctex > afaik there is no binary ... there is a library that has to be compiled into > a pdf viewer that intercept some 'goto the text file' command and then > launches an editor (afik the library has some heuristics build in wrt boxes > and nesting and so); at the tex end there is also a library that kicks in > addiional code for nodes and the backend (which is why enabling synctex will > have an impact on runtime) > wrt the synctex file, that one is generated by context (so we don't use the > synctex code in luatex and as luametatex has no backend there it's even > completely absent ... context generates the file itself which is also a bit > more efficient) >> Unfortunately, it’s not a drop-in replacement, so it doesn’t work with >> most editors. (I was thinking about a translating wrapper script, but >> didn’t do anything yet.) >> AFAIK TeXshop (MacOS) is the only TeX editor that supports ConTeXt’s >> workflow. > indeed texshop uses the approach that avoids the library and just calls > mtxrun to figure out the file/line that relates to the position; this is > more reliable because there is no need to re
[NTG-context] Re: ConTeXt support for Nova text editor (MacOS)
On 11/11/2023 11:43 PM, Paul Mazaitis wrote: On 11 Nov 2023, at 14:52, Aditya Mahajan wrote: Last time I checked tree-sitter on neovim, there were no good tree-sitters for context. I'd be interested in testing this out. Happy to have feedback! Does the parser detect nested metapost and luatex environments? The parser recognizes chunks of metapost and latex code and marks them in the syntax tree, but does nothing else: I figured the best approach here was to let applications call out to various tree-sitter parsers as needed. I don't know of a tree-sitter parser for either metapost or latex. The next one I am going to try to build a parser for is metapost (following the reference material in the back of the manual) but I haven't sat down to that task yet. (Plus, that one's going to need a _lot_ of testing by people other than I; I only use metapost for very simple things, and my understanding is surface level at best.) i don't know what a tree sitter is (probably a bird) but wasn't vim using lua ... if so, context ships with parsers for whatever it needs that one can look at also, when context gets updated there are also updated lua files in: context\data\scite\context\lexers\data\* that can be used for highlighting categories of commands, enviromnents etc Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: context not producing synctex output that my synctex program can use
On 11/12/2023 10:26 AM, Henning Hraban Ramm wrote: Am 12.11.23 um 00:59 schrieb Jim: Hi, I've read the wiki, looked at workflows-synctex.tex, searched the web, and scratched my head, all to no avail. So here I am, cap in hand... When I run context, I get a .synctex file which has some information in it, but I can't find any invocation of synctex to return anything useful. Nor does the okular example in the wiki (https://wiki.contextgarden.net/SyncTeX) work for me. Ocular starts, but always on the first page, regardless of what line number I give it. On the other hand, pdftex creates a .synctex file which my copy of synctex find useful. I am using the synctex from the current version of texlive: This is SyncTeX command line utility, version 1.5 Can anyone either (a) enlighten me on what I am doing wrong; or (b) definitively confirm that context is not currently playing nicely with synctex (the wiki notwithstanding) and I should give up this quest for now. ConTeXt doesn’t work with the synctex binary, but with mtxrun --script synctex afaik there is no binary ... there is a library that has to be compiled into a pdf viewer that intercept some 'goto the text file' command and then launches an editor (afik the library has some heuristics build in wrt boxes and nesting and so); at the tex end there is also a library that kicks in addiional code for nodes and the backend (which is why enabling synctex will have an impact on runtime) wrt the synctex file, that one is generated by context (so we don't use the synctex code in luatex and as luametatex has no backend there it's even completely absent ... context generates the file itself which is also a bit more efficient) Unfortunately, it’s not a drop-in replacement, so it doesn’t work with most editors. (I was thinking about a translating wrapper script, but didn’t do anything yet.) AFAIK TeXshop (MacOS) is the only TeX editor that supports ConTeXt’s workflow. indeed texshop uses the approach that avoids the library and just calls mtxrun to figure out the file/line that relates to the position; this is more reliable because there is no need to recompile a viewer when synctex updates you can run mtxrun --script synctex on the synctex file and check what areas are there ConTeXt’s synctex format is much simpler than the “standard” LaTeX one and should be at least as good, but alas it needs support from the editors. simpler in the sense that we only output what is needed for the synchronization to work reliable; fwiw, my collegue already for many years uses context with synctex enabled with sumatra pdf in pretty complex setups: a mix of tex and xml files with deeply nested inputs and it works ok (so we also get to the right spot in an (included) xml file) for synctex to work one has to call context with --synctex or put a directive on the topline of the file. Otherwise you won't get the right jobname. Of course it then still depends on the pdf viewer + lib used if things work out as expected. there isn't much we can do about the viewer part unless tit is not locked into the binary but as flexible like the texshop viewer is Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: ConTeXt support for Nova text editor (MacOS)
On 11 Nov 2023, at 14:52, Aditya Mahajan wrote: > Last time I checked tree-sitter on neovim, there were no good tree-sitters > for context. I'd be interested in testing this out. Happy to have feedback! > Does the parser detect nested metapost and luatex environments? The parser recognizes chunks of metapost and latex code and marks them in the syntax tree, but does nothing else: I figured the best approach here was to let applications call out to various tree-sitter parsers as needed. I don't know of a tree-sitter parser for either metapost or latex. The next one I am going to try to build a parser for is metapost (following the reference material in the back of the manual) but I haven't sat down to that task yet. (Plus, that one's going to need a _lot_ of testing by people other than I; I only use metapost for very simple things, and my understanding is surface level at best.) > Aditya -Paul ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: ConTeXt support for Nova text editor (MacOS)
On Sat, 11 Nov 2023, Paul Mazaitis wrote: I don't use MacOS, but ... > (As an aside, this extension uses an updated version of the ConTeXt > tree-sitter parser [https://github.com/pmazaitis/tree-sitter-context] that > can now recognize (most) environments and use them to parse out the document > hierarchy.) Last time I checked tree-sitter on neovim, there were no good tree-sitters for context. I'd be interested in testing this out. Does the parser detect nested metapost and luatex environments? Aditya ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] command to process CSV file (database module)
Dear list,
These are the following first four lines of a CSV file:
,,
"About \LuaTeX\ and
\ConTeXt","about.pdf","https://www.pragma-ade.com/general/manuals/about.pdf;
"l2r, r2l: A Few
Tips","bidi.pdf","https://www.pragma-ade.com/general/manuals/bidi.pdf;
"Flowcharts","charts-mkiv.pdf",
Faking a command such as \cA, \cB and \cC (for contents of columns A, B
or C) I would like to create a source document with an enumeration that
contains:
\doiftext{\cB}
{\item {\em\cA}\attachment[file=\cB]%
\doiftext{\cC}{ (also available at \cC)}.}
I would like to do that with the "database" module.
So far I have adapted the itemize environment, but I don't get the
contents for items right:
\usemodule[database]
\starttext
\def\ItemContents#1#2#3{\doiftext{#2}
{\item {\em #1}\attachment[file=#2]%
\doiftext{#3}{ (also available at #3)}.}}
\defineseparatedlist
[test]
[separator={,}, % tab
quotechar={"}, % tab
before={\startitemize[n]},after={\stopitemize},
first={\ItemContents},last={.},
left={\{},right={\}}]
\processdatabasefile[test][context-documents.csv]
\stoptext
I get an error about an unexpected symbol near "\" in the line of
"\processdatabasefile".
Could anyone enlighten me about what I am missing here?
Many thanks for your help,
Pablo
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: Combining python and lua
Hi,
Thanks for your inputs Aditya and Bruce.
I’m still having some issues when trying to include the output of the filter
module within lua.
MNWE:
\defineexternalfilter
[sympy]
[filtercommand={/Users/aleks/miniconda3/bin/python3
\externalfilterinputfile\space > \externalfilteroutputfile},
bufferbefore=init,
output={\externalfilterbasefile.out},
readcommand=\typefile,
read=no,]
\startbuffer[init]
from sympy import *
\stopbuffer
\starttext
\startluacode
local deg2rad = [[
%\startsympy
print(latex(rad(%angleVal%)))
%\stopsympy
]]
local calcTrigFunction = [[
\startsympy
from sympy import *
print(latex(%fname%(rad(%angleVal%
\stopsympy
]]
local angleList = {0, 30, 45, 60, 90, 120, 135, 150, 180, 210, 225,
240, 270, 300, 315, 330, 360}
for _, a in ipairs(angleList) do
context.templates[calcTrigFunction] {
fname = "sin",
angleVal = a
}
end
\stopluacode
\stoptext
In particular, it fails as soon as \startsympy and \stopsympy are part of the
template. Should I protect these?
A. Christe
Le 25 oct. 2023 à 21:56 +0200, Aditya Mahajan , a écrit :
> On Wed, 25 Oct 2023, Alexandre Christe wrote:
>
> > Dear list,
> >
> > I’d like to know the best approach to make this a bit more usable. I’m
> > trying to typeset a table with sin/cos/tan values. I’d like to be able to
> > convert the angles in degrees into radians (with math notation) and to
> > compute the trigonometric function leading to sin(pi/4) = 1/2, or cos(pi/6)
> > = sqrt(3)/2 and display it in math mode.
> >
> > Here’s my current MWE, where I fail to convert the angles in radians
>
> there is math.sind, cosd, etc. for computing sin for angle in degrees. The
> implementation is l-math.lua is:
>
> local pipi = 2*math.pi/360
>
> function math.sind(d) return sin(d*pipi) end
> function math.cosd(d) return cos(d*pipi) end
> function math.tand(d) return tan(d*pipi) end
>
> > and fail to display the result in symbolic form.
>
> Context doesn't do symbolic math. You can try checking if one of the symbolic
> math libraries in lua provides all the features that you want.
>
> > One possible way would be to use Python and the t-filter module, like this
>
> This can work as follows. Take the array of angles, and convert them to the
> desired format in python and write them to a temp file. Read that temp file
> in lua and typeset it as you want.
>
> Another option is an old proof of concept by Luigi:
> https://github.com/bastibe/lunatic-python which allowed two-way communication
> between python and luatex. Not sure if it still works.
>
> Aditya
>
> ___
> If your question is of interest to others as well, please add an entry to the
> Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
> archive : https://github.com/contextgarden/context
> wiki : https://wiki.contextgarden.net
> ___
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___
[NTG-context] Re: Combining python and lua
On Wed, 25 Oct 2023, Alexandre Christe wrote: > Dear list, > > I’d like to know the best approach to make this a bit more usable. I’m trying > to typeset a table with sin/cos/tan values. I’d like to be able to convert > the angles in degrees into radians (with math notation) and to compute the > trigonometric function leading to sin(pi/4) = 1/2, or cos(pi/6) = sqrt(3)/2 > and display it in math mode. > > Here’s my current MWE, where I fail to convert the angles in radians there is math.sind, cosd, etc. for computing sin for angle in degrees. The implementation is l-math.lua is: local pipi = 2*math.pi/360 function math.sind(d) return sin(d*pipi) end function math.cosd(d) return cos(d*pipi) end function math.tand(d) return tan(d*pipi) end > and fail to display the result in symbolic form. Context doesn't do symbolic math. You can try checking if one of the symbolic math libraries in lua provides all the features that you want. > One possible way would be to use Python and the t-filter module, like this This can work as follows. Take the array of angles, and convert them to the desired format in python and write them to a temp file. Read that temp file in lua and typeset it as you want. Another option is an old proof of concept by Luigi: https://github.com/bastibe/lunatic-python which allowed two-way communication between python and luatex. Not sure if it still works. Aditya ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror) archive : https://github.com/contextgarden/context wiki : https://wiki.contextgarden.net ___
[NTG-context] Re: \underbar in head
So clearly I would need to upgrade my version. It does not work with what I have at the moment. Thank you. Julian On 22/9/23 02:04, Wolfgang Schuster wrote: I get a line below the chapter title with LMTX and LuaTeX with the current ConTeXt version. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Re: \underbar in head
jbf schrieb am 21.09.2023 um 07:01:
However, Wolfgang, if I do, e.g.
\setuphead[chapter][textcommand={\setbar[underbar]}]
\starttext
\startchapter[title={My title}]
\input ward
\stopchapter
\stoptext
Then I do not get My Title with underline, which is what I want, and nor
is anything else underlined in 'Ward'.
I get a line below the chapter title with LMTX and LuaTeX with the
current ConTeXt version.
begin example
\setuphead
[chapter]
[textcommand={\setbar[underbar]}]
\starttext
\startchapter[title={My title}]
\input ward
\stopchapter
\stoptext
end example
The line is limited to the title because the textcommand key is used to
set \underbar, when you want a line below the whole chapter content you
can use the insidesection and aftersection keys.
begin example
\setuphead
[chapter]
[insidesection={\startbar[underbar]},
aftersection={\stopbar}]
\starttext
\startchapter[title={My title}]
\input ward
\stopchapter
\stoptext
end example
Wolfgang
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] Re: tiffs: autoconversion via graphicsmagick produces invalid pdfs
Ok, I've found a solution.
%
\enabletrackers[graphics.conversion]
\startluacode
local function convert(oldname, newname)
os.execute(string.format(
'gm convert "%s" "%s"', oldname, newname)
)
end
-- Set the PDF, JPEG and default TIFF converters to the above function.
figures.converters.tif.pdf = convert
figures.converters.tif.jpg = convert
figures.converters.tif.default = convert
\stopluacode
\setfigureconversion[tif][jpg] % has no effect
\starttext
\externalfigure[test.tif][conversion=jpg]
\stoptext
%%%
Would it make sense to add
tifconverter.pdf = converter
to grph-con.lua (line 293) ?
Why is it that \setfigureconversion has no effect? Without conversion=jpg on
\externalfigure, ConTeXt insists on converting to PDF. (I couldn't find the
command in the sources, but I'm not getting a undef'ed cs error either, so it
must be defined somewhere...)
I've also found out I can use a custom command that calls \externalfigure with
the right settings depending on the filetype:
%%%
\enabletrackers[graphics.conversion]
\startluacode
local function convert(oldname, newname)
os.execute(string.format(
'gm convert "%s" "%s"', oldname, newname)
)
end
-- Set the PDF and default TIFF converters to the above function.
figures.converters.tif.pdf = convert
figures.converters.tif.jpg = convert
figures.converters.tif.default = convert
\stopluacode
\setfigureconversion[tif][jpg] % has no effect
\defineexternalfigure[tif][conversion=jpg]
\starttexdefinition includegraphics #1
\splitfilename{#1}
\processaction[\splitofftype][
tif=>{\externalfigure[#1][tif]},
default=>{\externalfigure[#1]},
unknown=>{\externalfigure[#1]}
]
\stoptexdefinition
\starttext
\includegraphics{test.tif} % will be converted to jpg
\externalfigure[test.tif] % will be converted to pdf
\stoptext
But I think it would be nicer to stick to the default \externalfigure.
Best,
Denis
Von: denis.ma...@unibe.ch
Gesendet: Dienstag, 12. September 2023 17:09
An: ntg-context@ntg.nl
Betreff: [NTG-context] Re: tiffs: autoconversion via graphicsmagick produces
invalid pdfs
Sorry, that was too quick...
Hi,
currently, ConTeXt can't use tiffs directly, but it uses Graphicsmagick to
convert tiffs to pdf on the fly. However, as it seems, graphicsmagick is
producing invalid pdfs.
For every included tiff I have something like this in the log:
luatex warning > pdfe: invalid 11 0 R object at offset 573751
luatex warning > pdfe: invalid 11 0 R object at offset 629127
The offsets are different, but it's always this .
This bug has been known for quite some time, but it apparently hasn't been
fixed yet: https://sourceforge.net/p/graphicsmagick/bugs/513/
Converting the tiffs to jpeg circumvents the problem. Would it be an option to
convert tiffs to jpegs instead of to pdf? (Is that already possible?)
Best,
Denis
Von: denis.ma...@unibe.ch<mailto:denis.ma...@unibe.ch>
mailto:denis.ma...@unibe.ch>>
Gesendet: Dienstag, 12. September 2023 17:03
An: ntg-context@ntg.nl<mailto:ntg-context@ntg.nl>
Betreff: [NTG-context] tiffs: autoconversion via graphicsmagick produces
invalid pdfs
Hi,
currently, ConTeXt can't use tiffs directly, but it uses
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] Re: tiffs: autoconversion via graphicsmagick produces invalid pdfs
Sorry, that was too quick... Hi, currently, ConTeXt can't use tiffs directly, but it uses Graphicsmagick to convert tiffs to pdf on the fly. However, as it seems, graphicsmagick is producing invalid pdfs. For every included tiff I have something like this in the log: luatex warning > pdfe: invalid 11 0 R object at offset 573751 luatex warning > pdfe: invalid 11 0 R object at offset 629127 The offsets are different, but it's always this . This bug has been known for quite some time, but it apparently hasn't been fixed yet: https://sourceforge.net/p/graphicsmagick/bugs/513/ Converting the tiffs to jpeg circumvents the problem. Would it be an option to convert tiffs to jpegs instead of to pdf? (Is that already possible?) Best, Denis Von: denis.ma...@unibe.ch Gesendet: Dienstag, 12. September 2023 17:03 An: ntg-context@ntg.nl Betreff: [NTG-context] tiffs: autoconversion via graphicsmagick produces invalid pdfs Hi, currently, ConTeXt can't use tiffs directly, but it uses ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Re: TOC with sections titles and page numbers like a paragraph beneath chapter
That's kind of you Max, and I will definitely take a look at that, both for the current book I am working on, but also for the variations it can offer for other titles. In the meantime, Wolfgang gently reminded me that I had overlooked one various obvious (and simple) approach using alternative=d, which I confess I had entirely overlooked! Julian On 5/9/23 08:43, Max Chernoff wrote: Hi Julian, I am attempting to get a TOC that looks like the following (in other words with section titles and their relative page numbers in a block below the chapter): Has anyone put together a TOC of this kind and might be able to give me a hint to follow? This is fairly close to what you're looking for I think (the manual, not the package itself): http://mirrors.ctan.org/macros/luatex/generic/lua-widow-control/lua-widow-control.pdf The source is a little messy, but I've used it in a bunch of other documents and it seems fairly robust: https://github.com/gucci-on-fleek/lua-widow-control/blob/7c4544/docs/manual/lwc-manual.mkxl#L167-L234 There aren't any page numbers for the subsections in that, but you should be able to add those inside the definition of \SubsectionTOCcommand with either #3 or \currentlistentrypagenumber. Thanks, -- Max ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___ ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Re: TOC with sections titles and page numbers like a paragraph beneath chapter
Hi Julian, > I am attempting to get a TOC that looks like the following (in other > words with section titles and their relative page numbers in a block > below the chapter): > Has > anyone put together a TOC of this kind and might be able to give me a > hint to follow? This is fairly close to what you're looking for I think (the manual, not the package itself): http://mirrors.ctan.org/macros/luatex/generic/lua-widow-control/lua-widow-control.pdf The source is a little messy, but I've used it in a bunch of other documents and it seems fairly robust: https://github.com/gucci-on-fleek/lua-widow-control/blob/7c4544/docs/manual/lwc-manual.mkxl#L167-L234 There aren't any page numbers for the subsections in that, but you should be able to add those inside the definition of \SubsectionTOCcommand with either #3 or \currentlistentrypagenumber. Thanks, -- Max ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach
On Sun, Aug 20, 2023 at 06:41:42PM +0200, Hans Hagen wrote: > On 8/20/2023 5:51 PM, Carlos wrote: > > On Sun, Aug 20, 2023 at 03:38:15PM +0200, Wolfgang Schuster wrote: > > > Carlos schrieb am 19.08.2023 um 15:32: > > > > On Fri, Aug 18, 2023 at 08:58:58PM +0200, Wolfgang Schuster wrote: > > > > > Hi, > > > > > > > > > > 1. Learn to two provide a working minimal example which shows the > > > > > problem. > > > > > > > > > Did the minimal example I provided earlier wasn't enough for you? > > > > > > > > Besides, You know perfectly well that \stoptext is not even necessary, > > > > superflous; it's not required to compile any context flavor file for > > > > ages now. > > > > > > > > So I suggest you to save those keystrokes for other tasks. Not those, > > > > petty petty betty. I know it's hard to teach an ol' dog new tricks, > > > > but… it's worth to try! right? > > > > > > Please explain why this example (which is a valid ConTeXt document) works > > > > Opening a group with \starttext makes no sense because there is nothing > > after \stoptext. > > > > The possibility to nest \starttext is necessary when you \startproduct etc. > > where components can be be documents on its own and this means > > \startcomponent includes \starttext in its > > definition. > > > > > begin example > > > \starttext > > > > > > \starttext > > > > > > \stoptext > > > > > > \stoptext > > > end example > > > > > > but this doesn't. > > > > > > begin example > > > \starttext > > > > > > \starttext > > > end example > > > > > > Wolfgang > > > > Take a look at the command line when you process a file and you should see > > something like this: > > > > As you can see the luatex engine processes the file cont-yes.mkiv and not > > your document which put as argument to context. Your document is just read > > by cont-yes.mkiv and at the end of the document ConTeXt inserts an extra > > \stoptext which is ignored when your document > > is valid (equal number of \starttext and \stoptext). > > The bonus \starttext is just there so that we can use \startTEXpage etc > without wrapper and a second bonus is that it catches sloppy coding and if a > user want to take a shortcut and save a handful of keystrokes it's fine for > me but support converges to zero (unless one pays top money for the > incovenience). There is only so much you can expect from volunteers. > I remember now I read it somewhere before. > > Wolfgang. I do appreciate your emphasis and your input on all of this. > > I do. I really do. But we can't go over this, over and over again. Do > > you know who said the above? Not me. You. Do you know whose remarks > > are those? Not mine. Yours. > > > > Replace cont-yes.mkiv with the newer equivalent. And you're right though. > > \starttext is not even needed most of the times. > Wolfgang tries to educate you ... starttext is the anchor for checking if a > bodyfont has been defined and if not it kicks in some default. > > Now with that said: > > When Wolfgang asks / tells something because there is nothing in context > that he doesn't know. And you can bet then he knowa more than you do about > the internals, objectives and implementation. So, let me put it a bit > stronger: if Wolfgang gives you an answer that you don't like, you should be > very careful in your answering because there is very little change that he's > wrong. To stress his position here: if he sends me a patch I can merge it in > without testing it which (believe me) is a rather unique positin. From this > you might conclude that I don't like your tone. It has nothing to do with liking/disliking a tone. A simple document does not require any \stoptext and I told Wolfgang about it. > > And with that out if the way: > > When Mikael wonders if there might be something with your installation you > should indeed sit down and wonder a bit if that could be the case because he > is a pretty good tester who had been around for quite a while. So you can be > sure that he tested it well and that he has a proper setup. Personally I'd > be worried if someone doubts my installation. it has nothing to do with the installation. Different installations have nothing to do with what the backend fails to do in the end. It's deceitful. And lying his ass off. At least that message from the log, that is.
[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach
On 8/20/2023 5:51 PM, Carlos wrote: On Sun, Aug 20, 2023 at 03:38:15PM +0200, Wolfgang Schuster wrote: Carlos schrieb am 19.08.2023 um 15:32: On Fri, Aug 18, 2023 at 08:58:58PM +0200, Wolfgang Schuster wrote: Hi, 1. Learn to two provide a working minimal example which shows the problem. Did the minimal example I provided earlier wasn't enough for you? Besides, You know perfectly well that \stoptext is not even necessary, superflous; it's not required to compile any context flavor file for ages now. So I suggest you to save those keystrokes for other tasks. Not those, petty petty betty. I know it's hard to teach an ol' dog new tricks, but… it's worth to try! right? Please explain why this example (which is a valid ConTeXt document) works Opening a group with \starttext makes no sense because there is nothing after \stoptext. The possibility to nest \starttext is necessary when you \startproduct etc. where components can be be documents on its own and this means \startcomponent includes \starttext in its definition. begin example \starttext \starttext \stoptext \stoptext end example but this doesn't. begin example \starttext \starttext end example Wolfgang Take a look at the command line when you process a file and you should see something like this: As you can see the luatex engine processes the file cont-yes.mkiv and not your document which put as argument to context. Your document is just read by cont-yes.mkiv and at the end of the document ConTeXt inserts an extra \stoptext which is ignored when your document is valid (equal number of \starttext and \stoptext). The bonus \starttext is just there so that we can use \startTEXpage etc without wrapper and a second bonus is that it catches sloppy coding and if a user want to take a shortcut and save a handful of keystrokes it's fine for me but support converges to zero (unless one pays top money for the incovenience). There is only so much you can expect from volunteers. Wolfgang. I do appreciate your emphasis and your input on all of this. I do. I really do. But we can't go over this, over and over again. Do you know who said the above? Not me. You. Do you know whose remarks are those? Not mine. Yours. Replace cont-yes.mkiv with the newer equivalent. And you're right though. \starttext is not even needed most of the times. Wolfgang tries to educate you ... starttext is the anchor for checking if a bodyfont has been defined and if not it kicks in some default. Now with that said: When Wolfgang asks / tells something because there is nothing in context that he doesn't know. And you can bet then he knowa more than you do about the internals, objectives and implementation. So, let me put it a bit stronger: if Wolfgang gives you an answer that you don't like, you should be very careful in your answering because there is very little change that he's wrong. To stress his position here: if he sends me a patch I can merge it in without testing it which (believe me) is a rather unique positin. From this you might conclude that I don't like your tone. And with that out if the way: When Mikael wonders if there might be something with your installation you should indeed sit down and wonder a bit if that could be the case because he is a pretty good tester who had been around for quite a while. So you can be sure that he tested it well and that he has a proper setup. Personally I'd be worried if someone doubts my installation. Did you install from the garden, using the lmtx installer? Because that is the reference. Everything installed otherwise is the users problem. Which brings me to this file read only thing you mention. If your font cache is not writable you migth end up with bad metrics indeed just because there are no font resources but that's not up to context to deal with. Also, \␣ is a fixed space and has no glue so i keep wondering what this brings to the picture, Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach
Carlos schrieb am 20.08.2023 um 17:51: On Sun, Aug 20, 2023 at 03:38:15PM +0200, Wolfgang Schuster wrote: Carlos schrieb am 19.08.2023 um 15:32: On Fri, Aug 18, 2023 at 08:58:58PM +0200, Wolfgang Schuster wrote: Hi, 1. Learn to two provide a working minimal example which shows the problem. Did the minimal example I provided earlier wasn't enough for you? Besides, You know perfectly well that \stoptext is not even necessary, superflous; it's not required to compile any context flavor file for ages now. So I suggest you to save those keystrokes for other tasks. Not those, petty petty betty. I know it's hard to teach an ol' dog new tricks, but… it's worth to try! right? Please explain why this example (which is a valid ConTeXt document) works Opening a group with \starttext makes no sense because there is nothing after \stoptext. The possibility to nest \starttext is necessary when you \startproduct etc. where components can be be documents on its own and this means \startcomponent includes \starttext in its definition. begin example \starttext \starttext \stoptext \stoptext end example but this doesn't. begin example \starttext \starttext end example Wolfgang Take a look at the command line when you process a file and you should see something like this: As you can see the luatex engine processes the file cont-yes.mkiv and not your document which put as argument to context. Your document is just read by cont-yes.mkiv and at the end of the document ConTeXt inserts an extra \stoptext which is ignored when your document is valid (equal number of \starttext and \stoptext). Wolfgang. I do appreciate your emphasis and your input on all of this. I do. I really do. But we can't go over this, over and over again. Do you know who said the above? Not me. You. Do you know whose remarks are those? Not mine. Yours. Just because ConTeXt fixes your mistake doesn't mean you should abuse it and *no* user should learn from your example. Each ConTeXt document should contain a starttext/stoptext pair or equivalent commands (e.g. startdocument/stopdocument or startproduct/stopproduct). Replace cont-yes.mkiv with the newer equivalent. And you're right though. \starttext is not even needed most of the times. And now it gets even worse, see https://meeting.contextgarden.net/2021/talks/2021-09-21/starttext.pdf why \starttext is necessary. Wolfgang ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach
On Sun, Aug 20, 2023 at 03:38:15PM +0200, Wolfgang Schuster wrote: > Carlos schrieb am 19.08.2023 um 15:32: > > On Fri, Aug 18, 2023 at 08:58:58PM +0200, Wolfgang Schuster wrote: > > > Hi, > > > > > > 1. Learn to two provide a working minimal example which shows the problem. > > > > > Did the minimal example I provided earlier wasn't enough for you? > > > > Besides, You know perfectly well that \stoptext is not even necessary, > > superflous; it's not required to compile any context flavor file for > > ages now. > > > > So I suggest you to save those keystrokes for other tasks. Not those, > > petty petty betty. I know it's hard to teach an ol' dog new tricks, > > but… it's worth to try! right? > > Please explain why this example (which is a valid ConTeXt document) works > Opening a group with \starttext makes no sense because there is nothing after \stoptext. The possibility to nest \starttext is necessary when you \startproduct etc. where components can be be documents on its own and this means \startcomponent includes \starttext in its definition. > begin example > \starttext > > \starttext > > \stoptext > > \stoptext > end example > > but this doesn't. > > begin example > \starttext > > \starttext > end example > > Wolfgang Take a look at the command line when you process a file and you should see something like this: As you can see the luatex engine processes the file cont-yes.mkiv and not your document which put as argument to context. Your document is just read by cont-yes.mkiv and at the end of the document ConTeXt inserts an extra \stoptext which is ignored when your document is valid (equal number of \starttext and \stoptext). Wolfgang. I do appreciate your emphasis and your input on all of this. I do. I really do. But we can't go over this, over and over again. Do you know who said the above? Not me. You. Do you know whose remarks are those? Not mine. Yours. Replace cont-yes.mkiv with the newer equivalent. And you're right though. \starttext is not even needed most of the times. > > ___ > If your question is of interest to others as well, please add an entry to the > Wiki! > > maillist : ntg-context@ntg.nl / > https://www.ntg.nl/mailman/listinfo/ntg-context > webpage : https://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : https://contextgarden.net > ___ -- Real Users never use the Help key. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach
On 8/18/2023 8:48 PM, Carlos wrote: And with luatex frozen for better or for worse, I better stick to plain tex not sure what frozen has to do with it ... it will be around and maintained forever but no fundamental new functionality will be added that said: luametatex is of not much use when you use plain (or whatever else) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach
; > > > «In theory, this seems like it ought to work; but in practice, it fails > > > in two ways. One > > > rather obvious failure—at least, it becomes obvious when the macro is > > > tested—is that > > > all the empty lines of the file are omitted. The reason is that the \par > > > command at the > > > end of an empty line doesn’t start up a new paragraph, because it occurs > > > in vertical > > > mode. The other failure is not as obvious, because it occurs much less > > > often: The \tt > > > fonts contain ligatures for Spanish punctuation, so the sequences ?‘ and > > > !‘ will be > > > printed as ¿ and ¡ respectively. Both of these defects can be cured by > > > inserting > > > > > > and > > > > > > > > > «When INITEX creates a brand new TEX, all characters have a space factor > > > code > > > of 1000, except that the uppercase letters ‘A’ through ‘Z’ have code 999. > > > (This > > > slight difference is what makes punctuation act differently after an > > > uppercase letter; do > > > you see why?) Plain TEX redefines a few of these codes using the \sfcode > > > primitive, > > > which is similar to \catcode (see Appendix B); for example, the > > > instructions > > > \sfcode‘)=0 > > > \sfcode‘.=3000 > > > make right parentheses “transparent” to the space factor, while tripling > > > the stretcha- > > > bility after periods. The \frenchspacing operation resets \sfcode‘. to > > > 1000.» > > > > Everything you cite above is very likely true for plain TeX, but maybe > > not for ConTeXt... > > > > /Mikael > > > > PS I do not think that your emails come out well. In order to get > > help, I would suggest a strategy that not so much only sounds as > > nagging and complaints. One thing that has been lacking is a clear > > explanation of what you really try to achieve. > > Mikael, I'll surely heed your advice with that strategy. It's almost > impossible to have a decent looking pdf with lmtx > > kerning of a simple word sequence is off, along with spurious spaces > interjected between sentences. What gives? > > And with luatex frozen for better or for worse, I better stick to plain > tex > > -- > Thus spake the master programmer: > "After three days without programming, life becomes meaningless." > -- Geoffrey James, "The Tao of Programming" > > ___ > If your question is of interest to others as well, please add an entry to the > Wiki! > > maillist : ntg-context@ntg.nl / > https://www.ntg.nl/mailman/listinfo/ntg-context > webpage : https://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : https://contextgarden.net > ___ -- They are relatively good but absolutely terrible. -- Alan Kay, commenting on Apollos ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Re: redefine space to be the same as \␣ similar to knuthian approach
o the sequences ?‘ and !‘ > > will be > > printed as ¿ and ¡ respectively. Both of these defects can be cured by > > inserting > > > > and > > > > > > «When INITEX creates a brand new TEX, all characters have a space factor > > code > > of 1000, except that the uppercase letters ‘A’ through ‘Z’ have code 999. > > (This > > slight difference is what makes punctuation act differently after an > > uppercase letter; do > > you see why?) Plain TEX redefines a few of these codes using the \sfcode > > primitive, > > which is similar to \catcode (see Appendix B); for example, the instructions > > \sfcode‘)=0 > > \sfcode‘.=3000 > > make right parentheses “transparent” to the space factor, while tripling > > the stretcha- > > bility after periods. The \frenchspacing operation resets \sfcode‘. to > > 1000.» > > Everything you cite above is very likely true for plain TeX, but maybe > not for ConTeXt... > > /Mikael > > PS I do not think that your emails come out well. In order to get > help, I would suggest a strategy that not so much only sounds as > nagging and complaints. One thing that has been lacking is a clear > explanation of what you really try to achieve. Mikael, I'll surely heed your advice with that strategy. It's almost impossible to have a decent looking pdf with lmtx kerning of a simple word sequence is off, along with spurious spaces interjected between sentences. What gives? And with luatex frozen for better or for worse, I better stick to plain tex -- Thus spake the master programmer: "After three days without programming, life becomes meaningless." -- Geoffrey James, "The Tao of Programming" ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Re: startitemize[a, text] space in LMTX
On 8/16/2023 9:27 PM, Xavier B. wrote: OK. Thanks but it's about luatex [https://tracker.luatex.org/changelog_page.php]. Does we use luametatex? lmtx uses luametatex ... luatex dev is basically frozen (has to be stable because used by several macro packages now) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Re: startitemize[a, text] space in LMTX
OK. Thanks but it's about luatex [https://tracker.luatex.org/changelog_page.php]. Does we use luametatex? On Wed, 16 Aug 2023 21:07:47 +0200 Wolfgang Schuster ha escrit: > Xavier B. schrieb am 16.08.2023 um 20:38: > > Thanks. > > Anyway do ypu have public triaging bugs system for LMTX and ConTeXt? > > There is https://tracker.luatex.org/my_view_page.php but the normal way > is to report bugs on the mailing list. > > Wolfgang > ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Re: Why overbar is so big
Hi,
On Sun, Aug 13, 2023 at 9:13 AM Xavier B. wrote:
>
> So,
>
> Finally is it a bug in MKIV? It seems you fix some kind of bug in your
> messages. Is it true?
>
> > The output with Luametatex is correct but Luatex creates a raised bar
> > (and different linebreaking).
> >
> > \showglyphs
> >
> > \startTEXpage[offset=1ex]
> > \ruledhbox{$\overline{OA} = \overbar {OA} = 4.2$}
> > \par
> > \ruledhbox{$\underline {OA} = \underbar {OA} = 4.2$}
> > \par
> > \ruledhbox{$\widetilde {OA} = \widebar {OA} = 4.2$}
> > \par
> > \ruledhbox{$\overbracket {OA} = \underbracket {OA} = 4.2$}
> > \stopTEXpage
> >
> > I'll add a 'force fix in spite of extensible being present' in mkiv. In
> > lmtx we always fix also because we drop in nicer shapes (watch the round
> > tips in lm and fancy tips in antykwa) and concluded that fonts will
> > remain as they are.
> >
> > Hans
>
> As you suggested, I will give a try to LMTX but be aware most user still use
> MKIV until most distros upgrade the texlive version of context to LMTX.
>
> Regards,
> Xavier
One can also try to instead use the accent mechanism instead of a stacker:
% engine=luatex
\definemathtopaccent[widebar] ["0305]
\startTEXpage[offset=3pt]
$\overbar{OA}$
$\widebar{OA}$
\stopTEXpage
The \widebar is defined (almost) like that in lmtx.
/Mikael
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] Re: Why overbar is so big
On 8/13/2023 9:08 AM, Xavier B. wrote:
So,
Finally is it a bug in MKIV? It seems you fix some kind of bug in your
messages. Is it true?
Not really. It's a a bug in the fonts (that will stay if only for
compaibility reasons). There is a catch in mkiv that compensates for it
but only when characters are not there. So, for these two I now force
the catch.
In lmtx we have a bit different approach: we just assuem they are wrong
in all fonts and fix them or replace them. We also have a more advanced
math engine so we can control placement better.
There are also 'font parameters' involved that can be bad (i guess that
designers can't really test math font parameters). In lmtx we have more
of them, beyond what opentype math provides.
All of this is handled in goodie files. That mechanism is present in
mkiv but no one ever bothered to spent time on it. That said: the last
two years Mikeal and I spent a *lot* of time on math and we don't really
look back at mkiv / mkii also because there is way more neat things now
(most probably go unnoticed) ... you can read about it in some documents
that come with context, articles in tugboat, and there are talks by
Mikael at tug meetings on YT.
The output with Luametatex is correct but Luatex creates a raised bar
(and different linebreaking).
\showglyphs
\startTEXpage[offset=1ex]
\ruledhbox{$\overline{OA} = \overbar {OA} = 4.2$}
\par
\ruledhbox{$\underline {OA} = \underbar {OA} = 4.2$}
\par
\ruledhbox{$\widetilde {OA} = \widebar {OA} = 4.2$}
\par
\ruledhbox{$\overbracket {OA} = \underbracket {OA} = 4.2$}
\stopTEXpage
I'll add a 'force fix in spite of extensible being present' in mkiv. In
lmtx we always fix also because we drop in nicer shapes (watch the round
tips in lm and fancy tips in antykwa) and concluded that fonts will
remain as they are.
Hans
As you suggested, I will give a try to LMTX but be aware most user still use
MKIV until most distros upgrade the texlive version of context to LMTX.
It's not that hard to install lmtx alongside. If distributions take from
texlive then likely you also end up with files that are not needed (base
package) and lack some fonts (esp math) by default. You'd also benefit
from the last couple of years advancements. Keep in mind that for a long
term tex (document) project a snapshot approach is healthy because you
never know what a distribution adds / replaces (esp fonts can be a mess
and you want to know what you use).
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] Re: Why overbar is so big
So,
Finally is it a bug in MKIV? It seems you fix some kind of bug in your
messages. Is it true?
> The output with Luametatex is correct but Luatex creates a raised bar
> (and different linebreaking).
>
> \showglyphs
>
> \startTEXpage[offset=1ex]
> \ruledhbox{$\overline{OA} = \overbar {OA} = 4.2$}
> \par
> \ruledhbox{$\underline {OA} = \underbar {OA} = 4.2$}
> \par
> \ruledhbox{$\widetilde {OA} = \widebar {OA} = 4.2$}
> \par
> \ruledhbox{$\overbracket {OA} = \underbracket {OA} = 4.2$}
> \stopTEXpage
>
> I'll add a 'force fix in spite of extensible being present' in mkiv. In
> lmtx we always fix also because we drop in nicer shapes (watch the round
> tips in lm and fancy tips in antykwa) and concluded that fonts will
> remain as they are.
>
> Hans
As you suggested, I will give a try to LMTX but be aware most user still use
MKIV until most distros upgrade the texlive version of context to LMTX.
Regards,
Xavier
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] Re: Why overbar is so big
On 8/12/2023 11:46 AM, Wolfgang Schuster wrote:
Hans Hagen via ntg-context schrieb am 12.08.2023 um 11:13:
On 8/12/2023 10:10 AM, Xavier B. wrote:
The font is the default:
\setupbodyfont [modern, 12pt] % modern o cmr, 11pt
I use Linux (arch derivative).
Looks ok here (see atached). Does the modern-math.lfg file have:
AccentTopShiftUp = -60,
FlattenedAccentTopShiftUp = -60,
I assume it has the same lm math font as we use.
Do you test with Luatex?
Only when asked.
The output with Luametatex is correct but Luatex creates a raised bar
(and different linebreaking).
\showglyphs
\startTEXpage[offset=1ex]
\ruledhbox{$\overline{OA} = \overbar {OA} = 4.2$}
\par
\ruledhbox{$\underline {OA} = \underbar {OA} = 4.2$}
\par
\ruledhbox{$\widetilde {OA} = \widebar {OA} = 4.2$}
\par
\ruledhbox{$\overbracket {OA} = \underbracket {OA} = 4.2$}
\stopTEXpage
I'll add a 'force fix in spite of extensible being present' in mkiv. In
lmtx we always fix also because we drop in nicer shapes (watch the round
tips in lm and fancy tips in antykwa) and concluded that fonts will
remain as they are.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] Re: Why overbar is so big
Hans Hagen via ntg-context schrieb am 12.08.2023 um 11:13: On 8/12/2023 10:10 AM, Xavier B. wrote: The font is the default: \setupbodyfont [modern, 12pt] % modern o cmr, 11pt I use Linux (arch derivative). Looks ok here (see atached). Does the modern-math.lfg file have: AccentTopShiftUp = -60, FlattenedAccentTopShiftUp = -60, I assume it has the same lm math font as we use. Do you test with Luatex? The output with Luametatex is correct but Luatex creates a raised bar (and different linebreaking). Wolfgang ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] Problems with luametatex and texlive on OpenBSD
Hi everyone, I'm finalising packaging TeX Live 2023 for OpenBSD and have an issue with context using the new luametatex engine. I'm getting various Lua errors when running `context --make`, like: node-ini.lmt:54: attempt to call a nil value (local 'getvalues') and: node-nut.lmt:22: attempt to index a nil value (local 'nodecodes') (full log below) As far as I can see, I've set up the system in the same way as the other downstream packagers have (according to https://github.com/contextgarden/luametatex/issues/1 and https://wiki.contextgarden.net/Building_LuaMetaTeX_for_TeX_Live): - make symlinks * /usr/local/bin/context.lua -> ../share/texmf-dist/scripts/context/lua/context.lua * /usr/local/bin/mtx-context.lua -> ../share/texmf-dist/scripts/context/lua/mtx-context.lua * /usr/local/bin/mtxrun.lua -> ../share/texmf-dist/scripts/context/lua/mtxrun.lua * /usr/local/bin/context -> luametatex * /usr/local/bin/mtxrun -> luametatex - patch resolvers * https://github.com/jasperla/openbsd-wip/blob/master/print/texlive/texmf/patches/patch-texmf-dist_scripts_context_lua_mtxrun_lua * https://github.com/jasperla/openbsd-wip/blob/master/print/texlive/texmf/patches/patch-texmf-dist_tex_context_base_mkiv_data-res_lua * https://github.com/jasperla/openbsd-wip/blob/master/print/texlive/texmf/patches/patch-texmf-dist_web2c_texmf_cnf In OpenBSD, we install the trees in /usr/local/share/texmf* (a hangover from teTeX), so in these patches, TRUEPREFIX resolves to /usr/local. This does mean selfauto doesn't work, but in the past I've always just patched in absolute paths and it's been fine. Does anyone know what may cause these errors? I've prodded around inside the lua and luametatex sources, but I don't really know what's going on. I tend to agree with Lua that the variables in question are not defined, so using them causes a `nil` to appear which can't be indexed or called. Something else must be expected to set up the undefined variables somewhere... Any help would be greatly appreciated. Full output of `context --make`: ``` resolvers | resolving | configuration files already identified resolvers | resolving | loading configuration file '/usr/local/share/texmf-dist/web2c/texmfcnf.lua' resolvers | resolving | resolvers | resolving | locating list of 'home:.texlive2023/texmf-config' (runtime) (tree:///home:.texlive2023/texmf-config) resolvers | methods | resolving, method 'locators', how 'uri', handler 'tree', argument 'tree:///home:.texlive2023/texmf-config' resolvers | trees | locator 'home:.texlive2023/texmf-config' not found resolvers | resolving | locating list of 'home:texmf' (runtime) (tree:///home:texmf) resolvers | methods | resolving, method 'locators', how 'uri', handler 'tree', argument 'tree:///home:texmf' resolvers | trees | locator 'home:texmf' not found resolvers | resolving | locating list of '/usr/local/share/texmf-config' (cached) resolvers | methods | resolving, method 'locators', how 'uri', handler 'file', argument '/usr/local/share/texmf-config' resolvers | files | file locator '/usr/local/share/texmf-config' not found resolvers | resolving | locating list of '/usr/local/share/texmf-var' (cached) resolvers | methods | resolving, method 'locators', how 'uri', handler 'file', argument '/usr/local/share/texmf-var' resolvers | files | file locator '/usr/local/share/texmf-var' found as '/usr/local/share/texmf-var' resolvers | resolving | locating list of '/usr/local/share/texmf-project' (cached) resolvers | methods | resolving, method 'locators', how 'uri', handler 'file', argument '/usr/local/share/texmf-project' resolvers | files | file locator '/usr/local/share/texmf-project' not found resolvers | resolving | locating list of '/usr/local/share/texmf-fonts' (cached) resolvers | methods | resolving, method 'locators', how 'uri', handler 'file', argument '/usr/local/share/texmf-fonts' resolvers | files | file locator '/usr/local/share/texmf-fonts' not found resolvers | resolving | locating list of '/usr/local/share/texmf-local' (cached) resolvers | methods | resolving, method 'locators', how 'uri', handler 'file', argument '/usr/local/share/texmf-local' resolvers | files | file locator '/usr/local/share/texmf-local' found as '/usr/local/share/texmf-local' resolvers | resolving | locating list of '/usr/local/share/texmf-dist' (cached) resolvers | methods | resolving, method 'locators', how 'uri', handler 'file', argument '/usr/local/share/texmf-dist' resolvers | files | file locator '/usr/local/share/texmf-dist' found as '/usr/local/share/texmf-dist' resolvers | resolving | resolvers | methods | resolving, method 'generators', how 'uri', handler 'file', argument '/usr/local/share/texmf-var' resolvers | expansions | scanning path '/usr/local/share/texmf-var', branch
[NTG-context] Re: What are these warnings/errors?
> On 18 Jul 2023, at 21:49, Hans Hagen wrote:
>
> On 7/18/2023 9:37 PM, Gerben Wierda wrote:
>> I have a document that includes text and PDFs (which themselves have been
>> created with LMTX)
>> When it is compiled I see:
>> fonts > latin modern fonts are not preloaded
>> languages > language 'en' is active
>> open source > level 1, order 2, name './ArchiMate-sheets.tex'
>> fonts > preloading modern (math)
>> fonts > 'fallback modern mm 12pt' is loaded
>> fonts > preloading modern (mono)
>> fonts > 'fallback modern tt 12pt' is loaded
>> luatex warning > pdfe lib: lua expected
>> luatex warning > pdfe lib: lua expected
>> fonts > checking > char [ (U+0005B) in font '' with id 0: missing
>> fonts > checking > char t (U+00074) in font '' with id 0: missing
>> fonts > checking > char f (U+00066) in font '' with id 0: missing
>> fonts > checking > char = (U+0003D) in font '' with id 0: missing
>> fonts > checking > char s (U+00073) in font '' with id 0: missing
>> fonts > checking > char y (U+00079) in font '' with id 0: missing
>> fonts > checking > char l (U+0006C) in font '' with id 0: missing
>> fonts > checking > char e (U+00065) in font '' with id 0: missing
>> fonts > checking > char : (U+0003A) in font '' with id 0: missing
>> fonts > checking > char R (U+00052) in font '' with id 0: missing
>> fonts > checking > char g (U+00067) in font '' with id 0: missing
>> fonts > checking > char u (U+00075) in font '' with id 0: missing
>> fonts > checking > char a (U+00061) in font '' with id 0: missing
>> fonts > checking > char r (U+00072) in font '' with id 0: missing
>> fonts > checking > char , (U+0002C) in font '' with id 0: missing
>> fonts > checking > char b (U+00062) in font '' with id 0: missing
>> fonts > checking > char B (U+00042) in font '' with id 0: missing
>> fonts > checking > char o (U+0006F) in font '' with id 0: missing
>> fonts > checking > char d (U+00064) in font '' with id 0: missing
>> fonts > checking > char i (U+00069) in font '' with id 0: missing
>> fonts > checking > char I (U+00049) in font '' with id 0: missing
>> fonts > checking > char c (U+00063) in font '' with id 0: missing
>> fonts > checking > char ] (U+0005D) in font '' with id 0: missing
>> backend > xmp > using file
>> '/usr/local/context-osx-64/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml'
>> pages > flushing realpage 1, userpage 1, subpage 1
>> luatex warning > pdfe lib: lua expected
>> luatex warning > pdfe lib: lua expected
>> luatex warning > pdfe lib: lua expected
>> luatex warning > pdfe lib: lua expected
>> I' can't really see anything wrong with the result, What are these
>> warnings/errors?
> you can read the text vertically:
>
> [tf=syle
>
> and when you get that it's likely that this is typeste before \starttext when
> no font has been loaded (you then probably get some unexpected whitespace on
> top of the first page
>
> so, just grep for that orphaned text snippet in your style / document
Hmm, it ('syle') is nowhere to be found in my documents. The 'syle' typo is
found twice in ConTeXt itself, but only in manuals.
Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>, Mastodon
<https://newsie.social/@gctwnl>)
R IT Strategy <https://ea.rna.nl/> (main site)
Book: Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/>
Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
[NTG-context] Re: What are these warnings/errors?
On 7/18/2023 9:37 PM, Gerben Wierda wrote: I have a document that includes text and PDFs (which themselves have been created with LMTX) When it is compiled I see: fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 1, order 2, name './ArchiMate-sheets.tex' fonts > preloading modern (math) fonts > 'fallback modern mm 12pt' is loaded fonts > preloading modern (mono) fonts > 'fallback modern tt 12pt' is loaded luatex warning > pdfe lib: lua expected luatex warning > pdfe lib: lua expected fonts > checking > char [ (U+0005B) in font '' with id 0: missing fonts > checking > char t (U+00074) in font '' with id 0: missing fonts > checking > char f (U+00066) in font '' with id 0: missing fonts > checking > char = (U+0003D) in font '' with id 0: missing fonts > checking > char s (U+00073) in font '' with id 0: missing fonts > checking > char y (U+00079) in font '' with id 0: missing fonts > checking > char l (U+0006C) in font '' with id 0: missing fonts > checking > char e (U+00065) in font '' with id 0: missing fonts > checking > char : (U+0003A) in font '' with id 0: missing fonts > checking > char R (U+00052) in font '' with id 0: missing fonts > checking > char g (U+00067) in font '' with id 0: missing fonts > checking > char u (U+00075) in font '' with id 0: missing fonts > checking > char a (U+00061) in font '' with id 0: missing fonts > checking > char r (U+00072) in font '' with id 0: missing fonts > checking > char , (U+0002C) in font '' with id 0: missing fonts > checking > char b (U+00062) in font '' with id 0: missing fonts > checking > char B (U+00042) in font '' with id 0: missing fonts > checking > char o (U+0006F) in font '' with id 0: missing fonts > checking > char d (U+00064) in font '' with id 0: missing fonts > checking > char i (U+00069) in font '' with id 0: missing fonts > checking > char I (U+00049) in font '' with id 0: missing fonts > checking > char c (U+00063) in font '' with id 0: missing fonts > checking > char ] (U+0005D) in font '' with id 0: missing backend > xmp > using file '/usr/local/context-osx-64/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml' pages > flushing realpage 1, userpage 1, subpage 1 luatex warning > pdfe lib: lua expected luatex warning > pdfe lib: lua expected luatex warning > pdfe lib: lua expected luatex warning > pdfe lib: lua expected I' can't really see anything wrong with the result, What are these warnings/errors? you can read the text vertically: [tf=syle and when you get that it's likely that this is typeste before \starttext when no font has been loaded (you then probably get some unexpected whitespace on top of the first page so, just grep for that orphaned text snippet in your style / document Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
[NTG-context] What are these warnings/errors?
I have a document that includes text and PDFs (which themselves have been created with LMTX) When it is compiled I see: fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 1, order 2, name './ArchiMate-sheets.tex' fonts > preloading modern (math) fonts > 'fallback modern mm 12pt' is loaded fonts > preloading modern (mono) fonts > 'fallback modern tt 12pt' is loaded luatex warning > pdfe lib: lua expected luatex warning > pdfe lib: lua expected fonts > checking > char [ (U+0005B) in font '' with id 0: missing fonts > checking > char t (U+00074) in font '' with id 0: missing fonts > checking > char f (U+00066) in font '' with id 0: missing fonts > checking > char = (U+0003D) in font '' with id 0: missing fonts > checking > char s (U+00073) in font '' with id 0: missing fonts > checking > char y (U+00079) in font '' with id 0: missing fonts > checking > char l (U+0006C) in font '' with id 0: missing fonts > checking > char e (U+00065) in font '' with id 0: missing fonts > checking > char : (U+0003A) in font '' with id 0: missing fonts > checking > char R (U+00052) in font '' with id 0: missing fonts > checking > char g (U+00067) in font '' with id 0: missing fonts > checking > char u (U+00075) in font '' with id 0: missing fonts > checking > char a (U+00061) in font '' with id 0: missing fonts > checking > char r (U+00072) in font '' with id 0: missing fonts > checking > char , (U+0002C) in font '' with id 0: missing fonts > checking > char b (U+00062) in font '' with id 0: missing fonts > checking > char B (U+00042) in font '' with id 0: missing fonts > checking > char o (U+0006F) in font '' with id 0: missing fonts > checking > char d (U+00064) in font '' with id 0: missing fonts > checking > char i (U+00069) in font '' with id 0: missing fonts > checking > char I (U+00049) in font '' with id 0: missing fonts > checking > char c (U+00063) in font '' with id 0: missing fonts > checking > char ] (U+0005D) in font '' with id 0: missing backend > xmp > using file '/usr/local/context-osx-64/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml' pages > flushing realpage 1, userpage 1, subpage 1 luatex warning > pdfe lib: lua expected luatex warning > pdfe lib: lua expected luatex warning > pdfe lib: lua expected luatex warning > pdfe lib: lua expected I' can't really see anything wrong with the result, What are these warnings/errors? Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>, Mastodon <https://newsie.social/@gctwnl>) R IT Strategy <https://ea.rna.nl/> (main site) Book: Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/> Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/> ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] Off topic: Does a 'free for commercial use' flared-sans font exist in the world?
On 6/18/2023 8:37 PM, Carlos via ntg-context wrote: On Sat, Jun 17, 2023 at 06:53:06PM +0200, Hans Hagen via ntg-context wrote: On 6/17/2023 2:06 AM, linguafalsa--- via ntg-context wrote: On Fri, Jun 16, 2023 at 06:35:49PM +0200, Gerben Wierda via ntg-context wrote: I know this is off topic, but I suspect this community is actually one of the best places to find an answer. It is the best community. And I tell you what. What happened is that all TeX engines have neglected fonts from the beginning. Really? When tex showed up digital font technology was pretty much in flux. And, with metafont being part of the tex ecosystem, one can argue that tex was quite innovative too. Ecosystem. I would be very careful by including an ecosystem there. Yes. Yes. The TeX ecosystem is obviously part of TeX but is not part of the ecosystem of fonts either. And what is done on ecosystems can either benefit or affect ecosystems greatly. And it's a known trait that humans have been known for having more of a flock group mentality for no apparent rationally-based reasons than just being themselves making these decisions/following instincts or whatever and not because of a particular ecosystem, or for the benefit of the latter. With ecosystemn I mean: tex, metafont, cmr fonts, all kind of tools ... evolving into more engines, more fonts, macro packages, distributions, user groups and use group journals, meetings etc And the above does not imply, bear with me here, that metafont was not innovative, but it can be argued that without TeX there is no metafont, so no room is left for errors either. So, yes, it must be innovative. It has to be. There had to be metafont because there was not much else that could provide what tex needed (at that time). Potscript and its fonts came aroudn at the same time and were rather closed technologies. But as soon possible backend drivers (also part of the tex ecosystem) kicked in. Then we got virtual fonts which enhanced tex's capabilities. I really like Optima, and what I really like about it is the 'flared style'. But I would like to move to a flared-sans font that gives me more licensing freedom. I haven't been able to find one after extensive searching. The only one who were reasonably priced (not free) were the URW Classico ones in Adobe Creative Cloud, but those can only be used in Adobe programs like InDesign (and not TeX). Licensing freedom is an oxymoron. There's no freedom in licensing. Only greed. The only extension engine that at one point had a plan in mind, or most of the bases covered in this regard was Omega. One needs morr than plans. Afaik omega was more about input processing and th efont part was mostly going beyond 8 bit fonts but i might have missed something (omega was never productin ready). Notwithstanding the intricacies/details of what may have actually happened with its short lifespan I think it's more than clear the lack of support behind it. I'm not going to delve into what exactly caused its demise or if it was simply the after effect of other projects that contributed to it. It's irrelevant. Hm, its time span was not that short ... I first heard of omega at the eurotex meeting in arnhem where also etex was discussed (and you dont'want me to cite things said there) .. in successive years there have been announcemnts etc. However, for an engine to be used it must work reliable and guiseppes 'aleph' was basically a variant of omega that also had etex on board. In fact, that was supported in context mkii (and some used it because of the input processor which i think was the more innovative thing in omega but i never dived into it, other users did) It makes no sense to discuss into all this as all teams involved in engines have published in user group journals or presented plans at meetings. Also keep in mind that we're talking frontend here; omega is dvi based so like regular tex and etex whatever it does with fonts is not really related to the engine bu tup to the backend: the engine only needs metrics (omega extended tfm into ofm for that). pdftex brought a pdf backend, xetex pipes into a dvi backend, luatex has a pdf backend built in; (nts being related to etec never took of also because it was not that useable and in the meantime pdftex had taken over); there are afaik some very useable japanese tex engines; the fact that dvi survived was due to dvipdfmx development But stand by for a second. I look forward to your quick witted answers. But hear me out Suppose that on my prior message I was referring indeed to 'mkii' and not to 'omega' And also suppose for a second that the term 'omega' is to be replaced with 'mkii' on your reply accordingly After careful observation the resemblance is quite possibly identical, isn't it? and it could also inarguably apply to the circumstances as well. Don't you think? no it isn't, its building upon hat is there: mkii -> mkiv -> mkxl (p
Re: [NTG-context] Off topic: Does a 'free for commercial use' flared-sans font exist in the world?
TeX was > always pretty fast in picking up new stuff (maybe users less so). > > > When it came to commercial fonts the plan of action ahead was by > > including PFC data on these very same commercial fonts that would > > benefit primarily its opentype versions in the long run. > > What is PFC data? The glyph containers on a table-based SFNT format > > > What do you have right now? Opentype fonts only. Sure. Quality can be > > even the same than its type1 counterpart, and at times not so much > > according so some folks that have bothered to go the extra length in > > making the most accurate comparison that's available between them two. > > For most fonts it's just 'more shapes' which then also leads to more > ligatures, kerns etc btu that is already nice. And when fonts lack something > we can always tweak them (runtime). But it's not about kerns nor ligatures but hinting Hans, hinting, and that alone right there, underlies the whole reason by which experts have been infatuated with digital fonts for ages. But I guess what you wrote earlier aligns in more ways than one with what omega end-goal was, whether unwanted or not, routing along to an opentype tunnel vision perspective, while shrugging off other simplistic formats such as afm/tfm by breaking down the glyphs into smaller pieces Although I would see it differently, and perhaps I'm wrong. And perhaps it wasn't practical either, but for some folks it was worth the extra complexities to undertake at the time, while for many wasn't. Regardless, converters to take you over to the containers' formats and include the tables later on was likely needed either way. So why bother, right? But pfc was the correct method and not others :) and for the right reasons. > > > But looking at it from a bright side/perspective, I think we're no > > longer facing the same pre-historic constraints of including a font > > as before, as long as it's not for commercial purposes, You are well > > aware of these non and commercial uses even before your extensive > > search anyway, > > I'm not sure what is the difference between commercial fonts and free ones > as they use the same technology; with some exceptions, fonts are not that > expensive (take lucida from tug, making fonts takes time after all); and for > publishers it's noise on their budgets. > > > p.s many many years ago I read and followed some publications about > > the aformentioned extension and just went over them recently, to > > have an idea what did and did not work. In regards to typefaces, > > its goal was unmatched, or so I think. > > It might be comforting to know that right from the start luatex made a lot > possible wrt fonts (runtime manipulation) and was also one of the first to > support variable fonts, color fonts etc (not that many care about that). And > with luametatex we go even further. > > > > I found some flared-sans fonts, but not one with at least regular, > > > italic, bold, and bold-italic. > > > > > > Is there really not a single flared-sans font that is really free (so > > > also for commercial use) to use out there? > I had to search the net to figure out that flare sans fonts are sans fonts > with serifs > > For those into fonts: > > https://tug.org/TUGboat/tb44-1/tb136carter-romano.pdf > > I a very nice overview of how it went with digital fonts (and what we > probably lost in getting where we are now and might loose soon). > > Hans > > - > Hans Hagen | PRAGMA ADE > Ridderstraat 27 | 8061 GH Hasselt | The Netherlands >tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl > - > > ___ > If your question is of interest to others as well, please add an entry to the > Wiki! > > maillist : ntg-context@ntg.nl / > https://www.ntg.nl/mailman/listinfo/ntg-context > webpage : https://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : https://contextgarden.net > ___ > -- THE LESSER-KNOWN PROGRAMMING LANGUAGES #18: FIFTH FIFTH is a precision mathematical language in which the data types refer to quantity. The data types range from CC, OUNCE, SHOT, and JIGGER to FIFTH (hence the name of the language), LITER, MAGNUM and BLOTTO. Commands refer to ingredients such as CHABLIS, CHARDONNAY, CABERNET, GIN, VERMOUTH, VODKA, SCOTCH, and WHATEVERSAROUND. The
Re: [NTG-context] Off topic: Does a 'free for commercial use' flared-sans font exist in the world?
On 6/17/2023 2:06 AM, linguafalsa--- via ntg-context wrote: On Fri, Jun 16, 2023 at 06:35:49PM +0200, Gerben Wierda via ntg-context wrote: I know this is off topic, but I suspect this community is actually one of the best places to find an answer. It is the best community. And I tell you what. What happened is that all TeX engines have neglected fonts from the beginning. Really? When tex showed up digital font technology was pretty much in flux. And, with metafont being part of the tex ecosystem, one can argue that tex was quite innovative too. Potscript and its fonts came aroudn at the same time and were rather closed technologies. But as soon possible backend drivers (also part of the tex ecosystem) kicked in. Then we got virtual fonts which enhanced tex's capabilities. I really like Optima, and what I really like about it is the 'flared style'. But I would like to move to a flared-sans font that gives me more licensing freedom. I haven't been able to find one after extensive searching. The only one who were reasonably priced (not free) were the URW Classico ones in Adobe Creative Cloud, but those can only be used in Adobe programs like InDesign (and not TeX). Licensing freedom is an oxymoron. There's no freedom in licensing. Only greed. The only extension engine that at one point had a plan in mind, or most of the bases covered in this regard was Omega. One needs morr than plans. Afaik omega was more about input processing and th efont part was mostly going beyond 8 bit fonts but i might have missed something (omega was never productin ready). It is xetex that hooked into opentype although pdftex can actually deal with truetype fonts to some extend. Before there was something 'opentype' we had two competing but similar technologies. And it took a while before it was even clear how to interpre the specification (also think about reverse engeneering fonts and heuristics and ... bugs or features ...). TeX was always pretty fast in picking up new stuff (maybe users less so). When it came to commercial fonts the plan of action ahead was by including PFC data on these very same commercial fonts that would benefit primarily its opentype versions in the long run. What is PFC data? What do you have right now? Opentype fonts only. Sure. Quality can be even the same than its type1 counterpart, and at times not so much according so some folks that have bothered to go the extra length in making the most accurate comparison that's available between them two. For most fonts it's just 'more shapes' which then also leads to more ligatures, kerns etc btu that is already nice. And when fonts lack something we can always tweak them (runtime). But looking at it from a bright side/perspective, I think we're no longer facing the same pre-historic constraints of including a font as before, as long as it's not for commercial purposes, You are well aware of these non and commercial uses even before your extensive search anyway, I'm not sure what is the difference between commercial fonts and free ones as they use the same technology; with some exceptions, fonts are not that expensive (take lucida from tug, making fonts takes time after all); and for publishers it's noise on their budgets. p.s many many years ago I read and followed some publications about the aformentioned extension and just went over them recently, to have an idea what did and did not work. In regards to typefaces, its goal was unmatched, or so I think. It might be comforting to know that right from the start luatex made a lot possible wrt fonts (runtime manipulation) and was also one of the first to support variable fonts, color fonts etc (not that many care about that). And with luametatex we go even further. I found some flared-sans fonts, but not one with at least regular, italic, bold, and bold-italic. Is there really not a single flared-sans font that is really free (so also for commercial use) to use out there? I had to search the net to figure out that flare sans fonts are sans fonts with serifs For those into fonts: https://tug.org/TUGboat/tb44-1/tb136carter-romano.pdf I a very nice overview of how it went with digital fonts (and what we probably lost in getting where we are now and might loose soon). Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https
Re: [NTG-context] TiKz with LMTX
On 6/12/2023 6:49 PM, Carlos via ntg-context wrote: On Thu, Jun 08, 2023 at 11:57:36PM -0400, Aditya Mahajan via ntg-context wrote: On Thu, 8 Jun 2023, Jigé via ntg-context wrote: Thanks a lot Aditya. The very simple TikZ example with the cross works. The more complex example with the trigonometric circle from the pgf manual, quoted in https://wiki.contextgarden.net/TikZ , does not compile unless you also comment out or find(n,"pdftex") in line 181 of the mtx-install-modules.lua file before doing mtxrun --script install-modules --install tikz but I could guess that from a: Driver file ``pgfsys-pdftex.def'' not found.. message Ah so tikz uses both drivers. @Hans, so the validate function should be: local function validate(n) return not ( find(n,"latex") what's the point of latex there? -- or find(n,"lualatex") or for that matter this one lualatex too or find(n,"plain") or find(n,"optex") -- or find(n,"luatex") -- or find(n,"pdftex") ) end just getting rid of files we don't need Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] TiKz with LMTX
On Thu, Jun 08, 2023 at 11:57:36PM -0400, Aditya Mahajan via ntg-context wrote: > On Thu, 8 Jun 2023, Jigé via ntg-context wrote: > > > Thanks a lot Aditya. > > > > The very simple TikZ example with the cross works. > > The more complex example with the trigonometric circle from the pgf manual, > > quoted in https://wiki.contextgarden.net/TikZ , does not compile > > unless you also comment out > > or find(n,"pdftex") > > in line 181 of the mtx-install-modules.lua file > > before doing mtxrun --script install-modules --install tikz > > but I could guess that from a: > > Driver file ``pgfsys-pdftex.def'' not found.. > > message > > Ah so tikz uses both drivers. > > @Hans, so the validate function should be: > > local function validate(n) > return not ( >find(n,"latex") what's the point of latex there? > -- or find(n,"lualatex") or for that matter this one lualatex too > or find(n,"plain") > or find(n,"optex") > -- or find(n,"luatex") > -- or find(n,"pdftex") > ) > end > > > Aditya Through rsync only and by default without mtx-install-modules script, obviously, it'll simply fall back loading by pgfsys-pdftex so you'd be better off by just having local function validate(n) return not ( find(n,"latex") or find(n,"lualatex") or find(n,"plain") or find(n,"optex") -- or find(n,"luatex") or find(n,"pdftex") ) end instead. Also, forget about the curl --ssl or whatever you mentioned earlier. > ___ > If your question is of interest to others as well, please add an entry to the > Wiki! > > maillist : ntg-context@ntg.nl / > https://www.ntg.nl/mailman/listinfo/ntg-context > webpage : https://www.pragma-ade.nl / http://context.aanhet.net > archive : https://bitbucket.org/phg/context-mirror/commits/ > wiki : https://contextgarden.net > ___ -- Brian Kernighan has an automobile which he helped design. Unlike most automobiles, it has neither speedometer, nor gas gauge, nor any of the numerous idiot lights which plague the modern driver. Rather, if the driver makes any mistake, a giant "?" lights up in the center of the dashboard. "The experienced driver", he says, "will usually know what's wrong." ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] TiKz with LMTX
On Fri, 9 Jun 2023, Hans Hagen via ntg-context wrote: > On 6/9/2023 5:57 AM, Aditya Mahajan via ntg-context wrote: > > On Thu, 8 Jun 2023, Jigé via ntg-context wrote: > > > >> Thanks a lot Aditya. > >> > >> The very simple TikZ example with the cross works. > >> The more complex example with the trigonometric circle from the pgf > >> manual, > >> quoted in https://wiki.contextgarden.net/TikZ , does not compile > >> unless you also comment out > >> or find(n,"pdftex") > >> in line 181 of the mtx-install-modules.lua file > >> before doing mtxrun --script install-modules --install tikz > >> but I could guess that from a: > >> Driver file ``pgfsys-pdftex.def'' not found.. > >> message > > > > Ah so tikz uses both drivers. > > > > @Hans, so the validate function should be: > > > > local function validate(n) > > return not ( > > find(n,"latex") > > -- or find(n,"lualatex") > > or find(n,"plain") > > or find(n,"optex") > > -- or find(n,"luatex") > > -- or find(n,"pdftex") > > ) > > end > so an alternative is to ignore deleting those two files > > what is in lualatex that we need? can hardly be something generic pgf/tikz doesn't have anything with lualatex in the name. The only files that match luatex/pdftex are these def files. > (it being pretty big makes me wonder if we should have texmf-tikz for it as i > don't want to polute the modules tree too much - it gets hard to check other > modules for instance when i want to see if some change has impact) If it makes things easier to manage, we can definitely do that. We already have 7 trees, one more isn't going to make any difference :-) Aditya___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] TiKz with LMTX
On 6/9/2023 5:57 AM, Aditya Mahajan via ntg-context wrote: On Thu, 8 Jun 2023, Jigé via ntg-context wrote: Thanks a lot Aditya. The very simple TikZ example with the cross works. The more complex example with the trigonometric circle from the pgf manual, quoted in https://wiki.contextgarden.net/TikZ , does not compile unless you also comment out or find(n,"pdftex") in line 181 of the mtx-install-modules.lua file before doing mtxrun --script install-modules --install tikz but I could guess that from a: Driver file ``pgfsys-pdftex.def'' not found.. message Ah so tikz uses both drivers. @Hans, so the validate function should be: local function validate(n) return not ( find(n,"latex") -- or find(n,"lualatex") or find(n,"plain") or find(n,"optex") -- or find(n,"luatex") -- or find(n,"pdftex") ) end so an alternative is to ignore deleting those two files what is in lualatex that we need? can hardly be something generic (it being pretty big makes me wonder if we should have texmf-tikz for it as i don't want to polute the modules tree too much - it gets hard to check other modules for instance when i want to see if some change has impact) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] TiKz with LMTX
On Thu, 8 Jun 2023, Jigé via ntg-context wrote:
> Thanks a lot Aditya.
>
> The very simple TikZ example with the cross works.
> The more complex example with the trigonometric circle from the pgf manual,
> quoted in https://wiki.contextgarden.net/TikZ , does not compile
> unless you also comment out
> or find(n,"pdftex")
> in line 181 of the mtx-install-modules.lua file
> before doing mtxrun --script install-modules --install tikz
> but I could guess that from a:
> Driver file ``pgfsys-pdftex.def'' not found..
> message
Ah so tikz uses both drivers.
@Hans, so the validate function should be:
local function validate(n)
return not (
find(n,"latex")
-- or find(n,"lualatex")
or find(n,"plain")
or find(n,"optex")
-- or find(n,"luatex")
-- or find(n,"pdftex")
)
end
Aditya
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
Re: [NTG-context] TiKz with LMTX
Thanks a lot Aditya. The very simple TikZ example with the cross works. The more complex example with the trigonometric circle from the pgf manual, quoted in https://wiki.contextgarden.net/TikZ , does not compile unless you also comment out or find(n,"pdftex") in line 181 of the mtx-install-modules.lua file before doing mtxrun --script install-modules --install tikz but I could guess that from a: Driver file ``pgfsys-pdftex.def'' not found.. message Thanks again Jean-Guillaume Le jeudi 8 juin 2023 à 12:28:34 UTC+2, a écrit : Date: Mon, 5 Jun 2023 22:32:37 -0400 (EDT) From: Aditya Mahajan To: Aditya Mahajan via ntg-context Subject: Re: [NTG-context] TiKz with LMTX Message-ID: Content-Type: text/plain; charset="iso-8859-15" On Mon, 5 Jun 2023, Aditya Mahajan via ntg-context wrote: > On Sun, 4 Jun 2023, Jig? via ntg-context wrote: > > > > $ mkdir ~/.local/share/context > > $ cd ~/.local/share/context > > $ wget https://lmtx.pragma-ade.com/install-lmtx/context-linux-64.zip > > $ unzip context-linux-64.zip > > $ sh install.sh > > $ rm context-linux-64.zip > > $ cd ~/.local/share/context/tex > > $ mtxrun --script install-modules --list > > $ mtxrun --script install-modules --install tikz > > (And for good measure, I later did `mtxrun --script install-modules > > --install all`) > > > > $ cd my-working-directory > > $ vi some-sample-context-file.tex > > $ export PATH=/home/myname/.local/share/context/tex/texmf-linux-64/bin:$PATH > > $ context some-sample-context-file.tex > > > > Did I miss anything? It works just fine. > > On a new machine and pgfsys-luatex.def is missing for me as well. I'll try to > check what is going on. This was a bit crazy to track down. Here is the fix: In line 180 of mtx-install-modules.lua, comment the line or find(n,"luatex") Otherwise, the file tex/generic/pgf/systemlayer/pgfsys-luatex.def is not extracted from the tikz.zip! I don't know why OP and I (both on archlinux) were the only ones who had pgfsys-luatex.def missing. Everyone should have been affected by this. Aditya PS: Also on line 103, it may be a good idea to change the curl call to curl --ssl --location mirros.ctan.org will also do a HTTP 302 redirect and without the --location flag, curl will not follow the redirect. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] TiKz with LMTX
On Mon, 5 Jun 2023, Aditya Mahajan via ntg-context wrote: > On Sun, 4 Jun 2023, Jigé via ntg-context wrote: > > > > $ mkdir ~/.local/share/context > > $ cd ~/.local/share/context > > $ wget https://lmtx.pragma-ade.com/install-lmtx/context-linux-64.zip > > $ unzip context-linux-64.zip > > $ sh install.sh > > $ rm context-linux-64.zip > > $ cd ~/.local/share/context/tex > > $ mtxrun --script install-modules --list > > $ mtxrun --script install-modules --install tikz > > (And for good measure, I later did `mtxrun --script install-modules > > --install all`) > > > > $ cd my-working-directory > > $ vi some-sample-context-file.tex > > $ export PATH=/home/myname/.local/share/context/tex/texmf-linux-64/bin:$PATH > > $ context some-sample-context-file.tex > > > > Did I miss anything? It works just fine. > > On a new machine and pgfsys-luatex.def is missing for me as well. I'll try to > check what is going on. This was a bit crazy to track down. Here is the fix: In line 180 of mtx-install-modules.lua, comment the line or find(n,"luatex") Otherwise, the file tex/generic/pgf/systemlayer/pgfsys-luatex.def is not extracted from the tikz.zip! I don't know why OP and I (both on archlinux) were the only ones who had pgfsys-luatex.def missing. Everyone should have been affected by this. Aditya PS: Also on line 103, it may be a good idea to change the curl call to curl --ssl --location mirros.ctan.org will also do a HTTP 302 redirect and without the --location flag, curl will not follow the redirect. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___
Re: [NTG-context] TiKz with LMTX
On Mon, Jun 05, 2023 at 03:43:59PM -0400, Carlos via ntg-context wrote: > On Mon, Jun 05, 2023 at 03:06:10PM +0200, Floris van Manen via ntg-context > wrote: > > > > > > On 05/06/2023 14:49, Carlos via ntg-context wrote: > > > %# Synchronize all modules from ConTeXt Garden in the 'modules' > > > directory, which is created if it doesn’t exist. > > > to wherever the modules are > > > > > > isn't the command > > > > mtxrun --script install-modules --install tikz > > > > or > > > > mtxrun --script install-modules --install --all > > > > doing exactly that? > > > > Okay Floris. I see Aditya nearby. He'll take over from now on :) stand > by please. I know you didn't ask the original question but this is over > the pgfsys-pdftex and the pgfsys-luatex. It's a race between them !! > sort of > > The solutions are a few if any really, either as I suggested first and update > afterwards or install tikz > > if the driver is the problem, what does common sense tells you Floris? > the database needs to be updated, correct? The driver needs to be > loaded somehow, right? > > > system > ConTeXt ver: 2023.06.04 18:58 LMTX fmt: 2023.6.5 int: > english/english > > So install tikz. then run the file > > mtx-install-modules | from > 'https://mirrors.ctan.org/install/graphics/pgf/base/pgf.tds.zip' > mtx-install-modules | into 'texmf-modules' > 64 files of 642 done,2108636 bytes, 0.015 seconds > 128 files of 642 done, 13693106 bytes, 0.089 seconds > 194 files of 642 done, 15194110 bytes, 0.100 seconds > 317 files of 642 done, 16096396 bytes, 0.108 seconds > 382 files of 642 done, 17178524 bytes, 0.116 seconds > 446 files of 642 done, 17768214 bytes, 0.123 seconds > 510 files of 642 done, 18327708 bytes, 0.130 seconds > 574 files of 642 done, 18656649 bytes, 0.136 seconds > 638 files of 642 done, 18860083 bytes, 0.142 seconds > 642 files of 642 done, 18864376 bytes, 0.142 seconds > mtx-install-modules | from > 'https://mirrors.ctan.org/install/graphics/pgf/contrib/pgfplots.tds.zip' > mtx-install-modules | into 'texmf-modules' > 29 files of 168 done, 69116 bytes, 0.002 seconds > 48 files of 168 done,1596420 bytes, 0.010 seconds > 67 files of 168 done,1889062 bytes, 0.012 seconds > 83 files of 168 done,2761170 bytes, 0.017 seconds > 100 files of 168 done,3156638 bytes, 0.021 seconds > 116 files of 168 done,3508192 bytes, 0.024 seconds > 132 files of 168 done,4035279 bytes, 0.027 seconds > 148 files of 168 done,4163894 bytes, 0.029 seconds > 168 files of 168 done,4195360 bytes, 0.029 seconds > mtx-install-modules | from > 'https://mirrors.ctan.org/install/graphics/pgf/contrib/circuitikz.tds.zip' > mtx-install-modules | into 'texmf-modules' >7 files of 70 done, 14967 bytes, 0.000 seconds > 21 files of 70 done, 61604 bytes, 0.001 seconds > 28 files of 70 done,4839027 bytes, 0.033 seconds > 35 files of 70 done,5906994 bytes, 0.040 seconds > 42 files of 70 done,6399050 bytes, 0.043 seconds > 70 files of 70 done,6879048 bytes, 0.045 seconds > mtx-install-modules | wiping 17 files in 'tex/context/third/pgf/**' > mtx-install-modules | wiping 0 files in 'doc/context/third/pgf/**' > mtx-install-modules | wiping 0 files in 'source/context/third/pgf/**' > mtx-install-modules | wiping 0 files in 'tex/context/pgf/**' > mtx-install-modules | wiping 0 files in 'doc/context/pgf/**' > mtx-install-modules | wiping 0 files in 'source/context/pgf/**' > mtx-install-modules | wiping 0 files in 'scripts/pgf/**' > mtx-install-modules | wiping 2 files in 'tex/context/third/pgfplots/**' > mtx-install-modules | wiping 3 files in 'doc/context/third/pgfplots/**' > mtx-install-modules | wiping 1 files in 'source/context/third/pgfplots/**' > mtx-install-modules | wiping 0 files in 'tex/context/pgfplots/**' > mtx-install-modules | wiping 0 files in 'doc/context/pgfplots/**' > mtx-install-modules | wiping 0 files in 'source/context/pgfplots/**' > mtx-install-modules | wiping 4 files in 'scripts/pgfplots/**' > mtx-install-modules | wiping 8 files in 'tex/context/third/circuitikz/**' > mtx-install-modules | wiping 2 files in 'doc/context/third/circuitikz/**' > mtx-install-modules | wiping 0 files in 'source/context/third/circuitikz/**' > mtx-install-modules | wiping 0 files in 'tex/context/circuitikz/**' > mtx-install-modules | wiping 0 files in 'doc/context/circuitikz/**' > mtx-install-modules | wiping 0 files in 'source/context/circuitikz/**' > mtx-install-modules | wiping 0 files in 'scripts/circuitikz/**' > mtx-install-modul
Re: [NTG-context] TiKz with LMTX
On Mon, Jun 05, 2023 at 03:06:10PM +0200, Floris van Manen via ntg-context wrote: > > > On 05/06/2023 14:49, Carlos via ntg-context wrote: > > %# Synchronize all modules from ConTeXt Garden in the 'modules' directory, > > which is created if it doesn’t exist. > > to wherever the modules are > > > isn't the command > > mtxrun --script install-modules --install tikz > > or > > mtxrun --script install-modules --install --all > > doing exactly that? > Okay Floris. I see Aditya nearby. He'll take over from now on :) stand by please. I know you didn't ask the original question but this is over the pgfsys-pdftex and the pgfsys-luatex. It's a race between them !! sort of The solutions are a few if any really, either as I suggested first and update afterwards or install tikz if the driver is the problem, what does common sense tells you Floris? the database needs to be updated, correct? The driver needs to be loaded somehow, right? system > ConTeXt ver: 2023.06.04 18:58 LMTX fmt: 2023.6.5 int: english/english So install tikz. then run the file mtx-install-modules | from 'https://mirrors.ctan.org/install/graphics/pgf/base/pgf.tds.zip' mtx-install-modules | into 'texmf-modules' 64 files of 642 done,2108636 bytes, 0.015 seconds 128 files of 642 done, 13693106 bytes, 0.089 seconds 194 files of 642 done, 15194110 bytes, 0.100 seconds 317 files of 642 done, 16096396 bytes, 0.108 seconds 382 files of 642 done, 17178524 bytes, 0.116 seconds 446 files of 642 done, 17768214 bytes, 0.123 seconds 510 files of 642 done, 18327708 bytes, 0.130 seconds 574 files of 642 done, 18656649 bytes, 0.136 seconds 638 files of 642 done, 18860083 bytes, 0.142 seconds 642 files of 642 done, 18864376 bytes, 0.142 seconds mtx-install-modules | from 'https://mirrors.ctan.org/install/graphics/pgf/contrib/pgfplots.tds.zip' mtx-install-modules | into 'texmf-modules' 29 files of 168 done, 69116 bytes, 0.002 seconds 48 files of 168 done,1596420 bytes, 0.010 seconds 67 files of 168 done,1889062 bytes, 0.012 seconds 83 files of 168 done,2761170 bytes, 0.017 seconds 100 files of 168 done,3156638 bytes, 0.021 seconds 116 files of 168 done,3508192 bytes, 0.024 seconds 132 files of 168 done,4035279 bytes, 0.027 seconds 148 files of 168 done,4163894 bytes, 0.029 seconds 168 files of 168 done,4195360 bytes, 0.029 seconds mtx-install-modules | from 'https://mirrors.ctan.org/install/graphics/pgf/contrib/circuitikz.tds.zip' mtx-install-modules | into 'texmf-modules' 7 files of 70 done, 14967 bytes, 0.000 seconds 21 files of 70 done, 61604 bytes, 0.001 seconds 28 files of 70 done,4839027 bytes, 0.033 seconds 35 files of 70 done,5906994 bytes, 0.040 seconds 42 files of 70 done,6399050 bytes, 0.043 seconds 70 files of 70 done,6879048 bytes, 0.045 seconds mtx-install-modules | wiping 17 files in 'tex/context/third/pgf/**' mtx-install-modules | wiping 0 files in 'doc/context/third/pgf/**' mtx-install-modules | wiping 0 files in 'source/context/third/pgf/**' mtx-install-modules | wiping 0 files in 'tex/context/pgf/**' mtx-install-modules | wiping 0 files in 'doc/context/pgf/**' mtx-install-modules | wiping 0 files in 'source/context/pgf/**' mtx-install-modules | wiping 0 files in 'scripts/pgf/**' mtx-install-modules | wiping 2 files in 'tex/context/third/pgfplots/**' mtx-install-modules | wiping 3 files in 'doc/context/third/pgfplots/**' mtx-install-modules | wiping 1 files in 'source/context/third/pgfplots/**' mtx-install-modules | wiping 0 files in 'tex/context/pgfplots/**' mtx-install-modules | wiping 0 files in 'doc/context/pgfplots/**' mtx-install-modules | wiping 0 files in 'source/context/pgfplots/**' mtx-install-modules | wiping 4 files in 'scripts/pgfplots/**' mtx-install-modules | wiping 8 files in 'tex/context/third/circuitikz/**' mtx-install-modules | wiping 2 files in 'doc/context/third/circuitikz/**' mtx-install-modules | wiping 0 files in 'source/context/third/circuitikz/**' mtx-install-modules | wiping 0 files in 'tex/context/circuitikz/**' mtx-install-modules | wiping 0 files in 'doc/context/circuitikz/**' mtx-install-modules | wiping 0 files in 'source/context/circuitikz/**' mtx-install-modules | wiping 0 files in 'scripts/circuitikz/**' mtx-install-modules | wiping 0 files in 'tex/latex/**' mtx-install-modules | wiping 0 files in 'tex/plain/**' mtx-install-modules | wiping 0 files in 'doc/latex/**' mtx-install-modules | wiping 0 files in 'doc/plain/**' mtx-install-modules | wiping 148 files in 'doc/generic/**' mtx-install-modules | wiping 0 files in 'source/latex/**' mtx-install-modules | wiping 0 files in 'source/plain/**' mtx-install-modules | mtx-install-modules | renewing file database mtx-install-modules | mtx-install-modules | installed: tikz mtx-install-modules | system > b
Re: [NTG-context] TiKz with LMTX
On 6/4/2023 11:11 AM, Jigé via ntg-context wrote:
Hi all.
I'm trying to use TiKz inside ConTeXt. It has not been working for some time...
I checked the messages from last month on the mailing list (late april, early
may). Il didn't quit actually understand what was going on but I read that some
files had to be updated. Maybe as a workaround, while waiting for a new LMTX
format? Users reported it to work after some file updates.
So, because I was using a TeXlive package on Gnu/Archlinux, which might be
updated only after a few months or a year, I followed the wiki and did a
personal fresh install like this :
$ mkdir ~/.local/share/context
$ cd ~/.local/share/context
$ wget https://lmtx.pragma-ade.com/install-lmtx/context-linux-64.zip
$ unzip context-linux-64.zip
$ sh install.sh
$ rm context-linux-64.zip
$ cd ~/.local/share/context/tex
$ mtxrun --script install-modules --list
$ mtxrun --script install-modules --install tikz
(And for good measure, I later did `mtxrun --script install-modules --install
all`)
$ cd my-working-directory
$ vi some-sample-context-file.tex
$ export PATH=/home/myname/.local/share/context/tex/texmf-linux-64/bin:$PATH
$ context some-sample-context-file.tex
Did I miss anything? It works just fine.
But with a TiKz picture included, a very simple one like this:
\usemodule[tikz]
\starttext
We are working on
\starttikzpicture
\draw (-1.5,0) -- (1.5,0);
\draw (0,-1.5) -- (0,1.5);
\stoptikzpicture.
\stoptext
It doesn't compile. The output begins with:
resolvers | formats | executing runner 'run luametatex format':
[...]
and ends with:
[...]
open source > level 4, order 11, name 'pgf.cfg'
close source> level 4, order 11, name 'pgf.cfg'
Driver file for pgf: pgfsys-luatex.def
tex error > tex error on line 1757 in file pgfsys.code.tex: Package pgf
Error: Driver file ``pgfsys-luatex.def'' not found.
what if you run "mtxrun --generate" beforehand?
is that file somewhere in the tree?
it works here
\pgfutil@packageerror
#1#2#3->\errhelp {#3}\errmessage {Package #1 Error: #2}
\pgfutil@IfFileExists
#1#2#3->\openin \pgfutil@inputcheck =#1 \ifeof \pgfutil@inputcheck #3
\relax \else #2\relax \fi \closein \pgfutil@inputcheck
\pgferror{Driver file ``\pgfsysdriver'' not found.}}
This error message was generated by an \errmessage command, so I can't give any
explicit help. Pretend that you're Hercule Poirot: Examine all clues, and deduce
the truth by order and method.
mtx-context | fatal error: return code: 1
The PATH is set correctly, this is not the output from using the regular
TeXlive package which uses luatex, terminates because it doesn't understand
\pgfsetxvec{\pgfpoint{1cm}{0cm}} and makes no reference to Hercule Poirot.
I ingenuously tried to explicitly set some formats in the file
~/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgf.cfg
but with no success.
Is it related to this issue: https://github.com/pgf-tikz/pgf/issues/990 ?
Thanks in advance!...
Best regards
Jean-Guillaume
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
--
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___
